public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zan Lynx <zlynx@acm.org>
To: "Berck E. Nash" <flyboy@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	reiserfs-dev@namesys.com
Subject: Re: 2.6.22-rc3-mm1 reiser4 bug
Date: Sun, 03 Jun 2007 01:12:18 +0000	[thread overview]
Message-ID: <1180833139.7501.4.camel@localhost> (raw)
In-Reply-To: <4661C0DA.7040308@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 880 bytes --]

On Sat, 2007-06-02 at 13:11 -0600, Berck E. Nash wrote:
> All appears to work fine, until I try to boot a kernel with a Reiser4 /
> partition.  Then I get endless errors of the sort:
> 
> [  206.349450] sd 1:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET
> driverbyte=DRIVER_OK,SUGGEST_OK
> 
> (See attached dmesg for more, I only sent the first 1,000 lines, it goes
> on until a hard reboot.)
> 
> The same partition and the same kernel work great as long as that
> partition isn't the current system root.  The same kernel and the same
> hard drive works fine as long as the partition is formatted ReiserFS.

It can't be a simple bug, because I am running 2.6.22-rc3-mm1 and
Reiser4 on / right now, and it works well for me.

I am using a busybox initramfs that does the actual mounting.  I don't
know if that makes a difference.
-- 
Zan Lynx <zlynx@acm.org>

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 196 bytes --]

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3137 bytes --]

  reply	other threads:[~2007-06-03  1:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-02 19:11 2.6.22-rc3-mm1 reiser4 bug Berck E. Nash
2007-06-03  1:12 ` Zan Lynx [this message]
2007-06-05 11:40 ` Edward Shishkin

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=1180833139.7501.4.camel@localhost \
    --to=zlynx@acm.org \
    --cc=flyboy@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-dev@namesys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox