From: Andrew Morton <akpm@osdl.org>
To: "Olivier RAMAT" <olrt@ifrance.com>
Cc: linux-kernel@vger.kernel.org,
James Bottomley <James.Bottomley@steeleye.com>
Subject: Re: Kernel 2.6.9 oops during data transfer to noname usb key
Date: Fri, 3 Dec 2004 01:32:54 -0800 [thread overview]
Message-ID: <20041203013254.55534ef8.akpm@osdl.org> (raw)
In-Reply-To: <0412030857.370100@th00.idoo.com>
"Olivier RAMAT" <olrt@ifrance.com> wrote:
>
> Hello !
> This is my first post to the linux.kernel mailing list so please
> apologize ;-)
>
> Here's the oops that I experienced while copying files to my noname
> usb key :
A few things have been fixed since then. Please test either 2.6.10-rc2
plus
ftp://ftp.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.10-rc2-bk16.gz
or test 2.6.10-rc3 when it is released. And then send a followup report.
> Nov 10 07:47:40 darkstar kernel: [<c0103f25>]
> kernel_thread_helper+0x5/0x10
> Nov 10 07:47:40 darkstar kernel: SCSI error : <0 0 0 0> return code =
> 0x70000
> Nov 10 07:47:40 darkstar kernel: end_request: I/O error, dev sda, sector
> 348970
> Nov 10 07:47:40 darkstar kernel: Buffer I/O error on device sda1,
> logical block 348907
> Nov 10 07:47:40 darkstar kernel: lost page write due to I/O error on
> sda1
> Nov 10 07:47:50 darkstar kernel: ------------[ cut here ]------------
> Nov 10 07:47:50 darkstar kernel: kernel BUG at
> /usr/src/linux-2.6.9/drivers/block/as-iosched.c:1853!
Ouch. Haven't seen that before. Maybe scsi error recovery screwed up the
request queueing. James, have we fixed anything in that area post-2.6.9?
next prev parent reply other threads:[~2004-12-03 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 8:57 Kernel 2.6.9 oops during data transfer to noname usb key Olivier RAMAT
2004-12-03 9:32 ` Andrew Morton [this message]
2004-12-03 10:57 ` Jens Axboe
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=20041203013254.55534ef8.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=James.Bottomley@steeleye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olrt@ifrance.com \
/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.