Console Upgrade from 1.2 Release Embeded -> 1.2.1 BETA Embeded [Now Working]
-
Well she ran solid for four hours then locked up completely! :-\
I have had to drop back to 1.2-Release to remain stable until I can do some more testing. If its gunna take 4 hours each time it could take a while.
The hardware is know good and runs fine on 1.2 so this must be a problem with drivers in v7.0 or the fact that I had to use the 'full' update on an embedded install.
As I am running embedded no log files exist as to why the lockup occurred. -
Unfortunately last night I had another lockup but this time it lasted a full week before the lockup occurred, so I have dropped back once again to 1.2-RELEASE until at least someone else reports a lockup and I can compare notes.
-
Can you even give details about your hardware i am not seeing anywhere!
Ermal
-
A Jetway J7F4K 1.2Ghz + 1Gb Ram
http://www.jetway.com.tw/jw/ipcboard_view.asp?productid=279&proname=J7F4K1G2E
- a D-Link DFE-580TX Quad NIC PCI Card,
http://linitx.com/viewproduct.php?prodid=10393
Together run like an absolute dream under 1.2-Release embedded but has locked up twice under two different builds of 1.2.1 BETA.
I will run for a month on 1.2 to make sure a fault hasn't crept in but I'm sure its all fine as there is little that can go wrong really.
Cheers
-
Well 15 Day's back on 1.2-Release without error - I clearly don't have a hardware fault.
I will now try 1.2.1 again and pray it doesn't lock-up again.
-
Yet another lockup after being up for 5 days - this clearly is a compatibility problem between FreeBSD 7 and my hardware or a result of upgrading from embedded 1.2 to 1.2.1-BETA with the FULL update.
To try and rule out FreeBSD 7, I am now reluctantly going back to a non-embedded full install of 1.2.1 to a CF II Microdrive.
-
Can you be more specific on the meaning of the 'lockup' word?
-
I mean lockup in the old fashioned sence of the word:
-
No network activity on any interface (I have four active, 2 WAN, 1 Wireless DMZ and 1 LAN)
-
No serial console access.
-
No controlled halt when the power button is depressed.
I set up remote sys logging in the hope I may catch something as when it happens I loose any history for obvious reasons but alas it didn't show anything other than the time it locked up and the following reboot when I got home from work:
2008-08-12 16:43:44 Local0.Info 192.168.100.254 Aug 12 16:43:44 pf: 86. 848637 rule 142/0(match): pass in on ste1: (tos 0x0, ttl 110, id 27768, offset 0, flags [DF], proto TCP (6), length 48) 212.92.4.173.64893 > 192.168.100.5.25: [|tcp]
2008-08-12 16:44:34 Local0.Info 192.168.100.254 Aug 12 16:44:34 pf: 49. 779067 rule 142/0(match): pass in on ste1: (tos 0x0, ttl 114, id 37811, offset 0, flags [DF], proto TCP (6), length 48) 59.182.35.69.7099 > 192.168.100.5.25: [|tcp]
2008-08-12 16:45:17 Local0.Info 192.168.100.254 Aug 12 16:45:17 pf: 43. 584296 rule 142/0(match): pass in on ste1: (tos 0x0, ttl 114, id 6379, offset 0, flags [DF], proto TCP (6), length 48) 59.182.35.69.7244 > 192.168.100.5.25: [|tcp]
2008-08-12 16:46:12 Local0.Info 192.168.100.254 Aug 12 16:46:12 pf: 54. 506486 rule 142/0(match): pass in on ste1: (tos 0x0, ttl 114, id 48361, offset 0, flags [DF], proto TCP (6), length 48) 59.182.35.69.8318 > 192.168.100.5.25: [|tcp]
2008-08-12 16:47:14 Local0.Info 192.168.100.254 Aug 12 16:47:14 pf: 62. 320660 rule 142/0(match): pass in on ste1: (tos 0x0, ttl 117, id 50815, offset 0, flags [DF], proto TCP (6), length 48) 88.156.199.178.2415 > 192.168.100.5.25: [|tcp]
2008-08-12 16:48:23 Local0.Info 192.168.100.254 Aug 12 16:48:23 pf: 69. 379247 rule 142/0(match): pass in on ste1: (tos 0x0, ttl 111, id 65277, offset 0, flags [DF], proto TCP (6), length 48) 86.110.187.14.4613 > 192.168.100.5.25: [|tcp]
2008-08-12 16:48:34 Local0.Info 192.168.100.254 Aug 12 16:48:34 pf: 10. 291989 rule 142/0(match): pass in on ste1: (tos 0x0, ttl 115, id 23925, offset 0, flags [DF], proto TCP (6), length 48) 89.169.159.198.19732 > 192.168.100.5.25: [|tcp]
2008-08-12 16:49:36 Local0.Info 192.168.100.254 Aug 12 16:49:36 pf: 62. 583301 rule 142/0(match): pass in on ste1: (tos 0x0, ttl 115, id 62019, offset 0, flags [DF], proto TCP (6), length 48) 89.169.159.198.20202 > 192.168.100.5.25: [|tcp]
2008-08-12 16:51:43 Local0.Info 192.168.100.254 Aug 12 16:51:43 pf: 126. 487669 rule 142/0(match): pass in on ste1: (tos 0x0, ttl 115, id 1366, offset 0, flags [DF], proto TCP (6), length 48) 89.169.159.198.21415 > 192.168.100.5.25: [|tcp]
2008-08-12 17:09:17 Local0.Info 192.168.100.254 Aug 12 17:09:16 pf: 1053. 663179 rule 142/0(match): pass in on ste1: (tos 0x0, ttl 105, id 16896, offset 0, flags [none], proto TCP (6), length 44) 116.41.71.126.55633 > 192.168.100.5.25: [|tcp]
2008-08-12 18:08:57 Daemon.Info 192.168.100.254 Aug 12 18:08:51 dhclient[275]: DHCPDISCOVER on ste0 to 255.255.255.255 port 67 interval 2
2008-08-12 18:08:57 Auth.Info 192.168.100.254 Aug 12 18:08:51 sshd[300]: Server listening on :: port 22.
2008-08-12 18:08:57 Auth.Info 192.168.100.254 Aug 12 18:08:51 sshd[300]: Server listening on 0.0.0.0 port 22.
2008-08-12 18:08:57 Auth.Error 192.168.100.254 Aug 12 18:08:51 sshlockout[302]: sshlockout starting up
2008-08-12 18:08:58 Daemon.Info 192.168.100.254 Aug 12 18:08:52 dhclient[275]: DHCPDISCOVER on ste0 to 255.255.255.255 port 67 interval 3My current working theory is that there is a process that goes CPU bound and I stops me getting back in but then on a reboot I would expect the CPU temp to be a lot higher than 42 degrees after running at %100 for over an hour.
Cheers
-
-
I am thinking this might be a driver issue with ste on RELENG_7_0 FreeBSD.
-
:o Noooooooooo! :'( I can't write my router off just yet, I've only just finished building it.
Joke's aside, if 'patches' are released for FreeBSD 7 will the latest ones be incorporated in to 1.2.1-Release? or is the version of 7 you start with the version of 7 you go to press with? i.e. will the version of freeBSD 7 that comes with 1.2.1 be the same as the one that comes with 1.3.
Regards
EDIT: PS, would the D-link driver going AWOL also lock-up my on-board 1Gb Realtek?
