linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Juergen Beisert <jbe@pengutronix.de>
To: linux-kernel@vger.kernel.org
Cc: Mel Gorman <mel@csn.ul.ie>,
	linux-arm-kernel@lists.arm.linux.org.uk,
	linux-hotplug@vger.kernel.org
Subject: Re: Patch "page-allocator: preserve PFN ordering when __GFP_COLD is set" fails on my system
Date: Wed, 12 Aug 2009 11:11:34 +0000	[thread overview]
Message-ID: <200908121311.35321.jbe@pengutronix.de> (raw)
In-Reply-To: <20090812092034.GA19269@csn.ul.ie>

On Mittwoch, 12. August 2009, Mel Gorman wrote:
> > > I get the following Ooops message when "udevadm" is running on an ARM
> > > S3C2440 CPU based system:
>
> This is extremely odd. All that patch is doing is changing what order pages
> are returned in to the caller when __GFP_COLD is specified.  valid memory.
> Does reverting the patch really make the problem go away?

At least I can work with the system if I remove this patch. Theres is no oops, 
so udev creates all the required devnodes and the system comes up into the 
login prompt.

> > > [...]
> > > starting udevd...done
> > > Unable to handle kernel paging request at virtual address e3540000
> > > pgd = c39d4000
> > > [e3540000] *pgd\0000000
> > > Internal error: Oops: 5 [#1]
> > > Modules linked in:
> > > CPU: 0    Not tainted  (2.6.31-rc4-00296-ge084b2d-dirty #10)
> > > PC is at strlen+0xc/0x20
> > > LR is at kobject_get_path+0x24/0xa4
>
> I haven't tackled this sort of bug before but it looks more likely that
> there is garbage in the sysfs tree that is being tripped up on.

Yes, I think so, too. Because the same binary rc5 image runs on an S3C2410 CPU 
without an oops, but oopses on an S3C2440 (both CPUs are nearly the same, but 
only nearly). But how to track down such a failure?

Regards,
Juergen

-- 
Pengutronix e.K.                              | Juergen Beisert             |
Linux Solutions for Science and Industry      | Phone: +49-8766-939 228     |
Vertretung Sued/Muenchen, Germany             | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686              | http://www.pengutronix.de/  |

  reply	other threads:[~2009-08-12 11:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-11 16:30 Patch "page-allocator: preserve PFN ordering when __GFP_COLD is set" fails on my system Juergen Beisert
2009-08-12  7:47 ` Patch "page-allocator: preserve PFN ordering when __GFP_COLD Robert Schwebel
2009-08-12  9:20   ` Mel Gorman
2009-08-12 11:11     ` Juergen Beisert [this message]
2009-08-12 13:50       ` Mel Gorman
2009-08-12 15:35         ` Patch "page-allocator: preserve PFN ordering when __GFP_COLD is set" fails on my system Juergen Beisert
2009-08-12 18:40           ` Patch "page-allocator: preserve PFN ordering when __GFP_COLD Arnaud Faucher
2009-08-13  8:39             ` Mel Gorman
2009-08-13  9:22               ` Patch "page-allocator: preserve PFN ordering when __GFP_COLD is set" fails on my system Juergen Beisert

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=200908121311.35321.jbe@pengutronix.de \
    --to=jbe@pengutronix.de \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-hotplug@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mel@csn.ul.ie \
    /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;
as well as URLs for NNTP newsgroup(s).