From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Russell Howe <rhowe@siksai.co.uk>
Cc: linux-ide@vger.kernel.org
Subject: Re: IDE/ATAPI timeouts & lost interrupts on alpha with 2.6.20.2
Date: Sun, 11 Mar 2007 01:02:13 +0100 [thread overview]
Message-ID: <200703110102.13652.bzolnier@gmail.com> (raw)
In-Reply-To: <20070310225643.GB21407@xiao.rsnet>
Hi,
On Saturday 10 March 2007, Russell Howe wrote:
> Evening all,
>
> I just built a 2.6.20.2 kernel for my alpha (a digital personal
> workstation 500AU), and on bootup noticed the messages below, which took
> a long time to print. There was no media in the CDROM, and there's
> nothing else hanging off the IDE controller. The messages took several
> minutes to appear, stalling the boot process.
>
> Unrelated, no doubt, but the output from the init scripts doesn't seem
> to have made it to the serial console, so I'm not sure what processes
> were running at the time.
>
> The last kernel I ran on this thing was 2.6.17.11, which I appreciate is
> a long time ago, so if anyone could suggest a starting point for a
> binary search to determine the change which caused this regression, I'm
> all ears! Kernels take a while to build on this box, and I haven't got a
> crosscompiling toolchain setup...
>
> What's the best way to go about debugging this?
>
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> [...]
> CY82C693: IDE controller at PCI slot 0000:00:07.1
> CY82C693: chipset revision 0
> CY82C693: not 100% native mode: will probe irqs later
> CY82C693U driver v0.34 99-13-12 Andreas S. Krebs (akrebs@altavista.net)
> ide0: BM-DMA at 0x9080-0x9087, BIOS settings: hda:pio, hdb:pio
> PCI: Enabling device: (0000:00:07.2), cmd 47
> CY82C693: port 0x01f0 already claimed by ide0
> CY82C693: neither IDE port enabled (BIOS)
It seems that the generic IDE host driver is loaded first
(CONFIG_IDE_GENERIC=y/m) and "steals" resources needed by cy82c693.
Please try again without the generic IDE host driver so the proper
driver could be used.
If it doesn't help I think that the best way to chase it is git bisect.
Thanks,
Bart
> Probing IDE interface ide0...
> hda: TOSHIBA CD-ROM XTAPI CD/DVD-ROM drive
> hda: IRQ probe failed (0xfffffffff73bfeea)
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> ide-cd: cmd 0x5a timed out
> hda: lost interrupt
> ide-cd: cmd 0x5a timed out
> hda: lost interrupt
> ide-cd: cmd 0x5a timed out
> hda: lost interrupt
> hda: ATAPI 32X CD-ROM drive, 256kB Cache, DMA
> Uniform CD-ROM driver Revision: 3.20
> hda: lost interrupt
> ide-cd: cmd 0x3 timed out
> hda: lost interrupt
> ide-cd: cmd 0x3 timed out
> hda: lost interrupt
> hda: lost interrupt
> ide-cd: cmd 0x3 timed out
> hda: lost interrupt
> ide-cd: cmd 0x3 timed out
> hda: lost interrupt
> hda: lost interrupt
> ide-cd: cmd 0x3 timed out
> hda: lost interrupt
> ide-cd: cmd 0x3 timed out
> hda: lost interrupt
>
> --
> Russell Howe | Why be just another cog in the machine,
> rhowe@siksai.co.uk | when you can be the spanner in the works?
next prev parent reply other threads:[~2007-03-10 23:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-10 22:56 IDE/ATAPI timeouts & lost interrupts on alpha with 2.6.20.2 Russell Howe
2007-03-11 0:02 ` Bartlomiej Zolnierkiewicz [this message]
2007-03-11 1:29 ` Russell Howe
2007-03-12 1:07 ` Russell Howe
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=200703110102.13652.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=rhowe@siksai.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.