On Thu, Feb 24, 2000 at 09:03:55AM +0000, Doug Rabson wrote: [snip] > Nick Hibma's machine at work shows this problem. Its an AMD Athlon FWIW. > Nick spent a couple of hours looking at it without much success. I'll try > some things today to see if the probe is being called with interrupts > disabled. I'm getting this as well on my Twinhead Slimnote VX laptop. I'm loading vesa, linux, if_tun, usb and ums as modules. I can provide a successful boot dmesg and suchlike if you're interested. It's a PIIX4 controller and a mobile Pentium II 333. -- Benno Rice "No, no. We're *sweet* and XNFP Aries Dark Subculture- *innocent* evil bastards." friendly Internet Geek [EMAIL PROTECTED] "Defend your joy" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Re: After last ATAPI update system doesn't boot ... Mike Smith
- Re: After last ATAPI update system doesn't ... Thierry Herbelot
- Re: After last ATAPI update system does... Mike Smith
- Re: After last ATAPI update system ... Thierry Herbelot
- Re: After last ATAPI update system ... Mike Smith
- Re: After last ATAPI update system ... Yarema
- Re: After last ATAPI update system ... Mike Smith
- Re: After last ATAPI update system ... Soren Schmidt
- Re: After last ATAPI update system ... Doug Rabson
- Re: After last ATAPI update system ... Soren Schmidt
- Re: After last ATAPI update system ... Benno Rice
- Re: After last ATAPI update system ... Yarema
- Re: After last ATAPI update system ... Mike Smith
- Re: After last ATAPI update system ... Soren Schmidt
- Re: After last ATAPI update system ... Mike Smith
- Re: After last ATAPI update system ... Brian Fundakowski Feldman
- Re: After last ATAPI update system ... Mike Smith
- Re: After last ATAPI update system ... Brian Fundakowski Feldman
- Re: After last ATAPI update system ... Doug Barton
- Re: After last ATAPI update system ... Warner Losh