2.6.16-1.2096_FC5, kernel exception when waking up

[Charles-Edouard Ruault]

David Woodhouse wrote:
> On Mon, 2006-04-24 at 15:15 +0200, Charles-Edouard Ruault wrote:
>   
>> Well, so far i've not been able to find any side effect of this.
>> It's just that i don't think it's normal seeing things like that, as
>> it certainly outlines a problem  in the  kernel .... and therefore
>> should be fixed. 
>>     
>
> Which bit? The lack of suspend/resume for hci_usb? The harmless warning
> about using mdelay() in IDE code somewhere? The one about the root USB
> host?
>
>   
Well i was talking about this exception:
Badness in wait_for_ready at drivers/ide/ide-iops.c:516
Call Trace:
[C0393C40] [C0007A50] show_stack+0x54/0x184 (unreliable)
[C0393C60] [C000E574] program_check_exception+0x19c/0x520
[C0393CB0] [C000FC34] ret_from_except_full+0x0/0x4c
--- Exception: 700 at wait_for_ready+0x94/0xec
   LR = wait_for_ready+0x3c/0xec
[C0393D70] [C005A01C] disable_irq_nosync+0x7c/0x90 (unreliable)
[C0393D90] [C01DF36C] pmac_ide_do_setfeature+0x108/0x320
[C0393DB0] [C01DF88C] pmac_ide_dma_check+0x308/0x490
[C0393DE0] [C01D36AC] ide_do_request+0x618/0x8cc

Which, as you stated seems to be triggered by the use of mdelay(1) in 
wait_for_ready.
Since i'm not an expert, i won't comment on the fact that is is normal 
or not. I'm just worried when i see a message like 'Badness in 
wait_for_ready at drivers/ide/ide-iops.c:516' and then an exception 
trace ....

-- 
Charles-Edouard Ruault

+33 1 55 34 76 65
ce at idtect.com

Idtect SA
37 Bd des Capucines 
75002 Paris, France
www.idtect.com