kernel BUG: scheduling while atomic: bash/2513/0x10000001
Antonio Olivares
olivares14031 at yahoo.com
Thu Aug 19 02:15:24 UTC 2010
Dear folks,
I have downloaded/compiled and installed kernel 2.6.35.2 on one of my machines.
I get the above bug with details following:
I get the message that there is a kernel oops, but I can't report it since the
kernel is not a Fedora kernel and abrt does not work :(
Is there a way I can send this to kernel developers so they can get this error
and see what if anything causes it?
BUG: scheduling while atomic: bash/2513/0x10000001
Modules linked in: ppp_deflate bsd_comp ppp_async crc_ccitt ppp_generic slhc
nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack xt_tcpudp iptable_filter
ip_tables x_tables agrserial agrmodem(P) snd_seq_dummy snd_seq_oss
snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss ipv6 pcmcia
pcmcia_core agpgart lp ppdev parport_pc parport fuse snd_hda_codec_realtek
snd_hda_intel snd_hda_codec snd_hwdep snd_pcm acer_wmi fan snd_timer rtc_cmos
rtc_core rtc_lib rfkill led_class psmouse forcedeth evdev serio_raw processor
wmi thermal sg i2c_nforce2 snd button thermal_sys soundcore snd_page_alloc
k8temp i2c_core hwmon [last unloaded: pcmcia_core]
Pid: 2513, comm: bash Tainted: P 2.6.35.2-smp #1
Call Trace:
[<c103283e>] __schedule_bug+0x5e/0x70
[<c1980ec2>] schedule+0x652/0x6b0
[<c10429d5>] ? __do_softirq+0xe5/0x1b0
[<c1981062>] _cond_resched+0x32/0x50
[<c10cd27e>] anon_vma_prepare+0x1e/0x110
[<c198399b>] ? smp_apic_timer_interrupt+0x5b/0x8a
[<c10c940d>] expand_downwards+0x1d/0x160
[<c10c955d>] expand_stack+0xd/0x10
[<c10c754c>] handle_mm_fault+0x93c/0x9a0
[<c10c76aa>] __get_user_pages+0xfa/0x360
[<c10c79b4>] get_user_pages+0x54/0x70
[<c10e31e2>] get_arg_page+0x52/0xb0
[<c14baeeb>] ? strnlen_user+0x2b/0x60
[<c10e3310>] copy_strings+0xd0/0x180
[<c10e33e9>] copy_strings_kernel+0x29/0x40
[<c10e4d1a>] do_execve+0x19a/0x2c0
[<c14bb0d9>] ? copy_to_user+0x39/0x130
[<c14bb01a>] ? strncpy_from_user+0x3a/0x70
[<c100a6c7>] sys_execve+0x37/0x70
[<c10030ce>] ptregs_execve+0x12/0x18
[<c1982fdc>] ? syscall_call+0x7/0xb
Call Trace:
[<c103283e>] __schedule_bug+0x5e/0x70
[<c1980ec2>] schedule+0x652/0x6b0
[<c10b41a5>] ? __alloc_pages_nodemask+0xd5/0x5a0
[<c1981062>] _cond_resched+0x32/0x50
[<c10cd27e>] anon_vma_prepare+0x1e/0x110
[<c10c940d>] expand_downwards+0x1d/0x160
[<c102921e>] ? kmap_atomic_prot+0x4e/0xd0
[<c10c955d>] expand_stack+0xd/0x10
[<c10c754c>] handle_mm_fault+0x93c/0x9a0
[<c10c76aa>] __get_user_pages+0xfa/0x360
[<c10c79b4>] get_user_pages+0x54/0x70
[<c10e31e2>] get_arg_page+0x52/0xb0
[<c14baeeb>] ? strnlen_user+0x2b/0x60
[<c10e3310>] copy_strings+0xd0/0x180
[<c10e33e9>] copy_strings_kernel+0x29/0x40
[<c10e4d1a>] do_execve+0x19a/0x2c0
[<c14bb01a>] ? strncpy_from_user+0x3a/0x70
[<c100a6c7>] sys_execve+0x37/0x70
[<c10030ce>] ptregs_execve+0x12/0x18
[<c1982fdc>] ? syscall_call+0x7/0xb
Regards,
Antonio
P.S
I apologize in advance for sending this, since I know that it is my own fault
since the kernel is a nonFedora kernel and this is why Fedora has stayed a
little behind the times when it comes to kernels.
More information about the users
mailing list