RE: Tracking ATA/ATAPI ioctl() calls....

["Bryce Simonds" <bryce.simonds%charteramg.com@localhost>]

Unfortunately,

That has failed me.  I've tried building a debug version of the kernel and
stepping through my program using gdb, but it always dies at the ioctl()
call; and I have no idea how I can step through the kernel.

I found that there was an ATADEBUG define that I put into the Makefile of a
GENERIC kernel build, but this doesn't seem to have given me any additional
insight into the problem. =/

Should I just stick in extra printf() calls into the ATA driver?  I'd prefer
not to modify the kernel's source code if I can help it; but I'll do so if I
must.

Thanks,
Bryce

-----Original Message-----
From: tech-kern-owner%NetBSD.org@localhost 
[mailto:tech-kern-owner%NetBSD.org@localhost] On
Behalf Of Antti Kantee
Sent: Tuesday, October 07, 2008 4:51 PM
To: Bryce Simonds
Cc: tech-kern%NetBSD.org@localhost
Subject: Re: Tracking ATA/ATAPI ioctl() calls....

On Tue Oct 07 2008 at 16:45:28 -0500, Bryce Simonds wrote:
> Thank you for the help,
> 
> Though I'm still a bit stuck.  From what I can tell, I am sending the
> correct data to the drive, and the kernel isn't doing anything with it,
but
> every time I attempt to issue the ATA secure erase command through ioctl()
> it hard locks the computer, and the drive does nothing.
> 
> Any ideas?

Lots of printfs ;)
(or other means of tracing)

If you can figure out what exactly locks the system, it's easier for
other people to suggest how to fix it.

No virus found in this incoming message.
Checked by AVG - http://www.avg.com 
Version: 8.0.173 / Virus Database: 270.7.6/1712 - Release Date: 10/7/2008
6:40 PM