Re: fxp problems with latest stable Re: panics after upgrading to -STABLE Aug 9, 2002 (still something up)
On Sat, 10 Aug 2002, Mike Tancsa wrote: Dear Mike. I reported a similar problem on August the 9th and I must say, sorry, if I would have offered the dmesg output all should have seen that we use only Intel NICs around here! Another workstation with a 3Com NIC does not show this strange behaviour. I did some more tests with the new driver with 2 machines on a totally different segment and the same sorts of packet loss on simple pings. If I revert to the previous version, no packet loss at all. $FreeBSD: src/sys/dev/fxp/if_fxp.c,v 1.110.2.24 2002/08/09 02:04:20 luigi Exp $ vs $FreeBSD: src/sys/dev/fxp/if_fxp.c,v 1.110.2.23 2002/07/29 02:50:59 luigi Exp $ I confirmed this on 2 separate machines. The fxp nics in question are fxp0: Intel Pro 10/100B/100+ Ethernet port 0xa800-0xa81f mem 0xf900-0xf90f,0xfd00-0xfd000fff irq 11 at device 13.0 on pci0 fxp0: Ethernet address 00:a0:c9:89:d5:ba inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto and fxp0: Intel Pro 10/100B/100+ Ethernet port 0xa000-0xa03f mem 0xe950-0xe95f,0xe960-0xe9600fff irq 10 at device 4.0 on pci2 fxp0: Ethernet address 00:d0:b7:db:69:6a inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Both nics on both machines in question do have shard IRQs, but like I said, with the previous version of the driver it works fine. If I can provide any more information, please let me know. I do have a serial console on one machine and will have physical access to it once again on Monday. ---Mike At 08:53 PM 8/10/2002 -0400, Mike Tancsa wrote: Actually, I am still seeing a lot of strange things. The patch certainly fixed the panics, but now I am seeing packet loss on links off the same subnet. e.g. 32 packets transmitted, 23 packets received, 28% packet loss round-trip min/avg/max/stddev = 0.333/0.348/0.389/0.015 ms If I reboot with an old kernel its fine. Even stranger. If I do a dump from a machine a few hops away, I get my normal throughput. netstat -ni does not show any problems, nor do the switch counters show any issues. These are with fxp cards. Could it be the latest fxp commit ? ---Mike At 07:45 AM 8/10/2002 -0700, Randy Bush wrote: Could someone put the word out when this issue is fixed? This problem just hosed my web server after I forgot the prime directive: test on a non-critical machine. it was fixed randy To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message Mike Tancsa,tel +1 519 651 3400 Sentex Communications, [EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message -- MfG O. Hartmann [EMAIL PROTECTED] IT-Administration des Institut fuer Physik der Atmosphaere (IPA) Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinensaal) Tel: +496131/3924144 FAX: +496131/3923532 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: fxp problems with latest stable Re: panics after upgrading to -STABLE Aug 9, 2002 (still something up)
I have a machine that has two different interfaces (xl for the external and fxp for the LAN). After rebuilding the kernel after 8/9/02, I experienced kernel panic -- but only as as result of passing data through the fxp interface. It stayed stable until I ssh'ed into the router, which caused almost immediate panic. No connections (that were automatically opened by startup scripts) to the outside world via xl caused this problem. This is consistent with the idea that the fxp driver is borked somehow. The revision date in the CVS tag seems to support this. * $FreeBSD: src/sys/dev/fxp/if_fxp.c,v 1.110.2.24 2002/08/09 02:04:20 luigi Exp $ Just my observerations, it may be incorrect. I haven't tested the patch referenced, I'm wary of more downtime. -- Chris Original message from Mike Tancsa: Yes, I do not get those reproducible panics either. However, I think this fxp problem I am seeing now is something different. ---Mike At 07:36 PM 8/10/2002 -0700, David Wolfskill wrote: Date: Sat, 10 Aug 2002 18:42:25 -0700 From: cj_ [EMAIL PROTECTED] Can someone confirm when the -STABLE kernel is usable? I lack a throwaway machine to test this out on. I was able to get a dead-on reproducible panic, even with sources CVSupped as of 0347 hrs. PST (GMT-7) today. After hand-applying the patch in http://docs.freebsd.org/cgi/getmsg.cgi?fetch=2013026+0+current/cvs-all (which refers to PR kern/41492), I no longer get that (or any other, so far) panic. Cheers, david (links to my resume at http://www.catwhisker.org/~david) -- David H. Wolfskill [EMAIL PROTECTED] To paraphrase David Hilbert, there can be no conflicts between Microsoft and the discipline of systems administration, since they have nothing in common. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message Mike Tancsa,tel +1 519 651 3400 Sentex Communications, [EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
BASH using up major CPU while idle. Could it be caused by portupgrade?
Frequently I have had to kill -INT 1 to reboot because nothing on the box would respond. I used portupgrade bash and ever since I've been getting fork: Resource temporarily unavailable for every command. Maybe I'll put root's shell to tcsh and then uninstall bash, and install it by going cd /usr/ports/shells/bash2 make install clean Hopefully that will stop these errors. Thanks guys. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: BASH using up major CPU while idle. Could it be caused byportupgrade?
Just out of curiousity, what does the following return? sysctl kern.maxusers Charles -- Charles Sprickman [EMAIL PROTECTED] On Sun, 11 Aug 2002, lewwid wrote: Frequently I have had to kill -INT 1 to reboot because nothing on the box would respond. I used portupgrade bash and ever since I've been getting fork: Resource temporarily unavailable for every command. Maybe I'll put root's shell to tcsh and then uninstall bash, and install it by going cd /usr/ports/shells/bash2 make install clean Hopefully that will stop these errors. Thanks guys. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
RE: Boot failed - all data lost - SOLVED
Hi, and thanks for all the replies (on and off the list). I got the machine back from my Dell vendor last Friday with the explanation that it's BIOS (Dell A02) was broken. Under some operating systems, disabling the USB controller could interfere with the OS's boot process. Now, they weren't familiar with this FreeSDF system but they thought that might be it. Just to be sure they decided to format the disks, install Windows 200 Server and see if they could get the machine to boot. It booted. This may be the best way to troubleshoot hardware, but I beg to differ. Once back in my office I downgraded to A02 and installed FreeBSD. I tried disabling the USB controller in the BIOS with the same results as before. Boot failed and no sign of any data. Doing the same procedure with A03 has no affect and therefor I have written this off as a Dell BIOS thing. Of course, since Dell does not officially support other OSes than Windows or Redhat linux - running FreeBSD was at my own risk and I will have to pay for the times spent on fixing the machine. Thanks again for your replies, Bjorn Swift -Original Message- From: Robert L Sowders [mailto:[EMAIL PROTECTED]] Sent: 9. ágúst 2002 21:14 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Boot failed - all data lost Is this a SCSI disk? I had this same problem last night, it turned out to be a bad SCSI cable. The disks were found on boot and the SCSI bios could see them on the chain but when it tried to boot it kept saying no disk found. I booted a DOS disk with fdisk and it also couldn't see the disk. I almost trashed the drive. On a whim I replaced the cable and it everything worked. It turns out the scsi cable had a bad active terminator. I replaced the cable and everything came back. If your system is scsi, it's something to try anyway. Hanspeter Roth [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 08/09/2002 12:35 PM Please respond to freebsd-stable To: [EMAIL PROTECTED] cc: Subject:Re: Boot failed - all data lost On Aug 08 at 10:32, Björn Patrick Swift spoke: The first error I got was from the 'FreeBSD Boot Manager'. It started as normally and displayed 'F? FreeBSD', but as I struck 'enter' I got a 'boot failed' message. Then I rebooted the machine again and started getting 'No operating system found' messages. I thought that maybe the boot record had been damaged so I booted the FreeBSD 4.6-install CD and opened fdisk - all space unused, no partitions found. No sign of my data at all! Get your disk back from Dell. Then try testdisk or gpart. -Hanspeter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
boot process stuck at start_init: trying /sbin/init
installed freebsd source is/are dated around the hours of aug 10, 11
2002.
well, everything was going great... until i ran MAKEDEV thru
mergemaster. after running MAKEDEV, i saw errors flying by about
missing wheel operator groups... to which i didn't pay much
attention (as i was thinking that's just silly! wheel group has to
be in /etc/{passwd,groups}.)
since then after rebooting, i/boot process cannot go past...
start_init: trying /sbin/init
...un/loading new/old kernel doesn't further the boot in any way.
various devices -- cd-rw, floppy, hard drives, etc. -- are
identified correctly.
if it helps, kernel configuration is...
http://www103.pair.com/parv/comp/unix/cf/freebsd/KERNCONF
...and not-so-old (4.6-stable jun 26-27 2002) boot log...
http://www103.pair.com/parv/comp/unix/err/dmesg/delli5000e-dmesg
...what can i do now?
thanks in advance.
kindly cc me ([EMAIL PROTECTED]) as i can't access freebsd list
proper.
- desperate freebsd user
__
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
[no subject]
subscribe freebsd-stable subscribe cvs-all To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: SMP kernel: FreeBSD vs. Linux 2.4.x
Thus spake David Schultz [EMAIL PROTECTED]: That's what I heard, although I still don't know how the approaches are different. I read the Anderson paper, but I can't seem to find any documentation about the FreeBSD approach. (Given the signal delivery problems we're currently having, I'd guess that Julian et al. are going through the same hell that the Solaris developers did when implementing threading.) Could you please ellaborate on the differences in the FreeBSD approach? To answer on my own question based on information Julian posted to -current today: http://people.freebsd.org/~julian/freebsd_kse.tgz To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
