From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 50091] [BISECTED]GeForce 6150SE: system hangs on X-server start with garbled screen
Date: Wed, 26 Dec 2012 17:34:22 +0000 (UTC) [thread overview]
Message-ID: <20121226173422.F01AA11FE9A@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-50091-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=50091
--- Comment #22 from schaefer.frank@gmx.net 2012-12-26 17:34:22 ---
UPDATE:
I've tested with 3.8.0-rc1, and now I have a good chance that the system
starts.
The criticial point is shortly before the the KDE Desktop appears (near the end
of the KDE startup progress screen). If it survives this point, the machine
runs stable for hours.
Maybe this gives us a hint of what could be going on ?
Could this have something to do with memory allocation ? Remember that this is
an onboard device using a part of the systems RAM.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2012-12-26 17:34 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-50091-2300@https.bugzilla.kernel.org/>
2012-11-06 13:32 ` [Bug 50091] GeForce 6150SE: system hangs on X-server start with garbled screen bugzilla-daemon
2012-11-14 13:50 ` bugzilla-daemon
2012-11-14 14:33 ` [Bug 50091] [BISECTED]GeForce " bugzilla-daemon
2012-11-14 20:28 ` bugzilla-daemon
2012-11-15 14:59 ` bugzilla-daemon
2012-11-15 15:01 ` bugzilla-daemon
2012-11-15 15:05 ` bugzilla-daemon
2012-11-15 15:38 ` bugzilla-daemon
2012-11-15 15:39 ` bugzilla-daemon
2012-11-15 18:50 ` bugzilla-daemon
2012-11-15 20:06 ` bugzilla-daemon
2012-11-15 21:02 ` bugzilla-daemon
2012-11-15 21:45 ` bugzilla-daemon
2012-11-15 21:56 ` bugzilla-daemon
2012-11-16 12:10 ` bugzilla-daemon
2012-11-16 19:43 ` bugzilla-daemon
2012-11-16 20:27 ` bugzilla-daemon
2012-11-17 13:26 ` bugzilla-daemon
2012-11-17 15:24 ` bugzilla-daemon
2012-11-17 17:31 ` bugzilla-daemon
2012-11-17 18:34 ` bugzilla-daemon
2012-11-17 19:15 ` bugzilla-daemon
2012-11-17 20:05 ` bugzilla-daemon
2012-12-26 17:34 ` bugzilla-daemon [this message]
2012-12-26 17:35 ` bugzilla-daemon
2012-12-29 6:33 ` bugzilla-daemon
2012-12-29 10:34 ` bugzilla-daemon
2013-02-23 18:39 ` bugzilla-daemon
2013-03-02 16:45 ` bugzilla-daemon
2013-03-02 17:29 ` bugzilla-daemon
2013-03-04 9:53 ` bugzilla-daemon
2013-05-27 5:16 ` bugzilla-daemon
2013-07-12 17:58 ` bugzilla-daemon
2013-08-12 21:58 ` bugzilla-daemon
2013-11-19 18:54 ` bugzilla-daemon
2014-04-11 12:33 ` bugzilla-daemon
2014-04-14 10:17 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121226173422.F01AA11FE9A@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).