Re: em(4) on FreeBSD is sometimes annoying
Am Sat, 02 Aug 2008 23:50:10 +0200 schrieb Torfinn Ingolfsen [EMAIL PROTECTED]: On Sat, 02 Aug 2008 22:40:46 +0200 Martin [EMAIL PROTECTED] wrote: good point, no. The problem appears when the first thing called on this interface is dhclient (caused by ifconfig_em0=DHCP). I could So, if you don't automatically configure the interface, but instead do something like: 'ifconfig em0 up' and then the DHCP stuff does the interface work then? Hi Torfinn, I've put /sbin/ifconfig em0 up into rc.local. Now the behavior is slightly different. Steps: 1) I switch laptop on with cable unplugged. Everything ok (DHCP failed, of course; this is normal). 2) I plug the cable in: state: active. Yay! This is OK! 3) NIC does not get IP (one time it got the correct IP but the it lost it again, I could see by repeatedly typing ifconfig em0). 4) I kill the dhclient. 5) I manually start dhclient em0. No response (DHCPREQUEST, DHCPDISCOVER, does not finish). 6) I start ifconfig em0 down and once again dhclient em0 (this time without ifconfig em0 up!). 7) Got an IP, without delays (as it should be). -- Martin signature.asc Description: PGP signature
Portmaster questions (Was: Re: Using Portupgrade?)
Alex Goncharov wrote: ,--- You/Jeremy (Sun, 3 Aug 2008 19:26:18 -0700) * | I'd start by ceasing use of portupgrade. Try Doug Barton's portmaster, | which is in ports/ports-mgmt/portmaster. It's an extensive shell | script, and does not require ruby. Over the last couple of months, I've made a few shy attempts to switch from `portupgrade' to 'portmaster', but every time I try it, I find something that keeps me using the former. Don't remember everything of that sort but here are a couple of things I would like to ask portmaster users' opinion and advice about: 1. I see a significant difference in the time it takes to get the same information using the two tools: -- # time portversion -v | wc -l 473 real0m3.772s user0m2.462s sys 0m1.114s # time portmaster -L | wc -l 488 real0m50.042s user0m29.762s sys 0m15.470s -- I run `portversion' a lot, and this kind of performance difference is one argument for sticking with `portupgrade'. You do not have to run portversion or portmaster or any other 3rd party tool to check versions of installed ports. Use pkg_version which is included in base system and then you are independent of port management tools changes. portversion is using INDEX, portmaster not. pkg_version (by default) do not use INDEX, but have option to use it and then become clear winner (in speed): portmaster -L Usr: 11.431s Krnl: 4.179s Totl: 0:15.96s portversion -v Usr: 2.076s Krnl: 0.615s Totl: 0:02.75s pkg_version -v Usr: 9.803s Krnl: 3.183s Totl: 0:13.23s ## using INDEX, see man pkg_version for details ## pkg_version -vI Usr: 0.233s Krnl: 0.041s Totl: 0:00.31s With INDEX you can see results almost immediately: # time pkg_version -vIL = amavisd-new-2.5.4,1 needs updating (index has 2.6.1,1) awstats-6.7,1needs updating (index has 6.8_1,1) courier-authlib-base-0.60.6 needs updating (index has 0.61.0) courier-authlib-mysql-0.60.6 needs updating (index has 0.61.0) mod_python-3.3.1 needs updating (index has 3.3.1_1) nmap-4.62needs updating (index has 4.68) openvpn-2.0.6_8 needs updating (index has 2.0.6_9) py25-docutils-0.4needs updating (index has 0.5) py25-pygments-0.9needs updating (index has 0.10) subversion-python-1.4.6_2needs updating (index has 1.5.1) trac-0.10.4_1needs updating (index has 0.11_2) trac-ctxtnavaddplugin-1.1.r1 needs updating (index has 1.1.r1_2) trac-iniadmin-0.1needs updating (index has 0.1_2) Usr: 0.227s Krnl: 0.036s Totl: 0:00.27s CPU: 92.5% As I had problems with portupgrade's handling of dependencies, I am converted to portmaster. Only one feature that I am missing in portmaster is ability to do something before / after application install / upgrade (eg: restart of daemon, directory permission setting, backup of configs etc.) Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em(4) on FreeBSD is sometimes annoying
Am Sat, 2 Aug 2008 16:01:35 -0700 schrieb Jack Vogel [EMAIL PROTECTED]: Hi, After I typed /etc/rc.d/netif restart, I waited until I get giving up message. Then I plugged the cable in. After about 30 seconds the link LED was on. I noticed that at this point I couldn't get an address using DHCP. Well DUH, the agent exited, thats why it said giving up :) That ain't complex behavior, its behaving as designed. I'm describing the circumstances WHEN everything happens. I was trying to show you that even the cable is plugged in you cannot get an IP. The NIC is in a kind of dead state. Ya, so the update is slow, the fact that the LED is blinking means you have an autoneg failure, so again, its your switch not the NIC. I have this problem with every kind of switch. The switch at home is a 100Mbit switch made by Digitus (5-port). Let me guess, you have some 100Mb home router and you are trying to plug a gig nic into it and forcing the speed maybe? This is true except for the forcing the speed part. It's set to media: Ethernet autoselect. I asked for a hardware list, now that includes the switch. Digitus DN-5001C: http://www.amazon.de/Assmann-Digitus-DN-5001C-Switch-Fast/dp/B0009FHTWI -- Martin signature.asc Description: PGP signature
Re: em(4) on FreeBSD is sometimes annoying
On Mon, Aug 04, 2008 at 10:53:35AM +0200, Martin wrote: Am Sat, 2 Aug 2008 16:01:35 -0700 schrieb Jack Vogel [EMAIL PROTECTED]: After I typed /etc/rc.d/netif restart, I waited until I get giving up message. Then I plugged the cable in. After about 30 seconds the link LED was on. I noticed that at this point I couldn't get an address using DHCP. Well DUH, the agent exited, thats why it said giving up :) That ain't complex behavior, its behaving as designed. I'm describing the circumstances WHEN everything happens. I was trying to show you that even the cable is plugged in you cannot get an IP. The NIC is in a kind of dead state. Ya, so the update is slow, the fact that the LED is blinking means you have an autoneg failure, so again, its your switch not the NIC. I have this problem with every kind of switch. The switch at home is a 100Mbit switch made by Digitus (5-port). Can you try repeating the problem under Linux? It may be a bit much to ask, but I believe there's an Ubuntu Live CD you can download + burn + boot. You could try repeating the behaviour there. If it's identical, or at least still broken, then it's less likely FreeBSD's fault. Let me guess, you have some 100Mb home router and you are trying to plug a gig nic into it and forcing the speed maybe? This is true except for the forcing the speed part. It's set to media: Ethernet autoselect. Which means it's using auto-neg, which Jack says (based on the information he has) may be failing upon link loss + reconnect. As described, auto-negotiation has to be properly implemented on both the NIC/PHY and on the switch, as well as handled properly in the NIC driver. I can tell you that in the case of the Intel 82573E and FreeBSD's em(4) driver (version 6.x.x), auto-neg is performed properly, including when link is lost/cable pulled. I've personally tested this on numerous consumer switches (D-Link, Linksys, and Hawking Technologies), as well as enterprise switches (specifically ProCurve and Cisco). I can tell you that I've seen odd speed negotiation failures with Netgear consumer switches (100mbit being chosen instead of gigE). In fact, this weekend in my home, I just migrated from a D-Link switch to an HP ProCurve switch. I powered off one switch, installed the new one, powered it on, and link came up. Took a couple minutes. But then I decided to re-organise some of my cabling, which caused another disconnect. Here's evidence: em0: Intel(R) PRO/1000 Network Connection 6.9.5 port 0x4000-0x401f mem 0xe800-0xe801 irq 16 at device 0.0 on pci13 em0: Using MSI interrupt em0: [FILTER] em0: Ethernet address: 00:30:48:97:25:40 [EMAIL PROTECTED]:13:0:0:class=0x02 card=0x108c15d9 chip=0x108c8086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82573E Intel Corporation 82573E Gigabit Ethernet Controller (Copper)' class = network subclass = ethernet icarus# bzgrep kernel: em0 /var/log/all.log.3.bz2 Jul 31 06:28:23 icarus kernel: em0: link state changed to DOWN Jul 31 06:30:17 icarus kernel: em0: link state changed to UP Jul 31 06:32:36 icarus kernel: em0: link state changed to DOWN Jul 31 06:32:53 icarus kernel: em0: link state changed to UP And absolutely no problems: icarus# netstat -in -I em0 NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll em01500 Link#1 00:30:48:97:25:40 32941661 0 34620277 0 0 em01500 192.168.1.0/2 192.168.1.51 32915748 - 35942133 - - icarus# ifconfig em0 em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4 ether 00:30:48:97:25:40 inet 192.168.1.51 netmask 0xff00 broadcast 192.168.1.255 media: Ethernet autoselect (1000baseTX full-duplex) status: active What I'm saying is I don't know what to tell you. I'm not doubting your claims, but it would be worthwhile to test on Linux to see if it's a FreeBSD driver issue, something with the NIC/PHY, the way the NIC/PHY is implemented on the computer, or even the cable (yes really!). I'd start with the obvious: try replacing the cable, and go with a CAT5e cable that's pre-made (rather than self-rolled, if you're using such). -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em(4) on FreeBSD is sometimes annoying
On Sat, 2 Aug 2008 10:34:47 -0700 Jack Vogel [EMAIL PROTECTED] wrote: Telling me what kind of NIC it is isn't going to help, 82573's are working the world over :) What exactly is your laptop, what model, is the NIC a LOM (on the motherboard) or some addin. Hi Jack, this is a Lenovo Thinkpad T60p model 2007-93G. It's the standard built-in NIC by Lenovo on the mainboard. There should be NO need to specify full duplex, if you have to do that then you have some problem with your switch. No, I don't have to specify full duplex. Earlier someone has asked me if it might be some problem with the autonegotiation. I don't think it is. Are you loading the driver as a module, or is it static? Static. So, if you do this: get a cable and eliminate any switch, just a back to back connection between two machines, then if you load the driver and ifconfig address up... what happens?? Ok, I've done that. I connected my laptop directly to my home router. At the other side we have an xl(4) NIC, btw. Faulty variant: 1) Boot with cable disconnected. DHCP fails, of course, which is ok. 2) I plug in the cable where on the other side sits xl(4). ifconfig shows me no carrier, all LEDs at the NIC are off. No way to get an IP. No way to get status: active, by ifconfig em0 up/down. Ok: 1) Boot with cable directly connected to xl(4) at the other side. 2) em0 gets instantly an IP from DHCP server running on xl(4). -- Martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em(4) on FreeBSD is sometimes annoying
Martin [EMAIL PROTECTED] wrote: On Sat, 02 Aug 2008 12:55:53 +0200 Torfinn Ingolfsen [EMAIL PROTECTED] wrote: Just to be sure: also if the first command you try on the interface is 'ifconfig up'? Hello Torfinn, good point, no. The problem appears when the first thing called on this interface is dhclient (caused by ifconfig_em0=DHCP). I could also provoke this behavior after the interface was once up had an IP and was working (ping). All I need to do is to disconnect the NIC from the switch when I type /etc/rc.d/netif restart. I have noticed further strange effects here. The behavior seems to be even more complex. After I typed /etc/rc.d/netif restart, I waited until I get giving up message. Then I plugged the cable in. After about 30 seconds the link LED was on. I noticed that at this point I couldn't get an address using DHCP. So I disconnected physically the NIC (no cable) and link LED was still on! ifconfig showed me state: active with no cable plugged in. After further 30 seconds the LED went off. I attached the NIC again to the switch again and after 30 seconds again I got some other effect. The link LED went on (status: active) and the data LED was permanently blinking (about 2,5 times a second). I pulled the cable again and now the link LED is still on and the data LED still blinking (since about 10 minutes already). By the way... Now I'm typing this E-Mail without an ethernet cable plugged in and the link status LED is still on and the other data LED is blinking. -- Martin I may have misunderstood the purpose of this, but do you have the bpf compiled into your kernel? If you're having DHCP troubles, this could be a problem. Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em(4) on FreeBSD is sometimes annoying
2008/8/4 Jeremy Chadwick [EMAIL PROTECTED]: On Mon, Aug 04, 2008 at 11:00:16AM +0100, Chris Rees wrote: Martin [EMAIL PROTECTED] wrote: On Sat, 02 Aug 2008 12:55:53 +0200 Torfinn Ingolfsen [EMAIL PROTECTED] wrote: Just to be sure: also if the first command you try on the interface is 'ifconfig up'? Hello Torfinn, good point, no. The problem appears when the first thing called on this interface is dhclient (caused by ifconfig_em0=DHCP). I could also provoke this behavior after the interface was once up had an IP and was working (ping). All I need to do is to disconnect the NIC from the switch when I type /etc/rc.d/netif restart. I have noticed further strange effects here. The behavior seems to be even more complex. After I typed /etc/rc.d/netif restart, I waited until I get giving up message. Then I plugged the cable in. After about 30 seconds the link LED was on. I noticed that at this point I couldn't get an address using DHCP. So I disconnected physically the NIC (no cable) and link LED was still on! ifconfig showed me state: active with no cable plugged in. After further 30 seconds the LED went off. I attached the NIC again to the switch again and after 30 seconds again I got some other effect. The link LED went on (status: active) and the data LED was permanently blinking (about 2,5 times a second). I pulled the cable again and now the link LED is still on and the data LED still blinking (since about 10 minutes already). By the way... Now I'm typing this E-Mail without an ethernet cable plugged in and the link status LED is still on and the other data LED is blinking. -- Martin I may have misunderstood the purpose of this, but do you have the bpf compiled into your kernel? If you're having DHCP troubles, this could be a problem. I have never seen device bpf cause any sort of DHCP-related problems on FreeBSD. Can you expand on this, and provide reference material confirming such? -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | Sorry, I was referring to the possible absence of it. Ref: http://www.freebsd.org/doc/en/books/handbook/network-dhcp.html , section 27.5.4: Make sure that the bpf device is compiled into your kernel. To do this, add device bpf to your kernel configuration file, and rebuild the kernel. Chris -- R $h ! $- ! $+ $@ $2 @ $1 .UUCP. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em(4) on FreeBSD is sometimes annoying
On Mon, Aug 04, 2008 at 11:00:16AM +0100, Chris Rees wrote: Martin [EMAIL PROTECTED] wrote: On Sat, 02 Aug 2008 12:55:53 +0200 Torfinn Ingolfsen [EMAIL PROTECTED] wrote: Just to be sure: also if the first command you try on the interface is 'ifconfig up'? Hello Torfinn, good point, no. The problem appears when the first thing called on this interface is dhclient (caused by ifconfig_em0=DHCP). I could also provoke this behavior after the interface was once up had an IP and was working (ping). All I need to do is to disconnect the NIC from the switch when I type /etc/rc.d/netif restart. I have noticed further strange effects here. The behavior seems to be even more complex. After I typed /etc/rc.d/netif restart, I waited until I get giving up message. Then I plugged the cable in. After about 30 seconds the link LED was on. I noticed that at this point I couldn't get an address using DHCP. So I disconnected physically the NIC (no cable) and link LED was still on! ifconfig showed me state: active with no cable plugged in. After further 30 seconds the LED went off. I attached the NIC again to the switch again and after 30 seconds again I got some other effect. The link LED went on (status: active) and the data LED was permanently blinking (about 2,5 times a second). I pulled the cable again and now the link LED is still on and the data LED still blinking (since about 10 minutes already). By the way... Now I'm typing this E-Mail without an ethernet cable plugged in and the link status LED is still on and the other data LED is blinking. -- Martin I may have misunderstood the purpose of this, but do you have the bpf compiled into your kernel? If you're having DHCP troubles, this could be a problem. I have never seen device bpf cause any sort of DHCP-related problems on FreeBSD. Can you expand on this, and provide reference material confirming such? -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em(4) on FreeBSD is sometimes annoying
On Mon, Aug 04, 2008 at 11:34:48AM +0200, Martin wrote: On Sat, 2 Aug 2008 10:34:47 -0700 Jack Vogel [EMAIL PROTECTED] wrote: Telling me what kind of NIC it is isn't going to help, 82573's are working the world over :) What exactly is your laptop, what model, is the NIC a LOM (on the motherboard) or some addin. Hi Jack, this is a Lenovo Thinkpad T60p model 2007-93G. It's the standard built-in NIC by Lenovo on the mainboard. I also have a T60p (though a different model/type number). Note that the BIOSes for the T60p have historically documented numerous changes to how the NIC is initialised and fiddled with, **especially** if PXE booting is enabled (regardless if a PXE boot itself is performed or not). My employer sent a company-wide message to all owners of the T60p asking that they upgrade their BIOS solely to address link negotiation failures occasionally seen when PXE booting. Meaning: I would not be surprised if this issue proved to be something specific to Lenovo laptops, possibly this model. When I return to work on Wednesday night, I'll try to reproduce what you see (we have Juniper, Cisco, Extreme, and Netgear switches there), then bring the laptop home and test against a D-Link switch, as well as my ProCurve. I can tell you that I have absolutely no problems under Windows Vista when pulling the CAT5 cable out and reinserting it; and yes, DHCP is used. (I do this literally on a nightly basis, which is how/why I'm so sure.) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em(4) on FreeBSD is sometimes annoying
Am Mon, 4 Aug 2008 03:23:07 -0700 schrieb Jeremy Chadwick [EMAIL PROTECTED]: When I return to work on Wednesday night, I'll try to reproduce what you see (we have Juniper, Cisco, Extreme, and Netgear switches there), then bring the laptop home and test against a D-Link switch, as well as my ProCurve. Hi Jeremy, I'm trying some other things here. Before you waste time on PEBKAC problems ;) (which I now suspect to be). Let me try to install the latest GENERIC on my laptop first. I have made some modifications with polling and some other stuff like HZ and zero copy sockets. I tried several things now: Windows XP worked fine. Ubuntu also. FreeBSD 7.0R install CD works, too. Of course, there might be some other things from userland that cause the problem and that don't run during install (powerd?). I have to check it first to narrow down the problem. Thanks to all people here for helping me so far. I would not get that many ideas what to look at, if I hadn't asked. Sometimes, I expect too much to run flawlessly together, I think. I will tell more when I have checked the things I mentioned. -- Martin signature.asc Description: PGP signature
Re: em(4) on FreeBSD is sometimes annoying
Am Mon, 4 Aug 2008 12:51:38 +0200 schrieb Martin [EMAIL PROTECTED]: I'm trying some other things here. Before you waste time on PEBKAC problems ;) (which I now suspect to be). Let me try to install the latest GENERIC on my laptop first. I've build fresh world and then kernel (GENERIC configuration), I also removed everything from rc.conf except host name assignment, and ifconfig_re0=DHCP. I have still same effect as described before. Booting without ethernet cable will prevent me to get link status: active on em(4), when I try to use it later. GENERIC from FreeBSD 7.0 CD installation works fine. I checked it again. I can boot without cable in my NIC, try to assign an IP using DHCP and then plug the cable in and I have link. Is there a difference how /etc/rc.d/netif handles a NIC with DHCP and how the installation CD is handling it? Once again, steps to reproduce this behavior: 1) Power the laptop OFF. Really OFF, I mean. No reboots! 2) Detach the cable from NIC. 3) Boot FreeBSD. Let it pass the DHCP phase (ifconfig_em0=DHCP) until login appears. 4) Attach the cable to the NIC. 5) Voila... no link. -- Martin signature.asc Description: PGP signature
Re: Portmaster questions (Was: Re: Using Portupgrade?)
On Sun, 03 Aug 2008 22:14:54 -0700, Doug Barton wrote: It's really not appropriate to hijack the portupgrade thread for this, so I'm starting a new subject. Also, please respect followups to -ports. Alex Goncharov wrote: Don't remember everything of that sort but here are a couple of things I would like to ask portmaster users' opinion and advice about: 1. I see a significant difference in the time it takes to get the same information using the two tools: As I understand it, portupgrade uses the INDEX file to determine whether ports are up to date. Actually I think it uses bdb cache of index (INDEX-7.db) and also lies about it (says up-to-date with port instead of up-to-date with index). It's not even doing a good job at it, standard pkg_version significantly outperforms it: # time portversion -v | wc -l 769 real0m15.027s user0m9.235s sys 0m5.173s # time pkg_version -Iv | wc -l 769 real0m4.707s user0m3.648s sys 0m0.798s ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DigiBoard Xem with 2 extenal modules
On 7/4/08, Alexandre Biancalana [EMAIL PROTECTED] wrote:
On 7/4/08, Gavin Atkinson [EMAIL PROTECTED] wrote:
It's not a solution, but it may well be a great help in diagnosing where
the problem lies: it would be useful to know if the driver is simply
failing to detect the correct number of ports, or if the driver
physically cannot use them.
In /usr/src/sys/dev/digi/digi.c, line 510, you'll see the following
code:
if (sc-numports == 0) {
device_printf(sc-dev, %s, 0 ports found\n, sc-name);
sc-hidewin(sc);
return (0);
}
Just before that section, can you add a line sc-numports = 32;,
recompile, and see if the missing 16 ports are usable? If they are, I
suspect fixing the driver will be trivial.
Wow !! Now the 32 ports are detected and devices created.
# digictl -d 1 -r /dev/digi0.ctl
digi0: Got init reset after 0 us
digi0: BIOS uploaded
digi0: BIOS started after 0 us
digi0: BIOS booted after 1619 iterations
digi0: Loading FEP/OS
digi0: FEP/OS loaded
digi0: FEP/OS started after 28 iterations
digi0: Digiboard PCI PC/Xem ASIC, 32 ports found
# ls /dev/cuaD?? | wc -l
32
I will connect some modems to that ports to test and let you know.
Modems connected but they only work on ports of the first module, any
decice connected on ports of second module does not work.
Any other idea ?
Thank you
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em(4) on FreeBSD is sometimes annoying
The focus here on the laptop distracted me, but someone else at work reminded me. Its very important that you run the EEPROM fix for the 82573 that i posted a long while back, search in email archive for it. Its a DOS executable that will patch your EEPROM. I am not sure if the Lenova's need it, but get it, run it, and then see if your problem goes away. Jack On Mon, Aug 4, 2008 at 8:44 AM, Martin [EMAIL PROTECTED] wrote: Am Mon, 4 Aug 2008 12:51:38 +0200 schrieb Martin [EMAIL PROTECTED]: I'm trying some other things here. Before you waste time on PEBKAC problems ;) (which I now suspect to be). Let me try to install the latest GENERIC on my laptop first. I've build fresh world and then kernel (GENERIC configuration), I also removed everything from rc.conf except host name assignment, and ifconfig_re0=DHCP. I have still same effect as described before. Booting without ethernet cable will prevent me to get link status: active on em(4), when I try to use it later. GENERIC from FreeBSD 7.0 CD installation works fine. I checked it again. I can boot without cable in my NIC, try to assign an IP using DHCP and then plug the cable in and I have link. Is there a difference how /etc/rc.d/netif handles a NIC with DHCP and how the installation CD is handling it? Once again, steps to reproduce this behavior: 1) Power the laptop OFF. Really OFF, I mean. No reboots! 2) Detach the cable from NIC. 3) Boot FreeBSD. Let it pass the DHCP phase (ifconfig_em0=DHCP) until login appears. 4) Attach the cable to the NIC. 5) Voila... no link. -- Martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
5.x to 6.x or 7.x with 64MB /
I have a machine which I have recently upgraded using cvsup, from 4.x to RELENG_5, as a staging post en route to 7.x. The upgrade went well until installworld ran out of disk on / and I realised it was only 64BMB. My bad; should have checked before upgrading. With help from an on-site colleague the installworld was nursed to completion. But can I get the same machine up to 6.x or 7.x without repartitioning? Advice please. Partitions are as follows. ad0 2439 M ad0s1 2439 M ad0s1a64 M / ad0s1b 128 M swap ad0s1e 1024 M /var ad0s1f 600 M /home ad0s1g 623 M - ad157259 M ad1s1 57259 M ad0s1a 10240 M /usr It occurs to me that if ad0s1a is insufficient then I could use ad0s1g as swap, and repurpose ad0s1b as a new /. Is it straightforward to installworld/mergemaster to somewhere other than / ? Nick B ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em(4) on FreeBSD is sometimes annoying
Jack Vogel wrote, on 8/4/2008 9:18 AM: The focus here on the laptop distracted me, but someone else at work reminded me. Its very important that you run the EEPROM fix for the 82573 that i posted a long while back, search in email archive for it. Its a DOS executable that will patch your EEPROM. I am not sure if the Lenova's need it, but get it, run it, and then see if your problem goes away. Martin, there's also a link to it from Jeremy's Commonly Reported Issues page: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues Look for DOS-based EEPROM. Jack, is this issue the same one that is documented here? http://e1000.sourceforge.net/doku.php?id=known_issues#v_l_e_tx_unit_hang_messages ... and addressed by this script? http://e1000.sourceforge.net/doku.php?id=tx_unit_hang If so, the script could be used without booting from a DOS disk. If this is unrelated or is an unsafe way to apply this fix, that would be handy to know. Royce -- Royce D. Williams - http://royce.ws/ A finished person is a boring person. - Anna Quindlen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em(4) on FreeBSD is sometimes annoying
Thanks for the pointer Royce, and yes that's the issue, and if you want to boot Linux and use that instead of DOS then more power to you. Cheers, Jack On Mon, Aug 4, 2008 at 10:35 AM, Royce Williams [EMAIL PROTECTED] wrote: Jack Vogel wrote, on 8/4/2008 9:18 AM: The focus here on the laptop distracted me, but someone else at work reminded me. Its very important that you run the EEPROM fix for the 82573 that i posted a long while back, search in email archive for it. Its a DOS executable that will patch your EEPROM. I am not sure if the Lenova's need it, but get it, run it, and then see if your problem goes away. Martin, there's also a link to it from Jeremy's Commonly Reported Issues page: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues Look for DOS-based EEPROM. Jack, is this issue the same one that is documented here? http://e1000.sourceforge.net/doku.php?id=known_issues#v_l_e_tx_unit_hang_messages ... and addressed by this script? http://e1000.sourceforge.net/doku.php?id=tx_unit_hang If so, the script could be used without booting from a DOS disk. If this is unrelated or is an unsafe way to apply this fix, that would be handy to know. Royce -- Royce D. Williams - http://royce.ws/ A finished person is a boring person. - Anna Quindlen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em(4) on FreeBSD is sometimes annoying
Jack Vogel wrote, on 8/4/2008 9:54 AM: On Mon, Aug 4, 2008 at 10:35 AM, Royce Williams [EMAIL PROTECTED] wrote: Jack Vogel wrote, on 8/4/2008 9:18 AM: The focus here on the laptop distracted me, but someone else at work reminded me. Its very important that you run the EEPROM fix for the 82573 that i posted a long while back, search in email archive for it. Its a DOS executable that will patch your EEPROM. I am not sure if the Lenova's need it, but get it, run it, and then see if your problem goes away. Martin, there's also a link to it from Jeremy's Commonly Reported Issues page: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues Look for DOS-based EEPROM. Jack, is this issue the same one that is documented here? http://e1000.sourceforge.net/doku.php?id=known_issues#v_l_e_tx_unit_hang_messages ... and addressed by this script? http://e1000.sourceforge.net/doku.php?id=tx_unit_hang If so, the script could be used without booting from a DOS disk. If this is unrelated or is an unsafe way to apply this fix, that would be handy to know. Thanks for the pointer Royce, and yes that's the issue, and if you want to boot Linux and use that instead of DOS then more power to you. Excellent! For some folks, booting from a Knoppix or Ubuntu CD might be easier than trying to gen up a DOS-bootable USB key. I think that recent Knoppix and Ubuntu include ethtool out of the box. Point of clarity: the script that I linked to above is to test/invoke the problem, not to address it. Below is the script that calls ethtool to change the actual bits: http://e1000.sourceforge.net/files/fixeep-82573-dspd.sh Royce -- Royce D. Williams - http://royce.ws/ The only normal people are the ones you don't know very well. -A.Adler ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ddb(4) scripts not working in RELENG_7?
Hi Robert, On Sun, 03.08.2008 at 14:49:00 +0100, Robert Watson wrote: On Sun, 3 Aug 2008, Ulrich Spoerlein wrote: I was testing a patch and getting a panic (page fault while in kernel mode) in RELENG_7 running multiuser mode, but no scripts were automagically run, although I configured ddb_enable=YES in rc.conf. It simply dropped me to the interactive ddb(4) prompt, nothing more. Do you have any idea what I could be missing? I have been using DDB scripts on 7-STABLE without any problems, but I'm not sure I've tried it with a page fault, just regular panics. Could you try entering the debugger via sysctl debug.kdb.panic=1, which forces a panic, and see if your scripts run then? Perhaps there's some inconsistency in how we're entering the debugger. If things still appear not to be happening, try setting up a kdb.enter.default script and see if that works? Spot on! Entering via sysctl works as expected; the 'default' script will also be executed after a page fault, but not the panic-script. So either page faults should call the panic-script or some sort of kdb.enter.pfault should be introduced? Either way, I see another manpage update coming up :) Cheers, Ulrich Spoerlein -- It is better to remain silent and be thought a fool, than to speak, and remove all doubt. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Temperature monitoring on old desktop - Dell OptiPlex SX270?
On Sun, 03 Aug 2008 06:43:28 -0700 Jeremy Chadwick [EMAIL PROTECTED] wrote: Then the only possibility is to take a very high-resolution photo (read: 2048x1536 or higher) and send it to someone who can identify Ok, if I want to do that, I guess my Fujifilm Finepix F40fd (8 Mpixel) shold be able. ICs (I'm good at recognising H/W monitoring ICs :-) ). But even that won't guarantee anything; an IC that supports H/W monitoring may be For now, I'll lok at software tests to identify anything. The P4 TM feature is more of a thermal manager and not so much a monitor in the sense of what you think it might be (re: ability to provide thermal statistics to a program). It *is* a monitor in the sense that it reads temperature, but there's no way to access that internal data. Yes, Dan Nelson also explained that to me. Thanks for explaining! You could try Linux. Their lm-sensors project is incredibly thorough, Ok, I did so yesterday, see the SX270 and Xubuntu page[1]. but based on what I've looked at in the code, it's hit-or-miss. It I tested with sensors-detect from lm-sensors, but it was a miss. :-( sensors-detect output here[2]. Again, this would only allow you to detect whether or not there's an actual H/W monitoring IC on the board somewhere. I'm strongly doubting there is. It seems you are right. References: 1) http://tingox.googlepages.com/sx270_xubuntu 2) http://tingox.googlepages.com/sx270-xubuntu-sensors-detect-2008080.txt BTW, I will be traveling for about a week now, and don't know if I will have any connectivity at all. -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em(4) on FreeBSD is sometimes annoying
Right, the Linux driver implemented the ability to write as well as read the eeprom, I've always been hesitant to add that. But for some it will be easier to boot Linux and run the script. Thanks for adding the URL Royce. Jack On Mon, Aug 4, 2008 at 11:15 AM, Royce Williams [EMAIL PROTECTED] wrote: Jack Vogel wrote, on 8/4/2008 9:54 AM: On Mon, Aug 4, 2008 at 10:35 AM, Royce Williams [EMAIL PROTECTED] wrote: Jack Vogel wrote, on 8/4/2008 9:18 AM: The focus here on the laptop distracted me, but someone else at work reminded me. Its very important that you run the EEPROM fix for the 82573 that i posted a long while back, search in email archive for it. Its a DOS executable that will patch your EEPROM. I am not sure if the Lenova's need it, but get it, run it, and then see if your problem goes away. Martin, there's also a link to it from Jeremy's Commonly Reported Issues page: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues Look for DOS-based EEPROM. Jack, is this issue the same one that is documented here? http://e1000.sourceforge.net/doku.php?id=known_issues#v_l_e_tx_unit_hang_messages ... and addressed by this script? http://e1000.sourceforge.net/doku.php?id=tx_unit_hang If so, the script could be used without booting from a DOS disk. If this is unrelated or is an unsafe way to apply this fix, that would be handy to know. Thanks for the pointer Royce, and yes that's the issue, and if you want to boot Linux and use that instead of DOS then more power to you. Excellent! For some folks, booting from a Knoppix or Ubuntu CD might be easier than trying to gen up a DOS-bootable USB key. I think that recent Knoppix and Ubuntu include ethtool out of the box. Point of clarity: the script that I linked to above is to test/invoke the problem, not to address it. Below is the script that calls ethtool to change the actual bits: http://e1000.sourceforge.net/files/fixeep-82573-dspd.sh Royce -- Royce D. Williams - http://royce.ws/ The only normal people are the ones you don't know very well. -A.Adler ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em(4) on FreeBSD is sometimes annoying
On Mon, 04 Aug 2008 09:35:21 -0800 Royce Williams [EMAIL PROTECTED] wrote: Jack Vogel wrote, on 8/4/2008 9:18 AM: The focus here on the laptop distracted me, but someone else at work reminded me. Its very important that you run the EEPROM fix for the 82573 that i posted a long while back, search in email archive for it. Its a DOS executable that will patch your EEPROM. I am not sure if the Lenova's need it, but get it, run it, and then see if your problem goes away. Martin, there's also a link to it from Jeremy's Commonly Reported Issues page: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues Look for DOS-based EEPROM. Hi Royce, thank you for the link. I've read this issue description and I'm not sure if it helps. I don't have any watchdog timeouts and my EEPROM data looks clean: Interface EEPROM Dump: Offset 0x 0x0010 0053 0103 026b 2001 17aa 109a 8086 80df 0x0020 2000 7e54 0014 00da 0004 2700 0x0030 6cc9 3150 073e 040b 298b f000 0f02 (I masked out the MAC address) -- Martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em(4) on FreeBSD is sometimes annoying
OK, so your EEPROM is does not have the bug. As I was saying before, I would like to see what back to back behavior is. And, BTW, back to back does NOT mean hook to the switch, that's the very thing that is suspicious. It means NIC to NIC, no DHCP, assigned addresses. And then see that you pass traffic, and then unhook cable, see if link goes down, reconnect and it should go up. Oh, and exactly what kernel, and driver revision are you using. Jack On Mon, Aug 4, 2008 at 11:52 AM, Martin [EMAIL PROTECTED] wrote: On Mon, 04 Aug 2008 09:35:21 -0800 Royce Williams [EMAIL PROTECTED] wrote: Jack Vogel wrote, on 8/4/2008 9:18 AM: The focus here on the laptop distracted me, but someone else at work reminded me. Its very important that you run the EEPROM fix for the 82573 that i posted a long while back, search in email archive for it. Its a DOS executable that will patch your EEPROM. I am not sure if the Lenova's need it, but get it, run it, and then see if your problem goes away. Martin, there's also a link to it from Jeremy's Commonly Reported Issues page: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues Look for DOS-based EEPROM. Hi Royce, thank you for the link. I've read this issue description and I'm not sure if it helps. I don't have any watchdog timeouts and my EEPROM data looks clean: Interface EEPROM Dump: Offset 0x 0x0010 0053 0103 026b 2001 17aa 109a 8086 80df 0x0020 2000 7e54 0014 00da 0004 2700 0x0030 6cc9 3150 073e 040b 298b f000 0f02 (I masked out the MAC address) -- Martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Top, TIME and CPU columns
Hi, I have noticed this weirdness in top. Sometimes I can see no process having more than single percents in the (W)CPU column, yet there is one for that the TIME column is steadily increasing by 1 second per second. How is this (W)CPU column computed? Shouldn't it report something like 1/NCPU * 100 or something? -- VH signature.asc Description: OpenPGP digital signature
Re: 5.x to 6.x or 7.x with 64MB /
On Mon, 04 Aug 2008 18:48:03 +0200, Nick Barnes [EMAIL PROTECTED] wrote: I have a machine which I have recently upgraded using cvsup, from 4.x to RELENG_5, as a staging post en route to 7.x. The upgrade went well until installworld ran out of disk on / and I realised it was only 64BMB. My bad; should have checked before upgrading. With help from an on-site colleague the installworld was nursed to completion. But can I get the same machine up to 6.x or 7.x without repartitioning? Advice please. Partitions are as follows. ad0 2439 M ad0s1 2439 M ad0s1a64 M / ad0s1b 128 M swap ad0s1e 1024 M /var ad0s1f 600 M /home ad0s1g 623 M - ad157259 M ad1s1 57259 M ad0s1a 10240 M /usr It occurs to me that if ad0s1a is insufficient then I could use ad0s1g as swap, and repurpose ad0s1b as a new /. Is it straightforward to installworld/mergemaster to somewhere other than / ? That is very well doable. On boot you can interrupt the boot process by pressing space an set another location for the kernel. More information is here. http://www.freebsd.org/doc/en/books/handbook/boot-blocks.html The rest is just about files. After you copy everything in ad0s1b (with a fs in it) you can boot from ad0s1b:/boot/kernel. I think you can do something like make installkernel DESTDIR=/blabla, but I'm not sure. Maybe more easy is booting with a LIVE-cd. Than you can mount everything needed for installworld in /mnt/tmproot, so you get: /mnt/tmproot mounted the _new_ / partition (ad0s1b?) /mnt/tmproot/usr where /usr is mounted (ad0s1a) /mnt/tmproot/var where /var is mounted (ad0s1e) Do a chroot /mnt/tmproot and than run installworld and mergemaster as usual from /usr/src. Don't forget to make a backup. It is on your own risk. ;-) Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Using Portupgrade?
On Sun, 2008-08-03 at 19:26 -0700, Jeremy Chadwick wrote: On Sun, Aug 03, 2008 at 09:20:08PM -0400, Nic Reveles wrote: I've recently updated to freeBSD 6.3-STABLE from 5.3-RELEASE (amd64) and am struggling with out of date ports. I have tried updating 'ports-all' and 'src-all' numerous times (does src-all include ports-all? It takes forever) along with portupgrade. src-all does not include ports-all. It takes forever is wonderfully vague. :-) Chances are the cvsup server you're using is slow (usually caused by heavy disk I/O, not so much network I/O); pick another. Try them all, find one which is fast. I'd recommend a couple I commonly use, but then everyone will start using them... :-) One can install sysutils/fastest_cvsup and run fastest_cvsup -c ISO country code -- Alexandre Sunny Kovalenko (Олександр Коваленко) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em(4) on FreeBSD is sometimes annoying
On Mon, Aug 04, 2008 at 10:18:50AM -0700, Jack Vogel wrote: The focus here on the laptop distracted me, but someone else at work reminded me. Its very important that you run the EEPROM fix for the 82573 that i posted a long while back, search in email archive for it. Its a DOS executable that will patch your EEPROM. I am not sure if the Lenova's need it, but get it, run it, and then see if your problem goes away. The tool Jack is referring to is below. I knew saving it for a rainy day would be worth it. :-) http://people.freebsd.org/~koitsu/em_82573_manc_fix.zip -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portmaster questions (Was: Re: Using Portupgrade?)
,--- Doug Barton (Sun, 03 Aug 2008 22:14:54 -0700) * | It's really not appropriate to hijack the portupgrade thread for this, | so I'm starting a new subject. Also, please respect followups to | -ports. [ Being an inexperienced poster: sorry. Am I using a good cc: list now? ] | Alex Goncharov wrote: | 1. I see a significant difference in the time it takes to get the same | information using the two tools: | As I understand it, portupgrade uses the INDEX file to determine | whether ports are up to date. Portmaster recurses through each | installed port and does 'make -V PKGVERSION'. | | 2. It looks like there are no `portmaster' equivalents to | `portupgrade' `-P' and `-PP' options, which I want to have. | If portupgrade does the job for you, keep using it. :) I have said | many times that I'm not looking to write a portupgrade replacement. | Use the right tool for the job(s) you have to do. `---* Thank you for `postmaster' -- I do like it and am not trying to criticize. Hoped that somebody knowledgeable would tell me how to use the available port management tools better, which you just did re: versions, thanks. ,--- Miroslav Lachman (Mon, 04 Aug 2008 11:36:58 +0200) * | You do not have to run portversion or portmaster or any other 3rd party | tool to check versions of installed ports. Use pkg_version which is | included in base system and then you are independent of port management | tools changes. | pkg_version (by default) do not use INDEX, but have option to use it and | then become clear winner (in speed): Thank you -- I didn't know that and am switching to pkg_version -I now!.. | As I had problems with portupgrade's handling of dependencies, I am | converted to portmaster. `---* I've also had enough problems with portupgrade's -R option and essentially stopped using it (the option). ,--- Marcin Wisnicki (Mon, 4 Aug 2008 15:24:37 + (UTC)) * | It's not even doing a good job at it, standard pkg_version significantly | outperforms it: `---* Well, I guess I'll make another, better informed attempt to switch to portmaster now. Thank you all who replied for the useful information! -- Alex -- [EMAIL PROTECTED] -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
DarkStone MuOnline Server Challenge you To a Duel.
[votenew.jpg] _ [pixel.gif] www.darkstonemu.net [pixel.gif] [pixel.gif] [pixel.gif] [pixel.gif] [muonlinedarkstoneadv256vo4.gif] DarkStone MuOnline DarkStone MU Online is a MMORPG that takes the player, into a fantasy world full of excitement, adventure and monsters. With several ways to train a character, multiple character classes, and a vast continent to explore, GMO is a sure way to a unique adventure. Join thousands of players from all over the world and help defend the Continent of Legend, clearing it from the clenches of Kundun and his forces forever. . With new content and features being introduced regularly, this game is perfect for those looking for an exciting MMO experience. [pixel.gif] [pixel.gif] [pixel.gif] You start off as a Dark Wizard, a Dark Knight, Dark Lord, Magic GLadiator, a Summoner or a Fairy Elf, with accordant strengths and weaknesses. You can save different base characters, a fun feature that allows you to begin play as a wizard, and later, restart and switch to a knight--but not both at the same time. The look of your character changes to reflect any new accoutrements you get, including wings and spells. There's also a coordinate system on display, so it's easier to move around the elaborate MU world. Items can be combined in many different ways, but more game experience gets you better gear. You can even fight other players, but be warned: if you kill too many innocents, you'll be branded a murderer. Server Stats: ON * Experience: 1000x * Drops: 80% * Reset Level: 399 keep stats * Shops: +7 items. (you have to find some shops for the good items.) * Bless Bug On * Register: http://www.darkstonemu.net/DarkStone-Register.html * Download: http://www.darkstonemu.net/DarkStone-Downloads.html Official Game Installer: http://darkstonemu.net/Download/DarkStoneMu.exe In order to play free just enter your [1]Site and download the [2]Client. We encourage you to visit the DarkStone MU Online forums at [3]http://darkstonemu.net/ _ *Please do not respond to this e-mail as your reply will not be received. References 1. http://www.darkstonemu.net/DarkStone-Register.html 2. http://www.darkstonemu.net/DarkStone-Downloads.html 3. http://www.craiova-online.ro/rds-mu-server-212/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
