Date: Tue, 4 Apr 2000 12:51:17 +0200 From: Samuel Tardieu <sam@inf.enst.fr> To: John Hay <jhay@mikom.csir.co.za> Cc: Soren Schmidt <sos@freebsd.dk>, freebsd-current@FreeBSD.ORG Subject: Re: ATA & 82C596 bug in 4.0-RELEASE? Message-ID: <2000-04-04-12-51-17%2Btrackit%2Bsam@inf.enst.fr> In-Reply-To: <200004041019.MAA65929@zibbi.mikom.csir.co.za>; from jhay@mikom.csir.co.za on Tue, Apr 04, 2000 at 12:19:03PM %2B0200 References: <200004040645.IAA94288@freebsd.dk> <200004041019.MAA65929@zibbi.mikom.csir.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/04, John Hay wrote: | I have a machine that can be trashed. The trouble is that it cannot | install 4.x or -current because of the problem with the ata driver. | During installation it just go in a loop during newfs and keep on | spitting out errors. You are lucky, you go further than I do :) It stops after printing "Probing devices", with the HD led on, on my Compaq Armada V300. Using DDB, I can see that sysinstall is in bioread state. I haven't had time to continue serial remote debugging yet, and I do not know where to break in the kernel. A question for hackers: from within GDB, you can call subprograms on the target. Is there any "helper" subprogram in the kernel that can print a list of processes (as in DDB) and display the context of a particular process given its PID? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2000-04-04-12-51-17%2Btrackit%2Bsam>