reassign 429662 linux-image-2.6.21-2-powerpc
found 429662 2.6.21-5
thanks

On Tue, Jun 19, 2007 at 12:21:05PM +0000, Debian Bug Tracking System wrote:

> If you wish to submit further information on your problem, please send
> it to [EMAIL PROTECTED] (and *not* to
> [EMAIL PROTECTED]).

Suspending via closing the laptop lid appears to have been "fixed" by
2.6.21-2-powerpc but if I try to initiate a suspend from the GNOME power
manager GUI then that still fails (although it does not hang the
system).  Looking at the system log I'm not convinced that even the
hardware initiated suspend did as it should: the log below shows a
suspend initiated by closing the laptop lid which appears to have been
aborted by software part way through suspending although as the gap in
the timestamps indicates the system did in fact suspend.  When the
system was resumed there were no visible problems other than the issue
with the timesamp.

Jul  4 18:31:11 localhost gnome-power-manager: (broonie) Suspending computer bec
ause the lid has been closed on battery power
Jul  4 18:31:13 localhost kernel: eth1: suspending, WakeOnLan disabled
Jul  4 18:31:13 localhost kernel: bcm43xx: Suspending...
Jul  4 18:31:13 localhost kernel: bcm43xx: Radio turned off
Jul  4 18:31:13 localhost kernel: bcm43xx: DMA-32 0x0200 (RX) max used slots: 4/
64
Jul  4 18:31:13 localhost kernel: bcm43xx: DMA-32 0x02A0 (TX) max used slots: 
0/512
Jul  4 18:31:13 localhost kernel: bcm43xx: DMA-32 0x0280 (TX) max used slots: 
0/512
Jul  4 18:31:13 localhost kernel: bcm43xx: DMA-32 0x0260 (TX) max used slots: 
0/512
Jul  4 18:31:13 localhost kernel: bcm43xx: DMA-32 0x0240 (TX) max used slots: 
0/512
Jul  4 18:31:13 localhost kernel: bcm43xx: DMA-32 0x0220 (TX) max used slots: 
3/512
Jul  4 18:31:13 localhost kernel: bcm43xx: DMA-32 0x0200 (TX) max used slots: 
0/512
Jul  4 18:31:13 localhost kernel: bcm43xx: Device suspended.
Jul  4 18:31:13 localhost kernel: uninorth-agp: disabling AGP on device 
0000:00:10.0
Jul  4 18:31:13 localhost kernel: uninorth-agp: disabling AGP on bridge 
0000:00:0b.0
Jul  4 18:31:15 localhost kernel: agpgart: Putting AGP V2 device at 
0000:00:0b.0 into 1x mode
Jul  4 18:31:15 localhost kernel: agpgart: Putting AGP V2 device at 
0000:00:10.0 into 1x mode
Jul  4 18:31:15 localhost kernel: bcm43xx: Resuming...
Jul  4 18:31:15 localhost kernel: PCI: Enabling device 0001:10:12.0 (0000 -> 
0002)
Jul  4 18:31:15 localhost kernel: bcm43xx: PHY connected
Jul  4 18:31:15 localhost kernel: bcm43xx: Microcode rev 0x127, pl 0xe 
(2005-04-18  02:36:27)
Jul  4 18:31:15 localhost kernel: bcm43xx: Radio turned on
Jul  4 18:31:15 localhost kernel: bcm43xx: Radio enabled by hardware
Jul  4 18:31:15 localhost kernel: bcm43xx: Chip initialized
Jul  4 18:31:15 localhost kernel: bcm43xx: 30-bit DMA initialized
Jul  4 18:31:15 localhost kernel: bcm43xx: Keys cleared
Jul  4 18:31:15 localhost kernel: bcm43xx: Selected 802.11 core (phytype 2)
Jul  4 18:31:15 localhost kernel: bcm43xx: Device resumed.
Jul  4 18:31:15 localhost kernel: PCI: Enabling device 0001:10:1b.0 (0000 -> 
0002)
Jul  4 18:31:15 localhost kernel: PCI: Enabling device 0001:10:1b.1 (0000 -> 
0002)
Jul  4 18:31:15 localhost kernel: PCI: Enabling device 0001:10:1b.2 (0000 -> 
0002)
Jul  4 18:31:16 localhost kernel: ohci1394: fw-host0: OHCI-1394 1.1 (PCI): 
IRQ=[40]  MMIO=[f5000000-f50007ff]  Max Packet=[4096]  IR/IT contexts=[8/8]
Jul  4 18:31:16 localhost kernel: eth1: resuming
Jul  4 18:31:17 localhost kernel: hda: Enabling Ultra DMA 5
Jul  4 22:17:54 localhost kernel: hdc: Enabling MultiWord DMA 2
Jul  4 22:17:54 localhost kernel: adb: starting probe task...
Jul  4 22:17:54 localhost kernel: agpgart: Putting AGP V2 device at 
0000:00:0b.0 into 1x mode
Jul  4 22:17:54 localhost kernel: agpgart: Putting AGP V2 device at 
0000:00:10.0 into 1x mode
Jul  4 22:17:54 localhost kernel: [drm] Loading R300 Microcode
Jul  4 22:17:54 localhost kernel: ADB keyboard at 2, handler 1

-- 
"You grabbed my hand and we fell into it, like a daydream - or a fever."

Attachment: signature.asc
Description: Digital signature

Reply via email to