[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#602109: Acknowledgement ([linux-2.6] 1 multicall(s) failed: cpu 0)



Hi Ian,

On Monday 06 December 2010 11:10:40 Ian Campbell wrote:
> On Fri, 2010-12-03 at 18:57 +0100, Jan Wagner wrote:
> > On Friday, 3. December 2010, Ben Hutchings wrote:
> > > It is probably filtered out of syslog because it has a low priority
> > > level.  'dmesg' should show you all the kernel log buffer.
> > 
> > attached you can find the corresponding part of the modprobes of the
> > sysreq show state and the part of the boot dmesg where the oops
> > occures. Please notice, that there is a huge time gap before mounting
> > the swap. That's likely the part of booting, where i have the
> > troubles ... I have also attached a screenshot of that part. Like you
> > can see, there is a ^C needed to proceed at that part.
> 
> Thanks for the report.
> 
> I suspect that this issue will be resolved by this commit from upstream:
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=6832032
> 3a51c2378aca433c76157d9e66104ff1e
> 
> I can do a build with this patch against squeeze/sid for test purposes
> but it looks like you are running a .bpo package. Are you able to test
> with a kernel built against squeeze/sid?

Hmm ... As the system runs lenny and is hosted in a colo, I would say that 
could be a problem. I can even try to install the package via "dpkg -i", but I 
don't know if that works.
At least I would try it, as I'm able to powercycle the box, if there is any 
problem.
If the squeeze kernel doesn't work, maybe a patch against 2.6.32-28 could be 
applied to the source of the bpo kernel and I'm trying to rebuild it.

Many thanks, Jan.
-- 
Never write mail to <waja@spamfalle.info>, you have been warned!
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GIT d-- s+: a C+++ UL++++ P+ L+++ E--- W+++ N+++ o++ K++ w--- O M V- PS PE Y++
PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h---- r+++ y++++ 
------END GEEK CODE BLOCK------

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: