2.6.16-1.2096_FC5, kernel exception when waking up

[Charles-Edouard Ruault]

Hi all,
i've just installed pmud on my powerbook and tried a sleep/resume.
I'm getting the following exception ( running the latest Fedora kernel 
2.6.16-1.2096_FC5 ).
Has anyone had this problem ?

eth0: suspending, WakeOnLan disabled
radeonfb (0000:00:10.0): suspending to state: 2...
radeonfb (0000:00:10.0): resuming from state: 2...
PCI: Enabling device 0000:00:10.0 (0000 -> 0003)
PM: Writing back config space on device 0001:10:12.0 at offset 1. (Was 
100000, writing 100004)
PM: Writing back config space on device 0001:10:12.0 at offset 3. (Was 
0, writing 1000)
PM: Writing back config space on device 0001:10:12.0 at offset 4. (Was 
0, writing a0006000)
PM: Writing back config space on device 0001:10:12.0 at offset f. (Was 
100, writing 134)
PM: Writing back config space on device 0001:10:13.0 at offset 1. (Was 
2100000, writing 2100007)
PM: Writing back config space on device 0001:10:13.0 at offset 3. (Was 
20000, writing 2a808)
PM: Writing back config space on device 0001:10:13.0 at offset 4. (Was 
0, writing a0004000)
PM: Writing back config space on device 0001:10:13.0 at offset 6. (Was 
0, writing b0141110)
PM: Writing back config space on device 0001:10:13.0 at offset 7. (Was 
0, writing 90000000)
PM: Writing back config space on device 0001:10:13.0 at offset 8. (Was 
0, writing 9ffff000)
PM: Writing back config space on device 0001:10:13.0 at offset 9. (Was 
0, writing f3000000)
PM: Writing back config space on device 0001:10:13.0 at offset a. (Was 
0, writing f33ff000)
PM: Writing back config space on device 0001:10:13.0 at offset b. (Was 
0, writing 1000)
PM: Writing back config space on device 0001:10:13.0 at offset c. (Was 
0, writing 11fc)
PM: Writing back config space on device 0001:10:13.0 at offset d. (Was 
0, writing 1400)
PM: Writing back config space on device 0001:10:13.0 at offset e. (Was 
0, writing 15fc)
PM: Writing back config space on device 0001:10:13.0 at offset f. (Was 
34001ff, writing 5c00135)
PCI: Enabling device 0001:10:1b.0 (0000 -> 0002)
PCI: Enabling device 0001:10:1b.1 (0000 -> 0002)
PCI: Enabling device 0001:10:1b.2 (0000 -> 0002)
PM: Writing back config space on device 0001:10:1b.2 at offset 1. (Was 
2100006, writing 2100016)
usb usb4: root hub lost power or was reset
ehci_hcd 0001:10:1b.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
eth0: resuming
PHY ID: 1410cc1, addr: 0
hda: Enabling Ultra DMA 5
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
[C0393E50] [C01D3CF0] ide_intr+0x204/0x240
[C0393E80] [C0059CB8] handle_IRQ_event+0x54/0xa8
[C0393EA0] [C0059E10] __do_IRQ+0x104/0x188
[C0393EC0] [C00057E8] do_IRQ+0x4c/0x7c
[C0393EE0] [C000FC80] ret_from_except+0x0/0x14
--- Exception: 501 at default_idle+0x3c/0x44
    LR = default_idle+0x34/0x44
[C0393FA0] [C00247E0] cpu_idle+0x3c/0x5c (unreliable)
[C0393FB0] [C0003E70] rest_init+0x28/0x38
[C0393FC0] [C0394720] start_kernel+0x19c/0x1b0
[C0393FF0] [000037A0] 0x37a0
hdc: Enabling MultiWord DMA 2
hci_usb 1-1:1.0: no resume for driver hci_usb?
hci_usb 1-1:1.1: no resume for driver hci_usb?
eth0: Link is up at 100 Mbps, full-duplex.
eth0: Pause is disabled
adb: starting probe task...
adb devices: [2]: 2 c4 [3]: 3 1 [7]: 7 1f
ADB keyboard at 2, handler 1
ADB mouse at 3, handler set to 4 (trackpad)
adb: finished probe task...

Here's my /proc/cpuinfo

processor       : 0
cpu             : 7447/7457, altivec supported
clock           : 612.000000MHz
revision        : 0.1 (pvr 8002 0101)
bogomips        : 36.73
timebase        : 18432000
machine         : PowerBook5,2
motherboard     : PowerBook5,2 MacRISC3 Power Macintosh
detected as     : 287 (PowerBook G4 15")
pmac flags      : 0000001b
L2 cache        : 512K unified
pmac-generation : NewWorld

[David Woodhouse]

On Mon, 2006-04-24 at 14:29 +0200, Charles-Edouard Ruault wrote:
> Hi all,
> i've just installed pmud on my powerbook and tried a sleep/resume.
> I'm getting the following exception ( running the latest Fedora
> kernel 
> 2.6.16-1.2096_FC5 ).
> Has anyone had this problem ?

What's the problem? Everything in there looks cosmetic and harmless.

[Charles-Edouard Ruault]

David Woodhouse wrote:
> On Mon, 2006-04-24 at 14:29 +0200, Charles-Edouard Ruault wrote:
> > Hi all,
> > i've just installed pmud on my powerbook and tried a sleep/resume.
> > I'm getting the following exception ( running the latest Fedora
> > kernel 
> > 2.6.16-1.2096_FC5 ).
> > Has anyone had this problem ?
>
> What's the problem? Everything in there looks cosmetic and harmless.

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.

[David Woodhouse]

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?

[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 ....

[David Woodhouse]

On Mon, 2006-04-24 at 15:25 +0200, Charles-Edouard Ruault wrote:
> Badness in wait_for_ready at drivers/ide/ide-iops.c:516
> Call Trace:

That's just a WARN_ON(), which isn't the same as an oops or even a
BUG(). It's a FIXME, which is relatively harmless.

[Charles-Edouard Ruault]

David Woodhouse wrote:
> On Mon, 2006-04-24 at 15:25 +0200, Charles-Edouard Ruault wrote:
> > Badness in wait_for_ready at drivers/ide/ide-iops.c:516
> > Call Trace:
>
> That's just a WARN_ON(), which isn't the same as an oops or even a
> BUG(). It's a FIXME, which is relatively harmless.

I understand it's harmless, but i guess that since it's reported it 
should be fixed anyway ... but as you say, low priority !