From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
jsimmons@infradead.org, akpm@digeo.com
Subject: Re: 2.5.67-mm1 cause framebuffer crash at bootup
Date: Wed, 9 Apr 2003 14:24:00 +0200 [thread overview]
Message-ID: <11CB582A88@vcnet.vc.cvut.cz> (raw)
On 9 Apr 03 at 11:42, Helge Hafting wrote:
>
> 2.5.67-mm1 works if I drop framebuffer support completely.
Now when you sent full backtrace - it looks to me like that fbdev
drivers are initialized before pci subsystem in -mm1. Unfortunately,
as proven by i2c, kobjects infrastructure does not like if you reference
non-existing bus type before it is registered.
Can you try reverting _initcall changes? Although I see no reason
why it should matter, it is clear that pci subsystem is a bit unhappy.
Maybe it is caused by driver or device which is probed before fbdev?
Petr Vandrovec
vandrove@vc.cvut.cz
P.S.: And what about change in drivers/pci/probe.c, which does
- if (base && base <= limit) {
+ if (base <= limit) {
> Here is the printed backtrace for the radeon case, the matrox case was
> similiar:
>
> <a few lines scrolled off screen>
> pcibios_enable_device
> pci_enable_device_bars
> pci_enable_device
> radeonfb_pci_register
> sysfs_new_inode
> pci_device_probe
> bus_match
> device_attach
> bus_add_device
> kobject_add
> device_add
> pci_bus_add_devices
> pci_bus_add_devices
> pci_scan_bus_parented
> pcibios_scan_root
> pci_legacy_init
> do_initcalls
> init_workqueues
> init+0x36
> init+0x00
> kernel_thread_helper
> code: Bad EIP value <0>Kernel panic:attempt to kill init!
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
next reply other threads:[~2003-04-09 12:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-09 12:24 Petr Vandrovec [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-08 11:22 2.5.67-mm1 Andrew Morton
2003-04-09 9:42 ` 2.5.67-mm1 cause framebuffer crash at bootup Helge Hafting
[not found] ` <20030409030534.619f7fa0.akpm@digeo.com>
2003-04-09 10:05 ` Andrew Morton
[not found] ` <20030409031845.185d853f.akpm@digeo.com>
2003-04-09 10:18 ` Andrew Morton
2003-04-09 20:30 ` Randy.Dunlap
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=11CB582A88@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=akpm@digeo.com \
--cc=helgehaf@aitel.hist.no \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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