Urgent; stable problem on Intel MB
I have cvsup'd daily since Feb1 and recompiled. I cannot get a successful boot out of any kernel. GENERIC, MYKERNEL, anything. Mergemaster has been done. I have 2 different servers.. one ASUS, one Intel 440bx. Asus builds and boots fine, however the Intel gets 'Fatal trap 12 caught while in kernel mode'. Seeing how another Intel user had the same problem it must be an issue. Could someone please advise? I have backups and I am currently booting from kernel.backup (thank the good man above). I really wish I could have a successful boot :( Jeff. _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ipfw query..
sysctl -w net.inet.ip.fw.one_pass=0 This flag allows packets to pass through the pipes, until they are accepted by a pass or fail rule. But the configuration can be tricky. Another way is to place your packet processing (such as natd) first, then pass through the pipes. --Mike Chris Elsworth wrote: On Thu, Feb 15, 2001 at 02:05:11pm +, Simon Loader wrote: Bradley Kite wrote: I'm sure there is a flag you can append to the end of the pipe rules, that tell ipfw to continue going through the rules instead of stopping when they match. I cant remember what the flag is tho, sorry :-( [...] If I don't put the pipes first then I can't bandwidth limit, because when the packets go through one of the allow rules, to, say, sshd - then they'll never see the pipe and won't get limited or counted. So the pipes have to come first.. -- Chris Elsworth tel: 020 8371 1041_. Systems Administratormob: 07968 324 693 demon @ thus . . Web Hosting Team [EMAIL PROTECTED] http://www.demon.net 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: Urgent; stable problem on Intel MB
At 02:46 PM 2/16/01 +, Jeffrey Sewell wrote: I have cvsup'd daily since Feb1 and recompiled. I cannot get a successful boot out of any kernel. GENERIC, MYKERNEL, anything. Mergemaster has been done. I have 2 different servers.. one ASUS, one Intel 440bx. Asus builds and boots fine, however the Intel gets 'Fatal trap 12 caught while in kernel mode'. Seeing how another Intel user had the same problem it must be an issue. Could someone please advise? I have backups and I am currently booting from kernel.backup (thank the good man above). I really wish I could have a successful boot :( Jeff. Reseat your memory on that box. -Carroll Kong To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Urgent; stable problem on Intel MB
Jeffrey Sewell schrieb: I have cvsup'd daily since Feb1 and recompiled. I cannot get a successful boot out of any kernel. GENERIC, MYKERNEL, anything. Mergemaster has been done. I have 2 different servers.. one ASUS, one Intel 440bx. Asus builds and boots fine, however the Intel gets 'Fatal trap 12 caught while in kernel mode'. Seeing how another Intel user had the same problem it must be an issue. Could someone please advise? I have backups and I am currently booting from kernel.backup (thank the good man above). I really wish I could have a successful boot :( Sorry, without facts a solution will be impossible. If your machine crashed during compiles, most likely you got faulty hardware. OTOH, it is possible to compile a kernel without needed hardware support. Have a look at http://www.freebsd.org/handbook/kernelconfig.html before asking again. it tells what to ask for, too. HTH -Christoph Sold To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Drive not coming up
Michael DeMutis schrieb: Hi there. I'm running the 3.X stable tree. I added another hard drive, and went to /stand/sysinstall to install the drive. That all worked fine, I used DiskLabel to set my mount point to /backup It all works fine, until I reboot. When I reboot the drive is not mounted, and I have to use DiskLabel again in order to get the drive to show up. I don't lose any data in the process, it's just an inconvienience. Another thing to note is that the drive is not listing in /etc/fstab Here is my /etc/fstab# DeviceMountpoint FStype Options DumpPass# /dev/da0s1b noneswapsw 0 0 /dev/da0s1a / ufs rw 1 1 /dev/da0s1f /usrufs rw 2 2 /dev/da0s1e /varufs rw 2 2 proc/proc procfs rw 0 0 Sysinstall cannot add the entry for your new drive automtically. Assuming you added a second SCSI disk with just one big partition, inserting this line into fstab will help: /dev/da1s0e /new/mount/pointufs rw 2 2 HTH -Christoph Sold To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Fatal trap 12 during boot
[Note: not forwarded to list because of stuid guess. No real answer here.] Stupid guess: your acd0: CDROM MATSHITA CR-176 does things it should better not. Just for fun, disconnect the gizmo (or build a kernel without ATAPI), then try again. HTH -Christoph Sold Bjoern Groenvall schrieb: Dear Sirs, Today I cvsup:ed 4.2-STABLE and built a new kernel. The new kernel receives a "Fatal trap 12" where it usually prints "Waiting 3 seconds for SCSI devices to settle". Does anybody have any hints about what's wrong? Dmesg output and config file is attached. Cheers, Bjoern - FreeBSD 4.2-STABLE #0: Mon Feb 12 19:21:02 CET 2001 root@:/usr/src/sys/compile/KRUMELUR Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 799620991 Hz CPU: Pentium III/Pentium III Xeon/Celeron (799.62-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CM OV,PAT,PSE36,MMX,FXSR,SSE real memory = 536805376 (524224K bytes) avail memory = 517849088 (505712K bytes) [snip] ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppi0: Parallel I/O on ppbus0 acd0: CDROM MATSHITA CR-176 at ata0-master using PIO4 Fatal trap 12: page fault while in kernel mode [snip] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
More than 256 pty's
Hey, I'm currently running into difficulties on a multiuser system, (4.2-STABLE) we have 256 pty's (for some reason we still have pseudo-device pty 256, in the kernel conf...), and we are running out. Last year we ran into the same problem (February seems to be a busy month) and I believe that we followed the instructions in http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=8198069+8200098+/usr/local/www/db/text/1999/freebsd-questions/19990607.freebsd-questions quote You can have more than 256 ptys; the problem is what to name them. You can easily get 384 ptys by extending the current scheme slightly (using /dev/tty[tuTU]*; /dev/ttyv* is syscons so we hit our limit with this naming scheme). Edit /dev/MAKEDEV and /usr/src/lib/libutil/pty.c /quote However, I can't remember what we did (if we did at all) to MAKEDEV to overcome the 256 minor number limit. Can anyone help us out ? What is the possibility of creating more than 256 pty/tty devices ? If not, are there any plans to overcome this hard limit in the future ? Cheers, - bobb -- Oft it may chance that old wives keep in memory word of things that once were needful for the wise to know. - Celeborn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
openssh not setting DISPLAY
-stable of yesterday X 4.02 openssh, moving from /usr/ports/security/ssh1 going in with protocol 1 user's shell is bash DISPLAY env var not being set. i expect `hostname`:10.0 x forward not seeming to happen even if i set it manually. Port 22 Protocol 2,1 #ListenAddress 0.0.0.0 #ListenAddress :: HostKey /etc/ssh/ssh_host_key HostDsaKey /etc/ssh/ssh_host_dsa_key ServerKeyBits 768 LoginGraceTime 120 KeyRegenerationInterval 3600 PermitRootLogin yes # ConnectionsPerPeriod has been deprecated completely # After 10 unauthenticated connections, refuse 30% of the new ones, and # refuse any more than 60 total. MaxStartups 10:30:60 # Don't read ~/.rhosts and ~/.shosts files IgnoreRhosts yes # Uncomment if you don't trust ~/.ssh/known_hosts for RhostsRSAAuthentication #IgnoreUserKnownHosts yes StrictModes yes X11Forwarding yes X11DisplayOffset 10 PrintMotd yes KeepAlive yes randy, feeling stoopider than usual To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Fatal trap 12 during boot
Om det skulle behövas, men det tror jag inte. /Björn --- [Note: not forwarded to list because of stuüid guess. No real answer here.] Stupid guess: your acd0: CDROM MATSHITA CR-176 does things it should better not. Just for fun, disconnect the gizmo (or build a kernel without ATAPI), then try again. HTH -Christoph Sold Bjoern Groenvall schrieb: Dear Sirs, Today I cvsup:ed 4.2-STABLE and built a new kernel. The new kernel receives a "Fatal trap 12" where it usually prints "Waiting 3 seconds for SCSI devices to settle". Does anybody have any hints about what's wrong? Dmesg output and config file is attached. Cheers, Bjoern - FreeBSD 4.2-STABLE #0: Mon Feb 12 19:21:02 CET 2001 root@:/usr/src/sys/compile/KRUMELUR Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 799620991 Hz CPU: Pentium III/Pentium III Xeon/Celeron (799.62-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CM OV,PAT,PSE36,MMX,FXSR,SSE real memory = 536805376 (524224K bytes) avail memory = 517849088 (505712K bytes) [snip] ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppi0: Parallel I/O on ppbus0 acd0: CDROM MATSHITA CR-176 at ata0-master using PIO4 Fatal trap 12: page fault while in kernel mode [snip] -- _ _ ,___. Bjorn Gronvall (Björn Grönvall)/___/| Swedish Institute of Computer Science | || PO Box 1263, S-164 29 Kista, Sweden| Schroedingers || Email: [EMAIL PROTECTED], Phone +46 -8 633 15 25 | Cat |/ Cellular +46 -70 768 06 35, Fax +46 -8 751 72 30 `---' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ipfw query..
In message [EMAIL PROTECTED] Mike Bytnar writes: : This flag allows packets to pass through the pipes, until they are accepted by a : pass or fail rule. But the configuration can be tricky. : Another way is to place your packet processing (such as natd) first, then pass : through the pipes. Withouth this flag, do I need to do special things if I'm just filtering packets? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: More than 256 pty's
On Fri, 16 Feb 2001 17:28:54 + Robert bobb Crosbie [EMAIL PROTECTED] wrote: RC quote RC You can have more than 256 ptys; the problem is what to name them. You RC can easily get 384 ptys by extending the current scheme slightly (using RC /dev/tty[tuTU]*; /dev/ttyv* is syscons so we hit our limit with this RC naming scheme). Edit /dev/MAKEDEV and /usr/src/lib/libutil/pty.c RC /quote It looks to me like you also have to hack around in kern/tty_pty.c, there are hard coded assumptions in there about 256 minor numbers being mapped. Also comments about doing something about it, the mapping is defined in there. Making it work above 256 doesn't look hard, agreeing on a naming convention might be harder :) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: openssh not setting DISPLAY
Randy Bush [EMAIL PROTECTED] probably said: -stable of yesterday X 4.02 openssh, moving from /usr/ports/security/ssh1 DISPLAY env var not being set. i expect `hostname`:10.0 x forward not seeming to happen even if i set it manually. /etc/ssh/ssh_config Host * ForwardX11 yes P. -- pir [EMAIL PROTECTED][EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: openssh not setting DISPLAY
I had the same problem. I fixed it by putting ForwardX11 yes in /etc/ssh_config (I am assuming that here you are showing sshd_config). (Somehow I think ForwardX11 yes should be the default, but it seems not to be.) Randy Bush wrote: -stable of yesterday X 4.02 openssh, moving from /usr/ports/security/ssh1 going in with protocol 1 user's shell is bash DISPLAY env var not being set. i expect `hostname`:10.0 x forward not seeming to happen even if i set it manually. Port 22 Protocol 2,1 #ListenAddress 0.0.0.0 #ListenAddress :: HostKey /etc/ssh/ssh_host_key HostDsaKey /etc/ssh/ssh_host_dsa_key ServerKeyBits 768 LoginGraceTime 120 KeyRegenerationInterval 3600 PermitRootLogin yes # ConnectionsPerPeriod has been deprecated completely # After 10 unauthenticated connections, refuse 30% of the new ones, and # refuse any more than 60 total. MaxStartups 10:30:60 # Don't read ~/.rhosts and ~/.shosts files IgnoreRhosts yes # Uncomment if you don't trust ~/.ssh/known_hosts for RhostsRSAAuthentication #IgnoreUserKnownHosts yes StrictModes yes X11Forwarding yes X11DisplayOffset 10 PrintMotd yes KeepAlive yes randy, feeling stoopider than usual To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message -- Stephen Montgomery-Smith [EMAIL PROTECTED] 307 Math Science Building [EMAIL PROTECTED] Department of Mathematics [EMAIL PROTECTED] University of Missouri-Columbia Columbia, MO 65211 USA Phone (573) 882 4540 Fax (573) 882 1869 http://www.math.missouri.edu/~stephen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message