[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#570766: System hangs on X startup (855GM, KMS disabled)



Dear Cyril,

I am still having the problem, so the xserver-xorg-video-intel package is unusable for me. The kernel oops disappeared after some upgrade, so now there is no error messages I can read, because when I start the X server, with or without KMS enabled, it just crashes.

I am really sure, that the intel driver in lenny is working fine on my hardware. But unfortunately in squeeze it is not.

Do you have any ideas?

Regards,
Kojedzinszky Richard

On Thu, 4 Mar 2010, Cyril Brulebois wrote:

Richard Kojedzinszky <krichy@cflinux.hu> (03/03/2010):
Dear cyril,

Hi Richard,

For now i've tested the latest 2.6.32.y kernel source.
I've booted up, remotely loaded i915 with modeset=1, and this came into
dmesg:
[   49.316484] [drm] Initialized drm 1.1.0 20060810
[   49.351758] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ
16
[   49.351765] i915 0000:00:02.0: setting latency timer to 64
[   49.360262] [drm] set up 15M of stolen space
[   50.359223] [drm] DAC-6: set mode 640x480 0
[   50.835241] ------------[ cut here ]------------
[   50.835251] WARNING: at drivers/gpu/drm/drm_crtc_helper.c:1035
drm_helper_initial_config+0x3a/0x53 [drm_kms_helper]()
[   50.835255] Hardware name: AMILO M7405
[   50.835257] No connectors reported connected with modes
[   50.835260] Modules linked in: i915(+) drm_kms_helper drm i2c_algo_bit
acpi_cpufreq cpufreq_powersave cpufreq_stats cpufreq_userspace
cpufreq_conservative loop firewire_sbp2 arc4 ecb joydev ath5k 8139too
mac80211 snd_intel8x0 pcmcia ath snd_ac97_codec firewire_ohci 8139cp
cfg80211 firewire_core rfkill ac97_bus crc_itu_t yenta_socket snd_pcsp
rsrc_nonstatic snd_pcm pcmcia_core snd_timer video led_class mii uhci_hcd
intel_agp shpchp psmouse snd i2c_i801 ehci_hcd soundcore i2c_core usbcore
pci_hotplug evdev serio_raw agpgart ac battery output button processor
snd_page_alloc nls_base reiserfs dm_mod ide_cd_mod ide_gd_mod cdrom
thermal fan thermal_sys ata_generic libata scsi_mod ide_pci_generic piix
ide_core
[   50.835339] Pid: 1751, comm: modprobe Not tainted 2.6.32.9 #1
[   50.835342] Call Trace:
[   50.835352]  [<c1025f2b>] ? warn_slowpath_common+0x5d/0x70
[   50.835357]  [<c1025f71>] ? warn_slowpath_fmt+0x26/0x2a
[   50.835363]  [<f8efdd42>] ? drm_helper_initial_config+0x3a/0x53
[drm_kms_helper]
[   50.835389]  [<f8f559ce>] ? i915_driver_load+0xdc5/0xe6b [i915]
[   50.835402]  [<f8ecb1b5>] ? drm_get_dev+0x2a2/0x37c [drm]
[   50.835408]  [<c10e8c86>] ? sysfs_do_create_link+0xc0/0x102
[   50.835415]  [<c11361d7>] ? local_pci_probe+0xb/0xc
[   50.835420]  [<c1136f5c>] ? pci_device_probe+0x41/0x65
[   50.835425]  [<c1199326>] ? driver_probe_device+0x82/0xfd
[   50.835430]  [<c11993e1>] ? __driver_attach+0x40/0x5b
[   50.835437]  [<c1198b7f>] ? bus_for_each_dev+0x37/0x5f
[   50.835442]  [<c1199201>] ? driver_attach+0x11/0x13
[   50.835446]  [<c11993a1>] ? __driver_attach+0x0/0x5b
[   50.835451]  [<c1198ef3>] ? bus_add_driver+0x87/0x1bc
[   50.835457]  [<c1126f1c>] ? kset_find_obj+0x51/0x69
[   50.835462]  [<c11995f8>] ? driver_register+0x7a/0xd9
[   50.835467]  [<c1136a55>] ? __pci_register_driver+0x2c/0x82
[   50.835486]  [<f8f8b000>] ? i915_init+0x0/0x48 [i915]
[   50.835491]  [<c100113c>] ? do_one_initcall+0x54/0x14b
[   50.835498]  [<c104d783>] ? sys_init_module+0xa7/0x1d8
[   50.835503]  [<c1002a37>] ? sysenter_do_call+0x12/0x22
[   50.835508] ---[ end trace 9f1efd40b5f21a19 ]---
[   50.835519] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on
minor 0

You probably want to report that upstream, but read on.

You've mentioned some blog, but i did not found it in your letter,
or a link to it.

Failure from my side, as usual. Kernel versions are talked about in
those blog posts:
 http://ikibiki.org/blog/2010/02/28/Where_have_you_been/
 http://www.itp.tuwien.ac.at/~mattems/blog/2010/03/03#newer_linux_32_33

You might want to wait until another revision of the .32 or .33
kernels is available, then check whether the issue is still here.

If you were to open a bug in Debian, please put the kernel function
name or file path in the subject, that's AFAICT another story.

Mraw,
KiBi.




Reply to: