Re: if_em int_throttle_ceil patch
On Fri, Dec 10, 2004 at 12:00:21PM +0900, Shunsuke SHINOMIYA wrote: The previous patch to change if_em's int_throttle_ceil into sysctl-able cause a kernel panic. If you set em's int_throttle_ceil=0 and then reconfigure the em, it cause a diveded by zero panic. This patch for original if_em.[ch] which is attached to this mail is corrected this problem. Great work Shunsuke, thank you ! Any chance to get this patch reviewed and commited ? Although Bjoern Zeeb proposed to use a global way to control interrupt moderation among network drivers, there was no proposition to unify it. It would be a pity if this patch gets lost in the archives without being either commited or submited as a PR. Regards, -- Jeremie Le Hen [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cvs commit: src/etc/rc.d jail src/etc/defaults rc.conf
On Sat, Dec 11, 2004, Kim Culhan wrote: Took a look at the latest -stable rc.conf, this is a fine thing. Are there any docs with more info on this new jail setup ? There is an example under Jail Configuration in /etc/default/rc.conf. And together with a patch which we are currently further discussing (see http://people.freebsd.org/~rse/work/jail-startstop.txt), you can boot and shutdown jails both automatically and more flexibly. In the above patch there is also an example how the per-jail fstabs work. -- [EMAIL PROTECTED]Ralf S. Engelschall FreeBSD.org/~rse [EMAIL PROTECTED] FreeBSD committer www.engelschall.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
5.3-R : jail bug ?
Hello, I'm having a serious problem with jails on my 5.3-RELEASE machine. When I stop a jail using '/etc/rc.d jail stop jail name' the jail stops but jls still shows it running. I have tried fstat, lsof, nothing is running in this jail, yet if there is a reason why jls says it is running, how can i kill it ? I thought it could be related to time but it's been 1 hour now since the jail has been stopped. ruby# ps aux | grep J root46737 0.0 0.2 1472 808 p3 S+ 12:37PM 0:00.01 grep J ruby# killall -j 9 No matching processes were found ruby# lsof | grep jail ruby# ruby# jls JID IP Address Hostname Path 9 10.0.0.17 green.vps.kmem.org /usr/local/jails/green.vps.kmem.org ruby# sysctl -a -o | grep jail security.jail.set_hostname_allowed: 0 security.jail.socket_unixiproute_only: 1 security.jail.sysvipc_allowed: 0 security.jail.getfsstatroot_only: 1 security.jail.allow_raw_sockets: 1 security.jail.list: Format:S Length:1292 Dump:0x010009002f7573722f6c6f63... security.jail.jailed: 0 - kernel : ruby# uname -a FreeBSD ruby.london.kmem.org 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Tue Nov 16 12:08:02 GMT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/EPIA i386 My kernel and world are in sync. I have looked on google and found the Following PR's that describes my problem but it is said to have been resolved. Guess not for me though :( http://www.freebsd.org/cgi/query-pr.cgi?pr=65442 http://www.freebsd.org/cgi/query-pr.cgi?pr=54163 My version of tcp_subr.c: ruby# grep FreeBSD /sys/netinet/tcp_subr.c * $FreeBSD: src/sys/netinet/tcp_subr.c,v 1.201.2.1.2.1 2004/10/21 09:30:47 rwatson Exp $ If there is any data/information missing here, please let me know and i will provide it. Thanks Tom ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
TIMEOUT - WRITE_DMA on SATA disc
Hello, My system produces these messages that I already know well from current list (as well ;): TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=213249674 I would like to report my experiences with 5.3 RELEASE/STABLE/B7 After these messages the two former cases result in FAILURE and finally in panic. Even background fsck cannot run without another panic, only single user mode can help. All these prevent using them on my HW. However B7, although displays the messages as well, works seemingly fine. For the time being, this version is sufficent, but I'd like to know - if possible at all - what the difference could be between the versions and if one can expect to bring the actual 5.3 version's state to B7's in this respect? I also found that pendrive's sensing by 5.3 RELEASE/STABLE more frequently results in panic than B7's. (As a matter of fact I have not seen panic with B7 for weeks since I installed it.) I use the following either with GENERIC or custom kernel: Abit NF7-S (nVidia chipsets, SiI3112 on board), Athlon 2600+, 114498MB SAMSUNG SP1213C/SV100-27 [232632/16/63] at ata2-master SATA150 LEXAR MEDIA JUMPDRIVE, rev 1.10/0.01 Please cc it to me as well, since I'am not on the list for the time being. Many thanks! Zsolt Zsolt Kuti ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3: ed1: Ethernet address: aa:aa:aa:aa:aa:aa
On Sat, Dec 11, 2004 at 12:07:32AM -0800, Marcel Moolenaar wrote: On Dec 10, 2004, at 9:18 PM, Bruce Burden wrote: I build a 5.3 kernel and source from source. When I booted, I got: Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-RELEASE-p2 #0: Fri Dec 10 22:48:56 GMT 2004 [EMAIL PROTECTED]:/home/obj/usr/src/sys/TIGERPROWL link_elf: symbol Debugger undefined KLD file acpi.ko - could not finalize loading You might want to resolve this first. I don't know what you load as modules, but what you're booting is inconsistent. This may apply to pccard or if_ed and possibly the root cause of your problems. Just a suggestion, Hi Marcel, I do not believe that is a problem. For one, I was booting with the ACPI turned off, via the boot menu. For two, last week, when I booted 5.3 from the 5.3 disk set, I had the same problem with ed1, which used the 5.3 binaries. This attempt used the 5.2.1 binaries with a 5.3 kernel, as I was upgrading, which may explain the link_elf: symbol Debugger undefined. However, if it is shown this is the problem, and how to deal with it, I'll do so... Bruce -- I like bad! Bruce BurdenAustin, TX. - Thuganlitha The Power and the Prophet Robert Don Hughes ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hushlogin attribute
--- Lowell Gilbert [EMAIL PROTECTED] wrote: Rostislav Krasny [EMAIL PROTECTED] writes: --- Rostislav Krasny [EMAIL PROTECTED] wrote: Hello. The hushlogin attribute doesn't work when it is added to me record of ~/.login_conf or to default record of /etc/login.conf. However, having ~/.hushlogin file does its job well. Is it a bug or am I missing something? uname -a FreeBSD saturn 5.3-RELEASE-p2 FreeBSD 5.3-RELEASE-p2 #1: Fri Dec 3 13:57:01 IST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MYKERNEL i386 If I run 'cap_mkdb /etc/login.conf' after the /etc/login.conf was changed the hushlogin attribute works. But I can't find any way to make hushlogin attribute work from the ~/.login_conf. Running 'cap_mkdb ~/.login_conf' doesn't help. Is it possibly to make the hushlogin attribute work from ~/.login_conf file? P.S. IMHO the login.conf(5) manual page should say something about the /etc/login.conf.db file and its preferable usage by login(1). The first eight lines of login.conf cover this quite well. Yes, there are few words about one should run 'cap_mkdb /etc/login.conf' after each change. But this is not what I propose to add to the manual page and /etc/login.conf is not a manual page by itself. At first I wasn't pay attention to these lines at all because I already read the manual and I instinctively wasn't expected to find any new information in /etc/login.conf. FreeBSD 4.8 Errata have a much better explanation than lines 3 and 5 on /etc/login.conf. Why not to add something like that to the login.conf(5) manual page? By the way, do you know why hushlogin attribute doesn't work from the ~/.login_conf or how it can work from there? Thank you in advance. __ Do you Yahoo!? The all-new My Yahoo! - What will yours do? http://my.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Timecounter problems on 5.3 - things take twice as long
Hey Doug, On Tue, 7 Dec 2004 12:57:01 -0800 (PST), Doug White [EMAIL PROTECTED] wrote: On Tue, 7 Dec 2004, Arjan Van Leeuwen wrote: In other words, exactly the same thing. I should also note that earlier versions of 5-CURRENT worked correctly (-CURRENT from june 7). Is there anything else I could try? Replace the motherboard? :) The i8254 hasn't changed in years, so I doubt we're programming it wrong. Something along the way is applying a /2 divisor. Maybe its been broken forever and you only recnetly noticed due to the HZ change? Heh :). No, this is on 5.3-RELEASE and I've been running with HZ=1000 for a long time, because I use DUMMYNET. Good to know. Can you try booting an old kernel, or booting 5.2.1-R and see if it shows up there too? If it works with 5.2.1, then I'd start playing the binary-search game to find the commit(s) that broke you. Sorry for the late reply, I needed some time to try out older kernels. Looks like it's a hardware fault. Kernels that worked correctly in the past have the same problems if I boot them now. It probably had nothing to do with me upgrading to 5.3-RELEASE at all. Thanks for the help, Arjan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3: ed1: Ethernet address: aa:aa:aa:aa:aa:aa
On Dec 10, 2004, at 9:18 PM, Bruce Burden wrote: I build a 5.3 kernel and source from source. When I booted, I got: Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-RELEASE-p2 #0: Fri Dec 10 22:48:56 GMT 2004 [EMAIL PROTECTED]:/home/obj/usr/src/sys/TIGERPROWL link_elf: symbol Debugger undefined KLD file acpi.ko - could not finalize loading You might want to resolve this first. I don't know what you load as modules, but what you're booting is inconsistent. This may apply to pccard or if_ed and possibly the root cause of your problems. Just a suggestion, -- Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
hushlogin attribute
Hello. The hushlogin attribute doesn't work when it is added to me record of ~/.login_conf or to default record of /etc/login.conf. However, having ~/.hushlogin file does its job well. Is it a bug or am I missing something? uname -a FreeBSD saturn 5.3-RELEASE-p2 FreeBSD 5.3-RELEASE-p2 #1: Fri Dec 3 13:57:01 IST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MYKERNEL i386 __ Do you Yahoo!? Yahoo! Mail - 250MB free storage. Do more. Manage less. http://info.mail.yahoo.com/mail_250 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: cvs commit: src/etc/rc.d jail src/etc/defaults rc.conf
Ralf- Took a look at the latest -stable rc.conf, this is a fine thing. Are there any docs with more info on this new jail setup ? I've been running some 'virtual machines' for some time and I'd like to convert to this latest method for running jails. -kim __ Do you Yahoo!? Yahoo! Mail - Helps protect you from nasty viruses. http://promotions.yahoo.com/new_mail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hw.ata.ata_dma=0: can I do this during bootup at the
It would be nice if I can set hw.ata.ata_dma=0 at the loader prompt during bootup, so that the system at least will boot from harddisk. Is that possible? Yes, that's possible. Drop the loader to the prompt and do the following: set hw.ata.ata_dma=0 boot btw: I have a similar problems, but not with the boot disc, but one of my data drives, thus I want ata_dma enabled for the other discs. I have to dispatch a atacontrol mode 1 foo UDMA33 to set this drive (slave on second controller) to UDMA33 (otherwise it would use UDMA100). But I have to do it before /etc/rc.d/fsck starts accessing the device. Right now I've added above line to the beginning of aforesaid script. Is there a nicer/better place to tell the kernel (don't like editing the rc-scripts). You can use /etc/rc.early for that. You'll have to create it if it doesn't yet exist. Put 'atacontrol mode 1 foo UDMA33' in it, and it should execute that command before mounting the drives. Note that you can put this in loader.conf as well - if you're having trouble booting the system to do it, boot to safe mode - should get you in. I have an old Aladdin V with a buggy UDMA chipset, and doing this fixed the problem rather nicely. -- Erik Hollensbe [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hushlogin attribute
--- Rostislav Krasny [EMAIL PROTECTED] wrote: Hello. The hushlogin attribute doesn't work when it is added to me record of ~/.login_conf or to default record of /etc/login.conf. However, having ~/.hushlogin file does its job well. Is it a bug or am I missing something? uname -a FreeBSD saturn 5.3-RELEASE-p2 FreeBSD 5.3-RELEASE-p2 #1: Fri Dec 3 13:57:01 IST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MYKERNEL i386 If I run 'cap_mkdb /etc/login.conf' after the /etc/login.conf was changed the hushlogin attribute works. But I can't find any way to make hushlogin attribute work from the ~/.login_conf. Running 'cap_mkdb ~/.login_conf' doesn't help. Is it possibly to make the hushlogin attribute work from ~/.login_conf file? P.S. IMHO the login.conf(5) manual page should say something about the /etc/login.conf.db file and its preferable usage by login(1). __ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hushlogin attribute
Rostislav Krasny [EMAIL PROTECTED] writes: --- Rostislav Krasny [EMAIL PROTECTED] wrote: Hello. The hushlogin attribute doesn't work when it is added to me record of ~/.login_conf or to default record of /etc/login.conf. However, having ~/.hushlogin file does its job well. Is it a bug or am I missing something? uname -a FreeBSD saturn 5.3-RELEASE-p2 FreeBSD 5.3-RELEASE-p2 #1: Fri Dec 3 13:57:01 IST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MYKERNEL i386 If I run 'cap_mkdb /etc/login.conf' after the /etc/login.conf was changed the hushlogin attribute works. But I can't find any way to make hushlogin attribute work from the ~/.login_conf. Running 'cap_mkdb ~/.login_conf' doesn't help. Is it possibly to make the hushlogin attribute work from ~/.login_conf file? P.S. IMHO the login.conf(5) manual page should say something about the /etc/login.conf.db file and its preferable usage by login(1). The first eight lines of login.conf cover this quite well. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
latest -stable ucom0 not created
Just upgraded to the latest -stable. When I try to use tip with /dev/com0 it returns: /dev/ucom0: No such file or directory link down I added device ucom and device ubsa to the kernel config but this did not help. Any help here is greatly appreciated. -kim __ Do you Yahoo!? Send holiday email and support a worthy cause. Do good. http://celebrity.mail.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
