From owner-freebsd-bugs@FreeBSD.ORG Thu Jan 22 11:43:01 2004 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D37D16A4CE for ; Thu, 22 Jan 2004 11:43:01 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A241243D64 for ; Thu, 22 Jan 2004 11:40:05 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i0MJe5FR019558 for ; Thu, 22 Jan 2004 11:40:05 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i0MJe5cV019557; Thu, 22 Jan 2004 11:40:05 -0800 (PST) (envelope-from gnats) Resent-Date: Thu, 22 Jan 2004 11:40:05 -0800 (PST) Resent-Message-Id: <200401221940.i0MJe5cV019557@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A7EB16A4CF for ; Thu, 22 Jan 2004 11:36:42 -0800 (PST) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D4E043D3F for ; Thu, 22 Jan 2004 11:36:36 -0800 (PST) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.12.10/8.12.10) with ESMTP id i0MJaadL037051 for ; Thu, 22 Jan 2004 11:36:36 -0800 (PST) (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.12.10/8.12.10/Submit) id i0MJaZEf037050; Thu, 22 Jan 2004 11:36:35 -0800 (PST) (envelope-from nobody) Message-Id: <200401221936.i0MJaZEf037050@www.freebsd.org> Date: Thu, 22 Jan 2004 11:36:35 -0800 (PST) From: "Pablo L. R. Santos & Mario Sergio Fujikawa Ferreira" To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.0 Subject: kern/61746: System locks up on boot if both apic option and sio device are enabled in the kernel X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2004 19:43:01 -0000 >Number: 61746 >Category: kern >Synopsis: System locks up on boot if both apic option and sio device are enabled in the kernel >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 22 11:40:05 PST 2004 >Closed-Date: >Last-Modified: >Originator: Pablo L. R. Santos & Mario Sergio Fujikawa Ferreira >Release: FreeBSD 5.2-CURRENT i386 >Organization: >Environment: FreeBSD regulus.linf.cic.unb.br 4.9-STABLE FreeBSD 4.9-STABLE #6: Thu Jan 8 08:35:19 BRST 2004 root@regulus.linf.cic.unb.br:/usr/src/sys/compile/REGULUS i386 Running on an IBM xSeries 235 with 2 Xeon 2.9Ghz processors, LSI Logic 1030 SCSI Controller. Further details and the dmesg output are given below. >Description: System would lockup on boot and not even install unless we used "safe mode" option on beastie menu. We were trying the 5.2-RELEASE cd set. After reading both the -CURRENT lists and the 5.2-RELEASE ERRATA (and due to "safe mode" working), we assumed our trouble could be related to either apic or ACPI. Therefore, we disabled both when we compiled our first kernel. This was not satisfatory since disabling apic means no smp. I then compiled a stripped down kernel with the bare bones required for running this system and enabled apic: no lockup. I was intrigued. It could be either a "false" positive (no problem ONLY this time) or that an specific device giving trouble was removed. I was considering the 2nd option several boots with no problems later. We began with a GENERIC kernel and then disabled a device at a time PER boot trying to pin point the said device. Several hours later: we found the culprit. If both apic option and sio device were enabled, the system would lockup at boot time right after the SCSI 15 seconds delay. We had no ACPI yet but we got smp back. We then proceeded to CVSup update the system to latest -CURRENT (2003-01-21). Same behavior: locks up with apic+sio, does not lockup with apic without sio. Enabling ACPI only meant a lockup during boot so we assumed it would not be used this time. Later, we needed to hardwire the device identification for our SCSI drives. We wanted the 0:0:0 device to be da0, 0:1:0 to be da1 and so on. We wrote a kernel hints file for that. Compiled kernel, installed it, rebooted the system. Worked like a charm. For some reason, we enabled ACPI on one of the reboots. Now, it worked. ;) We worked but ACPI was not working "right". The system would not lockup but the power down button would not power down the machine. If you pressed power down, nothing would happend but ctrl-alt-del would power down the box. Weird, huh? If you pressed ctrl-alt-del without previously trying the power down button, the machine would reboot normally. Well, we decided to reinstall the system and try reproducing our results with a fresh 5.2-RELEASE. Well, we reproduced them exactly: 1) apic would mean a system lockup 2) apic would work after we disabled the sio device 3) ACPI would work after we hardwired the SCSI disks 4) power down button would "work" as aforementioned 5) same symptons after CVSup update to -CURRENT We are supplying some system information below. Please, ask if you need more. We are new to 5.x branch and we are not aware of possible side effects of using a hints file. Therefore, do not refrain yourselves from enlighten us even about the most basic things. Finally we detected a last bug, possibly related to the aforementioned problems; during system initialization, typing any key before the keyboard is set up [1] causes a reboot when that stage is reached. ps: For those of you having problems with scsi disks starting slow at 3.300 MB/s on mpt controllers, issuing a "camcontrol reset 0" will make all of the disks go to their correct top speed. Regards, [1] For the purpose of this PR, we consider the point at which keyboard is set up to be the moment the system presents the following lines at the console: atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 --------------- /var/run/dmesg.boot ------------- Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.2-CURRENT #7: Wed Jan 21 16:32:33 GMT 2004 root@rhea.linf.cic.unb.br:/usr/src/sys/i386/compile/RHEA Preloaded elf kernel "/boot/kernel/kernel" at 0xc0716000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc07161f4. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.90-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 2147385344 (2047 MB) avail memory = 2100158464 (2002 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic2 irqs 32-47 on motherboard ioapic1 irqs 16-31 on motherboard ioapic0 irqs 0-15 on motherboard Pentium Pro MTRR support enabled npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard pcibios: BIOS version 2.10 acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x488-0x48b on acpi0 acpi_cpu0: on acpi0 acpi_cpu1: on acpi0 acpi_cpu2: on acpi0 acpi_cpu3: on acpi0 pcib0: on acpi0 pci0: on pcib0 pcib0: slot 15 INTA is routed to irq 3 pci0: at device 9.0 (no driver attached) atapci0: port 0x700-0x70f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: simplex device, DMA on primary only ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] pci0: at device 15.2 (no driver attached) isab0: at device 15.3 on pci0 isa0: on isab0 pcib1: on acpi0 pci2: on pcib1 bge0: mem 0xfbff0000-0xfbffffff irq 29 at device 8.0 on pci2 bge0: Ethernet address: 00:09:6b:a5:75:6a miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto pcib2: on acpi0 pci5: on pcib2 mpt0: port 0x2300-0x23ff mem 0xf9fe0000-0xf9feffff,0xf9ff0000-0xf9ffffff irq 27 at device 7.0 on pci5 mpt1: port 0x2400-0x24ff mem 0xf9fc0000-0xf9fcffff,0xf9fd0000-0xf9fdffff irq 28 at device 7.1 on pci5 pcib3: on acpi0 pci7: on pcib3 pcib4: on acpi0 pci9: on pcib4 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 atkbd: unable to set the command byte. kbd0 at atkbd0 psm0: unable to set the command byte. fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 pmtimer0 on isa0 orm0: