Date: Mon, 20 May 2002 15:20:03 -0700 (PDT) From: Matthias Andree <matthias.andree@web.de> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/37060 Message-ID: <200205202220.g4KMK3493108@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/37060; it has been noted by GNATS. From: Matthias Andree <matthias.andree@web.de> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: Matthias Andree <matthias.andree@stud.uni-dortmund.de>, matthias.andree@web.de, freebsd-gnats-submit@freebsd.org, sos@freebsd.org Subject: Re: kern/37060 Date: Tue, 21 May 2002 00:12:02 +0200 On Mon, May 20, 2002 at 03:53:15PM -0400, Andrew Gallatin wrote: [ata-disk.c:710] > What if you protect those access with a check for a non-null driver? Didn't try yet. > Also, what happens if you comment out the call to the > ata_raiddisk_attach() in ad_attach() ? Good question: Skipping the if(ata_raiddisk_attach(adp)) call with "return" in a remote gdb on all occasions lets the machine boot up properly. One observation of the failed runs: The first raiddisk_attach (Primary Master) has a NULL table, and subsequently allocates one. The Primary Slave is skipped right away. When FreeBSD then tries to attach ad1 (ad2 with ATA_STATIC_ID, secondary master), it crashes with the known symptoms. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200205202220.g4KMK3493108>