Re: fxp0: device timeout and sk0: watchdog timeout problems
Hi, At 03:16 PM 1/19/2006, you wrote: On Thu, Jan 19, 2006 at 02:14:13PM +0800, Ganbold wrote: > I have same problem even after updating the sk code to the latest: > > Jan 19 12:58:53 gw kernel: fxp0: device timeout > Jan 19 12:59:10 gw kernel: sk0: watchdog timeout > Jan 19 12:59:10 gw kernel: sk0: link state changed to DOWN > Does interface down and up help your situation? This server is located 370km from where I'm now. People there just reboot the server. It would be great to know what mwchan is used if your application was blocked. mwchan? Would you try another onboard NIC with fxp to narrow down the issue? Hard to say since it is on remote site. I could ask person there. Since it's hard to reproduce the problem on my system I need more information. Would you show me more information for your network configuration and how to reproduce it? This machine is doing NAT, ipfw and it has squid from ports. It seems like 3GB-9GB web traffic is going through per day. gw# ifconfig -a sk0: flags=8843 mtu 1500 options=2b inet 175.176.1.11 netmask 0x broadcast 175.176.255.255 ether 00:11:95:e1:7d:16 media: Ethernet autoselect (1000baseTX ) status: active pcn0: flags=8802 mtu 1500 ether 00:06:29:50:e2:3c media: Ethernet autoselect (none) status: no carrier fxp0: flags=8843 mtu 1500 options=b inet x.x.x.x netmask 0xfff0 broadcast x.x.x.x ether 00:03:47:e0:64:3c media: Ethernet autoselect (100baseTX ) status: active Other onboard NIC is pcn: [EMAIL PROTECTED]:9:0: class=0x02 card=0x20001014 chip=0x20001022 rev=0x36 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Am79C970/1/2/3/5/6 PCnet LANCE PCI Ethernet Controller' class= network subclass = ethernet I heard this card also might have some problems, but I'm not sure. Correct me if I'm wrong. Ganbold -- Regards, Pyun YongHyeon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fxp0: device timeout and sk0: watchdog timeout problems
On Thu, Jan 19, 2006 at 02:14:13PM +0800, Ganbold wrote: > I have same problem even after updating the sk code to the latest: > > Jan 19 12:58:53 gw kernel: fxp0: device timeout > Jan 19 12:59:10 gw kernel: sk0: watchdog timeout > Jan 19 12:59:10 gw kernel: sk0: link state changed to DOWN > Jan 19 12:59:20 gw kernel: fxp0: device timeout > Jan 19 12:59:52 gw kernel: fxp0: device timeout > Jan 19 13:00:23 gw kernel: fxp0: device timeout > Jan 19 13:00:29 gw kernel: sk0: watchdog timeout > Jan 19 13:00:52 gw kernel: fxp0: device timeout > Jan 19 13:01:05 gw kernel: sk0: watchdog timeout > Does interface down and up help your situation? It would be great to know what mwchan is used if your application was blocked. Would you try another onboard NIC with fxp to narrow down the issue? Since it's hard to reproduce the problem on my system I need more information. Would you show me more information for your network configuration and how to reproduce it? -- Regards, Pyun YongHyeon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Gmirror'd SWAP: no dump?
On Wed, Jan 18, 2006 at 12:44:27PM -0600, Larry Rosenman wrote: > Are there any plans to support dumping to a gmirror'd swapfile? Dumping occurs when kernel is in "bad condition", so GEOM can not be safe used (for example panic in GEOM code). Check archives for last month of 2005 for longer explanation. > > My FreeBSD/amd64 6.0-STABLE as of today doesn't seem to want to do it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fxp0: device timeout and sk0: watchdog timeout problems
I have same problem even after updating the sk code to the latest: Jan 19 12:58:53 gw kernel: fxp0: device timeout Jan 19 12:59:10 gw kernel: sk0: watchdog timeout Jan 19 12:59:10 gw kernel: sk0: link state changed to DOWN Jan 19 12:59:20 gw kernel: fxp0: device timeout Jan 19 12:59:52 gw kernel: fxp0: device timeout Jan 19 13:00:23 gw kernel: fxp0: device timeout Jan 19 13:00:29 gw kernel: sk0: watchdog timeout Jan 19 13:00:52 gw kernel: fxp0: device timeout Jan 19 13:01:05 gw kernel: sk0: watchdog timeout Ganbold At 10:36 AM 1/18/2006, you wrote: On Wed, Jan 18, 2006 at 10:28:43AM +0800, Ganbold wrote: > At 09:55 AM 1/18/2006, you wrote: > > > inet 127.0.0.1 netmask 0xff00 > > > > > > I used new if_sk codes from Pyun YongHyeon but after 2 days I got > > > same problem device timeout. > > > fxp is also timing out and I don't know why. > > > Any idea? > > > > > > >If sk(4) is the cause of problem fxp wouldn't be affected. > > I guess so. But fxp also times out almost at same time as sk does. > > >Of course it's possible for sk(4) to corrupt kernel memory structure > >but the possibility is low. While fixing sk(4) I pushed sk(4) to the > >limit on sparc64. I never met such timeouts. > > > >atm I have no clue. How about updated sk(4)? > >http://people.freebsd.org/~yongari/sk/if_sk.c > >http://people.freebsd.org/~yongari/sk/if_skreg.h > > Is it new update? Because I used your update dated on Jan 12 2006. Is > it newer than that? > Yes. > >Disabling sk(4) remedy your issue? > > There is another on-board pcn NIC, I will try if problem exists with sk > driver. > Ok. Thank you. -- Regards, Pyun YongHyeon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ALTQ on GIF tunnels?
Gleb Smirnoff wrote: On Mon, Jan 16, 2006 at 11:48:34PM -0600, J. Buck Caldwell wrote: J> Is there any work on adding support for ALTQ to the GIF tunnel J> interface? I'm having wonderful results getting ALTQ working on normal J> interfaces, but it would be heavenly to prioritize the traffic inside J> the tunnels. You can (and probably should) enable ALTQ on the physical interface that gif(4) runnels use for encapsulated packets. Yes, but that doesn't do any good for the packets traveling inside the tunnel. Specifically, I have a corporate network hooked to a branch via VPN, and want to prioritize not just the tunnel over ordinary traffic, but prioritize different types of traffic inside the tunnel. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ndis0 does not associate since update to RELENG_6
On Wednesday 18 January 2006 02:58, Bill Paul wrote: > # ifconfig ndis0 ssid "yourssid" bssid up you can say bssid any adding bssid seems to be crucial for associating certain wlcards especial when using ndis and 11g then for using wep you may try as wepmode on weptxkey 1 wepkey 0x0101010111 João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Update is the binary update solution [Re: HEADS UP: Release schedule for 2006]
On 22. des. 2005, at 22.17, Jo Rhett wrote: On Sat, Dec 17, 2005 at 06:19:25PM -0700, Scott Long wrote: FreeBSD Update was written by, and is continuously maintained by the actual FreeBSD Security Officer. It's as official as it gets. If the only barrier to acceptance is that it's not distributed from the FreeBSD.org domain, then a) that's a silly argument, and b) it's easily solvable so long as Colin agrees. But FreeBSD Update suffers from all of the same limitations that I've been describing because of lack of integration with the Core OS. 1. modified kernels are foobar ..yet are practically mandatory on production systems 2. modified sources are foobar ..yet many common production situations require source compilation options Modified files cannot be patched, period. No matter what system you are on. A nice user-experience of backing up the modified file and reinstalling the default could be added on top to resemble other systems, but it would not solve your problem. What you are looking for is enough run-time knobs and a stable ABI layer for third party drivers so the need for compiling your own kernel disappears. 3. FreeBSD Update can't handle updates of jails and other situations that package systems deal with just fine. freebsd-update -b /usr/jail/foo ? From the manual: Act on a FreeBSD world based at the directory basedir. This is suitable for updating jails, but note that the usual rules about updating locally modified (or compiled) files apply, and the jail must belong to the same release version as the run- ning kernel. Frode Nordahl [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Gmirror'd SWAP: no dump?
Are there any plans to support dumping to a gmirror'd swapfile? My FreeBSD/amd64 6.0-STABLE as of today doesn't seem to want to do it. Thanks, LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sendmail is not functioning on FreeBSD 5.4
Firstly, I'm sorry if this message is put in wrong mailing list. Normally I use sendmail to send mails from my host to other hosts. I can send any mails using mutt mail client to any addresses like... hotmail, yahoo mail, and many more without any problems. As now I have switched to FreeBSD 5.4-RELEASE and still use sendmail. I have just subscribed to [EMAIL PROTECTED] The problem is that I couldn't send any mails to freebsd-stable@freebsd.org, while sending to other addresses is still nice on FreeBSD 5.4. I'm a noobie. Anyone have clues please point me out. Which configuration files shall I look at? Any ideas would be much appreciated. (This mail was delivered because I used web-based mail to send to same address) What does the server reject message say? Most likely, sendmail is not HELOing with an address that has a valid reverse-DNS lookup... ~Dan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sendmail is not functioning on FreeBSD 5.4
Hi all, Firstly, I'm sorry if this message is put in wrong mailing list. Normally I use sendmail to send mails from my host to other hosts. I can send any mails using mutt mail client to any addresses like... hotmail, yahoo mail, and many more without any problems. As now I have switched to FreeBSD 5.4-RELEASE and still use sendmail. I have just subscribed to [EMAIL PROTECTED] The problem is that I couldn't send any mails to freebsd-stable@freebsd.org, while sending to other addresses is still nice on FreeBSD 5.4. I'm a noobie. Anyone have clues please point me out. Which configuration files shall I look at? Any ideas would be much appreciated. (This mail was delivered because I used web-based mail to send to same address) Thanks, pongthep ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Creating a system RAID-10 device
* Sven Willenberger <[EMAIL PROTECTED]> [20060117 22:06]: > over 3 mirror raid arrays that would encompass the entire filesystem > including the /boot and root partitions. > > Generally I would create a RAID10 from 6 disks as follows: > > gmirror label -v -b round-robin md1 da0 da1 > gmirror label -v -b round-robin md2 da2 da3 > gmirror label -v -b round-robin md3 da4 da5 > > gstripe label -v -s 131072 > md0 /dev/mirror/md1 /dev/mirror/md2 /dev/mirror/md3 > > newfs /dev/stripe/md0 > > naturally the problem here is that it cannot be done on a system that > booted from da0. I have seen the example of setting up a mirrored system > drive > (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom-mirror.html ) > > which won't quite work for my case either. Using this method I could > probably get the one mirror (md1) to work, but I know of no way of then > adding the other 2 mirror sets and then redoing the system to stripe > across all 3 mirrored sets. Uhm. The problem is that you can't mount the root fs from a striped partition. Create an extra slice on each drive and either configure a 6-way mirror or a mirror-of-3-sripes to boot from. > The only thing I could think of was to boot from the livecd and create > the 6-disk array and then trying to install FreeBSD onto this > filesystem. In order to do this the installer would have to > recognize /dev/stripe/md0 as a valid "drive" -- is there any way to have > this happen? I don't believe sysinstall is smart enough, but you can always use the install.sh scripts on the distribution. However, the above still aplies. qvb -- pica ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ALTQ on GIF tunnels?
On Mon, Jan 16, 2006 at 11:48:34PM -0600, J. Buck Caldwell wrote: J> Is there any work on adding support for ALTQ to the GIF tunnel J> interface? I'm having wonderful results getting ALTQ working on normal J> interfaces, but it would be heavenly to prioritize the traffic inside J> the tunnels. You can (and probably should) enable ALTQ on the physical interface that gif(4) runnels use for encapsulated packets. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fxp0: device timeout and sk0: watchdog timeout problems
On Wed, Jan 18, 2006 at 11:36:46AM +0900, Pyun YongHyeon wrote: P> > > > same problem device timeout. P> > > > fxp is also timing out and I don't know why. P> > > > Any idea? P> > > > P> > > P> > >If sk(4) is the cause of problem fxp wouldn't be affected. P> > P> > I guess so. But fxp also times out almost at same time as sk does. Have you tried another motherboard? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[Fixed] Re: ndis0 does not associate since update to RELENG_6
[EMAIL PROTECTED] (Bill Paul) wrote: > > Is there a way I can provide more information? > > You haven't said yet what manufacturer/model your access point is. It's a Netgear WGT624 (Hardwareversion V3H1/Firmwareversion V1.1.125_1.1.1GR). I tried to associate ndis0 with wi0 in hostap mode and got the same results. > You also haven't said what Windows driver version you're using, but > you need to cheat a bit to figure that out. I usually do: > > % strings -e l foo.sys > Near the end of the output, there should be a bunch of version > information, including the vendor name of whoever built the driver > (in this case Intel). You might try downloading the latest driver > from Intel. (They have a generic one for their Centrino wireless > devices.) The old driver which was shipped with the Laptop: StringFileInfo 040904B0 Comments NDIS 5 Miniport Driver for Win2000 CompanyName Intel Corporation FileDescription Intel Wireless LAN Driver FileVersion 8010-28 Driver InternalName w22n50.SYS LegalCopyright Copyright Intel Corporation 2004 OriginalFilename w22n50.SYS ProductName Intel Wireless LAN Adapter VarFileInfo Translation The "new" one I downloaded from Intel today: StringFileInfo 040904B0 Comments NDIS 5.1 Miniport Driver CompanyName Intel Corporation FileDescription Intel Wireless LAN Driver FileVersion 9003-9 Driver InternalName w29n51.SYS LegalCopyright Copyright Intel Corporation 2004 OriginalFilename w29n51.SYS ProductName Intel Wireless LAN Adapter VarFileInfo Translation > You also haven't said what sort of laptop this is. Wouldn't hurt to > know that either. IBM ThinkPad R51 UN0K6GE. > Unfortunately, this is the sort of thing that can only be debugged > with the system sitting in front of me. I can't do it by remote > control, and I can't know exactly what information to ask you. I have > to experiment, and I can't do that from here. > > You should turn WEP off completely, make sure the AP is set for open > authentication mode, and try getting it to authenticate without WEP > first. It's one less variable to worry about. Try using the following: > > # ifconfig ndis0 ssid "" up > > # ifconfig ndis0 ssid "yourssid" bssid up Specifying the bssid is the solution. ifconfig ndis0 ssid ec60bfg3b4 bssid wepkey 1:0x\ deftxkey 1 wepmode on up Works with the new and the old driver and with both APs. [EMAIL PROTECTED] ~ $ifconfig ndis0 ndis0: flags=8843 mtu 1500 inet6 fe ... 7500%ndis0 prefixlen 64 scopeid 0x3 inet 192.168.0.32 netmask 0xff00 broadcast 192.168.0.255 ether 00 ... 00 media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/54Mbps) status: associated ssid ec60bfg3b4 channel 11 bssid 00:... authmode OPEN privacy ON deftxkey 1 wepkey 1:104-bit txpowmax 100 protmode CTS Thanks for your time Bill. Fabian -- http://www.fabiankeil.de/ signature.asc Description: PGP signature
