I also have an Armada E500 and had the same kernel oops in jaunty and
did not have that problem with hardy.

I think I've found a possible problem with the radio-maestro module.
With this patch I did not have a kernel oops and could boot without
adding any modules to /etc/modprobe.d/blacklist.conf.

The problem seems to be that video_device_release is called twice (once
in video_unregister_device, and once at the errfr1 label). One of the
last commits in 2.6.28 for this module was "add all missing
video_device_release callbacks", in case "radio_power_on(radio_unit)"
fails, this function is called twice. In kernel version 2.6.30 this
module is converted to a v4l2_device and the problem is probably fixed
there.

However I didn't compile a debug version, I only used info that was
available here, so I am not entirely sure this solves the problem. Can
someone confirm this is correct and really fixes the problem?

** Attachment added: "radio-maestro-oops.patch"
   http://launchpadlibrarian.net/29579711/radio-maestro-oops.patch

-- 
radio_maestro module generates kernel oops and crash
https://bugs.launchpad.net/bugs/357724
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to