[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#383725: marked as done (linux-image-2.6.16-2-686: cannot halt properly Thinkpad T22)

Your message dated Sat, 19 Aug 2006 14:39:02 +0200
with message-id <20060819123902.GA4868@baikonur.stro.at>
and subject line Bug#383725: linux-image-2.6.16-2-686: 2.6.17 works
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: linux-image-2.6.16-2-686
Version: 2.6.16-17
Severity: normal

Hello,

I see a clear regression here after upgrading from 2.6.15 to 2.6.16. The
kernel now doesn't shutdown cleanly the power on my laptop, a IBM
Thinkpad T22. It used to work real nice on 2.6.15, but now, the machine
just sits there after the "Shutting down drives: sda" (probably not the
exact wording, i don't clearly remember, but it's usually the last thing
on the console before the shutdown). I can safely poweroff the machine
by pressing the power key for 5 seconds, but it's a bit annoying.

Usually, i just "suspend to disk" this machine, using an ugly hack (echo
disk > /sys/power/state). This is also affect in that I need to poweroff
the same way as a shutdown, ie. by pressing the power key. The machine
resumes as normal.

Available for debugging/testing with right tools/instructions...

a.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-686
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6.16-2-686 depends on:
ii  initramfs-tools [linux-initra 0.73c      tools for generating an initramfs
ii  module-init-tools             3.2.2-3    tools for managing Linux kernel mo

Versions of packages linux-image-2.6.16-2-686 recommends:
ii  libc6-i686                    2.3.6-15   GNU C Library: Shared libraries [i

-- debconf information:
  linux-image-2.6.16-2-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.16-2-686/preinst/bootloader-initrd-2.6.16-2-686: true
  linux-image-2.6.16-2-686/postinst/old-system-map-link-2.6.16-2-686: true
  linux-image-2.6.16-2-686/preinst/failed-to-move-modules-2.6.16-2-686:
  linux-image-2.6.16-2-686/preinst/overwriting-modules-2.6.16-2-686: true
  linux-image-2.6.16-2-686/postinst/old-dir-initrd-link-2.6.16-2-686: true
  linux-image-2.6.16-2-686/postinst/depmod-error-initrd-2.6.16-2-686: false
  linux-image-2.6.16-2-686/postinst/create-kimage-link-2.6.16-2-686: true
  linux-image-2.6.16-2-686/postinst/bootloader-test-error-2.6.16-2-686:
  linux-image-2.6.16-2-686/prerm/removing-running-kernel-2.6.16-2-686: true
  linux-image-2.6.16-2-686/postinst/depmod-error-2.6.16-2-686: false
  linux-image-2.6.16-2-686/preinst/abort-install-2.6.16-2-686:
  linux-image-2.6.16-2-686/postinst/bootloader-error-2.6.16-2-686:
  linux-image-2.6.16-2-686/postinst/kimage-is-a-directory:
  linux-image-2.6.16-2-686/preinst/abort-overwrite-2.6.16-2-686:
  linux-image-2.6.16-2-686/prerm/would-invalidate-boot-loader-2.6.16-2-686: true
  linux-image-2.6.16-2-686/preinst/already-running-this-2.6.16-2-686:
  linux-image-2.6.16-2-686/preinst/elilo-initrd-2.6.16-2-686: true
  linux-image-2.6.16-2-686/preinst/initrd-2.6.16-2-686:
  linux-image-2.6.16-2-686/postinst/old-initrd-link-2.6.16-2-686: true
  linux-image-2.6.16-2-686/preinst/lilo-initrd-2.6.16-2-686: true

--- End Message ---
--- Begin Message --- 
On Sat, Aug 19, 2006 at 01:54:59PM +0200, The Anarcat wrote:
> Package: linux-image-2.6.16-2-686
> Version: 2.6.16-17
> Followup-For: Bug #383725
> 
> I confirm that 2.6.17 is not affected by this bug.
> 

thanks for verification,
thus closing bug report.

--
maks

--- End Message ---
Reply to: