From: Dave Jones <davej@redhat.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: "Georg C. F. Greve" <greve@fsfeurope.org>,
Hans Ulrich Niedermann <vserver@n-dimensional.de>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
ACPI Developers <acpi-devel@lists.sourceforge.net>,
Andrew Morton <akpm@osdl.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Herbert Poetzl <herbert@13thfloor.at>,
Nick Warne <nick@linicks.net>, Len Brown <len.brown@intel.com>
Subject: Re: PROBLEM: Kernel 2.6.10 crashing repeatedly and hard
Date: Sun, 2 Jan 2005 15:32:06 -0500 [thread overview]
Message-ID: <20050102203206.GB22295@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0501021147260.2280@ppc970.osdl.org>
On Sun, Jan 02, 2005 at 12:11:47PM -0800, Linus Torvalds wrote:
> DaveJ: this may explain the "Mobile Radeon" reports. Not because of
> anything Radeon-specific, but simply because they'd have four ports (CRT,
> LVDS TFT panel, tv-out, and tv-in, I think - ACPI doesn't tell me enough
> to be sure).
I think the problem biting Fedora people turned out to be a side-effect
of having the 4g/4g patch applied, but not enabled. (The affected kernels
we shipped didn't have the post-2.6.9 acpi video stuff).
Dave
next prev parent reply other threads:[~2005-01-02 20:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 0:31 PROBLEM: Kernel 2.6.10 crashing repeatedly and hard Georg C. F. Greve
2004-12-30 16:23 ` Georg C. F. Greve
[not found] ` <v3rda2-hjn.ln1@news.it.uc3m.es>
2004-12-30 17:53 ` Sandro Dentella
2004-12-30 19:50 ` Michael Tokarev
2004-12-30 20:54 ` berk walker
2005-01-01 13:39 ` Helge Hafting
2004-12-30 20:40 ` Linus Torvalds
2004-12-30 22:04 ` Georg C. F. Greve
2004-12-30 22:23 ` Linus Torvalds
2004-12-31 4:16 ` Herbert Poetzl
2004-12-31 4:53 ` Linus Torvalds
2004-12-31 10:55 ` Russell King
2004-12-31 9:58 ` Georg C. F. Greve
2005-01-01 20:06 ` Alan Cox
2005-01-02 20:11 ` Linus Torvalds
2005-01-02 20:32 ` Dave Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-30 10:21 Nick Warne
2004-12-31 11:46 Manfred Spraul
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=20050102203206.GB22295@redhat.com \
--to=davej@redhat.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greve@fsfeurope.org \
--cc=herbert@13thfloor.at \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@linicks.net \
--cc=torvalds@osdl.org \
--cc=vserver@n-dimensional.de \
/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