Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#16926 - [kernel26] KMS with Intel Graphic fails (i915)

Attached to Project: Arch Linux
Opened by Andrew S. Grigorev (eigrad) - Friday, 30 October 2009, 18:15 GMT
Last edited by Thomas Bächler (brain0) - Friday, 13 November 2009, 08:09 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan de Groot (JGC)
Thomas Bächler (brain0)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

For about a month I am successfully using KMS with Intel GMA 4500M. But
yesterday, after the upgrade, I got kernel panic when running Xorg. After
rebuilding intel-dri, mesa and the other from aur, a kernel
panic ceased to appear. Now I just have

2009 Oct 31 03:38:50 bbook Oops: 0000 [#1] PREEMPT SMP
2009 Oct 31 03:38:50 bbook last sysfs file:
/sys/devices/pci0000:00/0000:00:02.0/drm/card0/dev
2009 Oct 31 03:38:50 bbook Process modprobe (pid: 10351, ti=f5dc6000
task=f5e7b9c0 task.ti=f5dc6000)
2009 Oct 31 03:38:50 bbook Stack:
2009 Oct 31 03:38:50 bbook Call Trace:
2009 Oct 31 03:38:50 bbook Code: 8b 74 24 14 8d b4 26 00 00 00 00 83 bc 88 88
01 00 00 00 74 16 83 c1 01 83 f9 10 75 ee b8 ea ff ff ff eb 26 8d b4 26 00 00
00 00 <8b> 52 08 83 f9 10 89 9c c8 c8 01 00 00 89 b4 c8 cc 01 00 00 89
2009 Oct 31 03:38:50 bbook EIP: [<f82d6840>]
drm_connector_attach_property+0x40/0x80 [drm] SS:ESP 0068:f5dc7d54
2009 Oct 31 03:38:50 bbook CR2: 0000000000000008

output to console, and "(EE) intel(0): No kernel modesetting driver detected."
in Xorg.0.log.

Module i915 kernel does not load automatically at boot, and `modprobe i915`
gives
[<f83e0384>] ? intel_lvds_init+0x154/0x4a0 [i915]
[<f83db790>] ? intel_modeset_init+0x5a0/0xe80 [i915]
[<f83c7e81>] ? i915_driver_load+0xde1/0xfb0 [i915]
[<f82d1c0d>] ? drm_get_dev+0x2ad/0x4e0 [drm]
[<c1151c8c>] ? sysfs_do_create_link+0xbc/0x160
[<c11b10aa>] ? local_pci_probe+0x1a/0x40
[<c11b2361>] ? pci_device_probe+0x81/0xb0
[<c12343a9>] ? driver_probe_device+0x89/0x170
[<c1234521>] ? __driver_attach+0x91/0xa0
[<c1234490>] ? __driver_attach+0x0/0xa0
[<c1233a22>] ? bus_for_each_dev+0x62/0xa0
[<c12341d2>] ? driver_attach+0x22/0x40
[<c1234490>] ? __driver_attach+0x0/0xa0
[<c12331ae>] ? bus_add_driver+0xce/0x2b0
[<c11b2240>] ? pci_device_remove+0x0/0x60
[<c123489f>] ? driver_register+0x6f/0x130
[<c10687a6>] ? notifier_call_chain+0x46/0x80
[<f801f000>] ? i915_init+0x0/0x63 [i915]
[<c11b27f9>] ? __pci_register_driver+0x49/0xd0
[<c100115b>] ? do_one_initcall+0x3b/0x1b0
[<c107e645>] ? sys_init_module+0xe5/0x230
[<c1003cb3>] ? sysenter_do_call+0x12/0x28

at one time and nothing in other (just hang, no output no visible problems).

/var/lib/pacman.log of update that caused it:

[2009-10-30 02:15] synchronizing package lists
[2009-10-30 02:17] starting full system upgrade
[2009-10-30 02:50] upgraded abiword (2.8.0-2 -> 2.6.8-2)
[2009-10-30 02:50] upgraded kernel-headers (2.6.30.5-1 -> 2.6.31.4-1)
[2009-10-30 02:50] Generating locales...
[2009-10-30 02:50] en_US.UTF-8... done
[2009-10-30 02:50] en_US.ISO-8859-1... done
[2009-10-30 02:50] ru_RU.KOI8-R... done
[2009-10-30 02:50] ru_RU.UTF-8... done
[2009-10-30 02:50] ru_RU.ISO-8859-5... done
[2009-10-30 02:50] Generation complete.
[2009-10-30 02:50] upgraded glibc (2.10.1-4 -> 2.10.1-5)
[2009-10-30 02:50] upgraded attr (2.4.43-1 -> 2.4.44-1)
[2009-10-30 02:50] upgraded acl (2.2.47-2 -> 2.2.48-1)
[2009-10-30 02:50] upgraded binutils (2.19.1-5 -> 2.20-1)
[2009-10-30 02:50] upgraded gcc (4.4.1-1 -> 4.4.2-2)
[2009-10-30 02:50] upgraded gcc-libs (4.4.1-1 -> 4.4.2-2)
[2009-10-30 02:50] upgraded git (1.6.5.1-1 -> 1.6.5.2-1)
[2009-10-30 02:50] upgraded module-init-tools (3.10-2 -> 3.11.1-1)
[2009-10-30 02:50] >>> Updating module dependencies. Please wait ...
[2009-10-30 02:50] >>> MKINITCPIO SETUP
[2009-10-30 02:50] >>> ----------------
[2009-10-30 02:50] >>> If you use LVM2, Encrypted root or software RAID,
[2009-10-30 02:50] >>> Ensure you enable support in /etc/mkinitcpio.conf .
[2009-10-30 02:50] >>> More information about mkinitcpio setup can be found
here:
[2009-10-30 02:50] >>> http://wiki.archlinux.org/index.php/Mkinitcpio
[2009-10-30 02:50]
[2009-10-30 02:50] >>> Generating initial ramdisk, using mkinitcpio. Please
wait...
[2009-10-30 02:50] ==> Building image "default"
[2009-10-30 02:50] ==> Running command: /sbin/mkinitcpio -k 2.6.31-ARCH -c
/etc/mkinitcpio.conf -g /boot/kernel26.img
[2009-10-30 02:50] :: Begin build
[2009-10-30 02:50] :: Parsing hook [base]
[2009-10-30 02:50] :: Parsing hook [udev]
[2009-10-30 02:50] :: Parsing hook [autodetect]
[2009-10-30 02:51] :: Parsing hook [pata]
[2009-10-30 02:51] :: Parsing hook [scsi]
[2009-10-30 02:51] :: Parsing hook [sata]
[2009-10-30 02:51] :: Parsing hook [filesystems]
[2009-10-30 02:51] :: Generating module dependencies
[2009-10-30 02:51] :: Generating image '/boot/kernel26.img'...SUCCESS
[2009-10-30 02:51] ==> SUCCESS
[2009-10-30 02:51] ==> Building image "fallback"
[2009-10-30 02:51] ==> Running command: /sbin/mkinitcpio -k 2.6.31-ARCH -c
/etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
[2009-10-30 02:51] :: Begin build
[2009-10-30 02:51] :: Parsing hook [base]
[2009-10-30 02:51] :: Parsing hook [udev]
[2009-10-30 02:51] :: Parsing hook [pata]
[2009-10-30 02:51] :: Parsing hook [scsi]
[2009-10-30 02:51] :: Parsing hook [sata]
[2009-10-30 02:51] :: Parsing hook [filesystems]
[2009-10-30 02:52] :: Generating module dependencies
[2009-10-30 02:52] :: Generating image '/boot/kernel26-fallback.img'...SUCCESS
[2009-10-30 02:52] ==> SUCCESS
[2009-10-30 02:52] upgraded kernel26 (2.6.31.4-1 -> 2.6.31.5-1)
[2009-10-30 02:52] upgraded libevent (1.4.11-1 -> 1.4.12-1)
[2009-10-30 02:52] upgraded libfetch (2.25-1 -> 2.26-1)
[2009-10-30 02:52] upgraded mlocate (0.22.2-1 -> 0.22.2-2)
[2009-10-30 02:52] upgraded ntfs-3g (2009.4.4-1 -> 2009.4.4-2)
[2009-10-30 02:52] upgraded ode (0.11-1 -> 0.11.1-1)
[2009-10-30 02:52] upgraded popt (1.14-1 -> 1.15-1)
[2009-10-30 02:52] upgraded python (2.6.3-2 -> 2.6.4-1)
[2009-10-30 02:52] upgraded syslinux (3.82-1 -> 3.83-1)
[2009-10-30 02:53] Updating font cache... done.
[2009-10-30 02:53] installed ttf-freefont (20090104-2)
[2009-10-30 02:53] upgraded vlc (1.0.2-3 -> 1.0.2-4)
[2009-10-30 02:53] upgraded xmoto (0.5.2-1 -> 0.5.2-2)

Posted to http://bugzilla.kernel.org/show_bug.cgi?id=13776#c16
This task depends upon

Closed by  Thomas Bächler (brain0)
Friday, 13 November 2009, 08:09 GMT
Reason for closing:  Not a bug
Comment by Laszlo Papp (djszapi) - Saturday, 07 November 2009, 05:54 GMT
What were the error messages in syslog before trying AUR unsupported packages ? What caused the kernel panic ?
Comment by Andrew S. Grigorev (eigrad) - Monday, 09 November 2009, 06:33 GMT
Sorry, there was no kernel panic. Just

Nov 8 20:32:37 bbook kernel: i915: Unknown symbol drm_helper_initial_config
Nov 8 20:32:37 bbook kernel: i915: Unknown symbol drm_helper_disable_unused_functions
Nov 8 20:32:37 bbook kernel: i915: Unknown symbol drm_crtc_helper_set_mode
Nov 8 20:32:37 bbook kernel: i915: Unknown symbol drm_helper_crtc_in_use
Nov 8 20:32:37 bbook kernel: i915: Unknown symbol drm_helper_mode_fill_fb_struct
Nov 8 20:32:37 bbook kernel: i915: Unknown symbol drm_helper_connector_dpms
Nov 8 20:32:37 bbook kernel: i915: Unknown symbol drm_helper_probe_single_connector_modes
Nov 8 20:32:37 bbook kernel: i915: Unknown symbol drm_helper_resume_force_mode
Nov 8 20:32:37 bbook kernel: i915: Unknown symbol drm_crtc_helper_set_config

in dmesg after `modprobe i915 modeset=1`.

Today I built kernel26 package using abs (without changes in PKGBUILD), and i915 with KMS now just works again, and Xorg too. May be maintainer not rebuilt package correctly?
Comment by Thomas Bächler (brain0) - Monday, 09 November 2009, 12:11 GMT
The version in core works perfectly here on x86_64, all symbols are being properly resolved.
Comment by Thomas Bächler (brain0) - Tuesday, 10 November 2009, 23:12 GMT
Is this i686 or x86_64? What happens with 2.6.31.6 from testing?
Comment by Andrew S. Grigorev (eigrad) - Friday, 13 November 2009, 05:18 GMT
This is i686. Perhaps it was some problem in my system, and I can not reproduce it.

Loading...