Re: Some CDIO ioctl's are broken
"SÜren Schmidt" wrote: > It seems Maxim Sobolev wrote: > > Hi Soren, > > > > It seems that after a commit to reduce stack usage in ata driver some CDIO > > ioctl's stopped working. Particularly, CDIOCREADSUBCHANNEL now returns an > > 'Invalid argument'. This could be verified by executing `cdcontrol stat'. > > Uhm: > > sos> cdcontrol -f acd0 stat > No current status info available > No media catalog info available > Left volume = 255, right volume = 255 > > That looks pretty OK to me ... No it isn't normal. Try to truss(1) it and see the problem which leads to the first string to be "No current status info available". Alternatively, try to boot 11 days old kernel and see the difference. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Some CDIO ioctl's are broken
It seems Maxim Sobolev wrote: > Hi Soren, > > It seems that after a commit to reduce stack usage in ata driver some CDIO > ioctl's stopped working. Particularly, CDIOCREADSUBCHANNEL now returns an > 'Invalid argument'. This could be verified by executing `cdcontrol stat'. Uhm: sos> cdcontrol -f acd0 stat No current status info available No media catalog info available Left volume = 255, right volume = 255 That looks pretty OK to me ... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Some CDIO ioctl's are broken
Hi Soren, It seems that after a commit to reduce stack usage in ata driver some CDIO ioctl's stopped working. Particularly, CDIOCREADSUBCHANNEL now returns an 'Invalid argument'. This could be verified by executing `cdcontrol stat'. Please fix. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
