Re: i915 trouble -- IRQ being disabled
Hi,
On Fri, Feb 16, 2007 at 10:18:45AM +0100, Michel Dänzer wrote:
On Thu, 2007-02-15 at 14:22 -0500, Dominik Brodowski wrote:
This issue (IRQ being disabled) is still present in 2.6.20 and
2.6.20-git-as-of-yesterday. It breaks suspend-to-{}, it breaks switching
from console to tty, and sometimes it locks the system when trying to
shutdown. Any ideas?
Does this patch happen to make any difference?
It didn't apply correctly to latest git (or latest git +
i915-disable-vblank-interrupts.diff), so I manually replaced all relevant
instances of _READ16 or _WRITE16 with _READ and _WRITE. However, it didn't
make any difference..
Thanks,
Dominik
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: i915 trouble -- IRQ being disabled
Hi,
This issue (IRQ being disabled) is still present in 2.6.20 and
2.6.20-git-as-of-yesterday. It breaks suspend-to-{}, it breaks switching
from console to tty, and sometimes it locks the system when trying to
shutdown. Any ideas?
Thanks,
Dominik
On Tue, Jan 30, 2007 at 12:59:04AM -0500, Dominik Brodowski wrote:
Hi,
On Mon, Jan 29, 2007 at 01:00:39PM +0100, Michel Dänzer wrote:
On Sun, 2007-01-28 at 22:14 -0500, Dominik Brodowski wrote:
[...] I was able to git bisect it down to the drm patches which went in
after 2.6.19 and before 2.6.19-rc1 got released.
Can you bisect it down to a single commit? If that's not possible with
the kernel tree, you can try the drm git tree from
git://git.freedesktop.org/git/mesa/drm .
The culprit is one of these (kernel git tree):
2228ed67223f3f22ea09df8854e6a31ea06d5619 - drm: i915 updates
a0b136bb696cfa744a79c4dd0c8f9f30fe3f - drm: i915: fix up irqflags arg
21fa60ed4eab5b3b28d05930bb086615ecc191b1 - drm: i915: Only return EBUSY...
2dbb232c4d6b6c89fc367f7566c7c87dd3b56cd7 - drm: i915: Fix 'sequence has...
376642cf2eb0f32d8502b0a2c4efd96a3f13a8b8 - drm: i915: Add SAREA fileds...
5b51694aff705c465ef5941a99073036f3e444d9 - drm: Make handling of...
2228ed72... has the issue, while
541f29aad766b6c7b911a7d900d952744369bf53 - drm: DRM_I915_VBLANK_SWAP
doesn't have it -- and all kernels in between crash during X startup, and
the last message in the X logs is
(II) I810(0): X context handle = 0x1
instead of:
(II) I810(0): X context handle = 0x1
(II) I810(0): [drm] installed DRM signal handler
(II) I810(0): [DRI] installation complete
(II) I810(0): direct rendering: Enabled
(II) I810(0): RandR enabled, ignore the following RandR disabled message.
(II) I810(0): Rotating to 0 degrees
(--) RandR disabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
drmOpenDevice: node name is /dev/dri/card0
As a sidenote, the last working kernel
541f29aad766b6c7b911a7d900d952744369bf53 - drm: DRM_I915_VBLANK_SWAP
returned this in dmesg when switching from console to terminal:
[ 108.905000] INFO: trying to register non-static key.
[ 108.905000] the code is fine but needs lockdep annotation.
[ 108.905000] turning off the locking correctness validator.
[ 108.905000] [c01034ee] dump_trace+0x64/0x1d0
[ 108.905000] [c0103674] show_trace_log_lvl+0x1a/0x2f
[ 108.905000] [c0103d29] show_trace+0x12/0x14
[ 108.905000] [c0103dcc] dump_stack+0x19/0x1b
[ 108.905000] [c012df5f] __lock_acquire+0x128/0x995
[ 108.905000] [c012eae2] lock_acquire+0x6e/0x8b
[ 108.905000] [c039ced3] _spin_lock_irqsave+0x3e/0x4e
[ 108.905000] [c0268bbf] i915_vblank_tasklet+0x3f/0x314
[ 108.905000] [c0263482] drm_unlock+0x8e/0x115
[ 108.905000] [c0261ac0] drm_ioctl+0x15b/0x19f
[ 108.905000] [c0166780] do_ioctl+0x50/0x67
[ 108.905000] [c01669e3] vfs_ioctl+0x24c/0x25f
[ 108.905000] [c0166a27] sys_ioctl+0x31/0x4a
[ 108.905000] [c0102e4d] sysenter_past_esp+0x56/0x8d
[ 108.905000] [b7f1d410] 0xb7f1d410
[ 108.905000] ===
Any ideas? Any debugging you want me to do?
echo 1 /sys/module/drm/parameters/debug
before switching to console might provide something interesting in the
kernel output.
this is with 2.6.19-rc6-latest:
lots of similar messages
[ 1320.522000] [drm:i915_driver_irq_handler] i915_driver_irq_handler
flag=
[ 1320.527000] [drm:i915_driver_irq_handler] i915_driver_irq_handler
flag=0080
[ 1320.53] [drm:i915_driver_irq_handler] i915_driver_irq_handler
flag=
[ 1320.538000] [drm:i915_driver_irq_handler] i915_driver_irq_handler
flag=0020
[ 1320.542000] [drm:i915_driver_irq_handler] i915_driver_irq_handler
flag=0080
[ 1320.546000] [drm:i915_driver_irq_handler] i915_driver_irq_handler
flag=
[ 1320.554000] [drm:i915_driver_irq_handler] i915_driver_irq_handler
flag=0020
[ 1320.557000] [drm:i915_driver_irq_handler] i915_driver_irq_handler
flag=0080
[ 1320.562000] [drm:i915_driver_irq_handler] i915_driver_irq_handler
flag=
[ 1320.57] [drm:i915_driver_irq_handler] i915_driver_irq_handler
flag=0020
[ 1320.571000] [drm:drm_ioctl] pid=6459, cmd=0x4004644d, nr=0x4d, dev 0xe200,
auth=1
[ 1320.571000] [drm:drm_ioctl] pid=6459, cmd=0x40086414, nr=0x14, dev 0xe200,
auth=1
[ 1320.571000
Re: i915 trouble -- IRQ being disabled
Hi, On Mon, Jan 29, 2007 at 01:00:39PM +0100, Michel Dänzer wrote: On Sun, 2007-01-28 at 22:14 -0500, Dominik Brodowski wrote: [...] I was able to git bisect it down to the drm patches which went in after 2.6.19 and before 2.6.19-rc1 got released. Can you bisect it down to a single commit? If that's not possible with the kernel tree, you can try the drm git tree from git://git.freedesktop.org/git/mesa/drm . The culprit is one of these (kernel git tree): 2228ed67223f3f22ea09df8854e6a31ea06d5619 - drm: i915 updates a0b136bb696cfa744a79c4dd0c8f9f30fe3f - drm: i915: fix up irqflags arg 21fa60ed4eab5b3b28d05930bb086615ecc191b1 - drm: i915: Only return EBUSY... 2dbb232c4d6b6c89fc367f7566c7c87dd3b56cd7 - drm: i915: Fix 'sequence has... 376642cf2eb0f32d8502b0a2c4efd96a3f13a8b8 - drm: i915: Add SAREA fileds... 5b51694aff705c465ef5941a99073036f3e444d9 - drm: Make handling of... 2228ed72... has the issue, while 541f29aad766b6c7b911a7d900d952744369bf53 - drm: DRM_I915_VBLANK_SWAP doesn't have it -- and all kernels in between crash during X startup, and the last message in the X logs is (II) I810(0): X context handle = 0x1 instead of: (II) I810(0): X context handle = 0x1 (II) I810(0): [drm] installed DRM signal handler (II) I810(0): [DRI] installation complete (II) I810(0): direct rendering: Enabled (II) I810(0): RandR enabled, ignore the following RandR disabled message. (II) I810(0): Rotating to 0 degrees (--) RandR disabled (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension XC-APPGROUP (II) Initializing built-in extension SECURITY (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFIXES (II) Initializing built-in extension XFree86-Bigfont (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR (II) Initializing built-in extension COMPOSITE (II) Initializing built-in extension DAMAGE (II) Initializing built-in extension XEVIE drmOpenDevice: node name is /dev/dri/card0 As a sidenote, the last working kernel 541f29aad766b6c7b911a7d900d952744369bf53 - drm: DRM_I915_VBLANK_SWAP returned this in dmesg when switching from console to terminal: [ 108.905000] INFO: trying to register non-static key. [ 108.905000] the code is fine but needs lockdep annotation. [ 108.905000] turning off the locking correctness validator. [ 108.905000] [c01034ee] dump_trace+0x64/0x1d0 [ 108.905000] [c0103674] show_trace_log_lvl+0x1a/0x2f [ 108.905000] [c0103d29] show_trace+0x12/0x14 [ 108.905000] [c0103dcc] dump_stack+0x19/0x1b [ 108.905000] [c012df5f] __lock_acquire+0x128/0x995 [ 108.905000] [c012eae2] lock_acquire+0x6e/0x8b [ 108.905000] [c039ced3] _spin_lock_irqsave+0x3e/0x4e [ 108.905000] [c0268bbf] i915_vblank_tasklet+0x3f/0x314 [ 108.905000] [c0263482] drm_unlock+0x8e/0x115 [ 108.905000] [c0261ac0] drm_ioctl+0x15b/0x19f [ 108.905000] [c0166780] do_ioctl+0x50/0x67 [ 108.905000] [c01669e3] vfs_ioctl+0x24c/0x25f [ 108.905000] [c0166a27] sys_ioctl+0x31/0x4a [ 108.905000] [c0102e4d] sysenter_past_esp+0x56/0x8d [ 108.905000] [b7f1d410] 0xb7f1d410 [ 108.905000] === Any ideas? Any debugging you want me to do? echo 1 /sys/module/drm/parameters/debug before switching to console might provide something interesting in the kernel output. this is with 2.6.19-rc6-latest: lots of similar messages [ 1320.522000] [drm:i915_driver_irq_handler] i915_driver_irq_handler flag= [ 1320.527000] [drm:i915_driver_irq_handler] i915_driver_irq_handler flag=0080 [ 1320.53] [drm:i915_driver_irq_handler] i915_driver_irq_handler flag= [ 1320.538000] [drm:i915_driver_irq_handler] i915_driver_irq_handler flag=0020 [ 1320.542000] [drm:i915_driver_irq_handler] i915_driver_irq_handler flag=0080 [ 1320.546000] [drm:i915_driver_irq_handler] i915_driver_irq_handler flag= [ 1320.554000] [drm:i915_driver_irq_handler] i915_driver_irq_handler flag=0020 [ 1320.557000] [drm:i915_driver_irq_handler] i915_driver_irq_handler flag=0080 [ 1320.562000] [drm:i915_driver_irq_handler] i915_driver_irq_handler flag= [ 1320.57] [drm:i915_driver_irq_handler] i915_driver_irq_handler flag=0020 [ 1320.571000] [drm:drm_ioctl] pid=6459, cmd=0x4004644d, nr=0x4d, dev 0xe200, auth=1 [ 1320.571000] [drm:drm_ioctl] pid=6459, cmd=0x40086414, nr=0x14, dev 0xe200, auth=1 [ 1320.571000] [drm:drm_irq_uninstall] drm_irq_uninstall: irq=10 [ 1322.474000] irq 10: nobody cared (try booting with the irqpoll option) [ 1322.474000] [c01034d9] show_trace_log_lvl+0x1a/0x2f [ 1322.474000] [c0103b81] show_trace+0x12/0x14 [ 1322.474000] [c0103c33] dump_stack+0x16/0x18 [ 1322.474000] [c013fc74] __report_bad_irq+0x39/0x81 [ 1322.474000] [c013fe55] note_interrupt+0x199/0x1d4 [ 1322.474000] [c01406dd] handle_level_irq+0xa3
Re: i915 trouble -- IRQ being disabled
Hi, On Tue, Jan 30, 2007 at 12:17:16PM +0100, Michel Dänzer wrote: On Tue, 2007-01-30 at 00:59 -0500, Dominik Brodowski wrote: On Mon, Jan 29, 2007 at 01:00:39PM +0100, Michel Dänzer wrote: On Sun, 2007-01-28 at 22:14 -0500, Dominik Brodowski wrote: [...] I was able to git bisect it down to the drm patches which went in after 2.6.19 and before 2.6.19-rc1 got released. Can you bisect it down to a single commit? If that's not possible with the kernel tree, you can try the drm git tree from git://git.freedesktop.org/git/mesa/drm . The culprit is one of these (kernel git tree): 2228ed67223f3f22ea09df8854e6a31ea06d5619 - drm: i915 updates a0b136bb696cfa744a79c4dd0c8f9f30fe3f - drm: i915: fix up irqflags arg 21fa60ed4eab5b3b28d05930bb086615ecc191b1 - drm: i915: Only return EBUSY... 2dbb232c4d6b6c89fc367f7566c7c87dd3b56cd7 - drm: i915: Fix 'sequence has... 376642cf2eb0f32d8502b0a2c4efd96a3f13a8b8 - drm: i915: Add SAREA fileds... 5b51694aff705c465ef5941a99073036f3e444d9 - drm: Make handling of... 2228ed72... has the issue, while 541f29aad766b6c7b911a7d900d952744369bf53 - drm: DRM_I915_VBLANK_SWAP doesn't have it [...] Any ideas? Any debugging you want me to do? echo 1 /sys/module/drm/parameters/debug before switching to console might provide something interesting in the kernel output. this is with 2.6.19-rc6-latest: [ 1320.571000] [drm:drm_irq_uninstall] drm_irq_uninstall: irq=10 [ 1322.474000] irq 10: nobody cared (try booting with the irqpoll option) Hmm, so it looks like the driver tries to disable interrupts on the card and removes the handler, then the card still generates an interrupt, which is rejected by the remaining handlers. My best guess is that it's a vertical blank interrupt, which wasn't enabled before commit 5b51694aff705c465ef5941a99073036f3e444d9 because dev_priv-vblank_pipe didn't get initialized. Would this patch happen to make a difference? No, that doesn't help, unfortunately. Thanks for looking into this issue, Dominik - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
i915 trouble -- IRQ being disabled
Hi, When I switch from the X Window System Version 7.1.1 console to a terminal, IRQ 10: 10: 20XT-PIC-XTuhci_hcd:usb1, ehci_hcd:usb4, yenta, yenta, [EMAIL PROTECTED]::00:02.0 gets disabled (irq 10: nobody cared). The hardware is 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) and I was able to git bisect it down to the drm patches which went in after 2.6.19 and before 2.6.19-rc1 got released. While I have some other issues related to that IRQ line (usb autosuspend can causes the IRQ 10 becoming disabled, too), this issue only appeared once the drm/i915 patches got merged, so I logically derive that this is a separate issue. Any ideas? Any debugging you want me to do? Dominik - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: IRQ disabled (i915?) when switchig between gnome themes (gnome-theme-manager)
Hi, On Tue, Feb 14, 2006 at 05:55:16PM +1100, Dave Airlie wrote: Can you try the patch at http://www.skynet.ie/~airlied/patches/dri/i915_irq_stop.diff I think it might fix it, it cleans up any pending interrupts on disable.. Thanks, this patch solves the issue. Dominik --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
IRQ disabled (i915?) when switchig between gnome themes (gnome-theme-manager)
Hi, Something strange goes on when I try to switch more than two times between gnome themes using gnome-theme-manager: the X server is killed -- that also happens with 2.6.15, and that is surely an userspace bug, and the login manager restarts. With current git and also with 2.6.16-rc1-mm3 and -mm4 sometimes the screen, and _only_ the screen is frozen, and all the time IRQ 10 is disabled: 10: 34430 XT-PIC Intel 82801DB-ICH4, Intel 82801DB-ICH4 Modem, yenta, yenta, ehci_hcd:usb1, uhci_hcd:usb2, [EMAIL PROTECTED]::00:02.0 What's a bit strange about this is that the IRQ handler for i915 seems to be gone right at the moment the nobody cared check triggers -- maybe the IRQ handler is unregistered (a bit) too early? CONFIG_AGP_INTEL=y CONFIG_DRM_I915=y 00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02) 00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02) 00:00.3 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02) 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) 00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) Thanks, Dominik Linux version 2.6.16-rc1 ([EMAIL PROTECTED]) (gcc-Version 3.4.4 (Gentoo Hardened 3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8)) #2 PREEMPT Fri Jan 27 22:31:53 CET 2006 BIOS-provided physical RAM map: BIOS-e820: - 0009f800 (usable) BIOS-e820: 0009f800 - 000a (reserved) BIOS-e820: 000ce000 - 000d (reserved) BIOS-e820: 000d8000 - 000e (reserved) BIOS-e820: 000e4000 - 0010 (reserved) BIOS-e820: 0010 - 2f6e (usable) BIOS-e820: 2f6e - 2f6ec000 (ACPI data) BIOS-e820: 2f6ec000 - 2f70 (ACPI NVS) BIOS-e820: 2f70 - 3000 (reserved) BIOS-e820: fec1 - fec2 (reserved) BIOS-e820: ff80 - ffc0 (reserved) BIOS-e820: fc00 - 0001 (reserved) 758MB LOWMEM available. On node 0 totalpages: 194272 DMA zone: 4096 pages, LIFO batch:0 DMA32 zone: 0 pages, LIFO batch:0 Normal zone: 190176 pages, LIFO batch:31 HighMem zone: 0 pages, LIFO batch:0 DMI present. ACPI: RSDP (v000 PTLTD ) @ 0x000f7e80 ACPI: RSDT (v001 PTLTD Montara 0x0604 LTP 0x) @ 0x2f6e7bc3 ACPI: FADT (v001 INTEL MONTARA 0x0604 PTL 0x0050) @ 0x2f6ebed2 ACPI: BOOT (v001 PTLTD $SBFTBL$ 0x0604 LTP 0x0001) @ 0x2f6ebfd8 ACPI: SSDT (v001 INTEL CPU0CST 0x0001 INTL 0x20020725) @ 0x2f6e800c ACPI: SSDT (v001 INTEL EISTRef 0x2000 INTL 0x02012044) @ 0x2f6e7bf7 ACPI: DSDT (v001 INTEL MONTARAG 0x0604 MSFT 0x010e) @ 0x ACPI: PM-Timer IO Port: 0x1008 Allocating PCI resources starting at 4000 (gap: 3000:cec1) Built 1 zonelists Kernel command line: root=/dev/hda5 acpi_sleep=s3_mode psmouse.proto=imps resume=/dev/hda8 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c0444000 soft=c0443000 PID hash table entries: 4096 (order: 12, 65536 bytes) Detected 1396.066 MHz processor. Using pmtmr for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 766088k/777088k available (2297k kernel code, 10512k reserved, 870k data, 144k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 2793.78 BogoMIPS (lpj=1396892) Mount-cache hash table entries: 512 CPU: After generic identify, caps: a7e9f9bf 0180 CPU: After vendor identify, caps: a7e9f9bf 0180 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 1024K CPU: After all inits, caps: a7e9f9bf 0040 0180 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. mtrr: v2.0 (20020519) CPU: Intel(R) Pentium(R) M processor 1400MHz stepping 05 Checking 'hlt' instruction... OK. tbget-0284: *** Info: Table [DSDT] replaced by host OS tbxface-0109 [02] load_tables : ACPI Tables successfully acquired Parsing all Control Methods:.. Table [DSDT](id 0007) - 520 Objects with 56 Devices 154 Methods 20 Regions Parsing all Control Methods:. Table [SSDT](id 0004) - 1 Objects with 0 Devices 1
