RE: Recent -CURRENT panic (New interrupt code related?); backtrace included
On 13-Nov-2003 Xin LI/ÀîöÎ wrote: > Yes I have device apic enabled, and after setting options NO_MIXED_MODE, the > problem persists. However, fortunatelly, the spurious.patch seemed to solved > the problem, and the system has been up for 9 hours without panic'ing as I > described before. > > Do you need me to test atpic.patch as well? No, that is fine, thanks. I will have a better patch later today that should hopefully work both with and without mixed mode. -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Recent -CURRENT panic (New interrupt code related?); backtrace included
Yes I have device apic enabled, and after setting options NO_MIXED_MODE, the problem persists. However, fortunatelly, the spurious.patch seemed to solved the problem, and the system has been up for 9 hours without panic'ing as I described before. Do you need me to test atpic.patch as well? -Original Message- From: John Baldwin [mailto:[EMAIL PROTECTED] Sent: Thursday, November 13, 2003 12:29 AM To: Xin LI/李鑫 Cc: [EMAIL PROTECTED] Subject: RE: Recent -CURRENT panic (New interrupt code related?); backtrace included > Do you have 'device apic' enabled? If so, can you try using 'options NO_MIXED_MODE'. > Barring that, can you try http://www.FreeBSD.org/~jhb/patches/spurious.patch and if that doesn't work > http://www.FreeBSD.org/~jhb/patches/atpic.patch? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Recent -CURRENT panic (New interrupt code related?); backtrace included
On 12-Nov-2003 Xin LI/李鑫 wrote: > Hello, > > On recently compiled kernels, I often get panics which seemed to be interrupt > related. Among > other things, almost all of them claims that "Kernel trap 30", which seemd to be > strange. > > The kernel I am currently running, namely, > > FreeBSD servers.frontfree.net 5.1-CURRENT FreeBSD 5.1-CURRENT #5: Sat Oct 25 > 22:27:05 CST 2003 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SERVERS i386 > > seemed to be ok, however, when I am trying the new kernels (you see, 14 compile and > run > attempts:), it exhibits incredible instablity. > > FreeBSD 5.1-CURRENT #19: Wed Nov 12 12:17:28 CST 2003 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SERVERS > > Here is one of the crashdumps I caught. The machine was configured with a UP kernel, > with > DEVICE_POLLING enabled. There are two networking adapters attached to it, a fxp and > a dc, and the > machine itself act as a NAT gateway. The network load is not very heavy. If you > think the > backtrace helpful, or need any more information, please write me and I will try > everything I can > to help. Do you have 'device apic' enabled? If so, can you try using 'options NO_MIXED_MODE'. Barring that, can you try http://www.FreeBSD.org/~jhb/patches/spurious.patch and if that doesn't work http://www.FreeBSD.org/~jhb/patches/atpic.patch? -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
