Re: Kernel Panic in 3.7
On Wed, Jul 20, 2005 at 10:46:34AM -0400, Masoud Sharbiani wrote: | Is it possible to fix that out of memory condition panic() so that | instead of a panic system closes one or more of the processes to | continue to run? Great Idea ! That way, your server will just keep running and shooting of random processes as time goes by. Sort of like russian roulette - it may be that silly cronjob that should've been killed months ago, or it might be your sshd. All bets are on ! Hmm - might not be such a good idea after all. Perhaps we can mark certain processes as 'not killable' for this use, then you can rest assured that your memory will soon be filled with non-killable processes. The panic may not be the best solution to this problem, but killing processes is far worse. Feel free to think up a better solution, write a patch and submit it for review but let's not go the linux way, please ;P Cheers, Paul 'WEiRD' de Weerd -- >[<++>-]<+++.>+++[<-->-]<.>+++[<+ +++>-]<.>++[<>-]<+.--.[-] http://www.weirdnet.nl/ [demime 1.01d removed an attachment of type application/pgp-signature]
Re: Kernel Panic in 3.7
Masoud Sharbiani <[EMAIL PROTECTED]> writes: > Ted, > Is it possible to fix that out of memory condition panic() so that > instead of a panic system closes one or more of the processes to > continue to run? Is it possible to fix that we have peace on earth and end hunger? //art > cheers, > Masoud Sharbiani > > Ted Unangst wrote: > > >On Mon, 18 Jul 2005, Gordon Ross wrote: > > > > > >>I've got an OpneBSD 3.7 machine (no patches - just the standard 3.7 CD > >>install) running under VMWare GSX Server V3.1 Today, the machine had > >>stopped with a panic. I did a "trace" and "ps" as per the instructions. > >>Below is the result of these extracted from /var/adm/messages after I > >>rebooted the machine. > >> > > > > > >>Is there anything else I should provide ? Anything else I should do if it > >>happens again ? > >> > > > >running out of memeory is an unsupported configuration. buy some more.
Re: Kernel Panic in 3.7
Ted, Is it possible to fix that out of memory condition panic() so that instead of a panic system closes one or more of the processes to continue to run? cheers, Masoud Sharbiani Ted Unangst wrote: On Mon, 18 Jul 2005, Gordon Ross wrote: I've got an OpneBSD 3.7 machine (no patches - just the standard 3.7 CD install) running under VMWare GSX Server V3.1 Today, the machine had stopped with a panic. I did a "trace" and "ps" as per the instructions. Below is the result of these extracted from /var/adm/messages after I rebooted the machine. Is there anything else I should provide ? Anything else I should do if it happens again ? running out of memeory is an unsupported configuration. buy some more.
Re: Kernel Panic in 3.7
On Tue, 19 Jul 2005, Gordon Ross wrote: > So that's what the kernel panic really means: Out of memory ? yes and no. it means what it says, but the root cause is being out of memory. -- And that's why we're leaving California.
Re: Kernel Panic in 3.7
So that's what the kernel panic really means: Out of memory ? GTG >>> Ted Unangst <[EMAIL PROTECTED]> 19/07/2005 03:36 >>> On Mon, 18 Jul 2005, Gordon Ross wrote: > I've got an OpneBSD 3.7 machine (no patches - just the standard 3.7 CD > install) running under VMWare GSX Server V3.1 Today, the machine had stopped > with a panic. I did a "trace" and "ps" as per the instructions. Below is the > result of these extracted from /var/adm/messages after I rebooted the machine. > Is there anything else I should provide ? Anything else I should do if it > happens again ? running out of memeory is an unsupported configuration. buy some more. -- And that's why you should cast your ballot today.
Re: Kernel Panic in 3.7
On Mon, 18 Jul 2005, Gordon Ross wrote: > I've got an OpneBSD 3.7 machine (no patches - just the standard 3.7 CD > install) running under VMWare GSX Server V3.1 Today, the machine had stopped > with a panic. I did a "trace" and "ps" as per the instructions. Below is the > result of these extracted from /var/adm/messages after I rebooted the machine. > Is there anything else I should provide ? Anything else I should do if it > happens again ? running out of memeory is an unsupported configuration. buy some more. -- And that's why you should cast your ballot today.
Re: Kernel Panic in 3.7
On Tue, Jul 19, 2005 at 02:17:19AM +0200, Rico wrote: > [EMAIL PROTECTED] wrote: > >On Mon, July 18, 2005 11:31 am, Rico wrote: > > > >>You should not run OpenBSD under VMWare. > > > > > >>Runing any OS under a product like VMWare makes it hard to trust which > >>product is actually causing the errors, incl. kernel panics. > > > > > >That's ridiculous. > > No. But I trust you have full access to the source of VMWare so that you > really know what you talk about? > > Do I have access to that? No, but let the dude run OpenBSD on the exact > same hardware as before but without VMWare and lets see if the problems > still exists! > > > Sure, it adds a layer of complexity, but not much more > >than using varied hardware. > > Based on what do you state that? It not only adds a layer of complexity, > it adds a layer of tons of possible errors, which might or might not > show up. > > > > >For example, you could rewrite your statements: > > > >--- > >You should not run OpenBSD on PC clones. > > No, you could not rewrite my answer into to gobble like that. > > >That said, I've run OpenBSD on GSX 3.0, 3.1 and 3.2 on Windows, as well as > >ESX 2.1 and 2.5, without any major problems. > > Good for you. I never said you can't run it, I just said that he or > onyone should not. Unless you can provide a waranty that the kernel > panic isn't caused by VMWare. This issue has been reported in the past on real hardware. Now shut up and go away. You're creating unnecessary noise on this list for no good reason. Enough!
Re: Kernel Panic in 3.7
[EMAIL PROTECTED] wrote: On Mon, July 18, 2005 11:31 am, Rico wrote: You should not run OpenBSD under VMWare. Runing any OS under a product like VMWare makes it hard to trust which product is actually causing the errors, incl. kernel panics. That's ridiculous. No. But I trust you have full access to the source of VMWare so that you really know what you talk about? Do I have access to that? No, but let the dude run OpenBSD on the exact same hardware as before but without VMWare and lets see if the problems still exists! > Sure, it adds a layer of complexity, but not much more than using varied hardware. Based on what do you state that? It not only adds a layer of complexity, it adds a layer of tons of possible errors, which might or might not show up. For example, you could rewrite your statements: --- You should not run OpenBSD on PC clones. No, you could not rewrite my answer into to gobble like that. That said, I've run OpenBSD on GSX 3.0, 3.1 and 3.2 on Windows, as well as ESX 2.1 and 2.5, without any major problems. Good for you. I never said you can't run it, I just said that he or onyone should not. Unless you can provide a waranty that the kernel panic isn't caused by VMWare.
Re: Kernel Panic in 3.7
Bruno Delbono wrote: +++ Rico [Mon Jul 18, 2005 at 06:07:31PM +0200]: Bruno Delbono wrote: +++ Rico [Mon Jul 18, 2005 at 05:31:59PM +0200]: You should not run OpenBSD under VMWare. What makes you say that? I did explain this. Well then looking at what your wrote initially, there is no merit to your argument. There is indeed, but it depends on who reads the answer.
Re: Kernel Panic in 3.7
+++ Rico [Mon Jul 18, 2005 at 06:07:31PM +0200]: > Bruno Delbono wrote: > >+++ Rico [Mon Jul 18, 2005 at 05:31:59PM +0200]: > > > >>You should not run OpenBSD under VMWare. > > > > > >What makes you say that? > > I did explain this. Well then looking at what your wrote initially, there is no merit to your argument.
Re: Kernel Panic in 3.7
On Mon, July 18, 2005 11:31 am, Rico wrote: > You should not run OpenBSD under VMWare. > Runing any OS under a product like VMWare makes it hard to trust which > product is actually causing the errors, incl. kernel panics. That's ridiculous. Sure, it adds a layer of complexity, but not much more than using varied hardware. For example, you could rewrite your statements: --- You should not run OpenBSD on PC clones. Running any OS on a product like PC clones makes it hard to trust which product is actually causing the errors, incl. kernel panics. --- (Which is completely true...) That said, I've run OpenBSD on GSX 3.0, 3.1 and 3.2 on Windows, as well as ESX 2.1 and 2.5, without any major problems. Some things are annoying (like using X without their proprietary mouse driver) but no problems. In fact, at least the mpt driver has VMWare-specific checks, so arguably it's "supported".
Re: Kernel Panic in 3.7
Bruno Delbono wrote: +++ Rico [Mon Jul 18, 2005 at 05:31:59PM +0200]: You should not run OpenBSD under VMWare. What makes you say that? I did explain this.
Re: Kernel Panic in 3.7
+++ Rico [Mon Jul 18, 2005 at 05:31:59PM +0200]: > You should not run OpenBSD under VMWare. What makes you say that? > If you need serveral "virtual" machines, you can run OpenBSD chrooted as > many times as you need, without running it under VMWare. That simply is not true. OpenBSD runs great under VMWare. In fact, virtualization has enabled admins to have one server running several instances of Open/NetBSD and Windows 2003 EE (with exchange + AD) running fine. As for the original author, try adding more ram/swap to the GSX server and see if you can reproduce the crash
Re: Kernel Panic in 3.7
You should not run OpenBSD under VMWare. If you need serveral "virtual" machines, you can run OpenBSD chrooted as many times as you need, without running it under VMWare. Runing any OS under a product like VMWare makes it hard to trust which product is actually causing the errors, incl. kernel panics. Rico. Gordon Ross wrote: I've got an OpneBSD 3.7 machine (no patches - just the standard 3.7 CD install) running under VMWare GSX Server V3.1 Today, the machine had stopped with a panic. I did a "trace" and "ps" as per the instructions. Below is the result of these extracted from /var/adm/messages after I rebooted the machine. Jul 18 13:17:55 mx3 /bsd: panic: kernel diagnostic assertion "uvmexp.swpgonly <= uvmexp.swpages" failed: file "/usr/src/sys/uvm/uvm_pdaemon.c", line 581 Jul 18 13:17:56 mx3 /bsd: Stopped atDebugger+0x4: leave Jul 18 13:17:56 mx3 /bsd: RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! Jul 18 13:17:56 mx3 /bsd: DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! Jul 18 13:17:56 mx3 /bsd: ddb> Debugger(d0563130,a264,e3807e3c,d099f338,8a) at Debugger+0x4 Jul 18 13:17:56 mx3 /bsd: panic(d04dea60,d04aff97,d04f5600,d04f6e20,245) at panic+0x63 Jul 18 13:17:56 mx3 /bsd: tablefull(d04aff97,d04f6e20,245,d04f5600,d0563130) at tablefull Jul 18 13:17:56 mx3 /bsd: uvm_aiodone_daemon(d05ca308,d9a5,e3807f6c,d0307617) at uvm_aiodone_daemon+0x2c9 Jul 18 13:17:56 mx3 /bsd: uvm_aiodone_daemon(e66e,488c,d0100bde,d60863d8,d0306b18) at uvm_aiodone_daemon+0x9f8 Jul 18 13:17:56 mx3 /bsd: uvm_pageout(d60863d8) at uvm_pageout+0xc0 Jul 18 13:17:56 mx3 /bsd: Bad frame pointer: 0xd06d3ed8 Jul 18 13:17:56 mx3 /bsd: ddb>PID PPID PGRPUID S FLAGS WAIT COMMAND Jul 18 13:17:56 mx3 /bsd: 27067 4071 4071 1000 3 0xc0181 select exim-4.51-1 Jul 18 13:17:56 mx3 /bsd: 29661 4071 4071 1000 3 0xc0181 select exim-4.51-1 Jul 18 13:17:56 mx3 /bsd: 10755 4071 4071 1000 3 0xc0181 select exim-4.51-1 Jul 18 13:17:56 mx3 /bsd:505 4071 4071 1000 3 0xc0181 select exim-4.51-1 Jul 18 13:17:56 mx3 /bsd: 15696 4071 4071 1000 3 0xc0181 select exim-4.51-1 Jul 18 13:17:56 mx3 /bsd: 10625 4071 4071 1000 3 0xc0181 select exim-4.51-1 Jul 18 13:17:56 mx3 /bsd: 24014 4071 4071 1000 3 0xc0181 select exim-4.51-1 Jul 18 13:17:56 mx3 /bsd: 7796 4071 4071 1000 3 0xc0181 select exim-4.51-1 Jul 18 13:17:56 mx3 /bsd: 1680 4071 4071 1000 3 0xc0181 select exim-4.51-1 Jul 18 13:17:56 mx3 /bsd: 24147 4071 4071 1000 3 0xc0181 select exim-4.51-1 Jul 18 13:17:56 mx3 /bsd: 19545 4071 4071 1000 3 0xc0185 poll exim-4.51-1 Jul 18 13:17:56 mx3 /bsd: 11108 4071 4071 1000 3 0xc0185 select exim-4.51-1 Jul 18 13:17:56 mx3 /bsd: 9971 14302 14302 0 2 0x104 perl Jul 18 13:17:56 mx3 /bsd: 16342 14302 14302 0 2 0x104 perl Jul 18 13:17:56 mx3 /bsd: 15237 14302 14302 0 2 0x104 perl Jul 18 13:17:56 mx3 /bsd: 28206 14302 14302 0 2 0x104 perl Jul 18 13:17:56 mx3 /bsd: 15245 14302 14302 0 2 0x104 perl Jul 18 13:17:56 mx3 /bsd: 11698 4071 4071 1000 2 0xc0105 exim-4.51-1 Jul 18 13:17:56 mx3 /bsd: 17267 1 17267 0 3 0x4082 ttyin getty Jul 18 13:17:56 mx3 /bsd: 4662 1 4662 0 3 0x4082 ttyin getty Jul 18 13:17:56 mx3 /bsd: 25305 1 25305 0 3 0x4082 ttyin getty Jul 18 13:17:56 mx3 /bsd: 14302 1 14302 0 30x80 pause perl Jul 18 13:17:56 mx3 /bsd: 4071 1 4071 1000 3 0x40184 select exim-4.51-1 Jul 18 13:17:56 mx3 /bsd: 2380 1 2380 0 3 0x4082 ttyin getty Jul 18 13:17:56 mx3 /bsd: 26708 1 26708 0 3 0x4082 ttyin getty Jul 18 13:17:56 mx3 /bsd: 15247 1 15247 0 30x80 select cron Jul 18 13:17:56 mx3 /bsd: 5775 1 5775 0 3 0x180 select inetd Jul 18 13:17:56 mx3 /bsd: 16689 1 16689 0 30x84 poll ntpd Jul 18 13:17:56 mx3 /bsd: 3246 1 18125 83 3 0x186 poll ntpd Jul 18 13:17:56 mx3 /bsd: 19049 13402 13402 73 3 0x184 poll syslogd Jul 18 13:17:56 mx3 /bsd: 13402 1 13402 0 30x80 netio syslogd Jul 18 13:17:56 mx3 /bsd: 9 0 0 0 30x100204 crypto_wa crypto Jul 18 13:17:56 mx3 /bsd: 8 0 0 0 30x100204 aiodo
Kernel Panic in 3.7
I've got an OpneBSD 3.7 machine (no patches - just the standard 3.7 CD install) running under VMWare GSX Server V3.1 Today, the machine had stopped with a panic. I did a "trace" and "ps" as per the instructions. Below is the result of these extracted from /var/adm/messages after I rebooted the machine. Jul 18 13:17:55 mx3 /bsd: panic: kernel diagnostic assertion "uvmexp.swpgonly <= uvmexp.swpages" failed: file "/usr/src/sys/uvm/uvm_pdaemon.c", line 581 Jul 18 13:17:56 mx3 /bsd: Stopped atDebugger+0x4: leave Jul 18 13:17:56 mx3 /bsd: RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! Jul 18 13:17:56 mx3 /bsd: DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! Jul 18 13:17:56 mx3 /bsd: ddb> Debugger(d0563130,a264,e3807e3c,d099f338,8a) at Debugger+0x4 Jul 18 13:17:56 mx3 /bsd: panic(d04dea60,d04aff97,d04f5600,d04f6e20,245) at panic+0x63 Jul 18 13:17:56 mx3 /bsd: tablefull(d04aff97,d04f6e20,245,d04f5600,d0563130) at tablefull Jul 18 13:17:56 mx3 /bsd: uvm_aiodone_daemon(d05ca308,d9a5,e3807f6c,d0307617) at uvm_aiodone_daemon+0x2c9 Jul 18 13:17:56 mx3 /bsd: uvm_aiodone_daemon(e66e,488c,d0100bde,d60863d8,d0306b18) at uvm_aiodone_daemon+0x9f8 Jul 18 13:17:56 mx3 /bsd: uvm_pageout(d60863d8) at uvm_pageout+0xc0 Jul 18 13:17:56 mx3 /bsd: Bad frame pointer: 0xd06d3ed8 Jul 18 13:17:56 mx3 /bsd: ddb>PID PPID PGRPUID S FLAGS WAIT COMMAND Jul 18 13:17:56 mx3 /bsd: 27067 4071 4071 1000 3 0xc0181 select exim-4.51-1 Jul 18 13:17:56 mx3 /bsd: 29661 4071 4071 1000 3 0xc0181 select exim-4.51-1 Jul 18 13:17:56 mx3 /bsd: 10755 4071 4071 1000 3 0xc0181 select exim-4.51-1 Jul 18 13:17:56 mx3 /bsd:505 4071 4071 1000 3 0xc0181 select exim-4.51-1 Jul 18 13:17:56 mx3 /bsd: 15696 4071 4071 1000 3 0xc0181 select exim-4.51-1 Jul 18 13:17:56 mx3 /bsd: 10625 4071 4071 1000 3 0xc0181 select exim-4.51-1 Jul 18 13:17:56 mx3 /bsd: 24014 4071 4071 1000 3 0xc0181 select exim-4.51-1 Jul 18 13:17:56 mx3 /bsd: 7796 4071 4071 1000 3 0xc0181 select exim-4.51-1 Jul 18 13:17:56 mx3 /bsd: 1680 4071 4071 1000 3 0xc0181 select exim-4.51-1 Jul 18 13:17:56 mx3 /bsd: 24147 4071 4071 1000 3 0xc0181 select exim-4.51-1 Jul 18 13:17:56 mx3 /bsd: 19545 4071 4071 1000 3 0xc0185 poll exim-4.51-1 Jul 18 13:17:56 mx3 /bsd: 11108 4071 4071 1000 3 0xc0185 select exim-4.51-1 Jul 18 13:17:56 mx3 /bsd: 9971 14302 14302 0 2 0x104 perl Jul 18 13:17:56 mx3 /bsd: 16342 14302 14302 0 2 0x104 perl Jul 18 13:17:56 mx3 /bsd: 15237 14302 14302 0 2 0x104 perl Jul 18 13:17:56 mx3 /bsd: 28206 14302 14302 0 2 0x104 perl Jul 18 13:17:56 mx3 /bsd: 15245 14302 14302 0 2 0x104 perl Jul 18 13:17:56 mx3 /bsd: 11698 4071 4071 1000 2 0xc0105 exim-4.51-1 Jul 18 13:17:56 mx3 /bsd: 17267 1 17267 0 3 0x4082 ttyin getty Jul 18 13:17:56 mx3 /bsd: 4662 1 4662 0 3 0x4082 ttyin getty Jul 18 13:17:56 mx3 /bsd: 25305 1 25305 0 3 0x4082 ttyin getty Jul 18 13:17:56 mx3 /bsd: 14302 1 14302 0 30x80 pause perl Jul 18 13:17:56 mx3 /bsd: 4071 1 4071 1000 3 0x40184 select exim-4.51-1 Jul 18 13:17:56 mx3 /bsd: 2380 1 2380 0 3 0x4082 ttyin getty Jul 18 13:17:56 mx3 /bsd: 26708 1 26708 0 3 0x4082 ttyin getty Jul 18 13:17:56 mx3 /bsd: 15247 1 15247 0 30x80 select cron Jul 18 13:17:56 mx3 /bsd: 5775 1 5775 0 3 0x180 select inetd Jul 18 13:17:56 mx3 /bsd: 16689 1 16689 0 30x84 poll ntpd Jul 18 13:17:56 mx3 /bsd: 3246 1 18125 83 3 0x186 poll ntpd Jul 18 13:17:56 mx3 /bsd: 19049 13402 13402 73 3 0x184 poll syslogd Jul 18 13:17:56 mx3 /bsd: 13402 1 13402 0 30x80 netio syslogd Jul 18 13:17:56 mx3 /bsd: 9 0 0 0 30x100204 crypto_wa crypto Jul 18 13:17:56 mx3 /bsd: 8 0 0 0 30x100204 aiodoned aiodoned Jul 18 13:17:56 mx3 /bsd: 7 0 0 0 30x100204 syncer update Jul 18 13:17:56 mx3 /bsd: 6 0 0 0 30x100204 cleaner cleaner Jul 18 13:17:56 mx3 /bsd: 5 0 0 0 30x100204 reaper r
panic in 3.7 part II
This is the complete output of the panic with the trace and ps. I had to send it untill today because it broke again in this morning. Regards and thanks. ~panic: pool_get(mclpl): free list modified: magic=deaf; page 0xd3b38000; item addr 0xd3b38000 Sropped at Debuger+0x4: leave RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! ddb> trace Debugger(d05704e0,d05b7c40,d3b32400,d3b30800,d05b7d20) at Debugger+0x4 panic(d04de400,d04e0369,deaf,d3b3,d3b30800) at panic+0x63 pool_get(d05b7d20, 0,30, d3b32400,e)at pool_get+0x315 xl_newbuf(d0948800,d0948c58,d3b32400,d06d3e2c) at xl_newbuf+0xa5 xl_rxeof(d0948800,0,ad38,38ad1d,1)at xl_rxeof+0x1c6 xl_inrt(d0948800) at xl_intr+0x12b Xrecurse_legacy11() at Xrecurse_legacy11+0x8a - - -interrupt - - - idle_loop(d0650058,10,0,0,8000) at idle_loop+0x21 bpendtsleep(d05b2300,4,d04f59f1,0,0,d02fd6e4,8,202)at bpendtsleep uvm_scheduler(d05b22f8,3,0,d04afcec,7ec) at uvm_scheduler+0x6b check_console(0,0,0,0,0) at check_console ddb> ps PID PPIDPGRPUID S FLAGS WAITCOMMAND 4493261744930 3 0x4086 ttyin ksh 81371 81370 3 0x4086 ttyin getty 17041 17040 3 0x4086 ttyin getty 16099 1 16099 0 3 0x4086 ttyin getty 78351 78350 3 0x4086 ttyin getty 26171 26170 3 0x4086 pause csh 92361 92360 3 0x84 select cron 15310 1 15310 0 3 0x40184 select sendmail 14715 1 14715 0 3 0x84 select sshd 12116 1 12116 0 3 0x184 select inetd 26226 1575157573 3 0x184 pollsyssloge 15751 15750 3 0x84 netio syslogd 11 0 0 0 3 0x100204 crypto_wa crypto 10 0 0 0 3 0x100204 aiodonedaiodoned 9 0 0 0 3 0x100204 syncer update 8 0 0 0 3 0x100204 cleaner cleaner 7 0 0 0 3 0x100204 reaper reaper 6 0 0 0 3 0x100204 pgdaemonpagedaemon 5 0 0 0 3 0x100204 usbtsk usbtask 4 0 0 0 3 0x100204 usbevt usb0 3 0 0 0 3 0x100204 apmev apm0 2 0 0 0 3 0x100204 kmalloc kmthread 1 0 0 0 3 0x100204 waitinit 0 1 0 0 3 0x100204 scheduler swapper __ Correo Yahoo! Espacio para todos tus mensajes, antivirus y antispam !gratis! Regmstrate ya - http://correo.yahoo.com.mx/
Re: panic in 3.7
On 2005/07/01 13:34:25, Rafael Morales wrote: > Hi list. > > I have a pc (Dell Optiplex) with openbsd 3.7, which > will be firewall, but in this morning I found my pc > with this error message: > > ~panic: pool_get(mclpl): free list modified: > magic=deaf; page 0xd3b38000; > item addr 0xd3b38000 > Sropped at Debuger+0x4: leave 'Sropped' and 'Debuger'? Very odd. Is this a mis-paste or genuine output? If it's genuine, I'd be looking at hardware problems first...(run memtest?) > RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN > REPORTING THIS PANIC! > DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING > THAT INFORMATION! Surely, the above speaks for itself?
Re: panic in 3.7
On Fri, Jul 01, 2005 at 01:34:25PM -0500, Rafael Morales wrote: :RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN :REPORTING THIS PANIC! :DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING :THAT INFORMATION!
panic in 3.7
Hi list.
I have a pc (Dell Optiplex) with openbsd 3.7, which
will be firewall, but in this morning I found my pc
with this error message:
~panic: pool_get(mclpl): free list modified:
magic=deaf; page 0xd3b38000;
item addr 0xd3b38000
Sropped at Debuger+0x4: leave
RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN
REPORTING THIS PANIC!
DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING
THAT INFORMATION!
ddb>
This is my dmesg:
OpenBSD 3.7 (GENERIC) #0: Tue Jun 28 13:13:45 CDT 2005
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium III ("GenuineIntel" 686-class) 930
MHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real mem = 132489216 (129384K)
avail mem = 114380800 (111700K)
using 1642 buffers containing 6725632 bytes (6568K) of
memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(00) BIOS, date 03/07/01,
BIOS32 rev. 0 @ 0xfda74
apm0 at bios0: Power Management spec V1.2
apm0: AC on, battery charge unknown
pcibios0 at bios0: rev 2.1 @ 0xf/0x1
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf2f30/192
(10 entries)
pcibios0: PCI Interrupt Router at 000:31:0 ("Intel
82371FB ISA" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0xc000 0xcc000/0x800
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82810E" rev 0x03
vga1 at pci0 dev 1 function 0 "Intel 82810E Graphics"
rev 0x03: aperture at 0xf800, size 0x400
wsdisplay0 at vga1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
ppb0 at pci0 dev 30 function 0 "Intel 82801AA
Hub-to-PCI" rev 0x02
pci1 at ppb0 bus 1
xl0 at pci1 dev 8 function 0 "3Com 3c905C 100Base-TX"
rev 0x74: irq 11, address 00:01:02:bf:54:56
bmtphy0 at xl0 phy 24: Broadcom 3C905C internal PHY,
rev. 6
xl1 at pci1 dev 9 function 0 "3Com 3c905 100Base-TX"
rev 0x00: irq 10, address 00:60:08:52:d3:06
nsphy0 at xl1 phy 24: DP83840 10/100 PHY, rev. 1
"AT&T/Lucent LTMODEM" rev 0x00 at pci1 dev 11 function
0 not configured
ichpcib0 at pci0 dev 31 function 0 "Intel 82801AA LPC"
rev 0x02
pciide0 at pci0 dev 31 function 1 "Intel 82801AA IDE"
rev 0x02: DMA, channel 0 wired to compatibility,
channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA, 19092MB, 39102336 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 4
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: SCSI0 5/cdrom removable
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
uhci0 at pci0 dev 31 function 2 "Intel 82801AA USB"
rev 0x02: irq 9
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00,
addr 1
uhub0: 2 ports with 2 removable, self powered
"Intel 82801AA SMBus" rev 0x02 at pci0 dev 31 function
3 not configured
isa0 at ichpcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0 (mux 1 ignored for console): console
keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
midi0 at pcppi0:
sysbeep0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte
fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
biomask f36d netmask ff6d ttymask ffef
pctr: 686-class user-level performance counters
enabled
mtrr: Pentium Pro MTRR support
dkcsum: wd0 matched BIOS disk 80
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302
WARNING: / was not properly unmounted
--
Thanks for your help
