From: Thomas Meyer <thomas.mey3r@arcor.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [2.6.10-rc1] Segmentation fault in program "X"
Date: Sun, 24 Oct 2004 20:10:55 +0200 [thread overview]
Message-ID: <417BF02F.20704@arcor.de> (raw)
In-Reply-To: <200410241313.31151.vda@port.imtp.ilyichevsk.odessa.ua>
Denis Vlasenko wrote:
> On Sunday 24 October 2004 11:38, Thomas Meyer wrote:
>
>>Hello.
>>
>>X doesn't work under 2.6.10-rc1. i'm using the framebuffer X server.
>>Kernel 2.6.9 works. How could that be?
>
>
> Details?
> --
> vda
>
>
Hi.
Signal SIGSEGV happens while doing sys function
"ioctl(5, FBIOBLANK <unfinished ...>"
seems to be some changes between 2.6.9 and 2.6.10-rc1 in file "fbmem.c"
with kind regards
Thomas
next prev parent reply other threads:[~2004-10-24 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-24 8:38 [2.6.10-rc1] Segmentation fault in program "X" Thomas Meyer
2004-10-24 10:13 ` Denis Vlasenko
2004-10-24 18:10 ` Thomas Meyer [this message]
2004-10-24 20:24 ` Linus Torvalds
2004-10-24 23:00 ` Benjamin Herrenschmidt
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=417BF02F.20704@arcor.de \
--to=thomas.mey3r@arcor.de \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).