From: Nick Orlov <bugfixer@list.ru>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Jens Axboe <axboe@suse.de>
Subject: Re: Fw: 2.6.12-mm2: 3ware SATA RAID inaccessible
Date: Tue, 28 Jun 2005 21:58:30 -0400 [thread overview]
Message-ID: <20050629015830.GA4203@nikolas.hn.org> (raw)
In-Reply-To: <20050628142300.GX4410@suse.de>
On Tue, Jun 28, 2005 at 04:23:02PM +0200, Jens Axboe wrote:
> On Tue, Jun 28 2005, James Bottomley wrote:
> > On Tue, 2005-06-28 at 14:09 +0200, Jens Axboe wrote:
> > > > Hard to say. Kernel panics right after the small pause during detection.
> > > > And scroll back does not work. I don't really know what it prints before.
> > >
> > > Try this variant, fixes the mapping type and kunmap_atomic().
> >
> > Actually, I suspect the problem is the BUG_ON(len < 7). The mode sense
> > routines have to be really careful for USB, so we request 4 bytes at
> > first to get the true mode length, hence I think this trips.
>
> Sounds plausible, the other bugs wouldn't show up unless Nick is using
> highmem (or has it enabled, at least).
>
I'd like to confirm that this patch solves the problem for me :)
And yes, I don't use highmem.
Thank you,
Nick Orlov.
--
With best wishes,
Nick Orlov.
next prev parent reply other threads:[~2005-06-29 1:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-26 22:39 Fw: 2.6.12-mm2: 3ware SATA RAID inaccessible Andrew Morton
2005-06-26 23:37 ` James Bottomley
2005-06-27 4:46 ` Nick Orlov
2005-06-27 14:22 ` James Bottomley
2005-06-28 2:08 ` Nick Orlov
2005-06-28 4:05 ` James Bottomley
2005-06-28 11:02 ` Nick Orlov
2005-06-28 12:09 ` Jens Axboe
2005-06-28 14:18 ` James Bottomley
2005-06-28 14:23 ` Jens Axboe
2005-06-29 1:58 ` Nick Orlov [this message]
2005-06-27 7:52 ` Jens Axboe
2005-06-27 14:22 ` James Bottomley
2005-06-27 14:27 ` Jens Axboe
2005-06-28 8:25 ` 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=20050629015830.GA4203@nikolas.hn.org \
--to=bugfixer@list.ru \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox