Bug#697066: BUG: scheduling while atomic: swapper/0/0x00000800
found 697066 linux/3.2.35-2
severity 697066 important
quit
Joachim Ott wrote:
> This is a try with wheezy (was installed to sdb5, note the "was"). I tried
> to copy the the very same file as above from sda2 to sdb4 via "mc". mc was
> complaining about a corrupt file within the zip. When I tried to do it
> again to save a picture of the message, a panic occured, the result is that
> I can't boot from sdb5 anymore. See the attached pics.
>
> Note in the following lines, it first says "Not tainted" and later
> "Tainted".
>
> Jan 2 04:39:28 ott kernel: [ 1309.694570] EXT3-fs (sda2): using internal journal
> Jan 2 04:39:28 ott kernel: [ 1309.694578] EXT3-fs (sda2): mounted filesystem with ordered data mode
> Jan 2 04:39:45 ott kernel: [ 1326.863294] EXT4-fs (sdb4): mounted filesystem with ordered data mode. Opts: (null)
> Jan 2 04:46:37 ott kernel: [ 1738.748028] ------------[ cut here ]------------
> Jan 2 04:46:37 ott kernel: [ 1738.748038] WARNING: at /build/buildd-linux_3.2.35-2-amd64-v9djlH/linux-3.2.35/kernel/rcutree.c:374 rcu_enter_nohz+0x51/0x63()
> Jan 2 04:46:37 ott kernel: [ 1738.748042] Hardware name: M52L-S3
> Jan 2 04:46:37 ott kernel: [ 1738.748043] Modules linked in: ext3 jbd bnep rfcomm bluetooth rfkill binfmt_misc nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc loop snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec powernow_k8 mperf snd_hwdep snd_pcm radeon ttm snd_page_alloc drm_kms_helper drm snd_seq power_supply parport_pc i2c_nforce2 parport i2c_algo_bit snd_seq_device snd_timer snd psmouse pcspkr processor serio_raw evdev thermal_sys button k8temp i2c_core edac_mce_amd edac_core soundcore ext4 crc16 jbd2 mbcache sr_mod sg usb_storage cdrom sd_mod crc_t10dif ata_generic usbhid hid ohci_hcd pata_amd sata_nv libata ehci_hcd usbcore forcedeth usb_common scsi_mod [last unloaded: scsi_wait_scan]
> Jan 2 04:46:37 ott kernel: [ 1738.748098] Pid: 0, comm: swapper/0 Not tainted 3.2.0-4-amd64 #1 Debian 3.2.35-2
> Jan 2 04:46:37 ott kernel: [ 1738.748101] Call Trace:
> Jan 2 04:46:37 ott kernel: [ 1738.748103] <IRQ> [<ffffffff81046a75>] ? warn_slowpath_common+0x78/0x8c
> Jan 2 04:46:37 ott kernel: [ 1738.748112] [<ffffffff81095d35>] ? rcu_enter_nohz+0x51/0x63
> Jan 2 04:46:37 ott kernel: [ 1738.748115] [<ffffffff8104c30c>] ? irq_exit+0x5c/0x9a
> Jan 2 04:46:37 ott kernel: [ 1738.748120] [<ffffffff810241c8>] ? smp_apic_timer_interrupt+0x74/0x82
> Jan 2 04:46:37 ott kernel: [ 1738.748125] [<ffffffff81352ade>] ? apic_timer_interrupt+0x6e/0x80
> Jan 2 04:46:37 ott kernel: [ 1738.748127] <EOI> [<ffffffff81039831>] ? finish_task_switch+0xa2/0xb9
> Jan 2 04:46:37 ott kernel: [ 1738.748134] [<ffffffff8102b360>] ? native_safe_halt+0x2/0x3
> Jan 2 04:46:37 ott kernel: [ 1738.748138] [<ffffffff81014508>] ? default_idle+0x47/0x7f
> Jan 2 04:46:37 ott kernel: [ 1738.748142] [<ffffffff8101461f>] ? amd_e400_idle+0xdf/0xe4
> Jan 2 04:46:37 ott kernel: [ 1738.748146] [<ffffffff8100d24d>] ? cpu_idle+0xaf/0xf2
> Jan 2 04:46:37 ott kernel: [ 1738.748150] [<ffffffff816abb33>] ? start_kernel+0x3b3/0x3be
> Jan 2 04:46:37 ott kernel: [ 1738.748154] [<ffffffff816ab140>] ? early_idt_handlers+0x140/0x140
> Jan 2 04:46:37 ott kernel: [ 1738.748157] [<ffffffff816ab3c4>] ? x86_64_start_kernel+0x104/0x111
> Jan 2 04:46:37 ott kernel: [ 1738.748160] ---[ end trace 24da3cac68c8a28e ]---
[...]
> Time to go to sleep now.
Thanks. The tripped assertion this time is
WARN_ON_ONCE(atomic_read(&rdtp->dynticks) & 0x1);
from v2.6.32-rc1~724^2~2 (rcu: Changes from reviews: avoid casts,
fix/add warnings, improve comments, 2009-08-27).
This isn't similar to any other bug I know of. My only suggestion at
the moment is to check for hardware problems: run memtest86+, reseat
RAM, etc.
A full kernel log from a successful or unsuccessful boot would also
be useful, since it would help us get to know your hardware better.
Thanks again for your help and patience.
Regards,
Jonathan
Reply to: