From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Thomas Meyer <thomas.mey3r@arcor.de>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.10-rc1] Segmentation fault in program "X"
Date: Mon, 25 Oct 2004 09:00:03 +1000 [thread overview]
Message-ID: <1098658803.11740.206.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.58.0410241323140.13209@ppc970.osdl.org>
On Mon, 2004-10-25 at 06:24, Linus Torvalds wrote:
> > 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"
>
> Do you have radeon hardware? Is there any oops in your logs?
A Oops log would be useful...
I don't see anything, are you sure he is using radeonfb ? Look at the
fix posted by Tony Dapalas today fixing a possible Oops on blank for
fbdev's that have no blank() callback ...
Ben.
prev parent reply other threads:[~2004-10-24 23:03 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
2004-10-24 20:24 ` Linus Torvalds
2004-10-24 23:00 ` Benjamin Herrenschmidt [this message]
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=1098658803.11740.206.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.mey3r@arcor.de \
--cc=torvalds@osdl.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.