Hi Alan, ext Alan Stern wrote:Second try, slightly different tack: no dump_stack() in the _irq() functions, but disabled/enabled indication. Plus debugging code added in usb_hcd_add() to see the interrupt registration. Again too much data was printed for the bug to appear. Looking at the collected data it looks like - ehci_irq() is always entered with interrupts enabled (WRONG). - uhci_irq() is entered sometimes with either interrupts enabled (WRONG) or disabled (OK). But both interrupts are registered with IRQF_DISABLED... Regards, Stefan --- Stefan Becker E-Mail: Stefan.Becker@nokia.com
| Ingo Molnar | [patch 12/13] syslets: x86: optimized copy_uatom() |
| Greg Kroah-Hartman | [PATCH 017/196] aoechr: Convert from class_device to device |
| Yinghai Lu | Re: 2.6.26, PAT and AMD family 6 |
| Jan Engelhardt | intel iommu (Re: -mm merge plans for 2.6.23) |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | [GIT]: Networking |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Natalie Protasevich | [BUG] New Kernel Bugs |
