Re: more panics from current (partII)
Once again our vinum build failed. This time it could do over 90% of 14 hours of work and we didn't got a panic just a hang. Only we could do while system was printing ata error messages was to press reset button. Difference to earlier situation is that we put back old 3c905 xl-card and removed 4 port dc-Znyx. At the same time we changed pci card positions. Do you still think this has nothing do ata kernel code? Tomppa login: ad6: WARNING - WRITE_DMA recovered from missing interrupt ad6: WARNING - WRITE_DMA recovered from missing interrupt ad6: WARNING - WRITE_DMA recovered from missing interrupt ad4: WARNING - WRITE_DMA recovered from missing interrupt ata2: spurious interrupt - status=0x51 error=0x84 reason=0x01 ad6: WARNING - WRITE_DMA recovered from missing interrupt ata2: spurious interrupt - status=0x51 error=0x84 reason=0x01 ata2: spurious interrupt - status=0x51 error=0x84 reason=0x01 ata2: spurious interrupt - status=0x51 error=0x84 reason=0x01 ata2: spurious interrupt - status=0x51 error=0x84 reason=0x01 ata2: spurious interrupt - status=0x51 error=0x84 reason=0x01 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
more panics from current (partII)
After adding more disks to this system it dies continously. Last two traces look quite the same. Tomppa ---clipclip--- login: kernel trap 19 with interrupts disabled NMI ... going to debugger kernel: type 19 trap, code=0 Stopped at rtcintr+0x57: callrtcin db trace rtcintr(0) at rtcintr+0x57 Xfastintr8() at Xfastintr8+0x68 --- interrupt, eip = 0xc037ed02, esp = 0xcd680cdc, ebp = 0xcd680cdc --- cpu_idle(73042444,890002c0,bde8241c,c780,10c2444) at cpu_idle+0x22 idle_proc(0,cd680d48,c700,50082444,c7df) at idle_proc+0x25 fork_exit(c01ecd40,0,cd680d48) at fork_exit+0xb1 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xcd680d7c, ebp = 0 --- db rtcintr(0) at rtcintr+0x57 Xfastintr8() at Xfastintr8+0x68 --- interrupt, eip = 0xc037ed02, esp = 0xcd680cdc, ebp = 0xcd680cdc --- db panic panic: from debugger Debugger(panic) Fatal trap 3: breakpoint instruction fault while in kernel mode instruction pointer = 0x8:0xc0375b34 stack pointer = 0x10:0xcd680a80 frame pointer = 0x10:0xcd680a8c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= IOPL = 0 current process = 11 (idle) Stopped at rtcintr+0x57: callrtcin db panic: from debugger Uptime: 7h17m58s Dumping 255 MB 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 Dump complete Shutting down ACPI Automatic reboot in 15 seconds - press a key on the console to abort -- Press a key on the console to reboot, -- or switch off the system now. Rebooting... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: more panics from current (partII)
Tomi Vainio - Sun Finland [EMAIL PROTECTED] writes: After adding more disks to this system it dies continously. Last two traces look quite the same. Tomppa ---clipclip--- login: kernel trap 19 with interrupts disabled NMI ... going to debugger An NMI almost certainly indicates a hardware failure. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: more panics from current (partII)
On Sun, 28 Sep 2003 08:27 pm, Tomi Vainio - Sun Finland wrote: After adding more disks to this system it dies continously. Last two traces look quite the same. Tomppa It could be a power supply on the way out. I had an old dual P-166 that rebooted misterously until I took out two CD-ROM drives I wanted for another machine. (replaced the power supply, and refitted the CDROMS, and every thing worked ok.) Lucas ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
