On Mon, Oct 23, 2006 at 02:50:44PM -0400, Mikhail Teterin wrote:
> ? 23 ??? 2006 13:37, Mikhail Teterin ???:
> > > We aren't currently speaking about performance, we need to know whether
> > > kernel with DEVICE_POLLING option makes NIC work stable.
> >
> > Yes, that seems to be the
On Saturday 21 October 2006 13:33, Gleb Smirnoff wrote:
= We aren't currently speaking about performance, we need to know whether
= kernel with DEVICE_POLLING option makes NIC work stable.
Having noticed today's em-driver update, I rebuilt world/kernel and tried the
dump-test again.
The kernel ha
On Sat, Oct 21, 2006 at 07:09:41PM -0400, Kris Kennaway wrote:
> On Sat, Oct 21, 2006 at 09:32:50PM +0400, Gleb Smirnoff wrote:
> > On Sat, Oct 21, 2006 at 12:57:52PM -0400, Kris Kennaway wrote:
> > K> On Sat, Oct 21, 2006 at 10:17:06AM +0400, Gleb Smirnoff wrote:
> > K> > On Thu, Oct 19, 2006 at 0
понеділок 23 жовтень 2006 13:37, Mikhail Teterin написав:
> > We aren't currently speaking about performance, we need to know whether
> > kernel with DEVICE_POLLING option makes NIC work stable.
>
> Yes, that seems to be the case...
I spoke too soon :-( It took a lot longer this time (without poll
субота 21 жовтень 2006 13:33, Gleb Smirnoff написав:
> We aren't currently speaking about performance, we need to know whether
> kernel with DEVICE_POLLING option makes NIC work stable.
Yes, that seems to be the case... After I got to the machine's console
(there was no network access) and turning
On Sat, Oct 21, 2006 at 09:32:50PM +0400, Gleb Smirnoff wrote:
> On Sat, Oct 21, 2006 at 12:57:52PM -0400, Kris Kennaway wrote:
> K> On Sat, Oct 21, 2006 at 10:17:06AM +0400, Gleb Smirnoff wrote:
> K> > On Thu, Oct 19, 2006 at 02:18:13PM -0700, Jack Vogel wrote:
> K> > J> The engineer in our test g
On Sat, Oct 21, 2006 at 10:17:06AM +0400, Gleb Smirnoff wrote:
> On Thu, Oct 19, 2006 at 02:18:13PM -0700, Jack Vogel wrote:
> J> The engineer in our test group has installed 6.2 BETA2 and attempted via a
> J> number of tests to reproduce this problem, the machine even shares the em
> J> interrupt
= I'd appreciate if people who are observing the problem will report
= whether adding DEVICE_POLLING option to kernel config helps them
= or not. This will help to tell whether the problem is in the above
= quote or in the import of new versions from vendor.
I tried this yesterday -- before writin
On Sat, Oct 21, 2006 at 01:00:08PM -0400, Mikhail Teterin wrote:
M> = I'd appreciate if people who are observing the problem will report
M> = whether adding DEVICE_POLLING option to kernel config helps them
M> = or not. This will help to tell whether the problem is in the above
M> = quote or in the
On Sat, Oct 21, 2006 at 12:57:52PM -0400, Kris Kennaway wrote:
K> On Sat, Oct 21, 2006 at 10:17:06AM +0400, Gleb Smirnoff wrote:
K> > On Thu, Oct 19, 2006 at 02:18:13PM -0700, Jack Vogel wrote:
K> > J> The engineer in our test group has installed 6.2 BETA2 and attempted
via a
K> > J> number of tes
On Thu, Oct 19, 2006 at 12:18:16PM -0700, Jeremy Chadwick wrote:
J> > A bit more helpfull, but unfortunately not much is a datapoint saying no
J> > problems April 3rd and watchdog timeouts after September 28 RELENG_6. I
J> > know, probably too vague to be of any use, but there it is.
J>
J> Someone
On Thu, Oct 19, 2006 at 02:18:13PM -0700, Jack Vogel wrote:
J> The engineer in our test group has installed 6.2 BETA2 and attempted via a
J> number of tests to reproduce this problem, the machine even shares the em
J> interrupt with usb, and yet so far he has been unsuccessful.
I've failed to repr
On 10/20/06, Bill Paul <[EMAIL PROTECTED]> wrote:
[...]
> > Another thing that might be handy is improving the watchdog timeout
> > message so that it dumps the state of the ICR and ICM registers (and
> > maybe some other interesting driver and/or device state). The timeout
> > implies no inter
[...]
> > Another thing that might be handy is improving the watchdog timeout
> > message so that it dumps the state of the ICR and ICM registers (and
> > maybe some other interesting driver and/or device state). The timeout
> > implies no interrupts were delivered for a Long Time (tm). If the
>
> >
> > Just out of curiosity, what sort of torture tests does Intel do, in
> > general, on the em driver on FreeBSD? One thing that I've found which
> > works wonders at exposing race conditions is the Smartbits bi-directional
> > IP forwarding test. Put two NICs in a system, configure for it for
On 10/20/06, Bill Paul <[EMAIL PROTECTED]> wrote:
> This is exactly the test that Andre and I were running, though only in
> one direction (I think due to lack of hardware for a full test).
Yes, but did you do it with a Smartbits though, or just with a couple of
other FreeBSD machines? Unfortun
Bill Paul wrote:
Yes, but did you do it with a Smartbits though, or just with a couple of
other FreeBSD machines? Unfortunately, a typical FreeBSD system on its own
won't generate frames anywhere near fast enough to really torture test a
gigE interface. At best you might hit around 20 to 300
> Bill Paul wrote:
> > [Charset ISO-8859-1 unsupported, filtering to ASCII...]
> >
> >>On 10/19/06, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> >>
> >>>On Thu, Oct 19, 2006 at 02:18:13PM -0700, Jack Vogel wrote:
> >>>
> The engineer in our test group has installed 6.2 BETA2 and attempted via a
On 10/20/06, Scott Long <[EMAIL PROTECTED]> wrote:
Bill Paul wrote:
> [Charset ISO-8859-1 unsupported, filtering to ASCII...]
>
>>On 10/19/06, Kris Kennaway <[EMAIL PROTECTED]> wrote:
>>
>>>On Thu, Oct 19, 2006 at 02:18:13PM -0700, Jack Vogel wrote:
>>>
The engineer in our test group has inst
Bill Paul wrote:
[Charset ISO-8859-1 unsupported, filtering to ASCII...]
On 10/19/06, Kris Kennaway <[EMAIL PROTECTED]> wrote:
On Thu, Oct 19, 2006 at 02:18:13PM -0700, Jack Vogel wrote:
The engineer in our test group has installed 6.2 BETA2 and attempted via a
number of tests to reproduce
On 10/20/06, Bill Paul <[EMAIL PROTECTED]> wrote:
[Charset ISO-8859-1 unsupported, filtering to ASCII...]
> On 10/19/06, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> > On Thu, Oct 19, 2006 at 02:18:13PM -0700, Jack Vogel wrote:
> > > The engineer in our test group has installed 6.2 BETA2 and attemp
[Charset ISO-8859-1 unsupported, filtering to ASCII...]
> On 10/19/06, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> > On Thu, Oct 19, 2006 at 02:18:13PM -0700, Jack Vogel wrote:
> > > The engineer in our test group has installed 6.2 BETA2 and attempted via a
> > > number of tests to reproduce this pr
On Thu, Oct 19, 2006 at 02:23:54PM -0700, Jack Vogel wrote:
> Other suggestions?
Is the hardware the same? ACPI being used? APIC being used?
How about doing something that shares interrupts simultaneously,
like copying mass amounts of data to/from a USB hard disk via
USB 2.0 (hence using usb) wh
On Thu, Oct 19, 2006 at 05:29:55PM -0400, Kris Kennaway wrote:
> On Thu, Oct 19, 2006 at 02:23:54PM -0700, Jack Vogel wrote:
> > On 10/19/06, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> > >On Thu, Oct 19, 2006 at 02:18:13PM -0700, Jack Vogel wrote:
> > >> The engineer in our test group has installed
On Thu, Oct 19, 2006 at 02:23:54PM -0700, Jack Vogel wrote:
> On 10/19/06, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> >On Thu, Oct 19, 2006 at 02:18:13PM -0700, Jack Vogel wrote:
> >> The engineer in our test group has installed 6.2 BETA2 and attempted via
> >a
> >> number of tests to reproduce th
On 10/19/06, Kris Kennaway <[EMAIL PROTECTED]> wrote:
On Thu, Oct 19, 2006 at 02:18:13PM -0700, Jack Vogel wrote:
> The engineer in our test group has installed 6.2 BETA2 and attempted via a
> number of tests to reproduce this problem, the machine even shares the em
> interrupt with usb, and yet
On Thu, Oct 19, 2006 at 02:18:13PM -0700, Jack Vogel wrote:
> The engineer in our test group has installed 6.2 BETA2 and attempted via a
> number of tests to reproduce this problem, the machine even shares the em
> interrupt with usb, and yet so far he has been unsuccessful.
What tests is he runni
The engineer in our test group has installed 6.2 BETA2 and attempted via a
number of tests to reproduce this problem, the machine even shares the em
interrupt with usb, and yet so far he has been unsuccessful.
I have an Intel driver about to be released, it is close, but not identical to
the 6.2
Jack Vogel wrote:
On 10/19/06, Remko Lodder <[EMAIL PROTECTED]> wrote:
Kip Macy wrote:
>
> On Wed, 18 Oct 2006, Jack Vogel wrote:
>> I'm a bit confused from the way you worded this, do you have watchdogs
>> with em, or you use em to avoid them?
>
> I have watchdogs with the current (post vendor
On Thu, Oct 19, 2006 at 09:02:21PM +0200, Erwin Lansing wrote:
> A bit more helpfull, but unfortunately not much is a datapoint saying no
> problems April 3rd and watchdog timeouts after September 28 RELENG_6. I
> know, probably too vague to be of any use, but there it is.
Someone else has already
On Thu, Oct 19, 2006 at 12:13:33PM -0700, Jack Vogel wrote:
> On 10/19/06, Erwin Lansing <[EMAIL PROTECTED]> wrote:
> >On Thu, Oct 19, 2006 at 11:40:16AM -0700, Jack Vogel wrote:
> >> On 10/19/06, Remko Lodder <[EMAIL PROTECTED]> wrote:
> >> >Kip Macy wrote:
> >> >>
> >> >> On Wed, 18 Oct 2006, Jac
On 10/19/06, Erwin Lansing <[EMAIL PROTECTED]> wrote:
On Thu, Oct 19, 2006 at 11:40:16AM -0700, Jack Vogel wrote:
> On 10/19/06, Remko Lodder <[EMAIL PROTECTED]> wrote:
> >Kip Macy wrote:
> >>
> >> On Wed, 18 Oct 2006, Jack Vogel wrote:
> >>> I'm a bit confused from the way you worded this, do yo
On Thu, Oct 19, 2006 at 11:40:16AM -0700, Jack Vogel wrote:
> On 10/19/06, Remko Lodder <[EMAIL PROTECTED]> wrote:
> >Kip Macy wrote:
> >>
> >> On Wed, 18 Oct 2006, Jack Vogel wrote:
> >>> I'm a bit confused from the way you worded this, do you have watchdogs
> >>> with em, or you use em to avoid t
On 10/19/06, Remko Lodder <[EMAIL PROTECTED]> wrote:
Kip Macy wrote:
>
> On Wed, 18 Oct 2006, Jack Vogel wrote:
>> I'm a bit confused from the way you worded this, do you have watchdogs
>> with em, or you use em to avoid them?
>
> I have watchdogs with the current (post vendor update) em driver,
Kip Macy wrote:
On Wed, 18 Oct 2006, Jack Vogel wrote:
I'm a bit confused from the way you worded this, do you have watchdogs
with em, or you use em to avoid them?
I have watchdogs with the current (post vendor update) em driver, but
not with an older (pre vendor update) version of it.
Sam
On Wed, 18 Oct 2006, Kris Kennaway wrote:
I have been working with someone's system that has em shared with fxp,
and a simple fetch over the em (e.g. of a 10 GB file of zeroes) is
enough to produce watchdog timeouts after a few seconds.
As previously mentioned, changing the INTR_FAST to INTR_MP
On Wed, 18 Oct 2006, Jack Vogel wrote:
> On 10/18/06, Kip Macy <[EMAIL PROTECTED]> wrote:
> > I have a Sun T2000 that I generally run with the em driver from as of
> > July in order to avoid watchdog timeouts. One trivial scenario that
> > reproduces the problem with 100% consistency is running
Awesome, this is the kind of data that will help.
I'll see what I can do to get something repro'd.
Jack
On 10/18/06, Albert Shih <[EMAIL PROTECTED]> wrote:
Le 19/10/2006 01:03:40+0200, Albert Shih a écrit
> Le 18/10/2006 10:46:30-0700, Jack Vogel a écrit
> > I think there may be a few diff
On 10/18/06, Albert Shih <[EMAIL PROTECTED]> wrote:
>
> There is also a hardware eeprom issue on systems with an 82573
> type NIC on SOME systems. There is a utility to fix that, if you
and on HP ?
your system does not have 573 NICs, (what you show are 546) do you
have others that are?
Jack
_
Le 19/10/2006 01:03:40+0200, Albert Shih a ?crit
> Le 18/10/2006 10:46:30-0700, Jack Vogel a ?crit
> > I think there may be a few different problems going on with the em driver
> > on 6.2 that are being lumped under the general description of network
> > hangs. In order to solve these I need a
Le 18/10/2006 10:46:30-0700, Jack Vogel a ?crit
> I think there may be a few different problems going on with the em driver
> on 6.2 that are being lumped under the general description of network
> hangs. In order to solve these I need a reproducible failure, either on a
> system here at Intel, o
On Wed, Oct 18, 2006 at 03:31:53PM -0700, Jack Vogel wrote:
> On 10/18/06, Kip Macy <[EMAIL PROTECTED]> wrote:
> >I have a Sun T2000 that I generally run with the em driver from as of
> >July in order to avoid watchdog timeouts. One trivial scenario that
> >reproduces the problem with 100% consiste
On 10/18/06, Kip Macy <[EMAIL PROTECTED]> wrote:
I have a Sun T2000 that I generally run with the em driver from as of
July in order to avoid watchdog timeouts. One trivial scenario that
reproduces the problem with 100% consistency is running the ghc
configure script (a 20kloc shell script) over
I have a Sun T2000 that I generally run with the em driver from as of
July in order to avoid watchdog timeouts. One trivial scenario that
reproduces the problem with 100% consistency is running the ghc
configure script (a 20kloc shell script) over NFS. As the T2000
doesn't exactly represent "typic
I think there may be a few different problems going on with the em driver
on 6.2 that are being lumped under the general description of network
hangs. In order to solve these I need a reproducible failure, either on a
system here at Intel, or someone who is willing to be a remote guinea
pig :)
I
45 matches
Mail list logo
