2006-01-05 17:01:42

by Alexander Gran

[permalink] [raw]
Subject: Re. 2.6.15-mm1

Hi,

just tried 2.6.15-mm1 on my thinkpad. Various aspects that didn't work / look
good:
Jan 5 16:22:38 t40 kernel: pnp: PnP ACPI init
Jan 5 16:22:38 t40 kernel: pnp: PnPACPI: unknown resource type 7
Jan 5 16:22:38 t40 kernel: pnp: PnPACPI: unknown resource type 7
Jan 5 16:22:39 t40 last message repeated 10 times
Jan 5 16:22:39 t40 kernel: pnp: PnP ACPI: found 0 devices
All over the place logs like this:
Jan 5 16:22:43 t40 kernel: **** SET: Misaligned resource pointer: f7db5502
Type 07 Len 0
Unknown to me so far..
When X startet, the laptops crashed:
Jan 5 16:22:43 t40 kernel: <4>reiser4[syslogd(2729)]: disable_write_barrier
(fs/reiser4/wander.c:233)[zam-1055]:
Jan 5 16:22:43 t40 kernel: WARNING: disabling write barrier
Jan 5 16:22:43 t40 kernel:
Jan 5 16:22:47 t40 kernel: mtrr: 0xe0000000,0x8000000 overlaps existing
0xe0000000,0x4000000
Jan 5 16:22:48 t40 last message repeated 2 times
Jan 5 16:22:48 t40 kernel: agpgart: Found an AGP 2.0 compliant device at
0000:00:00.0.
Jan 5 16:22:48 t40 kernel: c028b7cf
Jan 5 16:22:48 t40 kernel: Modules linked in: irtty_sir sir_dev cfq_iosched
ehci_hcd uhci_hcd
Jan 5 16:22:48 t40 kernel: EIP: 0060:[<c028b7cf>] Not tainted VLI
Jan 5 16:22:48 t40 kernel: EFLAGS: 00013202 (2.6.15-mm1)
Jan 5 16:22:48 t40 kernel: <0>c028b9e9 f762ff08 00000002 00000000
c19720ec 00000000 1f000217 c1a79400
Jan 5 16:22:48 t40 kernel: <0>00000032 00000001 c028bfb5 c0297262
c1a79400 c02972af 1f000207 c029727f
Jan 5 16:22:48 t40 kernel: <3>[drm:drm_release] *ERROR* Device busy: 1 0
Jan 5 16:22:58 t40 kernel: SysRq : Emergency Sync
Jan 5 16:22:58 t40 kernel: <4>reiser4[pdflush(172)]: disable_write_barrier
(fs/reiser4/wander.c:233)[zam-1055]:
Jan 5 16:22:58 t40 kernel: WARNING: disabling write barrier
Jan 5 16:22:59 t40 kernel:

Dunno why. Sysrq worked, however
lspci:
0000:00:00.0 Host bridge: Intel Corporation 82855PM Processor to I/O
Controller (rev 03)
0000:00:01.0 PCI bridge: Intel Corporation 82855PM Processor to AGP Controller
(rev 03)
0000:00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
0000:00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)
0000:00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)
0000:00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2
EHCI Controller (rev 01)
0000:00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 81)
0000:00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface
Bridge (rev 01)
0000:00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller
(rev 01)
0000:00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
SMBus Controller (rev 01)
0000:00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
0000:00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
AC'97 Modem Controller (rev 01)
0000:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 Lf
[FireGL 9000] (rev 02)
0000:02:00.0 CardBus bridge: Texas Instruments PCI1520 PC card Cardbus
Controller (rev 01)
0000:02:00.1 CardBus bridge: Texas Instruments PCI1520 PC card Cardbus
Controller (rev 01)
0000:02:01.0 Ethernet controller: Intel Corporation 82540EP Gigabit Ethernet
Controller (Mobile) (rev 03)
0000:02:02.0 Ethernet controller: Atheros Communications, Inc. AR5211 802.11ab
NIC (rev 01)

.config and full bootlog attached.


regards
Alex
--
Encrypted Mails welcome.
PGP-Key at http://zodiac.dnsalias.org/misc/pgpkey.asc | Key-ID: 0x6D7DD291


Attachments:
(No filename) (0.00 B)
(No filename) (189.00 B)
Download all attachments

2006-01-05 22:48:04

by Andrew Morton

[permalink] [raw]
Subject: Re: Re. 2.6.15-mm1

Alexander Gran <[email protected]> wrote:
>
> Hi,
>
> just tried 2.6.15-mm1 on my thinkpad. Various aspects that didn't work / look
> good:

Thanks. A few people have some work to do before they are ready to merge to 2.6.16.

> Jan 5 16:22:38 t40 kernel: pnp: PnP ACPI init
> Jan 5 16:22:38 t40 kernel: pnp: PnPACPI: unknown resource type 7
> Jan 5 16:22:38 t40 kernel: pnp: PnPACPI: unknown resource type 7
> Jan 5 16:22:39 t40 last message repeated 10 times
> Jan 5 16:22:39 t40 kernel: pnp: PnP ACPI: found 0 devices

pnpacpi is unhappy.

> All over the place logs like this:
> Jan 5 16:22:43 t40 kernel: **** SET: Misaligned resource pointer: f7db5502
> Type 07 Len 0
> Unknown to me so far..

acpi is unhappy.

> When X startet, the laptops crashed:
> Jan 5 16:22:43 t40 kernel: <4>reiser4[syslogd(2729)]: disable_write_barrier
> (fs/reiser4/wander.c:233)[zam-1055]:
> Jan 5 16:22:43 t40 kernel: WARNING: disabling write barrier

Vladimir, is that expected?

> Jan 5 16:22:43 t40 kernel:
> Jan 5 16:22:47 t40 kernel: mtrr: 0xe0000000,0x8000000 overlaps existing
> 0xe0000000,0x4000000
> Jan 5 16:22:48 t40 last message repeated 2 times

Is that new?

> Jan 5 16:22:48 t40 kernel: agpgart: Found an AGP 2.0 compliant device at
> 0000:00:00.0.
> Jan 5 16:22:48 t40 kernel: c028b7cf
> Jan 5 16:22:48 t40 kernel: Modules linked in: irtty_sir sir_dev cfq_iosched
> ehci_hcd uhci_hcd
> Jan 5 16:22:48 t40 kernel: EIP: 0060:[<c028b7cf>] Not tainted VLI
> Jan 5 16:22:48 t40 kernel: EFLAGS: 00013202 (2.6.15-mm1)
> Jan 5 16:22:48 t40 kernel: <0>c028b9e9 f762ff08 00000002 00000000
> c19720ec 00000000 1f000217 c1a79400
> Jan 5 16:22:48 t40 kernel: <0>00000032 00000001 c028bfb5 c0297262
> c1a79400 c02972af 1f000207 c029727f

hm, it's not clear what oopsed. Can you get a cleaner copy of this?

> Jan 5 16:22:48 t40 kernel: <3>[drm:drm_release] *ERROR* Device busy: 1 0

drm is unhappy

2006-01-05 23:31:33

