Re: [Soekris] Soekris] 4801 thats stopped responding
On Thu, Mar 29, 2007 at 05:52:08PM -0400, Tuc at T-B-O-H.NET wrote: > > Anyway, on linux I never had any problems with the watchdog, so I assume > > that the hardware watchdog works. > > > I would think the FreeBSD one works too. What I meant - read my post - is that the soekris *hardware* part of the watchdog works (the actual circuits that reset the board). I didn't say at any moment it's freebsd's fault or such. I would suspect at this moment that you do have some hw problems. Iustin ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] Dissapearing Interface on Mini-PC Slot
Hi Chuck, Sorry, sometimes I forget that not everybody has a Soekris board next to their bed (just kidding everyone). hahahaha Take care, Frank Chuck (Doc) Beaudette wrote: I will do that. I have had a reason to flash a BIOS yet, so it will be a good opportunity to get a little hands on doing that. -Original Message- From: Frank Cole [mailto:[EMAIL PROTECTED] Sent: Thursday, March 29, 2007 3:35 PM To: Chuck (Doc) Beaudette Cc: soekris-tech@lists.soekris.com Subject: Re: [Soekris] Dissapearing Interface on Mini-PC Slot Hi Chuck, A slight correction comBIOS 1.30 was relesaed a couple of days ago. I dont know yet if the fix for this issue made it into the release or not. It isnt mentioned in the changelog but maybe we'll get lucky. As I am currently without a board to test it with, please give it a try and let me know if it fixes the problem. Best Regards, Frank Chuck (Doc) Beaudette wrote: Thanks for the info...very helpful -Original Message- From: Frank Cole [mailto:[EMAIL PROTECTED] Sent: Thursday, March 29, 2007 2:20 PM To: Chuck (Doc) Beaudette Cc: soekris-tech@lists.soekris.com Subject: Re: [Soekris] Dissapearing Interface on Mini-PC Slot Hi Chuck, We've had the same issue. The problem is with the comBIOS and how it is handling the single chip Atheros chipset on the Ubiquity and other Atheros single chip designs. Our experience on average was about 1 out of 30 power cycles the cards would not be initialized properly at/just after POST though some boards seemed to be more frequent and some less frequent. We sent a couple of cards to Soekris for them to experiment with and hopefully come up with a fix for the soon to be released comBIOS 1.30 update. Keep your fingers crossed. And you can stop reseating the card, it doesnt really do anything other than put wear on the card and the slot. Been there, done that. Only thing we've found that really does the trick is to do a hard reset (ie remove power and plug it back in) to correct the issue once it manifests as soft resets from the BIOS monitor dont consistently clear the problem up. Hope it helps Frank Cole Chuck (Doc) Beaudette wrote: I have run into an intersting anomoly and wonder if anyone else has seen something similar. I am using a net4501 w/ Mikrotik kernel. I installed a Ubiquiti XR2 wireless card. When I power cycle the unit, the wireless card disappears in the interface list. If I power off the unit, reseat the wireless card and power back up, the interface returns to the list. I originally thought this was a heat issue with the card because I was originally using a Mikrotik R52 in a small case, but I have since had this happen with mutliple wireless cards (using both XR2 and Mikrotik R52) and with multiple net4501 boards in fan cooled large enclosures. Doc ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech smime.p7s Description: S/MIME Cryptographic Signature ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] Dissapearing Interface on Mini-PC Slot
I will do that. I have had a reason to flash a BIOS yet, so it will be a good opportunity to get a little hands on doing that. -Original Message- From: Frank Cole [mailto:[EMAIL PROTECTED] Sent: Thursday, March 29, 2007 3:35 PM To: Chuck (Doc) Beaudette Cc: soekris-tech@lists.soekris.com Subject: Re: [Soekris] Dissapearing Interface on Mini-PC Slot Hi Chuck, A slight correction comBIOS 1.30 was relesaed a couple of days ago. I dont know yet if the fix for this issue made it into the release or not. It isnt mentioned in the changelog but maybe we'll get lucky. As I am currently without a board to test it with, please give it a try and let me know if it fixes the problem. Best Regards, Frank Chuck (Doc) Beaudette wrote: > Thanks for the info...very helpful > > -Original Message- > From: Frank Cole [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 29, 2007 2:20 PM > To: Chuck (Doc) Beaudette > Cc: soekris-tech@lists.soekris.com > Subject: Re: [Soekris] Dissapearing Interface on Mini-PC Slot > > Hi Chuck, > > We've had the same issue. The problem is with the comBIOS and how it > is handling the single chip Atheros chipset on the Ubiquity and other > Atheros single chip designs. Our experience on average was about 1 > out of 30 power cycles the cards would not be initialized properly > at/just after POST though some boards seemed to be more frequent and some less frequent. > > We sent a couple of cards to Soekris for them to experiment with and > hopefully come up with a fix for the soon to be released comBIOS 1.30 > update. > > Keep your fingers crossed. > > And you can stop reseating the card, it doesnt really do anything > other than put wear on the card and the slot. Been there, done that. > Only thing we've found that really does the trick is to do a hard > reset (ie remove power and plug it back in) to correct the issue once > it manifests as soft resets from the BIOS monitor dont consistently clear the problem up. > > Hope it helps > > Frank Cole > > Chuck (Doc) Beaudette wrote: >> I have run into an intersting anomoly and wonder if anyone else has >> seen something similar. >> >> I am using a net4501 w/ Mikrotik kernel. I installed a Ubiquiti XR2 >> wireless card. When I power cycle the unit, the wireless card >> disappears in the interface list. If I power off the unit, reseat the >> wireless card and power back up, the interface returns to the list. >> >> I originally thought this was a heat issue with the card because I >> was originally using a Mikrotik R52 in a small case, but I have since >> had this happen with mutliple wireless cards (using both XR2 and >> Mikrotik >> R52) and with multiple net4501 boards in fan cooled large enclosures. >> >> >> >> Doc >> >> ___ >> Soekris-tech mailing list >> Soekris-tech@lists.soekris.com >> http://lists.soekris.com/mailman/listinfo/soekris-tech >> > ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] Dissapearing Interface on Mini-PC Slot
Hi Chuck, A slight correction comBIOS 1.30 was relesaed a couple of days ago. I dont know yet if the fix for this issue made it into the release or not. It isnt mentioned in the changelog but maybe we'll get lucky. As I am currently without a board to test it with, please give it a try and let me know if it fixes the problem. Best Regards, Frank Chuck (Doc) Beaudette wrote: Thanks for the info...very helpful -Original Message- From: Frank Cole [mailto:[EMAIL PROTECTED] Sent: Thursday, March 29, 2007 2:20 PM To: Chuck (Doc) Beaudette Cc: soekris-tech@lists.soekris.com Subject: Re: [Soekris] Dissapearing Interface on Mini-PC Slot Hi Chuck, We've had the same issue. The problem is with the comBIOS and how it is handling the single chip Atheros chipset on the Ubiquity and other Atheros single chip designs. Our experience on average was about 1 out of 30 power cycles the cards would not be initialized properly at/just after POST though some boards seemed to be more frequent and some less frequent. We sent a couple of cards to Soekris for them to experiment with and hopefully come up with a fix for the soon to be released comBIOS 1.30 update. Keep your fingers crossed. And you can stop reseating the card, it doesnt really do anything other than put wear on the card and the slot. Been there, done that. Only thing we've found that really does the trick is to do a hard reset (ie remove power and plug it back in) to correct the issue once it manifests as soft resets from the BIOS monitor dont consistently clear the problem up. Hope it helps Frank Cole Chuck (Doc) Beaudette wrote: I have run into an intersting anomoly and wonder if anyone else has seen something similar. I am using a net4501 w/ Mikrotik kernel. I installed a Ubiquiti XR2 wireless card. When I power cycle the unit, the wireless card disappears in the interface list. If I power off the unit, reseat the wireless card and power back up, the interface returns to the list. I originally thought this was a heat issue with the card because I was originally using a Mikrotik R52 in a small case, but I have since had this happen with mutliple wireless cards (using both XR2 and Mikrotik R52) and with multiple net4501 boards in fan cooled large enclosures. Doc ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech smime.p7s Description: S/MIME Cryptographic Signature ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] Soekris] 4801 thats stopped responding
On 2007/03/29 17:52, Tuc at T-B-O-H.NET wrote: > don't want to burn up the read cycles No such thing, it's just erase/write that has some kind of limit. http://en.wikipedia.org/wiki/Flash_memory http://en.wikipedia.org/wiki/CompactFlash ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] Dissapearing Interface on Mini-PC Slot
Thanks for the info...very helpful -Original Message- From: Frank Cole [mailto:[EMAIL PROTECTED] Sent: Thursday, March 29, 2007 2:20 PM To: Chuck (Doc) Beaudette Cc: soekris-tech@lists.soekris.com Subject: Re: [Soekris] Dissapearing Interface on Mini-PC Slot Hi Chuck, We've had the same issue. The problem is with the comBIOS and how it is handling the single chip Atheros chipset on the Ubiquity and other Atheros single chip designs. Our experience on average was about 1 out of 30 power cycles the cards would not be initialized properly at/just after POST though some boards seemed to be more frequent and some less frequent. We sent a couple of cards to Soekris for them to experiment with and hopefully come up with a fix for the soon to be released comBIOS 1.30 update. Keep your fingers crossed. And you can stop reseating the card, it doesnt really do anything other than put wear on the card and the slot. Been there, done that. Only thing we've found that really does the trick is to do a hard reset (ie remove power and plug it back in) to correct the issue once it manifests as soft resets from the BIOS monitor dont consistently clear the problem up. Hope it helps Frank Cole Chuck (Doc) Beaudette wrote: > I have run into an intersting anomoly and wonder if anyone else has > seen something similar. > > I am using a net4501 w/ Mikrotik kernel. I installed a Ubiquiti XR2 > wireless card. When I power cycle the unit, the wireless card > disappears in the interface list. If I power off the unit, reseat the > wireless card and power back up, the interface returns to the list. > > I originally thought this was a heat issue with the card because I was > originally using a Mikrotik R52 in a small case, but I have since had > this happen with mutliple wireless cards (using both XR2 and Mikrotik > R52) and with multiple net4501 boards in fan cooled large enclosures. > > > > Doc > > ___ > Soekris-tech mailing list > Soekris-tech@lists.soekris.com > http://lists.soekris.com/mailman/listinfo/soekris-tech > ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] Dissapearing Interface on Mini-PC Slot
Hi Chuck, We've had the same issue. The problem is with the comBIOS and how it is handling the single chip Atheros chipset on the Ubiquity and other Atheros single chip designs. Our experience on average was about 1 out of 30 power cycles the cards would not be initialized properly at/just after POST though some boards seemed to be more frequent and some less frequent. We sent a couple of cards to Soekris for them to experiment with and hopefully come up with a fix for the soon to be released comBIOS 1.30 update. Keep your fingers crossed. And you can stop reseating the card, it doesnt really do anything other than put wear on the card and the slot. Been there, done that. Only thing we've found that really does the trick is to do a hard reset (ie remove power and plug it back in) to correct the issue once it manifests as soft resets from the BIOS monitor dont consistently clear the problem up. Hope it helps Frank Cole Chuck (Doc) Beaudette wrote: I have run into an intersting anomoly and wonder if anyone else has seen something similar. I am using a net4501 w/ Mikrotik kernel. I installed a Ubiquiti XR2 wireless card. When I power cycle the unit, the wireless card disappears in the interface list. If I power off the unit, reseat the wireless card and power back up, the interface returns to the list. I originally thought this was a heat issue with the card because I was originally using a Mikrotik R52 in a small case, but I have since had this happen with mutliple wireless cards (using both XR2 and Mikrotik R52) and with multiple net4501 boards in fan cooled large enclosures. Doc ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech smime.p7s Description: S/MIME Cryptographic Signature ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] Soekris] 4801 thats stopped responding
>
> On Wed, Mar 28, 2007 at 03:57:18PM -0400, Tuc at T-B-O-H.NET wrote:
> > Like :
> >
> > watchdogd -s 15 -t 120
> >
> > it should be operating correctly. But about 10 hours in,
> > it seems the system was still operational within 5 seconds of
> > the time it rebooted. I've now changed it to :
> >
> > watchdogd -s 120 -t 1200
> >
> > and will see if it "misfires".
> Given the fact that the manpage for watchdog states that the default is
> 1 second, why do you want such long sleep times?
>
Two reasons, atleast in my mind. First is that there is a
CF in there, and don't want to burn up the read cycles having it
do a stat of /etc every second. Second is that I just wanted to
give it a WIDE berth. It may not be the 30(timeout) to 1(sleep)
that the default is, but if a process running with a 2 minute
sleep takes over 20 minutes to execute Theres a problem.
>
> Also, the man page says that "If -e cmd is not specified, the daemon
> will perform a trivial file system check instead." - maybe this
> filesystem check is not successful on the soekris?
>
I threw myself for quite a curve with that at first. I
interpreted it as a "last chance" effort to reset the counter.
Its not. I was putting "-e 'logger I'm gonna hurl'" and it was
resetting constantly. Turns out it EXECUTES the command and then
does the sleep cycle, executes it and sleeps, etc. I also was
a bit freaked when I heard "file system check" as in fsck! I
was concerned this was going to really burn up the CF. Turns
out that the code actually just does a "stat /etc". While
not terrible, I still didn't feel like doing it every second
burning the CF reads. If a stat /etc fails, you have some
SERIOUS issues!
>
> Anyway, on linux I never had any problems with the watchdog, so I assume
> that the hardware watchdog works.
>
I would think the FreeBSD one works too. Poul-Henning Kamp
worked on it, and I know he's an active participant here. Besides,
when it comes down to it, theres really not much for it to do...
Arm it, execute the "stat /etc", if its ok poke the timer, sleep.
while (end_program == 0) {
failed = 0;
if (test_cmd != NULL)
failed = system(test_cmd);
else
failed = stat("/etc", &sb);
if (failed == 0)
watchdog_patpat();
sleep(nap);
}
int
watchdog_patpat(void)
{
return ioctl(fd, WDIOCPATPAT, &timeout);
}
Tuc
___
Soekris-tech mailing list
Soekris-tech@lists.soekris.com
http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] Soekris] 4801 thats stopped responding
On Wed, Mar 28, 2007 at 03:57:18PM -0400, Tuc at T-B-O-H.NET wrote: > Like : > > watchdogd -s 15 -t 120 > > it should be operating correctly. But about 10 hours in, > it seems the system was still operational within 5 seconds of > the time it rebooted. I've now changed it to : > > watchdogd -s 120 -t 1200 > > and will see if it "misfires". Given the fact that the manpage for watchdog states that the default is 1 second, why do you want such long sleep times? Also, the man page says that "If -e cmd is not specified, the daemon will perform a trivial file system check instead." - maybe this filesystem check is not successful on the soekris? Anyway, on linux I never had any problems with the watchdog, so I assume that the hardware watchdog works. iustin ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] 4801 thats stopped responding
On Tue, Mar 27, 2007 at 03:56:03PM -0400, Tuc at T-B-O-H.NET wrote: > > > > On Mon, Mar 26, 2007 at 10:58:43PM -0400, Tuc at T-B-O-H.NET wrote: > > > So my final option is a cold boot? Anything to do for future > > > times this happens? > > > > Well, I don't know about FreeBSD, but on Linux I use a watchdog daemon > > in combination with the hardware support present in the soekris. So, if > > the OS is really hung and the daemon doesn't get to run, the hardware > > will reboot the machine. Which, while not nice, is better than just > > having it stay there and do nothing. > > > Hi, > > Thanks I looked into this at one point, but if memory > serves me (AND IT USUALLY DOESN'T NOWADAYS) I had it set for like > 30 seconds and it would reboot in the middle of running... Hmm, never happened to me (on a lightly loaded 4801). I don't remember exactly what time I have set, but it's anyway under 60 seconds. Make sure you give the watchdog daemon high priority - either nice to -20 or run it as realtime task, otherwise it may be preempted by other high priority tasks. iustin ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] Rebooting net4501
At 02:35 PM 3/29/2007, Mike Tancsa wrote: >comBIOS ver. 1.30 20070326 Copyright (C) 2000-2005 Soekris Engineering. > >net45xx > >0064 Mbyte MemoryCPU 80486 100 Mhz > >Pri Mas TOSHIBA THNCF1G02QG LBA Xlt 992-32-63 1000 Mbyte > > > diskinfo -v /dev/ad0 >/dev/ad0 > 512 # sectorsize > 1024450560 # mediasize in bytes (977M) > 2000880 # mediasize in sectors > 1985# Cylinders according to firmware. > 16 # Heads according to firmware. > 63 # Sectors according to firmware. >ad0: 976MB at ata0-master PIO4 > >The strange thing is that the 4801s and some of my other embedded >devices dont suffer the same problem with this flash. Just the 45xx series. > Here is another CF from the same lot that works just fine. Visually looking at the CFs, they are identical # diskinfo -v /dev/ad0 /dev/ad0 512 # sectorsize 1014128640 # mediasize in bytes (967M) 1980720 # mediasize in sectors 1965# Cylinders according to firmware. 16 # Heads according to firmware. 63 # Sectors according to firmware. # dmesg | grep ad0 ad0: 967MB at ata0-master PIO4 Trying to mount root from ufs:/dev/ad0s1a comBIOS ver. 1.30 20070326 Copyright (C) 2000-2005 Soekris Engineering. net45xx 0064 Mbyte MemoryCPU 80486 100 Mhz Pri Mas KINGSTONLBA Xlt 982-32-63 990 Mbyte Seconds to automatic boot. Press Ctrl-P for entering Monitor. 1 FreeBSD 2 FreeBSD Default: 1 ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] Rebooting net4501
At 03:53 PM 6/10/2006, Matti J. Karki wrote: >Hi! > >I noticed an interesting thing with my net4501. I'm running FreeBSD >6.1 and - just out of curiosity - I tried to reboot the system by >calling "reboot". The FreeBSD does shut down successfully and the I have the same problem... It seems to be some CF cause this problem, but not others. The same issue happens with FreeBSD 4.x (monowall) and FreeBSD RELENG_6 (tried 2 differnt 4511s, one with 1.28 and one with 1.30). With a cold boot / power cycle, the 4511 boots up just fine. However, after a soft boot, it sees the CF, but does not want to boot off it. These are Kingston CFs, but I guess they switch manufactures often enough that in a lot of 10 that I bought, I see the disk come up as Toshiba, Kingston and yet another manufacturer. I just updated the flash to 1.30, but no difference. The same flash on a 4801 seems to boot just fine and I dont see the softboot problem. Just the 4511 has the softboot issue. comBIOS ver. 1.30 20070326 Copyright (C) 2000-2005 Soekris Engineering. net45xx 0064 Mbyte MemoryCPU 80486 100 Mhz Pri Mas TOSHIBA THNCF1G02QG LBA Xlt 992-32-63 1000 Mbyte comes up quite quickly. But after a soft boot, there is a 30 second delay, before Pri Mas TOSHIBA THNCF1G02QG LBA Xlt 992-32-63 1000 Mbyte comes up. I have the following set > show ConSpeed = 19200 ConLock = Enabled ConMute = Disabled BIOSentry = Enabled PCIROMS = Enabled PXEBoot = Disabled FLASH = Primary BootDelay = 5 FastBoot = Disabled BootPartition = Disabled BootDrive = 80 81 F0 FF ShowPCI = Enabled Reset = Hard > I tried with FastBoot enabled, but no luck. It just ends up going to comBIOS ver. 1.30 20070326 Copyright (C) 2000-2005 Soekris Engineering. net45xx 0064 Mbyte MemoryCPU 80486 100 Mhz Pri Mas TOSHIBA THNCF1G02QG LBA Xlt 992-32-63 1000 Mbyte Seconds to automatic boot. Press Ctrl-P for entering Monitor. NSC DP83815/DP83816 Fast Ethernet UNDI, v1.03 Copyright (C) 2002, 2003 National Semiconductor Corporation All rights reserved. Pre-boot eXecution Environment PXE-2.0 (build 082) Copyright (C) 1997-2000 Intel Corporation PXE-E61: Media test failure, check cable PXE-M0F: Exiting MacPhyter PXE ROM. No Boot device available, enter monitor. comBIOS Monitor. Press ? for help. > until I power cycle it. Diskinfo shows diskinfo -v /dev/ad0 /dev/ad0 512 # sectorsize 1024450560 # mediasize in bytes (977M) 2000880 # mediasize in sectors 1985# Cylinders according to firmware. 16 # Heads according to firmware. 63 # Sectors according to firmware. ad0: 976MB at ata0-master PIO4 The strange thing is that the 4801s and some of my other embedded devices dont suffer the same problem with this flash. Just the 45xx series. ---Mike ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
[Soekris] Dissapearing Interface on Mini-PC Slot
I have run into an intersting anomoly and wonder if anyone else has seen something similar. I am using a net4501 w/ Mikrotik kernel. I installed a Ubiquiti XR2 wireless card. When I power cycle the unit, the wireless card disappears in the interface list. If I power off the unit, reseat the wireless card and power back up, the interface returns to the list. I originally thought this was a heat issue with the card because I was originally using a Mikrotik R52 in a small case, but I have since had this happen with mutliple wireless cards (using both XR2 and Mikrotik R52) and with multiple net4501 boards in fan cooled large enclosures. Doc ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
[Soekris] "Lockup" update
Hi, Net4801-50. FreeBSD 5.5-RELEASE-p8. Not staying up/locking up... You know. ;) At 7:33am today I started watchdogd again, 120 sleep, 1200 timeout. At 11:11:08 my screen stopped updating, but it seems it wasn't until 12:21 that the unit actually reset. It seems to be getting worse and worse... If the watchdog is really getting set properly, why wouldn't it reset within the 20 minutes I specified? I can't seem to keep this unit running anymore for more than a few hours. The last time the kernel/OS was updated was October 16th, so its not like a "Well, I changed something, but that shouldn't have broken it". Do I still persue from the OS side, or is this a case of hardware that may keep failing? Thanks, Tuc ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
