On Mon, 2008-12-22 at 15:53 -0500, Bob Copeland wrote:
> On Mon, Dec 22, 2008 at 12:31 AM, Soeren Sonnenburg wrote:
> > Hi,
> >
> > I was using the ath5k_pci driver on a macbook pro 1,1 and it is working
> > for some time but then suddenly messages like the ones below appear and
> > I have to *tur
2008/12/22 Bob Copeland :
> On Mon, Dec 22, 2008 at 4:39 PM, Jiri Slaby wrote:
>>>
>>> Does the _HW lockup_ happen even with 2.6.28? The lockup should be gone
>>> there
>>> (with the messages still present).
>>
>> I see Bob already replied, ignore me, he knows better.
>
> I thought Felix's patch
On Mon, 2008-12-22 at 16:48 -0500, Bob Copeland wrote:
> On Mon, Dec 22, 2008 at 4:39 PM, Jiri Slaby wrote:
> >>
> >> Does the _HW lockup_ happen even with 2.6.28? The lockup should be gone
> >> there
> >> (with the messages still present).
> >
> > I see Bob already replied, ignore me, he knows b
On Mon, Dec 22, 2008 at 4:39 PM, Jiri Slaby wrote:
>>
>> Does the _HW lockup_ happen even with 2.6.28? The lockup should be gone there
>> (with the messages still present).
>
> I see Bob already replied, ignore me, he knows better.
I thought Felix's patch had gone into .28, but in fact it hasn't.
On 12/22/2008 10:37 PM, Jiri Slaby wrote:
> On 12/22/2008 09:58 PM, Andrew Morton wrote:
>> (cc linux-wireless)
>>
>> On Mon, 22 Dec 2008 06:31:53 +0100
>> Soeren Sonnenburg wrote:
>>
>>> Hi,
>>>
>>> I was using the ath5k_pci driver on a macbook pro 1,1 and it is working
>>> for some time but then
On 12/22/2008 09:58 PM, Andrew Morton wrote:
> (cc linux-wireless)
>
> On Mon, 22 Dec 2008 06:31:53 +0100
> Soeren Sonnenburg wrote:
>
>> Hi,
>>
>> I was using the ath5k_pci driver on a macbook pro 1,1 and it is working
>> for some time but then suddenly messages like the ones below appear and
>
On Mon, Dec 22, 2008 at 12:31 AM, Soeren Sonnenburg wrote:
> Hi,
>
> I was using the ath5k_pci driver on a macbook pro 1,1 and it is working
> for some time but then suddenly messages like the ones below appear and
> I have to *turn off* the machine to get it back working (even booting to
> osx is
