Re: Bug#327355: linux-image-2.6.12-1-k7: amverify w/ ide-tape causes bug, then kernel panic

[Horms]

Hi Anthony,

I am forwarding this to the IDE Tape maintainer for his consideration.

-- 
Horms

On Fri, Sep 09, 2005 at 08:43:54AM -0400, Anthony DeRobertis wrote:
> Package: linux-image-2.6.12-1-k7
> Version: 2.6.12-6
> Severity: important
> 
> amverify started, then shortly later (after the first thing was done
> verifying, I think) these managed to make it to syslog. As you can see,
> it got the bug message, then rebooted itself a few minutes later:
> 
> Sep  9 01:12:27 Maxwell kernel: ide-tape: bug: tape->next_stage != NULL
> Sep  9 01:16:14 Maxwell kernel: klogd 1.4.1#17, log source = /proc/kmsg started.
> Sep  9 01:16:14 Maxwell kernel: Inspecting /boot/System.map-2.6.12-1-k7
> 
> This is quite repeatable, and I never saw it on 2.6.8 (sarge). I'll test
> that particular tape on 2.6.8 just to be sure.
> 
> Shortly (as in a second at most) after that, it panics (with the "in the
> interrupt handler, not syncing" message), which doesn't make it to the
> log. If that info is imporant, I'll work on getting a serial console to
> capture it.
> 
> -- System Information:
> Debian Release: 3.1
>   APT prefers unstable
>   APT policy: (101, 'unstable')
> Architecture: i386 (i686)
> Kernel: Linux 2.6.12-1-k7
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> 
> Versions of packages linux-image-2.6.12-1-k7 depends on:
> ii  coreutils [fileutils]         5.2.1-2    The GNU core utilities
> ii  fileutils                     5.2.1-2    The GNU file management utilities 
> ii  initrd-tools                  0.1.81.1   tools to create initrd image for p
> ii  module-init-tools             3.2-pre1-2 tools for managing Linux kernel mo
> 
> -- no debconf information
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-kernel-REQUEST@xxxxxxxxxxxxxxxx
> with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

On Sat, Sep 10, 2005 at 02:41:13AM -0400, Anthony DeRobertis wrote:
> Oh, btw, it just died on a different tape tonight... I rebooted to
> 2.6.8, and it works fine there. So its definitely a regression from 2.6.8.
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-kernel-REQUEST@xxxxxxxxxxxxxxxx
> with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/