Kernel Panic
-
as of snap
2.0-BETA5 (i386)
built on Mon Jan 24 18:48:13 EST 2011fix did not work.
Maybe fix was not in this build?
It should have been.
So it still crashed the exact same way, with the same panic in the same place?
-
Did notice this from both panics though.
Panic from old P4 computer:
Kernel page fault with the following non-sleepable locks held: exclusive sleep mutex em0 (EM TX Lock) r = 0 (0xc2f52580) locked @ /usr/pfSensesrc/src/sys/dev/e1000/if_lem.c:1350Panic from Soekris board:
Kernel page fault with the following non-sleepable locks held: exclusive sleep mutex vr1 (network driver) r = 0 (0xc3640aec) locked @ /usr/pfSensesrc/src/sys/dev/vr/if_vr.c:1675Is it just coincidence?
Hard to say for sure.
I just setup my ALIX and opened a ton of browser tabs and pushed a bunch of traffic through it and I managed to crash Chrome but not the router… I wish I could reproduce this.
-
as of snap
2.0-BETA5 (i386)
built on Mon Jan 24 18:48:13 EST 2011fix did not work.
Maybe fix was not in this build?
It should have been.
So it still crashed the exact same way, with the same panic in the same place?
Here is the new screen shoot of the panic.
Same symptoms, only when using openvpn
-
The key is only when you connect to OpenVPN and then after successful connection, open a browser and the page should time out and you should get disconnected from the OpenVPN connection.
-
I had ~10 browser tabs open to all kinds of sites, streaming a youtube video, and was copying a file over SMB, all over OpenVPN from a client on the WAN side of my ALIX.
Perhaps it's a bug specific to the vr chip in the Soekris.
-
If it is a specific issue to the vr chip, then why am I getting the same type of panic with the em (as I had posted above)?
-
Bad luck? :-)
The em chips hit by this are specific older chips that fall under the "legacy em" ("lem") portion of the driver code.
-
LOL, seems to be me only that has the bad hardware then.
EDIT: Did you try it with squid havp, etc. loaded on it?
-
The key is only when you connect to OpenVPN and then after successful connection, open a browser and the page should time out and you should get disconnected from the OpenVPN connection.
Note the case for me,
Once connected i would start up outlook to sync to exchange and openvpn would crash
Same goes with doing a file/folder copy from host network to openvpn client. -
The key is only when you connect to OpenVPN and then after successful connection, open a browser and the page should time out and you should get disconnected from the OpenVPN connection.
Note the case for me,
Once connected i would start up outlook to sync to exchange and openvpn would crash
Same goes with doing a file/folder copy from host network to openvpn client.Wish I could have made it as far as you vito
-
EDIT: Did you try it with squid havp, etc. loaded on it?
I haven't tried it with squid, I'll load that on next. Do you have the OpenVPN server assigned as an interface and squid listening there? Otherwise, squid wouldn't be doing anything to the traffic coming from OpenVPN
-
No I am not having squid listen to anything but the 3 different vr networks. I am just wondering if the setup may have something to do with it. Doesn't hurt to recreate it completely.
-
fair enough. I'll give it a go.
-
EDIT: Did you try it with squid havp, etc. loaded on it?
I haven't tried it with squid, I'll load that on next. Do you have the OpenVPN server assigned as an interface and squid listening there? Otherwise, squid wouldn't be doing anything to the traffic coming from OpenVPN
Jimp,
it was most likely missed in this thread, but in my original thread with this problem from 12/13
had the packages i am running. http://forum.pfsense.org/index.php/topic,31031.msg165512.html#msg165512Packages i am running:
Squid
Squid Guard
Snort
OpenVPN Export
Light Squid
AnytermIf need be, i can test by stopping Squid and such….
-
It might be worth trying without any packages. (the only one I have is OpenVPN client export) to see if it makes a difference.
One thing - for everyone seeing the panic on em(4) devices, the output from
pciconf -lvbFor the em card seen in the crash would be helpful.
-
??? JimP, I am a little confused, do you want me to type that in after the crash happens and the db comes up? If not, what would you like from the crash?
-
I have a net5501-70, a Pro 1000GT (pci), and a spare pppoe DSL line. Jim, I can set this up with openvpn if you want to test against it. I have no experience with openvpn though, so would need some guidance setting that up.
Also note that my DSL line has pretty poor sync rates right now, and occasional disconnects, which is why it's not in use :/
-
??? JimP, I am a little confused, do you want me to type that in after the crash happens and the db comes up? If not, what would you like from the crash?
Just at a normal command prompt. It will show the chip id of the em card.
-
I have a net5501-70, a Pro 1000GT (pci), and a spare pppoe DSL line. Jim, I can set this up with openvpn if you want to test against it. I have no experience with openvpn though, so would need some guidance setting that up.
Also note that my DSL line has pretty poor sync rates right now, and occasional disconnects, which is why it's not in use :/
I'll keep that in mind, though I was hoping to do it locally since that makes it a lot easier to track down…
-
It might be worth trying without any packages. (the only one I have is OpenVPN client export) to see if it makes a difference.
One thing - for everyone seeing the panic on em(4) devices, the output from
pciconf -lvbFor the em card seen in the crash would be helpful.
Will try later tonight. :)
from my system
em1@pci0:3:0:0: class=0x020000 card=0x060a15d9 chip=0x10d38086 rev=0x00 hdr=0x00
  class   = network
  subclass = ethernet
  bar [10] = type Memory, range 32, base 0xfeae0000, size 131072, enabled
  bar [18] = type I/O Port, range 32, base 0xec00, size 32, enabled
  bar [1c] = type Memory, range 32, base 0xfeadc000, size 16384, enabled
