Re: Adventurous fix for wheel mouse not working in FreeBSD 6.0
On Wed, 07 Dec 2005 09:03:19 +0200, [EMAIL PROTECTED] wrote: After installing FreeBSD 6.0, I was no longer able to scroll using the wheel on my Logitech Optical Mouse. I ran moused with the -fd flags and confirmed that the mouse daemon was catching the z-axis events. My xorg.conf looked OK to me: Section InputDevice Identifier Mouse0 Driver mouse Option Device /dev/sysmouse Option CorePointer Option AlwaysCore Option Protocol Auto Option Buttons 5 Option ZAxisMapping 4 5 Option Emulate3Buttons no EndSection I struggled for days and tried dozens of things. I came to suspect that the problem was related to changes in the way ZAxisMapping is handled by Xorg. Based on stuff in an Xorg mailing list, I suspect further changes, likely to be corrective, will be in future versions of the FreeBSD xorg-server port. However, for the adventurous and impatient, this is what I did to fix my problem: 1. Edit /usr/ports/x11-servers/xorg-server/work/xc/programs/Xserver/hw/xfree86/input/mouse/mouse.c and change from NULL to 4 5 in the following line: 530c530 s = xf86SetStrOption(pInfo-options, ZAxisMapping, 4 5); --- s = xf86SetStrOption(pInfo-options, ZAxisMapping, NULL); 2. portupgrade -Wwf xorg-server 3. Restart the X server with CTRL-ALT-Backspace. I don't really know why it works, so I recommend it only for daredevils, unless someone wiser can say it is sound. Cheers, John Funny, besides upgrading from 5.4 to 6.0, I changed from nVidia to Radeon and from a bloated old mouse to a Logitech Optical USB mouse. Anyway, the video cards were easy to change. But the mouse was tricky. The generic /dev/sysmouse didn't work for me so i had to specify /dev/ums0 and ZAxisMapping 4 5 and the rest was history. I don't use xdm/gdm/kdm though, i have startx with kde for now. And sometimes i have to kill the moused daeomn before starting X. -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ ++ Serverele DataNet scaneaza automat toate mesajele dumneavoastra impotriva virusilor pentru a mentine un mediu cat mai curat. Retineti ca exista intotdeauna un risc pe care vi-l asumati atunci cand deschideti un mesaj e-mail. This message has been scanned automatically against viruses on DataNet servers. Please note that you allways assume a risk when you open an e-mail message. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Adventurous fix for wheel mouse not working in FreeBSD 6.0
Quoth [EMAIL PROTECTED] on Wed, Dec 07, 2005 at 07:03:19 + After installing FreeBSD 6.0, I was no longer able to scroll using the wheel on my Logitech Optical Mouse. I ran moused with the -fd flags and confirmed that the mouse daemon was catching the z-axis events. My xorg.conf looked OK to me: The following works fine with a Logitech UltraX optical mouse. However, I have using it in PS2 mode and not usb. Maybe the problem is there? Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 option Buttons 6 EndSection I am running: ; uname -a FreeBSD hovel.york.ac.uk 6.0-RC1 FreeBSD 6.0-RC1 #0: Sun Oct 9 20:32:57 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 ; pkg_info | grep xorg xorg-clients-6.8.2_1 X client programs and related files from X.Org xorg-documents-6.8.2 Documentation of X11 protocol and libraries from X.Org xorg-fonts-100dpi-6.8.2 X.Org 100dpi bitmap fonts xorg-fonts-75dpi-6.8.2 X.Org 75dpi bitmap fonts xorg-fonts-encodings-6.8.2 X.Org font encoding files xorg-fonts-miscbitmaps-6.8.2 X.Org miscellaneous bitmap fonts xorg-fonts-truetype-6.8.2 X.Org TrueType fonts xorg-fonts-type1-6.8.2 X.Org Type1 fonts xorg-fontserver-6.8.2 X font server from X.Org xorg-libraries-6.8.2 X11 libraries and headers from X.Org xorg-manpages-6.8.2 X.Org library manual pages xorg-server-6.8.2_7 X.Org X server and related programs -- [EMAIL PROTECTED] -=*=- www.kierun.org PGP: 009D 7287 C4A7 FD4F 1680 06E4 F751 7006 9DE2 6318 pgpN6aA09vuj3.pgp Description: PGP signature
Re: Adventurous fix for wheel mouse not working in FreeBSD 6.0
On Wed, 07 Dec 2005 11:29:49 +0200, Yann Golanski [EMAIL PROTECTED] wrote: Quoth [EMAIL PROTECTED] on Wed, Dec 07, 2005 at 07:03:19 + After installing FreeBSD 6.0, I was no longer able to scroll using the wheel on my Logitech Optical Mouse. I ran moused with the -fd flags and confirmed that the mouse daemon was catching the z-axis events. My xorg.conf looked OK to me: The following works fine with a Logitech UltraX optical mouse. However, I have using it in PS2 mode and not usb. Maybe the problem is there? Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 option Buttons 6 EndSection I am running: ; uname -a FreeBSD hovel.york.ac.uk 6.0-RC1 FreeBSD 6.0-RC1 #0: Sun Oct 9 20:32:57 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 ; pkg_info | grep xorg xorg-clients-6.8.2_1 X client programs and related files from X.Org xorg-documents-6.8.2 Documentation of X11 protocol and libraries from X.Org xorg-fonts-100dpi-6.8.2 X.Org 100dpi bitmap fonts xorg-fonts-75dpi-6.8.2 X.Org 75dpi bitmap fonts xorg-fonts-encodings-6.8.2 X.Org font encoding files xorg-fonts-miscbitmaps-6.8.2 X.Org miscellaneous bitmap fonts xorg-fonts-truetype-6.8.2 X.Org TrueType fonts xorg-fonts-type1-6.8.2 X.Org Type1 fonts xorg-fontserver-6.8.2 X font server from X.Org xorg-libraries-6.8.2 X11 libraries and headers from X.Org xorg-manpages-6.8.2 X.Org library manual pages xorg-server-6.8.2_7 X.Org X server and related programs It's works for me: Logitech UltraX optical mouse, USB-mode dmesg: ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/20.00, addr 3, iclass 3/1 ums0: 4 buttons and Z dir. xorg.conf: ... Section InputDevice Identifier Mouse1 Driver mouse Option ProtocolAuto Option Device /dev/sysmouse Option Buttons 6 Option ZAxisMapping 4 5 EndSection uname -a: FreeBSD callisto 6.0-STABLE FreeBSD 6.0-STABLE #4: Sat Dec 3 12:07:10 EET 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/callisto amd64 pkg_info | grep xorg xorg-6.8.2 X.Org distribution metaport xorg-clients-6.8.2_1 X client programs and related files from X.Org xorg-documents-6.8.2 Documentation of X11 protocol and libraries from X.Org xorg-fonts-100dpi-6.8.2 X.Org 100dpi bitmap fonts xorg-fonts-75dpi-6.8.2 X.Org 75dpi bitmap fonts xorg-fonts-cyrillic-6.8.2 X.Org Cyrillic bitmap fonts xorg-fonts-encodings-6.8.2 X.Org font encoding files xorg-fonts-miscbitmaps-6.8.2 X.Org miscellaneous bitmap fonts xorg-fonts-truetype-6.8.2 X.Org TrueType fonts xorg-fonts-type1-6.8.2 X.Org Type1 fonts xorg-fontserver-6.8.2 X font server from X.Org xorg-libraries-6.8.2 X11 libraries and headers from X.Org xorg-manpages-6.8.2 X.Org library manual pages xorg-nestserver-6.8.2 Nesting X server from X.Org xorg-printserver-6.8.2_2 X Print server from X.Org xorg-server-6.8.2_7 X.Org X server and related programs xorg-vfbserver-6.8.2 X virtual framebuffer server from X.Org -- WBR Android Andrew [:] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
ipf - freebsd 5.x and 6.x hangs
Hello, Yesterday, when I looking for solution that can replace following command from linux: ip route add default via x.x.x.x src y.y.y.y So I tried with ipf and execute following rule, (yes this is silly): -- pass out quick on rl0 to rl0:y.y.y.y from x.x.x.x to any keep state -- On rl0 I have 2 IP addresses: x.x.x.x and alias for y.y.y.y All freebsd boxes hangs after 20 seconds whitout notice. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.0-stable panic in ohci_softintr when using ucom/uftdi
In message [EMAIL PROTECTED], Paul Koch writes: As soon at the modem rings, the machine panics. I don't think the modem even gets time to pick up the line. This doesn't happen on a 5.4-stable box with 6 modems connected, but 5.4-stable appears to have other hanging issues, thus why I am trying out 6.0-stable. Recent changes to ohci.c (1.154.2.1) in this area (2 days ago) ?? Should I raise a PR ? I'll see if I can reproduce this later - the only thing I can think of now that might be responsible is a USB transfer reuse issue that the old patch here might help with: http://people.freebsd.org/~iedowse/releng_5_xfer_reuse.diff Could you see if that makes any difference? It should apply to 6-stable even though the name says releng_5. Ian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.0-stable panic in ohci_softintr when using ucom/uftdi
On Wed, 7 Dec 2005 09:02 pm, Ian Dowse wrote: In message [EMAIL PROTECTED], Paul Koch writes: As soon at the modem rings, the machine panics. I don't think the modem even gets time to pick up the line. This doesn't happen on a 5.4-stable box with 6 modems connected, but 5.4-stable appears to have other hanging issues, thus why I am trying out 6.0-stable. Recent changes to ohci.c (1.154.2.1) in this area (2 days ago) ?? Should I raise a PR ? I'll see if I can reproduce this later - the only thing I can think of now that might be responsible is a USB transfer reuse issue that the old patch here might help with: http://people.freebsd.org/~iedowse/releng_5_xfer_reuse.diff Could you see if that makes any difference? It should apply to 6-stable even though the name says releng_5. Ian I'll try it tomorrow morning when I get back to the office. I compiled in USB_DEBUG and set all the usb debug sysctl's to 100 and made it crash again. It is reproduceable 100% of the time. Are you interested in seeing the verbose debug log messages at all ? Paul. -- Paul Koch CTO Statseeker ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cpu-timer rate
I certainly do not have a full understanding of the interactions between the various FreeBSD software timers and i386 hardware clocks, but I do know this is not the first time we've seen a problem with the APIC/ACPI timers/clocks. See here: http://www.freebsd.org/cgi/getmsg.cgi?fetch=643512+646009+/usr/local/www/db/text/2005/freebsd-stable/20051120.freebsd-stable And workaround, here: http://www.freebsd.org/cgi/getmsg.cgi?fetch=687445+690193+/usr/local/www/db/text/2005/freebsd-stable/20051120.freebsd-stable I haven't made much of a fuss, since my vmware FreeBSD works just fine so long as I disable the APIC (not ACPI) device. I was guessing there was some assumption about relative rates gumming things up for vmware (the hardware APIC (not ACPI) timer runs at memory bus speed, not cpu speed, and thus will get goofed if you assume straight/DDR/quad/whatever memory-- from what I gather, you need to check it against a known-hz device, e.g. the PIT/i8253 clock). My complacency, however, is probably misguided, as the release notes for 6.0 clearly sate that FreeBSD always uses the local APIC timer even on uni-processor systems now, and will presumably continue to do so for the forseeable future. There is a nice layman's overview of various i386 hardware clock devices here: http://www.vmware.com/pdf/vmware_timekeeping.pdf Again, I'm no expert, but clock problems do keep cropping up here on the -STABLE list, and the explanations for them to date have not been consistent. This leads me to believe that the FreeBSD kernel clock/timer code is not well-understood by any one developer who monitors this list; I'm sure I'm not the only end-user who would appreciate it if the core team would look into this and post some information that would explain the various clock/timer problems that odd corners of the user community have been reporting. - Original Message - From: Peter Jeremy [EMAIL PROTECTED] To: Kevin Oberman [EMAIL PROTECTED] Cc: kama [EMAIL PROTECTED]; freebsd-stable@freebsd.org; Matthew D. Fuller [EMAIL PROTECTED] Sent: Tuesday, December 06, 2005 11:17 PM Subject: Re: cpu-timer rate On Mon, 2005-Dec-05 10:15:52 -0800, Kevin Oberman wrote: On Mon, Dec 05, 2005 at 09:42:08AM +0100 I heard the voice of kama, and lo! it spake thus: I appreciate that you took time to answer about the different clocks. But that does not answer why vmstat -i shows a rate of 2000 when I have set the hz to 1000. Because the rate is always twice hz. While I will concede that I have no explanation, but on all of my systems rate = HZ +/-1. I have never seen a case where rate/2 = HZ. Basically, it depends on what clock(s) your kernel is using. Traditionally, FreeBSD/i386 uses the one of the i8254 counters to generate hz (on irq0) and the RTC to generate profhz/stathz (on irq8). In this case, the rate on those interrupts should match the values reported by kern.clockrate. On SMP machines, this approach is fairly expensive because the interrupts need to be forwarded to all CPUs using IPIs. In early February, jhb implemented an alternative approach using the local APIC clock (sys/i386/i386/local_apic.c v1.13 and other files). Since every CPU has a LAPIC, every CPU gets its own clock interrupts without needing IPIs. The downside is that there's only a single LAPIC so a single hardware clock interrupt needs to generate separate (and independent) hz/tick and stathz/profhz clocks. Since the clocks need to be independent (to make process statistics meaningful), this implies that the hardware (LAPIC) clock (cpu0) needs to be faster than hz. The original commit ran LAPIC at hz*3 but this was later changed to hz*2 to reduce overheads. -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Will Robinson and all another
Hi PPL! I have a computer with parent payment ASUS P4C800E-DELUXE. OS FreeBSD 6.0-stable (CVS from 21.nov.2005) is established. It is established five hard disks: - One system on ICH5 ata100 Maxtor 6Y200P0 - And four on Promise RAID 0+1 WDC WD3200J (D/B) All fine worked (except for em0, but also he has normally earned after updating) while I have not wanted to establish two more hard disks (Maxtor 6Y080M0) on Intel in Stripe RAID. Hard disks have been put - the system of them has found out (the truth and known all bug failed to enable memory mapping), and I with them was more did than nothing (did not format, did not break - there was no time). In three days of job the system has given out me the following: ad4: req=0xc630f190 SETFEATURES SET TRANSFER MODE semaphore timeout!! DANGER Will Robinson!! This warning has been given many times. And ad4 it is established on Promise! After reboot smartd has given out the warning smartd [767]: Device:/dev/ad10, 1 Currently unreadable (pending) sectors smartd [767]: Device:/dev/ad10, 26 Offline uncorrectable sectors (ad10 the first disk in Stripe RAID on Intel MATRIX) After that has made CVSUP and has put for the night rebuild the world. In the morning has seen - to warrning ad4: req=0xc90efd48 SETFEATURES SET TRANSFER MODE semaphore timeout!! DANGER Will Robinson!! It was added: kern.maxfiles limit exceeded by uid 100, please see tuning (7). Has install the world, has spat and has disconnected these both HDDs from the controller (itself Matrix has remained switched on) Has passed three more days and yesterday has received the new letter:) kernel: DOH! ata_alloc_request failed! kernel: FAILURE - out of memory in ata_raid_init_request last message repeated 4 times kernel: g_vfs_done ():ar0s1d [WRITE (offset=554081878016, length=49152)] error = 5 kernel: g_vfs_done ():ar0s1d [WRITE (offset=554081730560, length=12288)] error = 5 kernel: g_vfs_done ():ar0s1d [WRITE (offset=554082091008, length=65536)] error = 5 kernel: g_vfs_done ():ar0s1d [WRITE (offset=554081927168, length=16384)] error = 5 kernel: g_vfs_done ():ar0s1d [WRITE (offset=554081943552, length=16384)] error = 5 syslogd: kernel boot file is/boot/kernel/kernel kernel: panic: kmem_malloc (4096): kmem_map too small: 172470272 total allocated Then has switched off also the controller, has again updated system and I wait some more days:) Immemorial Russian question - what to make?, I think here it is inappropriate, and so all is clear Remarks on system: it is switched on HHT (ACPI, SMP) and DEVICE POLLING, the network interface em0 and Intel Matrix, both stand on one irq. References Visible links Hidden links: 1. mailto:[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: Fatal trap 12: page fault while in kernel mode
On Wednesday 07 December 2005 02:47 am, Yuri Khotyaintsev wrote: On Friday 02 December 2005 14.54, John Baldwin wrote: On Friday 02 December 2005 05:00 am, Yuri Khotyaintsev wrote: I have the following panic occurring several times a week. The machine is an NFS server, and it usually panics early in the morning, when first people try to access it. After reboot it may work OK for 1-2 days, and then panics again. I have tried changing memory and replacing disk which was exported via NFS, but nothing helped :( Any suggestion on how to fix this panic will be very much appreciated ! This panic (in propagate_priority) is usually caused when a thread goes to sleep while holding a mutex (which is forbidden). If you enable INVARIANTS and/or WITNESS you should get a better panic, and with WITNESS you will even be warned when a thread goes to sleep while holding a mutex. However, these options do introduce considerable execution overhead, and sometimes that overhead changes the timing enough to hide the race. :( Here are the two panics which I got with INVARIANTS and WITNESS enabled. Unread portion of the kernel message buffer: Memory modified after free 0xc4759e00(508) val=0 @ 0xc4759e00 panic: Most recently used by UFS dirhash Well, this isn't the panic I was expecting, but it points to something trashing free'd memory via a stale pointer or some such. You might be able to use MEMGUARD to track this down. -- John Baldwin [EMAIL PROTECTED] http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve = http://www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Can't boot RELEASE-6.0 on ASUS P4S800D-X
Hi, I'm using the RELEASE-5.4 without any problem, but the RELEASE-6.0 CD boot stops just before the ad4: message. This is the output of dmesg on 5.4: begin Copyright (c) 1992-2005 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.4-RELEASE-p8 #0: Fri Dec 2 16:30:38 BRST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ME Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2800.81-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf34 Stepping = 4 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 = 1073414144 (1023 MB) avail memory = 1045049344 (996 MB) ACPI APIC Table: A M I OEMAPIC ioapic0: Changing APIC ID to 2 ioapic0 Version 1.1 irqs 0-23 on motherboard npx0: math processor on motherboard npx0: INT 16 interface acpi0: A M I OEMXSDT on motherboard acpi0: Power Button (fixed) Timecounter ACPI-safe frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 cpu0: ACPI CPU on acpi0 acpi_throttle0: ACPI CPU Throttling on cpu0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: SiS 655 host to AGP bridge mem 0xf800-0xfbff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 2.0 on pci0 isa0: ISA bus on isab0 atapci0: SiS 964 UDMA133 controller port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 2.5 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pcm0: SiS 7012 port 0xec00-0xec7f,0xe800-0xe8ff irq 18 at device 2.7 on pci0 pcm0: Analog Devices AD1888 AC97 Codec ohci0: SiS 5571 USB controller mem 0xfebfc000-0xfebfcfff irq 20 at device 3.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: SiS 5571 USB controller on ohci0 usb0: USB revision 1.0 uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: SiS 5571 USB controller mem 0xfebfd000-0xfebfdfff irq 21 at device 3.1 on pci0 usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: SiS 5571 USB controller on ohci1 usb1: USB revision 1.0 uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered ohci2: SiS 5571 USB controller mem 0xfebfe000-0xfebfefff irq 22 at device 3.2 on pci0 usb2: OHCI version 1.0, legacy support usb2: SMM does not respond, resetting usb2: SiS 5571 USB controller on ohci2 usb2: USB revision 1.0 uhub2: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pci0: serial bus, USB at device 3.3 (no driver attached) sis0: SiS 900 10/100BaseTX port 0xe400-0xe4ff mem 0xfebfb000-0xfebfbfff irq 19 at device 4.0 on pci0 miibus0: MII bus on sis0 rlphy0: RTL8201L 10/100 media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sis0: Ethernet address: 00:11:d8:d5:86:54 atapci1: SiS 964 SATA150 controller port 0xef90-0xef9f,0xefe0-0xefe3,0xefa8-0xefaf,0xefe4-0xefe7,0xeff0-0xeff7 irq 17 at device 5.0 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 acpi_button0: Power Button on acpi0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 fdc0: floppy drive controller (FDE) port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fd0: 1440-KB 3.5 drive on fdc0 drive 0 ppc0: Standard parallel printer port port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: Parallel port bus on ppc0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A orm0: ISA Option ROM at iomem 0xcf000-0xd6fff on isa0 pmtimer0 on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 ums0: Microsoft Basic Optical Mouse, rev 1.10/0.00, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. Timecounter TSC frequency 2800810684 Hz quality 800 Timecounters tick every 10.000 msec acd0: CDRW HL-DT-ST GCE-8520B/1.02 at ata1-master PIO4 ad4: 190782MB ST3200822AS/3.01 [387621/16/63] at ata2-master SATA150 Mounting root from ufs:/dev/ad4s2a end When it boots with 6.0 CD in verbose mode the following messages appears just before lock-up: begin ata2: reiniting channel ..
permanent per month panic on 5.4-p4
Approximately once per month or two this server panics.
We use it for InterSystems Cache` (under linux emulation) and as samba-server
(not heavy-loaded).
# dmesg -a
can be found at http://www.dp.uz.gov.ua/dmesg.isc-cache
kernel config - http://www.dp.uz.gov.ua/kernel.isc-cache
# uname -a
FreeBSD isc-cache.dp.uz.gov.ua 5.4-RELEASE-p4 FreeBSD 5.4-RELEASE-p4 #1: Fri
Nov 4 11:37:34 EET 2005 [EMAIL
PROTECTED]:/usr/obj/usr/src/sys/ISC-CACHE_KERNEL i386
# kgdb kernel.debug_5.4-p4_2005-11-04 vmcore.6
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:
Undefined symbol ps_pglobal_lookup]
#0 doadump () at pcpu.h:159
159 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) where
#0 doadump () at pcpu.h:159
#1 0xc050a102 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:410
#2 0xc050a3c8 in panic (fmt=0xc0656ebc %s) at
/usr/src/sys/kern/kern_shutdown.c:566
#3 0xc063ca14 in trap_fatal (frame=0xcbe69ae4, eva=0) at
/usr/src/sys/i386/i386/trap.c:817
#4 0xc063c141 in trap (frame=
{tf_fs = 24, tf_es = -1061093360, tf_ds = -1050869744, tf_edi =
-1052353024, tf_esi = -1053737324, tf_ebp = -874079452, tf_isp = -874079472,
tf_ebx = 0, tf_edx = -1057524608, tf_ecx = -1053737324, tf_eax = 0, tf_trapno =
12, tf_err = 0, tf_eip = -1068333178, tf_cs = 8, tf_eflags = 65606, tf_esp =
-874079428, tf_ss = -1068492228}) at /usr/src/sys/i386/i386/trap.c:255
#5 0xc062f0fa in calltrap () at /usr/src/sys/i386/i386/exception.s:140
#6 0x0018 in ?? ()
#7 0xc0c10010 in ?? ()
#8 0xc15d0010 in ?? ()
#9 0xc1465e00 in ?? ()
#10 0xc1313e94 in ?? ()
#11 0xcbe69b24 in ?? ()
#12 0xcbe69b10 in ?? ()
#13 0x in ?? ()
#14 0xc0f77480 in ?? ()
#15 0xc1313e94 in ?? ()
#16 0x in ?? ()
#17 0x000c in ?? ()
#18 0x in ?? ()
#19 0xc0528786 in turnstile_head (ts=0x0) at
/usr/src/sys/kern/subr_turnstile.c:763
#20 0xc0501a3c in _mtx_unlock_sleep (m=0xc1313e94, opts=0,
file=0xc1db7ec2 /usr/src/sys/modules/smbfs/../../netsmb/smb_iod.c,
line=97)
at /usr/src/sys/kern/kern_mutex.c:659
#21 0xc050188a in _mtx_unlock_flags (m=0x0, opts=0,
file=0xc1db7ec2 /usr/src/sys/modules/smbfs/../../netsmb/smb_iod.c,
line=97)
at /usr/src/sys/kern/kern_mutex.c:364
#22 0xc1dabe27 in ?? ()
#23 0xc1313e94 in ?? ()
#24 0x in ?? ()
#25 0xc1db7ec2 in ?? ()
#26 0x0061 in ?? ()
#27 0xc1465e00 in ?? ()
#28 0xc1a14800 in ?? ()
#29 0xc1313e00 in ?? ()
---Type return to continue, or q return to quit---
#30 0xcbe69b8c in ?? ()
#31 0xc1dabef6 in ?? ()
#32 0xc1465e00 in ?? ()
#33 0xc1465e00 in ?? ()
#34 0xc1465e00 in ?? ()
#35 0xcbe69ba4 in ?? ()
#36 0xc1dac766 in ?? ()
#37 0xc1465e00 in ?? ()
#38 0xc19abe00 in ?? ()
#39 0xc19abe88 in ?? ()
#40 0xc1313e00 in ?? ()
#41 0xcbe69bbc in ?? ()
#42 0xc1daa261 in ?? ()
#43 0xc1313e00 in ?? ()
#44 0xc1313e00 in ?? ()
#45 0x in ?? ()
#46 0xc1a14800 in ?? ()
#47 0xcbe69bd4 in ?? ()
#48 0xc1daa202 in ?? ()
#49 0xc1313e00 in ?? ()
#50 0xc1313e18 in ?? ()
#51 0xc19ff9e0 in ?? ()
#52 0xc1a14800 in ?? ()
#53 0xcbe69ce4 in ?? ()
#54 0xc1da8f12 in ?? ()
#55 0xc1313e00 in ?? ()
#56 0xc1313e00 in ?? ()
#57 0xc1313e18 in ?? ()
#58 0xc1a14800 in ?? ()
#59 0xc1db7cd9 in ?? ()
#60 0x in ?? ()
#61 0x in ?? ()
#62 0x0001 in ?? ()
#63 0x in ?? ()
#64 0x in ?? ()
#65 0xc1313e00 in ?? ()
#66 0xc1da79c3 in ?? ()
#67 0xc15da288 in ?? ()
---Type return to continue, or q return to quit---
#68 0x in ?? ()
#69 0xcbe69c30 in ?? ()
#70 0x in ?? ()
#71 0xcbe69c2c in ?? ()
#72 0xc0519e6a in sched_choose () at /usr/src/sys/kern/sched_4bsd.c:1137
Previous frame inner to this frame (corrupt stack?)
What additional information can I provide?
Thanks!
--
Best regards,
Palij Oleg, ISC (Pridn railway)
xmpp://[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: Help - vr0: rx packet loss on new 6.0 kernel
On Tuesday 06 December 2005 22:57, the author [EMAIL PROTECTED] contributed to the dialogue on- Help - vr0: rx packet loss on new 6.0 kernel: vr0: rx packet loss even on single user mode On Wednesday 07 December 2005 04:36, the author Randy Rowe contributed to the dialogue on- Re: Help - vr0: rx packet loss on new 6.0 kernel: [EMAIL PROTECTED] wrote: From: [EMAIL PROTECTED] Date: 2005/12/06 Tue PM 11:23:18 PST To: [EMAIL PROTECTED], freebsd-stable@freebsd.org Subject: Re: Re: Help - vr0: rx packet loss on new 6.0 kernel OK booted on the old kernel back to 5.4 Does anyone have any idea what may have caused the problem? Thanks From: [EMAIL PROTECTED] Date: 2005/12/06 Tue PM 11:13:31 PST To: [EMAIL PROTECTED], freebsd-stable@freebsd.org Subject: Re: Help - vr0: rx packet loss on new 6.0 kernel From: [EMAIL PROTECTED] Date: 2005/12/06 Tue PM 10:57:44 PST To: freebsd-stable@freebsd.org Subject: Help - vr0: rx packet loss on new 6.0 kernel Just upgraded from 5.4 6.0 and am getting vr0: rx packet loss even on single user mode I'm no expert but it sounds to me like your world and your kernel are not in sync. I'm not sure if a 5.4 kernel can run properly with a 6.0 world and so it could be that you still have a 5.4 world. Just my first guess. You might want to follow up with the steps that you used to move from 5.4 to 6.0. Thanks You may be right -- Well I booted up from kernel.old -- moved the new kernel to kernel.faulty chuckles and kernel.old to kernel, rebooted and came right up on 5.4. Here are the entries re vro in dmesg.boot on the 5.4 kernel: vr0: VIA VT6102 Rhine II 10/100BaseTX port 0xc400-0xc4ff mem 0xde016000-0xde0160ff irq 23 at device 18.0 on pci0 miibus0: MII bus on vr0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr0: Ethernet address: 00:50:8d:6e:9d:31 The repeated messages vr0: packet loss just took over the system. Here are the boot sequences Dec 6 22:38:24 dns1 kernel: FreeBSD 6.0-STABLE #0: Tue Dec 6 22:00:00 PST 2005 Dec 6 22:38:24 dns1 kernel: [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Dec 6 22:38:24 dns1 kernel: Timecounter i8254 frequency 1193182 Hz quality 0 Dec 6 22:38:24 dns1 kernel: CPU: AMD Athlon(tm) XP (1593.54-MHz 686-class CPU) Dec 6 22:38:24 dns1 kernel: Origin = AuthenticAMD Id = 0x6a0 Stepping = 0 Dec 6 22:38:24 dns1 kernel: Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE Dec 6 22:38:24 dns1 kernel: AMD Features=0xc0480800SYSCALL,MP,MMX+,3DNow+,3DNow Dec 6 22:38:24 dns1 kernel: real memory = 2080309248 (1983 MB) Dec 6 22:38:24 dns1 kernel: avail memory = 2030624768 (1936 MB) Dec 6 22:38:24 dns1 kernel: ACPI APIC Table: KM400A AWRDACPI Dec 6 22:38:24 dns1 kernel: ioapic0 Version 0.3 irqs 0-23 on motherboard Dec 6 22:38:24 dns1 kernel: npx0: [FAST] Dec 6 22:38:24 dns1 kernel: npx0: math processor on motherboard Dec 6 22:38:24 dns1 kernel: npx0: INT 16 interface Dec 6 22:38:24 dns1 kernel: acpi0: KM400A AWRDACPI on motherboard Dec 6 22:38:24 dns1 kernel: acpi0: Power Button (fixed) Dec 6 22:38:24 dns1 kernel: Timecounter ACPI-fast frequency 3579545 Hz quality 1000 Dec 6 22:38:24 dns1 kernel: acpi_timer0: 24-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 Dec 6 22:38:24 dns1 kernel: cpu0: ACPI CPU on acpi0 Dec 6 22:38:24 dns1 kernel: acpi_button0: Power Button on acpi0 Dec 6 22:38:24 dns1 kernel: pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 Dec 6 22:38:24 dns1 kernel: pci0: ACPI PCI bus on pcib0 Dec 6 22:38:24 dns1 kernel: agp0: VIA 8235/8237 (Apollo KM400/KM400A) host to PCI bridge mem 0xd000-0xd7ff at device 0.0 on pci0 Dec 6 22:38:24 dns1 kernel: pcib1: PCI-PCI bridge at device 1.0 on pci0 Dec 6 22:38:24 dns1 kernel: pci1: PCI bus on pcib1 Dec 6 22:38:24 dns1 kernel: pci1: display, VGA at device 0.0 (no driver attached) Dec 6 22:38:24 dns1 kernel: pci0: network, ethernet at device 9.0 (no driver attached) Dec 6 22:38:24 dns1 kernel: fwohci0: Texas Instruments TSB43AB23 mem 0xde014000-0xde0147ff,0xde01-0xde013fff irq 18 at device 10.0 on pci0 Dec 6 22:38:24 dns1 kernel: fwohci0: OHCI version 1.10 (ROM=1) Dec 6 22:38:24 dns1 kernel: fwohci0: No. of Isochronous channels is 4. Dec 6 22:38:24 dns1 kernel: fwohci0: EUI64 00:d0:03:56:00:b2:b7:e6 Dec 6 22:38:24 dns1 kernel: fwohci0: Phy 1394a available S400, 3 ports. Dec 6 22:38:24 dns1 kernel: fwohci0: Link S400, max_rec 2048 bytes. Dec 6 22:38:24 dns1 kernel: firewire0: IEEE1394(FireWire) bus on fwohci0 Dec 6 22:38:24 dns1 kernel: fwe0: Ethernet over FireWire on firewire0 Dec 6 22:38:24 dns1 kernel: if_fwe0: Fake Ethernet address: 02:d0:03:b2:b7:e6 Dec 6 22:38:24 dns1 kernel: fwe0: Ethernet address: 02:d0:03:b2:b7:e6 Dec 6 22:38:24 dns1 kernel: fwe0: if_start running deferred for Giant Dec 6 22:38:24 dns1 kernel: sbp0: SBP-2/SCSI over FireWire on firewire0 Dec 6 22:38:24 dns1 kernel: fwohci0:
Problem with rlwrap and pty
Hi all, I've found in the archive that there is some problem with rlwrap, and I've found the same thing... it has trouble opening a pty. This seems to have been around for a while under 5.x, while 4.x doesn't have the problem. Is there a workaround? jm -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't boot RELEASE-6.0 on ASUS P4S800D-X
Einstein Oliveira [EMAIL PROTECTED] writes: Hi, I'm using the RELEASE-5.4 without any problem, but the RELEASE-6.0 CD boot stops just before the ad4: message. This is the output of dmesg on 5.4: begin Copyright (c) 1992-2005 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.4-RELEASE-p8 #0: Fri Dec 2 16:30:38 BRST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ME Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2800.81-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf34 Stepping = 4 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 = 1073414144 (1023 MB) avail memory = 1045049344 (996 MB) ACPI APIC Table: A M I OEMAPIC ioapic0: Changing APIC ID to 2 ioapic0 Version 1.1 irqs 0-23 on motherboard npx0: math processor on motherboard npx0: INT 16 interface acpi0: A M I OEMXSDT on motherboard acpi0: Power Button (fixed) Timecounter ACPI-safe frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 cpu0: ACPI CPU on acpi0 acpi_throttle0: ACPI CPU Throttling on cpu0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: SiS 655 host to AGP bridge mem 0xf800-0xfbff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 2.0 on pci0 isa0: ISA bus on isab0 atapci0: SiS 964 UDMA133 controller port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 2.5 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pcm0: SiS 7012 port 0xec00-0xec7f,0xe800-0xe8ff irq 18 at device 2.7 on pci0 pcm0: Analog Devices AD1888 AC97 Codec ohci0: SiS 5571 USB controller mem 0xfebfc000-0xfebfcfff irq 20 at device 3.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: SiS 5571 USB controller on ohci0 usb0: USB revision 1.0 uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: SiS 5571 USB controller mem 0xfebfd000-0xfebfdfff irq 21 at device 3.1 on pci0 usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: SiS 5571 USB controller on ohci1 usb1: USB revision 1.0 uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered ohci2: SiS 5571 USB controller mem 0xfebfe000-0xfebfefff irq 22 at device 3.2 on pci0 usb2: OHCI version 1.0, legacy support usb2: SMM does not respond, resetting usb2: SiS 5571 USB controller on ohci2 usb2: USB revision 1.0 uhub2: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pci0: serial bus, USB at device 3.3 (no driver attached) sis0: SiS 900 10/100BaseTX port 0xe400-0xe4ff mem 0xfebfb000-0xfebfbfff irq 19 at device 4.0 on pci0 miibus0: MII bus on sis0 rlphy0: RTL8201L 10/100 media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sis0: Ethernet address: 00:11:d8:d5:86:54 atapci1: SiS 964 SATA150 controller port 0xef90-0xef9f,0xefe0-0xefe3,0xefa8-0xefaf,0xefe4-0xefe7,0xeff0-0xeff7 irq 17 at device 5.0 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 acpi_button0: Power Button on acpi0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 fdc0: floppy drive controller (FDE) port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fd0: 1440-KB 3.5 drive on fdc0 drive 0 ppc0: Standard parallel printer port port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: Parallel port bus on ppc0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A orm0: ISA Option ROM at iomem 0xcf000-0xd6fff on isa0 pmtimer0 on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 ums0: Microsoft Basic Optical Mouse, rev 1.10/0.00, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. Timecounter TSC frequency 2800810684 Hz quality 800 Timecounters tick every 10.000 msec acd0: CDRW HL-DT-ST GCE-8520B/1.02 at ata1-master PIO4 ad4: 190782MB ST3200822AS/3.01 [387621/16/63] at ata2-master SATA150 Mounting root from ufs:/dev/ad4s2a end
Re: Can't boot RELEASE-6.0 on ASUS P4S800D-X
Lowell Gilbert wrote: Einstein Oliveira [EMAIL PROTECTED] writes: Hi, I'm using the RELEASE-5.4 without any problem, but the RELEASE-6.0 CD boot stops just before the ad4: message. This is the output of dmesg on 5.4: begin Copyright (c) 1992-2005 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.4-RELEASE-p8 #0: Fri Dec 2 16:30:38 BRST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ME Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2800.81-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf34 Stepping = 4 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 = 1073414144 (1023 MB) avail memory = 1045049344 (996 MB) ACPI APIC Table: A M I OEMAPIC ioapic0: Changing APIC ID to 2 ioapic0 Version 1.1 irqs 0-23 on motherboard npx0: math processor on motherboard npx0: INT 16 interface acpi0: A M I OEMXSDT on motherboard acpi0: Power Button (fixed) Timecounter ACPI-safe frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 cpu0: ACPI CPU on acpi0 acpi_throttle0: ACPI CPU Throttling on cpu0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: SiS 655 host to AGP bridge mem 0xf800-0xfbff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 2.0 on pci0 isa0: ISA bus on isab0 atapci0: SiS 964 UDMA133 controller port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 2.5 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pcm0: SiS 7012 port 0xec00-0xec7f,0xe800-0xe8ff irq 18 at device 2.7 on pci0 pcm0: Analog Devices AD1888 AC97 Codec ohci0: SiS 5571 USB controller mem 0xfebfc000-0xfebfcfff irq 20 at device 3.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: SiS 5571 USB controller on ohci0 usb0: USB revision 1.0 uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: SiS 5571 USB controller mem 0xfebfd000-0xfebfdfff irq 21 at device 3.1 on pci0 usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: SiS 5571 USB controller on ohci1 usb1: USB revision 1.0 uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered ohci2: SiS 5571 USB controller mem 0xfebfe000-0xfebfefff irq 22 at device 3.2 on pci0 usb2: OHCI version 1.0, legacy support usb2: SMM does not respond, resetting usb2: SiS 5571 USB controller on ohci2 usb2: USB revision 1.0 uhub2: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pci0: serial bus, USB at device 3.3 (no driver attached) sis0: SiS 900 10/100BaseTX port 0xe400-0xe4ff mem 0xfebfb000-0xfebfbfff irq 19 at device 4.0 on pci0 miibus0: MII bus on sis0 rlphy0: RTL8201L 10/100 media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sis0: Ethernet address: 00:11:d8:d5:86:54 atapci1: SiS 964 SATA150 controller port 0xef90-0xef9f,0xefe0-0xefe3,0xefa8-0xefaf,0xefe4-0xefe7,0xeff0-0xeff7 irq 17 at device 5.0 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 acpi_button0: Power Button on acpi0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 fdc0: floppy drive controller (FDE) port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fd0: 1440-KB 3.5 drive on fdc0 drive 0 ppc0: Standard parallel printer port port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: Parallel port bus on ppc0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A orm0: ISA Option ROM at iomem 0xcf000-0xd6fff on isa0 pmtimer0 on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 ums0: Microsoft Basic Optical Mouse, rev 1.10/0.00, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. Timecounter TSC frequency 2800810684 Hz quality 800 Timecounters tick every 10.000 msec acd0: CDRW HL-DT-ST GCE-8520B/1.02 at ata1-master PIO4 ad4: 190782MB ST3200822AS/3.01 [387621/16/63] at ata2-master SATA150 Mounting root from ufs:/dev/ad4s2a end When it boots with 6.0 CD in verbose mode the following messages appears just before
Re: cpu-timer rate
On Wed, 2005-Dec-07 03:51:47 -0800, Ed wrote: I certainly do not have a full understanding of the interactions between the various FreeBSD software timers and i386 hardware clocks, but I do know this is not the first time we've seen a problem with the APIC/ACPI timers/clocks. You have a totally different problem. In your case the system is not keeping correct time - this is because VMware does not provide stable clock interrupts - probably due to interactions between VMware and the host OS. In kama's case, the interrupt rate reported by vmstat -i does not match the numbers reported by kern.clockrate. There is no indication that the system is not keeping correct time. Again, I'm no expert, but clock problems do keep cropping up here on the -STABLE list, and the explanations for them to date have not been consistent. AFAIR, all the problems reported here have been related to VMware clients. And as someone stated VMware plays fast and loose with clocks. I'm sure I'm not the only end-user who would appreciate it if the core team This is nothing to do with the core team. -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: permanent per month panic on 5.4-p4
On Wed, Dec 07, 2005 at 05:18:21PM +0200, Oleg Palij wrote: Approximately once per month or two this server panics. We use it for InterSystems Cache` (under linux emulation) and as samba-server (not heavy-loaded). #5 0xc062f0fa in calltrap () at /usr/src/sys/i386/i386/exception.s:140 #6 0x0018 in ?? () #7 0xc0c10010 in ?? () #8 0xc15d0010 in ?? () #9 0xc1465e00 in ?? () #10 0xc1313e94 in ?? () #11 0xcbe69b24 in ?? () #12 0xcbe69b10 in ?? () #13 0x in ?? () #14 0xc0f77480 in ?? () #15 0xc1313e94 in ?? () #16 0x in ?? () #17 0x000c in ?? () #18 0x in ?? () Unfortunately this trace looks corrupted. Are you building your kernel with -O2? Kris pgpar5SIpdPsu.pgp Description: PGP signature
Re: Upgrading 5.3 6.0 buildworld failure now in libmagic
Vizion wrote: Well I do not want to not thank those who have made the upgrades viable. The value of their work should not be underrated. That's a step in the right direction, thanks. :) There is however a perennial problem that freebsd documentation has always been seen as behind and seperate from the development process rather than an integral part of that process. You're right, however that is just the way it is. Most of our really top notch developers are actually very bad at documenting their work (I don't mean bad at being timely with it, I mean that they are bad at DOING it), and frankly their time is better spent elsewhere. The documentation is light years ahead of where it was 11 years ago when I started using FreeBSD for one simple reason. Interested users stepped up and helped make it better. That's the only way that things improve in an open source project. FWIW, I added a paragraph to the UPDATING file in both HEAD and RELENG_6 that describes why updating to the latest code in the installed branch is a good idea before trying a major version upgrade. Hopefully that will help the next person who stumbles over this same issue. Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Copying kernel and OS
I've two machines running FreeBSD 6.0-STABLE. One very fast machine and one very very slow machine. On the fast machine I can compile a new kernel and OS very quickly and easily. Is it possible to transfer the compile world and kernel to the slow machine. If yes whart directories etc... do i have to transfer. Jack ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Adventurous fix for wheel mouse not working in FreeBSD 6.0
On Wed, 07 Dec 2005 09:29:49 + Yann Golanski [EMAIL PROTECTED] wrote: Interesting discussion. Does moused do scrolling in the console? I thought I had used that feature, but now I can't get it to work. Anyway, more info below. Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 option Buttons 6 EndSection On my old machine (running 5.4-stable) the above (minus the ZAxisMapping line) gives me scrolling in X (Xorg) as long as I have moused_flags=-z4 in /etc/rc.conf This works with both a PS/2 connected mouse, and one connected with USB. The mice in question are: psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse Explorer, device ID 4 ums0: IBM Corporation product 0x310b, rev 2.00/1.10, addr 3, iclass 3/1 ums0: 3 buttons and Z dir. and I do start moused manually for the usb mouse, like this: moused -z4 -p /dev/ums0 -I /var/run/moused.ums0.pid (the reason for this is that 5.4 doesn't contain an entry in /etc/devd.conf to start moused when usb mice attaches) this box runs the following: [EMAIL PROTECTED] uname -a FreeBSD kg-work.kg4.no 5.4-STABLE FreeBSD 5.4-STABLE #3: Fri Jul 8 14:26:44 CEST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SS51G i386 [EMAIL PROTECTED] pv | grep xorg-6 xorg-6.8.2 = up-to-date with port [EMAIL PROTECTED] pv | grep xorg-server xorg-server-6.8.2_7 = up-to-date with port Then I tested on my amd64 machine, running FreeBSD 6.0-RELEASE: (Note: I use the same physical mice!) [EMAIL PROTECTED] dmesg | grep psm psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 [EMAIL PROTECTED] dmesg | grep ums ums0: vendor 0x04b3 product 0x310b, rev 2.00/1.10, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. This machine has the complete InputDevice section in /etc/X11/xorg.conf, like quoted above. And scrolling does NOT work. The amd64 machine runs: [EMAIL PROTECTED] uname -a FreeBSD kg-quiet.kg4.no 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Wed Nov 2 19:07:38 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 [EMAIL PROTECTED] pv | grep xorg-6 xorg-6.8.2 = up-to-date with port [EMAIL PROTECTED] pv | grep xorg-server xorg-server-6.8.99.903 = up-to-date with port So I test my laptop, which runs 6.0-stable: [EMAIL PROTECTED] uname -a FreeBSD kg-jobbpc3.kg4.no 6.0-STABLE FreeBSD 6.0-STABLE #0: Sun Nov 6 01:33:12 CET 2005 [EMAIL PROTECTED]:/storage/usr/obj/storage/usr/src/sys/GENERIC i386 This one is a ThinkPad T41, so it has a Synaptics, and in addition I used the same usb mouse as with the others: [EMAIL PROTECTED] dmesg | grep psm psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 [EMAIL PROTECTED] dmesg | grep ums0 ums0: vendor 0x04b3 product 0x310b, rev 2.00/1.10, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. and scrolling does NOT work here either. The laptop runs [EMAIL PROTECTED] pv | grep xorg-6 xorg-6.8.2 = up-to-date with port [EMAIL PROTECTED] pv | grep xorg-server xorg-server-6.8.2_6 needs updating (port has 6.8.2_7) I know that this report is a bit unorganzied, but doesn't the fact that my 5.4-stable machine runs a newer version of the xorg-server port than my 6.0-stable laptop indicate that the fault might be somewhere else than in the xorg-server? -- Regards, Torfinn Ingolfsen, Norway ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading 5.3 6.0 buildworld failure now in libmagic
On Wednesday 07 December 2005 13:01, the author Doug Barton contributed to the dialogue on- Re: Upgrading 5.3 6.0 buildworld failure now in libmagic: Vizion wrote: Well I do not want to not thank those who have made the upgrades viable. The value of their work should not be underrated. That's a step in the right direction, thanks. :) There is however a perennial problem that freebsd documentation has always been seen as behind and seperate from the development process rather than an integral part of that process. You're right, however that is just the way it is. Well having run many very large scale projects myself I find it difficult to accept either implication of this perspective. The first implication is that we should be complacent about it and not seek to find a method to improve the process. The second implication is that top notch developers do not care about end user comfort. My experience is that most do care but they needa helpful environment to achieve food documentation. Most of our really top notch developers are actually very bad at documenting their work (I don't mean bad at being timely with it, I mean that they are bad at DOING it), and frankly their time is better spent elsewhere. That is a judgment call - franky my experience has been that developers who are bad at ensuring their work is well documentated are second rate rather than top rate developers. What I have found works in development is to create team relationships that cover design, development and documentation. Unfortunately this does go against the somewhat individualistic elitist relationship that is unnecessarily sustained by the implications I referred to earlier (neither of which I buy and both of which seem to me to be condescending nonsense). My view would be that the freebsd project might do well to consider implementing a no release without quality documentation assurance policy. Such a policy forces design and development to integrate their work with whoever has been identified as responsible for user documentation (whether that is the designer, developer or a seprate documentation person or team. This encourage the preparation of user documentation as part of the project rather then an afterthought (that depends upon members of the hoi poloi. The documentation is light years ahead of where it was 11 years ago when I started using FreeBSD for one simple reason. Interested users stepped up and helped make it better. That's the only way that things improve in an open source project. OK so some of that talent needs to be harnessed and integrated into the development process. In this day and age we need to believe that user documentation provides a paradigm for design and development not design and development a paradigm for documentation. The latter view characterized development in the early 70,s and 80's. I thought we had moved beyond that. FWIW, I added a paragraph to the UPDATING file in both HEAD and RELENG_6 that describes why updating to the latest code in the installed branch is a good idea before trying a major version upgrade. Hopefully that will help the next person who stumbles over this same issue. Thank you so much for what you do. I trust that you will understand that recomendations for improvement are made BECAUSE the quality of design and development is so good. It deserves better and more professional attention to the role of end user documentation. my two pennorth Doug -- 40 yrs navigating and computing in blue waters. English Owner Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Copying kernel and OS
Jack Raats wrote: I've two machines running FreeBSD 6.0-STABLE. One very fast machine and one very very slow machine. On the fast machine I can compile a new kernel and OS very quickly and easily. Is it possible to transfer the compile world and kernel to the slow machine. If yes whart directories etc... do i have to transfer. see the handbook, this section seems for you: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/small-lan.html Erik -- Ph: +34.666334818 web: http://www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Copying kernel and OS
Jack Raats wrote: I've two machines running FreeBSD 6.0-STABLE. One very fast machine and one very very slow machine. On the fast machine I can compile a new kernel and OS very quickly and easily. Is it possible to transfer the compile world and kernel to the slow machine. If yes whart directories etc... do i have to transfer. Jack I do something like this. I build on the fast machine, and then use NFS to allow the slow machine to access /usr/src and /usr/obj. I have found that it is important to preserve the names of the directories, so that they are also called /usr/src and /usr/obj on the slow machine. Then I just do mergemaster, make installworld, make installkernel (in the appropriate order) on the slow machine, and it works like a charm. The entries in fstab are like this: hub2:/usr/obj/usr/objnfs rw,bg,noauto0 0 hub2:/usr/src/usr/srcnfs rw,bg,noauto0 0 where hub2 is the name of the fast machine. In /etc/exports on hub2 I have something like this /usr -maproot=root -alldirs -network 10.0.0.0 -mask 255.255.255.0 (here 10.0.0.0 is the IP addresses of my LAN) and in /etc/rc.conf on hub2 I have some lines like nfs_server_enable=YES rpcbind_enable=YES Then on the slow machine I simply type mount /usr/src mount /usr/obj -- Stephen Montgomery-Smith [EMAIL PROTECTED] http://www.math.missouri.edu/~stephen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[FreeBSD 6.0-RELEASE] Incorrect geometry for VIA RAID0 array
I'm trying to install FreeBSD 6.0-RELEASE on a RAID0 array attached to the VIA 8237 controller on my Asus A8V Deluxe motherboard. The array consists of two 74G drives. The installer recognizes the array as ar0, but when I enter FDISK to set up my partition, the size of the array is only recognized as 74G, rather than the true 148G. I've double-checked all my BIOS settings, and nothing seems out of order. Please help! Thanks, Jason Harmening ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help - vr0: rx packet loss on new 6.0 kernel
Hi I have two questions: 1. Why on booting up from a new freebsd 6.0 generic kernel I should get repeated messages at high frequency on the consol related to vr0: rx packet loss 2. How can I stop the messages to investigate? I have gone back to 5.4 to lick my wounds until I know how to deal with this one david ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading 5.3 6.0 buildworld failure now in libmagic
Doug Barton wrote: How does this change to UPDATING in RELENG_6 look to you: Index: UPDATING === RCS file: /home/ncvs/src/UPDATING,v retrieving revision 1.416.2.7 diff -u -r1.416.2.7 UPDATING --- UPDATING1 Nov 2005 23:44:40 - 1.416.2.7 +++ UPDATING7 Dec 2005 00:42:04 - @@ -229,7 +229,13 @@ page for more details. Due to several updates to the build infrastructure, source - upgrades from versions prior to 5.3 no longer supported. + upgrades from versions prior to 5.4-STABLE are not likely + to succeed. + + When upgrading from one major version to another, it is + generally best to upgrade to the latest code in the branch + currently installed first, then do another upgrade to the + new branch. Or as another poster said, just say latest RELENG_5 prior to upgrade This is an open source project. The only way that things improve is if people help make it better. It's also worth pointing out that this issue of upgrading to the latest version of the branch you're in has been common knowledge for, basically, always; so if the folks that wrote the release notes neglected to include it, it's understandable. (Although, as you point out, potentially frustrating for new(er) users.) Well, if it's common knowledge, lets see it documented. We're only talking a few lines in the handbook or the release notes, not an entire chapter. If RE wants to change the requirements for upgrading, then how bleeping hard would it be to update either release notes or errata. It's not so much that I now need to do multiple upgrades (ok, that IS pretty annoying), it's that I'd never of known unless I followed this thread. Ok, so, after you calm down a bit, why don't you write a message to [EMAIL PROTECTED] and mention this issue. rant3 My frustration comes from the fact that this seems to be getting worse, not better. In addition, every time I bring this up, I'm told (usually by someone with a freebsd.org address) that, oh we all know/knew about that or, it's common knowledge. In the case of the vinum/gvinum/gmirror trainwreck, I got silence, even though I strongly suspect multiple people knew there were problems, but just didn't want to talk about them. I'd gladly help document some of this, but I'm not the one who knows where the skeletons are snoozing (at least till I trip on a femur) So whats the big issue with letting the rest of us in on the secrets? I'm not looking for a book, just a line or two saying here be dragons somewhere /other /than the basement of the planing department in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying 'Beware of the Leopard' (apologies to Doug Adams). /rant ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [FreeBSD 6.0-RELEASE] Incorrect geometry for VIA RAID0 array
Here's the dmesg output from the installer: ad4: 70911MB WDC WD740GD-00FLA1 27.08D27 at ata2-master SATA150 ad6: 70911MB WDC WD740GD-00FLC0 33.08F33 at ata3-master SATA150 ar0: 70911MB VIA Tech V-RAID RAID0 (stripe 64 KB) status: READY ar0: disk0 READY using ad4 at ata2-master ar0: disk1 READY using ad6 at ata3-master On 12/7/05, Jason Harmening [EMAIL PROTECTED] wrote: I'm trying to install FreeBSD 6.0-RELEASE on a RAID0 array attached to the VIA 8237 controller on my Asus A8V Deluxe motherboard. The array consists of two 74G drives. The installer recognizes the array as ar0, but when I enter FDISK to set up my partition, the size of the array is only recognized as 74G, rather than the true 148G. I've double-checked all my BIOS settings, and nothing seems out of order. Please help! Thanks, Jason Harmening ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Stable Doc issues- thread branched from [Upgrading 5.3 6.0 buildworld failure]
On Wednesday 07 December 2005 13:34, the author Vizion contributed to the dialogue on- Re: Upgrading 5.3 6.0 buildworld failure now in libmagic now Stable Doc issues- thread branched from [Upgrading 5.3 6.0 buildworld failure] On Wednesday 07 December 2005 13:01, the author Doug Barton contributed to the dialogue on- Re: Upgrading 5.3 6.0 buildworld failure now in libmagic: Vizion wrote: Well I do not want to not thank those who have made the upgrades viable. The value of their work should not be underrated. That's a step in the right direction, thanks. :) There is however a perennial problem that freebsd documentation has always been seen as behind and seperate from the development process rather than an integral part of that process. You're right, however that is just the way it is. Well having run many very large scale projects myself I find it difficult to accept either implication of this perspective. The first implication is that we should be complacent about it and not seek to find a method to improve the process. The second implication is that top notch developers do not care about end user comfort. My experience is that most do care but they needa helpful environment to achieve food documentation. Most of our really top notch developers are actually very bad at documenting their work (I don't mean bad at being timely with it, I mean that they are bad at DOING it), and frankly their time is better spent elsewhere. That is a judgment call - franky my experience has been that developers who are bad at ensuring their work is well documentated are second rate rather than top rate developers. What I have found works in development is to create team relationships that cover design, development and documentation. Unfortunately this does go against the somewhat individualistic elitist relationship that is unnecessarily sustained by the implications I referred to earlier (neither of which I buy and both of which seem to me to be condescending nonsense). My view would be that the freebsd project might do well to consider implementing a no release without quality documentation assurance policy. Such a policy forces design and development to integrate their work with whoever has been identified as responsible for user documentation (whether that is the designer, developer or a seprate documentation person or team. This encourage the preparation of user documentation as part of the project rather then an afterthought (that depends upon members of the hoi poloi. The documentation is light years ahead of where it was 11 years ago when I started using FreeBSD for one simple reason. Interested users stepped up and helped make it better. That's the only way that things improve in an open source project. OK so some of that talent needs to be harnessed and integrated into the development process. In this day and age we need to believe that user documentation provides a paradigm for design and development not design and development a paradigm for documentation. The latter view characterized development in the early 70,s and 80's. I thought we had moved beyond that. FWIW, I added a paragraph to the UPDATING file in both HEAD and RELENG_6 that describes why updating to the latest code in the installed branch is a good idea before trying a major version upgrade. Hopefully that will help the next person who stumbles over this same issue. Thank you so much for what you do. I trust that you will understand that recomendations for improvement are made BECAUSE the quality of design and development is so good. It deserves better and more professional attention to the role of end user documentation. my two pennorth Just another thought - it seems that the current philosophy is We know generally what you the users want and you will know exactly what you have got when we have done it!! When we have done we will give it to you for you to sort out how you can use it! Ps. If you fo not like what we have done or the way we have done it you need to be reminded you are lucky we have done it for you!! Come on - it just cannot be like this for ever. Open source projects start like this but as they mature does not the concentatration need to shift towards user satisfaction rather than just a constant gallop towards greater technical functionality. david -- 40 yrs navigating and computing in blue waters. English Owner Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 6.0 as storage server with raid5?
I need to set up a storage server for my personal use. The current solution on my little local network is a haphazard collection of old machines with disks in them, and backups are so-so. I could just set up a normal FreeBSD server, with single disks, and setup another one for the backup. However, I would like to try something new for me; raid. Specifically, I'm looking to set up a server with raid 5 for storage. For the backup server, I haven't decided yet, but I am thinking about a normal server with external (firwire or usb 2.0) disks. I was thinking about gvinum for the storage server, but given the current documentation and the discussions about it now, I don't want to risk it. So, I'm looking at hardware raid 5 controllers. From this list, it seems that areca and 3ware are the best ones, but they are very expensive here. I also know that anything with a SIL 3112 on it are to be avoided. So here is the list over controllers I can get for a reasonable price: Highpoint RocketRAID 1640(4 ports) Promise FastTrak S150 SX4(4 ports) Promise FastTrak S150 SX4-M(4 ports) Highpoint RocketRAID 1810A(4 ports) Highpoint RocketRAID 1820A(8 ports) Intel RAID Controller SRCS16(6 ports) Which one should I get? Are there some that are not supported or should be avoided for other reasons? Other questions: 1) can I install several 4-port RAID controllers in one machine? I can get two RocketRAID 1640's for the price of one RocketRAID 1820A. 2) Rebuilding a damaged array - are some of these controllers better than others? (Easier to handle, rebuilds in shorter time, ?) 3) disks - I understand the importance of using disks from different production runs. Some people have suggested to use disks of different brands as well, but there were no conclusions. Should I stick to the same brand and model, or can I use disks of different brands as long as they are of the same size? 4) PSU considerations. How big a PSU do I need if I want to run two controllers and eight disks in one machine? are there any rules of thumb for sizing this? Other suggestions are welcome. -- Regards, Torfinn Ingolfsen, Norway ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cpu-timer rate
With all due respect, vmware plays fast and loose with the clocks is not a satisfactory technical explanation. The pdf file I linked to in my previous post *does* offer some actual insight as to how vmware simulates i386 hardware clocks and timers. It does not, however, offer any insight as to why it should be only a particular FreeBSD OS (specifically, FreeBSD 6.0-STABLE) which exhibits this curious behavior wherein the hosted OS has a system clock running at precisely half the rate of that of the host OS. I am not satisfied with it is vmware's fault as a technical explanation. They might indeed have simulated the LAPIC timer or some other device incorrectly (and subtly, such that no other OS reveals the flaw), but until the precise nature of that error (if any) is explained, your accusation rings hollow. For these reasons, I believe your technically unsupported assertion that This is nothing to do with the core team should be shelved, pending actual investigation of the phenomenon. I see a potential situation developing here in which two talented teams of developers each regard a shared problem as an outlier, and thus blame the other team without investigating, leaving the problem unresolved. It is no doubt true that those of us who run FreeBSD in VMWare are a minority of a minority, and as such should expect a bit of fiddling and adjusting from time to time rather than continuous smooth sailing on default configurations, but nevertheless, the problems we work around should not be dismissed before they are understood. --Ed P.S.-- The current workaround for the 1/2-speed clock problem is disabling the FreeBSD APIC device. This means FreeBSD can not be run (with a correct system clock) in SMP mode on VMWare emulated hardware. The most recent version of the most widely used vmware product, VMWare Workstation (5.5, released only weeks ago), added support for dual-cpu emulation, on systems that actually have two (or more?) processors. The workaround I found is, I'm afraid, becoming less adequate even as we speak. P.P.S.-- Though my aggrieved tone no doubt suggests otherwise, I would be most happy to offer any assistance I can in getting to the bottom of this. I've looked a bit at the ACPI (not APIC) code to try to figure out why the kernel chooses ACPI-safe rather than ACPI-fast for the kernel timer when APIC is disabled, but I saw no reference to the APIC device in the clock-choosing stuff. The role of the APIC device in the kernel clocks/timers remains opaque to me; all I know is that the release notes for 6.0 clearly state that it is now used in single-processor systems, and that this is a change from 5.x. - Original Message - From: Peter Jeremy [EMAIL PROTECTED] To: Ed [EMAIL PROTECTED] Cc: freebsd-stable@freebsd.org Sent: Wednesday, December 07, 2005 10:22 AM Subject: Re: cpu-timer rate On Wed, 2005-Dec-07 03:51:47 -0800, Ed wrote: I certainly do not have a full understanding of the interactions between the various FreeBSD software timers and i386 hardware clocks, but I do know this is not the first time we've seen a problem with the APIC/ACPI timers/clocks. You have a totally different problem. In your case the system is not keeping correct time - this is because VMware does not provide stable clock interrupts - probably due to interactions between VMware and the host OS. In kama's case, the interrupt rate reported by vmstat -i does not match the numbers reported by kern.clockrate. There is no indication that the system is not keeping correct time. Again, I'm no expert, but clock problems do keep cropping up here on the -STABLE list, and the explanations for them to date have not been consistent. AFAIR, all the problems reported here have been related to VMware clients. And as someone stated VMware plays fast and loose with clocks. I'm sure I'm not the only end-user who would appreciate it if the core team This is nothing to do with the core team. -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [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: cpu-timer rate
On Wed, Dec 07, 2005 at 03:39:04PM -0800, Ed wrote: For these reasons, I believe your technically unsupported assertion that This is nothing to do with the core team should be shelved, pending actual investigation of the phenomenon. Peter's assertion is entirely correct. You misunderstand the role of the core team. It has little to do with technical issues and nothing to do with debugging specific problems in the normal course of things. This problem should be fixed, but it's unlikely in the extreme that it's a problem the core team would have anything to do with. An individual member might in fact be the one to fix it the problem, but that wouldn't have anything to do with them being a core team member. -- Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 pgpEKCZTSuWjj.pgp Description: PGP signature
Re: permanent per month panic on 5.4-p4
On Wed, Dec 07, 2005 at 05:18:21PM +0200, Oleg Palij wrote: Approximately once per month or two this server panics. We use it for InterSystems Cache` (under linux emulation) and as samba-server (not heavy-loaded). # dmesg -a can be found at http://www.dp.uz.gov.ua/dmesg.isc-cache kernel config - http://www.dp.uz.gov.ua/kernel.isc-cache This is a samba server? It looks like you're using smbfs. -- Brian Fundakowski Feldman \'[ FreeBSD ]''\ [EMAIL PROTECTED] \ The Power to Serve! \ Opinions expressed are my own. \,,\ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cpu-timer rate
My apologies, I did not understand this specific meaning of core team when I wrote that. What term should I use in the future, when discussing problems of this nature? FreeBSD kernel developers, or some such? - Original Message - From: Brooks Davis [EMAIL PROTECTED] To: Ed [EMAIL PROTECTED] Cc: Peter Jeremy [EMAIL PROTECTED]; freebsd-stable@freebsd.org Sent: Wednesday, December 07, 2005 4:03 PM Subject: Re: cpu-timer rate ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cpu-timer rate
On Wed, Dec 07, 2005 at 04:23:04PM -0800, Ed wrote: My apologies, I did not understand this specific meaning of core team when I wrote that. What term should I use in the future, when discussing problems of this nature? FreeBSD kernel developers, or some such? FreeBSD developers is fine. Kris pgpiysucQ7zdt.pgp Description: PGP signature
Primise and Intel RAID dont work
Hi PPL! I have a computer with parent payment ASUS P4C800E-DELUXE. OS FreeBSD 6.0-stable (CVS from 21.nov.2005) is established. It is established five hard disks: - One system on ICH5 ata100 Maxtor 6Y200P0 - And four on Promise RAID 0+1 WDC WD3200J (D/B) All fine worked (except for em0, but also he has normally earned after updating) while I have not wanted to establish two more hard disks (Maxtor 6Y080M0) on Intel in Stripe RAID. Hard disks have been put - the system of them has found out (the truth and known all bug failed to enable memory mapping), and I with them was more did than nothing (did not format, did not break - there was no time). In three days of job the system has given out me the following: ad4: req=0xc630f190 SETFEATURES SET TRANSFER MODE semaphore timeout!! DANGER Will Robinson!! This warning has been given many times. And ad4 it is established on Promise! After reboot smartd has given out the warning smartd [767]: Device:/dev/ad10, 1 Currently unreadable (pending) sectors smartd [767]: Device:/dev/ad10, 26 Offline uncorrectable sectors (ad10 the first disk in Stripe RAID on Intel MATRIX) After that has made CVSUP and has put for the night rebuild the world. In the morning has seen - to warrning ad4: req=0xc90efd48 SETFEATURES SET TRANSFER MODE semaphore timeout!! DANGER Will Robinson!! It was added: kern.maxfiles limit exceeded by uid 100, please see tuning (7). Has install the world, has spat and has disconnected these both HDDs from the controller (itself Matrix has remained switched on) Has passed three more days and yesterday has received the new letter:) kernel: DOH! ata_alloc_request failed! kernel: FAILURE - out of memory in ata_raid_init_request last message repeated 4 times kernel: g_vfs_done ():ar0s1d [WRITE (offset=554081878016, length=49152)] error = 5 kernel: g_vfs_done ():ar0s1d [WRITE (offset=554081730560, length=12288)] error = 5 kernel: g_vfs_done ():ar0s1d [WRITE (offset=554082091008, length=65536)] error = 5 kernel: g_vfs_done ():ar0s1d [WRITE (offset=554081927168, length=16384)] error = 5 kernel: g_vfs_done ():ar0s1d [WRITE (offset=554081943552, length=16384)] error = 5 syslogd: kernel boot file is/boot/kernel/kernel kernel: panic: kmem_malloc (4096): kmem_map too small: 172470272 total allocated Then has switched off also the controller, has again updated system and I wait some more days:) Immemorial Russian question - what to make?, I think here it is inappropriate, and so all is clear Remarks on system: it is switched on HHT (ACPI, SMP) and DEVICE POLLING, the network interface em0 and Intel Matrix, both stand on one irq. --- Gy... That that is written above, I wrote yesterday and for a long time to wait it was not necessary In the evening the system has given out me the following: kernel: ar0: WARNING - mirror protection lost. RAID0+1 array in DEGRADED mode kernel: subdisk4: detached kernel: ad4: detached kernel: unknown: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=73576960 kernel: unknown: TIMEOUT - WRITE_DMA retrying (0 retries left) LBA=73576960 After reboot the first disk on Promise appeared in a array 1, and other disks in array 2. Has changed sheduler on old 4BSD and has removed from a kernel device polling References Visible links Hidden links: 1. mailto:[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: Copying kernel and OS
Is it also possible to scp both directories to the slow machine? JAck - Original Message - From: Stephen Montgomery-Smith [EMAIL PROTECTED] To: Jack Raats [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org; FreeBSD Stable freebsd-stable@freebsd.org Sent: Wednesday, December 07, 2005 10:29 PM Subject: Re: Copying kernel and OS Jack Raats wrote: I've two machines running FreeBSD 6.0-STABLE. One very fast machine and one very very slow machine. On the fast machine I can compile a new kernel and OS very quickly and easily. Is it possible to transfer the compile world and kernel to the slow machine. If yes whart directories etc... do i have to transfer. Jack I do something like this. I build on the fast machine, and then use NFS to allow the slow machine to access /usr/src and /usr/obj. I have found that it is important to preserve the names of the directories, so that they are also called /usr/src and /usr/obj on the slow machine. Then I just do mergemaster, make installworld, make installkernel (in the appropriate order) on the slow machine, and it works like a charm. The entries in fstab are like this: hub2:/usr/obj/usr/objnfs rw,bg,noauto0 0 hub2:/usr/src/usr/srcnfs rw,bg,noauto0 0 where hub2 is the name of the fast machine. In /etc/exports on hub2 I have something like this /usr -maproot=root -alldirs -network 10.0.0.0 -mask 255.255.255.0 (here 10.0.0.0 is the IP addresses of my LAN) and in /etc/rc.conf on hub2 I have some lines like nfs_server_enable=YES rpcbind_enable=YES Then on the slow machine I simply type mount /usr/src mount /usr/obj -- Stephen Montgomery-Smith [EMAIL PROTECTED] http://www.math.missouri.edu/~stephen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cpu-timer rate
On Wed, 2005-Dec-07 15:39:04 -0800, Ed wrote: With all due respect, vmware plays fast and loose with the clocks is not a satisfactory technical explanation. Hi-jacking unrelated e-mail threads and top posting is not good etiquette either. It is no doubt true that those of us who run FreeBSD in VMWare are a minority of a minority, I run FreeBSD in VMware at work. After installing vmware-tools and telling VMware to use the host clock I haven't seen any clock problems (definitely in 5.x and I don't recall seeing any in 4.x or 6.x). -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: permanent per month panic on 5.4-p4
Thu, Dec 08, 2005 at 02:44:40AM +0200, [EMAIL PROTECTED] написал: On Wed, Dec 07, 2005 at 05:18:21PM +0200, Oleg Palij wrote: Approximately once per month or two this server panics. We use it for InterSystems Cache` (under linux emulation) and as samba-server (not heavy-loaded). # dmesg -a can be found at http://www.dp.uz.gov.ua/dmesg.isc-cache kernel config - http://www.dp.uz.gov.ua/kernel.isc-cache This is a samba server? It looks like you're using smbfs. Yes, we use it as a samba server. Yes, we use smbfs. # mount | grep smbfs //[EMAIL PROTECTED]/FTPEXCHANGE on /mnt/exchange (smbfs) //[EMAIL PROTECTED]/FREEBSD on /mnt/FreeBSD (smbfs) -- Best regards, Palij Oleg, ISC (Pridn railway) xmpp://[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: permanent per month panic on 5.4-p4
Wed, Dec 07, 2005 at 10:31:32PM +0200, [EMAIL PROTECTED] написал: On Wed, Dec 07, 2005 at 05:18:21PM +0200, Oleg Palij wrote: Approximately once per month or two this server panics. We use it for InterSystems Cache` (under linux emulation) and as samba-server (not heavy-loaded). #5 0xc062f0fa in calltrap () at /usr/src/sys/i386/i386/exception.s:140 #6 0x0018 in ?? () #7 0xc0c10010 in ?? () #8 0xc15d0010 in ?? () #9 0xc1465e00 in ?? () #10 0xc1313e94 in ?? () #11 0xcbe69b24 in ?? () #12 0xcbe69b10 in ?? () #13 0x in ?? () #14 0xc0f77480 in ?? () #15 0xc1313e94 in ?? () #16 0x in ?? () #17 0x000c in ?? () #18 0x in ?? () Unfortunately this trace looks corrupted. Are you building your kernel with -O2? I guess that no. # cat /etc/make.conf WITHOUT_X11=yes WITHOUT_GUI=yes DISTDIR=/data/install/FreeBSD/distfiles NO_INET6=yes #NO_MODULES=1 # added by use.perl 2005-10-12 09:20:03 PERL_VER=5.8.7 PERL_VERSION=5.8.7 # set | grep -- '-O' # I built kernel with # make kernel KERNCONF=... Also, I noticed that in my work computer (6.0-R) all dumps I obtained seems to be corrupted too. I can not even guess why this can happen. -- Best regards, Palij Oleg, ISC (Pridn railway) xmpp://[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: permanent per month panic on 5.4-p4
On Thu, Dec 08, 2005 at 09:50:50AM +0200, Oleg Palij wrote: Wed, Dec 07, 2005 at 10:31:32PM +0200, [EMAIL PROTECTED] ???: On Wed, Dec 07, 2005 at 05:18:21PM +0200, Oleg Palij wrote: Approximately once per month or two this server panics. We use it for InterSystems Cache` (under linux emulation) and as samba-server (not heavy-loaded). #5 0xc062f0fa in calltrap () at /usr/src/sys/i386/i386/exception.s:140 #6 0x0018 in ?? () #7 0xc0c10010 in ?? () #8 0xc15d0010 in ?? () #9 0xc1465e00 in ?? () #10 0xc1313e94 in ?? () #11 0xcbe69b24 in ?? () #12 0xcbe69b10 in ?? () #13 0x in ?? () #14 0xc0f77480 in ?? () #15 0xc1313e94 in ?? () #16 0x in ?? () #17 0x000c in ?? () #18 0x in ?? () Unfortunately this trace looks corrupted. Are you building your kernel with -O2? I guess that no. # cat /etc/make.conf WITHOUT_X11=yes WITHOUT_GUI=yes DISTDIR=/data/install/FreeBSD/distfiles NO_INET6=yes #NO_MODULES=1 # added by use.perl 2005-10-12 09:20:03 PERL_VER=5.8.7 PERL_VERSION=5.8.7 # set | grep -- '-O' # I built kernel with # make kernel KERNCONF=... Also, I noticed that in my work computer (6.0-R) all dumps I obtained seems to be corrupted too. I can not even guess why this can happen. Strange. Can you obtain a trace from DDB for comparison next time? That will at least show where the problem lies, although it will be difficult to analyze without a usable core. Kris pgp3wJgGVIAFt.pgp Description: PGP signature
Re: permanent per month panic on 5.4-p4
On Thu, Dec 08, 2005 at 02:55:15AM -0500, Kris Kennaway wrote: Strange. Can you obtain a trace from DDB for comparison next time? That will at least show where the problem lies, although it will be difficult to analyze without a usable core. Or you might like to try updating to 6.0 to see if the problem is one of those that are already fixed. Kris pgpM7ykjp1RKY.pgp Description: PGP signature
