[rhelv6-list] vlan issue with RHEL 6.3 kernel 2.6.32-279

[Paul Preston]

I couldn't find any reference to any major changes in kernel 2.6.32-279 in regards to vlans. It's most likely a bug.

--
Paul Preston
Proxar IT Ltd. Registered in England and Wales: 6744401- VAT: 942985479
Tubs Hill House, London Road, Sevenoaks, Kent, TN13 1BL
Tel:  (+44) 0844 809 4335
Fax: (+44) 01732 459 423
Mob: (+44) 077 9509 3450
Web: www.proxar.co.uk
Email: paul.preston at proxar.co.uk


-----Original Message-----
From: rhelv6-list-bounces at redhat.com [mailto:rhelv6-list-bounces at redhat.com] On Behalf Of Derek Yarnell
Sent: 28 June 2012 14:55
To: Red Hat Enterprise Linux 6 (Santiago) discussion mailing-list
Subject: Re: [rhelv6-list] vlan issue with RHEL 6.3 kernel 2.6.32-279

On 6/28/12 9:19 AM, Akemi Yagi wrote:
> On Thu, Jun 28, 2012 at 5:50 AM, Werner Maes
> <Werner.Maes at icts.kuleuven.be> wrote:
>> Hello
>>
>> After upgrading from 6.2 to 6.3 I have a serious issue with the
>> latest RHEL6.3 kernel: 2.6.32-279.el6 My vlan network configuration no longer works (no traffic on the vlan interface), however if I boot with my old 6.2 kernel 2.6.32-220.el6 all works fine. What has changed?
>
> Maybe related to this?
>
> https://bugzilla.redhat.com/show_bug.cgi?id=834764
>
> Akemi
>
> _______________________________________________
> rhelv6-list mailing list
> rhelv6-list at redhat.com
> https://www.redhat.com/mailman/listinfo/rhelv6-list
>

Thanks for finding this, we hit this bug and had to roll back last thursday.  It seems for us to only get Broadcom nics using bnx2.  This is the 2nd regresssion bug with network drivers in the last two releases that Red Hat put out (The RHEL5.8 release kernel had a issue with tg3 w/ vlans). Ugh.

Thanks,
derek

--
---
Derek T. Yarnell
University of Maryland
Institute for Advanced Computer Studies


_______________________________________________
rhelv6-list mailing list
rhelv6-list at redhat.com
https://www.redhat.com/mailman/listinfo/rhelv6-list
Please note that we may monitor or record telephone calls, email traffic data and also the content of email for the purposes of security and staff training. This message (and any associated file or documentation) is intended only for the use of the individual or entity to whom it is addressed and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient you are hereby notifiedthat any dissemination, copying or distribution of this message, or files and documentation associated with this message, is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from oyur computer. Any views or opinions presented are solely those of the authorand do not necessarily represent those of the company.