From: Miles Lane <miles.lane@gmail.com>
To: Dave Airlie <airlied@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: OOPS in 2.6.13-rc1-mm1 -- EIP is at sysfs_release+0x49/0xb0
Date: Wed, 13 Jul 2005 09:54:10 -0500 [thread overview]
Message-ID: <a44ae5cd05071307546d3f8f9e@mail.gmail.com> (raw)
In-Reply-To: <21d7e99705071300173ae0c39b@mail.gmail.com>
On 7/13/05, Dave Airlie <airlied@gmail.com> wrote:
> > Thanks Dave,
> >
> > I switched to the i915 kernel driver and still got the OOPS.
> > I also continue to get the overlapping mtrr message. I am currently
> > testing 2.6.13-rc2-git3. I have tried to run strace with hald, but
> > cannot reproduce the problem this way. I am not sure I am invoking the
> > command corrently. I have written to the hal developers, but have not
> > received a response yet. Here's the current output:
> >
>
> Can you try and see if you apply the patch from
>
> http://lkml.org/lkml/2005/7/8/257
>
> It should apply to your kernel.. I cannot get this to happen on my
> system... the mtrr overlaps are just vesafb setting up the mtrrs, you
> might try without vesafb...
I will try booting without vesafb enabled.
I get an error building with the patch applied to 2.6.13-rc2-git3:
arch/i386/kernel/built-in.o(.text+0x4010): In function `die':
arch/i386/kernel/traps.c:343: undefined reference to `last_sysfs_name'
make: *** [.tmp_vmlinux1] Error 1
Thanks,
Miles
next prev parent reply other threads:[~2005-07-13 14:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-03 8:41 OOPS in 2.6.13-rc1-mm1 -- EIP is at sysfs_release+0x49/0xb0 Miles Lane
2005-07-06 22:27 ` Andrew Morton
2005-07-07 1:41 ` Schneelocke
2005-07-07 10:31 ` Dave Airlie
2005-07-07 14:56 ` Miles Lane
2005-07-11 4:26 ` Miles Lane
2005-07-13 7:17 ` Dave Airlie
2005-07-13 14:54 ` Miles Lane [this message]
2005-07-13 19:42 ` randy_dunlap
2005-08-08 16:53 ` Sonny Rao
2005-08-08 17:44 ` Andrew Morton
2005-08-08 20:18 ` Sonny Rao
2005-08-08 23:09 ` Keith Owens
2005-08-08 23:59 ` Sonny Rao
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=a44ae5cd05071307546d3f8f9e@mail.gmail.com \
--to=miles.lane@gmail.com \
--cc=airlied@gmail.com \
--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