mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Brad Tilley <bradtilley@usa.net>
Cc: linux-kernel@vger.kernel.org, Oleg Drokin <green@linuxhacker.ru>
Subject: Re: Possible Bug in 2.4.24???
Date: Fri, 16 Jan 2004 20:13:27 -0200 (BRST)	[thread overview]
Message-ID: <Pine.LNX.4.58L.0401162000200.30607@logos.cnet> (raw)
In-Reply-To: <306iaPsCz6064S16.1074277731@uwdvg016.cms.usa.net>



On Fri, 16 Jan 2004, Brad Tilley wrote:

> While running a script that recursively changes permissions on a ftp
> directory, I received an error to the term window where the script was
> running. I then checked out /var/log/messages and saw the below kernel errors.
> The machine was generally unresponsive and had to be physically rebooted at
> the power switch. It worked fine upon reboot an fsck ran w/o producing any
> error... the script ran fine too. This is a HP XW4100 with a P4, 1.5GB DDR RAM
> and two very fast (15,000 RPM), very large (140GB) SCSI HDDs. It had been up
> for 9 days (since compiling and installing 2.4.24) and has worked fine until
> this point. Could someone tell me if this is or isn't a kernel bug?
>
>
> Jan 16 11:50:43 athop1 kernel: SCSI disk error : host 0 channel 0 id 1 lun 0
> return code = 8000002
> Jan 16 11:50:43 athop1 kernel: Info fld=0x2cd1bd9, Current sd08:15: sense key
> Hardware Error
> Jan 16 11:50:43 athop1 kernel: Additional sense indicates Internal target
> failure
> Jan 16 11:50:43 athop1 kernel:  I/O error: dev 08:15, sector 54128
> Jan 16 11:50:43 athop1 kernel: journal-601, buffer write failed
> Jan 16 11:50:43 athop1 kernel:  (device sd(8,21))
> Jan 16 11:50:43 athop1 kernel: kernel BUG at prints.c:341!
> Jan 16 11:50:43 athop1 kernel: invalid operand: 0000
> Jan 16 11:50:43 athop1 kernel: CPU:    0
> Jan 16 11:50:43 athop1 kernel: EIP:    0010:[<c0189878>]    Tainted: P

Brad,

A device error happened (you see the "SCSI disk error : " message and
"Additional sense indicates Internal target failure") which reiserfs
could not handle.

kernel BUG at prints.c:341 == reiserfs_panic().

  reply	other threads:[~2004-01-16 22:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-16 18:28 Brad Tilley
2004-01-16 22:13 ` Marcelo Tosatti [this message]
2004-01-17  1:04 [Re: Possible Bug in 2.4.24???] Brad Tilley
2004-01-17  5:11 ` Oleg Drokin
2004-01-17  6:23   ` Mike Fedyk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.58L.0401162000200.30607@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=bradtilley@usa.net \
    --cc=green@linuxhacker.ru \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®