Re: unable to handle kernel NULL pointer / tty / 2.6.31-vanilla/ still persists

[Denys Fedoryschenko]

This time i didnt  notice anything suspicious. From daemons - zebra, 
ssh/telnet, snmpd (net-snmp). Job - NAT/firewall, QoS (HFSC/HTB) and routing. 
Nothing else (it is semi-embedded system with busybox).

Sep 15 10:04:46 10.22.24.2 globax: [default][2846]B/G 0/100|buf 
1328692B+4478B/941P 69428216/942/74260 (globalproof1) spd 996330<1875000 sock 
128000>64000>64000 rtt 0.393943 delay 0 pps 705 so 0 st 0 dr
Sep 15 10:04:50 10.22.24.2 ripd[5017]: rip_read: cannot find interface for 
packet from 80.83.24.49 port 520
Sep 15 10:04:51 10.22.24.2 kernel: [273169.803628] BUG: unable to handle 
kernel NULL pointer dereference at (null)
Sep 15 10:04:51 10.22.24.2 kernel: [273169.803710] IP: [<c0250f08>] 
process_echoes+0x65/0x240
Sep 15 10:04:51 10.22.24.2 kernel: [273169.803785] *pdpt = 000000002f97d001 
*pde = 0000000000000000

Latest ssh bruteforce attempts was 10-20 minutes ago.

On Tuesday 15 September 2009 18:04:55 Greg KH wrote:
> On Tue, Sep 15, 2009 at 10:32:53AM +0300, Denys Fedoryschenko wrote:
> > Kernel 2.6.31-rc7
> > x86 , 32-bit
> > gcc 4.4.1
> >
> > Happened on heavy network load, looks like as previous one, seems problem
> > still persists.
> > It is hyperthreading Xeon, as i heard on such CPU's SMP bugs most easy to
> > trigger. But for me triggered after few days of operation.
> >
> > Here is oops:
>
> Ugh.
>
> What are you doing at the time of this happening?  What kind of load is
> on the system?
>
> thanks,
>
> greg k-h


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/