Hal Update 0.5.9 Causes Suspend Issue

Bug #126019 reported by Sel on 2007-07-14
4
Affects Status Importance Assigned to Milestone
hal (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: hal

Steps to reproduce:

Using hal 0.5.9-1ubuntu2~feisty1

1. Suspend the computer and resume
2. Attempt to suspend the computer again
(the computer will fail to suspend)
3. Regress system back to previous hal (0.5.8.1-4ubuntu12).
4. Repeat steps 1,2
(the computer will now suspend and resume correctly)

Sel (seliqui) wrote :

I have also found that after attempting the second suspend (which fails) if I then log out, the computer will at that point fall into a suspended state, resuming will get you to the gdm.

Could you please test this with the latest version of Ubuntu, either 7.10 (Gutsy) or 8.04 (Hardy, development version)?

Thanks!

Changed in hal:
status: New → Incomplete

Hi Greg,

I have tested my 7.10 system 'as is'* and the following occurs:

1. Suspend - suspend completes and system powers down (fans stop,
screen suspends etc)
2. Resume - system resumes, it appears it may get a live kernel up but
no screen and no terminals (Ctrl+F1 etc)

My system has had the following two main changes since I filed that report:
1. Normal apt upgrade from feisty to gutsy.
2. Nvidia driver changed to version 169.04

I'm happy to send you any logs or configuration files you might want
to look at, and test any changes you might want to try.

Best regards,

David

On 04/03/2008, Greg Grossmeier <email address hidden> wrote:
> Could you please test this with the latest version of Ubuntu, either
> 7.10 (Gutsy) or 8.04 (Hardy, development version)?
>
> Thanks!
>
> ** Changed in: hal (Ubuntu)
> Status: New => Incomplete
>
>
> --
> Hal Update 0.5.9 Causes Suspend Issue
> https://bugs.launchpad.net/bugs/126019
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Thanks for the information.

Could you please provide some more?
 * Output of uname -a
 * Output of sudo lspci -vvnn
 * Output of sudo dmidecode
 * Try to suspend (using the non-working version of hal) and then restart the system and attach /var/log/kern.log.0
 * Tarball of /proc/acpi directory. You can't just tar all files because their content sometimes changes etc.
    * cp -r /proc/acpi /tmp
    * tar -cvjf ~/acpi.tar.bz /tmp/acpi

Also, it would be a great help if you could test the suspend using the latest LiveCD from the development version, Hardy. You can get it from here: http://cdimages.ubuntu.com/releases/8.04/alpha-6/

When running the LiveCD, attempt to suspend (hibernate won't work) and if it comes back from suspend, attach /var/log/kern.log and /var/log/kern.log.0

Thanks!

Changed in hal:
importance: Undecided → Medium
Sel (seliqui) wrote :
Download full text (33.3 KiB)

$ uname -a
Linux jade 2.6.22-14-generic #1 SMP Tue Feb 12 02:46:46 UTC 2008
x86_64 GNU/Linux

All other outputs attached

Kernel log to follow after suspend restart.

David

On 11/03/2008, Greg Grossmeier <email address hidden> wrote:
> Thanks for the information.
>
> Could you please provide some more?
> * Output of uname -a
> * Output of sudo lspci -vvnn
> * Output of sudo dmidecode
> * Try to suspend (using the non-working version of hal) and then restart the system and attach /var/log/kern.log.0
> * Tarball of /proc/acpi directory. You can't just tar all files because their content sometimes changes etc.
> * cp -r /proc/acpi /tmp
> * tar -cvjf ~/acpi.tar.bz /tmp/acpi
>
> Also, it would be a great help if you could test the suspend using the
> latest LiveCD from the development version, Hardy. You can get it from
> here: http://cdimages.ubuntu.com/releases/8.04/alpha-6/
>
> When running the LiveCD, attempt to suspend (hibernate won't work) and
> if it comes back from suspend, attach /var/log/kern.log and
> /var/log/kern.log.0
>
>
> Thanks!
>
> ** Changed in: hal (Ubuntu)
>
> Importance: Undecided => Medium
>
>
> --
> Hal Update 0.5.9 Causes Suspend Issue
> https://bugs.launchpad.net/bugs/126019
> You received this bug notification because you are a direct subscriber
> of the bug.
>

00:00.0 RAM memory [0500]: nVidia Corporation MCP61 Memory Controller [10de:03ea] (rev a1)
 Subsystem: ABIT Computer Corp. Unknown device [147b:1c2a]
 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=17 MastHost- DefDir- DUL-
  Link Control 0: CFlE- CST- CFE- <LkFail- Init+ EOC- TXO- <CRCErr=0 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=8bit DwFcIn- MLWO=8bit DwFcOut- LWI=8bit DwFcInEn- LWO=8bit DwFcOutEn-
  Revision ID: 1.03
  Link Frequency 0: 1.0GHz
  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: 200MHz
  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: [dc] HyperTransport: MSI Mapping

00:01.0 ISA bridge [0601]: nVidia Corporation MCP61 LPC Bridge [10de:03e0] (rev a2)
 Subsystem: ABIT Computer Corp. Unknown device [147b:1c2a]
 Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <T...

Sel (seliqui) wrote :

I have attached the kern.log file rather than the kern.log.0 as I
think it's more likely to be relevant (will contain record of the
restart).

I will download a hardy image and get back to you with the results.

David

On 11/03/2008, Greg Grossmeier <email address hidden> wrote:
> Thanks for the information.
>
> Could you please provide some more?
> * Output of uname -a
> * Output of sudo lspci -vvnn
> * Output of sudo dmidecode
> * Try to suspend (using the non-working version of hal) and then restart the system and attach /var/log/kern.log.0
> * Tarball of /proc/acpi directory. You can't just tar all files because their content sometimes changes etc.
> * cp -r /proc/acpi /tmp
> * tar -cvjf ~/acpi.tar.bz /tmp/acpi
>
> Also, it would be a great help if you could test the suspend using the
> latest LiveCD from the development version, Hardy. You can get it from
> here: http://cdimages.ubuntu.com/releases/8.04/alpha-6/
>
> When running the LiveCD, attempt to suspend (hibernate won't work) and
> if it comes back from suspend, attach /var/log/kern.log and
> /var/log/kern.log.0
>
>
> Thanks!
>
> ** Changed in: hal (Ubuntu)
>
> Importance: Undecided => Medium
>
>
> --
> Hal Update 0.5.9 Causes Suspend Issue
> https://bugs.launchpad.net/bugs/126019
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Changed in hal:
status: Incomplete → Confirmed
dino99 (9d9) wrote :
Changed in hal (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers