has anyone seen this kernel panic before?

both crashed. - Now we are just running the BACKUP (we didn't hookup MASTER to the network again because these are production FWs) Below the pictures of the traceback of the kernel panic: http://img61.imageshack.us/img61/1840/photo0615060079iq.jpg http://img83.imageshack.us/img83/9694/photo061506

Re: Kernel panic ... Unknown source ...

On 2006/06/12 08:24, Jirtme Loyet wrote: > > Hey, if this problem turns out to expose a true logic bug in > > OpenBSD, go ahead, find it, show us, and get credit for the > > fix. But if "everytime the panic is different", it sounds > > like things are Just Plain Broke on the system, if a BIOS

Re: Kernel panic ... Unknown source ...

On 6/12/06, Jirtme Loyet <[EMAIL PROTECTED]> wrote: > Scott Plumlee wrote: > Anyone who hasn't seen a broken piece of HW that works fine > with X but not Y is new to the game. Anyone who trusts a HW > diagnostic to "give" > them the answer is really, really new to the game. > > By themselves, di

Re: Kernel panic ... Unknown source ...

G support and > set ddb.panic > >> to 0 in sysctl.conf so that it's rebooting automaticly. > But no kernel > >> dump is made after a kernel panic. I searched on the web without > >> finding a solution. > >> > >> Everytime the kernel panic i

Re: Kernel panic ... Unknown source ...

automaticly. But no kernel dump is made after a kernel panic. I searched on the web without finding a solution. Everytime the kernel panic is different. I tried the -current (and also 3.8). The result is nearly the same: no more kernel panics but the system freeze but it's still responding to

Re: Kernel panic ... Unknown source ...

dump is made after a kernel panic. I searched on the web without finding a solution. Everytime the kernel panic is different. I tried the -current (and also 3.8). The result is nearly the same: no more kernel panics but the system freeze but it's still responding to the ping. As I said before

Kernel panic ... Unknown source ...

Hello, My OpenBSD 3.9-stable Box is quite unstable. I don't have physical access to my box so I can't debug it directly. I've recompiled a GENERIC kernel with DEBUG support and set ddb.panic to 0 in sysctl.conf so that it's rebooting automaticly. But no kernel dump is made aft

Stange lockups on OpenBSD/Sparc64 and kernel panic

online surfing , etc). Today while I was booting i had a kernel panic. I'm suspecting that this is a hardware problem, but I'm hoping someone has a better idea of what is happening (or even what part is failing). Testing using OpenBoot says that all tests are passing ok. The me

Re: Kernel panic -- Processor State .. PState

ECTED] > > De la part de Jerome Loyet > > Envoye : mardi 30 mai 2006 23:28 > > A : misc@openbsd.org > > Objet : Re: Kernel panic "smashed stack in ufs_makeinode" > > > > In fact this is not just a problem with my machine. > > I bought a dedic

Re: Kernel panic -- Processor State .. PState

On 2006/06/01 01:55, Jerome Loyet wrote: > The only difference between the 2 kind of machine is about the BIOS version > installed. > > The differences between the two BIOS are: > - The vcore has been updated to +0.1v > - Pstate has been removed > > The second release of the BIOS seams to be b

