From: Kurt Wall <kwall@kurtwerks.com>
To: Dave Jones <davej@redhat.com>,
Erwin Rol <mailinglists@erwinrol.com>,
Andrew Morton <akpm@osdl.org>,
"Carlo E. Prelz" <fluido@fluido.as>,
linux-kernel@vger.kernel.org
Subject: Re: ATI RS480-based motherboard: stuck while booting with kernel >= 2.6.15 rc1
Date: Sat, 21 Jan 2006 23:14:27 -0500 [thread overview]
Message-ID: <20060122041427.GA6183@kurtwerks.com> (raw)
In-Reply-To: <20060121220402.GC28051@redhat.com>
On Sat, Jan 21, 2006 at 05:04:02PM -0500, Dave Jones took 21 lines to write:
> On Sat, Jan 21, 2006 at 10:28:46PM +0100, Erwin Rol wrote:
> > I had also had the problem that my Shuttle ST20G5 (a RS480 IGP based
> > system) hung in pci_init. This was with one of the Fedora Rawhide
> > kernels, after reporting it Dave Jones fixed it cause the next rawhide
> > kernel worked again, maybe he could explain what it was, and where the
> > fix is (if it is the same thing, but it really looks like it).
>
> That was due to us carrying one of the 'make the clock not tick
> at twice the speed on ati chipsets' patches. Matthew Garrett's variant iirc.
> It worked fine in .14, but caused havoc in .15+
>
> I put it down to the problem being fixed in other ways upstream.
Heh. I think you mean s/fixed/worked around/.
The bugme tracking this, 3927, is a joyous muddle of patches,
patches to patches, workarounds, and dueling command line options.
I ported this patch,
http://www.ussg.iu.edu/hypermail/linux/kernel/0504.0/1625.html,
to 2.6.16-rc1 to fix my pain, but 1) it didn't work without the
disable_timer_pin_1 kernel option and, 2) I don't think it's a fix
so much as a workaround.
Kurt
--
I can read your mind, and you should be ashamed of yourself.
next prev parent reply other threads:[~2006-01-22 4:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 12:32 Carlo E. Prelz
2006-01-21 9:09 ` Andrew Morton
2006-01-21 12:57 ` Carlo E. Prelz
2006-01-21 20:58 ` Andrew Morton
2006-01-21 21:28 ` Erwin Rol
2006-01-21 22:04 ` Dave Jones
2006-01-22 4:14 ` Kurt Wall [this message]
2006-01-22 7:40 ` Carlo E. Prelz
2006-01-22 7:55 ` Andrew Morton
2006-01-22 8:30 ` Carlo E. Prelz
2006-01-22 11:11 ` Carlo E. Prelz
2006-02-05 10:33 ` Carlo E. Prelz
2006-02-05 19:45 ` [linux-usb-devel] " David Brownell
2006-02-06 8:02 ` Carlo E. Prelz
2006-02-06 16:24 ` David Brownell
2006-02-06 16:50 ` Carlo E. Prelz
2006-02-06 17:31 ` David Brownell
2006-02-06 17:45 ` Carlo E. Prelz
2006-01-23 19:01 ` David Brownell
2006-01-23 21:47 ` Carlo E. Prelz
2006-01-24 4:42 ` Greg KH
2006-01-24 15:15 ` David Brownell
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=20060122041427.GA6183@kurtwerks.com \
--to=kwall@kurtwerks.com \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=fluido@fluido.as \
--cc=linux-kernel@vger.kernel.org \
--cc=mailinglists@erwinrol.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
Powered by JetHome