Now that ken@ has checked in the SMR code I'm wondering how I can see
whether it's having any effect.
I have a 8TB SMR disk in a USB3 enclosure. Does the kernel emit any
sort of trace to indicate that it sees the drive as SMR and takes
that into account?
I have the probe trace enabled in my kern
On 26/05/2016 7:24 AM, Maksim Yevmenkin wrote:
can you also please try to start it manually and see where it stops?
i.e. something like
# sh -x /etc/rc.d/bluetooth start ubt0
Thanks for responding. The output of that command is below. I'll do some
more diagnosis when I get home tonight.
+ /u
Graham,
>> can you also please try to start it manually and see where it stops?
>> i.e. something like
>>
>> # sh -x /etc/rc.d/bluetooth start ubt0
>
> Thanks for responding. The output of that command is below. I'll do some
> more diagnosis when I get home tonight.
thanks a lot
[...]
> + /usr/
On 26/05/2016 01:56 AM, Maksim Yevmenkin wrote:
> Hi Graham
>
> On Tue, May 24, 2016 at 1:31 AM, Graham Menhennitt
> wrote:
>> I've been running 11-current AMD64 on this machine for about a year. It
>> has a bluetooth dongle that has worked correctly up until a week ago. I
>> updated to the latest
hiya,
I wrote a replacement ath3k bluetooth firmware upload tool, based on
the ath3k driver in linux. all the driver does is inject the "right"
firmware / config combination into the bluetooth chips.
https://github.com/erikarn/ath3k
I'd like to land this in -HEAD before 11, as it enables all of
hiya,
I wrote a replacement ath3k bluetooth firmware upload tool, based on
the ath3k driver in linux. all the driver does is inject the "right"
firmware / config combination into the bluetooth chips.
https://github.com/erikarn/ath3k
I'd like to land this in -HEAD before 11, as it enables all of
Hi Graham
On Tue, May 24, 2016 at 1:31 AM, Graham Menhennitt
wrote:
> I've been running 11-current AMD64 on this machine for about a year. It
> has a bluetooth dongle that has worked correctly up until a week ago. I
> updated to the latest source around then, so I presume that's what broke it.
c
On Wed, May 25, 2016 at 14:36:59 +0200, Gary Jennejohn wrote:
> On Wed, 25 May 2016 08:15:11 +0200
> Gary Jennejohn wrote:
>
> > On Tue, 24 May 2016 15:10:41 -0400
> > "Kenneth D. Merry" wrote:
> >
> > > Can you send full dmesg output from the working kernel?
> > >
> >
> > I'll give it a tr
On Wed, 25 May 2016 08:15:11 +0200
Gary Jennejohn wrote:
> On Tue, 24 May 2016 15:10:41 -0400
> "Kenneth D. Merry" wrote:
>
> > Can you send full dmesg output from the working kernel?
> >
>
> I'll give it a try and hope that the mail server doesn't strip it ==>
> dmesg.boot.gz.
>
> > It lo
