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

2010-12-07 Thread Ian Campbell
On Tue, 2010-12-07 at 16:05 +0100, Jan Wagner wrote: > Hi Ian, > > On Monday 06 December 2010 12:29:58 you wrote: > > > 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 > > > b

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

2010-12-06 Thread Jan Wagner
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 kerne

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

2010-12-06 Thread Ian Campbell
retitle 602109 xen: dom0: ACPI crash in xen_acpi_processor_add thanks Hi Jan, 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

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

2010-12-04 Thread Jan Wagner
Hi Ben, On Samstag, 4. Dezember 2010, you wrote: > Module loading is serialised by a lock. Because the 'oops' occurs > during module loading, the locks is never released and no more modules > can be loaded. So we don't need to worry about that - it's just a > symptom of the initial 'oops'. > >

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

2010-12-04 Thread Ben Hutchings
On Fri, 2010-12-03 at 18:57 +0100, Jan Wagner wrote: > Hi Ben, > > 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 p

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

2010-12-03 Thread Ben Hutchings
On Fri, 2010-12-03 at 12:33 +0100, Jan Wagner wrote: > Hi Ben, > > thanks for your reply. > > On Friday 03 December 2010 06:29:56 Ben Hutchings wrote: > > On Thu, 2010-12-02 at 22:00 +0100, Jan Wagner wrote: > > Please can you log information about the state of tasks by running: > > > > echo t >

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

2010-12-03 Thread Jan Wagner
Hi Ben, thanks for your reply. On Friday 03 December 2010 06:29:56 Ben Hutchings wrote: > On Thu, 2010-12-02 at 22:00 +0100, Jan Wagner wrote: > Please can you log information about the state of tasks by running: > > echo t > /proc/sysrq-trigger > > then send the messages for the modprobe tasks

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

2010-12-02 Thread Ben Hutchings
On Thu, 2010-12-02 at 22:00 +0100, Jan Wagner wrote: > Hi there, > > today I updated to linux-image-2.6.32-bpo.5-xen-686 2.6.32-28~bpo50+1 and > recognized that I have a couple of modprobe processes still running after > booting: [...] Please can you log information about the state of tasks by

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

2010-12-02 Thread Jan Wagner
Hi there, today I updated to linux-image-2.6.32-bpo.5-xen-686 2.6.32-28~bpo50+1 and recognized that I have a couple of modprobe processes still running after booting: root 966 0.2 0.0 2308 800 ?S