X fails with 2.6.24 kernel; ok with 2.6.22 kernel [G33]

Bug #174367 reported by Loïc Minier
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
xserver-xorg-video-intel (Ubuntu)

Bug Description


hardy recently gained 2.6.24 kernels; there were was a long series of cherry picks and reverts at the end of the gutsy cycle, in kernel and xorg's intel video driver, see bug #151351.

gdm wont come up (the screen will turn off until I start the shutdown with ctrl-alt-f1 + ctrl-alt-del and usplash changes the resolution again) and I see errors in the Xorg log (.old) after a reboot in the gutsy kernel. Will attach xorg log.


In other words, when in hardy booted with the hardy kernel, X doesn't come up. When in hardy but running the gutsy kernel, X does come up.

Revision history for this message
Loïc Minier (lool) wrote :

The following is "normal":
(EE) intel(0): Cannot support DRI with frame buffer width > 2048.

Losg ends with:
(II) EXA(0): Offscreen pixmap area of 50331648 bytes
(II) EXA(0): Driver registered support for the following operations:
(II) Solid
(II) Copy
(II) Composite (RENDER acceleration)
(==) intel(0): Backing store disabled
(==) intel(0): Silken mouse enabled
(II) intel(0): Initializing HW Cursor
(II) intel(0): Current clock rate multiplier: 1
(II) intel(0): xf86BindGARTMemory: bind key 0 at 0x006ff000 (pgoffset 1791)
(WW) intel(0): xf86BindGARTMemory: binding of gart memory with key 0
        at offset 0x6ff000 failed (Invalid argument)

Fatal server error:
Couldn't bind memory for front buffer

Revision history for this message
Loïc Minier (lool) wrote :
Revision history for this message
Loïc Minier (lool) wrote :
Bryce Harrington (bryce)
Changed in xserver-xorg-video-intel:
importance: Undecided → High
Bryce Harrington (bryce)
description: updated
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Loic,

It seems this might actually be a kernel bug. I don't suppose you'd be willing to do a kernel git bisect on the current Hardy kernel to try and narrow down which patch may be causing this issue? For more information about performing a git bisect please refer to http://www.kernel.org/doc/local/git-quick.html . And for help on building and booting the kernel from a git repository, please refer to: https://wiki.ubuntu.com/KernelTeam/GitKernelBuild . The GitKernelBuild guide actually uses the mainline kernel git tree in it's examples, so you'll just want to switch that with the Ubuntu kernel git tree which can be found here: http://kernel.ubuntu.com/git . Thanks!

Changed in linux:
status: New → Incomplete
Revision history for this message
Loïc Minier (lool) wrote :

