From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>
Subject: 2.6.11-rc2 complains badly aboud badness in local_bh_enable
Date: Sun, 23 Jan 2005 13:01:14 +0100 [thread overview]
Message-ID: <20050123120114.GA1348@elf.ucw.cz> (raw)
Hi!
-rc1 worked fine here. -rc2 complains a lot:
Jan 23 12:59:50 amd kernel: Badness in local_bh_enable at kernel/softirq.c:140
Jan 23 12:59:50 amd kernel: [local_bh_enable+137/144] local_bh_enable+0x89/0x90
Jan 23 12:59:50 amd kernel: [ppp_start_xmit+206/560] ppp_start_xmit+0xce/0x230
Jan 23 12:59:50 amd kernel: [qdisc_restart+107/368] qdisc_restart+0x6b/0x170
Jan 23 12:59:50 amd kernel: [ip_confirm+77/96] ip_confirm+0x4d/0x60
Jan 23 12:59:50 amd kernel: [dev_queue_xmit+526/688] dev_queue_xmit+0x20e/0x2b0
Jan 23 12:59:50 amd kernel: [ip_finish_output2+220/432] ip_finish_output2+0xdc/0x1b0
Jan 23 12:59:50 amd kernel: [ip_finish_output2+0/432] ip_finish_output2+0x0/0x1b0
Jan 23 12:59:50 amd kernel: [nf_hook_slow+225/272] nf_hook_slow+0xe1/0x110
Jan 23 12:59:50 amd kernel: [ip_finish_output2+0/432] ip_finish_output2+0x0/0x1b0
Jan 23 12:59:50 amd kernel: [dst_output+0/32] dst_output+0x0/0x20
Jan 23 12:59:50 amd kernel: [ip_finish_output+494/512] ip_finish_output+0x1ee/0x200
Jan 23 12:59:50 amd kernel: [ip_finish_output2+0/432] ip_finish_output2+0x0/0x1b0
Jan 23 12:59:50 amd kernel: [dst_output+0/32] dst_output+0x0/0x20
Jan 23 12:59:50 amd kernel: [dst_output+11/32] dst_output+0xb/0x20
Jan 23 12:59:50 amd kernel: [nf_hook_slow+225/272] nf_hook_slow+0xe1/0x110
Jan 23 12:59:50 amd kernel: [dst_output+0/32] dst_output+0x0/0x20
Jan 23 12:59:50 amd kernel: [ip_push_pending_frames+996/1088] ip_push_pending_frames+0x3e4/0x440
Jan 23 12:59:50 amd kernel: [dst_output+0/32] dst_output+0x0/0x20
Jan 23 12:59:50 amd kernel: [udp_push_pending_frames+361/672] udp_push_pending_frames+0x169/0x2a0
Jan 23 12:59:50 amd kernel: [udp_sendmsg+841/1728] udp_sendmsg+0x349/0x6c0
Jan 23 12:59:50 amd kernel: [inet_sendmsg+74/112] inet_sendmsg+0x4a/0x70
Jan 23 12:59:50 amd kernel: [sock_sendmsg+190/224] sock_sendmsg+0xbe/0xe0
Jan 23 12:59:50 amd kernel: [prep_new_page+85/96] prep_new_page+0x55/0x60
Jan 23 12:59:50 amd kernel: [buffered_rmqueue+204/496] buffered_rmqueue+0xcc/0x1f0
Jan 23 12:59:50 amd kernel: [prep_new_page+85/96] prep_new_page+0x55/0x60
Jan 23 12:59:50 amd kernel: [buffered_rmqueue+204/496] buffered_rmqueue+0xcc/0x1f0
Jan 23 12:59:51 amd kernel: [anon_vma_prepare+153/240] anon_vma_prepare+0x99/0xf0
Jan 23 12:59:51 amd kernel: [autoremove_wake_function+0/80] autoremove_wake_function+0x0/0x50
Jan 23 12:59:51 amd kernel: [sys_sendto+192/224] sys_sendto+0xc0/0xe0
Jan 23 12:59:51 amd kernel: [convert_fxsr_from_user+21/224] convert_fxsr_from_user+0x15/0xe0
Jan 23 12:59:51 amd kernel: [sys_socketcall+389/592] sys_socketcall+0x185/0x250
Jan 23 12:59:51 amd kernel: [do_page_fault+0/1378] do_page_fault+0x0/0x562
Jan 23 12:59:51 amd kernel: [syscall_call+7/11] syscall_call+0x7/0xb
I probably provoke it with transmitting data over cellphone over bluetooth?
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next reply other threads:[~2005-01-23 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-23 12:01 Pavel Machek [this message]
2005-01-23 14:57 ` Marcel Holtmann
2005-01-23 22:41 ` Jasper Spaans
2005-01-24 0:42 ` Patrick McHardy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050123120114.GA1348@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome