Bug in FreeBSD 4.4 in su
ok if you into your freebsd box from somewhere else and type su - root and then type the root password it just hangs there and you think I'm sure I typed the password correctly. So then you u think ok the the SSH session died for some reason try to log back in via ssh and you can't and when you try to ping the machine it appears down but its actually not down because if walk over to the machine down and up the network interface and reapply the firewall rules and then try to ssh to it, it works. which currently means I've no FreeBSD computer until I go and fix it. Getting withdrawl simptons already. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
problems with 3Com 900TPO network card
Hi I have the 3com card that I listed above and I have a problem with the network card light going off on the hub and the card it self basically crashing for some reason which leaves the machine in an unstable state and then prepares to reboot itself. this happens after 4 days of usage normally all though if you down and up the interface every 2 days you can get 13 days out of the machine. When it crashes it gives a crash dump from the driver which I'll try and take down next time it happens and maybe one of you guys will know why this is happening to me. thanks Bri, To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: possibily something to do with sshd
The system I am running freebsd 4.4 stable allthough I don't know how to reproduce the problem of the w, who, uptime, finger commaands hanging and taking the whole cpu and when you ssh back into the machine I think sshd runs one of these commands or calls a function that they use that makes it hang. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Bri Sent: 26 November 2001 13:22 To: [EMAIL PROTECTED] Subject: RE: possibily something to do with sshd rebooted and its fine. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Bri Sent: 26 November 2001 12:59 To: [EMAIL PROTECTED] Subject: possibily something to do with sshd 2827 root 60 0 2632K 1532K RUN 1:01 32.28% 32.28% sshd 2498 root 59 0 2632K 1548K RUN 5:04 32.23% 32.23% sshd 1262 root 58 0 2672K 1504K RUN 1:13 31.45% 31.45% sshd some info from top and these's should be basically idle. Maybe I should reboot. for some reason when I type in w, finger, uptime or who it just starts the process and uses about 100% CPU for something that should just take one secound to display what you want. Any idea's Bri, 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-hackers" in the body of the message
FreeBSD 4.4-RELEASE - question reguarding 3COM 900TPO 10Mbps net card.
Hi I was previously using FreeBSD 4.2 RELEASE and it ran stable but since I've made a new install on the system on the new hard drive I've put 4.4 RELEASE on the new hard drive and the new Promise TX-2 controller which are both working fine but after 4 or so days the 3COM 900TPO network card on xl0 die's after around this time I know it die's because the light blacks out on the hub and the system then becomes locked up and then it reboots and comes back in ok and a FreeBSD reinitializes the network card again without the need to completely turn off the system. And everything is fine for another 4 days any suggestions that would help are appreciated Thanks Bri, 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-hackers" in the body of the message
cvsup core dumped with
id Thr ead.T closure rootA* waiting for > 11 0x84ca8d4 0x8435d20 Apply *ready* 10 0x8434020 0x8435ce8 Apply A condition 0x8435480 9 0x8435ee0 0x8435cc0 Apply *ready * 8 0x8435db8 0x8436090 DispatcherRun A I/O 7 0x84334a4 0x84 33354 SndrApply A *ready* 6 0x843337c 0x8433344 RecvApply A I/O 5 0x844dc44 0x844dc08 Apply A timer 4 0x8 when updating src-base src-sys and the ports collection. it happened in the cvsupit dialog text style window. seems to be running fine now when i do /usr/local/bin/cvsup -g -L 2 /etc/cvsupfile after the core dump. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Whats with this -> sendto: No buffer space available
I have an interface that dies and its running IPFIREWALL IPDIVERT options in the kernel and the external interface dies the machine becomes unstable and reboots well sometimes other times you have to follow the emergency shutdown procedure it does when that system has become unstable. its a 3com card running on xl0 and of course with all this I'm running divert socket to. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Kal Torak Sent: 07 December 2001 05:38 Cc: FreeBSD Stable; FreeBSD ISP Subject: Re: Whats with this -> sendto: No buffer space available Jonathan Hanna wrote: > > No PPP involved with me, and I think with many others. I agree that the > "no affect" above does look like ordinary buffer exhaustion, though I also have > a working network except for one interface (or maybe divert socket?). Hmmm, perhaps this is related to NAT then??? Only the interface running NAT locks up for me, everything else works normaly... Is everyone with this problem running NAT or a divert socket of some kind on the interface that dies??? 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-hackers" in the body of the message
FW: the crash screen usually after 4 to 13 days not good...
yeah I'm running FreeBSD 4.4 running the lastest kernel 4.4 RELEASE-p1 with kernel options options IPFIREWALL options IPDIVERT options IPFIREWALL_VERBOSE yeah I'll take a look at the handbook on that issue thanks Bri, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: 19 December 2001 20:18 To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: the crash screen usually after 4 to 13 days not good... What happens is the network card on xl0 going to down and its light goes >off on the hub and I get this crash address straight after. > >It's a 3Com 900TPO 10Mbps > >Usually it reboots but its locked this time with it on the screen > >Fatal trap 12: page fault while in kernel mode >Fault virtual address = 0xb0 >Fault code = supervisor read, page not present >Instruction pointer = 0x8:0xc02d7507 >Stack pointer = 0x10:0xc4f8ae50 >Frame pointer = 0x10:0xc4f8ae84 >Code segment = base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 >processor eflags = interrupt enabled, resume, IOPL = 0 >current process= 11999 (sh) >interrupt mask = none >trap number= 12 >panic: page fault > >syncing disks... 10 >done >uptime: 2d18h27m28s > >when I reboot it I will be able to send this e-mail I hope:) > >any help is more than welcome >Bri, >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-stable" in the body of the message --- Please see the FAQ and the handbook about obtaining debugging crashdumps so this problem can be debugged. You also forgot to mention which version of FreeBSD you're running. Kris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: the crash screen usually after 4 to 13 days not good...
I've had the problem with the kernel panic's since I was running 4.2 STABLE and its recently been crashing more often so I've sent to crash dump to the list but the Fatal Trap 12 thing isn't new but it always seems that the network interface dies and then it happens it has got 2 nic's mind. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Slight Problem when Upgrading to 4.5 RC1
when I was upgrading to 4.5 RC1 and I tryed to do make world first in /usr/src and it broke after a several minutes of running so what I did was a make clean and tryed it again and it did the same. I've included the a last bit of the make world where it died. Although when I did a make buildworld everything went ok. Then I compiled the kernel and rebooted and its been running ever since. Bri, makeworld.log Description: Binary data
can any one log into ftp.freebsd.org
I can't. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: can any one log into ftp.freebsd.org
well it can't establish TCP connection or its very slow to connect this isn't usually the case but I can connect to other ftp sites ok i'm using ncftp3. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Peter Pentchev Sent: 01 February 2002 11:10 To: Bri Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: can any one log into ftp.freebsd.org On Fri, Feb 01, 2002 at 11:21:52AM -, Bri wrote: > I can't. It might help if you explained a bit - how exactly is it that you cannot log in? Your client cannot establish a TCP connection to the FTP site, or it does not receive the ProFTPD headers, or it cannot log in as anonymous, or it logs in and then the server terminates the connection with some message/explanation, or...? G'luck, Peter -- Thit sentence is not self-referential because "thit" is not a word. 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-hackers" in the body of the message
weird xl0 thing
I updated my machine to 4.5-RELEASE's lastest cvsup the other day because it was getting lots of crashes caused my the initial release of 4.5 something to do with vm pages but being found and going missing that seems to be fixed as it ran great after the cvs up but last night my computer was quite busy and the interface xl0 looped the message down the screen xl0: command never completed! is the anything that springs to mind that it could be or some sysctl variable I could tweak. the machine is quite an interesting one actually... AMD K5-PR133 48MB Simms/Dimms VX Motherboard Promise Ultra 100 TX2 40GB IBM 60GXP 3Com 900-TPO Kingston card for the secound card. // Both 10Mbps don't laugh it doesn't need to go any faster. well its a nat gateway and samba machine thats why all the disk space on such an elderly chip and board. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
chowning problem or somthing...
%pwd /usr/home %chown testuser4:staff testuser4/ %ls -l | grep testuser4 drwxr-xr-x 2 testuser3 staff 512 Feb 21 15:06 testuser4 %whoami root %uname -r 4.5-RELEASE // Notice how its still owned as testuser3 when I chowned it as testuser4 should own testuser4's directory maybe it does but the ls command isn't displaying it properly I'm not sure is not really a problem to me but its weird. It could be also something to do with me having testuser and testuser2 + 3 & 4 in the same directory. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: the crash screen usually after 4 to 13 days not good...
Well a nice follow up to all of these this is how it goes cvsupd compiled the kernel etc. etc. before I rebooted just over 2 weeks ago and someone has definately fixed something cos its been running ever since. 9:23AM up 20 days, 23:11, 2 users, load averages: 0.01, 0.08, 0.05 the funny thing is I tried all the debug stuff and to no avail none of it could find the problem for me so I thought to myself if I install a debug kernel and it crashes I loose all access to the machine for the rest of the day until and go and reboot it so i installed the normal kernel i used and its behaved ever since. I'm guessing there's been a vm fix or a bug in the xl net driver fixed. Bri, :) // Wonder if this is the end of my problem thread. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Michael Scheidell Sent: 20 December 2001 14:29 To: Bri; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: the crash screen usually after 4 to 13 days not good... - Original Message ----- From: "Bri" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, December 20, 2001 6:09 AM Subject: FW: the crash screen usually after 4 to 13 days not good... > yeah I'm running FreeBSD 4.4 running the lastest kernel 4.4 RELEASE-p1 > > with kernel options > > options IPFIREWALL > options IPDIVERT > options IPFIREWALL_VERBOSE > > yeah I'll take a look at the handbook on that issue thanks from an earler post: Id be currious if its crashing in the same vm section my system is crashing in. From: "Nick Hilliard" Newsgroups: comp.unix.bsd.freebsd.misc Sent: Tuesday, December 11, 2001 2:11 PM Subject: Re: hitting kern.maxfiles causes panic 12 reboot? > Michael Scheidell wrote: > > I know (overall) what the program is, nessusd ver 1.11 > > I increased kern.maxfiles to 8192 and it seems to get past the 4k files open > > point, but still dies. > > hard to directly tell what process is doing it since the panic shows up on > > the (nonexistant) console. > > You could get a crash dump and have a look at it: enable "dumpdev" in > /etc/rc.conf, > and then you should be able to get a kernel stack dump. > > There's more information about doing this sort of thing on: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneld ebug.html > > Nick > > Bri, > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of > [EMAIL PROTECTED] > Sent: 19 December 2001 20:18 > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: the crash screen usually after 4 to 13 days not good... > > > What happens is the network card on xl0 going to down and its light goes > >off on the hub and I get this crash address straight after. > > > >It's a 3Com 900TPO 10Mbps > > > >Usually it reboots but its locked this time with it on the screen > > > >Fatal trap 12: page fault while in kernel mode > >Fault virtual address = 0xb0 > >Fault code = supervisor read, page not present > >Instruction pointer = 0x8:0xc02d7507 > >Stack pointer = 0x10:0xc4f8ae50 > >Frame pointer = 0x10:0xc4f8ae84 > >Code segment = base 0x0, limit 0xf, type 0x1b > > = DPL 0, pres 1, def32 1, gran 1 > >processor eflags = interrupt enabled, resume, IOPL = 0 > >current process = 11999 (sh) > >interrupt mask = none > >trap number = 12 > >panic: page fault > > > >syncing disks... 10 > >done > >uptime: 2d18h27m28s > > > >when I reboot it I will be able to send this e-mail I hope:) > > > >any help is more than welcome > > >Bri, > > >To Unsubscribe: send mail to [EMAIL PROTECTED] > >with "unsubscribe freebsd-stable" in the body of the message > --- > > Please see the FAQ and the handbook about obtaining debugging > crashdumps so this problem can be debugged. You also forgot to > mention which version of FreeBSD you're running. > > Kris > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Question about the compile a kernel for Sparc
if i install FreeBSD 5.0-DP1 on i386 or upgrade my 4.5-RELEASE would I be able to compile a sparc kernel by going into the conf directory for the sparc architechure and configuring a new config file and then doing as follows. assuming here I have the sources already installed. config MY_KERNEL_CONFIG cd ../../compile/sparc64 make depend make am I right in thinking that make install would install my a sparc64 bootable kernel. or would I need extra tools for cross compiling I think I would cos you did for the powerpc port that I never got around to going all the way with. any help appreciated. Bri, To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
weird problem xl0 interface
I do ifconfig xl0 delete then dhclient -cf /etc/dhclient.conf -lf /var/db/dhclient.leases xl0 and I get a kernel message every few secounds xl0: watchdog timeout I've not a clue what it means but I do know that dhclient never detects the ip address from the ISP. allthough I put the same card in my other 4.4-RELEASE machine and it all goes fine the the only difference is that my other machine is running 4.4-RELEASE-p7 and thats about it. could some type of IRQ conflict be causing it. the kernel has options IPDIVERT IPFIREWALL IPFIREWALL_VERBOSE any help appreciated Bri, To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Problem: Too Many open files
Hi I'm getting a Too Many open files message on a FreeBSD 4.5-RELEASE machine of mine I originally had the disk in a AMD k5 150 machine with 48MB or RAM and it ran fine and the drive was on the Promise Ultra TX2 controller card and it all worked fine. Now that I've put the drive in a much bigger machine with 500 K6-2 with 512MB or ram it starts getting a Too many open files problem Even trying to run ls -l gives the messages all though my net access stays running as natd continues not matter what it seems it says its something to do with /dev/kmem but I'm not sure what this does with memory. I don't see any reason a bigger machine should fail where a smaller one worked fine maybe I should cvsup my kernel sources my current compile is Feburary 29 09:53am 2002 maybe a bit old. oh yeah the Hard disk is my trusty IBM 40GB the 7200RPM with 2MB Cache model which has always worked great. any help appreicated. Bri, To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
dhcp problems with my ISP
Hi I have a Cable and have a Cable Modem for my internet connection of which you use dhcp to obtain an IP address great but this only seems to work successfully on a Windows machine I've registered all the other mac addresses of unix boxes and Apple macs I have and they seem to have alot of difficulty obtaining IP addresses. Especially the UNIX machines which run FreeBSD 4.5-RELEASE or 5.0-CURRENT on sparc64 at the moment the sparc64 box which is a Sun Ultra 5 which is the worst for detecting an IP with dhclient. What I would really like to know is what does the windows dhcp do differently than say dhclient. I would be very interested to know as I would like a UNIX machine that can maintain and IP address. Bri, To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
UFS Disk partitions
Does anyone have any information regarding recovering diskpartitions as the machine crash in heavy I/O to that disk i've lost being able to fsck the drive and of course be able to mount it which means I'm quite lost in the way of how to recover the data. Any help apprieciated Bri, To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
