Re: pppd crashes, was: kde-freebsd] Question about KPPP on FreeBSD
On Sunday, 11. February 2007 02:43, Bruce M. Simpson wrote: So far so good. The problem is that the BSD magicians and the KDE GUI magicians are not sharing their spell-books, and thus, their models of how the code operates; the communities have to intersect somehow. That could be you, y'know. Human bridges are just as, if not more, important as ISO/OSI Layer 2 devices. :^) Quite true. However, this particular human bridge between developer communities is running at capacity already. We need some trunking here. Redundant links, y'know. When I said someone, I *do* mean someone who isn't me (and whose idea of communication isn't yelling at developers in bugzilla). :) -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpLeeG7cwMsu.pgp Description: PGP signature
Re: What is a good choice of sata-ii raid controller for freebsd?
Hello! On Fri, Feb 09, 2007 at 06:15:53PM +0300, Artem Kuchin wrote: Under gmirror OS must issue two commands to write to disks and some commands to check/set mark that mirrored data is intact. Under hardware RAID OS issue sonly one command to write and no checking command, since raid controller handles this async. So, software OS raid must be slower than controller based raid anyway. Yes. The OS has got to do a bit more work that is otherwise done by the CPU on the RAID controller. For modern CPUs this extra work is measurably neglegible. One guy that I happen to know, who was responsible for the database backend servers of Germany's biggest web mail provider at the time, ran extensive benchmarks. Result: for RAID 1, RAID 0 and RAID 1+0 there is no difference in hardware RAID vs. OS mirroring and striping. He used Linux, but I'd bet a huge amount that his findings can be transferred to arbitrary current operating systems. RAID 5 and RAID 6 are different beasts alltogether, but you do not want RAID 5 for transaction heavy systems, anyway. When you are running a huge DB that is not read mostly, you want to have your working set in memory. If the database needs to write to disk, eventually, it's all about latency. And latency on RAID 5 is horrendous, regardless if implemented in hardware RAID or not. Kind regards, Patrick -- punkt.de GmbH * Vorholzstr. 25 * 76137 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 [EMAIL PROTECTED] http://www.punkt.de Gf: Jürgen Egeling AG Mannheim 108285 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pppd crashes, was: kde-freebsd
On Sat, 2007-02-10 at 03:06 +0100, Michael Nottebrock wrote: [ snip ] All that your bug report accomplishes is broadcasting your bad and uninformed attitude to an even bigger audience. It is in your own and the FreeBSD community's best interest to backtrack before anyone gets to form a negative opinion on both. I just took a look at the list of bugs in pppd. Aside from being unmaintained it looks as though the functionality is still okay. This is borne out my experience using pppd with my wireless modem. Just last night on a trip from JFK in fact. Opinion is getting more important with the market arrival of affordable EVDO coverage and cards. EVDO is a wireless technology for connecting to the net. The connection speeds are between 700 ~ 3000 kb/s I nearly passed on the opportunity to get one card due to reports that FreeBSD 6.1 and 6.2 had rendered kernel ppp unusable. In the current generation these cards are very fast serial modems that connect to the USB bus. They configure exactly like a serial connected modem and ppp stack. They are primarily configured for windows but configurations for kernel pppd primarily for Linux and Mac OSX are readily available on the Internet. The argument for EVDO cards also holds for bluetooth enabled phones. With Verizon and Sprint allowing you to use the bluetooth stack in your phone to connect to the Internet at EVDO speeds for a nominal fee, we should expect more people and try to use FreeBSD in this manner. When they do they will com from Linux with a kernel pppd configuration. -- Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPv6 over gif(4) broken in 6.2-RELEASE?
On Fri, 09 Feb 2007 23:21:33 +0100, Dimitry Andric [EMAIL PROTECTED] said: Bruce A. Mah wrote: I've convinced myself that this problem needs to be tested in isolation (i.e. you have complete control over both ends of the tunnel) because incoming packets over the tunnel cause the host route to get added automatically if it wasn't there already. After reading the code and discussing this with a couple folks, I've managed to convince myself that 1.48.2.14 and 1.48.2.15 (and their analogues on HEAD) need to go away. I've committed diffs that back these out, and they solve the problem for me in my testing (which I've done with two VMs in isolation). The applicable revisions for nd6.c are 1.74 (HEAD) and 1.48.2.18 (RELENG_6). Updating up to (or beyond) these revisions should clear up the problem. Confirmed. I've updated the machine on which I originally had this problem to -STABLE as of today, and the problem has disappeared. I thought it was also planned to be incorporated to RELENG_6_2, right? JINMEI, Tatuya Communication Platform Lab. Corporate RD Center, Toshiba Corp. [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPv6 over gif(4) broken in 6.2-RELEASE?
JINMEI Tatuya / 神明達哉 wrote: Confirmed. I've updated the machine on which I originally had this problem to -STABLE as of today, and the problem has disappeared. I thought it was also planned to be incorporated to RELENG_6_2, right? I'm not sure if non-security related fixes are considered for release branches. Also, there's a workaround mentioned on the 6.2 errata page, under Known Issues: http://www.freebsd.org/releases/6.2R/errata.html Then again, it's really up to the release engineering team whether they deem this critical enough. :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSd 6.1 to 6.2 upgrade kernel errors: unknown: I/O range not supported
Hi list, Last Friday I upgraded my 6.1 to 6.2. This box is Compaq DL320G1 with the all latest firmwares running only cvsup-mirror service for other servers. No customization, any extra setting, default setup whatsoever. The upgrade went fine, no problems I encountered. It was not binary upgrade and I must admit that it was my FIRST upgrade on FreeBSD so followed basically the handbook step by step. After the upgrade at reboot I get weird errors (I/O range not supported) I don't quite like hence not dare to proceed with other production servers. The box behaves normal but these messages just make me concerned not to mention that at a certain stage (finding HW RAID array) the box hangs for a minute (didn't do before, HDD goes nuts) then mounts partitions and proceeds the boot process. Here it is my verbose dmesg: Copyright (c) 1992-2007 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-RELEASE #0: Fri Feb 9 08:52:41 NZDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel /boot/kernel/kernel at 0xc0b55000. Preloaded elf module /boot/kernel/acpi.ko at 0xc0b550cc. Table 'FACP' at 0xe80d0 Table 'APIC' at 0xe8144 MADT: Found table at 0xe8144 MP Configuration Table version 1.4 found at 0xc00f0b30 APIC: Using the MADT enumerator. MADT: Found CPU APIC ID 0 ACPI ID 0: enabled ACPI APIC Table: Calibrating clock(s) ... i8254 clock: 1193168 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 1258216274 Hz CPU: Intel(R) Pentium(R) III CPU family 1266MHz (1258.22-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6b1 Stepping = 1 Features=0x383fbff real memory = 268435456 (256 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x0010 - 0x003f, 3145728 bytes (768 pages) 0x00c25000 - 0x0fb3dfff, 250712064 bytes (61209 pages) avail memory = 253149184 (241 MB) bios32: Found BIOS32 Service Directory header at 0xc00fa000 bios32: Entry = 0xeca00 (c00eca00) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xeca00+0x1036 pnpbios: Found PnP BIOS data at 0xc00f7b10 pnpbios: Entry = f:6529 Rev = 1.0 Other BIOS signatures found: APIC: CPU 0 has ACPI ID 0 MADT: Found IO APIC ID 8, Interrupt 0 at 0xfec0 ioapic0: Routing external 8259A's -gt; intpin 0 ioapic0: intpin 0 -gt; ExtINT (edge, high) ioapic0: intpin 1 -gt; ISA IRQ 1 (edge, high) ioapic0: intpin 2 -gt; ISA IRQ 2 (edge, high) ioapic0: intpin 3 -gt; ISA IRQ 3 (edge, high) ioapic0: intpin 4 -gt; ISA IRQ 4 (edge, high) ioapic0: intpin 5 -gt; ISA IRQ 5 (edge, high) ioapic0: intpin 6 -gt; ISA IRQ 6 (edge, high) ioapic0: intpin 7 -gt; ISA IRQ 7 (edge, high) ioapic0: intpin 8 -gt; ISA IRQ 8 (edge, high) ioapic0: intpin 9 -gt; ISA IRQ 9 (edge, high) ioapic0: intpin 10 -gt; ISA IRQ 10 (edge, high) ioapic0: intpin 11 -gt; ISA IRQ 11 (edge, high) ioapic0: intpin 12 -gt; ISA IRQ 12 (edge, high) ioapic0: intpin 13 -gt; ISA IRQ 13 (edge, high) ioapic0: intpin 14 -gt; ISA IRQ 14 (edge, high) ioapic0: intpin 15 -gt; ISA IRQ 15 (edge, high) MADT: Found IO APIC ID 3, Interrupt 16 at 0xfec01000 ioapic1: intpin 0 -gt; PCI IRQ 16 (level, low) ioapic1: intpin 1 -gt; PCI IRQ 17 (level, low) ioapic1: intpin 2 -gt; PCI IRQ 18 (level, low) ioapic1: intpin 3 -gt; PCI IRQ 19 (level, low) ioapic1: intpin 4 -gt; PCI IRQ 20 (level, low) ioapic1: intpin 5 -gt; PCI IRQ 21 (level, low) ioapic1: intpin 6 -gt; PCI IRQ 22 (level, low) ioapic1: intpin 7 -gt; PCI IRQ 23 (level, low) ioapic1: intpin 8 -gt; PCI IRQ 24 (level, low) ioapic1: intpin 9 -gt; PCI IRQ 25 (level, low) ioapic1: intpin 10 -gt; PCI IRQ 26 (level, low) ioapic1: intpin 11 -gt; PCI IRQ 27 (level, low) ioapic1: intpin 12 -gt; PCI IRQ 28 (level, low) ioapic1: intpin 13 -gt; PCI IRQ 29 (level, low) ioapic1: intpin 14 -gt; PCI IRQ 30 (level, low) ioapic1: intpin 15 -gt; PCI IRQ 31 (level, low) MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 -gt; intpin 2 ioapic0: intpin 2 trigger: edge ioapic0: intpin 2 polarity: high MADT: Interrupt override: source 9, irq 9 ioapic0: intpin 9 trigger: level ioapic0: intpin 9 polarity: low lapic0: Routing NMI -gt; LINT1 lapic0: LINT1 trigger: edge lapic0: LINT1 polarity: high ioapic1 irqs 16-31 on motherboard ioapic0 irqs 0-15 on motherboard cpu0 BSP: ID: 0x VER: 0x00040011 LDR: 0x DFR: 0x lint0: 0x00010700 lint1: 0x0400 TPR: 0x SVR: 0x01ff timer: 0x000100ef therm: 0x err: 0x000100f0 pcm: 0x0001 wlan: ath_rate: version 1.2 null: random: nfslock: pseudo-device io: kbd: new array size 4 kbd1 at kbdmux0 mem: Pentium Pro MTRR support
Re: IPv6 over gif(4) broken in 6.2-RELEASE?
If memory serves me right, Dimitry Andric wrote: JINMEI Tatuya / 神明達哉 wrote: Confirmed. I've updated the machine on which I originally had this problem to -STABLE as of today, and the problem has disappeared. I thought it was also planned to be incorporated to RELENG_6_2, right? I'm not sure if non-security related fixes are considered for release branches. Also, there's a workaround mentioned on the 6.2 errata page, under Known Issues: Yes, we do this (most releases nowadays have at least a couple of errata notices / patches). http://www.freebsd.org/releases/6.2R/errata.html Then again, it's really up to the release engineering team whether they deem this critical enough. :) Its a joint decision between re@ and [EMAIL PROTECTED] I *am* on re@, and I'd planned on getting this change into RELENG_6_2, but I'm seriously ENOTIME (now trying to type one-handed with my sleeping two-week-old son in the other hand). I'll send a copy of this to re@, hopefully one of us will do this. Cheers, Bruce. signature.asc Description: OpenPGP digital signature
releng_6 (and possibly releng_6_2) missing force option to mount?
I've upgraded my laptop from 6.2-prerelease to latest 6-stable and it stuck at booting because mount can't recognize force option in the fstab. The file system is ext2fs and this looks like a genuine regression. signature.asc Description: OpenPGP digital signature
Re: What is a good choice of sata-ii raid controller for freebsd?
In mpc.lists.freebsd.stable, you wrote: : For modern CPUs this extra work is measurably neglegible. With all of the interrupt activity it seems counterintuitive that it would be negligible in that the processor is incurring many extra cache faults to service the controller. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What is a good choice of sata-ii raid controller for freebsd?
On Monday 12 February 2007 00:34, Patrick M. Hausen wrote: One guy that I happen to know, who was responsible for the database backend servers of Germany's biggest web mail provider at the time, ran extensive benchmarks. Result: for RAID 1, RAID 0 and RAID 1+0 there is no difference in hardware RAID vs. OS mirroring and striping. He used Linux, but I'd bet a huge amount that his findings can be transferred to arbitrary current operating systems. Software RAID won't help you if your primary disk gets an error in, say, the second stage loader. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpUoo0cmQXSe.pgp Description: PGP signature
Re: What is a good choice of sata-ii raid controller for freebsd?
Hi, all! On Mon, Feb 12, 2007 at 09:40:18AM +1030, Daniel O'Connor wrote: On Monday 12 February 2007 00:34, Patrick M. Hausen wrote: One guy that I happen to know, who was responsible for the database backend servers of Germany's biggest web mail provider at the time, ran extensive benchmarks. Result: for RAID 1, RAID 0 and RAID 1+0 there is no difference in hardware RAID vs. OS mirroring and striping. He used Linux, but I'd bet a huge amount that his findings can be transferred to arbitrary current operating systems. Software RAID won't help you if your primary disk gets an error in, say, the second stage loader. I don't really buy this booting arguement. What's the failure scenario here? If the system is up and running, it will just keep humming along. The SCSI or ATA layer is supposed to detach a failed drive and geom will disable one part of the mirror. You can react appropriately when you get the failure message. Regards, Patrick -- punkt.de GmbH * Vorholzstr. 25 * 76137 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 [EMAIL PROTECTED] http://www.punkt.de Gf: Jürgen Egeling AG Mannheim 108285 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Intermittent network issues with Freebsd 6.2
Hi All, I am having intermittent network issues with our IBM X236 dual xeon server. Server comes with two bge network cards. At random intervals internal lan drops out. And then few minutes later it comes back online. So far I can only find some interface errors on netstat -i. Can anyone help me to resolve this issue. Please refer to attached files and below outputs for more information. /etc/sysctl.conf kern.ipc.maxsockbuf=8388608 kern.ipc.somaxconn=2048 net.inet.tcp.sendspace=3217968 net.inet.tcp.recvspace=3217968 net.inet.tcp.rfc1323=1 #net.inet.tcp.rfc3042=0 net.inet.ip.portrange.hilast=65535 net.inet.ip.portrange.hifirst=49152 net.inet.ip.portrange.last=65535 net.inet.ip.portrange.first=1024 net.inet.tcp.inflight.enable=0 /boot/loader.conf kern.ipc.nmbclusters=32768 vmstat -i interrupt total rate irq52: ips075446 17 irq30: ahd0 81 0 irq31: ahd1 15 0 irq1: atkbd0 69 0 irq3: sio174 0 irq4: sio067 0 irq6: fdc090 0 irq14: ata0 47 0 irq16: bge0 bge1+1395326315 irq19: uhci1 15 0 irq23: ehci0 1 0 cpu0: timer 8845847 1998 cpu3: timer1 0 cpu1: timer2 0 cpu2: timer 8830658 1995 Total 19147739 4326 netstat -i NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll bge0 1500 Link#1 00:11:25:e9:7f:58 392325 880 449420 0 0 bge0 1500 192.168.1 lan 342652 - 4175 - - bge1 1500 Link#2 00:11:25:e9:7f:59 369744 1648 363688 0 0 Regards Dimuthu Parussalla Copyright (c) 1992-2007 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-STABLE #0: Tue Feb 6 18:13:39 EST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BSG WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant WARNING: MPSAFE network stack disabled, expect reduced performance. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.80GHz (3800.16-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf43 Stepping = 3 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SS E2,SS,HTT,TM,PBE Features2=0x659dSSE3,RSVD2,MON,DS_CPL,EST,TM2,CNTX-ID,CX16,b14 AMD Features=0x2000LM Logical CPUs per core: 2 real memory = 2147266560 (2047 MB) avail memory = 2096476160 (1999 MB) ACPI APIC Table: IBMSERONYXP FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic2 Version 2.0 irqs 48-71 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: IBM SERONYXP on motherboard acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x588-0x58b on acpi0 cpu0: ACPI CPU on acpi0 acpi_perf0: ACPI CPU Frequency Control on cpu0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge on acpi0 pci0: ACPI PCI bus on pcib0 pci0: unknown at device 0.1 (no driver attached) pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci2: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 0.0 on pci2 pci3: ACPI PCI bus on pcib2 ahd0: Adaptec AIC7902 Ultra320 SCSI adapter port 0x4000-0x40ff,0x4100-0x41ff mem 0xcfffe000-0xcfff irq 30 at device 7.0 on pci3 ahd0: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs ahd1: Adaptec AIC7902 Ultra320 SCSI adapter port 0x4200-0x42ff,0x4300-0x43ff mem 0xcfffc000-0xcfffdfff irq 31 at device 7.1 on pci3 ahd1: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel B,
Re: What is a good choice of sata-ii raid controller for freebsd?
On Monday 12 February 2007 10:21, Patrick M. Hausen wrote: Software RAID won't help you if your primary disk gets an error in, say, the second stage loader. I don't really buy this booting arguement. What's the failure scenario here? If the system is up and running, it will just keep humming along. The SCSI or ATA layer is supposed to detach a failed drive and geom will disable one part of the mirror. You can react appropriately when you get the failure message. Sure, if you're present. I regularly ship systems overseas where the power fails frequently. The inability to boot because one disk got hosed is Bad News (tm). It depends on your exact situation, I was just pointing out that SW RAID doesn't cover all the bases HW RAID does. Murphy dictates that the moment one of your disks down your system will glitch/panic/etc and reboot and then you'll be stuffed :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpqYtKYMRj3q.pgp Description: PGP signature
PXEboot fails at kernel (text) loading
Hi, I have a FreeBSD 6.1 PC as the server to a PXE boot of another Compaq Deskpro EN PC. The Compaq PC has the option of a Network Service Boot with the F12-key during BIOS boot up. On the server, tftpd, bootpd and dhcpd are all working well. For the diskless kernel config I have used the GENERIC one, but added: options BOOTP options BOOTP_NFSROOT options BOOTP_COMPAT When all this is in place, and I reboot the client PC, the PXE works fine and I get the Welcome to FreeBSD! window, that allows me to choose from a list of options: 1. Boot FreeBSD [default] 2. Boot FreeBSD with ACPI enabled 3. Boot FreeBSD in Safe Mode 4. Boot FreeBSD in single user mode 5. Boot FreeBSD with verbose logging 6. Escape to loader prompt 7. Reboot Now whatever option (1 to 5) I choose here, I always get: /boot/kernel/kernel text=0x4d568c / and the last slash is rotating for a very tiny while after which the system kind of implodes, blanks the screen and reboots from BIOS. Apparently something goes very, very wrong when loading the text part of the kernel. On the server, I've checked the /var/log/xferlog, which has entries like this: read request for //pxeboot: success read request for /boot/loader.rc: success read request for /boot/loader.4th: success read request for /boot/support.4th: success read request for /boot/beastie.4th: success read request for /boot/screen.4th: success read request for /boot/frames.4th: success read request for /boot/kernel/kernel: success read request for /boot/kernel/kernel: success Is it OK to have a double kernel read at the last two lines? Any idea what's wrong here or what I could do to further test what the actual problem is? Thanks, Rob. We won't tell. Get more on shows you hate to love (and love to hate): Yahoo! TV's Guilty Pleasures list. http://tv.yahoo.com/collections/265 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
