Still fresh, damnit!
- Oct 6, 2008
- Somewhere off the coast of the EU
Yeah, looks like it's got its knickers in a twist during some typec_fusb302 initialisation stuff, judging by what comes just before that crash and the stack trace. It seems to have loaded and address from 00a0 (probably in the address space of the kernel object, mapped via a mmu, so that's not too crazy, on consideration) and getting 0 then trying to jump there (which is where it all falls down). It does then carry on detecting new filesystems that come online, but if that's stopped it initiing properly and creating a login for you then that's rather irrelevant.