Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262349AbTKEAH4 (ORCPT ); Tue, 4 Nov 2003 19:07:56 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262425AbTKEAHz (ORCPT ); Tue, 4 Nov 2003 19:07:55 -0500 Received: from cherryhinton.org.uk ([194.106.52.201]:2368 "EHLO ivimey.org") by vger.kernel.org with ESMTP id S262349AbTKEAHx (ORCPT ); Tue, 4 Nov 2003 19:07:53 -0500 Message-Id: <5.2.0.9.0.20031104234330.02451b70@mailhost.ivimey.org> X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Wed, 05 Nov 2003 00:07:42 +0000 To: linux-kernel@vger.kernel.org From: Ruth Ivimey-Cook Subject: 2.6.0-test9 SATA and 1394 problems Cc: Ben Collins , Bartlomiej Zolnierkiewicz , Jeff Garzik Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.1 (/) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3471 Lines: 83 Folks, I have been running 2.6.0-t9 on an Asus A7V600 VIA VT600-based MB for a few days now. All seems relatively stable, which is good. A few issues to report, though, the most serious of which is that my SATA controller (VIA 8237 Southbridge) is only detected properly when the machine is fully power-cycled (that is, plug out the back, not just soft-off). When that is done, all seems well and the drives run fine. If you reboot the machine without a full power-cycle, the SATA controller is detected but no drives are found. Drives are new Seagate 7200.7 SATA 120Gig. I've tried disabling acpi, setting pci=noacpi and setting pci=usepirqmask as suggested in the acpi startup messages, but none of this helped. The BIOS has never reported the existence of the SATA drives on bootup as it does for PATA drives. I have updated the BIOS to the latest release version (1005). I should always get this: VIA8237SATA: IDE controller at PCI slot 0000:00:0f.0 VIA8237SATA: chipset revision 128 VIA8237SATA: 100% native mode on irq 20 ide4: BM-DMA at 0x9000-0x9007, BIOS settings: hdi:pio, hdj:pio ide5: BM-DMA at 0x9008-0x900f, BIOS settings: hdk:pio, hdl:pio hdi: ST3120026AS, ATA DISK drive ide4 at 0xa400-0xa407,0xa002 on irq 20 hdk: ST3120026AS, ATA DISK drive ide5 at 0x9800-0x9807,0x9402 on irq 20 but for a failed boot I just get this: VIA8237SATA: IDE controller at PCI slot 0000:00:0f.0 VIA8237SATA: chipset revision 128 VIA8237SATA: 100% native mode on irq 20 ide4: BM-DMA at 0x9000-0x9007, BIOS settings: hdi:pio, hdj:pio ide5: BM-DMA at 0x9008-0x900f, BIOS settings: hdk:pio, hdl:pio Why, btw, are two drives allocated when SATA is limited to one drive per interface? Is it just historical? I don't know if this is a "big thing" or not, but I also get this stack dump when the ohci1394 module is loaded. or when the kernel initialises that code if built-in: ohci1394: $Rev: 1045 $ Ben Collins ohci1394_0: Unexpected PCI resource length of 1000! ohci1394_0: OHCI-1394 1.0 (PCI): IRQ=[19] MMIO=[f1000000-f10007ff] Max Packet=[1024] Debug: sleeping function called from invalid context at mm/slab.c:1856 in_atomic():1, irqs_disabled():0 Call Trace: [] __might_sleep+0xab/0xf0 [] __kmalloc+0x89/0x90 [] hpsb_create_hostinfo+0x5e/0xe0 [ieee1394] [] nodemgr_add_host+0x24/0x130 [ieee1394] [] ohci_initialize+0x210/0x220 [ohci1394] [] highlevel_add_host+0x74/0x80 [ieee1394] [] hpsb_add_host+0x6d/0xa0 [ieee1394] [] ohci1394_pci_probe+0x482/0x590 [ohci1394] [] ohci_irq_handler+0x0/0x7b0 [ohci1394] [] pci_device_probe_static+0x4b/0x60 [] __pci_device_probe+0x36/0x50 [] pci_device_probe+0x2c/0x50 [] bus_match+0x3d/0x70 [] driver_attach+0x5a/0x90 [] bus_add_driver+0x9b/0xb0 [] driver_register+0x31/0x40 [] pci_register_driver+0x5b/0x80 [] ohci1394_init+0x15/0x3c [ohci1394] [] sys_init_module+0x14a/0x2a0 [] sysenter_past_esp+0x52/0x71 ieee1394: Host added: ID:BUS[0-00:1023] GUID[00c0d00001f79969] Regards, Ruth - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/