LinuxLists.cc - 2.5.70-bk radeonfb oops on boot.

2003-06-10 06:03:22

Subject: 2.5.70-bk radeonfb oops on boot.

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,
CONFIG_FB=y, CONFIG_FB_RADEON=y, CONFIG_FRAMEBUFFER_CONSOLE=n)
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=y
-# 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_VESA=y
+# CONFIG_FB is not set
CONFIG_VIDEO_SELECT=y
-# CONFIG_FB_HGA is not set
-# CONFIG_FB_RIVA is not set
-# CONFIG_FB_MATROX is not set
-CONFIG_FB_RADEON=y
-# 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_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
-CONFIG_FRAMEBUFFER_CONSOLE=y
-CONFIG_PCI_CONSOLE=y
-# CONFIG_FONTS is not set
-CONFIG_FONT_8x8=y
-CONFIG_FONT_8x16=y
-
-#
-# Logo configuration
-#
-CONFIG_LOGO=y
-# CONFIG_LOGO_LINUX_MONO is not set
-# CONFIG_LOGO_LINUX_VGA16 is not set
-CONFIG_LOGO_LINUX_CLUT224=y

#
# Sound
--------------------------------------------------

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

Simon

--
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/

Attachments:

(No filename) (4.49 kB)
(No filename) (189.00 B)
Download all attachments

2003-06-10 06:23:12

by Joshua Kwan

[permalink] [raw]

Subject: Re: 2.5.70-bk radeonfb oops on boot.

On Tue, Jun 10, 2003 at 04:16:54PM +1000, Simon Fowler wrote:
> 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:

That's interesting, my Radeon works fine:

$ dmesg | grep ATI
radeonfb: ATI Radeon M6 LY DDR SGRAM 32 MB

But I'm running 2.5.70-mm5, can you try that? If -mm5 works, it will
probably easier to pinpoint the problem.

Regards
Josh

--
New PGP public key: 0x27AFC3EE

Attachments:

(No filename) (594.00 B)
(No filename) (189.00 B)
Download all attachments

2003-06-10 06:32:30

by Greg KH

[permalink] [raw]

Subject: Re: 2.5.70-bk radeonfb oops on boot.

On Tue, Jun 10, 2003 at 04:16:54PM +1000, Simon Fowler wrote:
> 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:

Hm, mine boots, but my kernel locks up when accessing /dev/rtc in the
init scripts (through hwclock.) 2.5.69 works, 2.5.70 doesn't. I
haven't spent the time to search out the offending problem yet...

greg k-h

2003-06-10 06:40:09

by Simon Fowler

[permalink] [raw]

Subject: Re: 2.5.70-bk radeonfb oops on boot.

On Mon, Jun 09, 2003 at 11:48:29PM -0700, Greg KH wrote:
> On Tue, Jun 10, 2003 at 04:16:54PM +1000, Simon Fowler wrote:
> > 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:
>
> Hm, mine boots, but my kernel locks up when accessing /dev/rtc in the
> init scripts (through hwclock.) 2.5.69 works, 2.5.70 doesn't. I
> haven't spent the time to search out the offending problem yet...
>
Apparently there's some kind of problem with ACPI and the rtc driver
- leaving out /dev/rtc support got it up and running quite happily,
until this framebuffer oops came along.

Simon

--
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/

Attachments:

(No filename) (991.00 B)
(No filename) (189.00 B)
Download all attachments

2003-06-10 12:48:30

by Simon Fowler

[permalink] [raw]

Subject: Re: 2.5.70-bk radeonfb oops on boot.

On Tue, Jun 10, 2003 at 04:16:54PM +1000, Simon Fowler wrote:
> 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:
>
I've narrowed the start of the problem down: 2.5.70-bk13 works,
-bk14 oopses.

Simon

--
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/

Attachments:

(No filename) (615.00 B)
(No filename) (189.00 B)
Download all attachments

2003-06-10 13:05:48

by Helge Hafting

[permalink] [raw]

Subject: Re: 2.5.70-bk radeonfb oops on boot.

