Fedora 18 network freeze after a while...

Georgios Petasis petasisg at yahoo.gr
Tue Mar 5 20:26:38 UTC 2013


Στις 5/3/2013 9:34 μμ, ο/η Georgios Petasis έγραψε:
> Στις 5/3/2013 8:55 μμ, ο/η Rick Stevens έγραψε:
>> On 03/05/2013 10:31 AM, Georgios Petasis issued this missive:
>>> Hi all,
>>>
>>> I am facing a very strange problem after upgrading to fedora 18: while
>>> the system works ok (I use the machine through vnc),
>>> after some time (which can range from 30 minutes to a few hours) all
>>> network interaction rapidly deteriorates, until network is no
>>> more useful (i.e. I cannot even ssh to the machine).
>>>
>>> How can I find out why this is happening? I didn't had any problems 
>>> with
>>> fedora 17, and I have tested the RAM, which showed no errors.
>>
>> Need more info:
>>
>> 1. Wired or wireless?
> Wired.
>>
>> 2. Using NetworkManager or classic network config?
> Network manager.
>>
>> 3. DHCP or fixed IPs?
> Fixed IP.
>>
>> 4. Does anything weird show up in the output of dmesg or in any of the
>> log files (e.g. /var/log/messages, etc.)?
> No, but I am searching for it. The motherboard has a Z77 chipset.
>
> I see some errors like:
>
> DMA: Out of SW-IOMMU space for 32768 bytes at device 0000:05:00.0
>
> I don't know the device though.
>
> George
>
Finally, this is the problem, the kernel error comes from the driver for 
the atheros gbe lan chip.
I see that there is a bug in the atl1c kernel module, introduced with 
the 3.8.0 kernel, and exists also in3.8.1.
 From what I understood, 3.8.2 will also have this bug.

So, fedora is unusable at least until kernel 3.8.3 gets included, for 
systems with atheros chips (i.e. many gigabyte boards).

George


More information about the users mailing list