Re: VIA Rhine II network card
Dnia 16-11-2004, Wto o godzinie 13:38 +1030, Daniel O'Connor napisa(a): On Tue, 16 Nov 2004 13:27, Zoltan Frombach wrote: It could be a full-duplex/half duplex mismatch issue. Try not to use auto-negotiation. You can set your interface to fixed full-duplex (or half-duplex) in /etc/rc.conf You must match the setting with the other side of your connection (eg. your switch). I've found vr(4) devices (which are very common in Via chipset motherboards) don't like talking to some switches and I need to force half duplex then unplug and replug the cable :( I've tried all possible combinations with media and mediaopts, and I get nothing. When I try to set half-duplex it doesn't work at all. I didn't mentioned before that under FreeBSD 4.10 everything worked fine. I found also some interesting (but not clear for me) behaviour of ping: $ ping 213.25.86.88 [cut few lines] 64 bytes from 213.25.86.88: icmp_seq=5 ttl=64 time=0.311 ms 64 bytes from 213.25.86.88: icmp_seq=6 ttl=64 time=0.944 ms 92 bytes from 192.168.3.1: Redirect Host(New addr: 213.25.86.88) Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 0054 0105 0 40 01 8a7d 192.168.3.13 213.25.86.88 64 bytes from 213.25.86.88: icmp_seq=7 ttl=64 time=0.314 ms 64 bytes from 213.25.86.88: icmp_seq=8 ttl=64 time=0.288 ms I'm not local network, my IP is 192.168.3.13, 192.168.3.1 is my gateway. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VIA Rhine II network card
On Tue, 16 Nov 2004 19:22, Tomek Tylec wrote: I've found vr(4) devices (which are very common in Via chipset motherboards) don't like talking to some switches and I need to force half duplex then unplug and replug the cable :( I've tried all possible combinations with media and mediaopts, and I get nothing. When I try to set half-duplex it doesn't work at all. I didn't mentioned before that under FreeBSD 4.10 everything worked fine. Hmm, I'm not sure what changed sorry - perhaps you could look for changes in the code by using cvsweb.freebsd.org. I found also some interesting (but not clear for me) behaviour of ping: $ ping 213.25.86.88 [cut few lines] 64 bytes from 213.25.86.88: icmp_seq=5 ttl=64 time=0.311 ms 64 bytes from 213.25.86.88: icmp_seq=6 ttl=64 time=0.944 ms 92 bytes from 192.168.3.1: Redirect Host(New addr: 213.25.86.88) Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 0054 0105 0 40 01 8a7d 192.168.3.13 213.25.86.88 64 bytes from 213.25.86.88: icmp_seq=7 ttl=64 time=0.314 ms 64 bytes from 213.25.86.88: icmp_seq=8 ttl=64 time=0.288 ms I'm not local network, my IP is 192.168.3.13, 192.168.3.1 is my gateway. Strange.. never seen that before - what OS runs on the gateway? -- 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 pgp7caHHFA88x.pgp Description: PGP signature
status of ehci(4) in 5.3-stable?
Hiho! :-) What is the current status of ehci(4) in 5.3-stable, i.e. what are my chances that if I buy cheap 3.5 external usb 2.0 case it will just or probably work? Thanks in advance! Bye Marc ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Strange interrupts problem.
Hello. I'm running into a recurring problem. I tried to search the list for some info, but couldn't quite find anything related (there are some discussions on interrupt storms lately, but none seem to apply). I'm running FreeBSD-5.x on some old low end boxes, mostly for small tasks like small websites, email servers, and so on. Some time ago, on some of the boxes (with similar hardware - AMD Athlon 1.0GHz and 1.4GHz, MSI mainboards with VIA chipsets), I noticed a unusually high interrupt rate - top says around 10% CPU time at all times, even when the box is completely idle. The guilty process, according to top -S, is : 27 root -28 -147 0K12K RUN 17.9H 8.06% 8.06% swi5: clock sio Since those are production boxes, with custom kernels and all, I left them alone. Now, I have to mount another machine with old and used hardware, and I fall into the same problems, juste much worse. I tried two motherboards with completely different hardware (Celeron 600 with intel chip versus VIA C3 Samuel 2 with, well, VIA chip), and I have the same symptoms, just much worse : 27 root -28 -147 0K12K WAIT 5:12 23.93% 23.93% swi5: clock sio uname -a shows : FreeBSD cragganmore 5.3-STABLE FreeBSD 5.3-STABLE #0: Mon Nov 15 20:33:56 CET 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 (The box was upgraded from 5.3-BETAx. I made a GENERIC kernel to see if my custom config was not at fault, but no such luck. All was recompiled with no special tunables - the only line of interest in make.conf is 'CPUTYPE?=i586'.) After a few quick tests, it seems that the machine boots cleanly (no such load), but it begins to break under any kind of load : to stress it, I tried a make -j8 buildworld, and it took just a few minutes. Of course, once it begins, even if I leave the machine alone, the load stays the same. Some samples : 1) During the build : last pid: 12394; load averages: 7.65, 5.21, 2.54 up 0+00:07:42 10:28:45 105 processes: 10 running, 71 sleeping, 24 waiting CPU states: 49.2% user, 0.0% nice, 25.4% system, 25.4% interrupt, 0.0% idle Mem: 16M Active, 36M Inact, 35M Wired, 12K Cache, 59M Buf, 398M Free Swap: 1024M Total, 1024M Free PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND 27 root -28 -147 0K12K WAIT 0:32 24.02% 24.02% swi5: clock sio 9 root 171 52 0K12K RUN 0:09 0.68% 0.68% pagezero 2) Just after I hit ctrl-C : last pid: 12668; load averages: 3.64, 4.56, 2.46 up 0+00:08:37 10:29:40 73 processes: 2 running, 47 sleeping, 24 waiting CPU states: 0.0% user, 0.0% nice, 0.4% system, 24.5% interrupt, 75.1% idle Mem: 9684K Active, 36M Inact, 35M Wired, 12K Cache, 59M Buf, 405M Free Swap: 1024M Total, 1024M Free PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND 11 root 1320 0K12K RUN 1:37 65.28% 65.28% idle 27 root -28 -147 0K12K WAIT 0:45 22.71% 22.71% swi5: clock sio 3) Half an hour later : last pid: 12737; load averages: 0.00, 0.02, 0.40 up 0+00:33:38 10:54:41 73 processes: 2 running, 47 sleeping, 24 waiting CPU states: 0.8% user, 0.0% nice, 0.0% system, 25.6% interrupt, 73.6% idle Mem: 9768K Active, 37M Inact, 35M Wired, 12K Cache, 59M Buf, 403M Free Swap: 1024M Total, 1024M Free PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND 11 root 1070 0K12K RUN 20:29 75.54% 75.54% idle 27 root -28 -147 0K12K WAIT 6:47 23.05% 23.05% swi5: clock sio Strangely, it seems too that the load average falls much slower than expected (3.5 to 0.0 in more than one minute for the first number). On the other hand vmstat -i doesn't show anything anormal : interrupt total rate irq0: clk 349094 99 irq1: atkbd0 2 0 irq8: rtc 446819127 irq11: rl0 uhci0+ 10318 2 irq13: npx02 0 irq14: ata0 9015 2 irq15: ata1 48 0 Total 815298233 Of course, strangely enough, none of these boxes have any kind of device behind com ports (which are driven by sio, right ?). (BTW, on any kernel, I never had any interrupt storm messages - maybe 10-25% CPU is too low for that ? :) ) Well, this is it. I don't know what I can do to provide more information, but it's a test box, I can break it at will. You can find a dmesg output from a verbose boot at : http://www.lacave.net/~fred/dmesg.boot Fred -- Sysadmins can't be sued for malpractice, but surgeons don't have to deal with patients who install new versions of their own innards. ___ [EMAIL PROTECTED] mailing list
Re: status of ehci(4) in 5.3-stable?
At 05:55 AM 16/11/2004, Marc UBM Bocklet wrote: Hiho! :-) What is the current status of ehci(4) in 5.3-stable, i.e. what are my chances that if I buy cheap 3.5 external usb 2.0 case it will just or probably work? I think your chances would be better using a firewire adaptor and HD. On the Intel 865 boards I have tried with, USB 2.0 is pretty broken for me. ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: status of ehci(4) in 5.3-stable?
On Tue, 16 Nov 2004 07:58:53 -0500, Mike Tancsa [EMAIL PROTECTED] wrote: At 05:55 AM 16/11/2004, Marc UBM Bocklet wrote: Hiho! :-) What is the current status of ehci(4) in 5.3-stable, i.e. what are my chances that if I buy cheap 3.5 external usb 2.0 case it will just or probably work? I think your chances would be better using a firewire adaptor and HD. On the Intel 865 boards I have tried with, USB 2.0 is pretty broken for me. I think it depends on your chipset. I think my laptop (a D800) is an 855 chipset (ICH4, anyways), and the echi driver has been working well on it. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
vinum / 5.3
Hello all, I'm trying to create a stripe over 10 disks and am hitting a 32-bit wall in the volume size. The plex properly sees the full 3726 GB, but the volume shaves off the 32nd bit and only sees 1678 GB. Usual for vinum? Also, i kicked up gvinum to compare, but he doesn't seem to have a stripe command (despite saying he does in the help). nai-su% vinum vinum - l 0 drives: 0 volumes: 0 plexes: 0 subdisks: vinum - stripe -v /dev/aoed60 /dev/aoed61 /dev/aoed62 /dev/aoed63 /dev/aoed64 /dev/aoed65 /dev/aoed66 /dev/aoed67 /dev/aoed68 /dev/aoed69 drive vinumdrive0 device /dev/aoed60 drive vinumdrive1 device /dev/aoed61 drive vinumdrive2 device /dev/aoed62 drive vinumdrive3 device /dev/aoed63 drive vinumdrive4 device /dev/aoed64 drive vinumdrive5 device /dev/aoed65 drive vinumdrive6 device /dev/aoed66 drive vinumdrive7 device /dev/aoed67 drive vinumdrive8 device /dev/aoed68 drive vinumdrive9 device /dev/aoed69 volume vinum0 plex name vinum0.p0 org striped 279k sd name vinum0.p0.s0 drive vinumdrive0 size 781422503b sd name vinum0.p0.s1 drive vinumdrive1 size 781422503b sd name vinum0.p0.s2 drive vinumdrive2 size 781422503b sd name vinum0.p0.s3 drive vinumdrive3 size 781422503b sd name vinum0.p0.s4 drive vinumdrive4 size 781422503b sd name vinum0.p0.s5 drive vinumdrive5 size 781422503b sd name vinum0.p0.s6 drive vinumdrive6 size 781422503b sd name vinum0.p0.s7 drive vinumdrive7 size 781422503b sd name vinum0.p0.s8 drive vinumdrive8 size 781422503b sd name vinum0.p0.s9 drive vinumdrive9 size 781422503b V vinum0State: up Plexes: 1 Size: 1678 GB P vinum0.p0 S State: up Subdisks:10 Size: 3726 GB S vinum0.p0.s0 State: up D: vinumdrive0 Size: 372 GB S vinum0.p0.s1 State: up D: vinumdrive1 Size: 372 GB S vinum0.p0.s2 State: up D: vinumdrive2 Size: 372 GB S vinum0.p0.s3 State: up D: vinumdrive3 Size: 372 GB S vinum0.p0.s4 State: up D: vinumdrive4 Size: 372 GB S vinum0.p0.s5 State: up D: vinumdrive5 Size: 372 GB S vinum0.p0.s6 State: up D: vinumdrive6 Size: 372 GB S vinum0.p0.s7 State: up D: vinumdrive7 Size: 372 GB S vinum0.p0.s8 State: up D: vinumdrive8 Size: 372 GB S vinum0.p0.s9 State: up D: vinumdrive9 Size: 372 GB Cheers, Sam ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vinum / 5.3
Sam wrote: Also, i kicked up gvinum to compare, but he doesn't seem to have a stripe command (despite saying he does in the help). there is a geom stripe class called gstripe thats outside of the gvinum user interface. jim ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
IBM x225 Boot Failure with all recent 5.x releases
Has there been any change in the status of the x225 bug in 5.3? I've got a 5.3-release CD, and it still shows the same problem. Right now, my plans to deploy FreeBSD are stuck, until this bug gets resolved. To refresh memory (and I'm filling in a bug report as soon as I'm done here) - on any IBM x225 server, 5.3 (or 5.2.1) refuses to boot - it starts to load the bootloader, gets as far as 'Looking up /BOOT/LOADER - Found', and then I get continous loops of 'BTX Halted' plus register dumps. Never gets any further. Any clues? Lastest BIOS. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Unable to use ATAPI DVD drive in 5.3-STABLE-20041109
I ran into a similar problem when trying to install 5.3 RC1. I ended up installing 5.2.1 and then upgrading my source and rebuilding everything to get to 5.3-Stable. If I boot normally, I receive several errors on my DVD drive and I am unable to mount any kind of media (CD-R, CD, DVD-RW). However, if I boot verbosely, I get no errors and everything mounts fine. Any ideas on what might be going on? I am downloading 5.3-STABLE-20041116 to see if any changes may have fixed this problem. Thanks, -Matt Copyright (c) 1992-2004 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 5.3-STABLE-20041109-JPSNAP #6: Mon Nov 15 17:24:31 UTC 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MODULAR ACPI APIC Table: DELL GX260 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.26GHz (2258.31-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf27 Stepping = 7 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE # Booting normally acd0: FAILURE - MODE_SENSE_BIG timed out acd0: FAILURE - MODE_SENSE_BIG timed out acd0: FAILURE - MODE_SENSE_BIG timed out acd0: FAILURE - MODE_SENSE_BIG timed out acd0: FAILURE - MODE_SENSE_BIG timed out acd0: CDROM NEC DVD+RW ND-1100A/10GE at ata0-slave UDMA33 acd0: FAILURE - TEST_UNIT_READY timed out acd0: FAILURE - PREVENT_ALLOW timed out acd0: FAILURE - TEST_UNIT_READY timed out acd0: FAILURE - TEST_UNIT_READY timed out acd0: FAILURE - PREVENT_ALLOW timed out acd0: FAILURE - TEST_UNIT_READY timed out acd0: FAILURE - PREVENT_ALLOW timed out acd0: FAILURE - TEST_UNIT_READY timed out acd0: FAILURE - TEST_UNIT_READY timed out acd0: FAILURE - PREVENT_ALLOW timed out acd0: FAILURE - TEST_UNIT_READY timed out acd0: FAILURE - PREVENT_ALLOW timed out acd0: FAILURE - TEST_UNIT_READY timed out acd0: FAILURE - TEST_UNIT_READY timed out acd0: FAILURE - PREVENT_ALLOW timed out # Attempting to mount returns: 'cd9660: /dev/acd0: Input/output error' acd0: FAILURE - TEST_UNIT_READY timed out acd0: FAILURE - PREVENT_ALLOW timed out acd0: FAILURE - TEST_UNIT_READY timed out acd0: FAILURE - TEST_UNIT_READY timed out acd0: FAILURE - PREVENT_ALLOW timed out acd0: FAILURE - TEST_UNIT_READY timed out acd0: FAILURE - PREVENT_ALLOW timed out acd0: FAILURE - TEST_UNIT_READY timed out acd0: FAILURE - PREVENT_ALLOW timed out acd0: FAILURE - TEST_UNIT_READY timed out acd0: FAILURE - TEST_UNIT_READY timed out acd0: FAILURE - PREVENT_ALLOW timed out # Booting verbose acd0: stat=0x00 err=0x01 lsb=0x14 msb=0xeb acd0: pio=0x0c wdma=0x22 udma=0x42 cable=40pin acd0: setting PIO4 on Intel ICH4 chip acd0: setting UDMA33 on Intel ICH4 chip acd0: FAILURE - MODE_SENSE_BIG timed out acd0: NEC DVD+RW ND-1100A/10GE CDRW drive at ata0 as slave acd0: read 6890KB/s (6890KB/s) write 2755KB/s (2755KB/s), 2048KB buffer, UDMA33 acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, packet acd0: Writes: CDR, CDRW, test write, burnproof acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Questions about a 5.2.1 crash.....
Hi, I've been asked to help this former customer. This box is running 5.2.1 with as most exotic application jave/tomcat. And it crashes too often. The first essential question for the customer is: Is this hardware??? So I did the 'make -j 8 buildworld' test, which it survived with flying colors. What do I find in the logs: Nov 12 11:22:01 ktc syslogd: kernel boot file is /boot/kernel/kernel Nov 12 11:22:01 ktc kernel: panic: vm_fault: fault on nofault entry, addr: ee8fd000 Nov 12 11:22:01 ktc kernel: Nov 12 11:22:01 ktc kernel: syncing disks, buffers remaining... panic: bremfree: removing a buffer not on a queue Nov 12 11:22:01 ktc kernel: Uptime: 2d11h12m6s Nov 12 11:22:01 ktc kernel: Shutting down ACPI Nov 12 11:22:01 ktc kernel: Automatic reboot in 15 seconds - press a key on the console to abort .. Nov 12 11:22:02 ktc kernel: WARNING: / was not properly dismounted Nov 12 11:53:54 ktc syslogd: kernel boot file is /boot/kernel/kernel Nov 12 11:53:54 ktc kernel: panic: vm_fault: fault on nofault entry, addr: ee79f000 Nov 12 11:53:54 ktc kernel: Nov 12 11:53:54 ktc kernel: syncing disks, buffers remaining... panic: bremfree: removing a buffer not on a queue Nov 12 11:53:54 ktc kernel: Uptime: 31m36s Nov 12 11:53:54 ktc kernel: Shutting down ACPI Now the panic in the syncing part, I can imagine to just be there since syncing disk after a panic has not really worked all that well in 5.x Customer has disabled all warnings/witness/. And I can not make much of the comments on sys/vm/vm_fault.c:278, which is where the fault on nofault occurs... My feeling says: upgrade to 5.3, but this being a production server running soem applications I know very little off holds me back. So is this for sure a hardware problem, or just leftovers from 5.2.1 --WjW Original Message Date: Tue, 16 Nov 2004 20:57:26 +0100 (CET) From: Jan Willem [EMAIL PROTECTED] To: [EMAIL PROTECTED] 3.78.225.127:138 193.78.225.255:138 in via fxp0 TPTE at 0xbfc203e4 IS ZERO @ VA 080f9000 panic: bad pte syncing disks, buffers remaining... panic: bremfree: removing a buffer not on a queue Uptime: 6h59m22s Shutting down ACPI Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... Copyright (c) 1992-2004 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 5.2.1-RELEASE-p9 #4: Tue Aug 24 01:16:22 CEST 2004 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/KTC Preloaded elf kernel /boot/kernel/kernel at 0xc09ee000. Preloaded elf module /boot/kernel/aout.ko at 0xc09ee26c. Preloaded elf module /boot/kernel/acpi.ko at 0xc09ee318. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 3.20GHz (3192.22-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf29 Stepping = 9 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Hyperthreading: 2 logical CPUs real memory = 2129850368 (2031 MB) avail memory = 2063503360 (1967 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: INTEL D865GLC on motherboard pcibios: BIOS version 2.10 Using $PIR table, 12 entries at 0xc00f3d20 acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 acpi_cpu0: CPU on acpi0 acpi_cpu1: CPU on acpi0 device_probe_and_attach: acpi_cpu1 attach returned 6 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib0: slot 2 INTA is routed to irq 11 pcib0: slot 29 INTA is routed to irq 11 pcib0: slot 29 INTB is routed to irq 5 pcib0: slot 29 INTC is routed to irq 10 pcib0: slot 29 INTA is routed to irq 11 pcib0: slot 29 INTD is routed to irq 9 pcib0: slot 31 INTA is routed to irq 10 pcib0: slot 31 INTB is routed to irq 3 agp0: Intel 82865G (865G GMCH) SVGA controller port 0xec00-0xec07 mem 0xffa8-0xffaf,0xf000-0xf7ff irq 11 at device 2.0 on pci0 agp0: detected 16252k stolen memory agp0: aperture size is 128M uhci0: Intel 82801EB (ICH5) USB controller USB-A port 0xc800-0xc81f irq 11 at device 29.0 on pci0 usb0: Intel 82801EB (ICH5) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801EB (ICH5) USB controller USB-B port 0xcc00-0xcc1f irq 5 at device 29.1 on pci0 usb1: Intel 82801EB (ICH5) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: Intel 82801EB (ICH5) USB controller USB-C port 0xd000-0xd01f irq 10 at device 29.2 on pci0 usb2: Intel 82801EB (ICH5) USB controller USB-C on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00,
Re: VIA Rhine II network card
Dnia 16-11-2004, Wto o godzinie 20:08 +1030, Daniel O'Connor napisa(a): Hmm, I'm not sure what changed sorry - perhaps you could look for changes in the code by using cvsweb.freebsd.org. I made an experiment. I downloaded if_vr.c from cvs which was tagged as 5.2.1-RELEASE. Then I substituted if_vr.c in my /usr/src/sys/pci. Of course kernel did not compile, but I analyzed errors, and slightly modified if_vr.c according to latest version of that file. Then it compiled successfuly. But nothing changed... So I think there are 3 possibilities: 1) It's problem in my network. But it's very odd that it happens only when I run 5.3, not under Linux, and 5.1. 2) The problem is not in if_vr.c but in some other part of system, but which ? 3) Problem must be in part of code that I had to replace in if_vr.c, to have it correctly compiled. These were: a) functions: vr_start, vr_start_locked, vr_init, vr_init_locked In comments near these functions I read that they (vr_start*) are responsible for transmission. I've pasted them as they were in current vr_if.c because of changes in some structures used there... b) part of function vr_txeof Future examining of code is beyond my skills... Anyone knows what could be wrong ? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What OS are you? fun
Karel J. Bosschaart wrote: On Tue, Nov 16, 2004 at 07:39:13AM -0700, Dan MacMillan wrote: -Original Message- From: Andrew Sinclair Sent: November 16, 2004 15:32 To: [EMAIL PROTECTED] Subject: Re: What OS are you? fun By the way, speed of light in the other thread is way off. The accepted constant is bogus. The average speed is actually closer to 2.4 million kilometers per second. You'd better cite your source and / or reasoning, as ~3*10^8m/s =is= the accepted constant speed of light in vacuum. Yes indeed. Also, the word 'average' makes the statement pretty meaningless without specifying how the averaging is done (different materials I think?). Karel. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-chat To unsubscribe, send any mail to [EMAIL PROTECTED] OK, I'll bite on this. Check www.nist.gov. They occasionally update the fundamental physical constants, but we are talking about incredibly small amounts. Rob. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Named 9.3.0 weird error at bootup
On Mon, 15 Nov 2004, Samuel Trommel wrote: Recently I upgraded from 5.2.1-release to 5.3-release. When I try to start named I get a weird error: Nov 15 19:23:12 freebsd named[1152]: starting BIND 9.3.0 -4 -u bind -t /var/named/etc/namedb/ -c /etc/named.conf Nov 15 19:23:12 freebsd named[1152]: command channel listening on 0.0.0.0#953 Nov 15 19:23:12 freebsd named[1152]: /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/errno2result.c:109 : unexpected error: Nov 15 19:23:12 freebsd named[1152]: unable to convert errno to isc_result: 6: Device not configured After this my named is workin well, but wondering what this could be?? If this is reproduceable, it would be useful to try running named under ktrace and see which system call and arguments resulted in ENXIO. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Principal Research Scientist, McAfee Research ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
5.3 Loader Too Fragile
Can someone help me build a hardwired version of the loader that will let me boot my system? System is a 440LX dual CPU DEC Personal Workstation Station 333i+. There are no IDE devices. CD and HD are SCSI on 2940U2W controller. I saw in the code that this is bad news if guessing is required. Couldn't boot from floppy or CDROM, I couldn't even get them to take any of numerous variations of switching console from vidconsole to comconsole to capture error messages, so I built hard drive on another system. I get: BTX loader 1.00 BTX version is 1.01 Console: internal video/keyboard BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 509kB/130048kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED], Thu Nov 4 22:29:29 UTC 2004) Loading /boot/defaults/loader.conf /boot/kernel/kernel text=0x22c3e0 Console: internal video/keyboard BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 509kB/130048kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED], Thu Nov 4 22:29:29 UTC 2004) Can't work out which disk we are booting from. Guessed BIOS device 0x not found by probes defaulting to disk0: panic: free: guard1 fail @ 0x517c4 from [line folded for mail] /usr/src/sys/boot/i386/loader/../../common/module.c:957 -- Press a key on the console to reboot -- I had similar problems with 5.2.1 but was able to resolve them by upgrading to March 25th 5-Current, so I am reasonably sure the hardware is in good shape. Thanks, Roger L. Beeman ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Named 9.3.0 weird error at bootup
El Lunes, 15 de Noviembre de 2004 19:51, Samuel Trommel escribió: Hello, Recently I upgraded from 5.2.1-release to 5.3-release. When I try to start named I get a weird error: Nov 15 19:23:12 freebsd named[1152]: starting BIND 9.3.0 -4 -u bind -t /var/named/etc/namedb/ -c /etc/named.conf this doesn't seems good configured. How is your named setup? -- josemi ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Named 9.3.0 weird error at bootup
I already found out (Chroot problem /dev/random /dev/null) Thanks anyway for the help.. Samuel -Original Message- From: Jose M Rodriguez [mailto:[EMAIL PROTECTED] Sent: dinsdag 16 november 2004 23:43 To: [EMAIL PROTECTED] Cc: Samuel Trommel Subject: Re: Named 9.3.0 weird error at bootup El Lunes, 15 de Noviembre de 2004 19:51, Samuel Trommel escribió: Hello, Recently I upgraded from 5.2.1-release to 5.3-release. When I try to start named I get a weird error: Nov 15 19:23:12 freebsd named[1152]: starting BIND 9.3.0 -4 -u bind -t /var/named/etc/namedb/ -c /etc/named.conf this doesn't seems good configured. How is your named setup? -- josemi ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Named 9.3.0 weird error at bootup
Doug i appreciate your help, but it has nothing to with my config file... I migrated BIND 9.2.3 (Builded from ports) to the integrated BIND 9.3.0. The problem is that my chrootpoint is setup wrong. [23:57:[EMAIL PROTECTED]:/var/named/etc/namedb]# ls -alF total 18 drwxr-xr-x 9 root wheel 512 Nov 15 21:02 ./ drwxr-xr-x 3 root wheel 512 Nov 15 21:12 ../ drwxr-x--- 2 root wheel 512 Jul 13 13:53 bin/ drwxr-x--- 2 bind bind 512 Nov 15 19:22 dev/ drwxr-x--- 2 root wheel 512 Jul 14 18:31 etc/ drwxr-xr-x 2 bind bind 512 Nov 16 21:55 log/ drwxr-x--- 2 bind bind 512 Jul 14 10:46 master/ drwxrwx--- 2 bind bind 512 Sep 21 14:33 slave/ drwxrwx--- 4 bind bind 512 Jul 13 13:53 var/ I mounted /var/named/etc/namedb, instead /var/named/. I will do some maintance at the end of the week. I just need to create some devices with 'mknod' like null and random. Greet, Samuel Trommel -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Doug Barton Sent: dinsdag 16 november 2004 3:29 To: Samuel Trommel Cc: [EMAIL PROTECTED] Subject: Re: Named 9.3.0 weird error at bootup On Mon, 15 Nov 2004, Samuel Trommel wrote: Hello, Recently I upgraded from 5.2.1-release to 5.3-release. When I try to start named I get a weird error: Nov 15 19:23:12 freebsd named[1152]: starting BIND 9.3.0 -4 -u bind -t /var/named/etc/namedb/ -c /etc/named.conf I'm assuming from these command line params that you have customized your local configuration? If so, that's fine, just wanted to be sure. Nov 15 19:23:12 freebsd named[1152]: command channel listening on 0.0.0.0#953 Nov 15 19:23:12 freebsd named[1152]: /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/errno2result.c:109 : unexpected error: Nov 15 19:23:12 freebsd named[1152]: unable to convert errno to isc_result: 6: Device not configured This is indicative that you have an error in your config somewhere. I'd try named-checkconf, and make sure what you're specifying in the conf file matches the interfaces on your system. Doug -- This .signature sanitized for your protection ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Different snapshot sizes.
I'm somewhat confused. When I take snapshots, offtimes, they seem to be different sizes. I have a system that has two 120 Gig disks that are vinum (now gvinum) raid1'd. On that I have a root, swap, usr, var and 'u' partitions. All vinum created. As one (of several) backup policies, we take three filesystem snapshots per day, and progressively delete them such that the oldest snapshot we keep is about 30 days old. But the snapshots are often different sizes. This strikes me as odd, as I understood the format of a snapshot was to be the same as the format of the partition itself --- so they should all have the same size as the physical partition. An example: Making snapshot /usr/snap/20041116_18 done. total 193248 -r--r- 1 root operator 6442451256 Nov 16 17:32 20041116_094346 -r--r- 1 root operator 6442451256 Nov 16 18:00 20041116_120001 -r--r- 1 root operator 6442451264 Nov 16 18:00 20041116_18 ... the script above calls mksnap_ffs and then ls -l's the directory. Note that the last snapshot is 8 bytes larger. Very odd. It's not divisible by 512, but then neither are the other two. At any rate, this all wouldn't worry me if the server didn't crash with some regularity ... which it does. In fact, the /var partition gets the widest variety of snapshot sizes ... so I've disabled snapshots there alltogether. Dave. -- |David Gilbert, Independent Contractor. | Two things can only be | |Mail: [EMAIL PROTECTED]| equal if and only if they | |http://daveg.ca | are precisely opposite. | =GLO ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Different snapshot sizes.
David Gilbert wrote: and progressively delete them such that the oldest snapshot we keep is about 30 days old. Off topic comment: consider using ports/sysutils/fileprune for this task. Diomidis Spinellis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Different snapshot sizes.
On Tue, Nov 16, 2004 at 06:22:29PM -0500, David Gilbert wrote: But the snapshots are often different sizes. This strikes me as odd, as I understood the format of a snapshot was to be the same as the format of the partition itself --- so they should all have the same size as the physical partition. (To my surprise also) snapshot files seem to contain more data that one might expect. There's a comment in the code that says `Write out the list of allocated blocks to the end of the snapshot' (pointed out by folks on my local BSD mailing list. Full thread at [0]). Changes in the `list of allocated blocks' might account for the differences you're seeing. [0] http://lists.redbrick.dcu.ie/pipermail/bugi/2004-August/thread.html#579 ATB, james ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vinum / 5.3
On Tuesday, 16 November 2004 at 12:50:33 -0500, Sam wrote: Hello all, I'm trying to create a stripe over 10 disks and am hitting a 32-bit wall in the volume size. The plex properly sees the full 3726 GB, but the volume shaves off the 32nd bit and only sees 1678 GB. Usual for vinum? No. Could be some of the breakage introduced by changes to the kernel interfaces. Greg -- See complete headers for address and phone numbers. pgpRA5Bw1H1iq.pgp Description: PGP signature
VIA 83C572 USB controller not recognised as EHCI?
I have the following: uhci0: VIA 83C572 USB controller port 0xd400-0xd41f irq 12 at device 17.2 on p ci0 uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0xd400 uhci0: [GIANT-LOCKED] 'device ehci' in the kernel doesn't seem to recognise it. Is this a known issue ... or is it a magic byte issue? Dave. -- |David Gilbert, Independent Contractor. | Two things can only be | |Mail: [EMAIL PROTECTED]| equal if and only if they | |http://daveg.ca | are precisely opposite. | =GLO ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Questions about a 5.2.1 crash.....
I would risk the upgrade to 5.3. What can you lose? It is crashing frequently already... 5.2.1 was not a stable release officially. Just make sure that you follow the migration guide step by step (http://www.freebsd.org/releases/5.3R/migration-guide.html). Do not skip mergemaster. And you must recompile all installed binaries after the upgrade, including all installed ports. Zoltan Hi, I've been asked to help this former customer. This box is running 5.2.1 with as most exotic application jave/tomcat. And it crashes too often. The first essential question for the customer is: Is this hardware??? So I did the 'make -j 8 buildworld' test, which it survived with flying colors. What do I find in the logs: Nov 12 11:22:01 ktc syslogd: kernel boot file is /boot/kernel/kernel Nov 12 11:22:01 ktc kernel: panic: vm_fault: fault on nofault entry, addr: ee8fd000 Nov 12 11:22:01 ktc kernel: Nov 12 11:22:01 ktc kernel: syncing disks, buffers remaining... panic: bremfree: removing a buffer not on a queue Nov 12 11:22:01 ktc kernel: Uptime: 2d11h12m6s Nov 12 11:22:01 ktc kernel: Shutting down ACPI Nov 12 11:22:01 ktc kernel: Automatic reboot in 15 seconds - press a key on the console to abort .. Nov 12 11:22:02 ktc kernel: WARNING: / was not properly dismounted Nov 12 11:53:54 ktc syslogd: kernel boot file is /boot/kernel/kernel Nov 12 11:53:54 ktc kernel: panic: vm_fault: fault on nofault entry, addr: ee79f000 Nov 12 11:53:54 ktc kernel: Nov 12 11:53:54 ktc kernel: syncing disks, buffers remaining... panic: bremfree: removing a buffer not on a queue Nov 12 11:53:54 ktc kernel: Uptime: 31m36s Nov 12 11:53:54 ktc kernel: Shutting down ACPI Now the panic in the syncing part, I can imagine to just be there since syncing disk after a panic has not really worked all that well in 5.x Customer has disabled all warnings/witness/. And I can not make much of the comments on sys/vm/vm_fault.c:278, which is where the fault on nofault occurs... My feeling says: upgrade to 5.3, but this being a production server running soem applications I know very little off holds me back. So is this for sure a hardware problem, or just leftovers from 5.2.1 --WjW Original Message Date: Tue, 16 Nov 2004 20:57:26 +0100 (CET) From: Jan Willem wjw at ktc.netmaniacs.nl To: wjw at withagen.nl 3.78.225.127:138 193.78.225.255:138 in via fxp0 TPTE at 0xbfc203e4 IS ZERO @ VA 080f9000 panic: bad pte syncing disks, buffers remaining... panic: bremfree: removing a buffer not on a queue Uptime: 6h59m22s Shutting down ACPI Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... Copyright (c) 1992-2004 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 5.2.1-RELEASE-p9 #4: Tue Aug 24 01:16:22 CEST 2004 joao at ktc.netmaniacs.nl:/usr/src/sys/i386/compile/KTC Preloaded elf kernel /boot/kernel/kernel at 0xc09ee000. Preloaded elf module /boot/kernel/aout.ko at 0xc09ee26c. Preloaded elf module /boot/kernel/acpi.ko at 0xc09ee318. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 3.20GHz (3192.22-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf29 Stepping = 9 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Hyperthreading: 2 logical CPUs real memory = 2129850368 (2031 MB) avail memory = 2063503360 (1967 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: INTEL D865GLC on motherboard pcibios: BIOS version 2.10 Using $PIR table, 12 entries at 0xc00f3d20 acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 acpi_cpu0: CPU on acpi0 acpi_cpu1: CPU on acpi0 device_probe_and_attach: acpi_cpu1 attach returned 6 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib0: slot 2 INTA is routed to irq 11 pcib0: slot 29 INTA is routed to irq 11 pcib0: slot 29 INTB is routed to irq 5 pcib0: slot 29 INTC is routed to irq 10 pcib0: slot 29 INTA is routed to irq 11 pcib0: slot 29 INTD is routed to irq 9 pcib0: slot 31 INTA is routed to irq 10 pcib0: slot 31 INTB is routed to irq 3 agp0: Intel 82865G (865G GMCH) SVGA controller port 0xec00-0xec07 mem 0xffa8-0xffaf,0xf000-0xf7ff irq 11 at device 2.0 on pci0 agp0: detected 16252k stolen memory agp0: aperture size is 128M uhci0: Intel 82801EB (ICH5) USB controller USB-A port 0xc800-0xc81f irq 11 at device 29.0 on pci0 usb0: Intel 82801EB (ICH5) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801EB (ICH5) USB controller USB-B port 0xcc00-0xcc1f irq 5 at device 29.1 on pci0 usb1: Intel 82801EB
