From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pat LaVarre Subject: IRQ re-disabled when SATAPI via CONFIG_BLK_DEV_IDE_SATA Date: 17 Aug 2004 14:27:49 -0600 Sender: linux-ide-owner@vger.kernel.org Message-ID: <1092774469.4599.4.camel@patlinux.iomegacorp.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from email-out2.iomega.com ([147.178.1.83]:11440 "EHLO email.iomega.com") by vger.kernel.org with ESMTP id S268416AbUHQU27 (ORCPT ); Tue, 17 Aug 2004 16:28:59 -0400 List-Id: linux-ide@vger.kernel.org To: Jeff Garzik Cc: linux-ide@vger.kernel.org Jeff G: By the way, I see the following dmesg repeat often, like once per open of the device, if I connect SATAPI in 2.6.8.1 via CONFIG_BLK_DEV_IDE_SATA. kernel: irq 18: nobody cared! kernel: [] __report_bad_irq+0x2a/0x8b kernel: [] note_interrupt+0x6f/0x9f kernel: [] do_IRQ+0x1d4/0x226 kernel: [] default_idle+0x0/0x2d kernel: [] common_interrupt+0x18/0x20 kernel: [] default_idle+0x0/0x2d kernel: [] default_idle+0x2a/0x2d kernel: [] cpu_idle+0x37/0x40 kernel: [] start_kernel+0x1b0/0x201 kernel: [] unknown_bootoption+0x0/0x16f kernel: handlers: kernel: [] (ide_intr+0x0/0x1d1) kernel: Disabling IRQ #18 I recognise this "disabling IRQ" message from the history of libata.ko development, where I more often saw it once and then immediately a kernel crash. I imagine we don't care. I imagine for 2.6 we prefer to focus on teaching libata.ko etc. to talk SATAPI, rather than working to document the 2.6 behaviour of the old deprecated code. But ... I'm writing just to give everyone a chance to tell me this is not a boringly normal result. Pat LaVarre P.S. Also in my one sample I see assymmetric thruput: writes out maybe thirteen percent down below reads in, in the neighbourhood of the 1.5 GB/min = 25 MB/s that is the outside disc limit of my sample device.