AIC-7890 problems with kernel build
I've had this problem for the past couple of days (I went a while between updates of my kernel since I was busy installing a new disk and moving OSes around). Just after the "waiting for SCSI devices to settle" message, I'll get a number of SCB errors (which I don't have written down, unfortunately), and then eventually a panic. This is with ACPI enabled... if I don't enable ACPI, it will proceed immediately to the panic. The panic is a "Trap 12: page fault in kernel mode". with "interrupt mask: cam - SMP: XXX", and "Stopped at ahc_match_scb + 0x9d movl 0x2c(%eax), %eax" I apologize for the exceedingly lameassed manner of this bug report, I don't have serial ports enabled on this machine and don't know of a more effective means to get the details. With the kernel debugger, I get a stack trace similar to the following: ahc_match_scb(c0e7e000, c0e8e230, 0, 41, 0, 9, 1) ahc_search_qinfifo(c0e7e000, 0, 41, 0, 9, 1, 0, 1) ahc_timeout(c0e8e168, 4000, 0, 0, ) softclock(0, 18, c02b0010, 10, ) doreti_swi() I can dig up my kernel config and a "functional" dmesg as soon as I get back via the saved good kernel. For the record, this is via the onboard AIC-7890 on a Tyan Thunder/100 dual processor board running an SMP kernel. -- Brandon Hume- hume - BOFH.Halifax.NS.Ca, http://WWW.BOFH.Halifax.NS.Ca/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AIC-7890 problems with kernel build
On Mon, 4 Sep 2000, Brandon Hume wrote: Just after the "waiting for SCSI devices to settle" message, I'll get a number of SCB errors (which I don't have written down, unfortunately), and then eventually a panic. This is with ACPI enabled... if I don't enable ACPI, it will proceed immediately to the panic. Sounds similar to what I'm getting; after a boot I get a load of the following: ahc0: ahc_intr - referenced scb not valid during SELTO (31, 255) ahc1: ahc_intr - referenced scb not valid during SELTO (31, 139) followed by a panic: (probe0:ahc0:0:0:0): SCB 0x9 - timed out while idle, SEQADDR == 0xb panic: Waiting List inconsistency. SCB index == 255, yet numscbs == 20 (Being a technophobe I decided to write these down rather than dig out a breakout box to capture the serial port output!) Similar config to yours; a Tyan Thunder SMP BX with an onboard 7895 controller. I started getting this after my 29th Aug update, although this was a few days since the last working version I compiled (dmesg says the 24th so, er, I guess that's when it was) Lots of other blurb about "can't allocate register resources" for just about anything on the PCI bus, as I recall. Chris. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AIC-7890 problems with kernel build
Chris Hedley writes: On Mon, 4 Sep 2000, Brandon Hume wrote: Just after the "waiting for SCSI devices to settle" message, I'll get a number of SCB errors (which I don't have written down, unfortunately), and then eventually a panic. This is with ACPI enabled... if I don't enable ACPI, it will proceed immediately to the panic. Sounds similar to what I'm getting; after a boot I get a load of the following: I'll add a third to that. The SCB errors don't seem to depend on ACPI; they didn't happen on the update on Sept 1, but did on Sept 2. Similar config to yours; a Tyan Thunder SMP BX with an onboard 7895 controller. I started getting this after my 29th Aug update, although this was a few days since the last working version I compiled (dmesg says the 24th so, er, I guess that's when it was) Not quite the same. I've got a SuperMicro SMP Xeon system with an onboard 7890. mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AIC-7890 problems with kernel build
On Mon, 4 Sep 2000, Brandon Hume wrote: Sounds similar to what I'm getting; after a boot I get a load of the following: ahc0: ahc_intr - referenced scb not valid during SELTO (31, 255) That's what I get... although I get SELTO (31, 0) Similar config to yours; a Tyan Thunder SMP BX with an onboard 7895 Mine's a GX, with a 7895 also (not 7890, oops...) controller. I started getting this after my 29th Aug update, although this was a few days since the last working version I compiled (dmesg says the 24th so, er, I guess that's when it was) My working kernel was built 1 PM ADT on the 26th, so there's a slightly narrower window. Lots of other blurb about "can't allocate register resources" for just about anything on the PCI bus, as I recall. I think that's a double-probe problem mentioned on the commit list. Dunno if it would be related. Here's the kernel config and functional-dmesg I promised. dmesg: --- Copyright (c) 1992-2000 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.0-CURRENT #0: Sat Aug 26 13:00:17 ADT 2000 [EMAIL PROTECTED]:/build/src/sys/compile/JASHUGAN Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,XMM real memory = 134086656 (130944K bytes) avail memory = 126570496 (123604K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "JASHUGAN" at 0xc03e1000. Pentium Pro MTRR support enabled md0: Malloc disk apm0: APM BIOS on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443GX host to PCI bridge on motherboard pci0: PCI bus on pcib0 pci0: Intel 82443GX host to PCI bridge at 0.0 pcib2: Intel 82443GX (440 GX) PCI-PCI (AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib2 pci1: Matrox MGA G400 AGP graphics accelerator at 0.0 irq 16 isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0xffa0-0xffaf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xef80-0xef9f irq 19 at device 7.2 on pci0 usb0: Intel 82371AB/EB (PIIX4) 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 ugen0: Logitech, Inc. Camera, rev 1.00/1.00, addr 2 uhub1: Texas Instruments UT-USB41 hub, class 9/0, rev 1.10/1.10, addr 3 uhub1: 4 ports with 4 removable, bus powered ukbd0: Sun Microsystems Type 6 USB, rev 1.00/1.01, addr 4, iclass 3/1 kbd1 at ukbd0 ums0: Logitech USB-PS/2 Mouse, rev 1.00/1.10, addr 5, iclass 3/1 ums0: 3 buttons and Z dir. Timecounter "PIIX" frequency 3579545 Hz pci0: Intel 82371AB Power management controller at 7.3 pcib3: DEC 21152 PCI-PCI bridge at device 16.0 on pci0 pci2: PCI bus on pcib3 pci2: 3Dfx Voodoo 2 graphics accelerator at 4.0 pci2: unknown card (vendor=0x11d1, dev=0x01f7) at 5.0 irq 17 fxp0: Intel Pro 10/100B/100+ Ethernet port 0xef40-0xef5f mem 0xfea0-0xfeaf,0xfd2ff000-0xfd2f irq 19 at device 17.0 on pci0 fxp0: Ethernet address 00:e0:81:10:24:79 ahc0: Adaptec aic7895 Ultra SCSI adapter port 0xe400-0xe4ff mem 0xfebfe000-0xfebfefff irq 16 at device 18.0 on pci0 ahc0: aic7895 Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: Adaptec aic7895 Ultra SCSI adapter port 0xe800-0xe8ff mem 0xfebff000-0xfebf irq 16 at device 18.1 on pci0 ahc1: aic7895 Wide Channel B, SCSI Id=7, 32/255 SCBs pcm0: Creative EMU10K1 port 0xef20-0xef3f irq 16 at device 19.0 on pci0 pcib1: Intel 82443GX host to AGP bridge on motherboard pci3: PCI bus on pcib1 isa0: too many memory ranges fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 unknown: PNP0303 can't assign resources unknown: PNP0700 can't assign resources APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 IPsec: Initialized Security Association Processing. IP Filter: v3.4.9 initialized. Default = pass all, Logging = enabled SMP: AP CPU #1 Launched! acd0: DVD-ROM CREATIVEDVD-ROM DVD2240E 03/18/98 at ata0-master using WDMA2 Waiting 7 seconds
Re: AIC-7890 problems with kernel build
Hi, And, of course, the kernel config... a fair amount of crap still not trimmed out, but the only difference between this config and the one used to build the functional kernel is apm commented out and ACPI added, which I've already tried reversing without much difference. All I can say is that acpi is initilized after pcib and its children are attached so I don't think ACPI code affects PCI stuff... # Power management support (see LINT for more options) #device apm deviceacpi Could you disable acpi and try again to make the problem clearer? Without `device acpi' line in your kernel config file, any ACPI code isn't compiled in your kernel. Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AIC-7890 problems with kernel build
Could you disable acpi and try again to make the problem clearer? Without `device acpi' line in your kernel config file, any ACPI code As I mentioned, I've already done so. I know ACPI isn't causing the panic, but it does seem to change the BEHAVIOR of the panic. (I get the errors mentioned by the previous poster with ACPI, while without I proceed directly to the panic). -- Brandon Hume- hume - BOFH.Halifax.NS.Ca, http://WWW.BOFH.Halifax.NS.Ca/ - Solaris Snob and general NOCMonkey To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AIC-7890 problems with kernel build
Mitsuru IWASAKI writes: All I can say is that acpi is initilized after pcib and its children are attached so I don't think ACPI code affects PCI stuff... # Power management support (see LINT for more options) #device apm device acpi Could you disable acpi and try again to make the problem clearer? Without `device acpi' line in your kernel config file, any ACPI code isn't compiled in your kernel. That was the first thing I tried when mine failed. It didn't make any difference - I saw the same failure (the page fault, not the SCB errors). FWIW, my working kernel was built August 26, 10:05 GMT. mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AIC-7890 problems with kernel build
Could you disable acpi and try again to make the problem clearer? Without `device acpi' line in your kernel config file, any ACPI code isn't compiled in your kernel. That was the first thing I tried when mine failed. It didn't make any difference - I saw the same failure (the page fault, not the SCB errors). Ah, I haven't read previous mails. I'm sorry about that. # Now I can go to my bed :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
