Re: 2.6.30-rc4 kernel

[Borislav Petkov <petkovbb@googlemail.com>]

Hi,

On Tue, May 19, 2009 at 07:57:06AM +0200, Borislav Petkov wrote:
> (adding linux-ide to CC)
> 
> On Mon, May 18, 2009 at 09:05:58PM +0100, rob@housetosell.net wrote:
> > On Wed, May 13, 2009 at 07:17:17PM +0100, rob1@housetosell.net wrote:
> > 
> > Hi
> > 
> > I am not sure how much use this will be however if a break point is set to cdrom_newpc_intr and go is continuosly pressed then the kernel will actually boot (it will also boot if there is no media in the cdrom's) however the cdrom cannot be mounted. The dmesg output and the syslog may provide some useful information:-
> > 
> > from dmesg
> > 
> > ide-cd: hdc: ide_cd_check_ireason: bad interrupt reason 0x03
> > hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
> > ide: failed opcode was: unknown
> > hdc: drive not ready for command
> > 
> > and from the syslog
> > 
> > May 18 19:30:37 jewel kernel: hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
> > May 18 19:30:37 jewel kernel: ide: failed opcode was: unknown
> > May 18 19:30:37 jewel kernel: hdc: drive not ready for command
> > May 18 19:30:37 jewel kernel: attempt to access beyond end of device
> > May 18 19:30:37 jewel kernel: hdc: rw=0, want=68, limit=4
> > May 18 19:30:37 jewel kernel: isofs_fill_super: bread failed, dev=hdc, iso_blknum=16, block=16
> > 
> > Full versions of dmesg and the syslog are below.

by the way, can you send the dmesg of a kernel with which your hdc drive
works fine?

Thanks.

-- 
Regards/Gruss,
    Boris.