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@xxxxxxxxx> > To: "Andrew Morton" <akpm@xxxxxxxxxxxxxxxxxxxx> > Cc: LKML <linux-kernel@xxxxxxxxxxxxxxx>, > linux-wireless@xxxxxxxxxxxxxxx > 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@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > > - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