Simon Fowler wrote:
> 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:

I see the same oops on my desktop.
I tried 2.5.70-mm7 to see if anything happened to
the recent RAID problems, but didn't even
get the switch to framebuffer console.
It looks radeon related.
This is a UP machine with preempt. I
don't use any acpi or modules.

lspci
00:00.0 Host bridge: Silicon Integrated Systems [SiS] SiS645DX Host &
Memory & AGP Controller
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SiS 530 Virtual
PCI-to-PCI bridge (AGP)
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513 (rev 04)
00:02.1 SMBus: Silicon Integrated Systems [SiS]: Unknown device 0016
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS]
SiS7012 PCI Audio Accelerator (rev a0)
00:03.0 USB Controller: Silicon Integrated Systems [SiS] SiS7001 USB
Controller (rev 0f)
00:03.1 USB Controller: Silicon Integrated Systems [SiS] SiS7001 USB
Controller (rev 0f)
00:03.2 USB Controller: Silicon Integrated Systems [SiS] SiS7001 USB
Controller (rev 0f)
00:03.3 USB Controller: Silicon Integrated Systems [SiS] SiS7002 USB 2.0
00:0b.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado]
(rev 78)
00:0c.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY
[Radeon 7000/VE]

Helge Hafting

2003-06-10 21:07:24

by Andrew Morton

[permalink] [raw]

Subject: Re: 2.5.70-bk radeonfb oops on boot.

2003-06-11 02:05:51

by Simon Fowler

[permalink] [raw]

Subject: Re: 2.5.70-bk radeonfb oops on boot.

On Tue, Jun 10, 2003 at 02:14:40PM -0700, Andrew Morton wrote:
> Simon Fowler <[email protected]> wrote:
> >
> > On Tue, Jun 10, 2003 at 04:16:54PM +1000, Simon Fowler wrote:
> > > 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:
> > >
> > I've narrowed the start of the problem down: 2.5.70-bk13 works,
> > -bk14 oopses.
>
> That's funny. bk13->bk14 was almost all arm stuff. diffstat below.
>
> It might be worth reverting this chunk, see if that fixes it:
>
> --- b/drivers/char/mem.c Thu Jun 5 23:36:40 2003
> +++ b/drivers/char/mem.c Sun Jun 8 05:02:24 2003
> @@ -716 +716 @@
> -__initcall(chr_dev_init);
> +subsys_initcall(chr_dev_init);
>
And we have a winner . . . Reverting this hunk fixes the oops.

Simon

--
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/

Attachments:

(No filename) (1.13 kB)
(No filename) (189.00 B)
Download all attachments

2003-06-11 03:02:16

by Andrew Morton

[permalink] [raw]

Subject: Re: 2.5.70-bk radeonfb oops on boot.

Simon Fowler <[email protected]> wrote:
>
> On Tue, Jun 10, 2003 at 02:14:40PM -0700, Andrew Morton wrote:
> > Simon Fowler <[email protected]> wrote:
> > >
> > > On Tue, Jun 10, 2003 at 04:16:54PM +1000, Simon Fowler wrote:
> > > > 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:
> > > >
> > > I've narrowed the start of the problem down: 2.5.70-bk13 works,
> > > -bk14 oopses.
> >
> > That's funny. bk13->bk14 was almost all arm stuff. diffstat below.
> >
> > It might be worth reverting this chunk, see if that fixes it:
> >
> > --- b/drivers/char/mem.c Thu Jun 5 23:36:40 2003
> > +++ b/drivers/char/mem.c Sun Jun 8 05:02:24 2003
> > @@ -716 +716 @@
> > -__initcall(chr_dev_init);
> > +subsys_initcall(chr_dev_init);
> >
> And we have a winner . . . Reverting this hunk fixes the oops.
>

So it's another initcall problem in the PCI layer.

pci_enable_device_bars() is needing things which are not yet set up. A lot
of the PCI initialisation is at subsys_initcall() as well, and you got
unlucky with link order.

I expect the below patch will fix this as well. Could you please put the
above change back to normal and see if this one fixes it?