Re: Kernel panic -- Processor State .. PState

] [mailto:[EMAIL PROTECTED] > De la part de Jerome Loyet > Envoye : mardi 30 mai 2006 23:28 > A : misc@openbsd.org > Objet : Re: Kernel panic "smashed stack in ufs_makeinode" > > In fact this is not just a problem with my machine. > I bought a dedicated server (www.dedibox

Re: Kernel panic "smashed stack in ufs_makeinode"

On 2006/05/30 23:28, Jirtme Loyet wrote: > In fact this is not just a problem with my machine. > I bought a dedicated server (www.dedibox.fr). I installed OpenBSD 3.9 on it. > Other people did exactly the same and the have the same problem. That means it's less likely to be a failure particular to

Re: Kernel panic "smashed stack in ufs_makeinode"

? > -Message d'origine- > De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > De la part de Spruell, Darren-Perot > Envoyi : mardi 30 mai 2006 23:06 > @ : misc@openbsd.org > Objet : Re: Kernel panic "smashed stack in ufs_makeinode" > > From: [EMAIL PR

Re: Kernel panic "smashed stack in ufs_makeinode"

From: [EMAIL PROTECTED] > I got another kernel panic: free: non-malloced addr 0x10 type temp > > Many programs seg fault with "Program terminated with signal 11, > Segmentation fault" > > The memory has been tested with memtest86. > > Any idees? I've

Re: Kernel panic "smashed stack in ufs_makeinode"

On 2006/05/30 20:39, Jerome Loyet wrote: > I got another kernel panic: free: non-malloced addr 0x10 type temp > > Many programs seg fault with "Program terminated with signal 11, > Segmentation fault" > > The memory has been tested with memtest86. > > Any id

Re: Kernel panic "smashed stack in ufs_makeinode"

I got another kernel panic: free: non-malloced addr 0x10 type temp Many programs seg fault with "Program terminated with signal 11, Segmentation fault" The memory has been tested with memtest86. Any idees? > -Message d'origine- > De : [EMAIL PROTECTED] [mailto:[E

Kernel panic "smashed stack in ufs_makeinode"

Hello, I've just installed OpenBSD 3.9 and I've stranged behaviours. I've sometimes some seg fault, sometimes the system crashed with or without a panic in dmesg. I got once: --- panic: smashed stack in ufs_makeinode Stopped at It's a dedicated server, I don't have access to the console.

Re: Newer snaps throw kernel panic...

On Mon, 22 May 2006, Miod Vallat wrote: I've got a server that has been running fine with a bsd.mp kernel from Apr 23. I took it up to -current on May 19th and it threw a panic on boot. I booted from the old kernel and it was fine, so I cvsuped the source and built -current again. Same thing.

Re: Newer snaps throw kernel panic...

> I've got a server that has been running fine with a bsd.mp kernel > from Apr 23. I took it up to -current on May 19th and it threw a panic on > boot. I booted from the old kernel and it was fine, so I cvsuped the > source and built -current again. Same thing. This should be fixed with sys/

Re: Raid 1 and 2 Disks: kernel panic with "init: not found" when reboot into broken mirror

On 5/20/06, Joachim Schipper <[EMAIL PROTECTED]> wrote: > >... >Kernelized RAIDFrame activated >dkcsum wd0 matches BIOS drive 0x80 >dkcsum wd1 matches BIOS drive 0x81 >root on wd1a >rootdev=0x10 rrootdev=0x320 rawdev=0x312 >warning: /dev/console does not exist >ini

Newer snaps throw kernel panic...

0,0,0,0,0) at main+0x372) Booting from a /bsd single processor throws the same kernel panic. Here is the dmesg from the last good kernel: OpenBSD 3.9-current (GENERIC.MP) #0: Sun Apr 23 10:14:48 MDT 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel Pentium III (

Re: Raid 1 and 2 Disks: kernel panic with "init: not found" when reboot into broken mirror

On Wed, May 17, 2006 at 12:39:57AM +0200, ip wrote: > On 5/14/06, Joachim Schipper <[EMAIL PROTECTED]> wrote: > > > > >While wd1a does have a kernel, it does not have a proper root filesystem > >- for instance, no /dev directory, or more specifically no /dev/console. > > > >Fix this, and also have

Re: Raid 1 and 2 Disks: kernel panic with "init: not found" when reboot into broken mirror

On 5/14/06, Joachim Schipper <[EMAIL PROTECTED]> wrote: While wd1a does have a kernel, it does not have a proper root filesystem - for instance, no /dev directory, or more specifically no /dev/console. Fix this, and also have a look at daily(8) which documents the altroot mechanism, which is q

Re: Raid 1 and 2 Disks: kernel panic with "init: not found" when reboot into broken mirror

On Sat, May 13, 2006 at 01:38:40PM +0200, ip wrote: > Hello misc, > > I spent two days to read man and how-tos, but today I don't succeed > again to make raid 1 to work. > I want to install openbsd 3.9 on two ide disks (wd0,wd1) of 10 gb with > raidframe raid 1. > Following the main steps that I h

Raid 1 and 2 Disks: kernel panic with "init: not found" when reboot into broken mirror

