2.6.17.10 kernels crash on startup on sun v40z server

Bug #88092 reported by Bartek Wilczynski
4
Affects Status Importance Assigned to Milestone
linux-source-2.6.17 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6-amd64-generic

Installing Edgy on a sun v40z server (x86_64 arch, 4 Opteron cpu, large scsci raid formatted with lvm into xfs /root and /ext2 boot).

Installation went fine, but during startup procedure, the kernel throws a general protection fault:

[ 137.380598] ACPI: PCI Interrupt 0000:20:01.0[A] -> GSI 32 (level, low) -> IRQ 177
[ 137.380646] general protection fault: 0000 [1] SMP
[ 137.382695] CPU 2
[ 137.383722] Modules linked in: shpchp pci_hotplug floppy xfs sd_mod dm_mod ohci_hcd usbcore ide_generic megaraid_mbox megaraid_mm mptspi mptscsih mptba
se scsi_transport_spi scsi_mod ide_cd cdrom generic amd74xx thermal processor fan vesafb capability commoncap vga16fb cfbcopyarea vgastate cfbimgblt cfbfi
llrect fbcon tileblit font bitblit softcursor
[ 137.404531] Pid: 3441, comm: modprobe Not tainted 2.6.17-10-server #2
[ 137.406312] RIP: 0010:[<ffffffff80333db2>] <ffffffff80333db2>{strlen+2}
[ 137.408495] RSP: 0018:ffff8101fb839c90 EFLAGS: 00010246
[ 137.410274] RAX: 0000000000000000 RBX: ffffffff805f4270 RCX: 00000000fffffff4
[ 137.412214] RDX: 0000000000000000 RSI: babababababababa RDI: babababababababa
[ 137.414154] RBP: ffffffff806489e0 R08: 000000000004b000 R09: 0000000000000000
[ 137.452984] R10: 0000000000000000 R11: 0000000000000003 R12: babababababababa
[ 137.493075] R13: ffff8103fc7f8000 R14: 0000000000000001 R15: 0000000000000000
[ 137.534022] FS: 00002b2124ff06d0(0000) GS:ffff8101fc7a1c40(0000) knlGS:0000000000000000
[ 137.617629] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 137.661060] CR2: 00002af8e894d050 CR3: 00000002fc3d5000 CR4: 00000000000006e0
[ 137.705678] Process modprobe (pid: 3441, threadinfo ffff8101fb838000, task ffff810100302a30)
[ 137.795172] Stack: ffffffff80333ee0 0000000000000000 ffffffff806489e0 0000000000000000
[ 137.843709] ffffffff803af8b3 ffff8103fc7f8000 0000000000000001 00000000000000b1
[ 137.942930] ffffffff803428b0 00000000fe4b6000
[ 137.990612] Call Trace: <ffffffff80333ee0>{strstr+32} <ffffffff803af8b3>{dmi_check_system+51}
[ 138.057622] <ffffffff803428b0>{msi_init+32} <ffffffff80343643>{pci_enable_msi+99}
[ 138.123664] <ffffffff8822f87a>{:shpchp:shpc_init+1626} <ffffffff8026a175>{wait_for_completion+165}
[ 138.189095] <ffffffff8822b703>{:shpchp:shpc_probe+147} <ffffffff8033e733>{pci_device_probe+243}
[ 138.254285] <ffffffff803931a5>{driver_probe_device+101} <ffffffff80393280>{__driver_attach+0}
[ 138.319848] <ffffffff803932d8>{__driver_attach+88} <ffffffff80393280>{__driver_attach+0}
[ 138.385844] <ffffffff80392a79>{bus_for_each_dev+73} <ffffffff8039261d>{bus_add_driver+141}
[ 138.452322] <ffffffff8033e9b7>{__pci_register_driver+87} <ffffffff8810b036>{:shpchp:shpcd_init+54}
[ 138.519016] <ffffffff802a9067>{sys_init_module+199} <ffffffff8026544e>{system_call+126}
[ 138.617294]
[ 138.617295] Code: 80 3f 00 74 15 48 89 f8 66 66 90 66 66 90 48 83 c0 01 80 38
[ 138.717113] RIP <ffffffff80333db2>{strlen+2} RSP <ffff8101fb839c90>
[ 138.750628] <6>input: PC Speaker as /class/input/input0

After that, the server stops running the rcS script, but the root console apears and the normal operation can be resumed (mounting filesystems, bringing up network and running daemons).

It happens both with -generic and -server kernels.

Revision history for this message
Cristian Aravena Romero (caravena) wrote :

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description doesn't yet have enough information.

Please include the following additional information, if you have not already done so (please 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" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

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

Changed in linux-source-2.6.17:
assignee: nobody → caravena
status: Unconfirmed → Needs Info
Revision history for this message
Bartek Wilczynski (bartek) wrote : Re: [Bug 88092] Re: 2.6.17.10 kernels crash on startup on sun v40z server

Citing Cristian Aravena Romero <email address hidden>:
> 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.

Output from uname -a:

Linux octopus 2.6.17-10-server #2 SMP Tue Feb 13 01:19:38 UTC 2007 x86_64
GNU/Linux

> 2. Please run the command "dmesg > dmesg.log" and attach the resulting file
> "dmesg.log" to this bug report.

attached

> 3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the
> resulting file "lspci-vvnn.log" to this bug report.
attached.

I've now upgraded to feisty and the problem is gone.

--
regards
   Bartek

> Thanks for taking the time to report this bug. Unfortunately we can't
> fix it, because your description doesn't yet have enough information.
>
> Please include the following additional information, if you have not already
> done so (please pay attention to lspci's additional options), as required by
> the Ubuntu Kernel Team:
>
> For your reference, the full description of procedures for kernel-
> related bug reports is available at [WWW]
> http://wiki.ubuntu.com/DebuggingKernelProblems . Thanks in advance!
>
> ** Changed in: linux-meta (Ubuntu)
> Sourcepackagename: linux-meta => linux-source-2.6.17
>
> ** Changed in: linux-source-2.6.17 (Ubuntu)
> Assignee: (unassigned) => Cristian Aravena Romero
> Status: Unconfirmed => Needs Info
>
> --
> 2.6.17.10 kernels crash on startup on sun v40z server
> https://launchpad.net/bugs/88092
>

Revision history for this message
Bartek Wilczynski (bartek) wrote :

Somehow the attachments did not get to the site. Maybe this time it will work.

Revision history for this message
Bartek Wilczynski (bartek) wrote :

and one more

Changed in linux-source-2.6.17:
assignee: caravena → ubuntu-kernel-team
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

This version of Ubuntu (Edgy Eft) has reached end of life and is not supported anymore. So we are closing this report. If this is still an issue can you try with latest Ubuntu release? Thanks in advance.

Changed in linux-source-2.6.17:
status: Incomplete → Invalid
Revision history for this message
Bartek Wilczynski (bartek) wrote :
  • unnamed Edit (1.2 KiB, text/html; charset=ISO-8859-1)

No, in the newer releases it's ok.

regards Bartek

On Wed, Jun 11, 2008 at 10:09 AM, Jean-Baptiste Lallement <
<email address hidden>> wrote:

> This version of Ubuntu (Edgy Eft) has reached end of life and is not
> supported anymore. So we are closing this report. If this is still an
> issue can you try with latest Ubuntu release? Thanks in advance.
>
> ** Changed in: linux-source-2.6.17 (Ubuntu)
> Status: Incomplete => Invalid
>
> --
> 2.6.17.10 kernels crash on startup on sun v40z server
> https://bugs.launchpad.net/bugs/88092
> You received this bug notification because you are a direct subscriber
> of the bug.
>
>

--
Bartek Wilczynski
==================
Postdoctoral fellow
EMBL, Furlong lab
Meyerhoffstrasse 1,
69012 Heidelberg,
Germany

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thanks for the followup.

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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