Date: Thu, 9 Jan 1997 13:10:02 -0800 (PST) From: se@freebsd.org (Stefan Esser) To: freebsd-bugs Subject: Re: kern/2425: amd driver does not reprobe devices. Message-ID: <199701092110.NAA21676@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/2425; it has been noted by GNATS. From: se@freebsd.org (Stefan Esser) To: nsayer@quack.kfu.com Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: kern/2425: amd driver does not reprobe devices. Date: Thu, 9 Jan 1997 22:00:37 +0100 On Jan 8, nsayer@quack.kfu.com wrote: > >Description: > > scsi -f /dev/scsi -p does not reprobe for devices that were not present > at boot time. Well, do other drivers do ? > >How-To-Repeat: > > Boot with nothing attached to the SCSI bus. > Suspend the machine. > Attach 1 or more SCSI devices > Resume the machine > scsi -f /dev/scsi -p will say: > 0: nothing. > 1: nothing. > 2: nothing. > 3: nothing. > 4: nothing. > 5: nothing. > 6: nothing. > 7: nothing. At least it didn't crash your system :) > >Fix: > > Somehow the scan_devices flag needs to be set when a reprobe is called > for. Perhaps calling DC390_init() would help somehow? Hmm, I don't have much time to spend on this, currently. SCSI bus resan is not supported, and I have no way to test AMD driver changes, since I got no such controller card (that is, why I needed a BETA tester :) The driver will need changes to work with the new generic SCSI code (from the SCSI branch), I think the "scan_devices" hack should be removed, then. (I didn't like it at all, but didn't have time and test equipment to change that part of the code.) Regards, STefan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199701092110.NAA21676>