[Hewlett-Packard HP Pavilion dv6700 Notebook PC] suspend/resume failure [non-free: ath_hal nvidia]

[Don Forigua]

ubuntu doesn't start with the battery

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: amd64
CurrentDmesg:
 [ 54.215648] forcedeth 0000:00:0a.0: irq 2300 for MSI/MSI-X
 [ 54.215873] eth0: no link during initialization.
 [ 54.217101] ADDRCONF(NETDEV_UP): eth0: link is not ready
 [ 64.792042] ath0: no IPv6 routers present
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InterpreterPath: /usr/bin/python2.6
Lsusb:
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 002: ID 0458:003a KYE Systems Corp. (Mouse Systems)
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP Pavilion dv6700 Notebook PC
NonfreeKernelModules: ath_hal nvidia
Package: linux-image-2.6.28-9-generic 2.6.28-9.29
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=d8ee8168-63ba-42eb-b3a1-61e0fb79c769 ro xforcevesa quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-9.29-generic
SourcePackage: linux
StressLog: Error: [Errno 2] No such file or directory: '/var/lib/pm-utils/stress.log'
Tags: resume suspend
Title: [Hewlett-Packard HP Pavilion dv6700 Notebook PC] suspend/resume failure [non-free: ath_hal nvidia]
UserGroups:

[Leann Ogasawara (leannogasawara)]

Hi Ing. Forigua,

Can you clarify the bug description a little more. You mention "ubuntu doesn't start with the battery". The bug filed here was for a suspend/resume failure. So is it that the machine doesn't resume from suspend while using the battery? Does it resume fine if plugged in? Could you also take a look at https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume, specifically the Information Gathering section. Please provide any answers to the additional questions outlined there. Thanks.

[Don Forigua (ingforigua)]

At /boot/grub/menu.lst i use the kernel parameters:

title Ubuntu jaunty (development branch), kernel 2.6.28-11-generic
(on /dev/sda5)
root (hd0,4)
kernel /boot/vmlinuz-2.6.28-11-generic
root=UUID=d8ee8168-63ba-42eb-b3a1-61e0fb79c769 ro xforcevesa quiet splash
nohz=off highres=off
initrd /boot/initrd.img-2.6.28-11-generic
savedefault
boot

and my system runs ok, this bug apear afer i install madwifi source.

thanks

2009/3/26 Leann Ogasawara <email address hidden>

> Hi Ing. Forigua,
>
> Can you clarify the bug description a little more. You mention "ubuntu
> doesn't start with the battery". The bug filed here was for a
> suspend/resume failure. So is it that the machine doesn't resume from
> suspend while using the battery? Does it resume fine if plugged in?
> Could you also take a look at
> https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume,
> specifically the Information Gathering section. Please provide any
> answers to the additional questions outlined there. Thanks.
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
> --
> [Hewlett-Packard HP Pavilion dv6700 Notebook PC] suspend/resume failure
> [non-free: ath_hal nvidia]
> https://bugs.launchpad.net/bugs/341257
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
**********************************************************************
**********************************************************************
                            最もよいエンジニア
                  コロンビアの地下のチーム (CUT)
                          コロンビアの国民大学
                                    ボゴタ
                                 コロンビア
**********************************************************************
**********************************************************************
...Gratis lo recibisteis; dadlo gratis. (Mt 10, 8)
Visita mi blog http://ingeniero-forigua.blogspot.com/

[Don Forigua (ingforigua)]

At /boot/grub/menu.lst i use the kernel parameters:

title Ubuntu jaunty (development branch), kernel 2.6.28-11-generic (on /dev/sda5)
root (hd0,4)
kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=d8ee8168-63ba-42eb-b3a1-61e0fb79c769 ro xforcevesa quiet splash nohz=off highres=off
initrd /boot/initrd.img-2.6.28-11-generic
savedefault
boot

and my system runs ok, this bug apear afer i install madwifi source.

thanks

[don'tcare (jice)]

for the "human" user this method of bug reporting really sucks! there are people who actually use their computers to do things.

Anyway the laptop doesn't resume from suspend at all and then the next boot hangs too until I reset everything by yanking the battery. I have no idea where the report is now after all the registering & the logging in to launchbad.

Oh that's right I should be a programming geek to use linux and report problems-my boss made us use it but that experiment has failed thankfully.
bye

[Jerome Bonoan (jbonoan)]

In my case, the laptop will seem to wake up, but the video will not
turn back on (breaks while waking), no matter what I input into the
keyboard. My computer has the same video error no matter whether I am
on battery or plugged in. It's reproducible; happens every time I
sleep.

I haven't changed any kernel parameters as I can boot from the default
settings in 9.04.

On Thu, Mar 26, 2009 at 4:07 PM, Leann Ogasawara
<email address hidden> wrote:
> Hi Ing. Forigua,
>
> Can you clarify the bug description a little more.  You mention "ubuntu
> doesn't start with the battery".  The bug filed here was for a
> suspend/resume failure.  So is it that the machine doesn't resume from
> suspend while using the battery?  Does it resume fine if plugged in?
> Could you also take a look at
> https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume,
> specifically the Information Gathering section.  Please provide any
> answers to the additional questions outlined there.  Thanks.
>
> ** Changed in: linux (Ubuntu)
>       Status: New => Incomplete
>
> --
> [Hewlett-Packard HP Pavilion dv6700 Notebook PC] suspend/resume failure [non-free: ath_hal nvidia]
> https://bugs.launchpad.net/bugs/341257
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” source package in Ubuntu: Incomplete
>
> Bug description:
> ubuntu doesn't start with the battery
>
> ProblemType: KernelOops
> Annotation: This occured during a previous suspend and prevented it from resuming properly.
> Architecture: amd64
> CurrentDmesg:
>  [   54.215648] forcedeth 0000:00:0a.0: irq 2300 for MSI/MSI-X
>  [   54.215873] eth0: no link during initialization.
>  [   54.217101] ADDRCONF(NETDEV_UP): eth0: link is not ready
>  [   64.792042] ath0: no IPv6 routers present
> DistroRelease: Ubuntu 9.04
> ExecutablePath: /usr/share/apport/apportcheckresume
> Failure: suspend/resume
> InterpreterPath: /usr/bin/python2.6
> Lsusb:
>  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>  Bus 002 Device 002: ID 0458:003a KYE Systems Corp. (Mouse Systems)
>  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> MachineType: Hewlett-Packard HP Pavilion dv6700 Notebook PC
> NonfreeKernelModules: ath_hal nvidia
> Package: linux-image-2.6.28-9-generic 2.6.28-9.29
> ProcAttrCurrent: unconfined
> ProcCmdLine: root=UUID=d8ee8168-63ba-42eb-b3a1-61e0fb79c769 ro xforcevesa quiet splash
> ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
> ProcEnviron: PATH=(custom, no user)
> ProcVersionSignature: Ubuntu 2.6.28-9.29-generic
> SourcePackage: linux
> StressLog: Error: [Errno 2] No such file or directory: '/var/lib/pm-utils/stress.log'
> Tags: resume suspend
> Title: [Hewlett-Packard HP Pavilion dv6700 Notebook PC] suspend/resume failure [non-free: ath_hal nvidia]
> UserGroups:
>

[Leann Ogasawara (leannogasawara)]

@don'tcare and @Jerome Bonoan, even though you may be experiencing similar symptoms reported here it really is hardware specific. If you had hardware which differs from Inb. Forigua (the original bug reporter) it would be best to open a separate bug report.

For now I'm closing this bug as Ing. Forigua has commented this is now resolved. Thanks.