From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Re: [linux-2.6.10] radeonfb / oops
Date: Fri, 04 Feb 2005 16:59:53 +1100 [thread overview]
Message-ID: <1107496794.2362.90.camel@gaston> (raw)
In-Reply-To: <200502030925.09942.pluto@pld-linux.org>
On Thu, 2005-02-03 at 09:25 +0100, Pawe³ Sikora wrote:
> > > Hi,
> > >
> > > Could You look at this: http://lkml.org/lkml/2005/1/29/67
> > > Help will be appreciated.
> >
> > From: James Simmons <jsimmons@ww...>
> > Re: [linux-2.6.10] radeonfb / oops
> > 2005-02-01 12:54
> >
> > Can you post your config?
> >
> > On Tue, 1 Feb 2005, Pawel Sikora wrote:
> >
>
> I've tested kernel without grsec and fbsplash and it still oopses.
>
> plain text document attachment (.config)
You seem to have built both the old and new radeonfb's ... can you
remove the old one ?
Ben.
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-02-04 6:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-03 8:25 [linux-2.6.10] radeonfb / oops Paweł Sikora
2005-02-04 5:59 ` Benjamin Herrenschmidt [this message]
2005-02-04 20:42 ` James Simmons
2005-02-04 21:04 ` Jon Smirl
2005-02-04 21:17 ` Otto Wyss
2005-02-04 21:59 ` James Simmons
2005-02-05 0:36 ` Jon Smirl
2005-02-05 10:40 ` Otto Wyss
2005-02-04 20:42 ` James Simmons
-- strict thread matches above, loose matches on Subject: below --
2005-02-12 15:39 Paweł Sikora
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=1107496794.2362.90.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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.