public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Shaohua Li <shaohua.li@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
	linux-acpi@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: Fw: Re: 2.6.21-rc4-mm1 + 4 hotfixes -- BUG: unable to handle kernel paging request at virtual address 6b6b6ceb -- EIP is at module_put+0x7/0x1f
Date: Fri, 23 Mar 2007 10:04:26 +0800	[thread overview]
Message-ID: <1174615467.23591.3.camel@sli10-conroe.sh.intel.com> (raw)
In-Reply-To: <20070322095232.f992794a.akpm@linux-foundation.org>

On Fri, 2007-03-23 at 01:52 +0800, Andrew Morton wrote:
> 
> It looks like the cpuidle patches are doing incorrect things
> with their kobject protocol.
Looks the goal to force kobject to be allocated dynamically is to
release the memory of the kobject. But in the cpuidle case, we don't
want to free the memory as it might be used soon. I saw a lot of similar
staff too, like 'cpu_devices' in arch/i386/kernel/topology.c.


Thanks,
Shaohua
> Begin forwarded message:
> 
> Date: Thu, 22 Mar 2007 09:24:38 -0700
> From: "Miles Lane" <miles.lane@gmail.com>
> To: "Andrew Morton" <akpm@linux-foundation.org>
> Cc: LKML <linux-kernel@vger.kernel.org>,
> linux-wireless@vger.kernel.org
> Subject: Re: 2.6.21-rc4-mm1 + 4 hotfixes -- BUG: unable to handle
> kernel paging request at virtual address 6b6b6ceb -- EIP is at
> module_put+0x7/0x1f
> 
> 
> I cannot reproduce the BUG with your ml.bz2 patch applied.
> I am seeing this with both 2.6.21-rc4-mm1 + hotfixes, and with
> 2.6.21-rc4 + ml.bz2:
> 
> Mar 22 09:10:35 FractalPath kernel: ACPI: CPU0 (power states: C1[C1]
> C2[C2] C3[C3])
> Mar 22 09:10:35 FractalPath kernel: The kobject at, or inside
> per_cpu__cpuidle_devices+0x40/0x558 is not dynamically allocated.
> Mar 22 09:10:35 FractalPath kernel: The kobject at, or inside
> per_cpu__cpuidle_devices+0xd4/0x558 is not dynamically allocated.
> Mar 22 09:10:35 FractalPath kernel: The kobject at, or inside
> per_cpu__cpuidle_devices+0x168/0x558 is not dynamically allocated.
> Mar 22 09:10:35 FractalPath kernel: cpuidle: using driver acpi_idle
> 
> Not sure if this is a problem.  Also, the first time I booted the
> ml.bz2
> build, it hung.  I don't have netconsole or a serial debugging system
> set up, so I have no idea what the problem was.  The second boot,
> ipw2200 loaded with no errors, but NetworkManager wouldn't
> connect until I removed and reinserted the module.
> 
> All the best,
>            Miles
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 

  reply	other threads:[~2007-03-23  2:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22 17:52 Fw: Re: 2.6.21-rc4-mm1 + 4 hotfixes -- BUG: unable to handle kernel paging request at virtual address 6b6b6ceb -- EIP is at module_put+0x7/0x1f Andrew Morton
2007-03-23  2:04 ` Shaohua Li [this message]
2007-03-23  5:16   ` Greg KH
2007-03-28  3:52     ` Shaohua Li
2007-03-28  4:19       ` Greg KH
2007-03-28  4:27         ` Andrew Morton
2007-03-28  4:51           ` Greg KH
2007-03-28  5:09             ` Andrew Morton
2007-03-28  5:15               ` Greg KH
2007-03-28  5:13             ` Shaohua Li
2007-03-28  5:27               ` Greg KH
2007-03-28  5:39                 ` Shaohua Li
2007-03-28  5:58                   ` Greg KH
2007-03-28  6:49                     ` Shaohua Li
2007-03-29  8:16                       ` Shaohua Li
2007-03-30  5:18                       ` Greg KH
2007-03-30  6:33                         ` Shaohua Li
2007-03-30  7:05                           ` Greg KH
2007-03-30  7:08                             ` Shaohua Li
2007-03-30  7:51                               ` Greg KH
2007-03-30  7:55                                 ` Shaohua Li

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=1174615467.23591.3.camel@sli10-conroe.sh.intel.com \
    --to=shaohua.li@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=venkatesh.pallipadi@intel.com \
    /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