Prev: support for drives larger than 2TiB
Next: cfq-iosched: don't allow aliased requests to starve others
From: Allan, Bruce W on 10 Aug 2010 12:40
On Tuesday, August 10, 2010 5:05 AM, Marc Haber wrote:
> On Wed, Aug 04, 2010 at 12:23:45PM -0600, Tantilov, Emil S wrote:
>> Looking at your lspci output - your system has a slightly different
>> HW, but I don't know if this is significant.
>>
>> Are you loading the kernel with any parameters (cat /proc/cmdline)?
>
> BOOT_IMAGE=/vmlinuz-2.6.35-zgws1 root=/dev/mapper/root ro
> resume=/dev/mapper/swap0 quiet splash radeon.modeset=1
>
>> Do you have firewall configured (iptables -L)?
>
> I am working pretty intensively with virtual machines which are natted
> here and there. I have a handful of MASQUERADE rules in the
> nat/POSTROUTING chain, but that's it.
>
>> Also now that 2.6.35 is out - could you give it a try and see if the
>> situation had improved?
>
> Tried, no improvement.
>
> Greetings
> Marc

[adding e1000-devel, the Intel wired ethernet developers mailing list]

We have had other recent reports of issues with this part that are due to
ASPM L1 being enabled. Would you please try disabling L1 after the driver
is loaded as follows (assuming your adapter is still PCI bus/device/number
02:00.0 as indicated in the lspci output you provided earlier):
1) First check the hexadecimal value of the LnkCtl register -
# setpci -s 2:0.0 0xf0
2) Disable ASPM (both L0s and L1) by zeroing out bits 0 and 1 in the value
returned by the previous step. For example, if it returned 42 (hex 42,
that is) -
# setpci -s 2:0.0 0xf0=0x40
3) Confirm ASPM is disabled by checking the output from lspci again.

Please let us know if this helps your situation, thanks.
Bruce.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Marc Haber on 12 Aug 2010 07:00
Hi,

On Tue, Aug 10, 2010 at 09:34:52AM -0700, Allan, Bruce W wrote:
> [adding e1000-devel, the Intel wired ethernet developers mailing list]

Thanks.

> We have had other recent reports of issues with this part that are due to
> ASPM L1 being enabled. Would you please try disabling L1 after the driver
> is loaded as follows (assuming your adapter is still PCI bus/device/number
> 02:00.0 as indicated in the lspci output you provided earlier):
> 1) First check the hexadecimal value of the LnkCtl register -
> # setpci -s 2:0.0 0xf0

$ sudo setpci --version
setpci version 3.1.7
$ sudo setpci -s 2:0.0 0xf0
setpci: Missing width.
Try `setpci --help' for more information.
$

Looking at --help doesn't help me, sorry.

Greetings
Marc

--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Allan, Bruce W on 12 Aug 2010 12:20
On Thursday, August 12, 2010 3:50 AM, Marc Haber wrote:
> Hi,
>
> On Tue, Aug 10, 2010 at 09:34:52AM -0700, Allan, Bruce W wrote:
>> [adding e1000-devel, the Intel wired ethernet developers mailing
>> list]
>
> Thanks.
>
>> We have had other recent reports of issues with this part that are
>> due to ASPM L1 being enabled. Would you please try disabling L1
>> after the driver is loaded as follows (assuming your adapter is
>> still PCI bus/device/number 02:00.0 as indicated in the lspci output
>> you provided earlier): 1) First check the hexadecimal value of the
>> LnkCtl register - # setpci -s 2:0.0 0xf0
>
> $ sudo setpci --version
> setpci version 3.1.7
> $ sudo setpci -s 2:0.0 0xf0
> setpci: Missing width.
> Try `setpci --help' for more information.
> $
>
> Looking at --help doesn't help me, sorry.
>
> Greetings
> Marc

Hmm, that's a newer version than I am familiar with. Apparently in
more recent versions, the tool is requiring a width be specified for
unnamed registers and/or registers for which the width is unknown.
That being the case, append the width specifier .B (one byte) to the
register address. For example:

# setpci -s 2:0.0 0xf0.B

HTH,
Bruce.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Marc Haber on 12 Aug 2010 21:30
Hi Bruce,

On Tue, Aug 10, 2010 at 09:34:52AM -0700, Allan, Bruce W wrote:
> We have had other recent reports of issues with this part that are due to
> ASPM L1 being enabled. Would you please try disabling L1 after the driver
> is loaded as follows (assuming your adapter is still PCI bus/device/number
> 02:00.0 as indicated in the lspci output you provided earlier):
> 1) First check the hexadecimal value of the LnkCtl register -
> # setpci -s 2:0.0 0xf0
> 2) Disable ASPM (both L0s and L1) by zeroing out bits 0 and 1 in the value
> returned by the previous step. For example, if it returned 42 (hex 42,
> that is) -
> # setpci -s 2:0.0 0xf0=0x40
> 3) Confirm ASPM is disabled by checking the output from lspci again.

It returned 42, and after setting 0x40, LnkCtl now says "ASPM Disabled".

I'll dock the system now and will report after the weekend or after
the first crash.

Greetings
Marc

--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Marc Haber on 13 Aug 2010 04:10
On Fri, Aug 13, 2010 at 03:25:51AM +0200, Marc Haber wrote:
> On Tue, Aug 10, 2010 at 09:34:52AM -0700, Allan, Bruce W wrote:
> > We have had other recent reports of issues with this part that are due to
> > ASPM L1 being enabled. Would you please try disabling L1 after the driver
> > is loaded as follows (assuming your adapter is still PCI bus/device/number
> > 02:00.0 as indicated in the lspci output you provided earlier):
> > 1) First check the hexadecimal value of the LnkCtl register -
> > # setpci -s 2:0.0 0xf0
> > 2) Disable ASPM (both L0s and L1) by zeroing out bits 0 and 1 in the value
> > returned by the previous step. For example, if it returned 42 (hex 42,
> > that is) -
> > # setpci -s 2:0.0 0xf0=0x40
> > 3) Confirm ASPM is disabled by checking the output from lspci again.
>
> It returned 42, and after setting 0x40, LnkCtl now says "ASPM Disabled".
>
> I'll dock the system now and will report after the weekend or after
> the first crash.

Didn't work, freeze within the first 60 minutes after starting serious
work. The system did sit idle for the night though without freezing.

Greetings
Marc

--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
First  |  Prev  | 
Pages: 1 2 3
Prev: support for drives larger than 2TiB
Next: cfq-iosched: don't allow aliased requests to starve others