Date: Wed, 10 Feb 2010 18:12:42 +0000 From: Oliver Pinter <oliver.pntr@gmail.com> To: Masoom Shaikh <masoom.shaikh@gmail.com> Cc: stable@freebsd.org, x11@freebsd.org, freebsd-x11@freebsd.org Subject: Re: freebsd7, radeon, xorg-server -> deadlock or so Message-ID: <6101e8c41002101012v4ae8a311y3780643051b6d6f7@mail.gmail.com> In-Reply-To: <b10011eb1002092354u34e956b3l90259e139fd4b844@mail.gmail.com> References: <6101e8c41002091524q25a7e026u585e575eb4f1589c@mail.gmail.com> <b10011eb1002092354u34e956b3l90259e139fd4b844@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
no, it's a desktop system, without wifi it is a asus p5q-e motherboard On 2/10/10, Masoom Shaikh <masoom.shaikh@gmail.com> wrote: > On Wed, Feb 10, 2010 at 4:54 AM, Oliver Pinter <oliver.pntr@gmail.com>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 >> root@peonia.teteny.bme.hu:/usr/obj/usr/src/sys/stable amd64 >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >> > > 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 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6101e8c41002101012v4ae8a311y3780643051b6d6f7>