no, it's a desktop system, without wifi it is a asus p5q-e motherboard
On 2/10/10, Masoom Shaikh <[email protected]> wrote: > On Wed, Feb 10, 2010 at 4:54 AM, Oliver Pinter <[email protected]>wrote: > >> Hi all! >> >> After updated the xorg* and dri* and dependency, the system going to >> deadlock at second start of xserver. I think it is not an uniqe issue, >> as others wrote them at freebsd-x11: >> http://lists.freebsd.org/pipermail/freebsd-x11/2010-February/009370.html >> >> The symptoms: >> * independent from enabled or disabled DRI or GLX, first I think, this >> is the error, but not >> * the system going to deadlock state >> * no coredumps of xorgs >> * no panic, but the system is unusuable >> * independent from the driver: probed the radeon and radeonhd driver >> * independent from the WITHOUT_NOUVEAU or WITH_NOUVEAU compile options >> (make.conf) >> * the system is: FreeBSD peonia.teteny.bme.hu 7.3-PRERELEASE FreeBSD >> 7.3-PRERELEASE #29 r203612+fa83fdf: Mon Feb 8 02:11:08 CET 2010 >> [email protected]:/usr/obj/usr/src/sys/stable amd64 >> _______________________________________________ >> [email protected] mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "[email protected]" >> > > are you using intel wireless cards ? I had/having similar issues when such > freeze happens hard boot is the only option. I think it has something to do > with wlandev or something related to wpi driver. I cannot comment more since > coredumps are occasional and back trace suggests it is doadump(). > > here is my report earlier > http://lists.freebsd.org/pipermail/freebsd-questions/2009-November/207768.html > _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
