[linux-cifs-client] BUG: scheduling while atomic (2.6.24 ubuntu kernel)

Jeff Layton jlayton at redhat.com
Wed Jun 17 12:43:51 GMT 2009


On Wed, 17 Jun 2009 06:32:14 +0200
Bosko Radivojevic <bosko.radivojevic at gmail.com> wrote:

> Hi all,
> 
> a few moments ago I got a complete system lockup. From the logs it
> looks like CIFS problem:
> Jun 17 05:38:44 forum-db kernel: [    0.000000]  CIFS VFS: No response
> for cmd 162 mid 44085
> Jun 17 05:39:44 forum-db kernel: [    0.000000]  CIFS VFS: server not responding
> Jun 17 05:39:44 forum-db kernel: [    0.000000]  CIFS VFS: No response
> for cmd 162 mid 44091
> Jun 17 05:40:44 forum-db kernel: [    0.000000]  CIFS VFS: server not responding
> Jun 17 05:40:44 forum-db kernel: [    0.000000]  CIFS VFS: No response
> for cmd 162 mid 44097
> Jun 17 05:40:47 forum-db kernel: [    0.000000] BUG: scheduling while
> atomic: cp/20245/0xffffffff
> 
> It is ubuntu system with their latest kernel (2.6.24-23-generic #1 SMP
> Wed Apr 1 21:43:24 UTC 2009 x86_64 GNU/Linux). I've checked in the
> source for this specific kernel and
> http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=a403a0a370946e7dbcda6464a3509089daee54bc
> seems applied.
> 
> What could be a problem?
> 
> Sincerely,
> Bosko
> 
> PS. I'm not subscribed to the linux-cifs-* lists, please cc me if answering

Hmm...don't think I've ever seen CIFS cause such a problem. My
suspicion would be that something occurred elsewhere (maybe lower in
the networking stack). In order to diagnose it, you'll probably need to
look at the stack trace that was generated during the crash.

-- 
Jeff Layton <jlayton at redhat.com>


More information about the linux-cifs-client mailing list