From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Rodney Gordon II <meff@spherevision.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Tejun Heo <htejun@gmail.com>
Subject: Re: [BUG] IT8212 libata driver *still* hard-freezes system on boot on 2.6.22 final.
Date: Mon, 9 Jul 2007 10:49:30 +0100 [thread overview]
Message-ID: <20070709104930.4e26f38f@the-village.bc.nu> (raw)
In-Reply-To: <1183944204.8932.8.camel@ghreen.sphere>
On Sun, 08 Jul 2007 20:23:24 -0500
Rodney Gordon II <meff@spherevision.org> wrote:
> Have been quite busy, and I regret I haven't tried a rc kernel in
> awhile, but, this bug has gone un-fixed still.. Thought I'd throw in
> another "heads up"..
>
> 2.6.22 hang: http://spherevision.org/sync/visual/itelock.jpg
> lspci -vvv: http://spherevision.org/sync/tmp/lspci.out
>
> Pentium-D 830 3.0GHz Dualcore on a ASUS P5LD2 with latest bios rev.
> 1804.
>
> SysRq does not work when this locks up.
>
> Patches, info, things to try, anything is welcome, I am available for
> awhile now and will try anything to get this working.
I'm at a bit of a loss on this one I'm afraid - it seems to be specific
to a couple of boards and every IT821x box I can lay my paws on works
beautifully.
It would be useful to know if a kernel built with no DMA support for the
IT8212 behaved as that might give us a clue about what is choking. If you
look in drivers/ata/pata_it821x.c:it821x_init_one you'll see a pair of
lines that say
mwdma = 0x1f,
udma_mask = 0x7f
remove, rebuild and report..
Thanks
Alan
next prev parent reply other threads:[~2007-07-09 9:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 1:23 Rodney Gordon II
2007-07-09 7:23 ` Tejun Heo
2007-07-09 9:49 ` Alan Cox [this message]
2007-07-09 11:16 ` Rodney Gordon II
2007-07-09 12:16 ` Alan Cox
2007-07-09 12:44 ` Rodney Gordon II
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=20070709104930.4e26f38f@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=meff@spherevision.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
all inboxes | Powered by JetHome®