On Tuesday 02 January 2007 10:36, Jeremy Chadwick wrote:
Yes, I know 4.11 is EOL'd at the end of this month, but hopefully
someone can shed some light on this problem anyways. I simply don't
have the knowledge of what's going on on a low-level to determine
the cause.
I do have serial
On Thu, Jan 11, 2007 at 01:40:48PM -0500, John Baldwin wrote:
On Tuesday 02 January 2007 10:36, Jeremy Chadwick wrote:
Yes, I know 4.11 is EOL'd at the end of this month, but hopefully
someone can shed some light on this problem anyways. I simply don't
have the knowledge of what's going on
On Thursday 11 January 2007 16:13, Jeremy Chadwick wrote:
On Thu, Jan 11, 2007 at 01:40:48PM -0500, John Baldwin wrote:
On Tuesday 02 January 2007 10:36, Jeremy Chadwick wrote:
Yes, I know 4.11 is EOL'd at the end of this month, but hopefully
someone can shed some light on this problem
On Thu, Jan 11, 2007 at 04:47:17PM -0500, John Baldwin wrote:
On Thursday 11 January 2007 16:13, Jeremy Chadwick wrote:
The kernel I'm using was built on the following date (thus, src-all
for release=cvs tag=RELENG_4 was cvsup'd about an hour prior to this):
FreeBSD pentarou.parodius.com
Yes, I know 4.11 is EOL'd at the end of this month, but hopefully
someone can shed some light on this problem anyways. I simply don't
have the knowledge of what's going on on a low-level to determine
the cause.
I do have serial console on this box, and after enabling some
debugging for the
Brute force things to try, IMO:
a) Try a different (non-adaptec) SCSI controller
b) Run non-SMP
c) Swap motherboard
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to
On Tue, 2007-01-02 at 07:36 -0800, Jeremy Chadwick wrote:
Yes, I know 4.11 is EOL'd at the end of this month, but hopefully
someone can shed some light on this problem anyways. I simply don't
have the knowledge of what's going on on a low-level to determine
the cause.
I do have serial
On Tue, Jan 02, 2007 at 04:39:51PM +, Gavin Atkinson wrote:
On Tue, 2007-01-02 at 07:36 -0800, Jeremy Chadwick wrote:
# vmstat -i
ata0 irq14 6 0
fxp0 irq10 14874 28
mux irq11 65028125
fdc0 irq6
Jeremy Chadwick wrote:
Once the machine is hung like described, since running shell
commands (date/vmstat/even spawning sh itself) involves disk I/O,
this won't work. If date and vmstat could be cached in memory
somewhere, this might work, but I don't know how one would do that.
(A memory
