public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: dave young <hidave.darkstar@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, jeremy@goop.org
Subject: Re: i386 boot fail, EIP in __change_page_attr:166
Date: Tue, 26 Jun 2007 13:31:49 -0400	[thread overview]
Message-ID: <46814D85.5070406@redhat.com> (raw)
In-Reply-To: <a8e1da0706251811k636b7b8dmc21e5bfc26b09e06@mail.gmail.com>

On 06/25/2007 09:11 PM, dave young wrote:
> Hi,
> 
> 2007/6/25, Chuck Ebbert <cebbert@redhat.com>:
>> On 06/24/2007 11:43 PM, dave young wrote:
>> > Hi,
>> > I reconfig my kernel, boot and oops, EIP in __change_page_attr:166, I
>> > tried 2.6.22-rc4-mm2 and 2.6.22-rc5 , same result.
>> >
>> > Anyone has some clues?
>> >
>> > here is my config file:
>>
>> Where are the oops messages?
> Attached please find the screenshots. sorry for my phone camera resolution.
> screen1.png : vga=ask select mode 6
> screen2.png : normal 80x25 console

That's 2.6.22-rc4-mm2 which I don't have.

netsc520 is doing iounmap() of an area it did
ioremap_nocache() on earlier, because it has now failed to
find a device. Why it went BUG() I have no idea.

  parent reply	other threads:[~2007-06-26 17:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-25  3:43 i386 boot fail, EIP in __change_page_attr:166 dave young
2007-06-25 16:55 ` Chuck Ebbert
     [not found]   ` <a8e1da0706251811k636b7b8dmc21e5bfc26b09e06@mail.gmail.com>
2007-06-26 17:31     ` Chuck Ebbert [this message]
2007-06-27  1:15       ` dave young
2007-06-27 14:28         ` Jeremy Fitzhardinge
2007-06-29  9:00           ` Dave Young
2007-06-29  9:04             ` Dave Young
2007-06-29 12:44               ` Jeremy Fitzhardinge
2007-06-26 14:03 ` Jeremy Fitzhardinge
2007-06-27  1:08   ` dave young
2007-06-27 14:27     ` Jeremy Fitzhardinge

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=46814D85.5070406@redhat.com \
    --to=cebbert@redhat.com \
    --cc=hidave.darkstar@gmail.com \
    --cc=jeremy@goop.org \
    --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