At Wed, 26 Nov 2014 16:21:49 +0100,
Takashi Iwai wrote:
>
> At Wed, 26 Nov 2014 15:27:57 +0100,
> Oliver Neukum wrote:
> >
> > On Wed, 2014-11-26 at 15:12 +0100, Takashi Iwai wrote:
> > > At Wed, 26 Nov 2014 23:05:20 +0900,
> > > Marcel Holtmann wrote:
> > > >
> > > > Hi Oliver,
> > > >
> > > >
At Thu, 27 Nov 2014 10:46:05 +0100,
Arend van Spriel wrote:
>
> On 11/27/14 10:29, Arend van Spriel wrote:
> > On 11/27/14 10:17, Takashi Iwai wrote:
> >> At Thu, 27 Nov 2014 09:59:12 +0100,
> >> Arend van Spriel wrote:
> >>>
> >>> On 11/26/14 19:13, Takashi Iwai wrote:
> At Wed, 26 Nov 2014
On 11/27/14 10:29, Arend van Spriel wrote:
On 11/27/14 10:17, Takashi Iwai wrote:
At Thu, 27 Nov 2014 09:59:12 +0100,
Arend van Spriel wrote:
On 11/26/14 19:13, Takashi Iwai wrote:
At Wed, 26 Nov 2014 18:42:46 +0100,
Arend van Spriel wrote:
On 11/26/14 16:27, Takashi Iwai wrote:
At Wed, 26
On 11/27/14 10:17, Takashi Iwai wrote:
At Thu, 27 Nov 2014 09:59:12 +0100,
Arend van Spriel wrote:
On 11/26/14 19:13, Takashi Iwai wrote:
At Wed, 26 Nov 2014 18:42:46 +0100,
Arend van Spriel wrote:
On 11/26/14 16:27, Takashi Iwai wrote:
At Wed, 26 Nov 2014 17:26:15 +0200,
Mihai Donțu wrote:
At Thu, 27 Nov 2014 09:59:12 +0100,
Arend van Spriel wrote:
>
> On 11/26/14 19:13, Takashi Iwai wrote:
> > At Wed, 26 Nov 2014 18:42:46 +0100,
> > Arend van Spriel wrote:
> >>
> >> On 11/26/14 16:27, Takashi Iwai wrote:
> >>> At Wed, 26 Nov 2014 17:26:15 +0200,
> >>> Mihai Donțu wrote:
>
> >>
On 11/26/14 19:13, Takashi Iwai wrote:
At Wed, 26 Nov 2014 18:42:46 +0100,
Arend van Spriel wrote:
On 11/26/14 16:27, Takashi Iwai wrote:
At Wed, 26 Nov 2014 17:26:15 +0200,
Mihai Donțu wrote:
On Wed, 26 Nov 2014 16:19:49 +0100
Takashi Iwai wrote:
At Wed, 26 Nov 2014 16:56:09 +0200,
Miha
At Wed, 26 Nov 2014 18:42:46 +0100,
Arend van Spriel wrote:
>
> On 11/26/14 16:27, Takashi Iwai wrote:
> > At Wed, 26 Nov 2014 17:26:15 +0200,
> > Mihai Donțu wrote:
> >>
> >> On Wed, 26 Nov 2014 16:19:49 +0100
> >> Takashi Iwai wrote:
> >>
> >>> At Wed, 26 Nov 2014 16:56:09 +0200,
> >>> Mihai Do
On 11/26/14 16:27, Takashi Iwai wrote:
At Wed, 26 Nov 2014 17:26:15 +0200,
Mihai Donțu wrote:
On Wed, 26 Nov 2014 16:19:49 +0100
Takashi Iwai wrote:
At Wed, 26 Nov 2014 16:56:09 +0200,
Mihai Donțu wrote:
On Tue, 11 Nov 2014 13:12:28 -0500 Dave Jones wrote:
Since the addition of 10d4c6736e
At Wed, 26 Nov 2014 17:26:15 +0200,
Mihai Donțu wrote:
>
> On Wed, 26 Nov 2014 16:19:49 +0100
> Takashi Iwai wrote:
>
> > At Wed, 26 Nov 2014 16:56:09 +0200,
> > Mihai Donțu wrote:
> > >
> > > On Tue, 11 Nov 2014 13:12:28 -0500 Dave Jones wrote:
> > > > Since the addition of 10d4c6736ea "Blueto
On Wed, 26 Nov 2014 16:19:49 +0100
Takashi Iwai wrote:
> At Wed, 26 Nov 2014 16:56:09 +0200,
> Mihai Donțu wrote:
> >
> > On Tue, 11 Nov 2014 13:12:28 -0500 Dave Jones wrote:
> > > Since the addition of 10d4c6736ea "Bluetooth: btusb: Add Broadcom patch
> > > RAM support", I (and a number of othe
At Wed, 26 Nov 2014 15:27:57 +0100,
Oliver Neukum wrote:
>
> On Wed, 2014-11-26 at 15:12 +0100, Takashi Iwai wrote:
> > At Wed, 26 Nov 2014 23:05:20 +0900,
> > Marcel Holtmann wrote:
> > >
> > > Hi Oliver,
> > >
> > > >> In order to paper over this, we may also remember the failing firmware
> >
At Wed, 26 Nov 2014 16:56:09 +0200,
Mihai Donțu wrote:
>
> On Tue, 11 Nov 2014 13:12:28 -0500 Dave Jones wrote:
> > Since the addition of 10d4c6736ea "Bluetooth: btusb: Add Broadcom patch
> > RAM support", I (and a number of other people[*]) have been seeing
> > this trace on resume from suspend.
On Tue, 11 Nov 2014 13:12:28 -0500 Dave Jones wrote:
> Since the addition of 10d4c6736ea "Bluetooth: btusb: Add Broadcom patch
> RAM support", I (and a number of other people[*]) have been seeing
> this trace on resume from suspend.
>
> WARNING: CPU: 1 PID: 8565 at drivers/base/firmware_class.c:11
On Wed, 2014-11-26 at 15:31 +0100, Takashi Iwai wrote:
> Yes, that's what I mentioned in my reply. But, actually more puzzling
> is that the WARNING shouldn't have been triggered at all. That is,
> something is still racy there, so we'd need to fix it.
Did it trigger before khubd was replaced b
At Wed, 26 Nov 2014 15:23:20 +0100,
Oliver Neukum wrote:
>
> On Wed, 2014-11-26 at 11:53 +0100, Takashi Iwai wrote:
> > At Wed, 26 Nov 2014 11:43:36 +0100,
> > Oliver Neukum wrote:
> > >
> > > On Wed, 2014-11-26 at 11:31 +0100, Takashi Iwai wrote:
> > > > At Wed, 26 Nov 2014 11:10:23 +0100,
> > >
On Wed, 2014-11-26 at 15:12 +0100, Takashi Iwai wrote:
> At Wed, 26 Nov 2014 23:05:20 +0900,
> Marcel Holtmann wrote:
> >
> > Hi Oliver,
> >
> > >> In order to paper over this, we may also remember the failing firmware
> > >> and avoid loading it. This might be an easer way than the endless
> >
On Wed, 2014-11-26 at 11:53 +0100, Takashi Iwai wrote:
> At Wed, 26 Nov 2014 11:43:36 +0100,
> Oliver Neukum wrote:
> >
> > On Wed, 2014-11-26 at 11:31 +0100, Takashi Iwai wrote:
> > > At Wed, 26 Nov 2014 11:10:23 +0100,
> > > Oliver Neukum wrote:
> > > >
> > > > On Wed, 2014-11-26 at 09:52 +0100
On Wed, 2014-11-26 at 23:05 +0900, Marcel Holtmann wrote:
> Hi Oliver,
>
> >> In order to paper over this, we may also remember the failing firmware
> >> and avoid loading it. This might be an easer way than the endless
> >> fight against UMH race...
> >
> >
> > the full fix would be to impleme
At Wed, 26 Nov 2014 23:05:20 +0900,
Marcel Holtmann wrote:
>
> Hi Oliver,
>
> >> In order to paper over this, we may also remember the failing firmware
> >> and avoid loading it. This might be an easer way than the endless
> >> fight against UMH race...
> >
> >
> > the full fix would be to imp
Hi Takashi,
On Wed, 2014-11-26 at 09:52 +0100, Takashi Iwai wrote:
> At Wed, 26 Nov 2014 14:15:27 +0900,
> In order to paper over this, we may also remember the failing firmware
> and avoid loading it. This might be an easer way than the endless
> fight against UMH race
Hi Oliver,
>> In order to paper over this, we may also remember the failing firmware
>> and avoid loading it. This might be an easer way than the endless
>> fight against UMH race...
>
>
> the full fix would be to implement reset_resume() for btusb.
> It seems to me that setup() should be split
At Wed, 26 Nov 2014 11:43:36 +0100,
Oliver Neukum wrote:
>
> On Wed, 2014-11-26 at 11:31 +0100, Takashi Iwai wrote:
> > At Wed, 26 Nov 2014 11:10:23 +0100,
> > Oliver Neukum wrote:
> > >
> > > On Wed, 2014-11-26 at 09:52 +0100, Takashi Iwai wrote:
> > > > At Wed, 26 Nov 2014 14:15:27 +0900,
> > >
On Wed, 2014-11-26 at 11:31 +0100, Takashi Iwai wrote:
> At Wed, 26 Nov 2014 11:10:23 +0100,
> Oliver Neukum wrote:
> >
> > On Wed, 2014-11-26 at 09:52 +0100, Takashi Iwai wrote:
> > > At Wed, 26 Nov 2014 14:15:27 +0900,
> >
> > > In order to paper over this, we may also remember the failing firm
At Wed, 26 Nov 2014 11:10:23 +0100,
Oliver Neukum wrote:
>
> On Wed, 2014-11-26 at 09:52 +0100, Takashi Iwai wrote:
> > At Wed, 26 Nov 2014 14:15:27 +0900,
>
> > In order to paper over this, we may also remember the failing firmware
> > and avoid loading it. This might be an easer way than the e
On Wed, 2014-11-26 at 09:52 +0100, Takashi Iwai wrote:
> At Wed, 26 Nov 2014 14:15:27 +0900,
> In order to paper over this, we may also remember the failing firmware
> and avoid loading it. This might be an easer way than the endless
> fight against UMH race...
Hi,
the full fix would be to impl
At Wed, 26 Nov 2014 14:15:27 +0900,
Marcel Holtmann wrote:
>
> Hi Takashi,
>
> >> Since the addition of 10d4c6736ea "Bluetooth: btusb: Add Broadcom patch
> >> RAM support", I (and a number of other people[*]) have been seeing
> >> this trace on resume from suspend.
> >>
> >> WARNING: CPU: 1 PID:
Hi Takashi,
>> Since the addition of 10d4c6736ea "Bluetooth: btusb: Add Broadcom patch
>> RAM support", I (and a number of other people[*]) have been seeing
>> this trace on resume from suspend.
>>
>> WARNING: CPU: 1 PID: 8565 at drivers/base/firmware_class.c:1127
>> _request_firmware+0x4c1/0x7c
At Tue, 11 Nov 2014 13:12:28 -0500,
Dave Jones wrote:
>
> Since the addition of 10d4c6736ea "Bluetooth: btusb: Add Broadcom patch
> RAM support", I (and a number of other people[*]) have been seeing
> this trace on resume from suspend.
>
> WARNING: CPU: 1 PID: 8565 at drivers/base/firmware_class.
Since the addition of 10d4c6736ea "Bluetooth: btusb: Add Broadcom patch
RAM support", I (and a number of other people[*]) have been seeing
this trace on resume from suspend.
WARNING: CPU: 1 PID: 8565 at drivers/base/firmware_class.c:1127
_request_firmware+0x4c1/0x7c0()
CPU: 1 PID: 8565 Comm: kwor
29 matches
Mail list logo
