* 2.5.70-bk radeonfb oops on boot.
@ 2003-06-10 6:16 Simon Fowler
2003-06-10 6:36 ` Joshua Kwan
` (3 more replies)
0 siblings, 4 replies; 13+ messages in thread
From: Simon Fowler @ 2003-06-10 6:16 UTC (permalink / raw)
To: jsimmons; +Cc: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 4729 bytes --]
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/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: 2.5.70-bk radeonfb oops on boot.
2003-06-10 6:16 2.5.70-bk radeonfb oops on boot Simon Fowler
@ 2003-06-10 6:36 ` Joshua Kwan
2003-06-10 6:48 ` Greg KH
` (2 subsequent siblings)
3 siblings, 0 replies; 13+ messages in thread
From: Joshua Kwan @ 2003-06-10 6:36 UTC (permalink / raw)
To: Simon Fowler; +Cc: linux-kernel mailing list
[-- Attachment #1: Type: text/plain, Size: 613 bytes --]
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
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: 2.5.70-bk radeonfb oops on boot.
2003-06-10 6:16 2.5.70-bk radeonfb oops on boot Simon Fowler
2003-06-10 6:36 ` Joshua Kwan
@ 2003-06-10 6:48 ` Greg KH
2003-06-10 6:53 ` Simon Fowler
2003-06-10 13:02 ` Simon Fowler
2003-06-10 13:24 ` Helge Hafting
3 siblings, 1 reply; 13+ messages in thread
From: Greg KH @ 2003-06-10 6:48 UTC (permalink / raw)
To: jsimmons, linux-kernel
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
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: 2.5.70-bk radeonfb oops on boot.
2003-06-10 6:48 ` Greg KH
@ 2003-06-10 6:53 ` Simon Fowler
0 siblings, 0 replies; 13+ messages in thread
From: Simon Fowler @ 2003-06-10 6:53 UTC (permalink / raw)
To: Greg KH; +Cc: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]
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/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: 2.5.70-bk radeonfb oops on boot.
2003-06-10 6:16 2.5.70-bk radeonfb oops on boot Simon Fowler
2003-06-10 6:36 ` Joshua Kwan
2003-06-10 6:48 ` Greg KH
@ 2003-06-10 13:02 ` Simon Fowler
2003-06-10 21:14 ` Andrew Morton
2003-06-10 13:24 ` Helge Hafting
3 siblings, 1 reply; 13+ messages in thread
From: Simon Fowler @ 2003-06-10 13:02 UTC (permalink / raw)
To: jsimmons, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 631 bytes --]
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/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: 2.5.70-bk radeonfb oops on boot.
2003-06-10 6:16 2.5.70-bk radeonfb oops on boot Simon Fowler
` (2 preceding siblings ...)
2003-06-10 13:02 ` Simon Fowler
@ 2003-06-10 13:24 ` Helge Hafting
3 siblings, 0 replies; 13+ messages in thread
From: Helge Hafting @ 2003-06-10 13:24 UTC (permalink / raw)
To: Simon Fowler; +Cc: jsimmons, linux-kernel
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
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: 2.5.70-bk radeonfb oops on boot.
2003-06-10 13:02 ` Simon Fowler
@ 2003-06-10 21:14 ` Andrew Morton
2003-06-11 2:19 ` Simon Fowler
0 siblings, 1 reply; 13+ messages in thread
From: Andrew Morton @ 2003-06-10 21:14 UTC (permalink / raw)
To: Simon Fowler; +Cc: jsimmons, linux-kernel
Simon Fowler <simon@himi.org> 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);
Documentation/DocBook/kernel-api.tmpl | 3
Documentation/kbuild/makefiles.txt | 32
arch/alpha/kernel/asm-offsets.c | 1
arch/alpha/kernel/head.S | 3
arch/alpha/kernel/traps.c | 80
arch/alpha/lib/csum_partial_copy.c | 4
arch/alpha/lib/memmove.S | 9
b/Documentation/DocBook/Makefile | 48
b/MAINTAINERS | 42
b/Makefile | 2
b/arch/alpha/kernel/systbls.S | 1
b/arch/arm26/ACKNOWLEDGEMENTS | 27
b/arch/arm26/Config.help | 387 +++
b/arch/arm26/Kconfig | 572 ++++
b/arch/arm26/Makefile | 126 +
b/arch/arm26/boot/Makefile | 69
b/arch/arm26/boot/compressed/Makefile | 50
b/arch/arm26/boot/compressed/head.S | 517 ++++
b/arch/arm26/boot/compressed/hw-bse.c | 74
b/arch/arm26/boot/compressed/ll_char_wr.S | 162 +
b/arch/arm26/boot/compressed/misc.c | 316 ++
b/arch/arm26/boot/compressed/ofw-shark.c | 258 ++
b/arch/arm26/boot/compressed/uncompress.h | 111
b/arch/arm26/boot/compressed/vmlinux.lds.in | 60
b/arch/arm26/boot/install.sh | 62
b/arch/arm26/config.in | 151 +
b/arch/arm26/defconfig | 367 ++
b/arch/arm26/kernel/Makefile | 18
b/arch/arm26/kernel/arch.c | 30
b/arch/arm26/kernel/armksyms.c | 233 +
b/arch/arm26/kernel/asm-offsets.c | 64
b/arch/arm26/kernel/compat.c | 174 +
b/arch/arm26/kernel/dma.c | 302 ++
b/arch/arm26/kernel/ecard.c | 899 +++++++
b/arch/arm26/kernel/entry.S | 982 +++++++
b/arch/arm26/kernel/fiq.c | 202 +
b/arch/arm26/kernel/init_task.c | 41
b/arch/arm26/kernel/irq.c | 705 +++++
b/arch/arm26/kernel/process.c | 414 +++
b/arch/arm26/kernel/ptrace.c | 747 ++++++
b/arch/arm26/kernel/ptrace.h | 13
b/arch/arm26/kernel/semaphore.c | 215 +
b/arch/arm26/kernel/setup.c | 581 ++++
b/arch/arm26/kernel/signal.c | 542 ++++
b/arch/arm26/kernel/sys_arm.c | 283 ++
b/arch/arm26/kernel/time-acorn.c | 69
b/arch/arm26/kernel/time.c | 202 +
b/arch/arm26/kernel/traps.c | 553 ++++
b/arch/arm26/lib/Makefile | 31
b/arch/arm26/lib/ashldi3.c | 61
b/arch/arm26/lib/ashrdi3.c | 61
b/arch/arm26/lib/backtrace.S | 145 +
b/arch/arm26/lib/changebit.S | 28
b/arch/arm26/lib/clearbit.S | 31
b/arch/arm26/lib/copy_page.S | 62
b/arch/arm26/lib/csumipv6.S | 32
b/arch/arm26/lib/csumpartial.S | 130 +
b/arch/arm26/lib/csumpartialcopy.S | 52
b/arch/arm26/lib/csumpartialcopygeneric.S | 352 ++
b/arch/arm26/lib/csumpartialcopyuser.S | 115
b/arch/arm26/lib/delay.S | 57
b/arch/arm26/lib/ecard.S | 41
b/arch/arm26/lib/findbit.S | 67
b/arch/arm26/lib/floppydma.S | 32
b/arch/arm26/lib/gcclib.h | 21
b/arch/arm26/lib/getuser.S | 111
b/arch/arm26/lib/io-acorn.S | 71
b/arch/arm26/lib/io-readsb.S | 116
b/arch/arm26/lib/io-readsl-armv3.S | 78
b/arch/arm26/lib/io-readsw-armv3.S | 107
b/arch/arm26/lib/io-writesb.S | 122
b/arch/arm26/lib/io-writesl.S | 56
b/arch/arm26/lib/io-writesw-armv3.S | 127 +
b/arch/arm26/lib/kbd.c | 279 ++
b/arch/arm26/lib/lib1funcs.S | 314 ++
b/arch/arm26/lib/longlong.h | 184 +
b/arch/arm26/lib/lshrdi3.c | 61
b/arch/arm26/lib/memchr.S | 25
b/arch/arm26/lib/memcpy.S | 318 ++
b/arch/arm26/lib/memset.S | 80
b/arch/arm26/lib/memzero.S | 80
b/arch/arm26/lib/muldi3.c | 77
b/arch/arm26/lib/putuser.S | 108
b/arch/arm26/lib/setbit.S | 29
b/arch/arm26/lib/strchr.S | 25
b/arch/arm26/lib/strrchr.S | 25
b/arch/arm26/lib/testchangebit.S | 29
b/arch/arm26/lib/testclearbit.S | 29
b/arch/arm26/lib/testsetbit.S | 29
b/arch/arm26/lib/uaccess-kernel.S | 173 +
b/arch/arm26/lib/uaccess-user.S | 718 +++++
b/arch/arm26/lib/ucmpdi2.c | 51
b/arch/arm26/lib/udivdi3.c | 242 +
b/arch/arm26/machine/Makefile | 12
b/arch/arm26/machine/arch.c | 36
b/arch/arm26/machine/dma.c | 215 +
b/arch/arm26/machine/head.S | 93
b/arch/arm26/machine/irq.c | 165 +
b/arch/arm26/machine/oldlatches.c | 72
b/arch/arm26/machine/small_page.c | 191 +
b/arch/arm26/mm/Makefile | 12
b/arch/arm26/mm/extable.c | 40
b/arch/arm26/mm/fault.c | 318 ++
b/arch/arm26/mm/fault.h | 5
b/arch/arm26/mm/init.c | 401 +++
b/arch/arm26/mm/mm-memc.c | 204 +
b/arch/arm26/mm/proc-funcs.S | 359 ++
b/arch/arm26/nwfpe/ARM-gcc.h | 120
b/arch/arm26/nwfpe/ChangeLog | 83
b/arch/arm26/nwfpe/Makefile | 15
b/arch/arm26/nwfpe/double_cpdo.c | 288 ++
b/arch/arm26/nwfpe/entry.S | 114
b/arch/arm26/nwfpe/extended_cpdo.c | 273 ++
b/arch/arm26/nwfpe/fpa11.c | 221 +
b/arch/arm26/nwfpe/fpa11.h | 87
b/arch/arm26/nwfpe/fpa11.inl | 51
b/arch/arm26/nwfpe/fpa11_cpdo.c | 117
b/arch/arm26/nwfpe/fpa11_cpdt.c | 368 ++
b/arch/arm26/nwfpe/fpa11_cprt.c | 289 ++
b/arch/arm26/nwfpe/fpmodule.c | 182 +
b/arch/arm26/nwfpe/fpmodule.h | 47
b/arch/arm26/nwfpe/fpmodule.inl | 84
b/arch/arm26/nwfpe/fpopcode.c | 148 +
b/arch/arm26/nwfpe/fpopcode.h | 372 +++
b/arch/arm26/nwfpe/fpsr.h | 108
b/arch/arm26/nwfpe/milieu.h | 48
b/arch/arm26/nwfpe/single_cpdo.c | 255 ++
b/arch/arm26/nwfpe/softfloat-macros | 740 ++++++
b/arch/arm26/nwfpe/softfloat-specialize | 366 ++
b/arch/arm26/nwfpe/softfloat.c | 3439 ++++++++++++++++++++++++++++
b/arch/arm26/nwfpe/softfloat.h | 232 +
b/arch/arm26/vmlinux-armo.lds.in | 128 +
b/arch/arm26/vmlinux.lds.S | 12
b/drivers/char/mem.c | 2
b/include/asm-alpha/ptrace.h | 11
b/include/asm-alpha/unistd.h | 3
b/include/asm-arm26/a.out.h | 38
b/include/asm-arm26/arch.h | 62
b/include/asm-arm26/assembler.h | 106
b/include/asm-arm26/atomic.h | 115
b/include/asm-arm26/bitops.h | 349 ++
b/include/asm-arm26/bug.h | 21
b/include/asm-arm26/bugs.h | 15
b/include/asm-arm26/byteorder.h | 24
b/include/asm-arm26/cache.h | 19
b/include/asm-arm26/cacheflush.h | 44
b/include/asm-arm26/calls.h | 262 ++
b/include/asm-arm26/checksum.h | 158 +
b/include/asm-arm26/constants.h | 29
b/include/asm-arm26/current.h | 15
b/include/asm-arm26/delay.h | 34
b/include/asm-arm26/div64.h | 14
b/include/asm-arm26/dma.h | 184 +
b/include/asm-arm26/ecard.h | 291 ++
b/include/asm-arm26/elf.h | 77
b/include/asm-arm26/errno.h | 6
b/include/asm-arm26/fcntl.h | 86
b/include/asm-arm26/fiq.h | 37
b/include/asm-arm26/floppy.h | 141 +
b/include/asm-arm26/fpstate.h | 29
b/include/asm-arm26/hardirq.h | 93
b/include/asm-arm26/hardware.h | 109
b/include/asm-arm26/hdreg.h | 15
b/include/asm-arm26/ian_char.h | 79
b/include/asm-arm26/ide.h | 75
b/include/asm-arm26/io.h | 419 +++
b/include/asm-arm26/ioc.h | 72
b/include/asm-arm26/ioctl.h | 74
b/include/asm-arm26/ioctls.h | 81
b/include/asm-arm26/ipc.h | 28
b/include/asm-arm26/ipcbuf.h | 29
b/include/asm-arm26/irq.h | 50
b/include/asm-arm26/irqchip.h | 118
b/include/asm-arm26/keyboard.h.old | 78
b/include/asm-arm26/kmap_types.h | 12
b/include/asm-arm26/leds.h | 51
b/include/asm-arm26/limits.h | 11
b/include/asm-arm26/linkage.h | 7
b/include/asm-arm26/linux_logo.h | 19
b/include/asm-arm26/locks.h | 161 +
b/include/asm-arm26/mach-types.h | 36
b/include/asm-arm26/map.h | 24
b/include/asm-arm26/mc146818rtc.h | 28
b/include/asm-arm26/memory.h | 101
b/include/asm-arm26/mman.h | 41
b/include/asm-arm26/mmu.h | 9
b/include/asm-arm26/mmu_context.h | 51
b/include/asm-arm26/module.h | 12
b/include/asm-arm26/msgbuf.h | 31
b/include/asm-arm26/namei.h | 25
b/include/asm-arm26/oldlatches.h | 37
b/include/asm-arm26/page.h | 115
b/include/asm-arm26/param.h | 37
b/include/asm-arm26/parport.h | 18
b/include/asm-arm26/pci.h | 5
b/include/asm-arm26/percpu.h | 6
b/include/asm-arm26/pgalloc.h | 70
b/include/asm-arm26/pgtable.h | 298 ++
b/include/asm-arm26/poll.h | 25
b/include/asm-arm26/posix_types.h | 81
b/include/asm-arm26/proc-fns.h | 49
b/include/asm-arm26/processor.h | 121
b/include/asm-arm26/procinfo.h | 56
b/include/asm-arm26/ptrace.h | 103
b/include/asm-arm26/resource.h | 47
b/include/asm-arm26/rmap.h | 66
b/include/asm-arm26/scatterlist.h | 26
b/include/asm-arm26/segment.h | 11
b/include/asm-arm26/semaphore-helper.h | 84
b/include/asm-arm26/semaphore.h | 128 +
b/include/asm-arm26/sembuf.h | 25
b/include/asm-arm26/serial.h | 65
b/include/asm-arm26/setup.h | 205 +
b/include/asm-arm26/shmbuf.h | 42
b/include/asm-arm26/shmparam.h | 15
b/include/asm-arm26/sigcontext.h | 33
b/include/asm-arm26/siginfo.h | 6
b/include/asm-arm26/signal.h | 201 +
b/include/asm-arm26/sizes.h | 52
b/include/asm-arm26/smp.h | 10
b/include/asm-arm26/socket.h | 64
b/include/asm-arm26/sockios.h | 12
b/include/asm-arm26/softirq.h | 20
b/include/asm-arm26/spinlock.h | 6
b/include/asm-arm26/stat.h | 79
b/include/asm-arm26/statfs.h | 25
b/include/asm-arm26/string.h | 43
b/include/asm-arm26/suspend.h | 4
b/include/asm-arm26/sysirq.h | 61
b/include/asm-arm26/system.h | 204 +
b/include/asm-arm26/termbits.h | 170 +
b/include/asm-arm26/termios.h | 108
b/include/asm-arm26/thread_info.h | 144 +
b/include/asm-arm26/timex.h | 31
b/include/asm-arm26/tlb.h | 62
b/include/asm-arm26/tlbflush.h | 70
b/include/asm-arm26/topology.h | 6
b/include/asm-arm26/types.h | 59
b/include/asm-arm26/uaccess-asm.h | 151 +
b/include/asm-arm26/uaccess.h | 260 ++
b/include/asm-arm26/ucontext.h | 12
b/include/asm-arm26/unaligned.h | 118
b/include/asm-arm26/uncompress.h | 111
b/include/asm-arm26/unistd.h | 481 +++
b/include/asm-arm26/user.h | 84
b/include/asm-arm26/xor.h | 141 +
b/include/linux/zconf.h | 2
b/include/linux/zlib.h | 18
b/include/linux/zutil.h | 9
b/lib/zlib_deflate/deflate.c | 72
b/lib/zlib_deflate/deftree.c | 88
b/lib/zlib_inflate/infblock.c | 20
b/lib/zlib_inflate/infcodes.c | 10
b/lib/zlib_inflate/inffast.c | 45
b/lib/zlib_inflate/inflate.c | 34
b/lib/zlib_inflate/inftrees.c | 23
b/lib/zlib_inflate/infutil.c | 4
drivers/net/sis900.c | 72
include/asm-alpha/string.h | 1
include/asm-alpha/uaccess.h | 69
include/asm-alpha/unaligned.h | 2
kernel/kmod.c | 2
lib/zlib_inflate/inffixed.h | 8
scripts/docproc.c | 2
scripts/kernel-doc | 15
265 files changed, 34906 insertions(+), 359 deletions(-)
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: 2.5.70-bk radeonfb oops on boot.
2003-06-10 21:14 ` Andrew Morton
@ 2003-06-11 2:19 ` Simon Fowler
2003-06-11 3:16 ` Andrew Morton
0 siblings, 1 reply; 13+ messages in thread
From: Simon Fowler @ 2003-06-11 2:19 UTC (permalink / raw)
To: Andrew Morton; +Cc: jsimmons, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]
On Tue, Jun 10, 2003 at 02:14:40PM -0700, Andrew Morton wrote:
> Simon Fowler <simon@himi.org> 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/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: 2.5.70-bk radeonfb oops on boot.
2003-06-11 2:19 ` Simon Fowler
@ 2003-06-11 3:16 ` Andrew Morton
2003-06-11 3:55 ` Simon Fowler
0 siblings, 1 reply; 13+ messages in thread
From: Andrew Morton @ 2003-06-11 3:16 UTC (permalink / raw)
To: Simon Fowler; +Cc: jsimmons, linux-kernel
Simon Fowler <simon@himi.org> wrote:
>
> On Tue, Jun 10, 2003 at 02:14:40PM -0700, Andrew Morton wrote:
> > Simon Fowler <simon@himi.org> 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);
_
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: 2.5.70-bk radeonfb oops on boot.
2003-06-11 3:16 ` Andrew Morton
@ 2003-06-11 3:55 ` Simon Fowler
2003-06-11 4:16 ` Andrew Morton
0 siblings, 1 reply; 13+ messages in thread
From: Simon Fowler @ 2003-06-11 3:55 UTC (permalink / raw)
To: Andrew Morton; +Cc: jsimmons, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 2397 bytes --]
On Tue, Jun 10, 2003 at 08:16:41PM -0700, Andrew Morton wrote:
> Simon Fowler <simon@himi.org> wrote:
> >
> > On Tue, Jun 10, 2003 at 02:14:40PM -0700, Andrew Morton wrote:
> > > Simon Fowler <simon@himi.org> 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/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: 2.5.70-bk radeonfb oops on boot.
2003-06-11 3:55 ` Simon Fowler
@ 2003-06-11 4:16 ` Andrew Morton
2003-06-11 5:05 ` Simon Fowler
0 siblings, 1 reply; 13+ messages in thread
From: Andrew Morton @ 2003-06-11 4:16 UTC (permalink / raw)
To: Simon Fowler; +Cc: jsimmons, linux-kernel
Simon Fowler <simon@himi.org> 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.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: 2.5.70-bk radeonfb oops on boot.
2003-06-11 4:16 ` Andrew Morton
@ 2003-06-11 5:05 ` Simon Fowler
2003-06-11 7:56 ` Helge Hafting
0 siblings, 1 reply; 13+ messages in thread
From: Simon Fowler @ 2003-06-11 5:05 UTC (permalink / raw)
To: Andrew Morton; +Cc: jsimmons, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]
On Tue, Jun 10, 2003 at 09:16:07PM -0700, Andrew Morton wrote:
> Simon Fowler <simon@himi.org> 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/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: 2.5.70-bk radeonfb oops on boot.
2003-06-11 5:05 ` Simon Fowler
@ 2003-06-11 7:56 ` Helge Hafting
0 siblings, 0 replies; 13+ messages in thread
From: Helge Hafting @ 2003-06-11 7:56 UTC (permalink / raw)
To: Simon Fowler; +Cc: Andrew Morton, jsimmons, linux-kernel
Simon Fowler wrote:
> On Tue, Jun 10, 2003 at 09:16:07PM -0700, Andrew Morton wrote:
>
>>Simon Fowler <simon@himi.org> 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
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2003-06-11 7:37 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-06-10 6:16 2.5.70-bk radeonfb oops on boot Simon Fowler
2003-06-10 6:36 ` Joshua Kwan
2003-06-10 6:48 ` Greg KH
2003-06-10 6:53 ` Simon Fowler
2003-06-10 13:02 ` Simon Fowler
2003-06-10 21:14 ` Andrew Morton
2003-06-11 2:19 ` Simon Fowler
2003-06-11 3:16 ` Andrew Morton
2003-06-11 3:55 ` Simon Fowler
2003-06-11 4:16 ` Andrew Morton
2003-06-11 5:05 ` Simon Fowler
2003-06-11 7:56 ` Helge Hafting
2003-06-10 13:24 ` Helge Hafting
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox