Re: Someone ( bsg merge ? ) broke {sd,hd}parm on current git

[James Bottomley]

On Thu, 2007-07-19 at 08:25 +0900, FUJITA Tomonori wrote:
> From: Gabriel C <nix.or.die@xxxxxxxxxxxxxx>
> Subject: Re: Someone ( bsg merge ? ) broke {sd,hd}parm on current git
> Date: Tue, 17 Jul 2007 03:40:58 +0200
> 
> > FUJITA Tomonori wrote:
> > > From: Gabriel C <nix.or.die@xxxxxxxxxxxxxx>
> > > Subject: Re: Someone ( bsg merge ? ) broke {sd,hd}parm on current git
> > > Date: Tue, 17 Jul 2007 02:44:38 +0200
> > >
> > >   
> > >> Gabriel C wrote:
> > >>     
> > >>> Hello,
> > >>>
> > >>> sdparm and hdparm are broken for me on git (
> > >>> abce891a10559343d8ac9f79b46d78afdba63a40 )
> > >>>
> > >>>
> > >>> ~$ sudo hdparm  /dev/sdc
> > >>>
> > >>> /dev/sdc:
> > >>>  BLKROGET failed: Inappropriate ioctl for device
> > >>>  BLKRAGET failed: Inappropriate ioctl for device
> > >>>  BLKGETSIZE failed: Inappropriate ioctl for device
> > >>>
> > >>>
> > >>> ~$ sudo sdparm  --all /dev/sdc
> > >>> unable to access /dev/sdc, ATA disk?
> > >>>
> > >>>   
> > >>>       
> > >> Well it is bsg , setting BLK_DEV_BSG=n fixed all this errors.
> 
> I've not tested this yet (need to find sata drives in my workplace),
> but James Bottomley told me that both works for him with bsg enabled.
> It might worth trying the latest git tree.

It certainly does work for me.  However, my ATA devices are connected to
an aic94xx SAS controller.  Although this uses libata, the ioctl path is
probably slightly different from the libata one. I assume you're using a
SATA controller?  Unfortunately I have no ability to test on a SATA
controller, but I'd suggest looking at the ioctl and REQ_BLOCK_PC paths
in libata for clues.

James


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/