The system will hang while connected to my internet service provider. By
hang, I mean I can switch between consoles using alt-F?, but cannot use
any of them. All outgoing netowrk activity indicated by the modem leds
appears to cease. The hang may occur when the remote site opens a new
smtp connection, but that may be a coincidence. The hang can occur
anytime after making the dialup connection. It doesn't always happen.
If I use ALT-F9 to switch to console 9, when only 8 have been compiled in,
instead of the normal short beep the speaker will beep continuosly.
I thought at first that it was something to do with PPP, so I switched
to using slip. No joy.
No diagnostics or core-dumps are produced. The only thing I can do
is to reboot and fsck the disks.
PPP has worked 100% using 126.96.36.199 for many months.
None known at this time.
I don't know of any way to provoke the bug.
There were a variety of causes of system hangs and panics in this
area caused by improper allocation/reservation of cblocks. This has
been fixed during the past few months and should no longer occur.
>Originator: James Seward
>Synopsis: amd64/6-STABLE can't see disks at boot
>Environment: Output from a kernel that boots; all kernels after this have had the problem:
FreeBSD tomo.jamesoff.net 6.0-STABLE FreeBSD 6.0-STABLE #6: Sun Nov 6 13:10:48 GMT 2005 email@example.com:/usr/obj/usr/src/sys/TOMO64 amd64
Since approx Nov 6, 6-STABLE kernels are unable to see my ATA disks on my amd64 machine. Until that point, I have had no problems with that machine or 6-RELEASE/6-STABLE. The boot fails when it tries to mount the root partition but apparently can't see any ATA disks. I have both SATA and PATA disks on the machine and it can't see any of them. The IDE LED on the case goes on solidly and sticks at this point in the boot.
This problem occurs with both my custom config (as used in the working kernel) and with GENERIC. I have cvsup'd an entire clean src tree as well as nuked /usr/obj. My most recent test was a cvsup on the evening of Jan 15th 2006, and that failed too.
dmesg output from a successful boot:
dmesg -v output from an unsuccessful boot:
Boot a kernel > 6 Nov 2005
No fix; workaround is to boot a kernel from <= Nov 6 2005.