Ubuntu
nvidia-kernel-common package

gutsy system hang on hp xw8200

Bug #156885 reported by Alex Chiang on 2007-10-24

4

Affects		Status	Importance	Assigned to	Milestone
	nvidia-kernel-common (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

After upgrading from Feisty to Gutsy, my system experiences frequent, random lockups. System no longer responds to pings.

I configured a serial console, and managed to capture a magic sysrq of the task list, which I will attach. While it was dumping out the information to the console, even the serial console connection hung, so I am not sure if the dump is complete.

Please let me know if this is enough information, or if you need more. This is a pretty serious bug, as it renders my workstation unusable.

Revision history for this message

Alex Chiang (achiang) wrote on 2007-10-24:

#1

sysrq-t dump of hung system Edit (213.2 KiB, text/plain)

Revision history for this message

Alex Chiang (achiang) wrote on 2007-10-24:

#2

lspci output Edit (22.5 KiB, text/plain)

Revision history for this message

Alex Chiang (achiang) wrote on 2007-10-24:

#3

dmesg output Edit (29.8 KiB, text/plain)

Revision history for this message

Alex Chiang (achiang) wrote on 2007-10-24:

#4

dmesg-real Edit (27.2 KiB, text/plain)

Please disregard the prior dmesg. That came from an attempt to boot an older kernel into the gutsy userspace to see if it would bring stability. I am attaching a dmesg with the "real" gutsy kernel that causes the hangs.

Revision history for this message

Alex Chiang (achiang) wrote on 2007-10-26:

#5

I removed nvidia-kernel-common, nvidia-glx, and linux-restricted-modules-2.6.20-xx. I'm not sure if my upgrade from Feisty to Gutsy was botched there. I then reinstalled nvidia-kernel-common, nvidia-glx-new, and linux-restricted-modules-2.6.22-14. I regenerated an xorg.conf using nvidia-xconfig. System seems to be stable again.

Probably some sort of weird kernel module version mismatch. In any case, all is well again.

Revision history for this message

Johnathon (kirrus) wrote on 2007-11-05:

#6

Closing as no-longer a problem. Thanks for reporting a bug; please feel free to continue to submit bug reports when you experience problems.

Kind Regards,
Johnathon

Changed in nvidia-kernel-common:
status:	New → Invalid

Revision history for this message

npendar (pendar) wrote on 2007-11-08:

#7

I had the same problem and performed the above procedure. The system seemed stable but when I looked at my kern.log file, I still saw this:

Nov 8 12:09:19 localhost kernel: [ 40.991494] nvidia: module license 'NVIDIA' taints kernel.
Nov 8 12:09:19 localhost kernel: [ 41.242537] ACPI: PCI Interrupt 0000:40:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Nov 8 12:09:19 localhost kernel: [ 41.242697] PCI: Setting latency timer of device 0000:40:00.0 to 64
Nov 8 12:09:19 localhost kernel: [ 41.242900] NVRM: loading NVIDIA UNIX x86 Kernel Module 100.14.19 Wed Sep 12 14:12:24 PDT 2007

So I changed the video driver from 'nvidia' to 'nv' in my xorg.conf because I didn't want to risk another crash like that. Help is appreciated.

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.