by Etienne Lorrain

[permalink] [raw]
Subject: Re: Re. 2.6.15-mm1

I have my own OOPs with 2.6.15-mm1, this kind:

Jan 5 22:40:04 localhost fstab-sync[1919]: added mount point /media/floppy
for /dev/fd0
Jan 5 22:41:37 localhost kernel: Unable to handle kernel NULL pointer
dereference at virtual address 00000010
Jan 5 22:41:37 localhost kernel: printing eip:
Jan 5 22:41:37 localhost kernel: c013da3a
Jan 5 22:41:37 localhost kernel: *pde = 1d165067
Jan 5 22:41:37 localhost kernel: *pte = 00000000
Jan 5 22:41:37 localhost kernel: Oops: 0000 [#1]
Jan 5 22:41:37 localhost kernel: last sysfs file: /class/vc/vcs7/dev
Jan 5 22:41:37 localhost kernel: Modules linked in: autofs4 pcmcia
ipt_REJECT ipt_state ip_conntrack iptable_filter ip_tables vfat fat
yenta_socket rsrc_nonstatic pcmcia_core uhci_hcd ehci_hcd i2c_viapro
i2c_core snd_via82xx snd_ac97_codec snd_ac97_bus snd_seq_dummy snd_seq_oss
snd_seq_midi_event snd_seq snd_pcm_oss snd_mixer_oss snd_pcm snd_timer
snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore ext3
jbd
Jan 5 22:41:37 localhost kernel: CPU: 0
Jan 5 22:41:37 localhost kernel: EIP: 0060:[<c013da3a>] Not tainted
VLI
Jan 5 22:41:37 localhost kernel: EFLAGS: 00013256 (2.6.15-mm1)
Jan 5 22:41:37 localhost kernel: EIP is at __audit_inode+0xba/0x190
Jan 5 22:41:37 localhost kernel: eax: 00000008 ebx: 00000000 ecx:
dcbf02c0 edx: d9343268
Jan 5 22:41:37 localhost kernel: esi: d922ef44 edi: d9fd3000 ebp:
dcbf02c0 esp: d922ee88
Jan 5 22:41:37 localhost kernel: ds: 007b es: 007b ss: 0068
Jan 5 22:41:37 localhost kernel: Process X (pid: 2192, threadinfo=d922e000
task=d8abcff0)
Jan 5 22:41:37 localhost kernel: Stack: <0>00000003 00000000 dcbf02c0
fffffffe d922ef44 d9fd3000 00000003 c017002c
Jan 5 22:41:37 localhost kernel: <0>d9fd3000 d9343268 00000101
00000101 00000101 d922ef44 ffffffe9 00000003
Jan 5 22:41:37 localhost kernel: <0>c0170096 d922e000 00000002
d922ef44 00000006 c017011f d9fd3000 00000001
Jan 5 22:41:38 localhost gdm[2183]: gdm_slave_xioerror_handler: Fatal X
error - Restarting :0
Jan 5 22:41:38 localhost kernel: Call Trace:
Jan 5 22:41:39 localhost kernel: [<c017002c>] path_lookup+0x1ac/0x1d0
Jan 5 22:41:40 localhost kernel: [<c0170096>]
__path_lookup_intent_open+0x46/0xa0
Jan 5 22:41:41 localhost kernel: [<c017011f>] path_lookup_open+0x2f/0x40
Jan 5 22:41:41 localhost kernel: [<c0170b33>] open_namei+0x73/0x530
Jan 5 22:41:42 localhost kernel: [<c0144cdd>] __alloc_pages+0x5d/0x390
Jan 5 22:41:42 localhost kernel: [<c015e8b8>] filp_open+0x38/0x60
Jan 5 22:41:42 localhost kernel: [<c015eaf0>] get_unused_fd+0xb0/0xe0
Jan 5 22:41:42 localhost kernel: [<c015ec45>] do_sys_open+0x55/0x100
Jan 5 22:41:42 localhost kernel: [<c01031a5>] syscall_call+0x7/0xb
Jan 5 22:41:43 localhost kernel: Code: 42 38 89 d8 c1 e0 05 8d 04 98 c7 44
10 3c 00 00 00 00 89 d8 8b 54 24 24 8b 4c 24 08 c1 e0 05 8d 04 98 8d 2c 08
8b 82 c4 00 00 00 <8b> 40 08 89 45 48 0f b7 42 28 66 89 45 4c 8b 42 30 89 45
50 8b
Jan 5 22:44:05 localhost shutdown: shutting down for system reboot
Jan 5 22:44:05 localhost init: Switching to runlevel: 6
Jan 5 22:44:17 localhost shutdown: shutting down for system reboot
Jan 5 22:44:26 localhost dbus: avc: 2 AV entries and 2/512 buckets used,
longest chain length 1
Jan 5 22:44:32 localhost xfs[1848]: terminating
Jan 5 22:44:34 localhost shutdown: shutting down for system reboot
Jan 5 22:44:41 localhost last message repeated 7 times
Jan 5 22:44:58 localhost kernel: <6>[drm] Initialized drm 1.0.1 20051102
Jan 5 22:44:59 localhost kernel: [drm] Initialized radeon 1.21.0 20051229
on minor 0
Jan 5 22:45:01 localhost kernel: mtrr: 0xd0000000,0x8000000 overlaps
existing 0xd0000000,0x4000000
Jan 5 22:45:01 localhost kernel: agpgart: Found an AGP 3.5 compliant device
at 0000:00:00.0.
Jan 5 22:45:01 localhost kernel: Unable to handle kernel NULL pointer
dereference at virtual address 00000020
Jan 5 22:45:01 localhost kernel: printing eip:
Jan 5 22:45:01 localhost kernel: c0250b08
Jan 5 22:45:01 localhost kernel: *pde = 1d4d1067
Jan 5 22:45:01 localhost kernel: *pte = 00000000
Jan 5 22:45:01 localhost kernel: Oops: 0000 [#2]
Jan 5 22:45:01 localhost kernel: last sysfs file: /class/drm/card0/dev
Jan 5 22:45:01 localhost kernel: Modules linked in: radeon drm autofs4
pcmcia ipt_REJECT ipt_state ip_conntrack iptable_filter ip_tables vfat fat
yenta_socket rsrc_nonstatic pcmcia_core uhci_hcd ehci_hcd i2c_viapro
i2c_core snd_via82xx snd_ac97_codec snd_ac97_bus snd_seq_dummy snd_seq_oss
snd_seq_midi_event snd_seq snd_pcm_oss snd_mixer_oss snd_pcm snd_timer
snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore ext3
jbd
Jan 5 22:45:01 localhost kernel: CPU: 0
Jan 5 22:45:01 localhost kernel: EIP: 0060:[<c0250b08>] Not tainted
VLI
Jan 5 22:45:01 localhost kernel: EFLAGS: 00013282 (2.6.15-mm1)
Jan 5 22:45:01 localhost kernel: EIP is at
agp_collect_device_status+0x18/0x130
Jan 5 22:45:01 localhost kernel: eax: 00000058 ebx: df8cd008 ecx:
00003092 edx: 00000058
Jan 5 22:45:01 localhost kernel: esi: 00000032 edi: 00000001 ebp:
ddfb3900 esp: d978ceb4
Jan 5 22:45:01 localhost kernel: ds: 007b es: 007b ss: 0068
Jan 5 22:45:01 localhost kernel: Process X (pid: 2266, threadinfo=d978c000
task=db21a960)
Jan 5 22:45:01 localhost kernel: Stack: <0>00000000 00000084 00000004
d978cec4 1f000a07 df8cd008 00000032 00000001
Jan 5 22:45:01 localhost kernel: <0>ddfb3900 c0250ddd df8cd008
1f000201 1f000a07 d978cef0 ddfb3900 1f000a07
Jan 5 22:45:01 localhost kernel: <0>da0c6060 e14acd9f df8cd008
1f000201 da0c6060 e14ace09 da0c6060 1f000201
Jan 5 22:45:02 localhost kernel: Call Trace:
Jan 5 22:45:02 localhost kernel: [<c0250ddd>]
agp_generic_enable+0x8d/0x160
Jan 5 22:45:02 localhost kernel: [<e14acd9f>] drm_agp_enable+0x3f/0x60
[drm]
Jan 5 22:45:04 localhost kernel: [<e14ace09>]
drm_agp_enable_ioctl+0x49/0x60 [drm]
Jan 5 22:45:05 localhost kernel: [<e14acdc0>]
drm_agp_enable_ioctl+0x0/0x60 [drm]
Jan 5 22:45:05 localhost kernel: [<e14a80ba>] drm_ioctl+0xaa/0x216 [drm]
Jan 5 22:45:05 localhost kernel: [<c0173c41>] do_ioctl+0x81/0x90
Jan 5 22:45:06 localhost kernel: [<c0173db0>] vfs_ioctl+0x60/0x1f0
Jan 5 22:45:06 localhost kernel: [<c0173fc8>] sys_ioctl+0x88/0xa0
Jan 5 22:45:06 localhost kernel: [<c01031a5>] syscall_call+0x7/0xb
Jan 5 22:45:06 localhost kernel: Code: c4 08 89 f2 5b 5e 0f b6 c2 c3 89 f6
8d bc 27 00 00 00 00 83 ec 24 89 5c 24 14 89 74 24 18 89 7c 24 1c 89 6c 24
20 e8 98 ff ff ff <8b> 15 20 00 00 00 8b 0d 10 00 00 00 8d 6c 24 10 0f b6 c0
83 c0
Jan 5 22:45:07 localhost kernel: <3>[drm:drm_release] *ERROR* Device busy:
1 0
Jan 5 22:45:15 localhost shutdown: shutting down for system reboot

But because my command line is:
Jan 5 22:39:29 localhost kernel: Kernel command line:
/boot/linux-2.6.15-mm1a.kgz video=vesa keyboard=uk NumLock=on
mouse=/dev/psaux COLS=160 LINES=64 LANG=en rhgb ro root=/dev/hda3
ide0=0x1f0,0x3f6,14 ide1=0x170,0x376
those may not count - even if it is unrelated.

I have:
Jan 5 22:39:29 localhost kernel: Linux version 2.6.15-mm1
([email protected]) (gcc version 4.0.1 20050727 (Red Hat
4.0.1-5)) #1 Thu Jan 5 21:25:17 GMT 2006


The only other strange thing is:
Jan 5 22:39:29 localhost kernel: PCI: Using IRQ router VIA [1106/3177] at
0000:00:11.0
Jan 5 22:39:29 localhost kernel:
Jan 5 22:39:29 localhost kernel: PCI: IRQ 0 for device 0000:00:06.0 doesn't
match PIRQ mask - try pci=usepirqmask
Jan 5 22:39:29 localhost kernel: PCI: Sharing IRQ 5 with 0000:00:10.1
Jan 5 22:39:29 localhost kernel:
Jan 5 22:39:29 localhost kernel: PCI: IRQ 0 for device 0000:00:11.1 doesn't
match PIRQ mask - try pci=usepirqmask
but it is not new with -mm1.

Etienne.






___________________________________________________________________________
Nouveau : t?l?phonez moins cher avec Yahoo! Messenger ! D?couvez les tarifs exceptionnels pour appeler la France et l'international.
T?l?chargez sur http://fr.messenger.yahoo.com

2006-01-05 23:33:46

by Alexander Gran

[permalink] [raw]
Subject: Re: Re. 2.6.15-mm1

Am Donnerstag, 5. Januar 2006 23:47 schrieb Andrew Morton:
> > Jan 5 16:22:47 t40 kernel: mtrr: 0xe0000000,0x8000000 overlaps existing
> > 0xe0000000,0x4000000
> > Jan 5 16:22:48 t40 last message repeated 2 times
>
> Is that new?

Umm, no. I just thought it could be related to the X oops.

> hm, it's not clear what oopsed. Can you get a cleaner copy of this?

Hmm. I just rebooted to 2.6.15-mm1 runlevel one, fired up network and an sshd.
So I could ssh back to the oops machine. Well. X is clearer but even more
errors are in the logs now ;).
First the X oops:
EDAC PCI- Detected Parity Error on 0000:00:1e.0
mtrr: 0xe0000000,0x8000000 overlaps existing 0xe0000000,0x4000000
mtrr: 0xe0000000,0x8000000 overlaps existing 0xe0000000,0x4000000
mtrr: 0xe0000000,0x8000000 overlaps existing 0xe0000000,0x4000000
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Unable to handle kernel NULL pointer dereference at virtual address 00000020
printing eip:
c028b7cf
*pde = 372d4067
*pte = 00000000
Oops: 0000 [#1]
PREEMPT
last sysfs file: /block/hda/queue/scheduler
Modules linked in: aes_i586 cfq_iosched ehci_hcd uhci_hcd
CPU: 0
EIP: 0060:[<c028b7cf>] Not tainted VLI
EFLAGS: 00013202 (2.6.15-mm1)
EIP is at agp_collect_device_status+0x14/0xd4
eax: 00000058 ebx: f75c1f08 ecx: 00000000 edx: 00000058
esi: 1f000207 edi: c19a80c0 ebp: c19af428 esp: f75c1ed0
ds: 007b es: 007b ss: 0068
Process Xorg (pid: 3843, threadinfo=f75c0000 task=f7890550)
Stack: <0>00003246 1f000217 1f000207 1f000217 f75c1f08 1f000207 c19a80c0
c19af428
<0>c028b9e9 f75c1f08 00000002 00000000 c19720ec 00000000 1f000217
c19af400
<0>00000032 00000001 c028bfb5 c0297262 c19af400 c02972af 1f000207
c029727f
Call Trace:
[<c028b9e9>] agp_generic_enable+0x72/0x10f
[<c028bfb5>] agp_enable+0xa/0xb
[<c0297262>] drm_agp_enable+0x2c/0x49
[<c02972af>] drm_agp_enable_ioctl+0x30/0x39
[<c029727f>] drm_agp_enable_ioctl+0x0/0x39
[<c029311d>] drm_ioctl+0x93/0x1e4
[<c0163664>] do_ioctl+0x64/0x6d
[<c01637a9>] vfs_ioctl+0x50/0x1be
[<c01ae603>] write_unix_file+0x0/0x500
[<c016394b>] sys_ioctl+0x34/0x51
[<c0102d0f>] sysenter_past_esp+0x54/0x75
Code: 02 00 00 00 e8 94 66 f9 ff 89 c6 84 c0 74 de 89 f2 0f b6 c2 5b 5e c3 55
57 56 53 83 ec 10 89 54 24 08 89 4c 24 04 e8 bc ff ff ff <8b> 15 20 00 00 00
8b 1d 10 00 00 0
0 0f b6 c0 8d 48 04 8d 6c 24
<3>[drm:drm_release] *ERROR* Device busy: 1 0
EDAC PCI- Detected Parity Error on 0000:00:1e.0

Additionally every second or so I got these console (and kernel of cource)
message:
EDAC PCI- Detected Parity Error on 0000:00:1e.0
lspci:
0000:00:00.0 Host bridge: Intel Corporation 82855PM Processor to I/O
Controller (rev 03)
0000:00:01.0 PCI bridge: Intel Corporation 82855PM Processor to AGP Controller
(rev 03)
0000:00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
0000:00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)
0000:00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)
0000:00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2
EHCI Controller (rev 01)
0000:00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 81)
0000:00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface
Bridge (rev 01)
0000:00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller
(rev 01)
0000:00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
SMBus Controller (rev 01)
0000:00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
0000:00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
AC'97 Modem Controller (rev 01)
0000:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 Lf
[FireGL 9000] (rev 02)
0000:02:00.0 CardBus bridge: Texas Instruments PCI1520 PC card Cardbus
Controller (rev 01)
0000:02:00.1 CardBus bridge: Texas Instruments PCI1520 PC card Cardbus
Controller (rev 01)
0000:02:01.0 Ethernet controller: Intel Corporation 82540EP Gigabit Ethernet
Controller (Mobile) (rev 03)
0000:02:02.0 Ethernet controller: Atheros Communications, Inc. AR5211 802.11ab
NIC (rev 01)

