All of lore.kernel.org
 help / color / mirror / Atom feed
From: linux-kernel@jmbreuer.net
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: linux-kernel@jmbreuer.net, linux-scsi@vger.kernel.org,
	Kai.Makisara@kolumbus.fi
Subject: Re: [Bug 14563] SCSI tape driver: Spurious EIO and kernel BUG
Date: Tue, 17 Nov 2009 12:00:35 +0100	[thread overview]
Message-ID: <4B028253.1040407@jmbreuer.net> (raw)
In-Reply-To: <20091117141437G.fujita.tomonori@lab.ntt.co.jp>

FUJITA Tomonori wrote:
>>> Performing tape backups using amanda 2.6.0-p2 [using 512kB block size] leads to
>>> spurious 'EIO' errors when writing to the tape; most of the time a kernel BUG
>>> is hit shortly thereafter.
>>>
>> Can you try this with debugging enabled in st? (Edit st.c to
>> '#define DEBUG 1' and recompile the module.) This might give more 
>> information about the source of the EIO and the code path it uses.
> 
> Sorry about that bug.
> 
> Looks like that st drivers messes up memory management but the log
> doesn't give enough information.
> 
> As Kai suggested, please enable the debug option and send the new log.

I've attached the relevant information to
http://bugzilla.kernel.org/show_bug.cgi?id=14563

Thanks!


So long,
   Joe

  reply	other threads:[~2009-11-17 11:00 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09  8:29 [Bug 14563] New: SCSI tape driver: Spurious EIO and kernel OOPS bugzilla-daemon
2009-11-09  8:29 ` [Bug 14563] " bugzilla-daemon
2009-11-09  8:29 ` bugzilla-daemon
2009-11-09  8:30 ` bugzilla-daemon
2009-11-09  8:30 ` bugzilla-daemon
2009-11-09  8:31 ` bugzilla-daemon
2009-11-09  8:32 ` [Bug 14563] SCSI tape driver: Spurious EIO and kernel BUG bugzilla-daemon
2009-11-09  8:33 ` bugzilla-daemon
2009-11-16 19:19 ` [Bug 14563] New: SCSI tape driver: Spurious EIO and kernel OOPS Kai Makisara
2009-11-16 19:19 ` [Bug 14563] SCSI tape driver: Spurious EIO and kernel BUG bugzilla-daemon
2009-11-17  5:14   ` FUJITA Tomonori
2009-11-17 11:00     ` linux-kernel [this message]
2009-11-17 21:00       ` Kai Makisara
2009-11-18 21:55         ` Kai Makisara
2009-11-19  7:46           ` FUJITA Tomonori
2009-11-19 20:03             ` Kai Makisara
2009-11-17  5:15 ` bugzilla-daemon
2009-11-17 10:56 ` bugzilla-daemon
2009-11-18  9:18   ` FUJITA Tomonori
2009-11-17 10:57 ` bugzilla-daemon
2009-11-17 10:57 ` bugzilla-daemon
2009-11-18  9:18 ` bugzilla-daemon
2009-11-18 15:37 ` bugzilla-daemon
2009-11-18 15:38 ` bugzilla-daemon
2009-11-18 15:39 ` bugzilla-daemon
2009-11-18 16:53 ` bugzilla-daemon
2009-11-19  7:50   ` FUJITA Tomonori
2009-11-18 16:54 ` bugzilla-daemon
2009-11-19  7:51 ` bugzilla-daemon
2009-11-23 12:10 ` bugzilla-daemon
2009-11-23 20:12   ` Kai Makisara
2009-11-25  0:21   ` FUJITA Tomonori
2009-11-23 20:12 ` bugzilla-daemon
2009-11-25  0:21 ` bugzilla-daemon
2009-11-25  9:47 ` bugzilla-daemon
2009-11-25 16:51 ` bugzilla-daemon
2009-11-26  0:26   ` FUJITA Tomonori
2009-11-26  0:27 ` bugzilla-daemon
     [not found] <bug-14563-11613@https.bugzilla.kernel.org/>
2012-06-14 16:51 ` bugzilla-daemon
2012-06-14 16:51 ` bugzilla-daemon

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=4B028253.1040407@jmbreuer.net \
    --to=linux-kernel@jmbreuer.net \
    --cc=Kai.Makisara@kolumbus.fi \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --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.