Re: 2.6.21-git8+ BUG: NMI Watchdog detected LOCKUP on CPU1

2007-05-08 Thread Jiri Kosina
On Tue, 8 May 2007, Andrew Morton wrote: > happens when a local process sends packets with invalid IP headers > through raw sockets. [...] > Whatever happens, that printk should be toned down, shouldn't it? We > prefer to not let unprivileged apps spam the logs. Isn't "unprivileged app sendi

Re: 2.6.21-git8+ BUG: NMI Watchdog detected LOCKUP on CPU1

2007-05-08 Thread Michal Piotrowski
On 08/05/07, Andrew Morton <[EMAIL PROTECTED]> wrote: On Tue, 08 May 2007 10:35:14 +0200 Michal Piotrowski <[EMAIL PROTECTED]> wrote: > Hi, > > / filesystem was full > > [39525.46] BUG: NMI Watchdog detected LOCKUP on CPU1, eip 08056990, registers: > [39525.468000] Modules linked in: loop i

Re: 2.6.21-git8+ BUG: NMI Watchdog detected LOCKUP on CPU1

2007-05-08 Thread Patrick McHardy
Andrew Morton wrote: > Whatever happens, that printk should be toned down, shouldn't it? We > prefer to not let unprivileged apps spam the logs. Only priviledged apps can send these packets. I've never seen it in practice except for one case that was a bug in the network stack, so I'd prefer to

Re: 2.6.21-git8+ BUG: NMI Watchdog detected LOCKUP on CPU1

2007-05-08 Thread Andrew Morton
On Tue, 08 May 2007 10:35:14 +0200 Michal Piotrowski <[EMAIL PROTECTED]> wrote: > Hi, > > / filesystem was full > > [39525.46] BUG: NMI Watchdog detected LOCKUP on CPU1, eip 08056990, > registers: > [39525.468000] Modules linked in: loop ipt_MASQUERADE iptable_nat nf_nat > autofs4 af_packe