On Sat, 28 Jun 2008, Stefan Becker wrote:It certainly looks like you've found a flaw in the core kernel. Or else a subtle hardware flaw in your CPU... Just to be certain, take out all your new code and instead add a simple test at the start of usb_hcd_irq() in hcd.c. That routine is the registered handler for USB interrupts. If interrupts are ever enabled at that spot, then something is badly wrong. You might also keep track of the total number of each type of call, so whenever you find interrupts are enabled, you can print out something like this: usb_hcd_irq(): interrupts disabled %d, enabled %d where the two values are the numbers of times the routine has been called with interrupts off or on, respectively. You don't have to run this for a long time; since the test code should _never_ trigger, any output at all will indicate a real problem. When you get that, change the Subject of your email to make it more noticeable. A line like: BUG in 2.6.26-rc8 interrupt handling! should draw people's attention. :-) Include a description of the problem and a copy of /proc/interrupts. Alan Stern --
| Theodore Tso | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
| Amit K. Arora | [RFC] Heads up on sys_fallocate() |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 011/196] sysfs: Fix a copy-n-paste typo in comment |
git: | |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Frans Pop | svc: failed to register lockdv1 RPC service (errno 97). |