Full log again attached

--
Encrypted Mails welcome.
PGP-Key at http://zodiac.dnsalias.org/misc/pgpkey.asc | Key-ID: 0x6D7DD291


Attachments:
(No filename) (0.00 B)
(No filename) (189.00 B)
Download all attachments

2006-01-06 00:15:40

by Andrew Morton

[permalink] [raw]
Subject: Re: Re. 2.6.15-mm1

Etienne Lorrain <[email protected]> wrote:
>
> I have my own OOPs with 2.6.15-mm1, this kind:

Thanks for the report. This kernel seems to have been a bit of a disaster
- too much eggnog or something.

> Jan 5 22:40:04 localhost fstab-sync[1919]: added mount point /media/floppy
> for /dev/fd0
> Jan 5 22:41:37 localhost kernel: Unable to handle kernel NULL pointer
> dereference at virtual address 00000010
> Jan 5 22:41:37 localhost kernel: printing eip:
> Jan 5 22:41:37 localhost kernel: c013da3a
> Jan 5 22:41:37 localhost kernel: *pde = 1d165067
> Jan 5 22:41:37 localhost kernel: *pte = 00000000
> Jan 5 22:41:37 localhost kernel: Oops: 0000 [#1]
> Jan 5 22:41:37 localhost kernel: last sysfs file: /class/vc/vcs7/dev
> Jan 5 22:41:37 localhost kernel: Modules linked in: autofs4 pcmcia
> ipt_REJECT ipt_state ip_conntrack iptable_filter ip_tables vfat fat
> yenta_socket rsrc_nonstatic pcmcia_core uhci_hcd ehci_hcd i2c_viapro
> i2c_core snd_via82xx snd_ac97_codec snd_ac97_bus snd_seq_dummy snd_seq_oss
> snd_seq_midi_event snd_seq snd_pcm_oss snd_mixer_oss snd_pcm snd_timer
> snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore ext3
> jbd
> Jan 5 22:41:37 localhost kernel: CPU: 0
> Jan 5 22:41:37 localhost kernel: EIP: 0060:[<c013da3a>] Not tainted
> VLI
> Jan 5 22:41:37 localhost kernel: EFLAGS: 00013256 (2.6.15-mm1)
> Jan 5 22:41:37 localhost kernel: EIP is at __audit_inode+0xba/0x190
> Jan 5 22:41:37 localhost kernel: eax: 00000008 ebx: 00000000 ecx:
> dcbf02c0 edx: d9343268
> Jan 5 22:41:37 localhost kernel: esi: d922ef44 edi: d9fd3000 ebp:
> dcbf02c0 esp: d922ee88
> Jan 5 22:41:37 localhost kernel: ds: 007b es: 007b ss: 0068
> Jan 5 22:41:37 localhost kernel: Process X (pid: 2192, threadinfo=d922e000
> task=d8abcff0)
> Jan 5 22:41:37 localhost kernel: Stack: <0>00000003 00000000 dcbf02c0
> fffffffe d922ef44 d9fd3000 00000003 c017002c
> Jan 5 22:41:37 localhost kernel: <0>d9fd3000 d9343268 00000101
> 00000101 00000101 d922ef44 ffffffe9 00000003
> Jan 5 22:41:37 localhost kernel: <0>c0170096 d922e000 00000002
> d922ef44 00000006 c017011f d9fd3000 00000001
> Jan 5 22:41:38 localhost gdm[2183]: gdm_slave_xioerror_handler: Fatal X
> error - Restarting :0
> Jan 5 22:41:38 localhost kernel: Call Trace:
> Jan 5 22:41:39 localhost kernel: [<c017002c>] path_lookup+0x1ac/0x1d0
> Jan 5 22:41:40 localhost kernel: [<c0170096>]
> __path_lookup_intent_open+0x46/0xa0
> Jan 5 22:41:41 localhost kernel: [<c017011f>] path_lookup_open+0x2f/0x40
> Jan 5 22:41:41 localhost kernel: [<c0170b33>] open_namei+0x73/0x530
> Jan 5 22:41:42 localhost kernel: [<c0144cdd>] __alloc_pages+0x5d/0x390
> Jan 5 22:41:42 localhost kernel: [<c015e8b8>] filp_open+0x38/0x60
> Jan 5 22:41:42 localhost kernel: [<c015eaf0>] get_unused_fd+0xb0/0xe0
> Jan 5 22:41:42 localhost kernel: [<c015ec45>] do_sys_open+0x55/0x100
> Jan 5 22:41:42 localhost kernel: [<c01031a5>] syscall_call+0x7/0xb
> Jan 5 22:41:43 localhost kernel: Code: 42 38 89 d8 c1 e0 05 8d 04 98 c7 44
> 10 3c 00 00 00 00 89 d8 8b 54 24 24 8b 4c 24 08 c1 e0 05 8d 04 98 8d 2c 08
> 8b 82 c4 00 00 00 <8b> 40 08 89 45 48 0f b7 42 28 66 89 45 4c 8b 42 30 89 45
> 50 8b

The audit tree.

> Jan 5 22:44:05 localhost shutdown: shutting down for system reboot
> Jan 5 22:44:05 localhost init: Switching to runlevel: 6
> Jan 5 22:44:17 localhost shutdown: shutting down for system reboot
> Jan 5 22:44:26 localhost dbus: avc: 2 AV entries and 2/512 buckets used,
> longest chain length 1
> Jan 5 22:44:32 localhost xfs[1848]: terminating
> Jan 5 22:44:34 localhost shutdown: shutting down for system reboot
> Jan 5 22:44:41 localhost last message repeated 7 times
> Jan 5 22:44:58 localhost kernel: <6>[drm] Initialized drm 1.0.1 20051102
> Jan 5 22:44:59 localhost kernel: [drm] Initialized radeon 1.21.0 20051229
> on minor 0
> Jan 5 22:45:01 localhost kernel: mtrr: 0xd0000000,0x8000000 overlaps
> existing 0xd0000000,0x4000000
> Jan 5 22:45:01 localhost kernel: agpgart: Found an AGP 3.5 compliant device
> at 0000:00:00.0.
> Jan 5 22:45:01 localhost kernel: Unable to handle kernel NULL pointer
> dereference at virtual address 00000020
> Jan 5 22:45:01 localhost kernel: printing eip:
> Jan 5 22:45:01 localhost kernel: c0250b08
> Jan 5 22:45:01 localhost kernel: *pde = 1d4d1067
> Jan 5 22:45:01 localhost kernel: *pte = 00000000
> Jan 5 22:45:01 localhost kernel: Oops: 0000 [#2]
> Jan 5 22:45:01 localhost kernel: last sysfs file: /class/drm/card0/dev
> Jan 5 22:45:01 localhost kernel: Modules linked in: radeon drm autofs4
> pcmcia ipt_REJECT ipt_state ip_conntrack iptable_filter ip_tables vfat fat
> yenta_socket rsrc_nonstatic pcmcia_core uhci_hcd ehci_hcd i2c_viapro
> i2c_core snd_via82xx snd_ac97_codec snd_ac97_bus snd_seq_dummy snd_seq_oss
> snd_seq_midi_event snd_seq snd_pcm_oss snd_mixer_oss snd_pcm snd_timer
> snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore ext3
> jbd
> Jan 5 22:45:01 localhost kernel: CPU: 0
> Jan 5 22:45:01 localhost kernel: EIP: 0060:[<c0250b08>] Not tainted
> VLI
> Jan 5 22:45:01 localhost kernel: EFLAGS: 00013282 (2.6.15-mm1)
> Jan 5 22:45:01 localhost kernel: EIP is at
> agp_collect_device_status+0x18/0x130
> Jan 5 22:45:01 localhost kernel: eax: 00000058 ebx: df8cd008 ecx:
> 00003092 edx: 00000058
> Jan 5 22:45:01 localhost kernel: esi: 00000032 edi: 00000001 ebp:
> ddfb3900 esp: d978ceb4
> Jan 5 22:45:01 localhost kernel: ds: 007b es: 007b ss: 0068
> Jan 5 22:45:01 localhost kernel: Process X (pid: 2266, threadinfo=d978c000
> task=db21a960)
> Jan 5 22:45:01 localhost kernel: Stack: <0>00000000 00000084 00000004
> d978cec4 1f000a07 df8cd008 00000032 00000001
> Jan 5 22:45:01 localhost kernel: <0>ddfb3900 c0250ddd df8cd008
> 1f000201 1f000a07 d978cef0 ddfb3900 1f000a07
> Jan 5 22:45:01 localhost kernel: <0>da0c6060 e14acd9f df8cd008
> 1f000201 da0c6060 e14ace09 da0c6060 1f000201
> Jan 5 22:45:02 localhost kernel: Call Trace:
> Jan 5 22:45:02 localhost kernel: [<c0250ddd>]
> agp_generic_enable+0x8d/0x160
> Jan 5 22:45:02 localhost kernel: [<e14acd9f>] drm_agp_enable+0x3f/0x60
> [drm]
> Jan 5 22:45:04 localhost kernel: [<e14ace09>]
> drm_agp_enable_ioctl+0x49/0x60 [drm]
> Jan 5 22:45:05 localhost kernel: [<e14acdc0>]
> drm_agp_enable_ioctl+0x0/0x60 [drm]
> Jan 5 22:45:05 localhost kernel: [<e14a80ba>] drm_ioctl+0xaa/0x216 [drm]
> Jan 5 22:45:05 localhost kernel: [<c0173c41>] do_ioctl+0x81/0x90
> Jan 5 22:45:06 localhost kernel: [<c0173db0>] vfs_ioctl+0x60/0x1f0
> Jan 5 22:45:06 localhost kernel: [<c0173fc8>] sys_ioctl+0x88/0xa0
> Jan 5 22:45:06 localhost kernel: [<c01031a5>] syscall_call+0x7/0xb
> Jan 5 22:45:06 localhost kernel: Code: c4 08 89 f2 5b 5e 0f b6 c2 c3 89 f6
> 8d bc 27 00 00 00 00 83 ec 24 89 5c 24 14 89 74 24 18 89 7c 24 1c 89 6c 24
> 20 e8 98 ff ff ff <8b> 15 20 00 00 00 8b 0d 10 00 00 00 8d 6c 24 10 0f b6 c0
> 83 c0
> Jan 5 22:45:07 localhost kernel: <3>[drm:drm_release] *ERROR* Device busy:
> 1 0
> Jan 5 22:45:15 localhost shutdown: shutting down for system reboot

DRM problems.

> But because my command line is:
> Jan 5 22:39:29 localhost kernel: Kernel command line:
> /boot/linux-2.6.15-mm1a.kgz video=vesa keyboard=uk NumLock=on
> mouse=/dev/psaux COLS=160 LINES=64 LANG=en rhgb ro root=/dev/hda3
> ide0=0x1f0,0x3f6,14 ide1=0x170,0x376
> those may not count - even if it is unrelated.

I think it's legitimate - we've had another report of this.

> I have:
> Jan 5 22:39:29 localhost kernel: Linux version 2.6.15-mm1
> ([email protected]) (gcc version 4.0.1 20050727 (Red Hat
> 4.0.1-5)) #1 Thu Jan 5 21:25:17 GMT 2006
>
>
> The only other strange thing is:
> Jan 5 22:39:29 localhost kernel: PCI: Using IRQ router VIA [1106/3177] at
> 0000:00:11.0
> Jan 5 22:39:29 localhost kernel:
> Jan 5 22:39:29 localhost kernel: PCI: IRQ 0 for device 0000:00:06.0 doesn't
> match PIRQ mask - try pci=usepirqmask
> Jan 5 22:39:29 localhost kernel: PCI: Sharing IRQ 5 with 0000:00:10.1
> Jan 5 22:39:29 localhost kernel:
> Jan 5 22:39:29 localhost kernel: PCI: IRQ 0 for device 0000:00:11.1 doesn't
> match PIRQ mask - try pci=usepirqmask
> but it is not new with -mm1.

hm. That warning was added by a [email protected] four years ago. Various
PCI people cc'ed for suggestions, please.

2006-01-06 00:22:24

by Andrew Morton

[permalink] [raw]
Subject: Re: Re. 2.6.15-mm1

Alexander Gran <[email protected]> wrote:
>
> Am Donnerstag, 5. Januar 2006 23:47 schrieb Andrew Morton:
> > > Jan 5 16:22:47 t40 kernel: mtrr: 0xe0000000,0x8000000 overlaps existing
> > > 0xe0000000,0x4000000
> > > Jan 5 16:22:48 t40 last message repeated 2 times
> >
> > Is that new?
>
> Umm, no. I just thought it could be related to the X oops.

OK. I don't know how common this is, nor whether it'll cause problems.
David(s), do you know?

> > hm, it's not clear what oopsed. Can you get a cleaner copy of this?
>
> Hmm. I just rebooted to 2.6.15-mm1 runlevel one, fired up network and an sshd.
> So I could ssh back to the oops machine. Well. X is clearer but even more
> errors are in the logs now ;).
> First the X oops:
> EDAC PCI- Detected Parity Error on 0000:00:1e.0
> mtrr: 0xe0000000,0x8000000 overlaps existing 0xe0000000,0x4000000
> mtrr: 0xe0000000,0x8000000 overlaps existing 0xe0000000,0x4000000
> mtrr: 0xe0000000,0x8000000 overlaps existing 0xe0000000,0x4000000
> agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
> Unable to handle kernel NULL pointer dereference at virtual address 00000020
> printing eip:
> c028b7cf
> *pde = 372d4067
> *pte = 00000000
> Oops: 0000 [#1]
> PREEMPT
> last sysfs file: /block/hda/queue/scheduler
> Modules linked in: aes_i586 cfq_iosched ehci_hcd uhci_hcd
> CPU: 0
> EIP: 0060:[<c028b7cf>] Not tainted VLI
> EFLAGS: 00013202 (2.6.15-mm1)
> EIP is at agp_collect_device_status+0x14/0xd4
> eax: 00000058 ebx: f75c1f08 ecx: 00000000 edx: 00000058
> esi: 1f000207 edi: c19a80c0 ebp: c19af428 esp: f75c1ed0
> ds: 007b es: 007b ss: 0068
> Process Xorg (pid: 3843, threadinfo=f75c0000 task=f7890550)
> Stack: <0>00003246 1f000217 1f000207 1f000217 f75c1f08 1f000207 c19a80c0
> c19af428
> <0>c028b9e9 f75c1f08 00000002 00000000 c19720ec 00000000 1f000217
> c19af400
> <0>00000032 00000001 c028bfb5 c0297262 c19af400 c02972af 1f000207
> c029727f
> Call Trace:
> [<c028b9e9>] agp_generic_enable+0x72/0x10f
> [<c028bfb5>] agp_enable+0xa/0xb
> [<c0297262>] drm_agp_enable+0x2c/0x49
> [<c02972af>] drm_agp_enable_ioctl+0x30/0x39
> [<c029727f>] drm_agp_enable_ioctl+0x0/0x39
> [<c029311d>] drm_ioctl+0x93/0x1e4
> [<c0163664>] do_ioctl+0x64/0x6d
> [<c01637a9>] vfs_ioctl+0x50/0x1be
> [<c01ae603>] write_unix_file+0x0/0x500
> [<c016394b>] sys_ioctl+0x34/0x51
> [<c0102d0f>] sysenter_past_esp+0x54/0x75
> Code: 02 00 00 00 e8 94 66 f9 ff 89 c6 84 c0 74 de 89 f2 0f b6 c2 5b 5e c3 55
> 57 56 53 83 ec 10 89 54 24 08 89 4c 24 04 e8 bc ff ff ff <8b> 15 20 00 00 00
> 8b 1d 10 00 00 0
> 0 0f b6 c0 8d 48 04 8d 6c 24
> <3>[drm:drm_release] *ERROR* Device busy: 1 0
> EDAC PCI- Detected Parity Error on 0000:00:1e.0

OK. I've been assuming that this is a DRM bug but I note that the AGP tree
has been dinking with agp_collect_device_status(), so perhaps I had the wrong
David.

> Additionally every second or so I got these console (and kernel of cource)
> message:
> EDAC PCI- Detected Parity Error on 0000:00:1e.0

Alan, Rohit: do we expect that the EDAC fixes which you're cooking up will
address this? I think not?

> lspci:
> 0000:00:00.0 Host bridge: Intel Corporation 82855PM Processor to I/O
> Controller (rev 03)
> 0000:00:01.0 PCI bridge: Intel Corporation 82855PM Processor to AGP Controller
> (rev 03)
> 0000:00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM
> (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
> 0000:00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM
> (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)
> 0000:00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM
> (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)
> 0000:00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2
> EHCI Controller (rev 01)
> 0000:00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 81)
> 0000:00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface
> Bridge (rev 01)
> 0000:00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller
> (rev 01)
> 0000:00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
> SMBus Controller (rev 01)
> 0000:00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM
> (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
> 0000:00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
> AC'97 Modem Controller (rev 01)
> 0000:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 Lf
> [FireGL 9000] (rev 02)
> 0000:02:00.0 CardBus bridge: Texas Instruments PCI1520 PC card Cardbus
> Controller (rev 01)
> 0000:02:00.1 CardBus bridge: Texas Instruments PCI1520 PC card Cardbus
> Controller (rev 01)
> 0000:02:01.0 Ethernet controller: Intel Corporation 82540EP Gigabit Ethernet
> Controller (Mobile) (rev 03)
> 0000:02:02.0 Ethernet controller: Atheros Communications, Inc. AR5211 802.11ab
> NIC (rev 01)
>
> Full log again attached
>
> --
> Encrypted Mails welcome.
> PGP-Key at http://zodiac.dnsalias.org/misc/pgpkey.asc | Key-ID: 0x6D7DD291
>

2006-01-06 00:28:29

by Dave Airlie

[permalink] [raw]
Subject: Re: Re. 2.6.15-mm1


> > Unable to handle kernel NULL pointer dereference at virtual address 00000020
> > printing eip:
> > c028b7cf
> > *pde = 372d4067
> > *pte = 00000000
> > Oops: 0000 [#1]
> > PREEMPT
> > last sysfs file: /block/hda/queue/scheduler
> > Modules linked in: aes_i586 cfq_iosched ehci_hcd uhci_hcd
> > CPU: 0
> > EIP: 0060:[<c028b7cf>] Not tainted VLI
> > EFLAGS: 00013202 (2.6.15-mm1)
> > EIP is at agp_collect_device_status+0x14/0xd4
> > eax: 00000058 ebx: f75c1f08 ecx: 00000000 edx: 00000058
> > esi: 1f000207 edi: c19a80c0 ebp: c19af428 esp: f75c1ed0
> > ds: 007b es: 007b ss: 0068
> > Process Xorg (pid: 3843, threadinfo=f75c0000 task=f7890550)
> > Stack: <0>00003246 1f000217 1f000207 1f000217 f75c1f08 1f000207 c19a80c0
> > c19af428
> > <0>c028b9e9 f75c1f08 00000002 00000000 c19720ec 00000000 1f000217
> > c19af400
> > <0>00000032 00000001 c028bfb5 c0297262 c19af400 c02972af 1f000207
> > c029727f
> > Call Trace:
> > [<c028b9e9>] agp_generic_enable+0x72/0x10f
> > [<c028bfb5>] agp_enable+0xa/0xb
> > [<c0297262>] drm_agp_enable+0x2c/0x49
> > [<c02972af>] drm_agp_enable_ioctl+0x30/0x39
> > [<c029727f>] drm_agp_enable_ioctl+0x0/0x39
> > [<c029311d>] drm_ioctl+0x93/0x1e4
> > [<c0163664>] do_ioctl+0x64/0x6d
> > [<c01637a9>] vfs_ioctl+0x50/0x1be
> > [<c01ae603>] write_unix_file+0x0/0x500
> > [<c016394b>] sys_ioctl+0x34/0x51
> > [<c0102d0f>] sysenter_past_esp+0x54/0x75
> > Code: 02 00 00 00 e8 94 66 f9 ff 89 c6 84 c0 74 de 89 f2 0f b6 c2 5b 5e c3 55
> > 57 56 53 83 ec 10 89 54 24 08 89 4c 24 04 e8 bc ff ff ff <8b> 15 20 00 00 00
> > 8b 1d 10 00 00 0
> > 0 0f b6 c0 8d 48 04 8d 6c 24
> > <3>[drm:drm_release] *ERROR* Device busy: 1 0
> > EDAC PCI- Detected Parity Error on 0000:00:1e.0
>
> OK. I've been assuming that this is a DRM bug but I note that the AGP tree
> has been dinking with agp_collect_device_status(), so perhaps I had the wrong
> David.


Nothing in the DRM code in that area has changed enough to cuase that I
don't think... I'd guess AGP problems.. so I'll let DaveJ take a look and
prove its my fault :-)

Dave.

--
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied at skynet.ie
Linux kernel - DRI, VAX / pam_smb / ILUG

2006-01-06 00:37:20

by Linus Torvalds

[permalink] [raw]
Subject: Re: Re. 2.6.15-mm1



On Thu, 5 Jan 2006, Andrew Morton wrote:
> >
> > The only other strange thing is:
> > Jan 5 22:39:29 localhost kernel: PCI: Using IRQ router VIA [1106/3177] at
> > 0000:00:11.0
> > Jan 5 22:39:29 localhost kernel:
> > Jan 5 22:39:29 localhost kernel: PCI: IRQ 0 for device 0000:00:06.0 doesn't
> > match PIRQ mask - try pci=usepirqmask
> > Jan 5 22:39:29 localhost kernel: PCI: Sharing IRQ 5 with 0000:00:10.1
> > Jan 5 22:39:29 localhost kernel:
> > Jan 5 22:39:29 localhost kernel: PCI: IRQ 0 for device 0000:00:11.1 doesn't
> > match PIRQ mask - try pci=usepirqmask
> > but it is not new with -mm1.
>
> hm. That warning was added by a [email protected] four years ago. Various
> PCI people cc'ed for suggestions, please.

That warning is totally bogus. It shouldn't be printed out at all when
"newirq" is 0 (as in this case).

Even for a non-zero newirq, I suspect that 99% of the time,
"pci=usepirqmask" would end up causing more problems than it could ever
solve.

But this diff would seem to be the minimal fix.

The other problems _look_ like they are -mm related, not in plain 2.6.15.
Etienne, can you confirm?

Linus
---
diff --git a/arch/i386/pci/irq.c b/arch/i386/pci/irq.c
index 19e6f48..ee8e016 100644
--- a/arch/i386/pci/irq.c
+++ b/arch/i386/pci/irq.c
@@ -846,7 +846,7 @@ static int pcibios_lookup_irq(struct pci
* reported by the device if possible.
*/
newirq = dev->irq;
- if (!((1 << newirq) & mask)) {
+ if (newirq && !((1 << newirq) & mask)) {
if ( pci_probe & PCI_USE_PIRQ_MASK) newirq = 0;
else printk(KERN_WARNING "PCI: IRQ %i for device %s doesn't match PIRQ mask - try pci=usepirqmask\n", newirq, pci_name(dev));
}

2006-01-06 02:06:00

by Rohit Seth

[permalink] [raw]
Subject: RE: Re. 2.6.15-mm1

From: Andrew Morton Thursday, January 05, 2006 4:22 PM

>> 8b 1d 10 00 00 0
>> 0 0f b6 c0 8d 48 04 8d 6c 24
>> <3>[drm:drm_release] *ERROR* Device busy: 1 0
>> EDAC PCI- Detected Parity Error on 0000:00:1e.0
>
>OK. I've been assuming that this is a DRM bug but I note that the AGP
tree
>has been dinking with agp_collect_device_status(), so perhaps I had the
>wrong David.
>
>> Additionally every second or so I got these console (and kernel of
>cource)
>> message:
>> EDAC PCI- Detected Parity Error on 0000:00:1e.0
>
>Alan, Rohit: do we expect that the EDAC fixes which you're cooking up
will
>address this? I think not?
>

Nops. That one patch does not address this issue.

-rohit

2006-01-06 02:07:44

by Dave Jones

[permalink] [raw]
Subject: Re: Re. 2.6.15-mm1

On Thu, Jan 05, 2006 at 04:21:51PM -0800, Andrew Morton wrote:

> > Am Donnerstag, 5. Januar 2006 23:47 schrieb Andrew Morton:
> > > > Jan 5 16:22:47 t40 kernel: mtrr: 0xe0000000,0x8000000 overlaps existing
> > > > 0xe0000000,0x4000000
> > > > Jan 5 16:22:48 t40 last message repeated 2 times
> > >
> > > Is that new?
> >
> > Umm, no. I just thought it could be related to the X oops.
>
> OK. I don't know how common this is, nor whether it'll cause problems.
> David(s), do you know?

at worse, a video performance hit.

> > EIP is at agp_collect_device_status+0x14/0xd4
> OK. I've been assuming that this is a DRM bug but I note that the AGP tree
> has been dinking with agp_collect_device_status(), so perhaps I had the wrong
> David.

I'm a moron. I'll fix it up.
I only tested the 'have no agp' case which this changed, and didn't test
the commoncase 'have agp'. Doh.

Dave

2006-01-06 05:36:48

by Brown, Len

[permalink] [raw]
Subject: RE: Re. 2.6.15-mm1


>> Jan 5 16:22:38 t40 kernel: pnp: PnP ACPI init
>> Jan 5 16:22:38 t40 kernel: pnp: PnPACPI: unknown resource type 7
>> Jan 5 16:22:38 t40 kernel: pnp: PnPACPI: unknown resource type 7
>> Jan 5 16:22:39 t40 last message repeated 10 times
>> Jan 5 16:22:39 t40 kernel: pnp: PnP ACPI: found 0 devices
>
>pnpacpi is unhappy.

pnpacpi is fixed:
http://lkml.org/lkml/2006/1/5/287

>> Jan 5 16:22:43 t40 kernel: **** SET: Misaligned resource pointer: f7db5502
>
>acpi is unhappy.

Yes, that one is ours. We'll track it here:

http://bugme.osdl.org/show_bug.cgi?id=5841

thanks,
-Len

2006-01-06 09:30:24

by Hans Reiser

[permalink] [raw]
Subject: Re: Re. 2.6.15-mm1

Andrew Morton wrote:

>
>
>
>
>>When X startet, the laptops crashed:
>>Jan 5 16:22:43 t40 kernel: <4>reiser4[syslogd(2729)]: disable_write_barrier
>>(fs/reiser4/wander.c:233)[zam-1055]:
>>Jan 5 16:22:43 t40 kernel: WARNING: disabling write barrier
>>
>>
>
>Vladimir, is that expected?
>
>
Vladimir is in France skiing, as this is Russian Christmas right now.

Zam says that this merely means that the underlying device does not
support write barriers, and the code uses synchronous writes for commits
instead of write barriers when this happens. It should not affect
correctness. He will comment more this evening (russian time) when he
gets home. He suggests that he should change it from warning to
notice. He also suggests that this code is new code, so it is possible
it has bugs.....

>
>
>>Jan 5 16:22:43 t40 kernel:
>>Jan 5 16:22:47 t40 kernel: mtrr: 0xe0000000,0x8000000 overlaps existing
>>0xe0000000,0x4000000
>>Jan 5 16:22:48 t40 last message repeated 2 times
>>
>>
>
>Is that new?
>
>
>
>>Jan 5 16:22:48 t40 kernel: agpgart: Found an AGP 2.0 compliant device at
>>0000:00:00.0.
>>Jan 5 16:22:48 t40 kernel: c028b7cf
>>Jan 5 16:22:48 t40 kernel: Modules linked in: irtty_sir sir_dev cfq_iosched
>>ehci_hcd uhci_hcd
>>Jan 5 16:22:48 t40 kernel: EIP: 0060:[<c028b7cf>] Not tainted VLI
>>Jan 5 16:22:48 t40 kernel: EFLAGS: 00013202 (2.6.15-mm1)
>>Jan 5 16:22:48 t40 kernel: <0>c028b9e9 f762ff08 00000002 00000000
>>c19720ec 00000000 1f000217 c1a79400
>>Jan 5 16:22:48 t40 kernel: <0>00000032 00000001 c028bfb5 c0297262
>>c1a79400 c02972af 1f000207 c029727f
>>
>>
>
>hm, it's not clear what oopsed. Can you get a cleaner copy of this?
>
>
>
>>Jan 5 16:22:48 t40 kernel: <3>[drm:drm_release] *ERROR* Device busy: 1 0
>>
>>
>
>drm is unhappy
>
>
>
>
>

2006-01-06 10:04:09

by Etienne Lorrain

[permalink] [raw]
Subject: Re: Re. 2.6.15-mm1

--- Linus Torvalds <[email protected]> wrote?:
> The other problems _look_ like they are -mm related, not in
> plain 2.6.15.
> Etienne, can you confirm?

Plain linux-2.6.15 is perfectly working for me, excluding the
small "pci=usepirqmask" warning, even when I use the Gujin
bootloader.
I still sometimes have strange early reboot problem when
the kernel is not loaded and run at 1 Mbyte but at a higher
address - but that can be considered as still "unsupported
configuration". It may even be my fault...

Etienne.





___________________________________________________________________________
Nouveau : t?l?phonez moins cher avec Yahoo! Messenger. Appelez le monde entier ? partir de 0,012 ?/minute !
T?l?chargez sur http://fr.messenger.yahoo.com

2006-01-06 18:30:04

by Alexander Zarochentsev

[permalink] [raw]
Subject: Re: Re. 2.6.15-mm1

On Friday 06 January 2006 01:47, Andrew Morton wrote:
> Alexander Gran <[email protected]> wrote:
> > Hi,
> >
> > just tried 2.6.15-mm1 on my thinkpad. Various aspects that didn't work /
> > look good:
>
> Thanks. A few people have some work to do before they are ready to merge
> to 2.6.16.
>
> > Jan 5 16:22:38 t40 kernel: pnp: PnP ACPI init
> > Jan 5 16:22:38 t40 kernel: pnp: PnPACPI: unknown resource type 7
> > Jan 5 16:22:38 t40 kernel: pnp: PnPACPI: unknown resource type 7
> > Jan 5 16:22:39 t40 last message repeated 10 times
> > Jan 5 16:22:39 t40 kernel: pnp: PnP ACPI: found 0 devices
>
> pnpacpi is unhappy.
>
> > All over the place logs like this:
> > Jan 5 16:22:43 t40 kernel: **** SET: Misaligned resource pointer:
> > f7db5502 Type 07 Len 0
> > Unknown to me so far..
>
> acpi is unhappy.
>
> > When X startet, the laptops crashed:
> > Jan 5 16:22:43 t40 kernel: <4>reiser4[syslogd(2729)]:
> > disable_write_barrier (fs/reiser4/wander.c:233)[zam-1055]:
> > Jan 5 16:22:43 t40 kernel: WARNING: disabling write barrier

It means submit_bio(WRITE_BARRIER, bio) fails and reiser4 falls back to
synchronous write in the transaction commit code.

Ext3, reiserfs do similar checks in their code and all issue warnings if those
checks fail. But only ext3, it seems, has write barrier support disabled by
default.

> Vladimir, is that expected?
>
> > Jan 5 16:22:43 t40 kernel:
> > Jan 5 16:22:47 t40 kernel: mtrr: 0xe0000000,0x8000000 overlaps existing
> > 0xe0000000,0x4000000
> > Jan 5 16:22:48 t40 last message repeated 2 times
>
> Is that new?
>
> > Jan 5 16:22:48 t40 kernel: agpgart: Found an AGP 2.0 compliant device at
> > 0000:00:00.0.
> > Jan 5 16:22:48 t40 kernel: c028b7cf
> > Jan 5 16:22:48 t40 kernel: Modules linked in: irtty_sir sir_dev
> > cfq_iosched ehci_hcd uhci_hcd
> > Jan 5 16:22:48 t40 kernel: EIP: 0060:[<c028b7cf>] Not tainted VLI
> > Jan 5 16:22:48 t40 kernel: EFLAGS: 00013202 (2.6.15-mm1)
> > Jan 5 16:22:48 t40 kernel: <0>c028b9e9 f762ff08 00000002 00000000
> > c19720ec 00000000 1f000217 c1a79400
> > Jan 5 16:22:48 t40 kernel: <0>00000032 00000001 c028bfb5 c0297262
> > c1a79400 c02972af 1f000207 c029727f
>
> hm, it's not clear what oopsed. Can you get a cleaner copy of this?
>
> > Jan 5 16:22:48 t40 kernel: <3>[drm:drm_release] *ERROR* Device busy: 1
> > 0
>
> drm is unhappy

--
Alex.