[Gllug] Broken kernel code in Ubuntu too!

Nix nix at esperi.org.uk
Tue Nov 1 12:29:42 UTC 2005


On Mon, 31 Oct 2005, Adrian McMenamin mused:
> The rest of the stack trace doesn't help me identify what's broken -  a
> module appears to be failing though...

Yeah, a modprobe of the i82365 module is failing.

> [4294712.021000] Call Trace:
> [4294712.021000]  [<c0112d5a>] complete+0x1a/0x24
> [4294712.021000]  [<c019965b>] kobject_cleanup+0x40/0x65
> [4294712.021000]  [<c0199680>] kobject_release+0x0/0xa
> [4294712.021000]  [<c0199d92>] kref_put+0x46/0x54
> [4294712.021000]  [<c01996a0>] kobject_put+0x16/0x19
[kobject_cleanup(), eliminated by the sibcall optimization]
> [4294712.021000]  [<c0199680>] kobject_release+0x0/0xa
> [4294712.021000]  [<f8b1eda8>] init_i82365+0x70/0x165 [i82365]

I can't figure out how kobject_release() is getting called on a few
seconds' inspection, though. It's not macro-expanded by anything
called in init_i82365() and it's not sibcalled.

I'd guess that one of the sysfs registration or driver unregistration
calls are failing. Is anything in the dmesg log about module
initialization failure before this message?

> And I cannot seem to get the sound to work - not sure why. As far as I
> can see I have the volume for output tuned up...

Is your sound card a PCMCIA device?

-- 
`"Gun-wielding recluse gunned down by local police" isn't the epitaph
 I want. I am hoping for "Witnesses reported the sound up to two hundred
 kilometers away" or "Last body part finally located".' --- James Nicoll
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug




More information about the GLLUG mailing list