* One line summary of the problem
After applying the 2.6.33.1-vs2.3.0.36.30.4 patch I see "scheduling
while atomic" problems while accessing cifs shares
* Full description of the problem
I've been running 2.6.33.y for quite some time and had a very stable
experience (no crash whatsoever for several weeks). I wanted to try
out vserver and applied the aforementioned patch.
I've been seeing seeing the "scheduling while atomic" Oopses a few
times since then, always starting with cifs_readpages. (kernel log
attached)
* Kernel version (from /proc/version)
Linux version 2.6.33.1-vs2.3.0.36.30.4-vserver (max@nemesis) (gcc
version 4.4.3 20100108 (prerelease) (Debian 4.4.2-9) ) #23 SMP Mon Mar
29 05:51:08 CEST 2010
#
# Linux VServer
#
CONFIG_VSERVER_AUTO_LBACK=y
CONFIG_VSERVER_AUTO_SINGLE=y
CONFIG_VSERVER_COWBL=y
# CONFIG_VSERVER_VTIME is not set
CONFIG_VSERVER_DEVICE=y
CONFIG_VSERVER_PROC_SECURE=y
CONFIG_VSERVER_HARDCPU=y
CONFIG_VSERVER_IDLETIME=y
# CONFIG_VSERVER_IDLELIMIT is not set
# CONFIG_TAGGING_NONE is not set
# CONFIG_TAGGING_UID16 is not set
# CONFIG_TAGGING_GID16 is not set
CONFIG_TAGGING_ID24=y
# CONFIG_TAGGING_INTERN is not set
# CONFIG_TAG_NFSD is not set
# CONFIG_VSERVER_PRIVACY is not set
CONFIG_VSERVER_CONTEXTS=256
CONFIG_VSERVER_WARN=y
# CONFIG_VSERVER_DEBUG is not set
CONFIG_VSERVER=y
* Output of the Oops.. message (if applicable) with symbolic
information resolved (see Documentation/oops-tracing.txt in the kernel
source)
* Processor information (from /proc/cpuinfo)
* Module information (from /proc/modules)
see attached log for all three
Probably someone running the same version can try to reproduce this
--- anyway, hope it helps.
Regards,
Max