2.5.70-bk radeonfb oops on boot.

From: Simon Fowler (simon@himi.org)
Date: Tue Jun 10 2003 - 01:16:54 EST

I've started seeing a hard lockup on boot with my Fujitsu Lifebook
p2120 laptop, with a radeon mobility M6 LY, when using a Linus bk
kernel as of 2003-06-09 (possibly earlier - the last kernel I've
tested is bk as of 2003-06-04). lspci lists this hardware:

00:00.0 Host bridge: Transmeta Corporation LongRun Northbridge (rev 03)
00:00.1 RAM memory: Transmeta Corporation SDRAM controller
00:00.2 RAM memory: Transmeta Corporation BIOS scratchpad
00:02.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:04.0 Multimedia audio controller: ALi Corporation M5451 PCI AC-Link Controller Audio Device (rev 01)
00:06.0 Bridge: ALi Corporation M7101 PMU
00:07.0 ISA bridge: ALi Corporation M1533 PCI to ISA Bridge [Aladdin IV]
00:09.0 USB Controller: NEC Corporation USB (rev 41)
00:09.1 USB Controller: NEC Corporation USB (rev 41)
00:09.2 USB Controller: NEC Corporation USB 2.0 (rev 02)
00:0c.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller (rev 01)
00:0f.0 IDE interface: ALi Corporation M5229 IDE (rev c3)
00:10.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:12.0 Network controller: Harris Semiconductor Prism 2.5 Wavelan chipset (rev 01)
00:13.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link)
00:14.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY

Building the kernel without framebuffer support results in a
bootable kernel. Disabling only framebuffer console support (ie,
oopses the same way as with the framebuffer console enabled.

Unfortunately, the system locks up to the point where I can't scroll
back to get the full oops, and it never hits any logfiles, so all I
have (copied by hand, with a few formatting changes to make copying
easier) is the last 25 lines of the oops:

c01c042b pci_enable_device_bars+0x21/0x40
c01c0457 pci_enable_device+0x17/0x20
c0245c37 radeonfb_pci_register+0x37/0x66 (?)
c0109a1c common_interrupt+0x18/0x20
c01c23f2 pci_device_probe_static+0x52/0x70
c01c251c __pci_device_probe+0x3c/0x50
c01c255f pci_device_probe+0x2f/0x50
c02162a5 bus_match+0x45/0x80
c02163ce driver_attach+0x5e/0x60
c0216673 bus_add_driver+0x93/0xb0
c0216abf driver_register+0x2f/0x40
c015883d register_chrdev+0xcd/0x120
c01c2802 pci_register_driver+0x72/0xa0
c0378733 radeonfb_init+0x13/0x40
c0378207 fbmem_init+0x87/0xc0
c0374169 chr_dev_init+0x79/0xa0
c03627bb do_initcalls+0x2b/0xa0
c012bc3f init_workqueues+0xf/0x30
c010506b init+0x2b/0x180
c0105040 init+0x0/0x180
c010725d kernel_thread_helper+0x5/0x18

Code: bad EIP value.
 <0>Kernel panic: Attempted to kill init!

This is the diff between the working config (sans framebuffer
support) and the oopsing config:

--- /boot/config-2.5.70-20030610 2003-06-10 14:51:29.000000000 +1000
+++ /boot/config-2.5.70-20030610-nofb 2003-06-10 14:40:14.000000000 +1000
@@ -1036,27 +1036,8 @@
 # Graphics support
-# CONFIG_FB_CIRRUS is not set
-# CONFIG_FB_PM2 is not set
-# CONFIG_FB_CYBER2000 is not set
-# CONFIG_FB_IMSTT is not set
-# CONFIG_FB_VGA16 is not set
+# CONFIG_FB is not set
-# CONFIG_FB_HGA is not set
-# CONFIG_FB_RIVA is not set
-# CONFIG_FB_MATROX is not set
-# CONFIG_FB_ATY128 is not set
-# CONFIG_FB_ATY is not set
-# CONFIG_FB_SIS is not set
-# CONFIG_FB_NEOMAGIC is not set
-# CONFIG_FB_3DFX is not set
-# CONFIG_FB_VOODOO1 is not set
-# CONFIG_FB_TRIDENT is not set
-# CONFIG_FB_PM3 is not set
-# CONFIG_FB_VIRTUAL is not set
 # Console display driver support
@@ -1064,19 +1045,6 @@
 # CONFIG_MDA_CONSOLE is not set
-# CONFIG_FONTS is not set
-# Logo configuration
-# CONFIG_LOGO_LINUX_VGA16 is not set
 # Sound

If you need any other information, ask away - I'll do my best.


PGP public key Id 0x144A991C, or http://himi.org/stuff/himi.asc
(crappy) Homepage: http://himi.org
doe #237 (see http://www.lemuria.org/DeCSS) 
My DeCSS mirror: ftp://himi.org/pub/mirrors/css/ 

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

This archive was generated by hypermail 2b29 : Sun Jun 15 2003 - 22:00:22 EST