Re: [linux-usb-devel] Re: Fw: Re: oops in choose_configuration()

Alan Stern <[email protected]> wrote:
>
> What about those scheduler changes you found through the bisection search?  
>  Any word on that?

Ingo's gone over them pretty closely.  The current theory is that the CPU
scheduler change alters timing sufficiently for the bug to bite.

The machine passes memtest86.

Ingo's suspecting stack corruption.  Do you know whether USB anywhere does
DMA into automatically-allocated storage (ie: kernel stacks)?

Am about to reboot into a stack-corruption-detector patch from Ingo.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [linux-usb-devel] Re: Fw: Re: oops in choose_configuration()
    • From: Alan Stern <[email protected]>

• References:
  • Re: [linux-usb-devel] Re: Fw: Re: oops in choose_configuration()
    • From: Andrew Morton <[email protected]>
  • Re: [linux-usb-devel] Re: Fw: Re: oops in choose_configuration()
    • From: Alan Stern <[email protected]>

• Prev by Date: Re: [patch 3/4] net: percpufy frequently used vars -- proto.sockets_allocated
• Next by Date: Re: [patch 1/4] net: percpufy frequently used vars -- add percpu_counter_mod_bh
• Previous by thread: Re: [linux-usb-devel] Re: Fw: Re: oops in choose_configuration()
• Next by thread: Re: [linux-usb-devel] Re: Fw: Re: oops in choose_configuration()
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]