Hey - thanks for such a prompt response! Sorry, got the flu bug here, or the flu hog, or whatever, so my head is anything but clear at the moment. Of course. The whole output. 2009/11/17 David Woodhouse <dwmw2@xxxxxxxxxxxxx>: > On Tue, 2009-11-17 at 09:01 +0100, Clemens Ladisch wrote: >> >> > [ 16.216094] EIP: 0060:[<f812c48c>] EFLAGS: 00010206 CPU: 0 >> > [ 16.216099] EIP is at emi62_load_firmware+0x33c/0x740 [emi62] >> >> This is kernel crash, probably due to a bug in the firmware loader. >> Please also show a few more lines before this. > > ... including the line which said what that actual problem was, perhaps? > A NULL pointer dereference? At what address? Here's the full dmesg output: http://pastebay.com/70284 > Also 'list *emi_load_firmware+0x33c' in gdb so we know precisely which > line. Tried to comply, but dbg responds as follows: "No symbol table is loaded. Use the "file" command." Is there anything I'm missing? Haven't used the debugger before *sheepish grin*. Eh, wasn't that a name of a robot species in Chrono Trigger? There was also a weaker type called "bugger", no less; used to crack me up all the time back in the day (note to self: well done, smeghead, just keep on hiding your inability to make heads or tails of the dbg manual behind an array of irrelevant associations to all sorts of things generally associated with geekdom, and no one will ever notice, evvah) >> David, do you have any clue what could be going on? > > Not really -- this driver was using the same type of 'hex records' > before we touched it. Apply this, and maybe we'll see a little bit more > clearly what's going on... > > diff --git a/drivers/usb/misc/emi62.c b/drivers/usb/misc/emi62.c > index 602ee05..e370715 100644 > --- a/drivers/usb/misc/emi62.c > +++ b/drivers/usb/misc/emi62.c > @@ -130,6 +130,8 @@ static int emi62_load_firmware (struct usb_device *dev) <...> Erm, can't seem to find the file to patch. The last kernel came out of the box; haven't built a more compact version of my own as to yet (still need to figure out whether the rt patches are included in the latest unstable version, or constitute a branch of their very own). Guess the headers won't do, then, will they? Thanks for expressing such willingness to help, at any rate, and sorry for not coming across as the sharpest biscuit in this'ere crayon box. It's all that smeg in me head. Smeg flu, that's what it is. A new strain. And a perfect excuse for passing off me general ignorance as a temporary condition based on justifiable physiological premises, wot loik. Dunno if the kernel config is of any interest or use to anyone here, but here it is just in case: http://pastebay.com/70287 http://pastebay.com/70288 Will gladly find and post any data I can find, provided I can find it. And thanks again. Over/out, Pope Mickey XLII of Two Curry Stains, Three Vindaloo Blotches and One Zarked-Up Kernel Module. _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
