mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@hp.com>
To: linux-kernel@vger.kernel.org
Subject: bugcheck! __get_free_pages calls __init function w/ CONFIG_NUMA
Date: Tue, 06 Apr 2004 11:19:36 -0600	[thread overview]
Message-ID: <1081271975.2375.73.camel@patsy.fc.hp.com> (raw)


   I'm not sure why we haven't seen this before, but I started seeing a
stack trace on reboot on my rx2600 ia64 box running latest 2.6.  Here it
is:

 [<a0000001006ba020>] get_boot_pages+0x0/0x2c0
                                sp=e00000010267fc80 bsp=e000000102679130
 [<a0000001004a8fb0>] sba_alloc_coherent+0x70/0x1a0
                                sp=e00000010267fc80 bsp=e0000001026790f8
 [<a00000010047e3b0>] mptscsih_synchronize_cache+0x1d0/0x640
                                sp=e00000010267fc80 bsp=e000000102679010
 [<a0000001004665e0>] mptbase_shutdown+0xc0/0xe0
                                sp=e00000010267fd30 bsp=e000000102678fd8
 [<a0000001003a9140>] device_shutdown+0x260/0x280
                                sp=e00000010267fd30 bsp=e000000102678fa8
 [<a0000001000b10a0>] sys_reboot+0x2e0/0x720
                                sp=e00000010267fd30 bsp=e000000102678f50


sba_alloc_coherent is simply calling __get_free_pages() to setup a DMA
mapping for the mpt driver to sync a disk.  However, we've already
cleared system_running in sys_reboot, so w/ CONFIG_NUMA, we blowup
trying to call get_boot_pages, which was already freed.  I'm not sure if
the proper fix is to make get_boot_pages not an __init function or if
the CONFIG_NUMA code really intends to be keying off something else. 
Thoughts on the right fix?  Thanks,

	Alex

-- 
Alex Williamson                             HP Linux & Open Source Lab


                 reply	other threads:[~2004-04-06 17:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1081271975.2375.73.camel@patsy.fc.hp.com \
    --to=alex.williamson@hp.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

Powered by JetHome