Bug#457631: linux-image-2.6.18-5-powerpc: system freezes (occurred twice)

[Moritz Muehlenhoff <jmm@inutil.org>]

On Sat, Apr 05, 2008 at 02:05:03AM +0200, Vincent Lefevre wrote:
> reassign 457631 linux-image-2.6.18-6-powerpc
> found 457631 2.6.18.dfsg.1-18etch1
> thanks
> 
> I've got 3 crashes with linux-image-2.6.18-6-powerpc in a few days
> (I've been on holidays since April 1, using my PowerBook physically,
> that's why the crashes reappeared).
> 
> ay:~> last -axf /var/log/wtmp | egrep 'crash|boot'
> reboot   system boot  Sat Apr  5 01:19 - 01:56  (00:37)     2.6.24-1-powerpc
> reboot   system boot  Sat Apr  5 00:27 - 01:16  (00:49)     2.6.18-6-powerpc
> lefevre  tty1         Sat Apr  5 00:15 - crash  (00:12)     
> reboot   system boot  Sat Apr  5 00:13 - 01:16  (01:03)     2.6.18-6-powerpc
> lefevre  tty1         Thu Apr  3 17:53 - crash (1+06:20)    
> reboot   system boot  Thu Apr  3 17:51 - 01:16 (1+07:25)    2.6.18-6-powerpc
> lefevre  tty1         Wed Apr  2 22:37 - crash  (19:14)     
> reboot   system boot  Wed Apr  2 22:35 - 01:16 (2+02:41)    2.6.18-6-powerpc
> 
> I've just installed 2.6.24-1-powerpc. Let's see if it has the same
> problem...
> 
> On 2008-01-16 17:27:55 +0100, Vincent Lefevre wrote:
> > Since January 1, I haven't got any crash. In fact, the crashes occurred
> > only when I was on holidays. The two differences from normal use:
> > 
> >   * The network was different: I was using DHCP (with "pump"), while
> >     I normally use a static network configuration.
> 
> FYI, the current pump version was 0.8.24-2.1 with the last 3 crashes.
> 
> >   * I was using X11 much more often (I normally use this machine
> >     remotely). I also spent a few days abroad last week, where
> >     I had no connection by Ethernet (only USB) and where I was
> >     using X11 quite often, and I didn't get any crash.
> 
> Also, it seems that the crashes occur only when I use the keyboard.
> The application doesn't matter (I got crashes when typing in an Emacs
> window and in an xterm). My PowerBook is on all the time (I have some
> servers on it), and when I don't use it physically, it never crashes.

Does this error still occur with more recent kernel versions?

If you're running Etch, could you try to reproduce this bug
with the 2.6.24 based kernel added in 4.0r4?
http://packages.qa.debian.org/l/linux-2.6.24.html

Cheers,
        Moritz