All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Mansfield <patmans@us.ibm.com>
To: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: USB-storage/SCSI panic/error writing CF card
Date: Thu, 9 Jan 2003 10:53:29 -0800	[thread overview]
Message-ID: <20030109105329.A8326@beaverton.ibm.com> (raw)
In-Reply-To: <20030109183614.GA1167@Master.Wizards>; from murrayr@brain.org on Thu, Jan 09, 2003 at 01:36:14PM -0500

On Thu, Jan 09, 2003 at 01:36:14PM -0500, Murray J. Root wrote:

> Writing to the card sometimes hangs the process when unmounting 
> 
> Sometimes the data IS written to the card first, then it hangs the process.
> 
> Sometimes the card is corrupt (cannot cd to the mountpoint -I/O error)
>   /var/log/messages has several lines like:
>   Jan  9 13:08:51 Master kernel: FAT: Filesystem panic (dev sd(8,1))
>   Jan  9 13:08:51 Master kernel:     Directory 4: invalid cluster chain
>   
> Sometimes get kernel panic with ONLY these 2 lines:
>   "Error handler thread not present at f7a57000 f7bf0d80 drivers/scsi/scsi-error.c 154"
>   "In interrupt handler - not syncing"
>   No messages in logs

The panic is caused by timeout on a scsi command when the error handler
has unexpectedly gone away, possibly because of this bug, where the erorr
handler exits early because of a SIGHUP:

http://marc.theaimsgroup.com/?l=linux-scsi&m=104145526331820&w=2

Fixing the panic won't fix the corruption. scsi should really offline the
adapter and scsi devices on the adapter rather than panic.

-- Patrick Mansfield

      reply	other threads:[~2003-01-09 18:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-09 18:36 USB-storage/SCSI panic/error writing CF card Murray J. Root
2003-01-09 18:53 ` Patrick Mansfield [this message]

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=20030109105329.A8326@beaverton.ibm.com \
    --to=patmans@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.