Adaptec 2120S delays boot
Hello, I have a problem with server with Adaptec SCSI RAID 2120S controller. 5.4-RELEASE was installed. GENERIC kernel boots with long delay (about 10 minutes), printing following messages: aac0: Error 5 sending GetDeviceProbeInfo command aac0: Error 5 sending GetDeviceProbeInfo command aac0: Error 5 sending GetDeviceProbeInfo command aac0: Error 5 sending GetDeviceProbeInfo command aac0: Error 5 sending GetDeviceProbeInfo command ... Is somebody knows how to fix this ? dmesg boot 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 5.4-RELEASE #0: Sun May 8 10:21:06 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC ACPI APIC Table: A M I OEMAPIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.00GHz (2800.11-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 real memory = 2147352576 (2047 MB) avail memory = 2095861760 (1998 MB) ioapic1: Changing APIC ID to 10 ioapic1: WARNING: intbase 72 != expected base 24 ioapic2: Changing APIC ID to 8 ioapic2: WARNING: intbase 24 != expected base 96 ioapic3: Changing APIC ID to 9 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic2 Version 2.0 irqs 24-47 on motherboard ioapic3 Version 2.0 irqs 48-71 on motherboard ioapic1 Version 2.0 irqs 72-95 on motherboard npx0: math processor on motherboard npx0: INT 16 interface acpi0: A M I OEMXSDT on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 cpu0: ACPI CPU on acpi0 acpi_throttle0: ACPI CPU Throttling on cpu0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge irq 16 at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 0.0 on pci1 pci3: ACPI PCI bus on pcib2 aac0: Adaptec SCSI RAID 2120S mem 0xf800-0xfbff irq 24 at device 1.0 on pci3 aac0: Unknown processor 100MHz, 48MB cache memory, optional battery not installed aac0: Kernel 4.2-0, Build 7349, S/N c0b92b aac0: Supported Options=31d7eCLUSTERS,WCACHE,DATA64,HOSTTIME,RAID50,WINDOW4GB,SOFTERR,SGMAP64,ALARM,NONDASD aacp0: SCSI Passthrough Bus on aac0 pcib3: ACPI PCI-PCI bridge at device 0.2 on pci1 pci2: ACPI PCI bus on pcib3 pcib4: ACPI PCI-PCI bridge irq 16 at device 3.0 on pci0 pci4: ACPI PCI bus on pcib4 pcib5: ACPI PCI-PCI bridge at device 28.0 on pci0 pci5: ACPI PCI bus on pcib5 em0: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 port 0xcc00-0xcc3f mem 0xfc9e-0xfc9f irq 74 at device 1.0 on pci5 em0: Ethernet address: 00:30:48:83:67:be em0: Speed:N/A Duplex:N/A em1: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 port 0xc800-0xc83f mem 0xfc9a-0xfc9b irq 75 at device 2.0 on pci5 em1: Ethernet address: 00:30:48:83:67:bf em1: Speed:N/A Duplex:N/A uhci0: UHCI (generic) USB controller port 0xe800-0xe81f irq 16 at device 29.0 on pci0 usb0: UHCI (generic) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: UHCI (generic) USB controller port 0xec00-0xec1f irq 19 at device 29.1 on pci0 usb1: UHCI (generic) USB controller on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: base peripheral at device 29.4 (no driver attached) pci0: base peripheral, interrupt controller at device 29.5 (no driver attached) pci0: serial bus, USB at device 29.7 (no driver attached) pcib6: ACPI PCI-PCI bridge at device 30.0 on pci0 pci6: ACPI PCI bus on pcib6 pci6: display, VGA at device 2.0 (no driver attached) isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel 6300ESB UDMA100 controller port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: serial bus, SMBus at device 31.3 (no driver attached) acpi_button0: Power Button on acpi0 acpi_button1: Sleep Button on acpi0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: 16550A-compatible COM port port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc0: floppy drive controller (FDE) port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fd0: 1440-KB 3.5 drive on fdc0 drive 0 orm0: ISA Option ROMs at iomem 0xcd800-0xce7ff,0xcc800-0xcd7ff,0xc8000-0xcc7ff,0xc-0xc7fff on isa0 pmtimer0 on isa0 atkbdc0: Keyboard controller (i8042) at
Re: weird kernel panics
Hi Craig! On Tue, 16 Jul 2002, Craig Boston wrote: On Tue, 2002-07-16 at 13:41, Andrey Lakhno wrote: Do you have unitialized vlans ? E.g.: vlan1: flags=0 mtu 1500 ether 00:00:00:00:00:00 vlan: 0 parent interface: none I did back on 4.5 (4 vlans statically in the kernel I think). When I upgraded to 4.6, they became dynamic so I only have vlan0 now. Actually, that particular upgrade bit me because now cloned_interfaces=vlan0 in rc.conf is needed (that really should be in UPDATING, IMHO). So the first boot didn't work :( I haven't tried to see if it's still happened now that they're gone -- intentionally panicking a production box isn't very high on my list of things to do :) Seems that panics caused by disabling multicast on vlan interface. -- Andrey Lakhno, land-ripe To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
/root permissions after installworld
Hi ! Why "make installworld" changes /root permissions to 755 ? It is insecure to have /root directory world readable. -- Best regards, Andrey To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
3.1 - 4-S via NFS
Hi ! I have two boxes running FreeBSD 3.1-RELEASE and 4.X-STABLE. I want to build world on 4.X system and then install it over NFS to 3.1 system. Is there any pitfalls in this process ? Caveats ? -- Best regards, Andrey To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: kernel panics
Hi Alfred!
On Wed, 13 Dec 2000, Alfred Perlstein wrote:
* Andrey Lakhno [EMAIL PROTECTED] [001213 02:31] wrote:
Hi !
I have FreeBSD 4.x-STABLE box.
Hardware configuration: motherboard Intel D815EEA (i815 chipset) with
integrated Intel EtherExpress Pro/100+, CPU Celeron 500MHz, RAM 128Mb,
HDD IDE Seagate Baracuda ST320420A.
It randomly crashes. Kernel panics with following diagnostics:
[snip]
Please see:
http://www.freebsd.org/handbook/kerneldebug.html
Ok. I'v built a kernel with debug turning on. While crashing the kernel created
crash dumps which i tried to gdb.
Several files attached to this letter.
debug.log - output from gdb
After removing SOFTUPDATES from kernel configuration system keeps crashing.
dmesg.log - dmesg output
kernel.conf - kernel configuration
debug1.log - gdb output after removing SOFTUPDATES
--
Best regards,
Andrey
GNU gdb 4.18
Copyright 1998 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-unknown-freebsd".
(kgdb) symbol-file kernel.debug
Reading symbols from kernel.debug...done.
(kgdb) exec-file /var/crash/kernel.0
(kgdb) core-file /var/crash/vmcore.0
IdlePTD 2703360
initial pcb at 21fbe0
panicstr: page fault
panic messages:
---
Fatal trap 10: trace trap while in kernel mode
instruction pointer = 0x8:0xc01d2cd6
stack pointer = 0x10:0xc020593c
frame pointer = 0x10:0x0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, IOPL = 0
current process = Idle
interrupt mask = none
trap number = 10
panic: trace trap
syncing disks...
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x30
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc018a120
stack pointer = 0x10:0xc0205790
frame pointer = 0x10:0xc0205794
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = Idle
interrupt mask = bio
trap number = 12
panic: page fault
Uptime: 54m42s
dumping to dev #ad/0x20001, offset 794321
dump ata0: resetting devices .. done
126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106
105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79
78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50
49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21
20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
---
#0 dumpsys () at ../../kern/kern_shutdown.c:469
469 if (dumping++) {
(kgdb) backtrace
#0 dumpsys () at ../../kern/kern_shutdown.c:469
#1 0xc012debb in boot (howto=260) at ../../kern/kern_shutdown.c:309
#2 0xc012e238 in poweroff_wait (junk=0xc01fdbaf, howto=0) at
../../kern/kern_shutdown.c:556
#3 0xc01d3be9 in trap_fatal (frame=0xc0205750, eva=48) at ../../i386/i386/trap.c:951
#4 0xc01d38c1 in trap_pfault (frame=0xc0205750, usermode=0, eva=48) at
../../i386/i386/trap.c:844
#5 0xc01d347b in trap (frame={tf_fs = -1071644656, tf_es = -1072562160, tf_ds =
-1057095664,
tf_edi = 0, tf_esi = 0, tf_ebp = -1071622252, tf_isp = -1071622276, tf_ebx =
-1071568452,
tf_edx = 6864896, tf_ecx = -1057959923, tf_eax = 0, tf_trapno = 12, tf_err = 0,
tf_eip = -1072127712, tf_cs = 8, tf_eflags = 66054, tf_esp = -1015089312,
tf_ss = -107168}) at ../../i386/i386/trap.c:443
#6 0xc018a120 in acquire_lock (lk=0xc02129bc) at ../../ufs/ffs/ffs_softdep.c:267
#7 0xc018f298 in softdep_count_dependencies (bp=0xc37ef760, wantcount=0)
at ../../ufs/ffs/ffs_softdep.c:4525
#8 0xc0192444 in ffs_fsync (ap=0xc0205808) at ../../ufs/ffs/ffs_vnops.c:168
at vnode_if.h:537
#10 0xc015b7b3 in sync (p=0xc0232260, uap=0x0) at ../../kern/vfs_syscalls.c:545
#11 0xc012dc96 in boot (howto=256) at ../../kern/kern_shutdown.c:233
#12 0xc012e238 in poweroff_wait (junk=0xc01fdbba, howto=0) at
../../kern/kern_shutdown.c:556
#13 0xc01d3be9 in trap_fatal (frame=0xc02058fc, eva=0) at ../../i386/i386/trap.c:951
#14 0xc01d35cb in trap (frame={tf_fs = 16, tf_es = -1071513584, tf_ds = -65520, tf_edi
= -1,
tf_esi = 0, tf_ebp = 0, tf_isp = -1071621848, tf_ebx = 0, tf_edx = 23088,
tf_ecx = -1071447498, tf_eax = 0, tf_trapno = 10, tf_err = 0, tf_eip =
-1071829802,
tf_cs = 8, tf_eflags = 582, tf_esp = -1071829807, tf_ss = 14}) at
../../i386/i386/trap.c:613
(kgdb) where
#0 dumpsys () at ../
Re: kernel panics
Hi Brian! On Fri, 15 Dec 2000, Brian Dean wrote: On Fri, Dec 15, 2000 at 10:07:43AM +0200, Andrey Lakhno wrote: FreeBSD host.domain 4.2-RELEASE FreeBSD 4.2-RELEASE #3: Thu Dec 14 10:57:42 EET 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/KERN i386 Ok, thanks. We still need the info that Alfred asked you about. For that, please see: http://www.freebsd.org/handbook/kerneldebug.html If you can get us a crash dump, that would be great. A traceback would be helpful, but a crash dump would be even better. Ok. I have crash dump in my /var/crash directory. I even try to use gdb as described in handbook. But I'm unfamiliar with kernel intenals. Could you help me to track the problem ? -- Best regards, Andrey To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
recent ports on 2.2.8-R
Hi ! What i need to do to install programs from ports collection on my FreeBSD 2.2.8-RELEASE box ? Ports collection are fresh. Just cvsupped. Is there any caveats ? -- Best regards, Andrey To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
3.x - 4.x and disklabel
Hi ! I'v just cvsupped from 3.X-Stable to 4.1-Stable. make world was successful. Need I change my disk label using /sbin/disklabel ? if 'yes' what command issue ? -- Best regards, Andrey To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 3.x - 4.x and disklabel
Hi Kent! On Wed, 09 Aug 2000, Kent Stewart wrote: Andrey Lakhno wrote: Hi ! I'v just cvsupped from 3.X-Stable to 4.1-Stable. make world was successful. Need I change my disk label using /sbin/disklabel ? if 'yes' what command issue ? What I remember is seeing the boot info replaced automatically. You didn't say anything about doing an appropriate buildkernel and installkernel. If you make it through that sequence in /usr/src/UPDATING, I think you will find everything has been updated. Yes, i did it. But while booting I see this messages: FreeBSD/i386 BOOT Default: 0:wd(0,a)/boot/loader boot: In FreeBSD-4.X wd driver have been changed to ad. But this message says that old wd device still in use. -- Best regards, Andrey To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
