System hangs on Hardy

Bug #178685 reported by Kamba
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

System hangs sometimes.
I've upgraded from 2.6.20-15-generic (its feisty, because gutsy .22 kernel hadn't boot on my laptop). Hardy boots without problem, but in the beginning of boot process i can see the sign "Apparmour cann't register" or something like that.

System works about 1 hour, sometimes a couple - and hangs. Ctrl+Alt+Backspace doesn't work. Keybord and mouse are dead.

Tags: cft-2.6.27
Revision history for this message
Kamba (blamer) wrote :

syslog

Revision history for this message
Kamba (blamer) wrote :

hArdy, ofcourse. Moderators, please, retype the header of the post.

Revision history for this message
Kamba (blamer) wrote :

dmesg

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Can you recall if you are doing anything specifically when the system hangs? Per the kernel team's bug policy, can you also please attach the following information. Please be sure to attach each file as a separate attachment.

* uname -a > uname-a.log
* cat /proc/version_signature > version.log
* sudo lspci -vvnn > lspci-vvnn.log

For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies .

Also, just for future reference you can edit the title and summary of your own bug reports by clicking on the "Edit description/tags" link in the "Actions" area on the left had side of the bug report. Thanks.

Thanks again and we appreciate your help and feedback.

Changed in linux:
status: New → Incomplete
Revision history for this message
Kamba (blamer) wrote :
Download full text (22.3 KiB)

"uname -a" returnes Linux ******* 2.6.24-2-generic #1 SMP Thu Dec 20 17:36:12 GMT 2007 i686 GNU/Linux
version_signature - Ubuntu 2.6.24-2.4-generic

And lspci:

00:00.0 RAM memory [0500]: nVidia Corporation C51 Host Bridge [10de:02f3] (rev a2)
        Subsystem: ASUSTeK Computer Inc. Unknown device [1043:14b7]
        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: [44] HyperTransport: Slave or Primary Interface
                Command: BaseUnitID=0 UnitCnt=15 MastHost- DefDir- DUL-
                Link Control 0: CFlE+ CST- CFE- <LkFail- Init+ EOC- TXO- <CRCErr=3 IsocEn- LSEn+ ExtCTL- 64b-
                Link Config 0: MLWI=16bit DwFcIn- MLWO=16bit DwFcOut- LWI=16bit DwFcInEn- LWO=16bit DwFcOutEn-
                Link Control 1: CFlE+ CST- CFE- <LkFail- Init+ EOC- TXO- <CRCErr=0 IsocEn- LSEn+ ExtCTL- 64b-
                Link Config 1: MLWI=16bit DwFcIn- MLWO=16bit DwFcOut- LWI=8bit DwFcInEn- LWO=8bit DwFcOutEn-
                Revision ID: 1.03
                Link Frequency 0: 800MHz
                Link Error 0: <Prot- <Ovfl- <EOC- CTLTm-
                Link Frequency Capability 0: 200MHz+ 300MHz+ 400MHz+ 500MHz+ 600MHz+ 800MHz+ 1.0GHz+ 1.2GHz- 1.4GHz- 1.6GHz- Vend-
                Feature Capability: IsocFC+ LDTSTOP+ CRCTM- ECTLT- 64bA- UIDRD-
                Link Frequency 1: 800MHz
                Link Error 1: <Prot- <Ovfl- <EOC- CTLTm-
                Link Frequency Capability 1: 200MHz+ 300MHz+ 400MHz+ 500MHz+ 600MHz+ 800MHz+ 1.0GHz+ 1.2GHz- 1.4GHz- 1.6GHz- Vend-
                Error Handling: PFlE+ OFlE+ PFE- OFE- EOCFE- RFE- CRCFE- SERRFE- CF- RE- PNFE- ONFE- EOCNFE- RNFE- CRCNFE- SERRNFE-
                Prefetchable memory behind bridge Upper: 00-00
                Bus Number: 00
        Capabilities: [e0] HyperTransport: MSI Mapping

00:00.2 RAM memory [0500]: nVidia Corporation C51 Memory Controller 1 [10de:02fe] (rev a2)
        Subsystem: ASUSTeK Computer Inc. Unknown device [1043:14b7]
        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-

00:00.3 RAM memory [0500]: nVidia Corporation C51 Memory Controller 5 [10de:02f8] (rev a2)
        Subsystem: ASUSTeK Computer Inc. Unknown device [1043:14b7]
        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-

00:00.4 RAM memory [0500]: nVidia Corporation C51 Memory Controller 4 [10de:02f9] (rev a2)
        Subsystem: ASUSTeK Computer Inc. Unknown device [1043:14b7]
        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

00:00.5 RAM memory [0500]: nVidia Corporation C51 Host Bridge [10de:02ff] (rev a2)
        Subsystem: ASUSTeK Compute...

Revision history for this message
Kamba (blamer) wrote :

Sorry, i don't know, where these files are.

I cann't say that i do something special when system hangs. Sometimes it hangs when i download upgrades (or simply using internet), sometimes - when i watch video or just even read Open Office document. I have 2.6.20-15-generic kernel installed on my laptop - and it works perfect, so i'm sure that it is not a hardware problem, it hangs ONLY under 2.6.24-2-generic kernel.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Thanks Kamba. After you notice the system hangs and you have to reboot, can you then attach your /var/log/kern.log.0 file? Thanks.

Revision history for this message
Kamba (blamer) wrote :

patch this bug, i think it is critical, when system just hangs randomly.

Revision history for this message
Kamba (blamer) wrote :

Why the status of this bug is Incomplete? Is there more information needed?

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Care to retest with the latest 2.6.24-5.9 kernel and verify this issue still exists? Thanks.

Revision history for this message
Kamba (blamer) wrote :

In 2.6.24-5 kernel its still exists. I checked it.

Changed in linux:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Medium
status: Incomplete → Triaged
Revision history for this message
Kamba (blamer) wrote :

In 2.6.24-8 still exists.

If you need some logs or files - just ask. I want it fixed!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

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.

Revision history for this message
Jim Lieb (lieb) wrote :

Please upgrade to a current (Jaunty/9.04) Ubuntu release. If the problem persists, please open a new bug with logs and traces from the newer release for us to diagnose the problem. This bug on the older kernel is closed.

Changed in linux (Ubuntu):
status: Triaged → Won't Fix
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.