On Wed, May 31, 2000 at 02:30:14PM -0700, Chaitanya Tumuluri wrote:
> First off, there is no support for IDE devices in CONFIG_KIOBUF_IO.
> That option only works for scsi devices. And the code actually
> checks for that in ll_rw_blk.c, in the function ll_rw_kio():
>
> /*
> * Only support SCSI disk for now.
> *
> * ENOSYS to indicate caller
> * should try ll_rw_block()
> * for non-SCSI (e.g. IDE) disks.
> */
> if (!SCSI_DISK_MAJOR(MAJOR(dev))){
> *error = -ENOSYS;
> goto end_io;
> }
>
> And the pagebuf_segment_apply() routine should then try the regular
> buffer head patch if it gets an ENOSYS from trying a kiobuf-based
> I/O request.
Yes, I read that. My theory was that the fallback path is broken.
Unfortunately I cannot test it for tonight anymore, sorry.
>
> >> The kernel log gave:
> >>
> >> start mounting filesystem: ide1(22,5)
> >> Ending clean XFS mount for filesystem: ide1(22,5)
> >> blocklog end: 12
> >> linvfs_read_super: sb root ino/128 inode/0xc5a011a0 icnt/2 vp/0xc5a012b0
> >> attempt to access beyond end of device
> >> 16:05: rw=0, want=38781096, limit=8191984
> >> end_pg_buffer_io_async not uptodate 0 page 0xc119d150
> >> attempt to access beyond end of device
> >> 16:05: rw=0, want=38781096, limit=8191984
> >> end_pg_buffer_io_async not uptodate 0 page 0xc119d150
> >> attempt to access beyond end of device
> >> 16:05: rw=0, want=38781096, limit=8191984
> >> end_pg_buffer_io_async not uptodate 0 page 0xc119d150
>
> Hmmm..Its actually trying to go after a device with major number 16...that
> should be a cdrom device, unless I'm mistaken. This is definitely not in
> the new CONFIG_KIOBUF_IO codepath. Why should the requests be generated to
> read past 8MB of the CD device?
The HD is connected to the second controller, the HD is /dev/hdc
[was not my idea, I got it this way]
-Andi
|