From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: TAKADA Yoshihito <takada@mbf.nifty.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: IDE driver assined IRQ for disabled IDE channel
Date: Sat, 26 Jul 2008 13:58:59 +0200 [thread overview]
Message-ID: <200807261358.59667.bzolnier@gmail.com> (raw)
In-Reply-To: <20080725.143128.193681587.takada@mbf.nifty.com>
Hi,
On Friday 25 July 2008, TAKADA Yoshihito wrote:
> Hi.
> In kernel 2.6.26, I disable the secoundary IDE via BIOS. But kernel assigned IRQ to secondary IDE.
> I saw /proc/interrupts:
> - /proc/interrupts of 2.6.25
> CPU0
> 0: 232213 XT-PIC-XT timer
> 1: 388 XT-PIC-XT i8042
> 2: 0 XT-PIC-XT cascade
> 3: 1 XT-PIC-XT
> 4: 305 XT-PIC-XT
> 5: 1 XT-PIC-XT
> 7: 1 XT-PIC-XT
> 8: 0 XT-PIC-XT rtc0
> 9: 1 XT-PIC-XT
> 10: 1 XT-PIC-XT
> 11: 1 XT-PIC-XT
> 12: 110 XT-PIC-XT i8042
> 14: 5640 XT-PIC-XT ide0
> 15: 35 XT-PIC-XT yenta, ohci_hcd:usb1
> NMI: 0 Non-maskable interrupts
> TRM: 0 Thermal event interrupts
> SPU: 0 Spurious interrupts
> ERR: 0
>
> IRQ15 doesn't assigned for ide1.
>
> - /proc/interrupts of 2.6.26
> CPU0
> 0: 213884 XT-PIC-XT timer
> 1: 197 XT-PIC-XT i8042
> 2: 0 XT-PIC-XT cascade
> 3: 1 XT-PIC-XT
> 4: 309 XT-PIC-XT
> 5: 1 XT-PIC-XT
> 7: 2 XT-PIC-XT
> 8: 0 XT-PIC-XT rtc0
> 9: 1 XT-PIC-XT
> 10: 1 XT-PIC-XT
> 11: 1 XT-PIC-XT
> 12: 110 XT-PIC-XT i8042
> 14: 5621 XT-PIC-XT ide0
> 15: 0 XT-PIC-XT ide1
> NMI: 0 Non-maskable interrupts
> TRM: 0 Thermal event interrupts
> SPU: 0 Spurious interrupts
> ERR: 1
>
> However, kernel 2.6.26 assinged IRQ15 for ide1. And yenta and ohci
> (USB host controller) couldn't assign an IRQ.
>
> dmesg are:
> Yenta: CardBus bridge found at 0000:00:01.0 [0000:0000]
> Yenta: no PCI IRQ, CardBus support disabled for this socket.
> Yenta: check your BIOS CardBus, BIOS IRQ or ACPI settings.
>
> ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
> ohci_hcd 0000:00:13.0: OHCI Host Controller
> ohci_hcd 0000:00:13.0: new USB bus registered, assigned bus number 1
> ohci_hcd 0000:00:13.0: request interrupt 15 failed
> ohci_hcd 0000:00:13.0: USB bus 1 deregistered
> ohci_hcd 0000:00:13.0: init 0000:00:13.0 fail, -16
> ohci_hcd: probe of 0000:00:13.0 failed with error -16
Could you please post the full dmesg?
The second IDE port should be skipped by the corresponding host driver
if disabled in BIOS (it could be that this particular host driver neeeds
fixing).
> Signed-off-by: TAKADA Yoshihito <takada@mbf.nifty.com>
>
> diff -Narup a/drivers/ide/ide-probe.c b/drivers/ide/ide-probe.c
> --- a/drivers/ide/ide-probe.c 2008-07-25 13:21:37.000000000 +0900
> +++ b/drivers/ide/ide-probe.c 2008-07-25 13:42:38.000000000 +0900
> @@ -1546,6 +1546,8 @@ int ide_device_add_all(u8 *idx, const st
> continue;
>
> hwif = &ide_hwifs[idx[i]];
> + if (!hwif->present)
> + continue;
Unfortunately we can't fix it this way as this will cause regression
for other people (we now want ports with no devices attached to be also
registered to allow warm-plugging of IDE devices).
BTW sorry for breaking things for you with every major kernel release ;)
(any chance that you give linux-next kernels a test drive from time to
time so we catch such problems early?)
> if (hwif_init(hwif) == 0) {
> printk(KERN_INFO "%s: failed to initialize IDE "
> @@ -1582,12 +1584,11 @@ int ide_device_add_all(u8 *idx, const st
> continue;
>
> hwif = &ide_hwifs[idx[i]];
> -
> - ide_sysfs_register_port(hwif);
> - ide_proc_register_port(hwif);
> -
> - if (hwif->present)
> + if (hwif->present) {
> + ide_sysfs_register_port(hwif);
> + ide_proc_register_port(hwif);
> ide_proc_port_register_devices(hwif);
> + }
> }
>
> return rc;
next prev parent reply other threads:[~2008-07-26 12:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 5:31 IDE driver assined IRQ for disabled IDE channel TAKADA Yoshihito
2008-07-26 11:58 ` Bartlomiej Zolnierkiewicz [this message]
2008-07-27 1:51 ` TAKADA Yoshihito
2008-07-27 13:56 ` Bartlomiej Zolnierkiewicz
2008-07-30 17:57 ` TAKADA Yoshihito
2008-08-02 16:28 ` Bartlomiej Zolnierkiewicz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200807261358.59667.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=takada@mbf.nifty.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).