http://bugzilla.novell.com/show_bug.cgi?id=613160 http://bugzilla.novell.com/show_bug.cgi?id=613160#c yang xiaoyu 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#c2 --- Comment #2 from Pavel Volvach 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#c4 --- Comment #4 from Jiri Slaby 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#c6 --- Comment #6 from Jiri Slaby 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.

https://bugzilla.novell.com/show_bug.cgi?id=613160 https://bugzilla.novell.com/show_bug.cgi?id=613160#c8 --- Comment #8 from Jiri Slaby 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 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#c10 --- Comment #10 from Pavel Volvach 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.