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 <[email protected]>
Attachment:
signature.asc
Description: This is a digitally signed message part
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
- References:
- 2.6.22-rc3-mm1 reiser4 bug
- From: "Berck E. Nash" <[email protected]>
- 2.6.22-rc3-mm1 reiser4 bug
- Prev by Date: Re: Kernel 2.6.22-rc3 safe to migrate to?
- Next by Date: Re: Device Driver Etiquette
- Previous by thread: 2.6.22-rc3-mm1 reiser4 bug
- Next by thread: Re: 2.6.22-rc3-mm1 reiser4 bug
- Index(es):
 |