2.6.28 crashes when powernowd is started

[Tom Panning]

When I select 2.6.28-11 from the grub boot menu, my system crashes before I can log in with what looks like a kernel panic or oops (a backtrace in the kernel appears on the screen). If I select 2.6.27-11, the system runs fine.

I ran 2.6.28-11 kernel in recovery mode and selected the netroot option and the system runs. If I then run "/etc/init.d/powernowd start", I the system crashes with the kernel backtrace.

This behavior started when I upgraded from Ubuntu 8.10 to 9.04 beta. Please let me know if there is any other information that would be useful.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
HalComputerInfo: Error: command ['lshal', '-u', '/org/freedesktop/Hal/devices/computer'] failed with exit code 1: error: dbus_bus_get: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
Lsusb:
 Bus 001 Device 003: ID 05e3:0710 Genesys Logic, Inc. USB 2.0 33-in-1 Card Reader
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 002: ID 0488:00df Cirque Corp.
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Package: linux-image-2.6.28-11-generic 2.6.28-11.41
ProcCmdLine: root=UUID=1e4fffe1-9d2b-4ed0-8e76-f71ed4987003 ro single
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.28-11.41-generic
SourcePackage: linux

[Leann Ogasawara (leannogasawara)]

Hi Tom,

Is the kernel oops/panic captured in either your dmesg output or /var/log/kern.log.0 ? If so, could you attach it here? If not, would you be able to take a digital photo of it and attach the photo here? Thanks.

[Tom Panning (lurchvt)]

I'm attaching the kern.log from the crash.

[xteejx (xteejx)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test the current Ubuntu version (10.04). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect <bug #>, and any other logs that are relevant for this particular issue.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]