From: Manfred Spraul <manfred@colorfullife.com>
To: Andre Hedrick <andre@linux-ide.org>
Cc: "Murray J. Root" <murrayr@brain.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.40-ac4 kernel BUG at slab.c:1477!
Date: Mon, 07 Oct 2002 17:43:29 +0200 [thread overview]
Message-ID: <3DA1ABA1.7080802@colorfullife.com> (raw)
In-Reply-To: Pine.LNX.4.10.10210061845320.23945-100000@master.linux-ide.org
Andre Hedrick wrote:
>
> Only that if it is SG it must conform the ATA/ATAPI DMA on 64kb on 4b
> boundaries.
>
What does that mean?
Is a 4 byte aligned buffer that doesn't cross a page boundary (4096
byte) an acceptable buffer for the inquiry buffer of ide-scsi?
--
Manfred
next prev parent reply other threads:[~2002-10-07 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-06 13:31 2.5.40-ac4 kernel BUG at slab.c:1477! Manfred Spraul
2002-10-06 22:43 ` Murray J. Root
2002-10-08 2:58 ` Murray J. Root
2002-10-06 23:15 ` Murray J. Root
2002-10-07 1:48 ` Andre Hedrick
2002-10-07 15:43 ` Manfred Spraul [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-06 6:58 Murray J. Root
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=3DA1ABA1.7080802@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.org \
--cc=murrayr@brain.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;
as well as URLs for NNTP newsgroup(s).