linux-kernel - Re: Network problem with 2.6.18-mm1 ?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 28 Sep 2006 14:10:02 -0700
From:	"Jesse Brandeburg" <jesse.brandeburg@...il.com>
To:	"Sukadev Bhattiprolu" <sukadev@...ibm.com>
Cc:	"Auke Kok" <auke-jan.h.kok@...el.com>,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: Network problem with 2.6.18-mm1 ?

On 9/28/06, Sukadev Bhattiprolu <sukadev@...ibm.com> wrote:
> Thanks. See below for additional info
>
> Auke Kok [auke-jan.h.kok@...el.com] wrote:
> | Sukadev Bhattiprolu wrote:
> | >
> | >I am unable to get networking to work with 2.6.18-mm1 on my system.
> | >
> | >But 2.6.18 kernel on same system works fine. Here is some info about
> | >the system/debug attempts. Attached are the lspci output and config.
> | >
> | >Appreciate any help. Please let me know if you need more info.

It seems you're having interrupt delivery problems or interrupts are
getting lost.
rx_missed_errors indicates frames that were dropped due to the e1000
adapter's fifo getting full and over flowing.
> rx_no_buffer_count: 310
> rx_missed_errors: 5865
rx_no_buffer_count indicates that the driver didn't return buffers to
the hardware soon enough, but the hardware was able to store the
packet (at the time of reception) in the fifo to try again.

Both these indicate to me that there is something wrong with
interrupts.  Maybe interrupt sharing

can you possibly try a back to back connection with another linux box
and run tcpdump on both ends then ping?  it will tell us if traffic is
truely getting out and coming in okay.

also please send output of lspci -vv and cat /proc/interrupts

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