From: "Udo A. Steinberg" <us15@os.inf.tu-dresden.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
James Simmons <jsimmons@infradead.org>
Subject: [OOPS] Linux v2.5.54 Riva Framebuffer
Date: Fri, 3 Jan 2003 00:48:58 +0100 [thread overview]
Message-ID: <20030103004858.3d291fbe.us15@os.inf.tu-dresden.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0301011935410.8506-100000@penguin.transmeta.com>
[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]
On Wed, 1 Jan 2003 19:43:40 -0800 (PST) Linus Torvalds (LT) wrote:
LT> Happy new year to you all [...]
Happy new year to you, too.
LT> Summary of changes from v2.5.53 to v2.5.54
LT> James Simmons <jsimmons@infradead.org>:
LT> o Updates to the NVIDIA driver. We now support more cards. I still
LT> have more hacking to do
LT> o Voodoo 1 ported to new api. STI and NVIDIA updates. MDA console
LT> fixes. Moved the logo code from fbcon to fbdev
With Linux 2.5.54 I'm getting an oops in the riva framebuffer driver that didn't
occur with Linux 2.5.53. It seems to be related to aforementioned changes. Trace
copied by hand because I have no serial console.
EIP is at fb_copy_cmap + 0x7f/0x140
Trace:
hide_cursor + 0x75/0x90
get_default_font + 0x209/0x2a0
updatescrollmode + 0x4f3/0x770
rivafb_set_par + 0x88/0xe0
fbcon_bmove_rec + 0x132/0x1f0
set_origin + 0x11d/0x190
clear_buffer_attributes + 0x1aa/0x1d0
put_driver + 0x2f/0x40
do_pre_smp_initcalls + 0x3a/0x160
do_pre_smp_initcalls + 0x0/0x160
show_regs + 0x5/0x18
The card in question is a Geforce 2 GTS.
If more info is required to help solving this problem, let me know.
Please CC: me on any discussion on fbdev-list; I'm only subscribed to lkml.
Regards,
-Udo.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-01-02 23:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 3:43 Linux v2.5.54 Linus Torvalds
2003-01-02 4:38 ` William Lee Irwin III
2003-01-02 10:43 ` Rusty Russell
2003-01-02 10:55 ` Andi Kleen
2003-01-02 11:13 ` William Lee Irwin III
2003-01-02 4:52 ` Linux v2.5.54 - OHCI-HCD build fails Murray J. Root
2003-01-02 5:00 ` Murray J. Root
2003-01-02 5:16 ` [PATCH] " Andres Salomon
2003-01-02 5:43 ` Murray J. Root
2003-01-02 6:10 ` Andres Salomon
2003-01-02 10:34 ` Linux v2.5.54 SZALAY Attila
2003-01-02 15:50 ` Randy.Dunlap
2003-01-02 15:56 ` Randy.Dunlap
2003-01-03 9:32 ` SZALAY Attila
2003-01-03 11:04 ` SZALAY Attila
2003-01-03 12:19 ` Alan Cox
2003-01-03 12:44 ` Christoph Hellwig
2003-01-03 16:13 ` Randy.Dunlap
2003-01-02 15:08 ` Adrian Bunk
2003-01-02 15:10 ` Christoph Hellwig
2003-01-02 17:18 ` Adrian Bunk
2003-01-02 17:31 ` Jaroslav Kysela
2003-01-02 13:26 ` Adam Belay
2003-01-03 0:08 ` [2.5.54] OOPS: unable to handle kernel paging request Steven Barnhart
2003-01-03 6:49 ` Paul Rolland
2003-01-02 17:49 ` Linux v2.5.54 Rudmer van Dijk
2003-01-02 23:48 ` Udo A. Steinberg [this message]
2003-01-04 21:13 ` [OOPS] Linux v2.5.54 Riva Framebuffer James Simmons
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=20030103004858.3d291fbe.us15@os.inf.tu-dresden.de \
--to=us15@os.inf.tu-dresden.de \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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®