Bug#457631: marked as done (linux-image-2.6.18-5-powerpc: system freezes (occurred twice))
Your message dated Sun, 28 Dec 2008 01:55:30 +0100
with message-id <20081228005530.GB13301@galadriel.inutil.org>
and subject line Re: Bug#457631: linux-image-2.6.18-5-powerpc: system freezes (occurred twice)
has caused the Debian Bug report #457631,
regarding linux-image-2.6.18-5-powerpc: system freezes (occurred twice)
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
457631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=457631
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: linux-image-2.6.18-5-powerpc: system freezes (occurred twice)
- From: Vincent Lefevre <vincent@vinc17.org>
- Date: Mon, 24 Dec 2007 01:01:53 +0100
- Message-id: <20071224000152.GA4839@ay.vinc17.org>
Package: linux-image-2.6.18-5-powerpc
Version: 2.6.18.dfsg.1-13etch6
Severity: important
At about 00:25, the system completely froze: the mouse and the keyboard
were no longer working (even Ctrl-Alt-Del), and the network connection
was no longer working either. Not much in the log files before the
freeze:
/var/log/syslog
Dec 24 00:20:43 ay ctlinnd[24945]: Reading config from /etc/news/inn.conf
Dec 24 00:20:43 ay innd: s
Dec 24 00:25:01 ay /USR/SBIN/CRON[25100]: (root) CMD ([ -x /usr/lib/sysstat/sa1 ] && { [ -r "$DEFAULT" ] && . "$DEFAULT" ; [ "$ENABLED" = "true" ] && exec /usr/lib/sysstat/sa1 $SA1_OPTIONS 1 1 ; })
Dec 24 00:25:18 ay nnrpd[24938]: localhost group fr.misc.transport.rail 10
/var/log/messages
Dec 23 23:23:44 ay -- MARK --
Dec 23 23:43:45 ay -- MARK --
Dec 24 00:03:45 ay -- MARK --
Dec 24 00:23:46 ay -- MARK --
I was just using "tin" at that time. The only thing I could do was
to switched off the machine. A few minutes after rebooting it, I got
a second freeze (just after typing "reportbug ...").
I think I didn't have any such problem before (except when using the
smartmontools long self-test), in the last few years.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (900, 'testing'), (900, 'stable'), (200, 'unstable')
Architecture: powerpc (ppc)
Kernel: Linux 2.6.18-5-powerpc
Locale: LANG=POSIX, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.18-5-powerpc depends on:
ii coreutils 5.97-5.3 The GNU core utilities
ii debconf [debconf-2.0] 1.5.17 Debian configuration management sy
ii mkvmlinuz 33 create a kernel to boot a PowerPC
ii module-init-tools 3.3-pre11-4 tools for managing Linux kernel mo
ii yaird [linux-initramfs-tool] 0.0.12-24 Yet Another mkInitRD
linux-image-2.6.18-5-powerpc recommends no packages.
-- debconf information:
linux-image-2.6.18-5-powerpc/preinst/lilo-has-ramdisk:
linux-image-2.6.18-5-powerpc/postinst/old-initrd-link-2.6.18-5-powerpc: true
linux-image-2.6.18-5-powerpc/postinst/bootloader-error-2.6.18-5-powerpc:
linux-image-2.6.18-5-powerpc/preinst/abort-install-2.6.18-5-powerpc:
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.18-5-powerpc/prerm/removing-running-kernel-2.6.18-5-powerpc: true
linux-image-2.6.18-5-powerpc/preinst/overwriting-modules-2.6.18-5-powerpc: true
linux-image-2.6.18-5-powerpc/preinst/elilo-initrd-2.6.18-5-powerpc: true
linux-image-2.6.18-5-powerpc/preinst/initrd-2.6.18-5-powerpc:
linux-image-2.6.18-5-powerpc/postinst/kimage-is-a-directory:
linux-image-2.6.18-5-powerpc/postinst/old-system-map-link-2.6.18-5-powerpc: true
linux-image-2.6.18-5-powerpc/postinst/depmod-error-2.6.18-5-powerpc: false
linux-image-2.6.18-5-powerpc/prerm/would-invalidate-boot-loader-2.6.18-5-powerpc: true
* linux-image-2.6.18-5-powerpc/preinst/already-running-this-2.6.18-5-powerpc:
linux-image-2.6.18-5-powerpc/postinst/old-dir-initrd-link-2.6.18-5-powerpc: true
linux-image-2.6.18-5-powerpc/postinst/create-kimage-link-2.6.18-5-powerpc: true
linux-image-2.6.18-5-powerpc/postinst/bootloader-test-error-2.6.18-5-powerpc:
linux-image-2.6.18-5-powerpc/preinst/abort-overwrite-2.6.18-5-powerpc:
linux-image-2.6.18-5-powerpc/preinst/failed-to-move-modules-2.6.18-5-powerpc:
* linux-image-2.6.18-5-powerpc/preinst/bootloader-initrd-2.6.18-5-powerpc: false
linux-image-2.6.18-5-powerpc/postinst/depmod-error-initrd-2.6.18-5-powerpc: false
linux-image-2.6.18-5-powerpc/preinst/lilo-initrd-2.6.18-5-powerpc: true
--- End Message ---
--- Begin Message ---
Version: 2.6.26-1
On Sun, Dec 28, 2008 at 01:39:24AM +0100, Vincent Lefevre wrote:
> On 2008-12-27 22:40:07 +0100, Moritz Muehlenhoff wrote:
> > Does this error still occur with more recent kernel versions?
>
> No, and I've been using my laptop under the same conditions as
> last year since 5 days, without any problem. The current kernel
> is: linux-image-2.6.26-1-powerpc 2.6.26-12.
>
> According to my logs, 2.6.24-1-powerpc crashed twice on Apr 5 and 6.
> Then the crashes disappeared, but I wasn't using the keyboard any
> longer. I used my laptop under the same conditions from Jul 15 to
> Jul 26 with 2.6.25-2-powerpc; not a single crash. Between Apr 5 and
> Jul 26, I didn't change anything related to the kernel modules. So,
> I assume that there was really a bug that has been fixed between
> 2.6.24-2-powerpc and 2.6.25-2-powerpc (included).
Thanks, closing the bug in version 2.6.26-1 then.
Cheers,
Moritz
--- End Message ---
Reply to: