News
:
This forum is now permanently frozen.
m0n0wall Forum
>
m0n0wall Support (English)
>
General Questions
Topic: watchdog timeout resetting
Pages: [
1
]
Topic: watchdog timeout resetting (Read 4111 times)
watchdog timeout resetting
« on: November 26, 2007, 17:41:26 »
Peter
Posts: 3
Hi list
My system is a stripped IBM Netvista running on a CF. A couple weeks ago I added an opt1 NIC Intel Pro/1000 (same as my LAN nic) to setup a DMZ. Yesterday I got around to configuring the system and all appeared be be okay. Shortly thereafter I noticed entries in my logs and the console em1: watchdog timeout resetting
Is this error being generated by M0n0, the NIC, or by the pc and how do I resolve it.
Thanks in advance.
Peter
Life is too short to wear uncomfortable shoes.
http://sneaker-groups.com/
Re: watchdog timeout resetting
« Reply #1 on: November 26, 2007, 20:39:35 »
Peter
Posts: 3
Rolling M0m0 back to Version: 1.231 seems to have fixed this issue.
Life is too short to wear uncomfortable shoes.
http://sneaker-groups.com/
Re: watchdog timeout resetting
« Reply #2 on: December 01, 2007, 20:12:51 »
cmb
Posts: 851
Sounds like a driver regression between FreeBSD 4.x and 6.x. No m0n0wall developer is going to fix this, but if you can replicate with a stock FreeBSD 6.2 or 6.3 and report to freebsd-net, it may get resolved.
There may be things you can do to fix this, it could be a BIOS bug that didn't affect the previous drivers but is now a problem so check for a BIOS update, or could be BIOS setting related (make sure PNP OS is off).
Re: watchdog timeout resetting
« Reply #3 on: December 01, 2007, 20:28:25 »
Peter
Posts: 3
Hi Chris
Thanks for the reply. For now I've turned off the NIC. I had planned on upgrading the PC so I may just do that. What have have found odd though is the problem only occurred after I put traffic through the NIC. Low traffic does not trip this error but high http traffic does.
Regards,
Peter
Life is too short to wear uncomfortable shoes.
http://sneaker-groups.com/
Pages: [
1
]