Re: large system date skew on RELENG_6 changes causes select() failures
Stanislaw Halik wrote this message on Tue, Sep 05, 2006 at 06:51 +0200: Hello, A while ago, by accident, I've changed the system date back to the '98 using date(1). To my astonishment, screen(1) barfed about EINVAL in select() and died. Programs, including opera (native FreeBSD-6 binary) kept spinning the CPU until I killed them. I have no means for debugging it. Is this somehow expected? If not (i.e. it's a bug), is it known? Probably, they calculated timeout's which magicly became negative, which isn't a valid timeout, and none of the programs are programmed well enough to handle the case and exhibited the behavior that you saw... -- John-Mark Gurney Voice: +1 415 225 5579 All that I will do, has been done, All that I have, has not. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: large system date skew on RELENG_6 changes causes select() failures
Stanislaw Halik wrote this message on Tue, Sep 05, 2006 at 06:51 +0200:
Hello,
A while ago, by accident, I've changed the system date back to the '98
using date(1). To my astonishment, screen(1) barfed about EINVAL in
select() and died. Programs, including opera (native FreeBSD-6 binary)
kept spinning the CPU until I killed them.
I have no means for debugging it.
Is this somehow expected? If not (i.e. it's a bug), is it known?
Probably, they calculated timeout's which magicly became negative, which
isn't a valid timeout, and none of the programs are programmed well enough
to handle the case and exhibited the behavior that you saw...
Nope. Just a simple limit in itimerfix.
int
itimerfix(struct timeval *tv)
{
if (tv-tv_sec 0 || tv-tv_sec 1 ||
tv-tv_usec 0 || tv-tv_usec = 100)
return (EINVAL);
if (tv-tv_sec == 0 tv-tv_usec != 0 tv-tv_usec tick)
tv-tv_usec = tick;
return (0);
}
date -j 9809051630 +%s - 904977000
date +%s - 1157438219
1157438219 - 904977000 - 252461219 which is greater that 1
--
John-Mark GurneyVoice: +1 415 225 5579
All that I will do, has been done, All that I have, has not.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
--
ISC Training! October 16-20, 2006, in the San Francisco Bay Area,
covering topics from DNS to DHCP. Email [EMAIL PROTECTED]
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with Mitsumi 7-in-1 USB Card Reader/Floppy combo
On Tuesday 05 September 2006 03:16, Indigo 23 wrote: Thanks for the reply. I already tried that, but unfortunetly the same thing happens :( Any other suggestions? Maybe you want to try my new Giant free USB driver: # # How to install the new USB driver: # # # First get all the sources # (you need /usr/ports/devel/subversion installed): # svn --username anonsvn --password anonsvn \ checkout svn://svn.turbocat.net/i4b # # The following commands will # install the driver on FreeBSD 6.x/7.x: # cd i4b/trunk/i4b/FreeBSD.usb make S=../src package make install # # Then build a new kernel (with modules) # --HPS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: LSI/amr driver controller cache problem?
Hi, all! On Fri, Sep 01, 2006 at 11:15:37AM -0600, Scott Long wrote: It is very arguably a bug in the LSI firmware if it is actually dumping its cache when a PCI reset occurs, especially if a battery unit is present. However, I seriously doubt that you will get anyone at LSI to listen to this problem. Do you get any messages on the console at shutdown about the amr driver flushing the cache? Just verified - yes: amr0: flushing cache...done amr1: flushing cache...done Also, check the cache setting on the drives itself. Maybe the drives are loosing power or getting reset while data is in their cache. I'm starting to suspect something like this. The controller's setting for the individual drives' caches is OFF. But these (Seagate ST3500841NS) would not be the first ATA/SATA drives to lie about their cache for performance. From the settings that are readily available through the controller's and other knobs, I eliminated all: controller cache policy: WTHRU, drive cache: OFF, Softupdates: disabled (!). Just to be sure. Installworld, reboot, *bang* unexpected file system inconsistency, run fsck manually ... Any ideas? I'll invest some time researching other people's reports about my particular disk drives. Maybe there's a DOS/Windows tool to disable their cache permanently ... There's a small chance that actually setting the drives' caches to ON will help. If the controller is intelligent enough to issue flush cache commands to the individual drives and if it is so clever that it only issues this command when the cache is configured ON. ;-) Thanks, Patrick M. Hausen Leiter Netzwerke und Sicherheit -- punkt.de GmbH Internet - Dienstleistungen - Beratung Vorholzstr. 25Tel. 0721 9109 -0 Fax: -100 76137 Karlsruhe http://punkt.de ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: missed hostapd / ath MFC warning?
On 2006-09-04 22:57, Sam Leffler wrote: Volker wrote: ifconfig ath0 says: ath0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 2290 ether 00:09:5b:89:7d:1f media: IEEE 802.11 Wireless Ethernet autoselect status: no carrier ssid vtec channel 9 authmode WPA privacy MIXED deftxkey 2 TKIP 2:128-bit TKIP 3:128-bit txpowmax 30 bmiss 7 protmode CTS burst bintval 100 I just get a 'no carrier' and so no client system is able to see the AP. There's no configuration change just a recently csup'ed and rebuild system. Is there something I've overseen? ath0 is not set in hostap mode. Sam Sam, thanks for your answer... that's it and I've overseen that fact! The strange thing is, I've got that: ifconfig_ath0=inet 192.168.18.2/24 ssid 'vtec' mode 11g mediaopt hostap channel 9 chanlist '1-11' -powersave pureg hidessid wepmode on -apbridge -wme ... (removed a bunch of mac:add entries at the end) in my /etc/rc.conf. After I've manually set the interface into hostap mode, the device was defaulting to channel 36 (11a mode). After manually correcting hostap and 11g mode, everything now works fine again. I'm wondering if there has been something changed at initializing the ath device? Greetings, Volker ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: LSI/amr driver controller cache problem?
Hi, all! Also, check the cache setting on the drives itself. Maybe the drives are loosing power or getting reset while data is in their cache. I'm starting to suspect something like this. The controller's setting for the individual drives' caches is OFF. But these (Seagate ST3500841NS) would not be the first ATA/SATA drives to lie about their cache for performance. Seems like for i in 0 1 2 3 4 5 do megarc -pSetCache -WCE0 -SaveCacheSetting -ch0 -id$i -a0 done did the trick. This is supposed to disable the physical drives' write cache and save this setting in the drives' NVRAM, if supported. I don't know why simply setting the WC to off in the controller's BIOS setup tool didn't have the same effect. I'm keeping my fingers crossed ;-) Time to re-enable softupdates and do some more stress testing. Up to now the system survived two times make installworld reboot after I changed the settings. Thanks to the guys keeping the amr driver up-to-date. The Linux megamgr utility works just fine. If I find the time, I'll make a port. Regards, Patrick M. Hausen Leiter Netzwerke und Sicherheit -- punkt.de GmbH Internet - Dienstleistungen - Beratung Vorholzstr. 25Tel. 0721 9109 -0 Fax: -100 76137 Karlsruhe http://punkt.de ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: LSI/amr driver controller cache problem?
Hi, all! Here's the preliminary results: - Disk write cache off by the means of: megarc -pSetCache -WCE0 -SaveCacheSetting -ch0 -id$drive -a0 - Controller cache policy: write through (megamgr or BIOS setup) - Softupdates: enabled, FreeBSD 6-STABLE System is stable, so far. I will put it back into production this evening. *phew* ;-) Anyone tried the Intel/LSI web console for Linux instead of megamgr, yet? Regards, Patrick M. Hausen Leiter Netzwerke und Sicherheit -- punkt.de GmbH Internet - Dienstleistungen - Beratung Vorholzstr. 25Tel. 0721 9109 -0 Fax: -100 76137 Karlsruhe http://punkt.de ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with Mitsumi 7-in-1 USB Card Reader/Floppy combo
Thanks for that excellent suggestion. It worked perfectly. I just have a few questions. 1) Any idea when this will be imported in to RELENG_6? 2) I have to do this everytime I update my sources, correct? 3) This is relatively stable, correct? (I did test it out a bit, but of course not thorougly enough to see how stable it is) Thanks again. On 9/5/06, Hans Petter Selasky [EMAIL PROTECTED] wrote: On Tuesday 05 September 2006 03:16, Indigo 23 wrote: Thanks for the reply. I already tried that, but unfortunetly the same thing happens :( Any other suggestions? Maybe you want to try my new Giant free USB driver: # # How to install the new USB driver: # # # First get all the sources # (you need /usr/ports/devel/subversion installed): # svn --username anonsvn --password anonsvn \ checkout svn://svn.turbocat.net/i4b # # The following commands will # install the driver on FreeBSD 6.x/7.x: # cd i4b/trunk/i4b/FreeBSD.usb make S=../src package make install # # Then build a new kernel (with modules) # --HPS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with Mitsumi 7-in-1 USB Card Reader/Floppy combo
On Tuesday 05 September 2006 13:28, Indigo 23 wrote: Thanks for that excellent suggestion. It worked perfectly. I just have a few questions. 1) Any idea when this will be imported in to RELENG_6? I don't know. If I am right, you will see my driver in freebsd-current some time after Christmas. 2) I have to do this everytime I update my sources, correct? Yes. 3) This is relatively stable, correct? (I did test it out a bit, but of course not thorougly enough to see how stable it is) Yes, it is stable, but be aware that if your system runs low on memory, you can get a panic saying, sleeping with mutex XXX locked, or something alike. That is because the umass device driver is still under the USB emulation layer of the old USB API, which is depreciated, and will be removed once I have completed the conversion of all USB device drivers. This will most likely happen before the end of this month. Then I need some help testing all the rewritten USB device drivers. --HPS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Ports Update: Failed to Generate INDEX
Hi all,
While trying to update ports for FreeBSD 6.1-STABLE using this command:
/usr/local/sbin/portsdb -Uu
I got the following error (please see below for the process leading up
to this):
Updating the ports index ... Generating INDEX.tmp - please
wait..Makefile, lin
e 33: Could not find
/usr/ports/japanese/gnomelibs/../../x11/gnomelibs/Makefile
/usr/ports/Mk/bsd.port.mk, line 1886: Malformed conditional
(${X_WINDOW_SYSTEM
:L} == xfree86-3)
/usr/ports/Mk/bsd.port.mk, line 1951: Malformed conditional
(${PERL_LEVEL} =
500600)
/usr/ports/Mk/bsd.port.mk, line 1960: if-less endif
/usr/ports/Mk/bsd.port.mk, line 2200: Malformed conditional (${PREFIX}
== ${X1
1BASE_REL} || defined(USE_X_PREFIX))
/usr/ports/Mk/bsd.port.mk, line 2203: Malformed conditional
(${X_WINDOW_SYSTEM
:L} == xfree86-3)
/usr/ports/Mk/bsd.port.mk, line 2208: if-less elif
/usr/ports/Mk/bsd.port.mk, line 2210: if-less else
/usr/ports/Mk/bsd.port.mk, line 2212: if-less endif
/usr/ports/Mk/bsd.port.mk, line 2213: if-less endif
/usr/ports/Mk/bsd.port.mk, line 2864: Malformed conditional (${PREFIX}
== /usr
)
/usr/ports/Mk/bsd.port.mk, line 2866: if-less else
/usr/ports/Mk/bsd.port.mk, line 2868: if-less endif
/usr/ports/Mk/bsd.port.mk, line 2956: Malformed conditional (${PREFIX}
== /usr
)
/usr/ports/Mk/bsd.port.mk, line 2958: if-less else
/usr/ports/Mk/bsd.port.mk, line 2960: if-less endif
/usr/ports/Mk/bsd.port.mk, line 5503: Malformed conditional
((${PREFIX} != ${L
OCALBASE_REL} ${PREFIX} != ${X11BASE_REL} ${PREFIX} !=
${LINUXBASE_REL}
${PREFIX} != /usr))
/usr/ports/Mk/bsd.port.mk, line 5508: if-less endif
/usr/ports/Mk/bsd.port.mk, line 5992: if-less endif
make: fatal errors encountered -- cannot continue
=== japanese/gnomelibs failed
*** Error code 1
1 error
Before reporting this error, verify that you are running a supported
version of FreeBSD (see http://www.FreeBSD.org/ports/) and that you
have a complete and up-to-date ports collection. (INDEX builds are
not supported with partial or out-of-date ports collections -- in
particular, if you are using cvsup, you must cvsup the ports-all
collection, and have no refuse files.) If that is the case, then
report the failure to [EMAIL PROTECTED] together with relevant
details of your ports configuration (including FreeBSD version,
your architecture, your environment, and your /etc/make.conf
settings, especially compiler flags and WITH/WITHOUT settings).
Note: the latest pre-generated version of INDEX may be fetched
automatically with make fetchindex.
*** Error code 1
Stop in /usr/ports.
*** Error code 1
Stop in /usr/ports.
failed to generate INDEX!
portsdb: index generation error
Process:
cd /usr/ports/net/cvsup
make install clean
(reboot)
cp /usr/share/examples/cvsup/ports-supfile /root/
I then edited /root/ports-supfile and added the host:
*default host=cvsup12.FreeBSD.org
At first, I commented out all the ports for languages I don't understand
such as Russian, Japanese, etc. But I got a similar error, so I
commented out all the individual ports and uncommented ports-all to do a
complete job of it. That's when I ran portsdb -Uu and got the above error.
This is my first time doing this, so I'm sure I've missed something
somewhere.
-Ron T.
--
Ron Tarrant
Blog:A HREF=http://www.writingup.com/blog/phpgtk2;PHP-Gtk2/A
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports Update: Failed to Generate INDEX
Ron Tarrant wrote:
Hi all,
While trying to update ports for FreeBSD 6.1-STABLE using this command:
/usr/local/sbin/portsdb -Uu
I got the following error (please see below for the process leading up
to this):
Updating the ports index ... Generating INDEX.tmp - please
wait..Makefile, lin
e 33: Could not find
/usr/ports/japanese/gnomelibs/../../x11/gnomelibs/Makefile
/usr/ports/Mk/bsd.port.mk, line 1886: Malformed conditional
(${X_WINDOW_SYSTEM
:L} == xfree86-3)
/usr/ports/Mk/bsd.port.mk, line 1951: Malformed conditional
(${PERL_LEVEL} =
500600)
/usr/ports/Mk/bsd.port.mk, line 1960: if-less endif
/usr/ports/Mk/bsd.port.mk, line 2200: Malformed conditional
(${PREFIX} == ${X1
1BASE_REL} || defined(USE_X_PREFIX))
/usr/ports/Mk/bsd.port.mk, line 2203: Malformed conditional
(${X_WINDOW_SYSTEM
:L} == xfree86-3)
/usr/ports/Mk/bsd.port.mk, line 2208: if-less elif
/usr/ports/Mk/bsd.port.mk, line 2210: if-less else
/usr/ports/Mk/bsd.port.mk, line 2212: if-less endif
/usr/ports/Mk/bsd.port.mk, line 2213: if-less endif
/usr/ports/Mk/bsd.port.mk, line 2864: Malformed conditional
(${PREFIX} == /usr
)
/usr/ports/Mk/bsd.port.mk, line 2866: if-less else
/usr/ports/Mk/bsd.port.mk, line 2868: if-less endif
/usr/ports/Mk/bsd.port.mk, line 2956: Malformed conditional
(${PREFIX} == /usr
)
/usr/ports/Mk/bsd.port.mk, line 2958: if-less else
/usr/ports/Mk/bsd.port.mk, line 2960: if-less endif
/usr/ports/Mk/bsd.port.mk, line 5503: Malformed conditional
((${PREFIX} != ${L
OCALBASE_REL} ${PREFIX} != ${X11BASE_REL} ${PREFIX} !=
${LINUXBASE_REL}
${PREFIX} != /usr))
/usr/ports/Mk/bsd.port.mk, line 5508: if-less endif
/usr/ports/Mk/bsd.port.mk, line 5992: if-less endif
make: fatal errors encountered -- cannot continue
=== japanese/gnomelibs failed
*** Error code 1
1 error
Before reporting this error, verify that you are running a supported
version of FreeBSD (see http://www.FreeBSD.org/ports/) and that you
have a complete and up-to-date ports collection. (INDEX builds are
not supported with partial or out-of-date ports collections -- in
particular, if you are using cvsup, you must cvsup the ports-all
collection, and have no refuse files.) If that is the case, then
report the failure to [EMAIL PROTECTED] together with relevant
details of your ports configuration (including FreeBSD version,
your architecture, your environment, and your /etc/make.conf
settings, especially compiler flags and WITH/WITHOUT settings).
Note: the latest pre-generated version of INDEX may be fetched
automatically with make fetchindex.
*** Error code 1
Stop in /usr/ports.
*** Error code 1
Stop in /usr/ports.
failed to generate INDEX!
portsdb: index generation error
Process:
cd /usr/ports/net/cvsup
make install clean
(reboot)
cp /usr/share/examples/cvsup/ports-supfile /root/
I then edited /root/ports-supfile and added the host:
*default host=cvsup12.FreeBSD.org
At first, I commented out all the ports for languages I don't
understand such as Russian, Japanese, etc. But I got a similar error,
so I commented out all the individual ports and uncommented ports-all
to do a complete job of it. That's when I ran portsdb -Uu and got the
above error.
This is my first time doing this, so I'm sure I've missed something
somewhere.
-Ron T.
Instead of regenerating the INDEX, why not just download it?
# cd /usr/ports
# make fetchindex
Regards,
Chris Jones
--
Chris Jones
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports Update: Failed to Generate INDEX
On Tue, 05 Sep 2006 09:25:38 -0400, Ron Tarrant [EMAIL PROTECTED] wrote: At first, I commented out all the ports for languages I don't understand such as Russian, Japanese, etc. But I got a similar error, so I commented out all the individual ports and uncommented ports-all to do a complete job of it. That's when I ran portsdb -Uu and got the above error. This is my first time doing this, so I'm sure I've missed something somewhere. IIRC, you must have all the ports (ports-all in your config file) in order to generate an INDEX, as it will fail otherwise. -- Ricardo Nabinger Sanchez [EMAIL PROTECTED],wait4.org} Powered by FreeBSD Left to themselves, things tend to go from bad to worse. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports Update: Failed to Generate INDEX
On Tue, 5 Sep 2006 11:01:39 -0300, Ricardo Nabinger Sanchez [EMAIL PROTECTED] wrote: On Tue, 05 Sep 2006 09:25:38 -0400, Ron Tarrant [EMAIL PROTECTED] wrote: At first, I commented out all the ports for languages I don't understand such as Russian, Japanese, etc. But I got a similar error, so I commented out all the individual ports and uncommented ports-all to do a complete job of it. That's when I ran portsdb -Uu and got the above error. This is my first time doing this, so I'm sure I've missed something somewhere. IIRC, you must have all the ports (ports-all in your config file) in order to generate an INDEX, as it will fail otherwise. After sending, I saw your comment about having already done that (ports-all). Don't know what's wrong, then -- sorry for the noise. -- Ricardo Nabinger Sanchez [EMAIL PROTECTED],wait4.org} Powered by FreeBSD Left to themselves, things tend to go from bad to worse. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports Update: Failed to Generate INDEX
Ricardo Nabinger Sanchez wrote: On Tue, 5 Sep 2006 11:01:39 -0300, Ricardo Nabinger Sanchez [EMAIL PROTECTED] wrote: On Tue, 05 Sep 2006 09:25:38 -0400, Ron Tarrant [EMAIL PROTECTED] wrote: At first, I commented out all the ports for languages I don't understand such as Russian, Japanese, etc. But I got a similar error, so I commented out all the individual ports and uncommented ports-all to do a complete job of it. That's when I ran portsdb -Uu and got the above error. This is my first time doing this, so I'm sure I've missed something somewhere. IIRC, you must have all the ports (ports-all in your config file) in order to generate an INDEX, as it will fail otherwise. After sending, I saw your comment about having already done that (ports-all). Don't know what's wrong, then -- sorry for the noise. No problem, Ricardo. Thanks for the reply anyway. -Ron T. -- Ron Tarrant Blog:A HREF=http://www.writingup.com/blog/phpgtk2;PHP-Gtk2/A ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports Update: Failed to Generate INDEX
Chris Jones wrote: Instead of regenerating the INDEX, why not just download it? # cd /usr/ports # make fetchindex Regards, Chris Jones Thanks for the reply, Chris. Yup, good idea. I did this and found out that INDEX-6 was already up-to-date. Could this be why index generation failed? -Ron T. -- Ron Tarrant Blog:A HREF=http://www.writingup.com/blog/phpgtk2;PHP-Gtk2/A ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports Update: Failed to Generate INDEX
Hi, [..] At first, I commented out all the ports for languages I don't understand such as Russian, Japanese, etc. But I got a similar error, so I commented out all the individual ports and uncommented ports-all to do a complete job of it. That's when I ran portsdb -Uu and got the above error. just to make sure: You did run cvsup after uncommenting ports-all and before running portsdb -Uu, right? Wolfgang ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports Update: Failed to Generate INDEX
Ron Tarrant wrote: Chris Jones wrote: Instead of regenerating the INDEX, why not just download it? # cd /usr/ports # make fetchindex Regards, Chris Jones Thanks for the reply, Chris. Yup, good idea. I did this and found out that INDEX-6 was already up-to-date. Could this be why index generation failed? -Ron T. Shouldn't have mattered... all that would happen is the generated INDEX would've overwritten the downloaded one. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.2 ETA
On 8/30/06, Yoshihiro Ota [EMAIL PROTECTED] wrote: It may be a bit early but I switched to RELENG_6 fot that reason. Me too, on a couple of not really production machines. I generally switch a couple more production but not critical machines over once the RE cycle begins, which is why I was asking. Is it too early to report incidents? You should always report incidents, whether there's a RE cycle in progress or not. If nobody knows there are problems, nobody will fix them. Bryan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports Update: Failed to Generate INDEX
On Tue, Sep 05, 2006 at 09:25:38AM -0400, Ron Tarrant wrote: Updating the ports index ... Generating INDEX.tmp - please wait..Makefile, lin e 33: Could not find /usr/ports/japanese/gnomelibs/../../x11/gnomelibs/Makefile Why not? have a complete and up-to-date ports collection. (INDEX builds are not supported with partial or out-of-date ports collections -- in particular, if you are using cvsup, you must cvsup the ports-all collection, and have no refuse files.) If that is the case, then At first, I commented out all the ports for languages I don't understand such as Russian, Japanese, etc. But I got a similar error, so I commented out all the individual ports and uncommented ports-all to do a complete job of it. That's when I ran portsdb -Uu and got the above error. This makes me think that you didn't re-run cvsup since your similar error is precisely what you'd expect if you didn't have anything in japanese/. Kris pgpZtnGmckzZt.pgp Description: PGP signature
Re: Ports Update: Failed to Generate INDEX
Wolfgang Zenker wrote: just to make sure: You did run cvsup after uncommenting ports-all and before running portsdb -Uu, right? Thanks for the reply, Wolfgang. I'm pretty sure I did. That was last night and I have a vague memory of doing it. That tty is tied up right now, so I can't check command history until it's done. I'll repost with the answer once I can double-check. Thanks. -Ron T. -- Ron Tarrant Blog:A HREF=http://www.writingup.com/blog/phpgtk2;PHP-Gtk2/A ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports Update: Failed to Generate INDEX
Chris Jones wrote: Yup, good idea. I did this and found out that INDEX-6 was already up-to-date. Could this be why index generation failed? Shouldn't have mattered... all that would happen is the generated INDEX would've overwritten the downloaded one. Hmm... Very curious. Thanks. -Ron T. -- Ron Tarrant Blog:A HREF=http://www.writingup.com/blog/phpgtk2;PHP-Gtk2/A ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
6.1-STABLE spontaneously reboots!
This server was in production and rock steady with 4.10-STABLE for years. Before moving it to a colo center, I took it offline and did a clean install of 6.1, cvsup'd to STABLE on 8/30/06 and then installed the latest stable versions of all the applications and mods. It's now back in production and for no cause that I can find, it reboots itself roughly twice a day. Nothing in the syslog or console log, it looks basically like a power event...system comes back up with uncleanly dismounted file systems. However, it is on very clean power, has dual power supplies and none of the other boxes on that circuit has any pwer problems. On boot, I had noticed some complaints about ACPI, but I even tried disabling it, but it still did this several hours later. The ONLY hardware change I'd made was to remove a SCSI passthrough cable that enabled the on-board SCSI (it's an L440GX+) to be used with an external tape drive. If somebody can point me in the right direction, or to the right list, I'd greatly appreciate it! (please reply directly, as I am not subscribed to all lists) James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am = ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports Update: Failed to Generate INDEX
On Tue, 5 Sep 2006, Ron Tarrant wrote:
Hi all,
While trying to update ports for FreeBSD 6.1-STABLE using this command:
/usr/local/sbin/portsdb -Uu
I've seen errors similar to yours when your Mk files are out of
date with the rest of your ports tree. As root:
# cd /usr/ports/Mk
# cvs -R update -P -d
I'm assuming that the rest of your ports tree has also been
updated accordingly ('cd /usr/ports; cvs -R update -P -d').
--
DE
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.1-STABLE spontaneously reboots!
On Tue, Sep 05, 2006, [EMAIL PROTECTED] wrote: It's now back in production and for no cause that I can find, it reboots itself roughly twice a day. Nothing in the syslog or console log [...] Try setting `dumpdev' in your rc.conf to the swap device. After the machine reboots, you might get a dump in /var/crash. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: tcp/udp performance
Jack Vogel wrote: On 8/30/06, Danny Braniss [EMAIL PROTECTED] wrote: ever since 6.1 I've seen fluctuations in the performance of the em (Intel(R) PRO/1000 Gigabit Ethernet). motherboard OBN (On Board NIC) -- 1- Intel SE7501WV2S Intel 82546EB::2.1 2- Intel SE7320VP2D2INTEL 82541 3- Sun Fire X4100 ServerIntel(R) PRO/1000 test 1: writing to a NetApp filer via NFS/UDP FreeBSD Linux MegaBytes/sec 1- Average: 18.48 32.61 2- Average: 15.69 35.72 3- Average: 16.61 29.69 (interstingly, doing NFS/TCP instead of NFS/UDP shows an increase in speed of around 60% on FreeBSD but none on Linux) test2: iperf using 1 as server: FreeBSD(*) Linux Mbits/sec 1- 926 905 (this machine was busy) 2- 545 798 3- 910 912 *: did a 'sysctl net.inet.tcp.sendspace=65536' So, it seems to me something is not that good in the UDP department, but I can't find what to tweek. Any help? danny Have discussed this some internally, the best idea I've heard is that UDP is not giving us the interrupt rate that TCP would, so we end up not cleaning up as often, and thus descriptors might not be as quickly available.. Its just speculation at this point. If a high interrupt rate is a problem and your NIC+driver supports it, then try enabling polling(4) aswell. This has helped me for bulk transfers on slower boxes but i have noticed problems with ALTQ/dummynet and other highly realtime dependent networking code. YMMV. More info in the man 4 polling. I think recent linux kernels/drivers have this implemented so it will enable it dynamically on high load. However i only skimmed the documents and i'm not a linux expert so i may be wrong on that. /Junics Try this: the default is only to have 256 descriptors, try going for the MAX which is 4K. Cheers, Jack ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports Update: Failed to Generate INDEX
Hi Kris, Thanks for the reply... Kris Kennaway wrote: On Tue, Sep 05, 2006 at 09:25:38AM -0400, Ron Tarrant wrote: Updating the ports index ... Generating INDEX.tmp - please wait..Makefile, lin e 33: Could not find /usr/ports/japanese/gnomelibs/../../x11/gnomelibs/Makefile Why not? Good question. I checked the paths and they all make sense. The Makefile is in place. This makes me think that you didn't re-run cvsup since your similar error is precisely what you'd expect if you didn't have anything in japanese/. I'll have to recheck to make sure once that tty is free. Thanks. -Ron T. -- Ron Tarrant Blog:A HREF=http://www.writingup.com/blog/phpgtk2;PHP-Gtk2/A ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
em watchdog timeout on UP, 6-stable
Updated my Athlon-xp 6-stable system last night, got an em watchdog timeout for the first time a few hours later, during a fairly high-traffic period. System is UP but does have device apic in the config. Any chance this is the recent race condition? Workaround? ifconfig em0 down, ifconfig em0 up seemed to cure it, at least for the moment. Thanks, Barney Wolff -- Barney Wolff I never met a computer I didn't like. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.1-STABLE spontaneously reboots!
On Tue, Sep 05, 2006 at 10:55:04AM -0400, [EMAIL PROTECTED] wrote: This server was in production and rock steady with 4.10-STABLE for years. Before moving it to a colo center, I took it offline and did a clean install of 6.1, cvsup'd to STABLE on 8/30/06 and then installed the latest stable versions of all the applications and mods. It's now back in production and for no cause that I can find, it reboots itself roughly twice a day. Nothing in the syslog or console log, it looks basically like a power event...system comes back up with uncleanly dismounted file systems. However, it is on very clean power, has dual power supplies and none of the other boxes on that circuit has any pwer problems. It sounds like hardware trouble to me. I had a box go buggy on me after it had been running for a long time. After I powered it on again it became unstable. I suspect some part in the powersupply or on the mobo got fried. But there are some things you could check. Get syslog to log to another machine. That way you can check at which time the reboots happen. If they are regular, there might be a connection to running programs, cron jobs etc. On boot, I had noticed some complaints about ACPI, but I even tried disabling it, but it still did this several hours later. The ONLY hardware change I'd made was to remove a SCSI passthrough cable that enabled the on-board SCSI (it's an L440GX+) to be used with an external tape drive. Check all internal connections; cables, and PCI cards if any. Check if the RAM is properly seated. Maybe run a RAM test. Check the board for bad capacitators. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpnnU87a1DMK.pgp Description: PGP signature
Re: Problems with Mitsumi 7-in-1 USB Card Reader/Floppy combo
Thanks again for the help. If you require beta testers, just e-mail me to let me know. On 9/5/06, Hans Petter Selasky [EMAIL PROTECTED] wrote: On Tuesday 05 September 2006 13:28, Indigo 23 wrote: Thanks for that excellent suggestion. It worked perfectly. I just have a few questions. 1) Any idea when this will be imported in to RELENG_6? I don't know. If I am right, you will see my driver in freebsd-current some time after Christmas. 2) I have to do this everytime I update my sources, correct? Yes. 3) This is relatively stable, correct? (I did test it out a bit, but of course not thorougly enough to see how stable it is) Yes, it is stable, but be aware that if your system runs low on memory, you can get a panic saying, sleeping with mutex XXX locked, or something alike. That is because the umass device driver is still under the USB emulation layer of the old USB API, which is depreciated, and will be removed once I have completed the conversion of all USB device drivers. This will most likely happen before the end of this month. Then I need some help testing all the rewritten USB device drivers. --HPS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
em0: watchdog timeout -- resetting (6.1-STABLE)
Hello, I get these errors a lot. Sep 5 11:55:12 ronald kernel: em0: watchdog timeout -- resetting Sep 5 11:55:12 ronald kernel: em0: link state changed to DOWN Sep 5 11:55:14 ronald kernel: em0: link state changed to UP Sep 5 12:00:37 ronald kernel: em0: watchdog timeout -- resetting Sep 5 12:00:37 ronald kernel: em0: link state changed to DOWN Sep 5 12:00:39 ronald kernel: em0: link state changed to UP I tried turning off rxcsum/txcsum and set these sysctl's. dev.em.0.rx_int_delay: 0 dev.em.0.tx_int_delay: 0 (default 66) But the error is still there. Searching the internet and the list provides more of the same problems, but I didn't find an answer. My dmesg is attached. Is there any info I need to provide to debug this or can I try patches? Ronald. -- Ronald Klop Amsterdam, The Netherlands dmesg.boot Description: Binary data ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sqlz bgvnmloi o
You recently sent mail to [EMAIL PROTECTED] The e-mail address, [EMAIL PROTECTED], has been changed. The new e-mail address is [EMAIL PROTECTED] Your mail was forwarded to the new address; you do not need to resend it. This message was sent automatically. No reply is necessary. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em0: watchdog timeout -- resetting (6.1-STABLE)
On Tuesday 05 September 2006 14:52, Ronald Klop wrote: Hello, I get these errors a lot. Sep 5 11:55:12 ronald kernel: em0: watchdog timeout -- resetting Sep 5 11:55:12 ronald kernel: em0: link state changed to DOWN Sep 5 11:55:14 ronald kernel: em0: link state changed to UP Sep 5 12:00:37 ronald kernel: em0: watchdog timeout -- resetting Sep 5 12:00:37 ronald kernel: em0: link state changed to DOWN Sep 5 12:00:39 ronald kernel: em0: link state changed to UP So am I. Especially when I transfer a GB or 2 from Windows XP to 6.1-stable. I use the FreeBSD machine as a backup for digital photos and my ripped mp3 files. A photo session is usually in excess of 1 GB and can hang with the watchdog timeout. Kent I tried turning off rxcsum/txcsum and set these sysctl's. dev.em.0.rx_int_delay: 0 dev.em.0.tx_int_delay: 0 (default 66) But the error is still there. Searching the internet and the list provides more of the same problems, but I didn't find an answer. My dmesg is attached. Is there any info I need to provide to debug this or can I try patches? Ronald. -- Kent Stewart Richland, WA http://www.soyandina.com/ I am Andean project. http://users.owt.com/kstewart/index.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports Update: Failed to Generate INDEX
Ricardo Nabinger Sanchez wrote: IIRC, you must have all the ports (ports-all in your config file) in order to generate an INDEX, as it will fail otherwise. Yeah, when I realized that I interrupted the cvsup command, edited ports-supfile to change it to ports-all, then reran cvsup. Perhaps interrupting it the first time is what caused the problem. -Ron T. -- Ron Tarrant Blog:A HREF=http://www.writingup.com/blog/phpgtk2;PHP-Gtk2/A ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports Update: Failed to Generate INDEX
Wolfgang Zenker wrote: just to make sure: You did run cvsup after uncommenting ports-all and before running portsdb -Uu, right? Yes. I double-checked the command history and I definitely did. -Ron T. -- Ron Tarrant Blog:A HREF=http://www.writingup.com/blog/phpgtk2;PHP-Gtk2/A ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports Update: Failed to Generate INDEX
Kris Kennaway wrote: This makes me think that you didn't re-run cvsup since your similar error is precisely what you'd expect if you didn't have anything in japanese/. It's there in my command history twice with an ee ports-supfile between the two occurances of cvsup. BTW, this is the exact command with arguments: cvsup -g -L 2 ports-supfile Also, I ran this while pwd was /root/ Perhaps I should have been in /usr/ports? -Ron T. -- Ron Tarrant Blog:A HREF=http://www.writingup.com/blog/phpgtk2;PHP-Gtk2/A ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports Update: Failed to Generate INDEX
Hi Daniel,
Welcome to the discussion.
Daniel Eischen wrote:
I've seen errors similar to yours when your Mk files are out of
date with the rest of your ports tree. As root:
# cd /usr/ports/Mk
# cvs -R update -P -d
I'm assuming that the rest of your ports tree has also been
updated accordingly ('cd /usr/ports; cvs -R update -P -d').
Okay, now I'm confused. I thought updating the ports tree was done with:
cvsup -g -L 2 ports-supfile
-Ron T.
--
Ron Tarrant
Blog:A HREF=http://www.writingup.com/blog/phpgtk2;PHP-Gtk2/A
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: tcp/udp performance
Jack Vogel wrote: On 8/30/06, Danny Braniss [EMAIL PROTECTED] wrote: ever since 6.1 I've seen fluctuations in the performance of the em (Intel(R) PRO/1000 Gigabit Ethernet). motherboard OBN (On Board NIC) -- 1- Intel SE7501WV2S Intel 82546EB::2.1 2- Intel SE7320VP2D2INTEL 82541 3- Sun Fire X4100 ServerIntel(R) PRO/1000 test 1: writing to a NetApp filer via NFS/UDP FreeBSD Linux MegaBytes/sec 1- Average: 18.48 32.61 2- Average: 15.69 35.72 3- Average: 16.61 29.69 (interstingly, doing NFS/TCP instead of NFS/UDP shows an increase in speed of around 60% on FreeBSD but none on Linux) test2: iperf using 1 as server: FreeBSD(*) Linux Mbits/sec 1- 926 905 (this machine was busy) 2- 545 798 3- 910 912 *: did a 'sysctl net.inet.tcp.sendspace=65536' So, it seems to me something is not that good in the UDP department, but I can't find what to tweek. Any help? danny Have discussed this some internally, the best idea I've heard is that UDP is not giving us the interrupt rate that TCP would, so we end up not cleaning up as often, and thus descriptors might not be as quickly available.. Its just speculation at this point. If a high interrupt rate is a problem and your NIC+driver supports it, then try enabling polling(4) aswell. This has helped me for bulk transfers on slower boxes but i have noticed problems with ALTQ/dummynet and other highly realtime dependent networking code. YMMV. More info in the man 4 polling. I think recent linux kernels/drivers have this implemented so it will enable it dynamically on high load. However i only skimmed the documents and i'm not a linux expert so i may be wrong on that. /Junics as far as i know, polling only works on UP machines, besides, TCP performance is much better than UDP - which goes against basic instincts. the packets arriving at the NIC get processed - interrupt - before you can tell that they are IP/TCP/UDP, so the iterrupt latency should be the same for all. Try this: the default is only to have 256 descriptors, try going for the MAX which is 4K. Cheers, Jack ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
