Bug#427826: marked as done (linux-image-2.6.18-4-sparc64: machine (several tested) hangs after a while)
Your message dated Wed, 13 Jun 2007 16:18:46 -0600
with message-id <[🔎] 20070613221846.GB20090@colo.lackof.org>
and subject line Bug#427826: probably due to a filesystem bug
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.18-4-sparc64
Version: 2.6.18.dfsg.1-12
Severity: critical
Justification: breaks the whole system
I have installed Debian Unstable on a SunBlade100 and the box keeps hanging. Sometimes it is after several hours and other just after a few minutes.
I have tried kernels 2.6.21-1-sparc64, 2.6.21-1-sparc64-smp and 2.6.18-4-sparc64.
I have also tried deactivating the framebuffer booting with video=atyfb:off but the behaviour of the system didn't change.
I have moved the HD to another similar machine and it also hanged.
I don't know if there is any magical key combination I can use to get some postmortem information about the system.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: sparc (sparc64)
Kernel: Linux 2.6.18-4-sparc64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.18-4-sparc64 depends on:
ii coreutils 5.97-5.3 The GNU core utilities
ii debconf [debconf-2.0] 1.5.13 Debian configuration management sy
ii initramfs-tools [linux-initr 0.88 tools for generating an initramfs
ii module-init-tools 3.3-pre11-1 tools for managing Linux kernel mo
linux-image-2.6.18-4-sparc64 recommends no packages.
-- debconf information:
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.18-4-sparc64/preinst/abort-install-2.6.18-4-sparc64:
linux-image-2.6.18-4-sparc64/postinst/old-dir-initrd-link-2.6.18-4-sparc64: true
linux-image-2.6.18-4-sparc64/preinst/overwriting-modules-2.6.18-4-sparc64: true
linux-image-2.6.18-4-sparc64/postinst/old-system-map-link-2.6.18-4-sparc64: true
linux-image-2.6.18-4-sparc64/postinst/depmod-error-initrd-2.6.18-4-sparc64: false
linux-image-2.6.18-4-sparc64/prerm/would-invalidate-boot-loader-2.6.18-4-sparc64: true
linux-image-2.6.18-4-sparc64/preinst/failed-to-move-modules-2.6.18-4-sparc64:
linux-image-2.6.18-4-sparc64/preinst/lilo-has-ramdisk:
linux-image-2.6.18-4-sparc64/preinst/bootloader-initrd-2.6.18-4-sparc64: true
linux-image-2.6.18-4-sparc64/postinst/bootloader-error-2.6.18-4-sparc64:
linux-image-2.6.18-4-sparc64/postinst/create-kimage-link-2.6.18-4-sparc64: true
linux-image-2.6.18-4-sparc64/preinst/abort-overwrite-2.6.18-4-sparc64:
linux-image-2.6.18-4-sparc64/postinst/depmod-error-2.6.18-4-sparc64: false
linux-image-2.6.18-4-sparc64/preinst/elilo-initrd-2.6.18-4-sparc64: true
linux-image-2.6.18-4-sparc64/preinst/lilo-initrd-2.6.18-4-sparc64: true
linux-image-2.6.18-4-sparc64/preinst/initrd-2.6.18-4-sparc64:
linux-image-2.6.18-4-sparc64/postinst/kimage-is-a-directory:
linux-image-2.6.18-4-sparc64/prerm/removing-running-kernel-2.6.18-4-sparc64: true
linux-image-2.6.18-4-sparc64/preinst/already-running-this-2.6.18-4-sparc64:
linux-image-2.6.18-4-sparc64/postinst/bootloader-test-error-2.6.18-4-sparc64:
linux-image-2.6.18-4-sparc64/postinst/old-initrd-link-2.6.18-4-sparc64: true
--- End Message ---
--- Begin Message ---
On Wed, Jun 13, 2007 at 03:58:19AM -0700, Salvador Fandi????o wrote:
> Hi,
>
> The machine is stable since I run fsck on all the file systems some
> days ago, it has not hanged again. Probably, the problem was related
> to some bug on the file system code. There is no way to reproduce it
> and so I suppose the ticket can be closed.
>
ok, closing then. thanks for the update.
--
dann frazier
--- End Message ---
Reply to: