Boot error 2.6.17-11-386 : [171799607.172000] BUG: soft lockup detected on CPU#0

Thanks for your bug report. Could you please add the full output of 'lspci -vv' and 'lspci -vvn' as attachments to your bug report? Thanks in advance.

>>>>> "Brian" == Brian Murray <email address hidden> writes:

Brian> Thanks for your bug report. Could you please add the full
Brian> output of 'lspci -vv' and 'lspci -vvn' as attachments to your
Brian> bug report? Thanks in advance.

The below is when using the version 2.6.17-10-386 where there is no
bug. Is that what you need? Sorry for the late answer.

00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03)
 Subsystem: Dell Unknown device 01c2
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
 Latency: 0
 Capabilities: <access denied>

00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express PCI Express Root Port (rev 03) (prog-if 00 [Normal decode])
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 0, Cache Line Size: 64 bytes
 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
 Memory behind bridge: ed000000-efefffff
 Prefetchable memory behind bridge: 00000000d0000000-00000000dff00000
 Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
 BridgeCtl: Parity- SERR+ NoISA- VGA+ MAbort- >Reset- FastB2B-
 Capabilities: <access denied>

00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
 Subsystem: Dell Unknown device 01c2
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 0, Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 50
 Region 0: Memory at efffc000 (64-bit, non-prefetchable) [size=16K]
 Capabilities: <access denied>

00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01) (prog-if 00 [Normal decode])
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 0, Cache Line Size: 64 bytes
 Bus: primary=00, secondary=0b, subordinate=0b, sec-latency=0
 Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
 BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
 Capabilities: <access denied>

00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 01) (prog-if 00 [Normal decode])
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 0, Cache Line Size: 64 bytes
 Bus: primary=00, secondary=0c, subordinate=0c, sec-latency=0
 Memory behind bridge: ecf00000-ecffffff
 Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
 BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
 Capabili...

Could you please run 'dmesg > dmesg.log' and give us dmesg.log as an attachment?

>>>>> "Mark" == Mark Reitblatt <email address hidden> writes:

Mark> Could you please run 'dmesg > dmesg.log' and give us dmesg.log
Mark> as an attachment?

Mark> ** Changed in: linux-source-2.6.17 (Ubuntu) Status: Confirmed =>
Mark> Needs Info

Mark> -- Boot error 2.6.17-11-386 : [171799607.172000] BUG: soft
Mark> lockup detected on CPU#0 https://launchpad.net/bugs/86441

--
Associate Prof. Ph.D Torben Knudsen Phone : (+45) 9635 8670
Section of Automation and Control, Email : <email address hidden>
Department of Electronic Systems,
Aalborg University
Fredrik Bajersvej 7
DK-9220 Aalborg Ø
Denmark

The status for this bug is "Needs info". I thought I have send all
you asked fore. If you need more please tell me what it is?

Thanks for your effort.
--
Associate Prof. Ph.D Torben Knudsen Phone : (+45) 9635 8670
Section of Automation and Control, Email : <email address hidden>
Department of Electronic Systems,
Aalborg University
Fredrik Bajersvej 7
DK-9220 Aalborg Ø
Denmark

I'm sorry, but I don't see where we have the output for dmesg? Please run 'dmesg > dmesg.log' and give us dmesg.log as an attachment.

>>>>> "Mark" == Mark Reitblatt <email address hidden> writes:

Mark> I'm sorry, but I don't see where we have the output for dmesg?
Mark> Please run 'dmesg > dmesg.log' and give us dmesg.log as an
Mark> attachment.

Here it is

Mark> -- Boot error 2.6.17-11-386 : [171799607.172000] BUG: soft
Mark> lockup detected on CPU#0 https://bugs.launchpad.net/bugs/86441
Mark> You received this bug notification because you are a direct
Mark> subscriber of the bug.

--
Associate Prof. Ph.D Torben Knudsen Phone : (+45) 9635 8670
Section of Automation and Control, Email : <email address hidden>
Department of Electronic Systems,
Aalborg University
Fredrik Bajersvej 7
DK-9220 Aalborg Ø
Denmark

Unfortunately, I don't think launchpad supports attachments by email. You'll have to go to the actual bug report itself (link at the bottom of this email) and attach it.

Please find dmesg.log attached

>>>>> "Mark" == Mark Reitblatt <email address hidden> writes:

Mark> Unfortunately, I don't think launchpad supports attachments by
Mark> email. You'll have to go to the actual bug report itself (link
Mark> at the bottom of this email) and attach it.

Done

Mark> ** Changed in: linux-source-2.6.17 (Ubuntu) Assignee:
Mark> (unassigned) => Mark Reitblatt

Mark> ** Changed in: linux-source-2.6.17 (Ubuntu) Importance: High =>
Mark> Undecided

Mark> -- Boot error 2.6.17-11-386 : [171799607.172000] BUG: soft
Mark> lockup detected on CPU#0 https://bugs.launchpad.net/bugs/86441
Mark> You received this bug notification because you are a direct
Mark> subscriber of the bug.

--
Associate Prof. Ph.D Torben Knudsen Phone : (+45) 9635 8670
Section of Automation and Control, Email : <email address hidden>
Department of Electronic Systems,
Aalborg University
Fredrik Bajersvej 7
DK-9220 Aalborg Ø
Denmark

This looks like a dupe of Bug #63418. It's marked as fixed in Feisty, so you should consider upgrading when Feisty stable is released (this week?).

Yep, it works in Feisty, so it can be closed.

> *** This bug is a duplicate of bug 63418 ***
> https://bugs.launchpad.net/bugs/63418
>
> This looks like a dupe of Bug #63418. It's marked as fixed in Feisty, so
> you should consider upgrading when Feisty stable is released (this
> week?).
>
> ** This bug has been marked a duplicate of bug 63418
> CPU soft lockup during boot if ipw3945 kill switch is on
>
> ** Changed in: linux-source-2.6.17 (Ubuntu)
> Status: Needs Info => Confirmed

>>>>> "Mark" == Mark Reitblatt <email address hidden> writes:

Mark> *** This bug is a duplicate of bug 63418 ***
Mark> https://bugs.launchpad.net/bugs/63418

Mark> This looks like a dupe of Bug #63418. It's marked as fixed in
Mark> Feisty, so you should consider upgrading when Feisty stable is
Mark> released (this week?).

How do I know "Feisty stable" is released? Will I get it
automatically via the ubuntu software update system?
--
Associate Prof. Ph.D Torben Knudsen Phone : (+45) 9635 8670
Section of Automation and Control, Email : <email address hidden>
Department of Electronic Systems,
Aalborg University
Fredrik Bajersvej 7
DK-9220 Aalborg Ø
Denmark

It's been released. If you are running Edgy (6.10) then it should show
up in update manager.

On 4/25/07, Torben Knudsen <email address hidden> wrote:
>
> How do I know "Feisty stable" is released? Will I get it
> automatically via the ubuntu software update system?

--
Mark Reitblatt

The 18 month support period for Edgy Eft 6.10 has reached its end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!