I've reproduced this panic with a virgin (kernel.org) 2.6.15.7 (I reused the ubuntu 2.6.15-23-server config with make oldconfig). I could NOT reproduce the panic with 2.6.19.1. So logically methinks something was fixed along the way.
Any pointers for what to do next? Anyone want to lend a hand in nailing this bug?
I've reproduced this panic with a virgin (kernel.org) 2.6.15.7 (I reused the ubuntu 2.6.15-23-server config with make oldconfig). I could NOT reproduce the panic with 2.6.19.1. So logically methinks something was fixed along the way.
Any pointers for what to do next? Anyone want to lend a hand in nailing this bug?