From: Andrew Morton <akpm@digeo.com>
To: Alexander Hoogerhuis <alexh@ihatent.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Christoph Hellwig <hch@lst.de>
Subject: Re: 2.5.70-mm6
Date: Sat, 7 Jun 2003 17:56:49 -0700 [thread overview]
Message-ID: <20030607175649.6bf3813b.akpm@digeo.com> (raw)
In-Reply-To: <873cilz9os.fsf@lapper.ihatent.com>
Alexander Hoogerhuis <alexh@ihatent.com> wrote:
>
> Andrew Morton <akpm@digeo.com> writes:
> >
> > [SNIP]
> >
>
> It builds nicely here and runs nicely so far, but my USB-drive still
> blows up after a few gigs
Is that usb-storage? There seem to have been a few reports of
erratic behaviour lately.
> and I have this one when plugging it in:
>
> Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
> spurious 8259A interrupt: IRQ7.
> SCSI device sda: 490232832 512-byte hdwr sectors (250999 MB)
> sda: cache data unavailable
> sda: assuming drive cache: write through
> /dev/scsi/host0/bus0/target0/lun0: p1
> devfs_mk_dir(scsi/host0/bus0/target0/lun0): could not append to dir: ea549820 "target0"
Maybe Christph can decode this one for us.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-06-08 0:56 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-07 22:14 2.5.70-mm6 Andrew Morton
2003-06-08 0:37 ` 2.5.70-mm6 Alexander Hoogerhuis
2003-06-08 0:56 ` Andrew Morton [this message]
2003-06-08 1:13 ` 2.5.70-mm6 Alexander Hoogerhuis
2003-06-08 12:25 ` 2.5.70-mm6 Christoph Hellwig
2003-06-08 12:09 ` 2.5.70-mm6 Felipe Alfaro Solana
2003-06-08 22:52 ` 2.5.70-mm6 Pasi Savolainen
2003-06-09 17:45 ` 2.5.70-mm6 Maciej Soltysiak
2003-06-09 17:39 ` 2.5.70-mm6 Martin J. Bligh
2003-06-09 18:19 ` 2.5.70-mm6 Maciej Soltysiak
2003-06-09 18:51 ` 2.5.70-mm6 Martin J. Bligh
2003-06-09 19:42 ` 2.5.70-mm6 Maciej Soltysiak
2003-06-09 20:04 ` 2.5.70-mm6 William Lee Irwin III
2003-06-10 8:54 ` 2.5.70-mm6 Maciej Soltysiak
2003-06-10 9:20 ` 2.5.70-mm6 William Lee Irwin III
2003-06-10 11:31 ` 2.5.70-mm6 Mike Galbraith
2003-06-10 11:41 ` 2.5.70-mm6 William Lee Irwin III
2003-06-10 11:51 ` Sharing Boottime allocated memory with user-space processes ZCane, Ed (Test Purposes)
2003-06-10 18:53 ` 2.5.70-mm6 Mike Galbraith
2003-06-10 19:11 ` 2.5.70-mm6 William Lee Irwin III
2003-06-10 11:52 ` 2.5.70-mm6 Maciej Soltysiak
2003-06-09 20:08 ` 2.5.70-mm6 Felipe Alfaro Solana
2003-06-09 20:14 ` 2.5.70-mm6 Martin J. Bligh
2003-06-09 21:09 ` 2.5.70-mm6 Felipe Alfaro Solana
2003-06-10 9:56 ` 2.5.70-mm6 Felipe Alfaro Solana
2003-06-09 18:39 ` 2.5.70-mm6 Felipe Alfaro Solana
2003-06-09 18:06 ` 2.5.70-mm6 Alistair J Strachan
2003-06-09 18:36 ` 2.5.70-mm6 Felipe Alfaro Solana
2003-06-09 19:07 ` 2.5.70-mm6 Pasi Savolainen
2003-06-11 2:15 ` 2.5.70-mm6 Mingming Cao
2003-06-11 3:12 ` 2.5.70-mm6 Andrew Morton
2003-06-11 22:15 ` 2.5.70-mm6 Mingming Cao
2003-06-12 16:37 ` 2.5.70-mm6 Mingming Cao
2003-06-12 17:50 ` 2.5.70-mm6 Andrew Morton
2003-06-12 18:43 ` 2.5.70-mm6 Mingming Cao
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=20030607175649.6bf3813b.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=alexh@ihatent.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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