Hello misc, I spent two days to read man and how-tos, but today I don't succeed again to make raid 1 to work. I want to install openbsd 3.9 on two ide disks (wd0,wd1) of 10 gb with raidframe raid 1. Following the main steps that I have executed: 1. regular installation of openbsd 3.9 on wd0 2. co

Re: kernel panic in ieee80211_release_node while using ral0 ("Ralink RT2561S")

Hello, I'm happy to write that after upgrading to 3.9-current (today's sources) the problem goes away and now I'm able to either associate or to provide host AP. Thanks to the developer who fixed this issue! Karel On Sun, 26 Mar 2006, Karel Gardas wrote: Hello, someone notified me to als

Re: kernel panic in ieee80211_release_node while using ral0 ("Ralink RT2561S")

Hello, someone notified me to also show panic message. Sorry for this omission. Whole console output looks: kernel: page fault trap, code=0 Stopped at ieee80211_release_nod+0x16:movl 0x10(%esi),%ebx when I do `show panic' I get: ddb> show panic the kernel did not panic ddb> I hope

kernel panic in ieee80211_release_node while using ral0 ("Ralink RT2561S")

Hello, I've hit following kernel panic while trying to use my Ralink chipset based WiFi card on OpenBSD 3.9/i386, which I installed from snapshots on March 23: The simple test is `ifconfig -M ral0', just repeat it several times (I've got crash till third attempt from three

Re: kernel panic

Joe Advisor wrote: ... Can anybody provide any insight for me as to what I might be doing wrong? I am not sure where to be even begin to debug. Thanks in advance. http://www.openbsd.org/faq/faq2.html#Bugs Nick.

Re: Sporadic kernel panic booting old i386 hardware, 3.7 GENERIC

On Thu, Mar 23, 2006 at 09:31:38AM +1030, Damon McMahon wrote: > Greetings, re > For the second time in a week the following kernel panic has occured > on boot. In between these two events the firewall has booted many > times without issue. > > booting hd0a:/bsd: 4686336+945680

kernel panic

I have several machines that periodically kernel panic. Many times, the kernel panics at boot... as rc is running, it will panic. Occassionally, the machines will make it past boot, but then randomly panic after several hours of normal operation. Here is the message that appears on the console

Re: Sporadic kernel panic booting old i386 hardware, 3.7 GENERIC

Thanks to all who've responded. Through google I eventually found source code for memtester 4.0.5 at http://pyropus.ca/software/memtester/ . Compiled out of the box, however my RAM tested all OK which leaves me back to where i started... Any other suggestions? At the ddb> prompt is there anythih

Re: Sporadic kernel panic booting old i386 hardware, 3.7 GENERIC

On 3/22/06, Damon McMahon <[EMAIL PROTECTED]> wrote: > Thanks, Stuart. > > Hmmm... the machine is only connected by a serial console. Does anyone > know if OpenBSD-compatible source code for memtest86 is available? The > linux code doesn't compile on OpenBSD, and I'd like to be able to > interact w

Re: Sporadic kernel panic booting old i386 hardware, 3.7 GENERIC

Thanks, Stuart. Hmmm... the machine is only connected by a serial console. Does anyone know if OpenBSD-compatible source code for memtest86 is available? The linux code doesn't compile on OpenBSD, and I'd like to be able to interact with it via a serial console, preferably. Cheers, Damon On 23/0

Re: Sporadic kernel panic booting old i386 hardware, 3.7 GENERIC

