From: Alex Thiel <stderr@web.de>
To: James Simmons <jsimmons@infradead.org>
Cc: linux-fbdev-devel@sourceforge.net
Subject: Re: Neomagic fb driver oopses with linux 2.5
Date: Tue, 29 Jul 2003 22:14:19 +0200 [thread overview]
Message-ID: <m34r15ks4k.fsf@spock.alex.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0307291811080.5874-100000@phoenix.infradead.org> (James Simmons's message of "Tue, 29 Jul 2003 18:14:02 +0100 (BST)")
James Simmons <jsimmons@infradead.org> writes:
>> I noticed that ksymoops complained about not being able to open
>> /proc/ksyms which seems to have gone in 2.5. Can this cause a
>> misinterpretation of the raw oops data?
>>
>> Anyway, I managed to connect to the laptop via a serial line and hope
>> to be able to track down the problem a little more this way.
>
> Hm. It has changed again. Anyone know the current method for backtracing.
I have recompiled the kernel with debugging symbols included, and gdb
thinks the oops occurs at line 264 in cfbimgblt.c. I don't know how
accurate this is, though, since this line is in function
fast_imageblit() while the backtrace rather pointed at cfb_imageblit().
Alex
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
next prev parent reply other threads:[~2003-07-29 20:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 9:30 Neomagic fb driver oopses with linux 2.5 Alex Thiel
2003-07-24 23:51 ` James Simmons
2003-07-26 18:25 ` Alex Thiel
2003-07-29 17:14 ` James Simmons
2003-07-29 20:14 ` Alex Thiel [this message]
2003-08-12 8:55 ` Alex Thiel
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=m34r15ks4k.fsf@spock.alex.net \
--to=stderr@web.de \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@sourceforge.net \
/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).