On Fri, 2014-03-28 at 09:17 -0700, Don Armstrong wrote: > On Fri, 28 Mar 2014, daniel.gassen@basf.com wrote: > > any update on this bug report so far? > > Do you need further information from us? > > This looks awfully like > https://bugzilla.kernel.org/show_bug.cgi?id=6816. > > Presumably, you're writing the LOG requests to something (serial console > or similar) which cannot keep up, and the printk blocks. > > You should probably switch to using -j ULOG and ulogd instead of -j LOG. Yes, logging network events to the console without rate-limiting is a misconfiguration. Combining that with a serial console would be a particularly bad idea. This is because the kernel logs synchronously, a deliberate decision to ensure that all messages prior to a crash are actually recorded. Ben. -- Ben Hutchings Always try to do things in chronological order; it's less confusing that way.
Attachment:
signature.asc
Description: This is a digitally signed message part