diff -puN arch/i386/pci/irq.c~pci-init-ordering-fix arch/i386/pci/irq.c
--- 25/arch/i386/pci/irq.c~pci-init-ordering-fix Tue Jun 10 15:40:19 2003
+++ 25-akpm/arch/i386/pci/irq.c Tue Jun 10 15:40:19 2003
@@ -791,7 +791,7 @@ static int __init pcibios_irq_init(void)
return 0;
}

-subsys_initcall(pcibios_irq_init);
+arch_initcall(pcibios_irq_init);

void pcibios_penalize_isa_irq(int irq)
diff -puN arch/i386/pci/legacy.c~pci-init-ordering-fix arch/i386/pci/legacy.c
--- 25/arch/i386/pci/legacy.c~pci-init-ordering-fix Tue Jun 10 15:46:35 2003
+++ 25-akpm/arch/i386/pci/legacy.c Tue Jun 10 15:46:47 2003
@@ -65,4 +65,4 @@ static int __init pci_legacy_init(void)
return 0;
}

-subsys_initcall(pci_legacy_init);
+arch_initcall(pci_legacy_init);

_

2003-06-11 03:41:51

by Simon Fowler

[permalink] [raw]

Subject: Re: 2.5.70-bk radeonfb oops on boot.

On Tue, Jun 10, 2003 at 08:16:41PM -0700, Andrew Morton wrote:
> Simon Fowler <[email protected]> wrote:
> >
> > On Tue, Jun 10, 2003 at 02:14:40PM -0700, Andrew Morton wrote:
> > > Simon Fowler <[email protected]> wrote:
> > > >
> > > > On Tue, Jun 10, 2003 at 04:16:54PM +1000, Simon Fowler wrote:
> > > > > 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:
> > > > >
> > > > I've narrowed the start of the problem down: 2.5.70-bk13 works,
> > > > -bk14 oopses.
> > >
> > > That's funny. bk13->bk14 was almost all arm stuff. diffstat below.
> > >
> > > It might be worth reverting this chunk, see if that fixes it:
> > >
> > > --- b/drivers/char/mem.c Thu Jun 5 23:36:40 2003
> > > +++ b/drivers/char/mem.c Sun Jun 8 05:02:24 2003
> > > @@ -716 +716 @@
> > > -__initcall(chr_dev_init);
> > > +subsys_initcall(chr_dev_init);
> > >
> > And we have a winner . . . Reverting this hunk fixes the oops.
> >
>
> So it's another initcall problem in the PCI layer.
>
> pci_enable_device_bars() is needing things which are not yet set up. A lot
> of the PCI initialisation is at subsys_initcall() as well, and you got
> unlucky with link order.
>
> I expect the below patch will fix this as well. Could you please put the
> above change back to normal and see if this one fixes it?
>
I applied this to a clean 2.5.70-bk14 tree, and it failed to boot -
I've copied the output after switching to the framebuffer:

--------------------------------------------------
onsole: switching to colour frame buffer device 160x48
pty: 256 Unix98 ptys configured.
block request queues:
4/128 requests per read queue
4/128 requests per write queue
Enter congestion at 15
Exit congestion at 17
PCI: Cannot allocate resource region 0 of device 00:14.0
PCI: Cannot allocate resource region 2 of device 00:14.0
--------------------------------------------------

00:14.0 is the Radeon.

Simon

--
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/

Attachments:

(No filename) (2.28 kB)
(No filename) (189.00 B)
Download all attachments

2003-06-11 04:01:42

by Andrew Morton

[permalink] [raw]

Subject: Re: 2.5.70-bk radeonfb oops on boot.

Simon Fowler <[email protected]> wrote:
>
> > > >
> > > > It might be worth reverting this chunk, see if that fixes it:
> > > >
> > > > --- b/drivers/char/mem.c Thu Jun 5 23:36:40 2003
> > > > +++ b/drivers/char/mem.c Sun Jun 8 05:02:24 2003
> > > > @@ -716 +716 @@
> > > > -__initcall(chr_dev_init);
> > > > +subsys_initcall(chr_dev_init);
> > > >
> > > And we have a winner . . . Reverting this hunk fixes the oops.
> > >
> >
> > So it's another initcall problem in the PCI layer.
> >
> > pci_enable_device_bars() is needing things which are not yet set up. A lot
> > of the PCI initialisation is at subsys_initcall() as well, and you got
> > unlucky with link order.
> >
> > I expect the below patch will fix this as well. Could you please put the
> > above change back to normal and see if this one fixes it?
> >
> I applied this to a clean 2.5.70-bk14 tree, and it failed to boot -
> I've copied the output after switching to the framebuffer:
>
> --------------------------------------------------
> onsole: switching to colour frame buffer device 160x48
> pty: 256 Unix98 ptys configured.
> block request queues:
> 4/128 requests per read queue
> 4/128 requests per write queue
> Enter congestion at 15
> Exit congestion at 17
> PCI: Cannot allocate resource region 0 of device 00:14.0
> PCI: Cannot allocate resource region 2 of device 00:14.0
> --------------------------------------------------
>
> 00:14.0 is the Radeon.

Thanks for testing.

All the initcall ordering of chardevs versus pci, pci versus pci and who
knows what else is all bollixed up.

Unfortunately I do not have the bandwidth to work on this.

2003-06-11 04:52:08

by Simon Fowler

[permalink] [raw]

Subject: Re: 2.5.70-bk radeonfb oops on boot.

On Tue, Jun 10, 2003 at 09:16:07PM -0700, Andrew Morton wrote:
> Simon Fowler <[email protected]> wrote:
> >
> > > > >
> > > > > It might be worth reverting this chunk, see if that fixes it:
> > > > >
> > > > > --- b/drivers/char/mem.c Thu Jun 5 23:36:40 2003
> > > > > +++ b/drivers/char/mem.c Sun Jun 8 05:02:24 2003
> > > > > @@ -716 +716 @@
> > > > > -__initcall(chr_dev_init);
> > > > > +subsys_initcall(chr_dev_init);
> > > > >
> > > > And we have a winner . . . Reverting this hunk fixes the oops.
> > > >
<snippage>
> Thanks for testing.
>
> All the initcall ordering of chardevs versus pci, pci versus pci and who
> knows what else is all bollixed up.
>
> Unfortunately I do not have the bandwidth to work on this.

Since this seems to be a showstopper for people using radeonfb,
getting the 'fix' above in might be a good idea . . .

Simon

--
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/

Attachments:

(No filename) (1.04 kB)
(No filename) (189.00 B)
Download all attachments

2003-06-11 07:37:48

by Helge Hafting

[permalink] [raw]

Subject: Re: 2.5.70-bk radeonfb oops on boot.

Simon Fowler wrote:
> On Tue, Jun 10, 2003 at 09:16:07PM -0700, Andrew Morton wrote:
>
>>Simon Fowler <[email protected]> wrote:
>>
>>>>>>It might be worth reverting this chunk, see if that fixes it:
>>>>>>
>>>>>>--- b/drivers/char/mem.c Thu Jun 5 23:36:40 2003
>>>>>>+++ b/drivers/char/mem.c Sun Jun 8 05:02:24 2003
>>>>>>@@ -716 +716 @@
>>>>>>-__initcall(chr_dev_init);
>>>>>>+subsys_initcall(chr_dev_init);
>>>>>>
>>>>>
>>>>>And we have a winner . . . Reverting this hunk fixes the oops.
>>>>>
>>>>
> <snippage>
>
>>Thanks for testing.
>>
>>All the initcall ordering of chardevs versus pci, pci versus pci and who
>>knows what else is all bollixed up.
>>
>>Unfortunately I do not have the bandwidth to work on this.
>
>
> Since this seems to be a showstopper for people using radeonfb,
> getting the 'fix' above in might be a good idea . . .

It isn't merely radeonfb. A machine with matroxfb dies
the same death, pci_enable_device_bars() oopses
before the framebuffer even comes up
with 2.5.70-mm7.

Helge Hafting