All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Mel Gorman <mel@csn.ul.ie>
Cc: Steven Rostedt <rostedt@goodmis.org>, werner <w.landgraf@ru.ru>,
	linux-kernel@vger.kernel.org,
	David Rientjes <rientjes@google.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	"David S. Miller" <davem@davemloft.net>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: kernel problem
Date: Mon, 7 Dec 2009 22:09:43 +0100	[thread overview]
Message-ID: <20091207210943.GH8742@kernel.dk> (raw)
In-Reply-To: <20091207145011.GA14743@csn.ul.ie>

On Mon, Dec 07 2009, Mel Gorman wrote:
> On Fri, Dec 04, 2009 at 10:41:09AM -0500, Steven Rostedt wrote:
> > [ Added Cc's of people that may be interested in this ]
> > > <SNIP>
> > > ------------[ cut here ]------------
> > > WARNING: at mm/page_alloc.c:1805
> > > __alloc_pages_nodemask+0x127/0x48f()
> > > Hardware name: System Product Name
> > > Modules linked in:
> > > Pid: 1, comm: swapper Not tainted 2.6.32-rc8-git5 #1
> > > Call Trace:
> > >  [<c103d94b>] warn_slowpath_common+0x65/0x95
> > >  [<c103d98d>] warn_slowpath_null+0x12/0x15
> > >  [<c109550c>] __alloc_pages_nodemask+0x127/0x48f
> > >  [<c10be964>] ? get_slab+0x8/0x50
> > >  [<c10b8979>] alloc_page_interleave+0x2e/0x6e
> > >  [<c10b8a10>] alloc_pages_current+0x57/0x99
> > >  [<c2083a4a>] ? xd_init+0x0/0x482
> > >  [<c1094c38>] __get_free_pages+0xd/0x1e
> > >  [<c2083a94>] xd_init+0x4a/0x482
> > >  [<c2082df0>] ? loop_init+0x104/0x16a
> > >  [<c169162d>] ? loop_probe+0x0/0xaf
> > >  [<c2083a4a>] ? xd_init+0x0/0x482
> > >  [<c1001143>] do_one_initcall+0x51/0x13f
> > >  [<c204a307>] kernel_init+0x10b/0x15f
> > >  [<c204a1fc>] ? kernel_init+0x0/0x15f
> > >  [<c1004347>] kernel_thread_helper+0x7/0x10
> > > ---[ end trace 686db6333ade6e7a ]---
> > > xd: Out of memory.
> 
> First off, it would appear that every block driver under the sun is
> being loaded. I seriously doubt this controller really exists in the
> machine.
> 
> Second, it's a real warning as the driver is trying to allocate a buffer of
> size 0 which get_order() chokes on. For bonus points, it tries to allocate
> a buffer before it knows what size it should be. This patch should resolve
> the problem but because I don't have the hardware to test it on, it could
> do with a second set of eyes just to be sure the rejigged logic makes sense.
> 
> If this is ok, what is the appropriate submission path for unmaintained
> block drivers? Is it the block maintainer or someone else?

Thanks Mel, I'll add this to the next pull queue.

-- 
Jens Axboe


  parent reply	other threads:[~2009-12-07 21:09 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03  7:40 kernel problem werner
2009-12-04 15:41 ` Steven Rostedt
2009-12-07 14:50   ` Mel Gorman
2009-12-07 20:48     ` Andrew Morton
2009-12-07 21:09     ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-05-11 15:17 Kernel problem Frank Vosberg
2017-05-11 16:57 ` Randy Dunlap
2017-05-12  5:56   ` Michal Hocko
2009-12-09  7:01 kernel problem werner
2009-12-09  7:01 werner
2009-12-04 19:48 werner
2009-12-04 19:47 werner
2009-02-25 11:43 Kernel problem Denis Romanenko
2009-02-26  9:39 ` Herbert Xu
2009-02-26  9:38   ` Denys Fedoryschenko
2009-02-26 10:56   ` Jarek Poplawski
2009-02-26 11:24     ` Denis Romanenko
2009-02-26 12:00       ` Jarek Poplawski
2009-02-26 12:47         ` Jarek Poplawski
2009-02-26 12:51           ` Denis Romanenko
2009-02-26 13:17             ` Jarek Poplawski
2009-02-26 11:56     ` Herbert Xu
2009-02-26 12:10       ` David Miller
2009-02-26 13:06         ` Herbert Xu
2009-02-26 13:19           ` Jarek Poplawski
2009-02-27  4:11           ` Herbert Xu
2009-02-27  8:03             ` David Miller
2009-02-27 11:45               ` Herbert Xu
2009-02-27 13:24                 ` David Miller
2009-02-27  8:41             ` Jarek Poplawski
2009-02-27  8:59               ` David Miller
2009-02-27  9:12                 ` Jarek Poplawski
2009-02-27  9:16                   ` David Miller
2009-02-27  9:29                     ` Jarek Poplawski
2009-03-01  7:38                     ` Herbert Xu
2009-03-01  8:12                       ` David Miller
2007-01-13 10:56 kernel problem Suresh Chandra Mannava
2004-06-22 16:54 Kernel problem Juhani Pirttilahti
2004-06-22 17:18 ` William Lee Irwin III
2004-06-22 19:47   ` Juhani Pirttilahti
2004-06-22 22:43     ` Juhani Pirttilahti
2004-06-23  8:33 ` Geert Uytterhoeven
2002-05-20  6:04 Kernel Problem Brinley Craig
1998-05-18 18:07 Kernel problem Stephan van Hienen

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=20091207210943.GH8742@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=acme@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mel@csn.ul.ie \
    --cc=rientjes@google.com \
    --cc=rjw@sisk.pl \
    --cc=rostedt@goodmis.org \
    --cc=w.landgraf@ru.ru \
    /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.