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

Bug#393882: marked as done (linux-image-2.6.18-1-vserver-powerpc: system freezes eratically with no reason [powerpc, vserver])



Your message dated Sat, 28 Oct 2006 20:14:05 +0200
with message-id <20061028181330.GA15661@powerlinux.fr>
and subject line Bug#393882: linux-image-2.6.18-1-vserver-powerpc: system freezes eratically with no reason [powerpc, vserver]
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-1-vserver-powerpc
Version: 2.6.18-2
Severity: critical
Justification: breaks the whole system


I have upgraded my box with a 2.6.18-1-vserver-powerpc kernel, and its the
third time my box completely freeze after some time (between 10 minutes and 1
hour): no more keyboard, no more mouse, no more network activity. The system
just hang forever. No specific messages in any logs (I checked syslog,
messages and kern.log).

I was just writing mail (emacs+mutt+postfix), nothing special.

I do not remember getting such a behavior with any computer running Linux
since my early days using the SLS distribution.

I run Debian sid on a Mac Powerbook Aluminium (PowerBook5,4) and am connected
to my LAN through the airport (bcm53xx) card. I wonder if it may come from the
bcm53xx driver (see bugs #392065).

I switched back to a 2.6.17-2-vserver-powerpc kernel in order to try if it
comes from the kernel, since then everything seems right (no freeze yet).

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-vserver-powerpc
Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15)

Versions of packages linux-image-2.6.18-1-vserver-powerpc depends on:
ii  initramfs-tools [linux-initra 0.60       tools for generating an initramfs
ii  mkvmlinuz                     24         create a kernel to boot a PowerPC 
ii  module-init-tools             3.2.2-3    tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.12-15  Yet Another mkInitRD

Versions of packages linux-image-2.6.18-1-vserver-powerpc recommends:
ii  util-vserver                 0.30.210-10 user-space tools for Linux-Vserver

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


--- End Message ---
--- Begin Message ---
On Sat, Oct 28, 2006 at 04:01:42PM +0200, Bruno Beaufils wrote:
> On Thu, Oct 19, 2006 at 08:54:45AM +0200, Bruno Beaufils wrote:
> > > which is fixed in the 2.6.18.1 upstream release, and available in the upcoming
> > > 2.6.18-3 upload. Changelog entry says :
> > > 
> > >      - bcm43xx: fix regressions in 2.6.18 (Closes: #392065)
> > > 
> > > If so, it is important you try the daily snapshot builds Bastian mentioned.
> > 
> > OK I will try this next upload.
> 
> I tried it since some days without problems :
> 
> $ dpkg --list |grep linux-image-2.6.18-1-powerpc
> ii  linux-image-2.6.18-1-powerpc             2.6.18-3                    Linux 2.6.18 image on uniprocessor 32-bit PowerPC
> 
> No more complete freeze. Maybe someone could close the bug.

Yep.

> I get another new problems but am not sure it is related, so I will look to
> into the bugs system to see if other people get the same one.
> 
> Shortly said, when on battery the screen blank completely after a short period
> of time without any possibility to wake up. The box is not freezed (I can ping
> it or ssh to it) but am not able to see anything on the screen. The only
> solution I found to get my screen back is to suspend-to-ram and wake up the
> box.

I got this also sometime on my powerbook (3,5 one), and it is just the
blacklight which goes off, but otherwise the box seems ok. This may be an
hardware issue, since the hinges of my tibook broke.

Friendly,

Sven Luther

--- End Message ---

Reply to: