From owner-freebsd-current@FreeBSD.ORG Sun Nov 16 14:34:33 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28C1A16A4CE for ; Sun, 16 Nov 2003 14:34:33 -0800 (PST) Received: from maeko.hayai.de (maeko.hayai.de [217.172.178.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC7F843FB1 for ; Sun, 16 Nov 2003 14:34:31 -0800 (PST) (envelope-from mail@maeko.hayai.de) Received: from maeko.hayai.de (localhost [127.0.0.1]) by maeko.hayai.de (8.12.7/8.12.7) with ESMTP id hAGMYTpP008685 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Sun, 16 Nov 2003 23:34:30 +0100 Received: (from mail@localhost) by maeko.hayai.de (8.12.7/8.12.7/Submit) id hAGMYSxY008684 for current@freebsd.org; Sun, 16 Nov 2003 23:34:28 +0100 Date: Sun, 16 Nov 2003 23:34:28 +0100 From: Marco Wertejuk To: current@freebsd.org Message-ID: <20031116223428.GA8570@maeko.hayai.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.4i Subject: CF cards / ATAng / interrupt code still broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Nov 2003 22:34:33 -0000 Hello, as reproducable seen on my IBM Thinkpad, current as of some days ago has problems to boot with my 128MB noname CF card inserted. The panic output is very similar the problem Alex Dupre reported in mid of september, but Sorens patch which should be tried to get this stuff fixed but the patch does not help. These messages get logged while booting verbose: (... beginning removed because it's probably not interesting) pccard0: CIS version PCCARD 2.0 or 2.1 pccard0: CIS info: CF, 128MB, pccard0: Manufacturer code 0xa, product 0x0 pccard0: function 0: fixed disk, ccr addr 200 mask f pccard0: function 0, config table entry 0: memory card; irq mask 0; memspace 0-7ff; mwait_required rdybsy_active powerdown pccard0: function 0, config table entry 1: I/O card; irq mask ffff; iomask 4, iospace 0-f; memspace 0-7ff; rdybsy_active io8 io16 irqshare irqpulse irqlevel powerdown pccard0: function 0, config table entry 2: I/O card; irq mask 4000; iomask a, iospace 1f0-1f7 3f6-3f7; memspace 0-7ff; rdybsy_active io8 io16 irqshare irqpulse irqlevel powerdown pccard0: function 0, config table entry 3: I/O card; irq mask 4000; iomask a, iospace 170-177 376-377; memspace 0-7ff; rdybsy_active io8 io16 irqshare irqpulse irqlevel powerdown pccard0: Allocation failed for cfe 0 ata2: at port 0x100-0x10f irq 11 function 0 config 1 on pccard0 ata2: reset tp1 mask=01 ostat0=50 ostat1=b7 ata2-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata2: reset tp2 mask=01 stat0=50 stat1=00 devices=0x1 ata2: [MPSAFE] ata2: spurious interrupt - status=0x50 error=0x01 ata0-master: pio=0x0c wdma=0x22 udma=0x45 cable=80pin ata0-master: setting PIO4 on Intel PIIX4 chip ata0-master: setting UDMA33 on Intel PIIX4 chip GEOM: create disk ad0 dp=0xc2972b60 ad0: ATA-5 disk at ata0-master ad0: 57231MB (117210240 sectors), 116280 C, 16 H, 63 S, 512 B ad0: 16 secs/int, 1 depth queue, UDMA33 GEOM: new disk ad0 ata2-master: pio=0x08 wdma=0xffffffff udma=0xffffffff cable=40pin ad4: FAILURE - SETFEATURES status=51 error=4 ad4: FAILURE - SETFEATURES status=51 error=4 GEOM: create disk ad4 dp=0xc297a260 ad4: <^A/.65> ATA-0 disk at ata2-master Fatal trap 18: integer divide fault while in kernel mode instruction pointer = 0x8:0xc06650cb stack pointer = 0x10:0xc0821c2c frame pointer = 0x10:0xc0821cac code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) kernel: type 18 trap, code=0 Stopped at __qdivrem+0x3b: divl %ecx,%eax db> trace __qdivrem(0,0,0,0,0) at __qdivrem+0x3b __udivdi3(0,0,0,0,0) at __udivdi3+0x2e ad_print(c297a200,c297a260,1,0,0,0,f,c2a0a400,0,0) at ad_print+0xbd ad_attach(c2a0a4a4,2,c1292040,c06d1650,c0821d80) at ad_attach+0x40b ata_boot_attach(0,826000,c0821d80,c0504e2a,0) at ata_boot_attach+0x47 run_interrupt_driven_config_hooks(0,81e000,81ec00,81e000,0) at run_interrupt_driven_config_hooks+0x2b mi_startup() at mi_startup+0xb5 begin() at begin+0x2c db> If I insert the card after the system is up and running the panic does not appear, probably because ATAng does not get the information about a newly inserted drive? At least atacontrol list does not display any drives: desire:~>sudo atacontrol list ATA channel 0: Master: ad0 ATA/ATAPI rev 5 Slave: no device present ATA channel 1: Master: no device present Slave: no device present ATA channel 2: Master: no device present Slave: no device present If there are further patches available I would like to test them in order to use my CF card again ;) -- Mit freundlichen Gruessen, Marco Wertejuk - mwcis.com Consulting & Internet Solutions