From: Antonino Daplas <adaplas@pol.net>
To: Siim Vahtre <siim@pld.ttu.ee>
Cc: Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: cat /dev/fb1 produces kernel bug
Date: 24 Feb 2003 05:34:24 +0800 [thread overview]
Message-ID: <1046035982.1308.74.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.SOL.4.31.0302231958260.28624-100000@pitsa.pld.ttu.ee>
On Mon, 2003-02-24 at 02:07, Siim Vahtre wrote:
> Call Trace:
> [<c020e678>] kobject_register+0x58/0x70
> [<c021a58b>] bus_add_driver+0x5b/0xe0
> [<c021a9df>] driver_register+0x2f/0x40
> [<c017a8e3>] create_proc_entry+0x83/0xd0
> [<c021170b>] pci_register_driver+0x4b/0x60
> [<c010507f>] init+0x3f/0x160
> [<c0105040>] init+0x0/0x160
> [<c010726d>] kernel_thread_helper+0x5/0x18
>
For a quick fix, try this:
diff -Naur linux-2.5.61/drivers/video/riva/fbdev.c linux/drivers/video/riva/fbdev.c
--- linux-2.5.61/drivers/video/riva/fbdev.c 2003-02-16 00:49:23.000000000 +0000
+++ linux/drivers/video/riva/fbdev.c 2003-02-23 21:30:50.000000000 +0000
@@ -1961,12 +1961,10 @@
int __init rivafb_init(void)
{
- int err;
- err = pci_module_init(&rivafb_driver);
- if (err)
- return err;
- pci_register_driver(&rivafb_driver);
- return 0;
+ if (pci_register_driver(&rivafb_driver) > 0)
+ return 0;
+ pci_unregister_driver(&rivafb_driver);
+ return -ENODEV;
}
Or Try James' patch...
http://phoenix.infradead.org/~jsimmons/fbdev.diff.gz
...and Geert's "Logo Updates" which he just sent recently.
Tony
-------------------------------------------------------
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
prev parent reply other threads:[~2003-02-23 21:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-23 18:07 cat /dev/fb1 produces kernel bug Siim Vahtre
2003-02-23 21:34 ` Antonino Daplas [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=1046035982.1308.74.camel@localhost.localdomain \
--to=adaplas@pol.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=siim@pld.ttu.ee \
/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).