[Jaunty] APIC error on CPU crashes system

[Mark Eaton]

Using alpha 6 of 9.04 I've started getting alot of system hangs (see the following kern.log messges)
I've currently got 2.6.28-11-generic but I was also getting it with 2.6.8-10.
I don't always get a useful trace in the log but when I do it isn't in the one application.

kern.log messages - http://launchpadlibrarian.net/24170669/eaton_kern.log
(separate attachment in comment 4)

[Connor Imes (ckimes)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux (the kernel).
For future reference you might be interested to know that a lot of applications have bug reporting functionality built in to them. This can be accessed via the Report a Problem option in the Help menu for the application with which you are having an issue. You can learn more about this feature at https://wiki.ubuntu.com/ReportingBugs.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

Also, does the problem still exist if you use "noapic nolapic" as boot options?

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

[Mark Eaton (eaton-mark)]

I will test the noapic and nolapic options and see if they help. I'm also going to test without the nvidia driver. The other information is below.

Linux G1S 2.6.28-11-generic #34-Ubuntu SMP Tue Mar 17 20:33:41 UTC 2009 x86_64 GNU/Linux

dmesg

[ 0.000000] BIOS EBDA/lowmem at: 0009fc00/0009fc00
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.28-11-generic (buildd@yellow) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #34-Ubuntu SMP Tue Mar 17 20:33:41 UTC 2009 (Ubuntu 2.6.28-11.34-generic)
[ 0.000000] Command line: root=UUID=42f97515-87f5-49c7-808c-60bb647d2a5a ro quiet splash
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 00000000bffb0000 (usable)
[ 0.000000] BIOS-e820: 00000000bffb0000 - 00000000bffbe000 (ACPI data)
[ 0.000000] BIOS-e820: 00000000bffbe000 - 00000000bfff0000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000bfff0000 - 00000000c0000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
[ 0.000000] BIOS-e820: 0000000100000000 - 0000000140000000 (usable)
[ 0.000000] DMI 2.4 present.
[ 0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working it around.
[ 0.000000] last_pfn = 0x140000 max_arch_pfn = 0x3ffffffff
[ 0.000000] last_pfn = 0xbffb0 max_arch_pfn = 0x3ffffffff
[ 0.000000] Scanning 0 areas for low memory corruption
[ 0.000000] modified physical RAM map:
[ 0.000000] modified: 0000000000000000 - 0000000000010000 (reserved)
[ 0.000000] modified: 0000000000010000 - 000000000009fc00 (usable)
[ 0.000000] modified: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] modified: 00000000000e4000 - 0000000000100000 (reserved)
[ 0.000000] modified: 0000000000100000 - 00000000bffb0000 (usable)
[ 0.000000] modified: 00000000bffb0000 - 00000000bffbe000 (ACPI data)
[ 0.000000] modified: 00000000bffbe000 - 00000000bfff0000 (ACPI NVS)
[ 0.000000] modified: 00000000bfff0000 - 00000000c0000000 (reserved)
[ 0.000000] modified: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] modified: 00000000ffb00000 - 0000000100000000 (reserved)
[ 0.000000] modified: 0000000100000000 - 0000000140000000 (usable)
[ 0.000000] init_memory_mapping: 0000000000000000-00000000bffb0000
[ 0.000000] 0000000000 - 00bfe00000 page 2M
[ 0.000000] 00bfe00000 - 00bffb0000 page 4k
[ 0.000000] kernel direct mapping tables up to bffb0000 @ 10000-15000
[ 0.000000] last_map_addr: bffb0000 end: bffb0000
[ 0.000000] init_memory_mapping: 0000000100000000-0000000140000000
[ 0.000000] 0100000000 - 0140000000 page 2M
[ 0.000000] kernel direct mapping tables up to 140000000 @ ...

[Mark Eaton (eaton-mark)]

System won't boot with nolapic but I'm currently testing it with noapic

[Connor Imes (ckimes)]

Thank you for providing that, but can you please upload the files as separate attachments like I initially requested rather than dumping all the output into a comment. It really makes it much easier to read and filter through. You can attach one file at a time using the Attachment section at the bottom of this bug report page, under "Add a comment/attachment". It is very much appreciated. Thank you.

Also, I noticed you are using a modified kernel, which I think is for an Asus system. We may need to take this bug upstream since you are not using a kernel direct from the Ubuntu repositories. More can be found about filing kernel bugs upstream here - https://wiki.ubuntu.com/Bugs/Upstream/kernel

I attached the kern.log output you posted in the initial description of this bug report, I will edit it out of the description.

Again, thank you for taking the time to report this and help make Ubuntu better!

[Mark Eaton (eaton-mark)]

Ok It crashed with noapic for me last night. (see attached kern.log)

I'm not sure what you mean about the modified kernel. I'm just using the default 64 bit kernel that gets installed/upgraded by installation/apt.

I will try to test the problem without the nvidia driver installed now.

[Mark Eaton (eaton-mark)]

Without the nvidia module I was unable to get the system to crash during use. However when I shut the system down it failed to power off and there was an APIC error in the log when I rebooted (see attached)

[Connor Imes (ckimes)]

Thank you for attaching those logs, I will mark this bug as Triaged so the kernel team can look at it and decide what else might be needed. Thanks again for reporting this bug.

[Mark Eaton (eaton-mark)]

I switched to using the 173 version of the nvidia driver and the problem hasn't occured since (a few weeks now) so I would guess that this is caused by some problem with the 180 drivers and the 2.6.28 kernel.

[Mark Eaton (eaton-mark)]

Forgot to mention that the problem where it won't power down correctly seems unrelated. It works fine unless I have USB headphones attached.

[Mark Eaton (eaton-mark)]

Ok, the laptop died and ASUS had to replace the motherboard. Since getting it back I haven't had any problems so I would guess that problems were due to the pending hardware failure.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, 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.]

[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.]