Re: Repeated lockups with 4.10
From: stan (stanb_at_panix.com)
Date: 07/30/04
- Previous message: Ezequiel: "contigmalloc1: size must not be 0"
- In reply to: Steve: "Re: Repeated lockups with 4.10"
- Next in thread: Steve: "Re: Repeated lockups with 4.10"
- Reply: Steve: "Re: Repeated lockups with 4.10"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 30 Jul 2004 09:47:57 -0400 To: Steve <steve@n2sw.com>
On Fri, Jul 30, 2004 at 07:34:27AM -0700, Steve wrote:
> do you have anything in dmesg, logs, any cores, etc ......
Unfortunately no. It apears that teh systems are getting some sort of
hardware intrupt (serial port?, disk I/O ?), and that they then corupt
somthing, and since they are off in an iterupt, they never return.
Is it possible to add any kernel debuging or something like that to try to
track this?
-- "They that would give up essential liberty for temporary safety deserve neither liberty nor safety." -- Benjamin Franklin _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
- Previous message: Ezequiel: "contigmalloc1: size must not be 0"
- In reply to: Steve: "Re: Repeated lockups with 4.10"
- Next in thread: Steve: "Re: Repeated lockups with 4.10"
- Reply: Steve: "Re: Repeated lockups with 4.10"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|