Stuart Henderson wrote: On 2006/03/23 09:31, Damon McMahon wrote: Is this (very old) hardware just giving up the ghost, bad RAM (I've seen a couple of mentions in the archives pointing to this), some other component in need of replacement, or something else worth investigating further?

Re: Sporadic kernel panic booting old i386 hardware, 3.7 GENERIC

On 2006/03/23 09:31, Damon McMahon wrote: > Is this (very old) hardware just giving up the ghost, bad RAM (I've > seen a couple of mentions in the archives pointing to this), some > other component in need of replacement, or something else worth > investigating further? Memory is a fairly likely c

Sporadic kernel panic booting old i386 hardware, 3.7 GENERIC

Greetings, For the second time in a week the following kernel panic has occured on boot. In between these two events the firewall has booted many times without issue. booting hd0a:/bsd: 4686336+945680 [52+241344+223335]=0x5d08e0 entry point at 0x100120 [ using 465104 bytes of bsd ELF symbol

xSeries 335 GENERIC.MP kernel panic

Hello misc, My xSeries 335 Dual Xeon 2.0 Ghz server has kernel panic when the load is heavy. (e.g.: 4-5). OpenBSD 3.8 GENERIC.MP just installed a few minutes ago. The trace output: panic: fp_save ipi didn't Stopped at Debugger+0x4: leave ddb{0}>trace Debugger(1,d187f800,

Re: Kernel panic on fresh 3.8 amd64 after make build

Peter Philipp wrote: >> cd /usr/src >> cvs -d [EMAIL PROTECTED]:/cvs -q up -rOPENBSD_3_8 -Pd >> [...] > Thanks for the response. I reinstalled the machine. Updated the sources as indicated above and then entered "make build" It just stopped responding after a while. The last messages from the s

Re: Kernel panic on fresh 3.8 amd64 after make build

On Tue, Jan 17, 2006 at 03:02:09PM +0100, Koen Van Impe wrote: > cd /usr/src > ftp ftp://ftp.openbsd.org/pub/OpenBSD/3.8/src.tar.gz > tar zxvf src.tar.gz Should stick a -p in here as well.. > cd /usr/src > cvs -d [EMAIL PROTECTED]:/cvs -q up -rOPENBSD_3_8 -Pd > > cd /usr/src/sys/arc

Kernel panic on fresh 3.8 amd64 after make build

Hi, I get a kernel panic on a fresh 3.8 machine. As far as I can tell all the hardware is functional. The install-process went without any problem whatsover. The only commands issued after the install (upon first boot) are these : cd /usr/src ftp ftp://ftp.openbsd.org/pub/OpenBSD/3.8

Re: lockups, crashes on a Compaq Presario 5304 (Kernel PANIC, should I report?)

While fooling around with /dev/lpt0, I am able to make the GENERIC 3.7 kernel go into panic mode. Should I fill-in a report or is this a known and accepted behavior (lpt0 is connected to a hp laserjet 1100 which seem to dislike interrupt mode of operation)? Pascal On Sat, 10 Sep 2005 06:56:51

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 ran

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, > Maso

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 - jus

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

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 extrac

Re: Kernel Panic in 3.7

t 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 no

Re: Kernel Panic in 3.7

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

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 meri

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

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 grea

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. kerne

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 m

[Fwd: Re: PR 4230 -- kernel panic on pf]

Hi all, I need help to solve the problem described in the attached thread. I didn't received any reply from Brad to my last mail (12 days ago). Anyone on the list can help me. Thank you Paolo Messaggio Originale Oggetto:Re: PR 4230 -- kernel panic on pf Data:

Re: Kernel Panic

The Whole thing some how seam to be specific to this machine doing the same stuff on a an other machine (Intel SE7501WV2 Board ) does not have any of these Problems: Dmesg of the machine w/o Problems dmesg OpenBSD 3.7 (GENERIC) #6: Tue Apr 19 07:08

Re: Kernel Panic / Update

When booting the machine with bsd.mp the problem does not end up with a Kernel panic but the interface stops to transmit packets. Tcpdump works fine but I can not send out anything (checked on the switch with packet debugging ) Manon --On 5. Mai 2005 03:27:29 +0200 Manon Goo <[EMAIL PROTEC

Re: Kernel Panic / Update

I am getting the same problem with other Interfaces (on different cards) ifconfig em4 down acheron02:~ root[0]# ifconfig em4 up acheron02:~ root[0]# ping XXX.XXX.YYY.26 PING XXX.XXX.YYY.26 (XXX.XXX.YYY.26): 56 data bytes panic: pool_get(mclpl): free list modified: magic=400beef; page 0xde57f000; i

Kernel Panic

Does this look like a hardware error ? I had problems withe this machine before. Does this look like a buggy em(4) Card ? The machine is a IBM x345 Manon ifconfig em5 down acheron02:~ root[0]# ifconfig vlan vlan1124: flags=8843 mtu 1500 address: 00:04:23:9e:e6:6a vlan: 1124 par

<    1   2   3   4   5   6