Re: upgrading 5.4 - 6.0 without reinstalling. safe ?
On Wed, 9 Nov 2005, Ronald Klop wrote: PS.: Just did an upgrade remote from 5.4-RELEASE to 6.0-RELEASE without any problems. Steps taken as described above ;) How do you reboot into single-usermode from remote? (Rebooting isn't really the problem, working in single-usermode is.) Typically, using a serial console which allows you to specify the boot flags and access the console remotely. A serial console is an invaluable tool for remote administration in the event of upgrades, hardware failures, etc, especially if your box supports remote bios and raid management using a serial port but not a command line tool. It is possible to do upgrades without single user mode, but it comes with risks -- if you do this, you want to make sure that you've shut down any important services, and blocked logins by users. Otherwise applications may keel over as shared objects are replaced (generally, pluggable ones), configuration files change, programs start and stop working for windows as they are replaced, etc. This is not a recommended approach, and I don't promise it will work, but I've done remote upgrades on multiuser but quiesced systems many, many times without problems. Robert N M Watson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
kernel problem
hello i got a problem with my 6.0 GENERIC kernel i have done a kgdb on the dumps it gave out here is the output [EMAIL PROTECTED]kgdb kernel.debug /usr/local/var/crash/vmcore.1 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol ps_pglobal_lookup] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd. Unread portion of the kernel message buffer: instruction pointer = 0x20:0xc08badd7 stack pointer = 0x28:0xd4496cc8 frame pointer = 0x28:0xd4496ccc code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, IOPL = 0 current process = 30 (irq19: em0) trap number = 30 panic: unknown/reserved trap Uptime: 46m5s Dumping 511 MB (2 chunks) chunk 0: 1MB (160 pages) ... ok chunk 1: 511MB (130800 pages) 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:165 165 __asm __volatile(movl %%fs:0,%0 : =r (td)); (kgdb) hope this helps you help me !DSPAM:437315ac6516536821444! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_6 tinderbox] failure on i386/i386
TB --- 2005-11-10 08:36:54 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-11-10 08:36:54 - starting RELENG_6 tinderbox run for i386/i386 TB --- 2005-11-10 08:36:54 - cleaning the object tree TB --- 2005-11-10 08:37:19 - checking out the source tree TB --- 2005-11-10 08:37:19 - cd /tinderbox/RELENG_6/i386/i386 TB --- 2005-11-10 08:37:19 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_6 src TB --- 2005-11-10 08:46:59 - building world (CFLAGS=-O -pipe) TB --- 2005-11-10 08:46:59 - cd /src TB --- 2005-11-10 08:46:59 - /usr/bin/make -B buildworld Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything TB --- 2005-11-10 09:36:31 - building generic kernel (COPTFLAGS=-O -pipe) TB --- 2005-11-10 09:36:31 - cd /src TB --- 2005-11-10 09:36:31 - /usr/bin/make buildkernel KERNCONF=GENERIC Kernel build for GENERIC started on Thu Nov 10 09:36:32 UTC 2005 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything Kernel build for GENERIC completed on Thu Nov 10 09:50:41 UTC 2005 TB --- 2005-11-10 09:50:41 - generating LINT kernel config TB --- 2005-11-10 09:50:41 - cd /src/sys/i386/conf TB --- 2005-11-10 09:50:41 - /usr/bin/make -B LINT TB --- 2005-11-10 09:50:41 - building LINT kernel (COPTFLAGS=-O -pipe) TB --- 2005-11-10 09:50:41 - cd /src TB --- 2005-11-10 09:50:41 - /usr/bin/make buildkernel KERNCONF=LINT Kernel build for LINT started on Thu Nov 10 09:50:41 UTC 2005 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies [...] rm -f .newdep /usr/bin/make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES | MKDEP_CPP=cc -E CC=cc xargs mkdep -a -f .newdep -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding /src/sys/dev/acpi_support/acpi_asus.c:50:18: acpi.h: No such file or directory /src/sys/dev/acpi_support/acpi_fujitsu.c:40:18: acpi.h: No such file or directory /src/sys/dev/acpi_support/acpi_panasonic.c:40:18: acpi.h: No such file or directory /src/sys/dev/acpi_support/acpi_sony.c:34:18: acpi.h: No such file or directory /src/sys/dev/acpi_support/acpi_toshiba.c:37:18: acpi.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /obj/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-11-10 09:52:16 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-11-10 09:52:16 - ERROR: failed to build lint kernel TB --- 2005-11-10 09:52:16 - tinderbox aborted ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
unmount pending error on 6.0
Hi, [ Please Cc: me in replies, I'm not subscribed to this list. ] I run a recent RELENG_6 from three days ago. This is my file server and all my drives are doubled. I made a small script that mounts the mirror disk, rsync all files to it and finally unmount it. While testing this script, I interrupted the rsync and the script's trap tried to unmount the filesystem. umount(8) seemed to stall for a couple of minutes (I didn't mesure precisely) and finally I get the following error message : % /mnt/mp3-mirror: unmount pending error: blocks 0 files 10 What is this ? How can I debug it ? Thanks. Regards, -- Jeremie Le Hen jeremie at le-hen dot org ttz at chchile dot org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel problem
On 11/10/05, Jens Holmqvist [EMAIL PROTECTED] wrote:
hello i got a problem with my 6.0 GENERIC kernel
i have done a kgdb on the dumps it gave out here is the output
[EMAIL PROTECTED]kgdb kernel.debug /usr/local/var/crash/vmcore.1
[GDB will not be able to debug user-mode threads:
/usr/lib/libthread_db.so: Undefined symbol ps_pglobal_lookup]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for
details.
This GDB was configured as i386-marcel-freebsd.
Unread portion of the kernel message buffer:
instruction pointer = 0x20:0xc08badd7
stack pointer = 0x28:0xd4496cc8
frame pointer = 0x28:0xd4496ccc
code segment = base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, IOPL = 0
current process = 30 (irq19: em0)
trap number = 30
panic: unknown/reserved trap
Uptime: 46m5s
Dumping 511 MB (2 chunks)
chunk 0: 1MB (160 pages) ... ok
chunk 1: 511MB (130800 pages) 495 479 463 447 431 415 399 383 367
351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95
79 63 47 31 15
#0 doadump () at pcpu.h:165
165 __asm __volatile(movl %%fs:0,%0 : =r (td));
(kgdb)
hope this helps you help me
!DSPAM:437315ac6516536821444!
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
i forgot to do a backtrace so here is a new kgdb output
[EMAIL PROTECTED]kgdb kernel.debug /usr/local/var/crash/vmcore.2
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:
Undefined symbol ps_pglobal_lookup]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as i386-marcel-freebsd.
Unread portion of the kernel message buffer:
instruction pointer = 0x20:0xc08badd7
stack pointer = 0x28:0xd4496cc8
frame pointer = 0x28:0xd4496ccc
code segment = base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, IOPL = 0
current process = 30 (irq19: em0)
trap number = 30
panic: unknown/reserved trap
Uptime: 56m17s
Dumping 511 MB (2 chunks)
chunk 0: 1MB (160 pages) ... ok
chunk 1: 511MB (130800 pages) 495 479 463 447 431 415 399 383 367 351 335
319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15
#0 doadump () at pcpu.h:165
165 __asm __volatile(movl %%fs:0,%0 : =r (td));
(kgdb) quit
[EMAIL PROTECTED]kgdb kernel.debug /usr/local/var/crash/vmcore.2
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:
Undefined symbol ps_pglobal_lookup]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as i386-marcel-freebsd.
Unread portion of the kernel message buffer:
instruction pointer = 0x20:0xc08badd7
stack pointer = 0x28:0xd4496cc8
frame pointer = 0x28:0xd4496ccc
code segment = base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, IOPL = 0
current process = 30 (irq19: em0)
trap number = 30
panic: unknown/reserved trap
Uptime: 56m17s
Dumping 511 MB (2 chunks)
chunk 0: 1MB (160 pages) ... ok
chunk 1: 511MB (130800 pages) 495 479 463 447 431 415 399 383 367 351 335
319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15
#0 doadump () at pcpu.h:165
165 __asm __volatile(movl %%fs:0,%0 : =r (td));
(kgdb) backtrace
#0 doadump () at pcpu.h:165
#1 0xc069d978 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399
#2 0xc069dca6 in panic (fmt=0xc0943594 unknown/reserved trap) at
/usr/src/sys/kern/kern_shutdown.c:555
#3 0xc08c4968 in trap_fatal (frame=0xd4496c88, eva=0) at
/usr/src/sys/i386/i386/trap.c:833
#4 0xc08c43a7 in trap (frame=
{tf_fs = 8, tf_es = 40, tf_ds = 40, tf_edi = -1046961280, tf_esi = 4, tf_ebp
= -733385524, tf_isp = -733385548, tf_ebx = -1046941312, tf_edx = 0, tf_ecx
= -1046941312, tf_eax = 524870, tf_trapno = 30, tf_err = 0, tf_eip =
-1064587817, tf_cs = 32, tf_eflags = 524870, tf_esp = -1046941312, tf_ss =
-733385468}) at /usr/src/sys/i386/i386/trap.c:629
#5 0xc08b109a in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#6 0xc08badd7 in spinlock_exit ()
Re: unmount pending error on 6.0
On 11/10/05, Jeremie Le Hen [EMAIL PROTECTED] wrote: I run a recent RELENG_6 from three days ago. This is my file server and all my drives are doubled. I made a small script that mounts the mirror disk, rsync all files to it and finally unmount it. While testing this script, I interrupted the rsync and the script's trap tried to unmount the filesystem. umount(8) seemed to stall for a couple of minutes (I didn't mesure precisely) and finally I get the following error message : % /mnt/mp3-mirror: unmount pending error: blocks 0 files 10 What is this ? How can I debug it ? My suggestion is that you re-mount the volume read-only, and then do a fsck -fy over it. Another thing to bet is to do fsck -Bfy over the volume, which does a background fsck (in cases that you want the volume to be read-write at the moment). Cheers, ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Filesystems 1TB not possible on 6.0-R (anymore?).
On 11/9/05, Barkley Vowk [EMAIL PROTECTED] wrote: I've got a 3TB (7 x 500GB w/ hot-spare) array on an areca board in amd64. Under 5.4-R I could have 1TB filesystems without an issue. I recall not having problems with 6.0-BETA5 too. [snip] Would you please consider to try gpt instead of bsdlabel? BTW. The dmesg meesage indicates that your array is degraded :-( Cheers, ___ 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.4 - 6.0 without reinstalling. safe ?
Thanks for all the comments - it sounds like it's a pretty safe thing to do. I have one more question though - when I upgrade a machine this wa I will remove all the ports first, so it is just back to the basic system. But Perl is now a port - should I remove this, or should I leave it alone, i.e. is it required for the build process ? cheers, -pcf. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
After 6.0-RELEASE, still cannot find ATA disk com VIA8235
Hi, After 5.4-RELEASE I did try to install FreeBSD on a spare desktop at work, but it failed to boot, with a kernel trap 12 and ATA_IDENTIFY time out. Knowning that 6.0 has a completely new ata driver, I did it again. Now the system boots, and shows absolutely no error message. But also could not identify neither the Samsung Hard disk, nor the CDROM on the VIA8235 ata interface. This same machine is running Fedora Core 3 and Windows XP SP2 perfectly. Indeedm this email is comming out from it, over Windows XP. The motherboard is an ASUS P4VP-MX, with a 2.0GHz P4 CPU, and 1G RAM. The harddisk is a Samsung SP0411N, on primary master, and the CDROM is an LG GCR-8523B, on secondary slave. I also did try with a DVD-writer on secondary master, with no success. Any ideas? TIA, Jonny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Adaptec SATA 1210SA+ Freebsd 6.0
Hi, I just installed freebsd 6 and it all runs fine, but when I try (via sysinstall) to make a new label on a partition on ar0, the system says: 'ata2 disconnect requested' and freezes. I there something extra I need to do make ar0 to work properly? Many thanks, Filip This is the output of my dmesg.boot: = 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 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC ACPI APIC Table: DELL PE500SC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) III CPU family 1133MHz (1130.45-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6b1 Stepping = 1 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA, CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 1207894016 (1151 MB) avail memory = 1173618688 (1119 MB) ioapic0: Changing APIC ID to 1 ioapic1: Changing APIC ID to 2 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 Version 1.1 irqs 0-15 on motherboard ioapic1 Version 1.1 irqs 16-31 on motherboard npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: DELL PE500SC on motherboard acpi0: Power Button (fixed) pci_link0: ACPI PCI Link LNKA on acpi0 pci_link1: ACPI PCI Link LNKB on acpi0 pci_link2: ACPI PCI Link LNKC on acpi0 pci_link3: ACPI PCI Link LNKD on acpi0 pci_link4: ACPI PCI Link LNKE irq 11 on acpi0 pci_link5: ACPI PCI Link LNKF on acpi0 pci_link6: ACPI PCI Link LNKG on acpi0 pci_link7: ACPI PCI Link LNKH irq 10 on acpi0 pci_link8: ACPI PCI Link LNKI on acpi0 pci_link9: ACPI PCI Link LNKJ on acpi0 pci_link10: ACPI PCI Link LNKK on acpi0 pci_link11: ACPI PCI Link LNKL on acpi0 pci_link12: ACPI PCI Link LNKM on acpi0 pci_link13: ACPI PCI Link LNKN on acpi0 pci_link14: ACPI PCI Link LNKO irq 5 on acpi0 pci_link15: ACPI PCI Link LNKP on acpi0 pci_link16: ACPI PCI Link LUSB irq 3 on acpi0 Timecounter ACPI-safe frequency 3579545 Hz quality 1000 acpi_timer0: 32-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 cpu0: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge on acpi0 pci0: ACPI PCI bus on pcib0 fxp0: Intel 82559 Pro/100 Ethernet port 0xecc0-0xecff mem 0xfe102000-0xfe102fff,0xfe00-0xfe0f irq 20 at device 2.0 on pci0 miibus0: MII bus on fxp0 inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:c0:9f:0a:3d:56 atapci0: SiI 3112 SATA150 controller port 0xecb8-0xecbf,0xecb0-0xecb3,0xeca0-0xeca7,0xec98-0xec9b,0xec80-0xec8f mem 0xfe103000-0xfe1031ff irq 23 at device 6.0 on pci0 ata2: ATA channel 0 on atapci0 ata3: ATA channel 1 on atapci0 amr0: LSILogic MegaRAID 1.51 mem 0xfb00-0xfb00 irq 30 at device 10.0 on pci0 amr0: LSILogic CERC ATA100/4ch Firmware H661, BIOS 1.01, 16MB RAM pci0: display, VGA at device 11.0 (no driver attached) isab0: PCI-ISA bridge at device 15.0 on pci0 isa0: ISA bus on isab0 atapci1: ServerWorks CSB5 UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x8b0-0x8bf,0x8c0-0x8c3 at device 15.1 on pci0 ata0: ATA channel 0 on atapci1 ata1: ATA channel 1 on atapci1 ohci0: OHCI (generic) USB controller mem 0xfe10-0xfe100fff irq 3 at device 15.2 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: OHCI (generic) USB controller on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pcib1: ACPI Host-PCI bridge on acpi0 pci1: ACPI PCI bus on pcib1 fdc0: floppy drive controller port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A ppc0: ECP parallel printer port port 0x378-0x37f,0x778-0x77f irq 7 drq 1 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: Parallel port bus on ppc0 plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 pmtimer0 on isa0 orm0: ISA Option ROMs at iomem 0xc-0xc7fff,0xc8000-0xcbfff,0xec000-0xe 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 Timecounter TSC frequency 1130453349 Hz quality 800 Timecounters tick every 1.000 msec acd0: CDROM SAMSUNG CD-ROM
Re: upgrading 5.4 - 6.0 without reinstalling. safe ?
On Thursday 10 November 2005 12:27, Pete French wrote: Thanks for all the comments - it sounds like it's a pretty safe thing to do. I have one more question though - when I upgrade a machine this way I will remove all the ports first, so it is just back to the basic system. But Perl is now a port - should I remove this, or should I leave it alone, i.e. is it required for the build process ? You don't have to remove the ports prior to upgrading. Just recompile them later. A portupgrade -fa will do the trick. I do this port-rebuild remotely using screen thus in case of a lost connection I can reconnect to the portupgrade output. In this case I don't upgrade screen and the command is like portupgrade -fpa -x screen cheers, -pcf. ___ 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]
TCP error messages in 6.0
After 6.0 hit stable, I decided to upgrade my machine. Uname now reads: FreeBSD pumpkin.lolikon.org 6.0-STABLE FreeBSD 6.0-STABLE #0: Sat Nov 5 08:12:50 CET 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PUMPKIN i386 After the upgrade, however, I started getting spurts of error messages posted to me in the daily security run output, looking like this: pumpkin.lolikon.org kernel log messages: +++ /tmp/security.rHb8JAYI Thu Nov 10 03:02:41 2005 +tcp_sack_output: Computed sack_bytes_retransmitted (2904) not the same as cached value (5808) +tcp_sack_output: Computed sack_bytes_retransmitted (2864) not the same as cached value (5768) +tcp_sack_output: Computed sack_bytes_retransmitted (2904) not the same as cached value (5808) +tcp_sack_output: Computed sack_bytes_retransmitted (2904) not the same as cached value (5808) +tcp_sack_output: Computed sack_bytes_retransmitted (2896) not the same as cached value (5800) These appear with a timestamp in /var/log/messages, and it seems I get 800 of these in one second, once a day at random timestamps. Never saw them in 5.4, so I'm assuming it's because of the 6.0 kernel. This is my ifconfig report on the NIC: xl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=9RXCSUM,VLAN_MTU inet6 fe80::210:4bff:fe07:279d%xl0 prefixlen 64 scopeid 0x1 inet 192.168.0.3 netmask 0xff00 broadcast 192.168.0.255 ether 00:10:4b:07:27:9d media: Ethernet autoselect (100baseTX full-duplex) status: active Any ideas on cause and solution? I've never posted on this list before, so if you manage to help, it'll make a very good first impression. ;) Regards, Patrik Roos ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Apache2, mod_python and nss_ldap: Coredump...
On 10 nov 2005, at 00.25, Brian Fundakowski Feldman wrote: On Wed, Nov 09, 2005 at 10:20:26AM +0100, Johan Ström wrote: Hi I got a new 6.0-STABLE box. Rebuilt kernel and world 2 hours ago (against RELENG_6), so it should be pretty new. Im trying to have apache 2.0.55, mod_python 3.1.4 and nss_ldap 239, all the latest from ports. The problem I have is this: If i have LoadModule python_module libexec/apache2/mod_python.so in my httpd.conf, and at the same time have either group: files ldap and/or passwd: files ldap in my nsswitch.conf, i get Segfaults. Example: [EMAIL PROTECTED]:~$ apachectl configtest Syntax OK Segmentation fault (core dumped) [EMAIL PROTECTED]:~$ However, apache itself is running fine, even using mod_python. If i remove either the LoadModule or both the ldap-entrys in nsswitch, the segfaults dissappear. I've compiled httpd with debug symbols, and this is what I found with gdb (httpd -t is same as apachectl configtest): [...] (gdb) where #0 0x in ?? () #1 0x28be6744 in ?? () from /usr/local/lib/nss_ldap.so.1 #2 0x28bf2200 in ?? () from /usr/local/lib/nss_ldap.so.1 Can you try making sure that nss_ldap gets built and linked with -g, and is not stripped, so that all symbols and debug info are preserved as well? Looks to be atexit(3)-related, from here, but the symbols should clear things up. Hi, thanks for the answer! I *think* i got the nss_ldap.so to not be strip'd, at least I cant find any call in the port Makefile or the sources makefile/configure stuff that would strip it. Same result as before, no new symbols.. Strange? I'm compiling with -g and -O0.. However, I've noticed one thing, if I run gdb httpd and then run -t, I get this: [EMAIL PROTECTED]:~$ gdb httpd GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd... (gdb) run -t Starting program: /usr/local/sbin/httpd -t warning: Unable to get location for thread creation breakpoint: generic error [New LWP 100128] [New Thread 0x80fa000 (LWP 100128)] wWarning: DocumentRoot [/usr/local/nagios/share] does not exist Syntax OK [New LWP 100128] Program received signal SIGTRAP, Trace/breakpoint trap. [Switching to LWP 100128] 0x28bce277 in pthread_testcancel () from /usr/lib/libpthread.so.2 (gdb) where #0 0x28bce277 in pthread_testcancel () from /usr/lib/libpthread.so.2 Error accessing memory address 0x28bcd7a8: Bad address. (gdb) Thats the pthread_cancel thing I was talking about before... However, if I do run httpd -t and then check the dump with gdb httpd - c httpd.core, I get the same as first posted. Did the test over and over again, got the same pthread_cancel error, reading the same memory address, re-ran httpd -t a couple of times and seems I only get these pthread_cancel calls... Is there any way to check if a lib is strip'd/got debug symbols or not? Thanks Johan ___ 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.4 - 6.0 without reinstalling. safe ?
You don't have to remove the ports prior to upgrading. Just recompile them later. Why would I want to do that though ? It gives me no advantages, and some serious disadvantages (especially if I am doing this on a 'live' system). Much easier to delete everything prior to the upgrade, and then I know that the machine is just the base system, and that none of my users are running apache, or pine, or exim or whatever - because I deleted them :-). Standard practice for me, even when going from one minor release to the next... -pcf. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Adaptec SATA 1210SA+ Freebsd 6.0
Hi, I also tried to create the label via the command line (following the handbook). web2# dd if=/dev/zero of=/dev/ar0 count=2 2+0 records in 2+0 records out 1024 bytes transferred in 0.000757 secs (1352746 bytes/sec) web2# disklabel /dev/ar0 | disklabel -B -R -r ar0 /dev/stdin disklabel: /dev/ar0: no valid label found And the system freezes and shows 'ata2: DISCONNECT requested' Any help would be appreciated. Thanks, Filip :-Original Message- :From: [EMAIL PROTECTED] :[mailto:[EMAIL PROTECTED] On Behalf Of Filip Wuytack :Sent: 10 November 2005 11:45 :To: freebsd-stable@freebsd.org :Subject: Adaptec SATA 1210SA+ Freebsd 6.0 : :Hi, : :I just installed freebsd 6 and it all runs fine, but when I try (via :sysinstall) to make a new label on a partition on ar0, the system says: :'ata2 disconnect requested' and freezes. I there something :extra I need to :do make ar0 to work properly? : :Many thanks, : :Filip : :This is the output of my dmesg.boot: := : :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 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 :[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC :ACPI APIC Table: DELL PE500SC :Timecounter i8254 frequency 1193182 Hz quality 0 :CPU: Intel(R) Pentium(R) III CPU family 1133MHz :(1130.45-MHz 686-class :CPU) : Origin = GenuineIntel Id = 0x6b1 Stepping = 1 : :Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP, :MTRR,PGE,MCA, :CMOV,PAT,PSE36,MMX,FXSR,SSE :real memory = 1207894016 (1151 MB) :avail memory = 1173618688 (1119 MB) :ioapic0: Changing APIC ID to 1 :ioapic1: Changing APIC ID to 2 :MADT: Forcing active-low polarity and level trigger for SCI :ioapic0 Version 1.1 irqs 0-15 on motherboard :ioapic1 Version 1.1 irqs 16-31 on motherboard :npx0: [FAST] :npx0: math processor on motherboard :npx0: INT 16 interface :acpi0: DELL PE500SC on motherboard :acpi0: Power Button (fixed) :pci_link0: ACPI PCI Link LNKA on acpi0 :pci_link1: ACPI PCI Link LNKB on acpi0 :pci_link2: ACPI PCI Link LNKC on acpi0 :pci_link3: ACPI PCI Link LNKD on acpi0 :pci_link4: ACPI PCI Link LNKE irq 11 on acpi0 :pci_link5: ACPI PCI Link LNKF on acpi0 :pci_link6: ACPI PCI Link LNKG on acpi0 :pci_link7: ACPI PCI Link LNKH irq 10 on acpi0 :pci_link8: ACPI PCI Link LNKI on acpi0 :pci_link9: ACPI PCI Link LNKJ on acpi0 :pci_link10: ACPI PCI Link LNKK on acpi0 :pci_link11: ACPI PCI Link LNKL on acpi0 :pci_link12: ACPI PCI Link LNKM on acpi0 :pci_link13: ACPI PCI Link LNKN on acpi0 :pci_link14: ACPI PCI Link LNKO irq 5 on acpi0 :pci_link15: ACPI PCI Link LNKP on acpi0 :pci_link16: ACPI PCI Link LUSB irq 3 on acpi0 :Timecounter ACPI-safe frequency 3579545 Hz quality 1000 :acpi_timer0: 32-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 :cpu0: ACPI CPU on acpi0 :pcib0: ACPI Host-PCI bridge on acpi0 :pci0: ACPI PCI bus on pcib0 :fxp0: Intel 82559 Pro/100 Ethernet port 0xecc0-0xecff mem :0xfe102000-0xfe102fff,0xfe00-0xfe0f irq 20 at device :2.0 on pci0 :miibus0: MII bus on fxp0 :inphy0: i82555 10/100 media interface on miibus0 :inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto :fxp0: Ethernet address: 00:c0:9f:0a:3d:56 :atapci0: SiI 3112 SATA150 controller port :0xecb8-0xecbf,0xecb0-0xecb3,0xeca0-0xeca7,0xec98-0xec9b,0xec80- :0xec8f mem :0xfe103000-0xfe1031ff irq 23 at device 6.0 on pci0 :ata2: ATA channel 0 on atapci0 :ata3: ATA channel 1 on atapci0 :amr0: LSILogic MegaRAID 1.51 mem 0xfb00-0xfb00 irq :30 at device :10.0 on pci0 :amr0: LSILogic CERC ATA100/4ch Firmware H661, BIOS 1.01, 16MB RAM :pci0: display, VGA at device 11.0 (no driver attached) :isab0: PCI-ISA bridge at device 15.0 on pci0 :isa0: ISA bus on isab0 :atapci1: ServerWorks CSB5 UDMA100 controller port :0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x8b0-0x8bf,0x8c0-0x8c3 at :device 15.1 :on pci0 :ata0: ATA channel 0 on atapci1 :ata1: ATA channel 1 on atapci1 :ohci0: OHCI (generic) USB controller mem :0xfe10-0xfe100fff irq 3 at :device 15.2 on pci0 :ohci0: [GIANT-LOCKED] :usb0: OHCI version 1.0, legacy support :usb0: SMM does not respond, resetting :usb0: OHCI (generic) USB controller on ohci0 :usb0: USB revision 1.0 :uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 :uhub0: 2 ports with 2 removable, self powered :pcib1: ACPI Host-PCI bridge on acpi0 :pci1: ACPI PCI bus on pcib1 :fdc0: floppy drive controller port 0x3f0-0x3f5,0x3f7 irq 6 :drq 2 on acpi0 :fdc0: [FAST] :fd0: 1440-KB 3.5 drive on fdc0 drive 0 :atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 :atkbd0: AT Keyboard irq 1 on atkbdc0 :kbd0 at atkbd0 :atkbd0: [GIANT-LOCKED] :psm0: PS/2 Mouse irq 12 on atkbdc0 :psm0: [GIANT-LOCKED] :psm0: model Generic PS/2 mouse, device ID 0 :sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on :acpi0 :sio0: type 16550A :ppc0: ECP parallel printer
Re: upgrading 5.4 - 6.0 without reinstalling. safe ?
On Thu, 10 Nov 2005 11:27:52 + Pete French [EMAIL PROTECTED] wrote: will remove all the ports first, so it is just back to the basic system. But Perl is now a port - should I remove this, or should I leave it alone, i.e. is it required for the build process ? No, nothing outside the base system is required to build the base system. But don't nuke the ports before running cvsup :) -- C:WIN | Directable Mirror Arrays The computer obeys and wins.| A better way to focus the sun You lose and Bill collects. |licences available see |http://www.sohara.org/ ___ 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.4 - 6.0 without reinstalling. safe ?
No, nothing outside the base system is required to build the base system. But don't nuke the ports before running cvsup :) Heh, I have done that in the past, I have to admit :-) Also must note that one should not remove ones login shell before changing back to /bin/sh if one wants to be able to login again! :-) -pcf. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anyone having problems with xorg 6.8.2 on 6.0-R
On Wed, Nov 09, 2005 at 08:47:41PM -0500, Will Saxon wrote: Hello, I upgraded my amd64 installation to 6.0-RELEASE, and I am no longer able to use X. It exits with a signal 11 error. I have recompiled from ports, installed from packages from freebsd.org and performed a clean installation from an i386 6.0-R cd again installing from both port compilation and packages. I get the same error every time. This was all working fine last Thursday on I believe 6.0-BETA5. System is a dual Opteron 244 on an MSI K8T Master2-FAR with an ATI Radeon 9200SE. I'm using a Radeon 9250 on an amd64 (single athlon64, Asus K8V mobo) system without problems. I've rebuilt xorg with -DWITH_DEBUG and here is a backtrace from the core file: #0 0x282384b3 in kill () from /lib/libc.so.6 #1 0x2822d4f0 in raise () from /lib/libc.so.6 #2 0x282a7c5c in abort () from /lib/libc.so.6 #3 0x0806c1d6 in ddxGiveUp () at xf86Init.c:1228 #4 0x080d945e in AbortServer () at log.c:395 #5 0x080d9520 in FatalError ( f=0x8187798 Caught signal %d. Server aborting\n) at log.c:541 #6 0x08081618 in xf86SigHandler (signo=11) at xf86Events.c:1298 #7 0xbfbfff94 in ?? () #8 0x000b in ?? () #9 0x000c in ?? () #10 0xbfbfe680 in ?? () #11 0x022c in ?? () #12 0x080815c0 in xf86InterceptSignals () at xf86Events.c:1270 #13 0x28632934 in RADEONDisplayDDCConnected (pScrn=0x81df800, DDCType=DDC_VGA, port=0x81c2a44) at radeon_driver.c:914 #14 0x2863e10f in RADEONPreInit (pScrn=0x81df800, flags=0) at radeon_driver.c:1810 #15 0x0806dcc0 in InitOutput (pScreenInfo=0x81b9ac0, argc=4, argv=0xbfbfed20) at xf86Init.c:588 #16 0x080c2ae7 in main (argc=4, argv=0xbfbfed20, envp=0xbfbfed34) at main.c:365 As I mentioned earlier, this occurs on i386 and amd64, compiled on the machine or using packages from freebsd.org. I have tried with and without dri enabled. For DRI, you need an extra device on 6.0. On 5.4 it used to be: device radeondrm On 6.0 it should be: device drm device radeondrm HTH, Roland -- R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt pgpwFpr1ooQeZ.pgp Description: PGP signature
Re: Filesystems 1TB not possible on 6.0-R (anymore?).
On 11/9/05, Barkley Vowk [EMAIL PROTECTED] wrote: I've got a 3TB (7 x 500GB w/ hot-spare) array on an areca board in amd64. Under 5.4-R I could have 1TB filesystems without an issue. I recall not having problems with 6.0-BETA5 too. However, 6.0-R gives me a tragic: /dev/da0s1d723G 54G611G 8%/home Certainly not what I was hoping for. I've tried both i386 and amd64 releases. Especially since that apparent limit is much smaller than 1TB. Curious. Is there any remaining space for a second slice, as in da0s2? ___ 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.4 - 6.0 without reinstalling. safe ?
Pete French [EMAIL PROTECTED] wrote: No, nothing outside the base system is required to build the base system. But don't nuke the ports before running cvsup :) Heh, I have done that in the past, I have to admit :-) Also must note that one should not remove ones login shell before changing back to /bin/sh if one wants to be able to login again! :-) That's why I always put a statically linked copy of my favourite shell (zsh) in /bin, so I can even use it in single-user mode. Under some circumstances it can also be useful to have an emergency user which is not dependant on anything outside the base system (i.e. doesn't use anything from /usr/local, doesn't have its home on an NFS volume, doesn't has its account information on NIS etc.). It should be a member of the wheel group so it can do su. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. cat man du : where Unix geeks go when they die ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Apache2, mod_python and nss_ldap: Coredump...
I can't help with most of your problem, but... On Thu, 10 Nov 2005, Johan Ström wrote: Is there any way to check if a lib is strip'd/got debug symbols or not? file(1) will tell you. /usr/obj/usr/src/lib/libmagic/compress.o: ELF 32-bit LSB relocatable, Intel 80386, version 1 (FreeBSD), not stripped strip(1) the file, and it becomes... /usr/obj/usr/src/lib/libmagic/compress.o: ELF 32-bit LSB relocatable, Intel 80386, version 1 (FreeBSD), stripped David Adam [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: After 6.0-RELEASE, still cannot find ATA disk com VIA8235
João Carlos Mendes Luis [EMAIL PROTECTED] wrote: After 5.4-RELEASE I did try to install FreeBSD on a spare desktop at work, but it failed to boot, with a kernel trap 12 and ATA_IDENTIFY time out. Knowning that 6.0 has a completely new ata driver, I did it again. Now the system boots, and shows absolutely no error message. But also could not identify neither the Samsung Hard disk, nor the CDROM on the VIA8235 ata interface. That's strange. I also have a VT8235 system running 6.0 (RELENG_6 of last week), and the ATA drives work perfectly fine. This is what ``pciconf -lv'' reports: [EMAIL PROTECTED]:17:1: class=0x01018a card=0xaa011106 chip=0x05711106 rev=0x06 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82 EIDE Controller (All VIA Chipsets)' class= mass storage subclass = ATA And these are the relevant lines from /var/run/dmesg.boot: atapci0: VIA 8235 UDMA133 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe000-0xe00f at device 17.1 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 ad0: 238475MB HDS722525VLAT80 V36OA6MA at ata0-master UDMA100 acd0: DVDROM LG DVD-ROM DRD-8160B/1.01 at ata0-slave UDMA33 ad2: 239372MB Maxtor 4A250J0 RAMB1TU0 at ata1-master UDMA133 Maybe you should share your pciconf/dmesg output with us. Messages from a verbose boot might be useful, too. The motherboard is an ASUS P4VP-MX, with a 2.0GHz P4 CPU, and 1G RAM. The harddisk is a Samsung SP0411N, on primary master, and the CDROM is an LG GCR-8523B, on secondary slave. That's not a supported configuration. You cannot have a slave without a master. (It _might_ work if you're lucky, but it's not reliable.) However, it should at least detect the master on the first channel, so that's not the cause of your problem. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. If you aim the gun at your foot and pull the trigger, it's UNIX's job to ensure reliable delivery of the bullet to where you aimed the gun (in this case, Mr. Foot). -- Terry Lambert, FreeBSD-hackers mailing list. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
ahd0: Invalid Sequencer interrupt occurred.
Hi all, The University where i work recent acquire a new server, i install FreeBSD 6.0 and update for STABLE yestarday, in dmesg i see this messages ahd0: Invalid Sequencer interrupt occurred. full-dmesg-output 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 6.0-STABLE #0: Wed Nov 9 01:03:14 UTC 2005 root@:/usr/obj/usr/src/sys/SMP ACPI APIC Table: PTLTD APIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.20GHz (3200.13-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf41 Stepping = 1 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 Features2=0x641dSSE3,RSVD2,MON,DS_CPL,CNTX-ID,CX16,b14 AMD Features=0x2010NX,LM Hyperthreading: 2 logical CPUs real memory = 1073152000 (1023 MB) avail memory = 1041080320 (992 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard ioapic2 Version 2.0 irqs 48-71 on motherboard npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: PTLTD RSDT on motherboard acpi0: Power Button (fixed) pci_link0: ACPI PCI Link LNKA irq 5 on acpi0 pci_link1: ACPI PCI Link LNKB irq 10 on acpi0 pci_link2: ACPI PCI Link LNKC irq 10 on acpi0 pci_link3: ACPI PCI Link LNKD irq 11 on acpi0 pci_link4: ACPI PCI Link LNKE irq 0 on acpi0 pci_link5: ACPI PCI Link LNKF irq 0 on acpi0 pci_link6: ACPI PCI Link LNKG irq 0 on acpi0 pci_link7: ACPI PCI Link LNKH irq 0 on acpi0 Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pci0: unknown at device 0.1 (no driver attached) pci0: base peripheral at device 1.0 (no driver attached) pcib1: ACPI PCI-PCI bridge irq 16 at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge irq 16 at device 3.0 on pci0 pci2: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge at device 0.0 on pci2 pci3: ACPI PCI bus on pcib3 ahd0: Adaptec AIC7902 Ultra320 SCSI adapter port 0x2400-0x24ff,0x2000-0x20ff mem 0xdd20-0xdd201fff irq 32 at device 2.0 on pci3 ahd0: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs ahd1: Adaptec AIC7902 Ultra320 SCSI adapter port 0x2c00-0x2cff,0x2800-0x28ff mem 0xdd202000-0xdd203fff irq 33 at device 2.1 on pci3 ahd1: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs pci2: base peripheral, interrupt controller at device 0.1 (no driver attached) pcib4: ACPI PCI-PCI bridge at device 0.2 on pci2 pci4: ACPI PCI bus on pcib4 em0: Intel(R) PRO/1000 Network Connection, Version - 2.1.7 port 0x3000-0x303f mem 0xdd30-0xdd31 irq 54 at device 2.0 on pci4 em0: Ethernet address: 00:30:48:2e:71:a4 em0: Speed:N/A Duplex:N/A em1: Intel(R) PRO/1000 Network Connection, Version - 2.1.7 port 0x3040-0x307f mem 0xdd32-0xdd33 irq 55 at device 2.1 on pci4 em1: Ethernet address: 00:30:48:2e:71:a5 em1: Speed:N/A Duplex:N/A pci2: base peripheral, interrupt controller at device 0.3 (no driver attached) pcib5: ACPI PCI-PCI bridge irq 16 at device 4.0 on pci0 pci5: ACPI PCI bus on pcib5 pcib6: ACPI PCI-PCI bridge irq 16 at device 6.0 on pci0 pci6: ACPI PCI bus on pcib6 pcib7: ACPI PCI-PCI bridge at device 30.0 on pci0 pci7: ACPI PCI bus on pcib7 pci7: display, VGA at device 1.0 (no driver attached) isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH5 UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1420-0x142f at device 31.1 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 pci0: serial bus, SMBus at device 31.3 (no driver attached) acpi_button0: Power Button on acpi0 ppc0: ECP parallel printer port port 0x378-0x37f,0x778-0x77f irq 7 drq 1 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: Parallel port bus on ppc0 plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: 16550A-compatible COM port port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc0: floppy drive controller port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 pmtimer0 on isa0 orm0: ISA Option ROMs at iomem 0xc-0xc7fff,0xc8000-0xc8fff on isa0 sc0:
Re: upgrading 5.4 - 6.0 without reinstalling. safe ?
hi all On Thu, Nov 10, 2005 at 11:17:13AM +, Jan Grant wrote: FWIW I've just done a successful remote source-based upgrade from 5.4 to 6.0 (I'm brave) with no problems. I use a second root and /usr to be also did that last night with the latest sources, but failed when booting in single user mode: i get a kernel panic when the kernel is loading the nvidia0 device. Providing you remember to rebuild or disable any 5.x-era kernel modules from ports (nvidia, rtc, etc) prior to the reboot it should work fine and offers a now this is interesting :) i have a nvidia gforce 6600xl, but i can't remember installing/using the nvidia port. perhaps its installed as dependency of xorg? moreover in the sources, there is also a agp_nvidia.c. anyone perhaps knows how this relates to the ports? is it an equivalent? are they redundant to eachother? i'll try recompiling this evening the port and try a boot -s :) filip -- http://filip.freeshell.org mailto:[EMAIL PROTECTED] SDF Public Access UNIX System - http://sdf.lonestar.org ___ 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.4 - 6.0 without reinstalling. safe ?
On Thu, 10 Nov 2005, Filip Lenaerts wrote: hi all On Thu, Nov 10, 2005 at 11:17:13AM +, Jan Grant wrote: FWIW I've just done a successful remote source-based upgrade from 5.4 to 6.0 (I'm brave) with no problems. I use a second root and /usr to be also did that last night with the latest sources, but failed when booting in single user mode: i get a kernel panic when the kernel is loading the nvidia0 device. Providing you remember to rebuild or disable any 5.x-era kernel modules from ports (nvidia, rtc, etc) prior to the reboot it should work fine and offers a now this is interesting :) i have a nvidia gforce 6600xl, but i can't remember installing/using the nvidia port. perhaps its installed as dependency of xorg? moreover in the sources, there is also a agp_nvidia.c. anyone perhaps knows how this relates to the ports? is it an equivalent? are they redundant to eachother? You have an option to use the FreeBSD agp device support or nVidia's. I have no idea what criteria one might use to select between them. i'll try recompiling this evening the port and try a boot -s :) If the device is loaded from /boot/loader.conf you might need to disable that in order for the boot to single-user to work. YMMV. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44 (0)117 3317661 http://ioctl.org/jan/ Goth isn't dead, it's just lying very still and sucking its cheeks in. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel problem
On 11/10/05, Jens Holmqvist [EMAIL PROTECTED] wrote: [...] trap number = 30 panic: unknown/reserved trap Uptime: 46m5s Looks weird. Would you please also attach the dmesg.boot generated with boot -v (or verbose boot if you use beastie boot menu), which may be helpful for us to figure out what was happening. Cheers, ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Apache2, mod_python and nss_ldap: Coredump
On 10 nov 2005, at 13.55, Stephane Bortzmeyer wrote: On Wed, Nov 09, 2005 at 01:46:37PM +0100, Johan Ström [EMAIL PROTECTED] wrote a message of 112 lines which said: Im trying to have apache 2.0.55, mod_python 3.1.4 and nss_ldap 239, all the latest from ports. The problem I have is this: If i have LoadModule python_module libexec/apache2/mod_python.so in my httpd.conf, and at the same time have either group: files ldap and/or passwd: files ldap in my nsswitch.conf, i get Segfaults. Example: The only thing I can say is that I have the same problem on FreeBSD 5.4-RELEASE. Intresting... So it seems im not the only one with problems then. CC'ing this to the freebsd-stable-list (and the correct mod_python mail-address.. had it wrong in the first mail to apache-users).. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Anyone having problems with xorg 6.8.2 on 6.0-R
-Original Message- From: Roland Smith [mailto:[EMAIL PROTECTED] Sent: Thursday, November 10, 2005 7:38 AM To: Will Saxon Cc: [EMAIL PROTECTED] Subject: Re: Anyone having problems with xorg 6.8.2 on 6.0-R For DRI, you need an extra device on 6.0. On 5.4 it used to be: device radeondrm On 6.0 it should be: device drm device radeondrm HTH, Roland Thanks Roland. I loaded the radeon kernel module and that usually takes care of things. What I have also determined that I think is odd, is that I can start X remotely from home, via SSH, without issue. It is only locally that I am not able to start X. -Will ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel problem
On 11/10/05, Xin LI [EMAIL PROTECTED] wrote: On 11/10/05, Jens Holmqvist [EMAIL PROTECTED] wrote: [...] trap number = 30 panic: unknown/reserved trap Uptime: 46m5s Looks weird. Would you please also attach the dmesg.boot generated with boot -v (or verbose boot if you use beastie boot menu), which may be helpful for us to figure out what was happening. Cheers, ok here is my dmesg when i started it in verbose 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 6.0-STABLE #0: Tue Nov 8 03:32:10 CET 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel /boot/kernel/kernel at 0xc0b55000. Preloaded elf module /boot/kernel/acpi.ko at 0xc0b55188. Calibrating clock(s) ... i8254 clock: 1193368 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 1400600893 Hz CPU: AMD Athlon(tm) XP 1600+ (1400.60-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x662 Stepping = 2 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE AMD Features=0xc0480800SYSCALL,MP,MMX+,3DNow+,3DNow Data TLB: 32 entries, fully associative Instruction TLB: 16 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 internal cache: 256 kbytes, 64 bytes/line, 1 lines/tag, 8-way associative real memory = 536805376 (511 MB) Physical memory chunk(s): 0x1000 - 0x0009, 651264 bytes (159 pages) 0x0010 - 0x003f, 3145728 bytes (768 pages) 0x00c25000 - 0x1f6b7fff, 514404352 bytes (125587 pages) avail memory = 515964928 (492 MB) MP Configuration Table version 1.4 found at 0xc00f1400 Table 'FACP' at 0x1fff3040 Table 'APIC' at 0x1fff6b00 MADT: Found table at 0x1fff6b00 APIC: Using the MADT enumerator. MADT: Found CPU APIC ID 0 ACPI ID 0: enabled ACPI APIC Table: VIA694 AWRDACPI bios32: Found BIOS32 Service Directory header at 0xc00fb030 bios32: Entry = 0xfb4a0 (c00fb4a0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xb4d0 pnpbios: Found PnP BIOS data at 0xc00fbfa0 pnpbios: Entry = f:bfd0 Rev = 1.0 Other BIOS signatures found: APIC: CPU 0 has ACPI ID 0 MADT: Found IO APIC ID 2, Interrupt 0 at 0xfec0 ioapic0: Routing external 8259A's - intpin 0 ioapic0: intpin 0 - ExtINT (edge, high) ioapic0: intpin 1 - ISA IRQ 1 (edge, high) ioapic0: intpin 2 - ISA IRQ 2 (edge, high) ioapic0: intpin 3 - ISA IRQ 3 (edge, high) ioapic0: intpin 4 - ISA IRQ 4 (edge, high) ioapic0: intpin 5 - ISA IRQ 5 (edge, high) ioapic0: intpin 6 - ISA IRQ 6 (edge, high) ioapic0: intpin 7 - ISA IRQ 7 (edge, high) ioapic0: intpin 8 - ISA IRQ 8 (edge, high) ioapic0: intpin 9 - ISA IRQ 9 (edge, high) ioapic0: intpin 10 - ISA IRQ 10 (edge, high) ioapic0: intpin 11 - ISA IRQ 11 (edge, high) ioapic0: intpin 12 - ISA IRQ 12 (edge, high) ioapic0: intpin 13 - ISA IRQ 13 (edge, high) ioapic0: intpin 14 - ISA IRQ 14 (edge, high) ioapic0: intpin 15 - ISA IRQ 15 (edge, high) ioapic0: intpin 16 - PCI IRQ 16 (level, low) ioapic0: intpin 17 - PCI IRQ 17 (level, low) ioapic0: intpin 18 - PCI IRQ 18 (level, low) ioapic0: intpin 19 - PCI IRQ 19 (level, low) ioapic0: intpin 20 - PCI IRQ 20 (level, low) ioapic0: intpin 21 - PCI IRQ 21 (level, low) ioapic0: intpin 22 - PCI IRQ 22 (level, low) ioapic0: intpin 23 - PCI IRQ 23 (level, low) MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 - intpin 2 ioapic0: intpin 2 trigger: edge ioapic0: intpin 2 polarity: high MADT: Interrupt override: source 9, irq 9 ioapic0: intpin 9 trigger: level ioapic0: intpin 9 polarity: low ioapic0 Version 0.2 irqs 0-23 on motherboard cpu0 BSP: ID: 0x VER: 0x00040010 LDR: 0x0100 DFR: 0x0fff lint0: 0x00010700 lint1: 0x0400 TPR: 0x SVR: 0x01ff timer: 0x000100ef therm: 0x err: 0x0001 pcm: 0x0001 wlan: 802.11 Link Layer random: entropy source, Software, Yarrow nfslock: pseudo-device io: I/O mem: memory Pentium Pro MTRR support enabled null: null device, zero device npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: VIA694 AWRDACPI on motherboard acpi0: [MPSAFE] pci_open(1): mode 1 addr port (0x0cf8) is 0x80008840 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=30991106) pcibios: BIOS version 2.10 Found $PIR table, 8 entries at 0xc00fdef0 PCI-Only Interrupts: 10 11 12 Location Bus Device Pin Link IRQs slot 1 0 16 A 0x01 3 4 5 7 9 10 11 12 14 15 slot 1 0 16 B 0x02 3 4 5 7 9 10 11 12 14 15 slot 1 0 16 C 0x03 3 4 5 7 9 10 11 12 14 15 slot 1 0 16 D 0x04 3 4 5 7 9 10 11 12 14 15 slot 2 0 15 A 0x02 3 4 5 7 9 10 11 12 14 15 slot 2 0 15 B 0x04 3 4 5 7 9 10 11 12 14 15 slot 2 0 15 C 0x03 3 4
Re: Apache2, mod_python and nss_ldap: Coredump...
On 10 nov 2005, at 12.54, Johan Ström wrote: On 10 nov 2005, at 00.25, Brian Fundakowski Feldman wrote: On Wed, Nov 09, 2005 at 10:20:26AM +0100, Johan Ström wrote: Hi I got a new 6.0-STABLE box. Rebuilt kernel and world 2 hours ago (against RELENG_6), so it should be pretty new. Im trying to have apache 2.0.55, mod_python 3.1.4 and nss_ldap 239, all the latest from ports. The problem I have is this: If i have LoadModule python_module libexec/apache2/mod_python.so in my httpd.conf, and at the same time have either group: files ldap and/or passwd: files ldap in my nsswitch.conf, i get Segfaults. Example: [EMAIL PROTECTED]:~$ apachectl configtest Syntax OK Segmentation fault (core dumped) [EMAIL PROTECTED]:~$ However, apache itself is running fine, even using mod_python. If i remove either the LoadModule or both the ldap-entrys in nsswitch, the segfaults dissappear. I've compiled httpd with debug symbols, and this is what I found with gdb (httpd -t is same as apachectl configtest): [...] (gdb) where #0 0x in ?? () #1 0x28be6744 in ?? () from /usr/local/lib/nss_ldap.so.1 #2 0x28bf2200 in ?? () from /usr/local/lib/nss_ldap.so.1 Can you try making sure that nss_ldap gets built and linked with -g, and is not stripped, so that all symbols and debug info are preserved as well? Looks to be atexit(3)-related, from here, but the symbols should clear things up. Hi, thanks for the answer! I *think* i got the nss_ldap.so to not be strip'd, at least I cant find any call in the port Makefile or the sources makefile/ configure stuff that would strip it. Same result as before, no new symbols.. Strange? I'm compiling with -g and -O0.. However, I've noticed one thing, if I run gdb httpd and then run - t, I get this: [EMAIL PROTECTED]:~$ gdb httpd GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd... (gdb) run -t Starting program: /usr/local/sbin/httpd -t warning: Unable to get location for thread creation breakpoint: generic error [New LWP 100128] [New Thread 0x80fa000 (LWP 100128)] wWarning: DocumentRoot [/usr/local/nagios/share] does not exist Syntax OK [New LWP 100128] Program received signal SIGTRAP, Trace/breakpoint trap. [Switching to LWP 100128] 0x28bce277 in pthread_testcancel () from /usr/lib/libpthread.so.2 (gdb) where #0 0x28bce277 in pthread_testcancel () from /usr/lib/libpthread.so.2 Error accessing memory address 0x28bcd7a8: Bad address. (gdb) Thats the pthread_cancel thing I was talking about before... However, if I do run httpd -t and then check the dump with gdb httpd -c httpd.core, I get the same as first posted. Did the test over and over again, got the same pthread_cancel error, reading the same memory address, re-ran httpd -t a couple of times and seems I only get these pthread_cancel calls... Is there any way to check if a lib is strip'd/got debug symbols or not? Thanks Johan Okay, some news here then.. Thanks to David Adam I used file to determine if it was striped or not, seems it was.. So now I've fixed it, not striped anymore (the install command striped it, i missed that).. New debug output then: (gdb) where #0 0x in ?? () #1 0x28bd9730 in __do_global_dtors_aux () from /usr/local/lib/ nss_ldap.so.1 #2 0x28be2984 in _fini () from /usr/local/lib/nss_ldap.so.1 #3 0x280b5018 in tls_dtv_generation () from /libexec/ld-elf.so.1 #4 0x280b63d8 in ?? () from /libexec/ld-elf.so.1 #5 0xbfbfe628 in ?? () #6 0x2809d076 in elf_hash () from /libexec/ld-elf.so.1 #7 0x2809f958 in dlclose () from /libexec/ld-elf.so.1 #8 0x284b064c in _nsdbtaddsrc () from /lib/libc.so.6 #9 0x284b020f in endhostent () from /lib/libc.so.6 #10 0x284b06cc in _nsdbtaddsrc () from /lib/libc.so.6 #11 0x284cf35f in __cxa_finalize () from /lib/libc.so.6 #12 0x284cef9a in exit () from /lib/libc.so.6 #13 0x0806b746 in destroy_and_exit_process (process=0x80a4090, process_exit_value=0) at main.c:216 #14 0x0806c0fe in main (argc=2, argv=0xbfbfe838) at main.c:565 (Also sent this to the other lists this thread is discussed in). Johan ___ 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.4 - 6.0 without reinstalling. safe ?
On Thu, Nov 10, 2005 at 02:13:26PM +0100, Oliver Fromme wrote: Under some circumstances it can also be useful to have an emergency user which is not dependant on anything outside the base system (i.e. doesn't use anything from /usr/local, doesn't have its home on an NFS volume, doesn't has its account information on NIS etc.). It should be a member of the wheel group so it can do su. In the same idea, I never change root's shell (and often on NIS environnement I keep the least uper bound shell of all install and had a little trick to startup files to find my fav' shell at login and then exec it ... ) I think also that root should have /rescue/*sh as shell (static versions) just to be sure ... -- Burelle Marwan, Equipe Bases de Donnees - LRI http://www.cduce.org ([EMAIL PROTECTED] | [EMAIL PROTECTED]) pgpYvt7CaIHXw.pgp Description: PGP signature
Re: upgrading 5.4 - 6.0 without reinstalling. safe ?
Marwan Burelle [EMAIL PROTECTED] wrote: On Thu, Nov 10, 2005 at 02:13:26PM +0100, Oliver Fromme wrote: Under some circumstances it can also be useful to have an emergency user which is not dependant on anything outside the base system (i.e. doesn't use anything from /usr/local, doesn't have its home on an NFS volume, doesn't has its account information on NIS etc.). It should be a member of the wheel group so it can do su. In the same idea, I never change root's shell I never change root's login shell either -- because it is never used. I think also that root should have /rescue/*sh as shell (static versions) just to be sure ... Well, I vote for /sbin/nologin as root's login shell. In single-user mode, the systems asks for the shell, with /bin/sh being the default. In multi-user mode, nobody should ever log in as root. You rather log in as normal user and then use su -m, or use sudo(8) or super(1) or whatever. Therefore I think root's login shell has zero meaning, and it should be /sbin/nologin for security reasons (in case you accidentally enabled root login via ssh, or you have set the virtual terminals set to secure in /etc/ttys). Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATA RAID problem in 6.0-RC1 (ata_alloc_request/ata_raid_init_request)
On Wed, 26 Oct 2005, David Taylor wrote: I've been seeing a number of strange messages in my log since updating to 6.0-RC1. Usually they happen when some intense disk access is happening (e.g. when /etc/periodic/security/100.chksetuid is running at 03:01), but it doesn't happen _every_ morning, and it doesn't always happen if I manually run the script. It also occasionally happens at times where I wouldn't say I was doing much with the disk. [snip] I'm still seeing (lots) of these messages (below) on 6.0-RELEASE. Should I just file a PR about it, and is there anything else that would be useful to track down what's causing them? A sample of the error messages follows: Oct 25 21:20:21 outcold kernel: DOH! ata_alloc_request failed! Oct 25 21:20:23 outcold kernel: FAILURE - out of memory in ata_raid_init_request Oct 25 21:20:23 outcold last message repeated 131 times Oct 25 21:20:23 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=34597617664, length=16384)]error = 5 Oct 25 21:20:23 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=34597748736, length=16384)]error = 5 Oct 25 21:20:23 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=34597961728, length=16384)]error = 5 Oct 25 21:20:23 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=34598207488, length=16384)]error = 5 Oct 25 21:20:23 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=34598453248, length=16384)]error = 5 Oct 25 21:20:23 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=34598682624, length=16384)]error = 5 Oct 25 21:20:23 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=34598895616, length=16384)]error = 5 Oct 25 21:20:23 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=34599174144, length=16384)]error = 5 Oct 25 21:20:23 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=34599452672, length=16384)]error = 5 Oct 25 21:20:23 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=34599747584, length=16384)]error = 5 ... ... Oct 25 21:20:23 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=34629107712, length=16384)]error = 5 Oct 25 21:20:23 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=34629386240, length=16384)]error = 5 Oct 25 21:20:23 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=34629648384, length=16384)]error = 5 Oct 25 21:20:53 outcold kernel: DOH! ata_alloc_request failed! Oct 25 21:20:53 outcold kernel: FAILURE - out of memory in ata_raid_init_request Oct 25 21:20:53 outcold last message repeated 146 times Oct 25 21:20:53 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=7635156992, length=16384)]error = 5 Oct 25 21:20:53 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=7635533824, length=16384)]error = 5 Oct 25 21:20:53 outcold kernel: g_vfs_done():ar0s1f[WRITE(offset=7635992576, length=16384)]error = 5 ... ... etc -- David Taylor ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATA RAID problem in 6.0-RC1 (ata_alloc_request/ata_raid_init_request)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Taylor wrote: | [snip] | | I'm still seeing (lots) of these messages (below) on 6.0-RELEASE. | Should I just file a PR about it, and is there anything else that | would be useful to track down what's causing them? I get these with an HighPoint HPT372N UDMA133 controller .. what is your's? Michael -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) iD8DBQFDc2IAiJykeV6HPMURAoKTAKC9yGD590r1xrjeV0DCKNUtqQvhewCeIQzt B7+frZ9Nvb+iE59RaTBHZAM= =NAXF -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATA RAID problem in 6.0-RC1 (ata_alloc_request/ata_raid_init_request)
On Thu, 10 Nov 2005, Michael Butler wrote: David Taylor wrote: | [snip] | | I'm still seeing (lots) of these messages (below) on 6.0-RELEASE. | Should I just file a PR about it, and is there anything else that | would be useful to track down what's causing them? I get these with an HighPoint HPT372N UDMA133 controller .. what is your's? It was in my previous mail, perhaps I snipped a little too much... anyway: atapci0: Promise PDC20579 SATA150 controller port 0xec00-0xec7f,0xe800-0xe8ff mem 0xcfffb000-0xcfffbfff,0xcffc-0xcffd irq 17 at device 13.0 on pci0 atapci1: VIA 6420 SATA150 controller port 0xc800-0xc807,0xc400-0xc403,0xc000-0 xc007,0xbc00-0xbc03,0xb800-0xb80f,0xb400-0xb4ff irq 20 at device 15.0 on pci0 atapci2: VIA 8237 UDMA133 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376, ar0 (mentioned in the error messages) is ad4 and ad6, which are connected to the Promise controller. ata2: ATA channel 0 on atapci0 ata3: ATA channel 1 on atapci0 ata4: ATA channel 2 on atapci0 ad4: 156334MB Maxtor 6B160M0 BANC1B70 at ata2-master SATA150 ad6: 156334MB Maxtor 6B160M0 BANC1B70 at ata3-master SATA150 ar0: 156334MB Promise Fasttrak RAID1 status: READY ar0: disk0 READY (master) using ad6 at ata3-master ar0: disk1 READY (mirror) using ad4 at ata2-master -- David Taylor ___ 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.4 - 6.0 without reinstalling. safe ?
On 11/10/05, Oliver Fromme [EMAIL PROTECTED] wrote: Well, I vote for /sbin/nologin as root's login shell. In single-user mode, the systems asks for the shell, with /bin/sh being the default. In multi-user mode, nobody should ever log in as root. You rather log in as normal user and then use su -m, or use sudo(8) or super(1) or whatever. It's awkward to have to reboot a machine just to log in to it from a console. Let's say you're colocated and utilize a remote hands service, or you make a mistake with your firewall. You're better off disabling root logins in sshd_config, so no one can use root from remote. Then you can leave a password on the root account and still have console access. I just leave root logins enabled and use ssh keys. Leaves a very nice, easy to follow, one-line-per-login paper trail of who logged in as root from where and when. But it all comes down to preference, since all options for root access (su, ssh keys, sudo, etc) all carry risk. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATA RAID problem in 6.0-RC1 (ata_alloc_request/ata_raid_init_request)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Taylor wrote: | ar0: 156334MB Promise Fasttrak RAID1 status: READY | ar0: disk0 READY (master) using ad6 at ata3-master | ar0: disk1 READY (mirror) using ad4 at ata2-master Ok - so the apparent kernel memory leak appears to be associated with RAID-1. I have RAID-0+1 configured. To confirm another observation of mine, do you see lots of allocated memory blocks for the controller?, e.g. [EMAIL PROTECTED]:/home/imb sysctl -a | grep ^ata_ ata_composit:192,0, 69703,117, 406336 ata_request: 200,0, 139406, 73, 2106449 (size) (max.) (used) (avail) (requests) There appears to be a path through the ar driver which fails to free the blocks recording the requests .. Michael -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) iD8DBQFDc3FsiJykeV6HPMURArjlAJ409EXGbq1WORzvtEzoIYKcTkIk4gCgxbFY W5Mc2+ylgsb06Rgk0ZjepIs= =hpS6 -END PGP SIGNATURE- ___ 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.4 - 6.0 without reinstalling. safe ?
How is this different from a fresh install? Except for a very limited amount in config files, which would be easier to save and restore. And home directories. Again, save and restore. Pete French wrote: *** This message has been scanned by the InterScan for CSC-SSM and found to be free of known security risks. ***-*** You don't have to remove the ports prior to upgrading. Just recompile them later. Why would I want to do that though ? It gives me no advantages, and some serious disadvantages (especially if I am doing this on a 'live' system). Much easier to delete everything prior to the upgrade, and then I know that the machine is just the base system, and that none of my users are running apache, or pine, or exim or whatever - because I deleted them :-). Standard practice for me, even when going from one minor release to the next... -pcf. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- __ Paul T. Root /_ \ 1977 MGB / /|| \\ ||\/ || _ | || || || \ ||__// \__/ ___ 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.4 - 6.0 without reinstalling. safe ?
How is this different from a fresh install? It doesnt require physical access to the machine and a CD drive (or any of the other hoops I sometime jump through to boot the install process). Much easier. -pcf. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
usbd.conf
Hi,
I've found that usbd on 6.0-RELEASE doesn't react on detach event properly:
usbd.conf:
device iKey 3000 Series Token
vendor 0x04b9
product 0x1300
detach /usr/local/etc/rc.d/openct.sh stop
attach /usr/local/etc/rc.d/openct.sh start
what happens (usbd -d -):
usbd: opened /dev/usb0
usbd: opened /dev/usb1
usbd: opened /dev/usb2
usbd: opened /dev/usb3
usbd: reading configuration file /etc/usbd.conf
usbd: action 1: ActiveWire board, firmware download
vndr=0x0854 prdct=0x0100 rlse=0x
attach='/usr/local/bin/ezdownload -f
/usr/local/share/usb/firmware/0854.0100.0_01.hex ${DEVNAME}'
usbd: action 2: Entrega Serial with UART
vndr=0x1645 prdct=0x8001 rlse=0x0101
attach='/usr/sbin/ezdownload -v -f /usr/share/usb/firmware/1645.8001.0101
/dev/${DEVNAME}'
usbd: action 3: Handspring Visor
vndr=0x082d prdct=0x0100 rlse=0x0100
devname: ugen[0-9]+
attach='/usr/local/bin/coldsync -md -p /dev/${DEVNAME} -t usb'
usbd: action 4: iKey 3000 Series Token
vndr=0x04b9 prdct=0x1300
attach='/usr/local/etc/rc.d/openct.sh start'
detach='/usr/local/etc/rc.d/openct.sh stop'
usbd: action 5: USB device
usbd: 5 actions
usbd: opened /dev/usb
usbd: processing event queue on /dev/usb
usbd: device-attach event at 1131639766.674323000, iKey 3000 Series Token,
vendor 0x04b9:
vndr=0x04b9 prdct=0x1300 rlse=0x0100 clss=0x00ff subclss=0x prtcl=0x
device names: ugen0
=== match attempt: ugen0
usbd: Found action 'iKey 3000 Series Token' for iKey 3000 Series Token, vendor
0x04b9 at ugen0
usbd: action 0: iKey 3000 Series Token
vndr=0x04b9 prdct=0x1300
attach='/usr/local/etc/rc.d/openct.sh start'
detach='/usr/local/etc/rc.d/openct.sh stop'
usbd: Setting DEVNAME='ugen0'
usbd: Executing '/usr/local/etc/rc.d/openct.sh start'
Starting smart card terminal framework: OpenCTDebug: ifd_scan_usb: BSD:
ifd_scan_usb
Debug: ifd_scan_usb: BSD: ifd_scan_usb: ifd_driver_for(vendor
0x04b9[0x04b9].iKey 3000 Series Token[0x1300)
Debug: ifd_spawn_handler: driver=ikey3k, device=/dev/ugen0, index=-1
usbd: '/usr/local/etc/rc.d/openct.sh start' is ok
usbd: processing event queue on /dev/usb
usbd: device-detach event at 1131639769.712468000, product 0x1300, vendor
0x04b9:
vndr=0x04b9 prdct=0x1300 rlse=0x0100 clss=0x00ff subclss=0x prtcl=0x
So attach event works correctly, but even though detach is noted by
usbd, it doesn't launch the action. Any hint before diving into
sources and ktracing?
Thanks,
Petr
Petr Holub
CESNET z.s.p.o. Supercomputing Center Brno
Zikova 4 Institute of Compt. Science
162 00 Praha 6, CZMasaryk University
Czech Republic Botanicka 68a, 60200 Brno, CZ
e-mail: [EMAIL PROTECTED] phone: +420-549493944
fax: +420-541212747
e-mail: [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: Filesystems 1TB not possible on 6.0-R (anymore?).
On 11/9/05, Barkley Vowk [EMAIL PROTECTED] wrote: No. The installer showed only one slice da0s1d, and the whole disk was assigned to it. I'd check on the running box but: koth# disklabel -e /dev/da0 disklabel: disks with more than 2^32-1 sectors are not supported /dev only shows: koth# ls /dev/da0* /dev/da0/dev/da0s1 /dev/da0s1c /dev/da0s1d So I expect it is all assigned to the one slice. Yeah, I would guess that as well. FWIW, we've used FreeBSD 5.4 with 1TB partitions, and 5.4-STABLE as of a few months ago. This was with a 3ware card. If something happened to reduce the maximum slice size, it was recent. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gnome-upgrade.sh
On Wednesday 09 November 2005 18:26, Paul Root wrote: Michael C. Shultz wrote: *** This message has been scanned by the InterScan for CSC-SSM and found to be free of known security risks. ***-*** port and install or restart gnome-upgrade.sh I'm now assuming that since all gnome has been wiped off the disk, that the thing to do is build/install the port directly. Starting that up, I seem to be having the same downloading difficulties. As an alternative to gnome-upgrade.sh you may want to consider using sysutils/portmanager, all you need do is run portmanager x11/gnome2 It'll do the upgrade no problem, tested it twice now myself. Interesting. The web page said specifically don't do portupgrade. I didn't say portupgrade, it is sysutils/portmanager My main problem is it's having trouble downloading, I think. I'm not sure why. We found problems on our Pix (actually the new ASA firewall) and the port the machine is on. We were getting half duplex, but those are all fixed now. Curiously, command line ftp never has a problem downloading, it's fetch (I think it's using fetch), that can't seem to download. While your problem has nothing to do with gnome-upgrade.sh, portmanager is designed to automatically pickup from where it left off, so stopping and starting isn't a problem, and it won't remove a port until its replacement is successfully built so if the port didn't fetch you won't lose anything, portmanager will just move on to the next port that can be upgraded, it is very fail safe. -Mike Note: I removed [EMAIL PROTECTED] from the return address as it is a dupe of [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: gnome-upgrade.sh
On Thursday 10 November 2005 09:42, Paul T. Root wrote: I moved the machine to a DSL line here, and am running portmanager. It seems to be working. We're going to investigate issues with this beta Cisco ASA machine. I am very interested at how things go with your upgrade, please keep me informed. Just to let you know, the current version of portmanager is 0.3.3_2 if anything goes wrong check that first portmanager -v. If any problems arise I am more than happy to work with you in solving them quickly. -Mike Michael C. Shultz wrote: *** This message has been scanned by the InterScan for CSC-SSM and found to be free of known security risks. ***-*** On Wednesday 09 November 2005 18:26, Paul Root wrote: Michael C. Shultz wrote: *** This message has been scanned by the InterScan for CSC-SSM and found to be free of known security risks. ***-*** port and install or restart gnome-upgrade.sh I'm now assuming that since all gnome has been wiped off the disk, that the thing to do is build/install the port directly. Starting that up, I seem to be having the same downloading difficulties. As an alternative to gnome-upgrade.sh you may want to consider using sysutils/portmanager, all you need do is run portmanager x11/gnome2 It'll do the upgrade no problem, tested it twice now myself. Interesting. The web page said specifically don't do portupgrade. I didn't say portupgrade, it is sysutils/portmanager My main problem is it's having trouble downloading, I think. I'm not sure why. We found problems on our Pix (actually the new ASA firewall) and the port the machine is on. We were getting half duplex, but those are all fixed now. Curiously, command line ftp never has a problem downloading, it's fetch (I think it's using fetch), that can't seem to download. While your problem has nothing to do with gnome-upgrade.sh, portmanager is designed to automatically pickup from where it left off, so stopping and starting isn't a problem, and it won't remove a port until its replacement is successfully built so if the port didn't fetch you won't lose anything, portmanager will just move on to the next port that can be upgraded, it is very fail safe. -Mike Note: I removed [EMAIL PROTECTED] from the return address as it is a dupe of [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: Filesystems 1TB not possible on 6.0-R (anymore?).
On 11/10/05, Xin LI [EMAIL PROTECTED] wrote: Would you please consider to try gpt instead of bsdlabel? BTW. The dmesg meesage indicates that your array is degraded :-( Is it possible to have sysinstall use gpt instead of bsdlabel, and then to boot from a gpt based array? I haven't had luck with it, but maybe that was fixed with 6.0. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic with cdrecord
On Sat, 05 Nov 2005 18:41:05 +0100 Torfinn Ingolfsen [EMAIL PROTECTED] wrote: but anything else fails. (Ok, I have tested the vommands -toc, -msinfo, -prcap, -atip, -checkdrive, -prcap) Ok, the machine now has 6.0-release / amd64 on it, and the error seems to be gone. At least none of the commands above causes a panic anymore. i have yet to test writing a cd with cdrecord. I also tried burncd, and it works, but it fails while fixating the CD, giving me a coaster. (I have read in the release notes that this is fixed in FreeBSD 6.0-release, and I am going to try 6.0 later.) I haven't tested burncd yet. -- 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: gnome-upgrade.sh
Things are running better now. I moved it to a dedicated DSL line in my lab, and it's chugging along. I see an occasional g_vfs_done message fly across. Error 16 on a read. Something like g_vfs_done: acd0[READ(offset=81920, length=2048) Error = 16 Opps, I crashed the machine. When I moved it, I unplugged the USB DVD-RW and I had mounted one of the dist discs on there. When I did a umount it paniced. My bad. acd0 would be the internal DVD drive. It seems that problem with my network was indeed the Cisco ASA box we're beta testing. We have the CSC module installed which is a stand alone linux box running trend for virus, intrusion, etc. And there is a bug in the ftp inspection. Hangs things up. Ok, since I think the network is solved, I'll take this opportunity to restart portmanager on the network. Michael C. Shultz wrote: *** This message has been scanned by the InterScan for CSC-SSM and found to be free of known security risks. ***-*** On Thursday 10 November 2005 09:42, Paul T. Root wrote: I moved the machine to a DSL line here, and am running portmanager. It seems to be working. We're going to investigate issues with this beta Cisco ASA machine. I am very interested at how things go with your upgrade, please keep me informed. Just to let you know, the current version of portmanager is 0.3.3_2 if anything goes wrong check that first portmanager -v. If any problems arise I am more than happy to work with you in solving them quickly. -Mike Michael C. Shultz wrote: *** This message has been scanned by the InterScan for CSC-SSM and found to be free of known security risks. ***-*** On Wednesday 09 November 2005 18:26, Paul Root wrote: Michael C. Shultz wrote: *** This message has been scanned by the InterScan for CSC-SSM and found to be free of known security risks. ***-*** port and install or restart gnome-upgrade.sh I'm now assuming that since all gnome has been wiped off the disk, that the thing to do is build/install the port directly. Starting that up, I seem to be having the same downloading difficulties. As an alternative to gnome-upgrade.sh you may want to consider using sysutils/portmanager, all you need do is run portmanager x11/gnome2 It'll do the upgrade no problem, tested it twice now myself. Interesting. The web page said specifically don't do portupgrade. I didn't say portupgrade, it is sysutils/portmanager My main problem is it's having trouble downloading, I think. I'm not sure why. We found problems on our Pix (actually the new ASA firewall) and the port the machine is on. We were getting half duplex, but those are all fixed now. Curiously, command line ftp never has a problem downloading, it's fetch (I think it's using fetch), that can't seem to download. While your problem has nothing to do with gnome-upgrade.sh, portmanager is designed to automatically pickup from where it left off, so stopping and starting isn't a problem, and it won't remove a port until its replacement is successfully built so if the port didn't fetch you won't lose anything, portmanager will just move on to the next port that can be upgraded, it is very fail safe. -Mike Note: I removed [EMAIL PROTECTED] from the return address as it is a dupe of [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- __ Paul T. Root /_ \ 1977 MGB / /|| \\ ||\/ || _ | || || || \ ||__// \__/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gnome-upgrade.sh
On Thursday 10 November 2005 11:32, Paul T. Root wrote: Things are running better now. I moved it to a dedicated DSL line in my lab, and it's chugging along. I see an occasional g_vfs_done message fly across. Error 16 on a read. Something like g_vfs_done: acd0[READ(offset=81920, length=2048) Error = 16 Opps, I crashed the machine. When I moved it, I unplugged the USB DVD-RW and I had mounted one of the dist discs on there. When I did a umount it paniced. My bad. acd0 would be the internal DVD drive. It seems that problem with my network was indeed the Cisco ASA box we're beta testing. We have the CSC module installed which is a stand alone linux box running trend for virus, intrusion, etc. And there is a bug in the ftp inspection. Hangs things up. Ok, since I think the network is solved, I'll take this opportunity to restart portmanager on the network. good luck :) -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Consistent 6.0-STABLE Hang
Running the Citrix ICA wfcmgr (from ports) to change settings, e.g. password, for connection to a Windows terminal server hangs FreeBSD 6.0 (as of Nov 4) quite consistently. I've tried this on one of my 6.0 systems at home and a 6.0 system here at work. I suspect it may have something to do with Linux emulation however until I dig into this more I won't know for sure. The only way to unhang the system is to press the reset switch. Cheers, Cy Schubert [EMAIL PROTECTED] Web: http://www.komquats.com and http://www.bcbodybuilder.com FreeBSD UNIX: [EMAIL PROTECTED] Web: http://www.FreeBSD.org BC Government: [EMAIL PROTECTED] Lift long enough and I believe arrogance is replaced by humility and fear by courage and selfishness by generosity and rudeness by compassion and caring. -- Dave Draper ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: loader.conf setting ignored
Sarxan Elxanzade wrote: It looks like console access is necessary. But may be someone prompt another solution. So it turns out you can set kern.geom.debugflags from loader.conf. The gvinum mirror problem I was trying to debug was causing the problem. Edits to loader.conf were only being written to the second disk, but the loader was reading the first disk during boot. After manually copying /boot over it worked fine. Just thought I would mention that for the archives. - Ben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Crashing after umounting unavailable filesystems
On 10 November 2005, Michael C. Shultz wrote: Opps, I crashed the machine. When I moved it, I unplugged the USB DVD-RW and I had mounted one of the dist discs on there. When I did a umount it paniced. My bad. That happened to me the other day too. I'd mounted a USB flash drive, unplugged the USB hub, replugged it, remounted the drive, and then of course I couldn't umount the first mount. I did a umount -f and the machine crashed instantly. Is this the sort of thing that's really hard to handle, or might it be safer one day? I don't know how serious it is to do bad things to mounted file systems, but I'm curious. Bill -- William Denton : Toronto, Canada : www.miskatonic.org : www.frbr.org ___ 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.4 - 6.0 without reinstalling. safe ?
You have an option to use the FreeBSD agp device support or nVidia's. I have no idea what criteria one might use to select between them. i'll try recompiling this evening the port and try a boot -s :) If the device is loaded from /boot/loader.conf you might need to disable that in order for the boot to single-user to work. YMMV. the upgrade was successful! tnx, jan, for the tips and the list for accurate information on this subject. overview of the 5.4-release to RELENG_6 upgrade: following the steps as described in the UPDATING document with additional disabling of '3th party' modules (see also [1] in updating) nvidia driver: comment out nvidia_load=YES in /boot/loader.conf linux emu: comment out linux_load=YES in /boot/loader.conf vmware: chmod a-x of /usr/local/etc/rc.d/rtc.sh and vmware.sh at this point i recompiled successfully the new nvidia driver. tnx everyone and esp. the freebsd team for this release! filip -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44 (0)117 3317661 http://ioctl.org/jan/ Goth isn't dead, it's just lying very still and sucking its cheeks in. -- http://filip.freeshell.org mailto:[EMAIL PROTECTED] SDF Public Access UNIX System - http://sdf.lonestar.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: i386/87208 : /dev/cuad[0/1] bad file descriptor error during
Hello!
I'm CCing this follow-up to freebsd-stable because this problem can
prevent use of RELENG_6 machines in production (mgetty is quite usual
example of such a use). This bug is a regression vs. RELENG_5/4.
My analysis shows that it isn't only dup() problem. File descriptor 0
get somehow reserved in RELENG_6, but only IF process has been started
by the init via /etc/ttys! Look at this simple program:
#include unistd.h
#include syslog.h
#include fcntl.h
#include stdio.h
#include string.h
#include stdarg.h
main()
{
int res;
while((res=open(/dev/null,O_RDONLY)) 3)
if (res == -1) syslog(LOG_ERR,open(): %m);
syslog(LOG_ERR,Started); sleep(10);
if (close(0) == -1) syslog(LOG_ERR,close(0): %m);
if (close(2) == -1) syslog(LOG_ERR,close(2): %m);
if ((res=dup(1)) == -1) syslog(LOG_ERR,dup(1): %m);
syslog(LOG_ERR,dup() gave %d\n,res);
sleep(10);
return 0;
}
One can watch the file descriptor usage in two points where program is
sleeping: first after program has opened enough files to use descriptor
#3, and second after closing descriptors #0 and #2 and copying descriptor
#1. So, when I start this program under 6.0-RELEASE in usual way (./a.out),
in first point lsof shows me the following (I'll show only plain descriptors
and omit cwd/rtd/txt information):
At first sleep:
a.out 837 root0u VCHR 0,70 0t77713 70 /dev/ttyv1
a.out 837 root1u VCHR 0,70 0t77713 70 /dev/ttyv1
a.out 837 root2u VCHR 0,70 0t77713 70 /dev/ttyv1
a.out 837 root3r VCHR 0,13 0t0 13 /dev/null
a.out 837 root4u unix 0xc1c7b9bc 0t0-0xc1bf7de8
(descriptor #4 has been created by syslog()). Program logged the following:
a.out: dup() gave 0
At the second sleep:
a.out 837 root0u VCHR 0,70 0t77713 70 /dev/ttyv1
a.out 837 root1u VCHR 0,70 0t77713 70 /dev/ttyv1
a.out 837 root3r VCHR 0,13 0t0 13 /dev/null
a.out 837 root4u unix 0xc1c7b9bc 0t0-0xc1bf7de8
So all OK in this mode: there were 3 standard files open at the beginning
(descr. 0-2), program has opened descr. 3 (and 4), closed 0 and 2
successfully, and copied 1 to 0. Now let's start this program from the
/etc/ttys:
cuad0 /root/tmp/a.out unknown on insecure
Now we have the following at the first sleep():
a.out 817 root1r VCHR 0,13 0t0 13 /dev/null
a.out 817 root2r VCHR 0,13 0t0 13 /dev/null
a.out 817 root3r VCHR 0,13 0t0 13 /dev/null
a.out 817 root4u unix 0xc1c7bde8 0t0-0xc1bf7de8
Note that open() has also skipped descr. 0! Then program tries to close it,
gives an error:
close(0): Bad file descriptor
dup() gave 2
Note that descriptor 0 isn't open: close() refuses to close it. But dup()
doesn't see it and returns descr. 2 instead. At the second sleep, we
have exactly the same open file table: descr. 0 is not in use, 1-3 point
at /dev/null. So it seems to me that open() suffers from the same problem
here as a dup(): descriptor 0 becomes reserved somehow.
Sincerely, Dmitry
--
Atlantis ISP, System Administrator
e-mail: [EMAIL PROTECTED]
nic-hdl: LYNX-RIPE
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: loader.conf setting ignored
On Thu, Nov 10, 2005 at 03:57:56PM -0500, Ben Kelly wrote: So it turns out you can set kern.geom.debugflags from loader.conf. The gvinum mirror problem I was trying to debug was causing the problem. Edits to loader.conf were only being written to the second disk, but the loader was reading the first disk during boot. After manually copying /boot over it worked fine. Just thought I would mention that for the archives. Just a tip that may help in circumstances like this. Anything that can be set from loader.conf (or device.hints for that matter) can also be set from the loader prompt: set kern.geom.debugflags=XXX ...of course in your case it looked like the values _were_ being set, but it can be handy when loader.conf is difficult or impossible to edit. Craig ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ahd0: Invalid Sequencer interrupt occurred.
On Nov 10, 2005, at 05:30 , Ricardo A. Reis wrote: Reducing the problem to the relevant pieces: ahd0: Adaptec AIC7902 Ultra320 SCSI adapter port 0x2400-0x24ff, 0x2000-0x20ff mem 0xdd20-0xdd201fff irq 32 at device 2.0 on pci3 ahd0: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs ahd1: Adaptec AIC7902 Ultra320 SCSI adapter port 0x2c00-0x2cff, 0x2800-0x28ff mem 0xdd202000-0xdd203fff irq 33 at device 2.1 on pci3 ahd1: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs [...] da0 at ahd0 bus 0 target 0 lun 0 da0: SEAGATE ST373307LC 0006 Fixed Direct Access SCSI-3 device da0: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 70007MB (143374744 512 byte sectors: 255H 63S/T 8924C) da1 at ahd0 bus 0 target 1 lun 0 da1: SEAGATE ST373307LC 0006 Fixed Direct Access SCSI-3 device da1: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 70007MB (143374744 512 byte sectors: 255H 63S/T 8924C) Trying to mount root from ufs:/dev/da0s1a Adaptec HBAs and Seagate drives have a long and intensely painful history of not working well together. Adaptec blames Seagate. Seagate blames Adaptec. Throw in the myriad of subtly different AIC controllers that are commonplace on 1U and 2U rackmount servers, and things get even more entertaining. You essentially have 3 options 1) replace the HBA -- somewhat difficult to do if it's embedded and you need the PCIX slots for something else. 2) replace the drives -- IBM/Hitachi are fine choices here. Make sure to tell whomever you purchase systems from that you'll not accept Seagate drives in the future. 3) inside the adaptec bios, drop the drives to U160 speed, making sure that *both* packetizing *and* QAS are turned OFF. You'll lose a little bit of performance (but not all that much, Seagate drives really are garbage), and get some semblance of stability. -aDe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: loader.conf setting ignored
Oh, ignore me I just read the thread from beginning and saw that you already thought of that and didn't have console access :-/ Craig ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: usbd.conf
usbd is deprecated. Please use devd. From: Petr Holub I've found that usbd on 6.0-RELEASE doesn't react on detach event properly: ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
GENERIC kernel, crashing server
hello i got a problem with my server running 6.0 sometimes it just crashes
and reboots i dont know why
this fenomena might be when there is lot of access to my ar0 i have cut all
access to it atm and havent crashed just a guess though
but here is the output of kgdb with backtrace and below you got the output
of boot -v
[EMAIL PROTECTED]kgdb kernel.debug /usr/local/var/crash/vmcore.2
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:
Undefined symbol ps_pglobal_lookup]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as i386-marcel-freebsd.
Unread portion of the kernel message buffer:
instruction pointer = 0x20:0xc08badd7
stack pointer = 0x28:0xd4496cc8
frame pointer = 0x28:0xd4496ccc
code segment = base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, IOPL = 0
current process = 30 (irq19: em0)
trap number = 30
panic: unknown/reserved trap
Uptime: 56m17s
Dumping 511 MB (2 chunks)
chunk 0: 1MB (160 pages) ... ok
chunk 1: 511MB (130800 pages) 495 479 463 447 431 415 399 383 367 351 335
319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15
#0 doadump () at pcpu.h:165
165 __asm __volatile(movl %%fs:0,%0 : =r (td));
(kgdb) backtrace
#0 doadump () at pcpu.h:165
#1 0xc069d978 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399
#2 0xc069dca6 in panic (fmt=0xc0943594 unknown/reserved trap) at
/usr/src/sys/kern/kern_shutdown.c:555
#3 0xc08c4968 in trap_fatal (frame=0xd4496c88, eva=0) at
/usr/src/sys/i386/i386/trap.c:833
#4 0xc08c43a7 in trap (frame=
{tf_fs = 8, tf_es = 40, tf_ds = 40, tf_edi = -1046961280, tf_esi = 4, tf_ebp
= -733385524, tf_isp = -733385548, tf_ebx = -1046941312, tf_edx = 0, tf_ecx
= -1046941312, tf_eax = 524870, tf_trapno = 30, tf_err = 0, tf_eip =
-1064587817, tf_cs = 32, tf_eflags = 524870, tf_esp = -1046941312, tf_ss =
-733385468}) at /usr/src/sys/i386/i386/trap.c:629
#5 0xc08b109a in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#6 0xc08badd7 in spinlock_exit () at cpufunc.h:365
#7 0xc0684a89 in ithread_loop (arg=0xc198a380) at
/usr/src/sys/kern/kern_intr.c:597
#8 0xc068387f in fork_exit (callout=0xc0684780 ithread_loop, arg=0x80246,
frame=0x80246) at /usr/src/sys/kern/kern_fork.c:789
#9 0xc08b10fc in fork_trampoline () at
/usr/src/sys/i386/i386/exception.s:208
(kgdb)
here is the output of boot -v
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 6.0-STABLE #0: Tue Nov 8 03:32:10 CET 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
Preloaded elf kernel /boot/kernel/kernel at 0xc0b55000.
Preloaded elf module /boot/kernel/acpi.ko at 0xc0b55188.
Calibrating clock(s) ... i8254 clock: 1193368 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
Timecounter i8254 frequency 1193182 Hz quality 0
Calibrating TSC clock ... TSC clock: 1400600893 Hz
CPU: AMD Athlon(tm) XP 1600+ (1400.60-MHz 686-class CPU)
Origin = AuthenticAMD Id = 0x662 Stepping = 2
Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
AMD Features=0xc0480800SYSCALL,MP,MMX+,3DNow+,3DNow
Data TLB: 32 entries, fully associative
Instruction TLB: 16 entries, fully associative
L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative
L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way
associative
L2 internal cache: 256 kbytes, 64 bytes/line, 1 lines/tag, 8-way associative
real memory = 536805376 (511 MB)
Physical memory chunk(s):
0x1000 - 0x0009, 651264 bytes (159 pages)
0x0010 - 0x003f, 3145728 bytes (768 pages)
0x00c25000 - 0x1f6b7fff, 514404352 bytes (125587 pages)
avail memory = 515964928 (492 MB)
MP Configuration Table version 1.4 found at 0xc00f1400
Table 'FACP' at 0x1fff3040
Table 'APIC' at 0x1fff6b00
MADT: Found table at 0x1fff6b00
APIC: Using the MADT enumerator.
MADT: Found CPU APIC ID 0 ACPI ID 0: enabled
ACPI APIC Table: VIA694 AWRDACPI
bios32: Found BIOS32 Service Directory header at 0xc00fb030
bios32: Entry = 0xfb4a0 (c00fb4a0) Rev = 0 Len = 1
pcibios: PCI BIOS entry at 0xf+0xb4d0
pnpbios: Found PnP BIOS data at 0xc00fbfa0
pnpbios: Entry = f:bfd0 Rev = 1.0
Other BIOS signatures found:
APIC: CPU 0 has ACPI ID 0
MADT: Found IO APIC ID 2, Interrupt 0 at 0xfec0
ioapic0: Routing external 8259A's - intpin 0
ioapic0: intpin 0 - ExtINT (edge, high)
ioapic0: intpin 1 - ISA IRQ 1 (edge, high)
ioapic0: intpin 2 - ISA IRQ 2 (edge, high)
ioapic0: intpin 3 - ISA IRQ 3 (edge, high)
ioapic0: intpin 4 - ISA
gvinum forgetting drives in 6.0R?
I'm doing some testing in 6.0, and something strange is happening: 1) uname -a FreeBSD 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 2) I build a stripe set using 'gvinum create' and the following config: drive dr3 device /dev/ad3s1 drive dr2 device /dev/ad2s1 drive dr1 device /dev/ad1s1 volume v0 plex name v0.p0 org striped 256s vol v0 sd name v0.p0.s2 drive dr3 len 613376s driveoffset 265s plex v0.p0 plexoffset 512s sd name v0.p0.s1 drive dr2 len 613376s driveoffset 265s plex v0.p0 plexoffset 256s sd name v0.p0.s0 drive dr1 len 613376s driveoffset 265s plex v0.p0 plexoffset 0s 3) After this is done, everything's okay, and 'gvinum l' looks like: 3 drives: D dr1 State: up /dev/ad1s1 A: 0/299 MB (0%) D dr2 State: up /dev/ad2s1 A: 0/299 MB (0%) D dr3 State: up /dev/ad3s1 A: 0/299 MB (0%) 1 volume: V v0State: up Plexes: 1 Size:898 MB 1 plex: P v0.p0 S State: up Subdisks: 3 Size:898 MB 3 subdisks: S v0.p0.s0 State: up D: dr1 Size:299 MB S v0.p0.s1 State: up D: dr2 Size:299 MB S v0.p0.s2 State: up D: dr3 Size:299 MB 4) gvinum saveconfig 5) Reboot 6) 'gvinum l' now looks like: 0 drives: 1 volume: V v0State: up Plexes: 0 Size: 0 B 1 plex: P v0.p0 S State: up Subdisks: 0 Size: 0 B 3 subdisks: S v0.p0.s0 State: up D: dr1 Size:299 MB S v0.p0.s1 State: up D: dr2 Size:299 MB S v0.p0.s2 State: up D: dr3 Size:299 MB Notice the lack of drives and the subsequent death of my plex and volume? Also, everything is conveniently in the up state, but there is no /dev/gvinum directory. 7) For kicks, add the following to /etc/rc.conf like I saw in an e-mail somewhere: geom_vinum_load=YES start_cmd=gvinum start 8) Reboot 9) Things still look like 6) above. Is this a bug or am I silly? Caveat: This testing is being done in qemu, but the behavior matches a physical system I have. I haven't tested other kinds of plexes yet, either. dmesg: 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 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Pentium II/Pentium II Xeon/Celeron (2064.81-MHz 686-class CPU) Origin = GenuineIntel Id = 0x633 Stepping = 3 Features=0x781a9fdFPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,PGE,CMOV,PAT,MMX,FXSR,SSE,SSE2 real memory = 134217728 (128 MB) avail memory = 121815040 (116 MB) npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface cpu0 on motherboard pcib0: Host to PCI bridge pcibus 0 on motherboard pir0: PCI Interrupt Routing Table: 6 Entries on motherboard pci0: PCI bus on pcib0 isab0: PCI-ISA bridge at device 1.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX3 WDMA2 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc000-0xc00f at device 1.1 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 pci0: display, VGA at device 2.0 (no driver attached) ed0: RealTek 8029 port 0xc100-0xc1ff irq 11 at device 3.0 on pci0 ed0: Ethernet address: 52:54:00:12:34:56 ed0: type NE2000 (16 bit) pmtimer0 on isa0 orm0: ISA Option ROM at iomem 0xc-0xc7fff on isa0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: Parallel port bus on ppc0 plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16450 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 Timecounter TSC frequency 2064806075 Hz quality 800 Timecounters tick every 1.000 msec ad0: 1000MB QEMU HARDDISK 0.7.2 at ata0-master PIO2 ad1: 300MB QEMU HARDDISK 0.7.2 at ata0-slave PIO2 ad2: 300MB QEMU HARDDISK 0.7.2 at ata1-master PIO2 ad3: 300MB QEMU HARDDISK 0.7.2 at ata1-slave PIO2 Trying to mount root from ufs:/dev/ad0s1a -- Marc Ramirez Blue Circle Software Corporation 513-688-1070 (main) 513-382-1270 (direct)
