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

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



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 > /proc/sysrq-trigger
> > 
> > then send the messages for the modprobe tasks.
> 
> I guess it should be found in the syslog.
> 
> mordor:~# echo t > /proc/sysrq-trigger
> mordor:~# grep modprobe /var/log/syslog
> 
> But it seems not tobe found there.

It is probably filtered out of syslog because it has a low priority
level.  'dmesg' should show you all the kernel log buffer.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

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


Reply to: