On Sat, Dec 04, 2010 at 05:21:30PM +0000, Ben Hutchings wrote: > I am inclined to suspect the fglrx driver. Please try to reproduce this > without that driver loaded.
No solid results yet. My system freezes without fglrx driver right after I log in via gdm. It is always reproducible and I will go ahead and create a separate issue on it. I did not manage to reproduce the freeze with just the gdm window left idle. The system does not freeze at this case, but using oith open source and fglrx driver. I managed to get system running over the night using fglrx and it did not freeze. So now my target is to understand what exactly happens after gdm login that makes this bug reproducible. > The warning in the log about r8169 is in no way fatal, it just means the > network transmit path locked up and had to be reset. By the way, the > firmware licencing situation for this driver (bug #564628) looks likely > to be resolved soon. Great to hear, but if it is not related to it than it looks to be working without this firmware in my case. -- Anton Martchukov http://www.martchukov.com 0xFC4FBF28 96BC 3DAB 231A 7FCC 4F49 D783 9A69 65C1 FC4F BF28
signature.asc
Description: Digital signature
