From: "J.O. Aho" <trizt@iname.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: linux-kernel maillist <linux-kernel@vger.kernel.org>,
sparclinux@vger.kernel.org
Subject: Re: Sparc: Kernel 2.6.13 to 2.6.15-rc2 bug when running X11
Date: Wed, 7 Dec 2005 12:05:43 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0512071203460.8861@localhost.localdomain> (raw)
In-Reply-To: <20051206.152316.82233251.davem@davemloft.net>
On Tue, 6 Dec 2005, David S. Miller wrote:
> From: "J.O. Aho" <trizt@iname.com>
> Date: Tue, 6 Dec 2005 17:10:07 +0100 (CET)
>
>> On Mon, 5 Dec 2005, David S. Miller wrote:
>>
>>> 2) You didn't give what the failure mode is for kernels such
>>> as 2.6.14.2, which should work, and certainly don't print out
>>> that bug message
>>
>> It's the same as for 2.6.13 and 2.6.15rc, did build a 2.6.14.3 as had
>> removed the 14.2 when I started to use 15rc.
>
> You're still not answering my question, what is this failure
> mode? Xorg doesn't start? The kernel crashes when Xorg starts?
> Xorg starts but you get a blank screen? You did not mention
> this critical information anywhere. Mentioning a list of other
> kernels that "it's the same" for doesn't describe the failure
> mode. :)
Sorry, thought the log from Xorg was quite selfexplaining
Xorg jumps to VT7, you see a console cursor, "_", at the top left corner
and thats it. It's impossible to change back to VT1 (or any other), the
only thing that works is to press [stop]-[a] so that you get back to the
OBP from where I can reset the machine (resetting by the reset button
don't work). It's still possible to ssh to the machine, more and dmesg is
possible, but running ps causes the machine to completly lock up, change
init mode don't give any affects att all and trying to turn off or kill X
results in the same as ps.
When running in plain console (without trying to run X) everything works
fine (just telling that so I won't get people to ask if ps segfaults in
other cases or claims that my init is broke and so on).
--
//Aho
------------------------------------------------------------------------
E-Mail: trizt@iname.com URL: http://www.kotiaho.net/~trizt/
ICQ: 13696780
System: Linux System (PPC7447/1000 AMD K7A/2000)
------------------------------------------------------------------------
EU forbids you to send spam without my permission
------------------------------------------------------------------------
next prev parent reply other threads:[~2005-12-07 11:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 2:04 J.O. Aho
2005-12-06 2:17 ` David S. Miller
2005-12-06 16:10 ` J.O. Aho
2005-12-06 23:23 ` David S. Miller
2005-12-07 11:05 ` J.O. Aho [this message]
2005-12-07 14:07 ` Ben Collins
2005-12-07 15:42 ` J.O. Aho
2005-12-07 20:34 ` David S. Miller
2005-12-07 21:22 ` J.O. Aho
2005-12-07 21:32 ` David S. Miller
2005-12-09 12:07 ` J.O. Aho
2005-12-10 22:25 ` J.O. Aho
2005-12-10 22:35 ` David S. Miller
2005-12-10 22:52 ` J.O. Aho
2005-12-10 23:00 ` David S. Miller
2005-12-10 23:22 ` J.O. Aho
2005-12-12 5:07 ` David S. Miller
2005-12-12 8:26 ` J.O. Aho
2005-12-12 16:28 ` J.O. Aho
2006-02-01 13:15 ` J.O. Aho
2005-12-12 10:13 Mark Fortescue
2005-12-12 10:38 ` J.O. Aho
2005-12-12 22:26 ` David S. Miller
2005-12-18 22:03 ` J.O. Aho
2005-12-18 23:10 ` David S. Miller
2006-01-03 14:01 ` J.O. Aho
2006-01-03 20:18 ` David S. Miller
2006-01-03 21:15 ` J.O. Aho
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=Pine.LNX.4.64.0512071203460.8861@localhost.localdomain \
--to=trizt@iname.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.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
all inboxes | Powered by JetHome®