Re: More experiences with 2.6.13-rc3 with ec_polling patch

[Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>]

Hi!

> 5) After resume from S4:
> 
> irq 10: nobody cared (try booting with the "irqpoll" option)
>  [<c01412aa>] __report_bad_irq+0x2a/0xa0
>  [<c0140a50>] handle_IRQ_event+0x30/0x70
>  [<c01413c0>] note_interrupt+0x80/0xf0
>  [<c0140bc4>] __do_IRQ+0x134/0x140
>  [<c0105f73>] do_IRQ+0x23/0x40
>  [<c0103f16>] common_interrupt+0x1a/0x20
>  [<c0124773>] __do_softirq+0x43/0xb0
>  [<c012480d>] do_softirq+0x2d/0x30
>  [<c01248e7>] irq_exit+0x37/0x40
>  [<c0105f78>] do_IRQ+0x28/0x40
>  [<c0103f16>] common_interrupt+0x1a/0x20
>  [<c039f360>] schedule+0x0/0x650
>  [<c039fa63>] preempt_schedule_irq+0x43/0x80
>  [<c010349e>] need_resched+0x1f/0x21
>  [<c013ee20>] swsusp_suspend+0x50/0xc0
>  [<c013faac>] pm_suspend_disk+0x3c/0x90
>  [<c013d86c>] enter_state+0x6c/0x70
>  [<c013d87f>] software_suspend+0xf/0x20
>  [<c0247322>] acpi_system_write_sleep+0x6a/0x84
>  [<c0162716>] vfs_write+0xb6/0x180
>  [<c01628b1>] sys_write+0x51/0x80
>  [<c0103559>] syscall_call+0x7/0xb
> handlers:
> [<dc86e850>] (snd_intel8x0_interrupt+0x0/0x240 [snd_intel8x0])
> Disabling IRQ #10
> 
> ...and then
> 
> ohci_hcd 0000:00:02.3: Unlink after no-IRQ?  Controller is probably
> using the wrong IRQ.

Okay, can you enable debugging in .../usb/core/hcd-pci.c and see what
happens? It seems to call request_irq in resume routine, add printk to
verify that it really does call it.

Oh and probably Cc: some usb list, or David Brownell directly.

								Pavel
-- 
teflon -- maybe it is a trademark, but it should not be.


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click