@Leann: As I pointed to the original bug report where the commit was discussed, I'd appreciate if you could simply check whether reverting a14a5742c371dc55ca55bfc23bec892dfea26b9b one time more would be the fix. I just git pulled the hardy kernel, and:
% git diff v2.6.24-rc5 drivers/char/agp/intel-agp.c
--- a/drivers/char/agp/intel-agp.c
+++ b/drivers/char/agp/intel-agp.c
@@ -508,6 +508,11 @@ static void intel_i830_init_gtt_entries(void)
        } else {
+ /* G33's GTT stolen memory is separate from gfx data
+ * stolen memory.
+ */
+ if (IS_G33)
+ size = 0;
                switch (gmch_ctrl & I855_GMCH_GMS_MASK) {
                case I855_GMCH_GMS_STOLEN_1M:
                        gtt_entries = MB(1) - KB(size);

So the only difference between the Ubuntu tree and the upstream tree on the file which was changed and reverted 4 or 5 times in gutsy is the exact same code -- and I bet upstream has a working G33. I checked the xserver-xorg-video-intel tree and saw that the change in gutsy was not kept over for hardy, and Kyle told me that the change had to be in both the driver and kernel or none of them.

I think reverting a14a5742c371dc55ca55bfc23bec892dfea26b9b is the way to go; could you check whether that makes sense?

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Loic,

That makes sense to me. I'll reassign to the kernel team and ask them to revert the patch once again. Thanks.

Changed in linux:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → High
milestone: none → hardy-alpha-3
status: Incomplete → Triaged
Tim Gardner (timg-tpi)
Changed in linux:
status: Triaged → Fix Committed
Revision history for this message
Bryce Harrington (bryce) wrote :

Closing the -intel component since this sounds to be a kernel issue. (Feel free to reopen the -intel component if there's follow-on X.org work to do.)

Changed in xserver-xorg-video-intel:
status: New → Invalid
Steve Langasek (vorlon)
Changed in linux:
milestone: hardy-alpha-3 → hardy-alpha-4
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (3.2 KiB)

This bug was fixed in the package linux - 2.6.24-4.6

linux (2.6.24-4.6) hardy; urgency=low

  [Alessio Igor Bogani]

  * Fix -rt build FTBS.

  [Amit Kucheria]

  * LPIACOMPAT: Update thermal patches to be inline with lpia flavour
  * Poulsbo: Add USB Controller patch and corresponding config change

  [Fabio M. Di Nitto]

  * Enable aoe and nbd modules on hppa Ignore: yes
  * Fix ia64 build by using gcc-4.1

  [Tim Gardner]

  * Enable JFFS2 LZO compression.
    - LP: #178343
  * Remove IS_G33 special handling.
    - LP: #174367
    - LP: #95089
  * Enabled CONFIG_B43LEGACY=m
  * Enabled CONFIG_SCSI_QLOGIC_1280=m
  * Enabled CONFIG_FUSION=y for virtual
  * USB bluetooth device 0x0e5e:0x6622 floods errors to syslog
    - LP: #152689
  * Removed lpia from d-i.
  * Added ia64 modules.
  * Added hppa32/64 modules.

  [Upstream Kernel Changes]

  * DMI autoload dcdbas on all Dell systems.
  * sched: fix gcc warnings
  * leds: Fix leds_list_lock locking issues
  * leds: Fix locomo LED driver oops
  * x86: fix asm-x86/byteorder.h for userspace export
  * x86: fix asm-x86/msr.h for user-space export
  * fix lguest rmmod "bad pgd"
  * slub: provide /proc/slabinfo
  * [POWERPC] Fix build failure on Cell when CONFIG_SPU_FS=y
  * slub: register slabinfo to procfs
  * [SCSI] scsi_sysfs: restore prep_fn when ULD is removed
  * Unify /proc/slabinfo configuration
  * scsi: revert "[SCSI] Get rid of scsi_cmnd->done"
  * restrict reading from /proc/<pid>/maps to those who share ->mm or can
    ptrace pid
  * Fix kernel/ptrace.c compile problem (missing "may_attach()")
  * hwmon: (w83627ehf) Be more careful when changing VID input level
  * NFS: Fix a possible Oops in fs/nfs/super.c
  * NFSv4: Fix circular locking dependency in nfs4_kill_renewd
  * NFS: add newline to kernel warning message in auth_gss code
  * NFSv4: nfs4_open_confirm must not set the open_owner as confirmed on
  * NFSv4: Fix open_to_lock_owner sequenceid allocation...
  * IB/srp: Fix list corruption/oops on module reload
  * Console is utf-8 by default
  * [IA64] Update Altix BTE error return status patch
  * [IA64] Update Altix nofault code
  * [X25]: Add missing x25_neigh_put
  * [XFRM]: Do not define km_migrate() if !CONFIG_XFRM_MIGRATE
  * [CASSINI]: Fix endianness bug.
  * [CASSINI]: Revert 'dont touch page_count'.
  * [CASSINI]: Program parent Intel31154 bridge when necessary.
  * [CASSINI]: Set skb->truesize properly on receive packets.
  * [CASSINI]: Fix two obvious NAPI bugs.
  * [CASSINI]: Bump driver version and release date.
  * [INET]: Fix netdev renaming and inet address labels
  * [CONNECTOR]: Return proper error code in cn_call_callback()
  * [ISDN] i4l: 'NO CARRIER' message lost after ldisc flush
  * [ISDN]: i4l: Fix DLE handling for i4l-audio
  * fix: using joysticks in 32 bit applications on 64 bit systems
  * hda_intel suspend latency: shorten codec read
  * CPU hotplug: fix cpu_is_offline() on !CONFIG_HOTPLUG_CPU
  * Linux 2.6.24-rc7
  * PIE executabl...


Changed in linux:
status: Fix Committed → Fix Released
Revision history for this message
Loïc Minier (lool) wrote :

I'm happy to report that this is indeed fixed as expected and as the bug status already says.

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.