[Bug 613160] New: Many kernel reports: ratelimit callbacks suppressed
http://bugzilla.novell.com/show_bug.cgi?id=613160 http://bugzilla.novell.com/show_bug.cgi?id=613160#c0 Summary: Many kernel reports: ratelimit callbacks suppressed Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Minor Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: pavel.volvach@gmail.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100317 SUSE/3.5.9-0.1.1 Firefox/3.5.9 We have many kernel reports about callbacks suppressed errors which was appeared in messages.log after the last few (3-4) kernel updates. Each regular update increase the number of messages and the number of callbacks suppressed. What can cause this errors? Here is a fragment of messages.log: Jun 10 09:53:09 server kernel: __ratelimit: 22 callbacks suppressed Jun 10 09:53:15 server kernel: __ratelimit: 32 callbacks suppressed Jun 10 09:53:20 server kernel: __ratelimit: 24 callbacks suppressed Jun 10 09:53:26 server kernel: __ratelimit: 18 callbacks suppressed Jun 10 09:53:31 server kernel: __ratelimit: 265 callbacks suppressed Jun 10 09:53:36 server kernel: __ratelimit: 511 callbacks suppressed Jun 10 09:53:42 server kernel: __ratelimit: 509 callbacks suppressed Jun 10 09:53:47 server kernel: __ratelimit: 508 callbacks suppressed Jun 10 09:53:52 server kernel: __ratelimit: 511 callbacks suppressed Jun 10 09:53:58 server kernel: __ratelimit: 500 callbacks suppressed Jun 10 09:54:03 server kernel: __ratelimit: 514 callbacks suppressed Jun 10 09:54:08 server kernel: __ratelimit: 509 callbacks suppressed Jun 10 09:54:13 server kernel: __ratelimit: 527 callbacks suppressed Jun 10 09:54:18 server kernel: __ratelimit: 280 callbacks suppressed Jun 10 09:54:23 server kernel: __ratelimit: 26 callbacks suppressed Jun 10 09:54:28 server kernel: __ratelimit: 30 callbacks suppressed Jun 10 09:54:34 server kernel: __ratelimit: 17 callbacks suppressed Reproducible: Always Steps to Reproduce: Do not know how to reproduce Actual Results: Error messages appear all the time Expected Results: Error message should not be appear -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=613160 http://bugzilla.novell.com/show_bug.cgi?id=613160#c yang xiaoyu <xyyang@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyyang@novell.com AssignedTo|bnc-team-screening@forge.pr |kernel-maintainers@forge.pr |ovo.novell.com |ovo.novell.com -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=613160 http://bugzilla.novell.com/show_bug.cgi?id=613160#c1 Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |jslaby@novell.com InfoProvider| |pavel.volvach@gmail.com --- Comment #1 from Jiri Slaby <jslaby@novell.com> 2010-07-28 13:24:10 UTC --- (In reply to comment #0)
What can cause this errors?
Usually a bug somewhere (in SW or HW) which causes kernel to report something too frequently. Could you attach whole dmesg to see what messages were suppressed? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=613160 http://bugzilla.novell.com/show_bug.cgi?id=613160#c2 --- Comment #2 from Pavel Volvach <pavel.volvach@gmail.com> 2010-08-02 07:44:18 UTC --- Created an attachment (id=379756) --> (http://bugzilla.novell.com/attachment.cgi?id=379756) Messages.log -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=613160 http://bugzilla.novell.com/show_bug.cgi?id=613160#c3 --- Comment #3 from Pavel Volvach <pavel.volvach@gmail.com> 2010-08-02 07:46:26 UTC --- (From update of attachment 379756) Thank you for your reply! In the attachment the full messages.log which contain a few days -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=613160 http://bugzilla.novell.com/show_bug.cgi?id=613160#c4 --- Comment #4 from Jiri Slaby <jslaby@novell.com> 2010-08-02 08:03:47 UTC --- (In reply to comment #3)
In the attachment the full messages.log which contain a few days
But it is not enough. We need to see what happened before the first ratelimit message since boot. So could you attach an older log where this can be seen? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=613160 http://bugzilla.novell.com/show_bug.cgi?id=613160#c5 --- Comment #5 from Pavel Volvach <pavel.volvach@gmail.com> 2010-08-02 08:08:25 UTC --- Created an attachment (id=379758) --> (http://bugzilla.novell.com/attachment.cgi?id=379758) messagesOLD.log This is the oldest file that we could find -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=613160 http://bugzilla.novell.com/show_bug.cgi?id=613160#c6 --- Comment #6 from Jiri Slaby <jslaby@novell.com> 2010-08-02 08:17:50 UTC --- (In reply to comment #5)
This is the oldest file that we could find
We don't need the latest, but the one which contains the kernel start. From uptime command you can guess the log. The last 11.1 kernel update is from July, so depending on when you updated, it should be in last 2-3 messages log. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=613160 http://bugzilla.novell.com/show_bug.cgi?id=613160#c7 --- Comment #7 from Pavel Volvach <pavel.volvach@gmail.com> 2010-08-02 08:44:43 UTC --- Created an attachment (id=379766) --> (http://bugzilla.novell.com/attachment.cgi?id=379766) Messages.log Update and running server were held on Jul 27 at 15:05:43 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=613160 https://bugzilla.novell.com/show_bug.cgi?id=613160#c8 --- Comment #8 from Jiri Slaby <jslaby@novell.com> 2010-11-07 15:24:55 UTC --- Hm, it looks like this: 0000:05:00.0: eth0: Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX br0: topology change detected, propagating br0: port 1(eth0) entering forwarding state suspend: event channel 58 RPC: Registered udp transport module. RPC: Registered tcp transport module. Installing knfsd (copyright (C) 1996 okir@monad.swb.de). tun: Universal TUN/TAP device driver, 1.6 tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com> device tap1.0 entered promiscuous mode br0: topology change detected, propagating br0: port 2(tap1.0) entering forwarding state device vif1.0 entered promiscuous mode br0: topology change detected, propagating br0: port 3(vif1.0) entering forwarding state NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory NFSD: starting 90-second grace period (cdrom_add_media_watch() file=drivers/xen/blkback/cdrom.c, line=108) nodename:backend/vbd/1/5632 (cdrom_is_type() file=drivers/xen/blkback/cdrom.c, line=95) type:0 vbd vbd-1-768: 2 creating vbd structure __ratelimit: 42 callbacks suppressed __ratelimit: 56 callbacks suppressed And unfortunately we cannot guess anything from that. Is this reproducible in 11.3? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=613160 https://bugzilla.novell.com/show_bug.cgi?id=613160#c9 --- Comment #9 from Pavel Volvach <pavel.volvach@gmail.com> 2010-11-24 10:05:20 UTC --- Thank you for your reply. Unfortunately, we have a difficult configuration, and migrating to version 11.3 can cause alot of problems. Also we tried to put the latest kernel version 6.2.1936, but the error still appears. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=613160 https://bugzilla.novell.com/show_bug.cgi?id=613160#c10 --- Comment #10 from Pavel Volvach <pavel.volvach@gmail.com> 2010-11-25 12:06:11 UTC --- It seems that we have found the source of the problem. Tonight, one of our network interfaces is down due to buffer overflow. So we switched it off and after the server recovering errors are gone. Thank you for your help! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=613160 https://bugzilla.novell.com/show_bug.cgi?id=613160#c11 Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|pavel.volvach@gmail.com | Resolution| |WONTFIX --- Comment #11 from Jiri Slaby <jslaby@novell.com> 2011-03-02 21:16:34 UTC --- Ok. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com