From: Christopher Zimmermann <madroach@zakweb.de>
To: sparclinux@vger.kernel.org
Subject: Re: Sparc: Kernel 2.6.13 to 2.6.15-rc2 bug when running X11
Date: Wed, 07 Dec 2005 13:56:27 +0000 [thread overview]
Message-ID: <20051207135627.GA767@sparc> (raw)
In-Reply-To: <20051205.181732.34234732.davem@davemloft.net>
On Tue, Dec 06, 2005 at 03:39:58PM -0800, David S. Miller wrote:
> From: Christopher Zimmermann <madroach@zakweb.de>
> Date: Tue, 6 Dec 2005 16:08:10 +0100
>
> > I'm not sure, if this is the same problem, but since 2.6.15rc3 my X11 broke
> > too. I'm working on an Ultra2 Creator. This is what my X11 says on 2.6.15rc5:
> >
> > Call Trace:
> > [0000000000439de4] copy_process+0x8e4/0xe40
>
> This was fixed in 2.6.15rc4 and later.
As I said, I tested 2.6.15rc5, too. It performs as badly as rc3.
The symptoms are the same J.H. Aho described. But in contrast to J.H.
Aho I can switch back to a vt. By pressing CTRL+c on the vt I started X
on, I can kill the X server. This is the output I get after pressing
CTRL+c:
waiting for X server to shut down Bad pte = 800001fc00600e88, process = Xorg, vm_flags = 184473, vaddr = 7001e000
Call Trace:
[000000000046c390] unmap_region+0x90/0x140
[000000000046cad4] do_munmap+0x174/0x240
[000000000046cbbc] sys_munmap+0x1c/0x40
[0000000000406cd4] linux_sparc_syscall32+0x34/0x40
[00000000003d3ee0] 0x3d3ee0
xinit: unexpected signal 2.
next prev parent reply other threads:[~2005-12-07 13:56 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 2:04 Sparc: Kernel 2.6.13 to 2.6.15-rc2 bug when running X11 J.O. Aho
2005-12-06 2:17 ` David S. Miller
2005-12-06 2:17 ` David S. Miller
2005-12-06 15:08 ` Christopher Zimmermann
2005-12-06 16:10 ` J.O. Aho
2005-12-06 16:10 ` J.O. Aho
2005-12-06 23:23 ` David S. Miller
2005-12-06 23:23 ` David S. Miller
2005-12-07 11:05 ` J.O. Aho
2005-12-07 11:05 ` J.O. Aho
2005-12-07 14:07 ` Ben Collins
2005-12-07 14:07 ` Ben Collins
2005-12-07 15:42 ` J.O. Aho
2005-12-07 15:42 ` J.O. Aho
2005-12-07 20:34 ` David S. Miller
2005-12-07 20:34 ` David S. Miller
2005-12-07 21:22 ` J.O. Aho
2005-12-07 21:22 ` J.O. Aho
2005-12-07 21:32 ` David S. Miller
2005-12-07 21:32 ` David S. Miller
2005-12-09 12:07 ` J.O. Aho
2005-12-09 12:07 ` J.O. Aho
2005-12-10 22:25 ` J.O. Aho
2005-12-10 22:25 ` J.O. Aho
2005-12-10 22:35 ` David S. Miller
2005-12-10 22:35 ` David S. Miller
2005-12-10 22:52 ` J.O. Aho
2005-12-10 22:52 ` J.O. Aho
2005-12-10 23:00 ` David S. Miller
2005-12-10 23:00 ` David S. Miller
2005-12-10 23:22 ` J.O. Aho
2005-12-10 23:22 ` J.O. Aho
2005-12-12 5:07 ` David S. Miller
2005-12-12 5:07 ` David S. Miller
2005-12-12 8:26 ` J.O. Aho
2005-12-12 8:26 ` J.O. Aho
2005-12-12 16:28 ` J.O. Aho
2005-12-12 16:28 ` J.O. Aho
2006-02-01 13:15 ` J.O. Aho
2006-02-01 13:15 ` J.O. Aho
2005-12-06 23:39 ` David S. Miller
2005-12-07 13:56 ` Christopher Zimmermann [this message]
2005-12-07 20:49 ` David S. Miller
2005-12-07 22:11 ` Christopher Zimmermann
2005-12-07 22:17 ` David S. Miller
2005-12-12 10:13 ` Mark Fortescue
2005-12-12 10:13 ` Mark Fortescue
2005-12-12 10:38 ` J.O. Aho
2005-12-12 10:38 ` J.O. Aho
2005-12-12 22:26 ` David S. Miller
2005-12-12 22:26 ` David S. Miller
2005-12-18 22:03 ` J.O. Aho
2005-12-18 22:03 ` J.O. Aho
2005-12-18 23:10 ` David S. Miller
2005-12-18 23:10 ` David S. Miller
2006-01-03 14:01 ` J.O. Aho
2006-01-03 14:01 ` J.O. Aho
2006-01-03 20:18 ` David S. Miller
2006-01-03 20:18 ` David S. Miller
2006-01-03 21:15 ` J.O. Aho
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=20051207135627.GA767@sparc \
--to=madroach@zakweb.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.