Ubuntu
linux package

[Apple Computer, Inc. MacBookPro1,1] suspend/resume failure [non-free: ath_hal]

Bug #356104 reported by FrejSoya
10
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

resume from suspend fails. (stil black screen).

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: i386
CurrentDmesg:
 [ 51.415153] sky2 eth0: enabling interface
 [ 51.415371] ADDRCONF(NETDEV_UP): eth0: link is not ready
 [ 53.672060] virbr0: no IPv6 routers present
 [ 62.060046] ath0: no IPv6 routers present
 [ 1235.725340] tracker-extract[8956]: segfault at 14 ip b7f52946 sp bfa8e960 error 4 in libtracker-common.so.0.0.0[b7f46000+29000]
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InterpreterPath: /usr/bin/python2.6
MachineType: Apple Computer, Inc. MacBookPro1,1
NonfreeKernelModules: ath_hal
Package: linux-image-2.6.28-11-generic 2.6.28-11.40
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=fbacb821-ab48-472d-8392-ff3d31512703 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-11.40-generic
SourcePackage: linux
Tags: resume suspend
Title: [Apple Computer, Inc. MacBookPro1,1] suspend/resume failure [non-free: ath_hal]
UserGroups:

Revision history for this message
FrejSoya (frej) wrote :
Revision history for this message
Ian Weisser (ian-weisser) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the following additional information, if you have not already done so (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" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo 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 https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

affects: ubuntu → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
kernel-janitor (kernel-janitor) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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