SCIENTIFIC-LINUX-USERS Archives

August 2011

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Alan Bartlett <[log in to unmask]>
Reply To:
Alan Bartlett <[log in to unmask]>
Date:
Mon, 15 Aug 2011 15:31:57 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (49 lines)
On 15 August 2011 06:10, William Scott <[log in to unmask]> wrote:
> I recently did a http install of SL6.1 as a virtualisation host.
>
> One of the network interfaces is a Atheros Communications AR8131
> Gigabit Ethernet (rev c0) using the ATL1C driver.
>
> One of the host machines (under KVM) has a https web interface
> (Vyatta). Attempting to reach this interface via the above bridged
> interface resulted in a corrupted page. Wireshark indicated that there
> was multiple “Broken TCP” packets.
>
> A web search revealed that the atl1c driver had/has issues with kernel 2.6.32.
>
> Did a pci/device ID check at Elrepo which reported that the atl1e
> driver was usable.
>
> Quick install with …
> yum install http://elrepo.org/linux/elrepo/el6/x86_64/RPMS/kmod-atl1e-1.0.1.14-1.el6.elrepo.x86_64.rpm
>
> Blacklisted the atl1c driver…
> vi /etc/modprobe.d/blacklist-net.conf
> blacklist atl1c
>
> Followed by a reboot.
>
> Https page now loads correctly and no broken TCP messages in
> Wireshark. Also got rid of some ssh issues (garbled decryption).
>
> Just a FYI post and to say thanks to Elrepo.

Hello William,

Thank you for you positive report and kind words regarding the ELRepo
Project -- it is always nice to read of a person's success.

In this case I think it is important that you have posted here, on the
Scientific Linux m/l, so that your issue with the atl1c driver (part
of the distributed kernel package) is recorded. As the SL kernel is
identical to that from upstream and never modified (apart from the
"branding" of the kernel modules), it would be worthwhile you opening
a bug report against the atl1c driver from the current kernel in the
Red Hat bug tracker [1].

Regards,
Alan.
(Scientific Linux user and co-founder of the ELRepo Project.)

[1] https://bugzilla.redhat.com/frontpage.cgi

ATOM RSS1 RSS2