From: Martin Dalecki <dalecki@evision-ventures.com>
To: John Langford <jcl@cs.cmu.edu>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, ahaas@neosoft.com,
dave@zarzycki.org, ben.de.rydt@pandora.be
Subject: Re: BUG: 2.4.18 & ALI15X3 DMA hang on boot
Date: Sat, 23 Mar 2002 14:11:21 +0100 [thread overview]
Message-ID: <3C9C7EF9.8020307@evision-ventures.com> (raw)
In-Reply-To: <200203221956.g2MJuhK32671@gs176.sp.cs.cmu.edu>
John Langford wrote:
> I went nuts with printk statements and managed to isolate the hang to
> one particular line of code. The final printk in this code fragment
> never gets executed.
>
> } else if (m5229_revision >= 0xC3) {
> /*
> * 1553/1535 (m1533, 0x79, bit 1)
> */
> printk("ata66_ali15x3 } else if (m5229_revisi\on >= 0xC3) {\n");
> pci_write_config_byte(isa_dev, 0x79, tmpbyte | 0x02);
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
pci_write_config to isa_dev???? This looks at least suspicious.
You may very well check whatever isa_dev is trully a PCI device
handle or just some random IO base for ISA bus!
> }
> printk("ata66_ali15x3 endif\n");
>
> Art, Dave, and Ben may or may not have the same problem. It would be
> interesting to know if they get a hang here.
>
> Any ideas for fixing?
See above :-)
next prev parent reply other threads:[~2002-03-23 13:13 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-21 20:47 BUG: 2.4.18 & ALI15X3 DMA hang on boot John Langford
2002-03-21 22:17 ` Alan Cox
2002-03-21 22:41 ` John Langford
2002-03-22 0:47 ` Dave Zarzycki
2002-03-22 1:43 ` John Langford
2002-03-22 20:46 ` John Langford
2002-03-23 13:25 ` Martin Dalecki
2002-03-23 14:19 ` John Langford
2002-03-23 14:22 ` Martin Dalecki
2002-03-23 14:51 ` Art Haas
2002-03-23 19:49 ` Dave Zarzycki
2002-03-24 22:47 ` Martin Dalecki
2002-03-22 10:55 ` Martin Dalecki
2002-03-22 11:24 ` Andre Hedrick
2002-03-22 11:50 ` Martin Dalecki
2002-03-22 15:59 ` John Langford
2002-03-23 5:16 ` Andre Hedrick
2002-03-23 13:05 ` Martin Dalecki
2002-03-25 2:26 ` Andre Hedrick
2002-03-22 13:25 ` Jens Axboe
2002-03-22 14:49 ` Alan Cox
2002-03-22 20:53 ` Andre Hedrick
2002-03-22 21:52 ` Andre Hedrick
2002-03-23 3:51 ` Ian Molton
2002-03-23 3:57 ` Ian Molton
2002-03-22 19:56 ` John Langford
2002-03-22 21:53 ` Vojtech Pavlik
2002-03-23 13:11 ` Martin Dalecki [this message]
2002-03-23 13:43 ` Jeff Garzik
2002-03-23 13:47 ` Martin Dalecki
2002-03-23 20:23 ` Vojtech Pavlik
2002-03-23 21:43 ` Andre Hedrick
2002-03-24 22:50 ` Martin Dalecki
2002-03-25 1:26 ` Andre Hedrick
2002-03-25 9:24 ` Vojtech Pavlik
2002-03-25 9:40 ` Andre Hedrick
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=3C9C7EF9.8020307@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=ahaas@neosoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ben.de.rydt@pandora.be \
--cc=dave@zarzycki.org \
--cc=jcl@cs.cmu.edu \
--cc=linux-kernel@vger.kernel.org \
/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