Thinkpad brightness keys kill X on 2.6.26.5
Hi all,
I just upgraded from 2.6.25.17 to 2.6.26.5 on my Thinkpad Z61t, and found the brightness keys will cause the X server to die. When using the brightness up/down keys, the screen will go blank -- Control+Alt+F# will still switch to a different virtual console, but switching back will not restore the video state.
After killing the window manager, I was able to bring up X again without a problem -- but using the brightness keys still causes it to go blank again within X, while the brightness does get changed correctly on the console.
There were no kernel messages, but this appeared in the Xorg log:
Backtrace: 0: X(xf86SigHandler+0x84) [0x80c43e4]
1: [0xffffe420]
2: /usr/lib/xorg/modules/extensions/libglx.so(__glXVendorPrivate+0x19c) [0xb7c9d bec]
3: /usr/lib/xorg/modules/extensions/libglx.so [0xb7ca1f6a]
4: X(Dispatch+0x19b) [0x8086ccb]
5: X(main+0x489) [0x806e6b9]
6: /lib/tls/libc.so.6(__libc_start_main+0xc8) [0xb7de4ea8]
7: X(FontFileCompleteXLFD+0xa5) [0x806d9f1]
Fatal server error:
Caught signal 4. Server aborting
(WW) I810(0): Successfully set original devices
(WW) I810(0): Setting the original video mode instead of restoring
the saved state
(--) I810(0): A non-CRT device is attached to pipe B.
No refresh rate overrides will be attempted.
(WW) I810(0): Extended BIOS function 0x5f05 failed.
(II) I810(0): BIOS call 0x5f05 not supported, setting refresh with VBE 3 method. (II) I810(0): xf86UnbindGARTMemory: unbind key 12
(II) I810(0): xf86UnbindGARTMemory: unbind key 8
(II) I810(0): xf86UnbindGARTMemory: unbind key 9
(II) I810(0): xf86UnbindGARTMemory: unbind key 11
(II) I810(0): xf86UnbindGARTMemory: unbind key 10
(WW) I810(0): Successfully set original devices (2)
I'm currently running on a Debian/etch system with the following packages:
xserver-xorg 7.1.0-19
xserver-xorg-video-i810 1.7.2-4
gcc 4.1.2 from Debian, Core Duo (T2500).
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)
.config attached -- is this a known issue? In the meantime, I'm starting a bisection to figure out where the problem crops up.
-- DN
Daniel
CONFIG_X86_32=yCONFIG_X86=y CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig" CONFIG_GENERIC_TIME=yCONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_FAST_CMPXCHG_LOCAL=yCONFIG_MMU=yCONFIG_ZONE_DMA=yCONFIG_GENERIC_ISA_DMA=yCONFIG_GENERIC_IOMAP=yCONFIG_GENERIC_BUG=yCONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y CONFIG_ARCH_POPULATES_NODE_MAP=y CONFIG_ARCH_SUPPORTS_AOUT=y CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_GENERIC_PENDING_IRQ=yCONFIG_X86_SMP=yCONFIG_X86_32_SMP=yCONFIG_X86_HT=yCONFIG_X86_BIOS_REBOOT=yCONFIG_X86_TRAMPOLINE=yCONFIG_KTIME_SCALAR=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_EXPERIMENTAL=yCONFIG_LOCK_KERNEL=yCONFIG_INIT_ENV_ARG_LIMIT=32CONFIG_LOCALVERSION=""CONFIG_LOCALVERSION_AUTO=yCONFIG_SWAP=yCONFIG_SYSVIPC=yCONFIG_SYSVIPC_SYSCTL=yCONFIG_POSIX_MQUEUE=yCONFIG_BSD_PROCESS_ACCT=yCONFIG_BSD_PROCESS_ACCT_V3=yCONFIG_IKCONFIG=yCONFIG_IKCONFIG_PROC=yCONFIG_LOG_BUF_SHIFT=17CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=yCONFIG_GROUP_SCHED=yCONFIG_USER_SCHED=yCONFIG_SYSFS_DEPRECATED=yCONFIG_SYSFS_DEPRECATED_V2=yCONFIG_RELAY=yCONFIG_CC_OPTIMIZE_FOR_SIZE=yCONFIG_SYSCTL=yCONFIG_EMBEDDED=yCONFIG_UID16=yCONFIG_SYSCTL_SYSCALL=yCONFIG_SYSCTL_SYSCALL_CHECK=yCONFIG_HOTPLUG=yCONFIG_PRINTK=yCONFIG_BUG=yCONFIG_ELF_CORE=yCONFIG_BASE_FULL=yCONFIG_FUTEX=yCONFIG_ANON_INODES=yCONFIG_EPOLL=yCONFIG_SIGNALFD=yCONFIG_TIMERFD=yCONFIG_EVENTFD=yCONFIG_SHMEM=yCONFIG_VM_EVENT_COUNTERS=yCONFIG_SLUB_DEBUG=yCONFIG_SLUB=yCONFIG_PROFILING=yCONFIG_OPROFILE=yCONFIG_HAVE_OPROFILE=yCONFIG_HAVE_KPROBES=yCONFIG_HAVE_KRETPROBES=yCONFIG_PROC_PAGE_MONITOR=yCONFIG_SLABINFO=yCONFIG_RT_MUTEXES=yCONFIG_BASE_SMALL=0CONFIG_MODULES=yCONFIG_MODULE_UNLOAD=yCONFIG_STOP_MACHINE=yCONFIG_BLOCK=yCONFIG_BLK_DEV_IO_TRACE=y
CONFIG_IOSCHED_NOOP=yCONFIG_IOSCHED_DEADLINE=yCONFIG_DEFAULT_DEADLINE=yCONFIG_DEFAULT_IOSCHED="deadline"CONFIG_PREEMPT_NOTIFIERS=yCONFIG_CLASSIC_RCU=y
CONFIG_TICK_ONESHOT=yCONFIG_NO_HZ=yCONFIG_HIGH_RES_TIMERS=yCONFIG_GENERIC_CLOCKEVENTS_BUILD=yCONFIG_SMP=yCONFIG_X86_PC=yCONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER=yCONFIG_PARAVIRT_GUEST=yCONFIG_KVM_CLOCK=yCONFIG_PARAVIRT=yCONFIG_PARAVIRT_CLOCK=yCONFIG_MCORE2=yCONFIG_X86_CPU=yCONFIG_X86_CMPXCHG=yCONFIG_X86_L1_CACHE_SHIFT=6CONFIG_X86_XADD=yCONFIG_X86_WP_WORKS_OK=yCONFIG_X86_INVLPG=yCONFIG_X86_BSWAP=yCONFIG_X86_POPAD_OK=yCONFIG_X86_GOOD_APIC=yCONFIG_X86_INTEL_USERCOPY=yCONFIG_X86_USE_PPRO_CHECKSUM=yCONFIG_X86_P6_NOP=yCONFIG_X86_TSC=yCONFIG_X86_MINIMUM_CPU_FAMILY=6CONFIG_X86_DEBUGCTLMSR=yCONFIG_HPET_TIMER=yCONFIG_HPET_EMULATE_RTC=yCONFIG_DMI=yCONFIG_NR_CPUS=2CONFIG_SCHED_MC=yCONFIG_PREEMPT=yCONFIG_X86_LOCAL_APIC=yCONFIG_X86_IO_APIC=yCONFIG_X86_MCE=yCONFIG_X86_MCE_NONFATAL=yCONFIG_X86_MCE_P4THERMAL=yCONFIG_VM86=yCONFIG_X86_REBOOTFIXUPS=yCONFIG_MICROCODE=yCONFIG_MICROCODE_OLD_INTERFACE=yCONFIG_X86_MSR=yCONFIG_X86_CPUID=yCONFIG_HIGHMEM4G=yCONFIG_VMSPLIT_3G=yCONFIG_PAGE_OFFSET=0xC0000000CONFIG_HIGHMEM=yCONFIG_ARCH_FLATMEM_ENABLE=yCONFIG_ARCH_SPARSEMEM_ENABLE=yCONFIG_ARCH_SELECT_MEMORY_MODEL=yCONFIG_SELECT_MEMORY_MODEL=yCONFIG_FLATMEM_MANUAL=yCONFIG_FLATMEM=yCONFIG_FLAT_NODE_MEM_MAP=yCONFIG_SPARSEMEM_STATIC=yCONFIG_PAGEFLAGS_EXTENDED=yCONFIG_SPLIT_PTLOCK_CPUS=4CONFIG_ZONE_DMA_FLAG=1CONFIG_BOUNCE=yCONFIG_VIRT_TO_BUS=yCONFIG_HIGHPTE=yCONFIG_MTRR=yCONFIG_X86_PAT=yCONFIG_HZ_300=yCONFIG_HZ=300CONFIG_SCHED_HRTICK=yCONFIG_PHYSICAL_START=0x100000CONFIG_PHYSICAL_ALIGN=0x100000CONFIG_COMPAT_VDSO=yCONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_PM=yCONFIG_ACPI=yCONFIG_ACPI_PROCFS=yCONFIG_ACPI_PROCFS_POWER=yCONFIG_ACPI_SYSFS_POWER=yCONFIG_ACPI_PROC_EVENT=yCONFIG_ACPI_AC=yCONFIG_ACPI_BATTERY=yCONFIG_ACPI_BUTTON=yCONFIG_ACPI_VIDEO=yCONFIG_ACPI_FAN=yCONFIG_ACPI_DOCK=yCONFIG_ACPI_BAY=mCONFIG_ACPI_PROCESSOR=yCONFIG_ACPI_THERMAL=yCONFIG_ACPI_CUSTOM_DSDT_FILE=""CONFIG_ACPI_BLACKLIST_YEAR=0CONFIG_ACPI_EC=yCONFIG_ACPI_POWER=yCONFIG_ACPI_SYSTEM=yCONFIG_X86_PM_TIMER=y
CONFIG_CPU_FREQ=yCONFIG_CPU_FREQ_TABLE=yCONFIG_CPU_FREQ_STAT=yCONFIG_CPU_FREQ_STAT_DETAILS=yCONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=yCONFIG_CPU_FREQ_GOV_PERFORMANCE=yCONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_X86_ACPI_CPUFREQ=y
CONFIG_CPU_IDLE=yCONFIG_CPU_IDLE_GOV_LADDER=yCONFIG_CPU_IDLE_GOV_MENU=y
CONFIG_PCI=yCONFIG_PCI_GOANY=yCONFIG_PCI_BIOS=yCONFIG_PCI_DIRECT=yCONFIG_PCI_MMCONFIG=yCONFIG_PCI_DOMAINS=yCONFIG_PCIEPORTBUS=yCONFIG_PCIEAER=yCONFIG_ARCH_SUPPORTS_MSI=yCONFIG_PCI_MSI=yCONFIG_HT_IRQ=yCONFIG_ISA_DMA_API=yCONFIG_ISA=yCONFIG_PCCARD=mCONFIG_PCMCIA=mCONFIG_PCMCIA_LOAD_CIS=yCONFIG_CARDBUS=y
CONFIG_YENTA=mCONFIG_YENTA_TI=yCONFIG_YENTA_ENE_TUNE=yCONFIG_PCMCIA_PROBE=yCONFIG_PCCARD_NONSTATIC=m
CONFIG_BINFMT_ELF=y
CONFIG_NET=y
CONFIG_PACKET=yCONFIG_PACKET_MMAP=yCONFIG_UNIX=yCONFIG_XFRM=yCONFIG_XFRM_USER=yCONFIG_NET_KEY=yCONFIG_INET=yCONFIG_IP_MULTICAST=yCONFIG_IP_FIB_HASH=yCONFIG_INET_AH=yCONFIG_INET_ESP=yCONFIG_INET_IPCOMP=yCONFIG_INET_XFRM_TUNNEL=yCONFIG_INET_TUNNEL=yCONFIG_INET_XFRM_MODE_TRANSPORT=yCONFIG_INET_XFRM_MODE_TUNNEL=yCONFIG_INET_LRO=yCONFIG_INET_DIAG=yCONFIG_INET_TCP_DIAG=yCONFIG_TCP_CONG_CUBIC=yCONFIG_DEFAULT_TCP_CONG="cubic"CONFIG_NETFILTER=yCONFIG_NETFILTER_ADVANCED=yCONFIG_BRIDGE_NETFILTER=y
CONFIG_NF_CONNTRACK=yCONFIG_NF_CONNTRACK_EVENTS=yCONFIG_NF_CONNTRACK_FTP=yCONFIG_NF_CONNTRACK_IRC=yCONFIG_NF_CONNTRACK_NETBIOS_NS=yCONFIG_NF_CONNTRACK_TFTP=yCONFIG_NETFILTER_XTABLES=yCONFIG_NETFILTER_XT_MATCH_CONNTRACK=yCONFIG_NETFILTER_XT_MATCH_HELPER=yCONFIG_NETFILTER_XT_MATCH_IPRANGE=yCONFIG_NETFILTER_XT_MATCH_LENGTH=yCONFIG_NETFILTER_XT_MATCH_OWNER=yCONFIG_NETFILTER_XT_MATCH_POLICY=yCONFIG_NETFILTER_XT_MATCH_MULTIPORT=yCONFIG_NETFILTER_XT_MATCH_STATE=yCONFIG_NETFILTER_XT_MATCH_U32=y
CONFIG_NF_CONNTRACK_IPV4=yCONFIG_NF_CONNTRACK_PROC_COMPAT=yCONFIG_IP_NF_IPTABLES=yCONFIG_IP_NF_FILTER=yCONFIG_IP_NF_TARGET_REJECT=yCONFIG_IP_NF_TARGET_LOG=yCONFIG_NF_NAT=yCONFIG_NF_NAT_NEEDED=yCONFIG_IP_NF_TARGET_MASQUERADE=yCONFIG_IP_NF_TARGET_REDIRECT=yCONFIG_NF_NAT_FTP=yCONFIG_NF_NAT_IRC=yCONFIG_NF_NAT_TFTP=y
CONFIG_BRIDGE_NF_EBTABLES=yCONFIG_BRIDGE_EBT_BROUTE=yCONFIG_BRIDGE_EBT_T_FILTER=yCONFIG_BRIDGE_EBT_T_NAT=yCONFIG_BRIDGE_EBT_802_3=yCONFIG_BRIDGE_EBT_IP=yCONFIG_BRIDGE_EBT_ARPREPLY=yCONFIG_BRIDGE_EBT_DNAT=yCONFIG_BRIDGE_EBT_REDIRECT=yCONFIG_BRIDGE_EBT_SNAT=yCONFIG_BRIDGE_EBT_LOG=yCONFIG_BRIDGE=yCONFIG_VLAN_8021Q=yCONFIG_LLC=yCONFIG_NET_SCH_FIFO=y
CONFIG_CFG80211=yCONFIG_NL80211=yCONFIG_WIRELESS_EXT=yCONFIG_MAC80211=y
CONFIG_MAC80211_RC_DEFAULT_PID=y
CONFIG_MAC80211_RC_DEFAULT="pid"CONFIG_MAC80211_RC_PID=yCONFIG_IEEE80211=yCONFIG_IEEE80211_CRYPT_WEP=yCONFIG_IEEE80211_CRYPT_CCMP=yCONFIG_IEEE80211_CRYPT_TKIP=yCONFIG_RFKILL=yCONFIG_RFKILL_INPUT=y
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"CONFIG_PREVENT_FIRMWARE_BUILD=yCONFIG_FW_LOADER=yCONFIG_PNP=y
CONFIG_PNPACPI=yCONFIG_BLK_DEV=yCONFIG_BLK_DEV_LOOP=yCONFIG_CDROM_PKTCDVD=yCONFIG_CDROM_PKTCDVD_BUFFERS=8CONFIG_VIRTIO_BLK=yCONFIG_MISC_DEVICES=yCONFIG_THINKPAD_ACPI=yCONFIG_THINKPAD_ACPI_DEBUG=yCONFIG_THINKPAD_ACPI_BAY=yCONFIG_THINKPAD_ACPI_VIDEO=yCONFIG_THINKPAD_ACPI_HOTKEY_POLL=yCONFIG_HAVE_IDE=y
CONFIG_SCSI=yCONFIG_SCSI_DMA=yCONFIG_SCSI_PROC_FS=y
CONFIG_BLK_DEV_SD=yCONFIG_BLK_DEV_SR=mCONFIG_CHR_DEV_SG=y
CONFIG_SCSI_WAIT_SCAN=m
CONFIG_ATA=yCONFIG_ATA_ACPI=yCONFIG_SATA_PMP=yCONFIG_SATA_AHCI=yCONFIG_ATA_SFF=yCONFIG_ATA_PIIX=mCONFIG_MD=yCONFIG_BLK_DEV_MD=yCONFIG_MD_LINEAR=yCONFIG_BLK_DEV_DM=yCONFIG_DM_CRYPT=yCONFIG_DM_SNAPSHOT=m
CONFIG_NETDEVICES=yCONFIG_TUN=yCONFIG_NETDEV_1000=yCONFIG_TIGON3=m
CONFIG_WLAN_80211=yCONFIG_AIRO=mCONFIG_AIRO_CS=mCONFIG_IWLWIFI=yCONFIG_IWLCORE=yCONFIG_IWLWIFI_RFKILL=yCONFIG_IWL3945=mCONFIG_IWL3945_SPECTRUM_MEASUREMENT=y
CONFIG_VIRTIO_NET=y
CONFIG_INPUT=y
CONFIG_INPUT_MOUSEDEV=yCONFIG_INPUT_MOUSEDEV_PSAUX=yCONFIG_INPUT_MOUSEDEV_SCREEN_X=1024CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768CONFIG_INPUT_EVDEV=y
CONFIG_INPUT_KEYBOARD=yCONFIG_KEYBOARD_ATKBD=yCONFIG_INPUT_MOUSE=yCONFIG_MOUSE_PS2=yCONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_SERIO=yCONFIG_SERIO_I8042=yCONFIG_SERIO_LIBPS2=y
CONFIG_VT=yCONFIG_VT_CONSOLE=yCONFIG_HW_CONSOLE=yCONFIG_DEVKMEM=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_UNIX98_PTYS=yCONFIG_NVRAM=yCONFIG_RTC=y
CONFIG_HPET=yCONFIG_HPET_RTC_IRQ=yCONFIG_HPET_MMAP=yCONFIG_DEVPORT=yCONFIG_I2C=yCONFIG_I2C_BOARDINFO=yCONFIG_I2C_HELPER_AUTO=yCONFIG_I2C_ALGOBIT=y
CONFIG_POWER_SUPPLY=yCONFIG_HWMON=yCONFIG_SENSORS_CORETEMP=yCONFIG_THERMAL=yCONFIG_THERMAL_HWMON=y
CONFIG_SSB_POSSIBLE=y
CONFIG_AGP=yCONFIG_AGP_INTEL=yCONFIG_DRM=yCONFIG_DRM_I915=yCONFIG_VIDEO_OUTPUT_CONTROL=yCONFIG_FB=yCONFIG_FIRMWARE_EDID=yCONFIG_FB_DDC=yCONFIG_FB_CFB_FILLRECT=yCONFIG_FB_CFB_COPYAREA=yCONFIG_FB_CFB_IMAGEBLIT=yCONFIG_FB_MODE_HELPERS=y
CONFIG_FB_INTEL=yCONFIG_FB_INTEL_I2C=yCONFIG_BACKLIGHT_LCD_SUPPORT=yCONFIG_LCD_CLASS_DEVICE=yCONFIG_BACKLIGHT_CLASS_DEVICE=y
CONFIG_VGA_CONSOLE=yCONFIG_VIDEO_SELECT=yCONFIG_DUMMY_CONSOLE=yCONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_SOUND=m
CONFIG_SND=mCONFIG_SND_TIMER=mCONFIG_SND_PCM=mCONFIG_SND_SEQUENCER=mCONFIG_SND_OSSEMUL=yCONFIG_SND_MIXER_OSS=mCONFIG_SND_PCM_OSS=mCONFIG_SND_PCM_OSS_PLUGINS=yCONFIG_SND_SEQUENCER_OSS=yCONFIG_SND_RTCTIMER=mCONFIG_SND_SEQ_RTCTIMER_DEFAULT=yCONFIG_SND_DYNAMIC_MINORS=yCONFIG_SND_SUPPORT_OLD_API=yCONFIG_SND_VERBOSE_PROCFS=yCONFIG_SND_VMASTER=y
CONFIG_SND_AC97_CODEC=m
CONFIG_SND_HDA_INTEL=mCONFIG_SND_HDA_CODEC_ANALOG=yCONFIG_SND_HDA_POWER_SAVE=yCONFIG_SND_HDA_POWER_SAVE_DEFAULT=120CONFIG_SND_INTEL8X0=m
CONFIG_AC97_BUS=mCONFIG_HID_SUPPORT=yCONFIG_HID=y
CONFIG_USB_HID=yCONFIG_USB_SUPPORT=yCONFIG_USB_ARCH_HAS_HCD=yCONFIG_USB_ARCH_HAS_OHCI=yCONFIG_USB_ARCH_HAS_EHCI=yCONFIG_USB=yCONFIG_USB_ANNOUNCE_NEW_DEVICES=y
CONFIG_USB_DEVICEFS=yCONFIG_USB_DEVICE_CLASS=yCONFIG_USB_DYNAMIC_MINORS=yCONFIG_USB_SUSPEND=y
CONFIG_USB_EHCI_HCD=mCONFIG_USB_EHCI_ROOT_HUB_TT=yCONFIG_USB_UHCI_HCD=m
CONFIG_USB_STORAGE=yCONFIG_USB_LIBUSUAL=y
CONFIG_USB_MON=y
CONFIG_NEW_LEDS=yCONFIG_LEDS_CLASS=y
CONFIG_DMADEVICES=y
CONFIG_DMIID=y
CONFIG_EXT2_FS=mCONFIG_EXT3_FS=yCONFIG_JBD=yCONFIG_INOTIFY=yCONFIG_INOTIFY_USER=y
CONFIG_ISO9660_FS=yCONFIG_JOLIET=yCONFIG_UDF_FS=yCONFIG_UDF_NLS=y
CONFIG_FAT_FS=yCONFIG_MSDOS_FS=yCONFIG_VFAT_FS=yCONFIG_FAT_DEFAULT_CODEPAGE=437CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"CONFIG_NTFS_FS=y
CONFIG_PROC_FS=yCONFIG_PROC_KCORE=yCONFIG_PROC_SYSCTL=yCONFIG_SYSFS=yCONFIG_TMPFS=yCONFIG_CONFIGFS_FS=y
CONFIG_NETWORK_FILESYSTEMS=yCONFIG_NFS_FS=yCONFIG_NFS_V3=yCONFIG_LOCKD=yCONFIG_LOCKD_V4=yCONFIG_NFS_COMMON=yCONFIG_SUNRPC=yCONFIG_SUNRPC_BIND34=yCONFIG_SMB_FS=yCONFIG_SMB_NLS_DEFAULT=yCONFIG_SMB_NLS_REMOTE="cp437"CONFIG_CIFS=yCONFIG_CIFS_STATS=yCONFIG_CIFS_STATS2=yCONFIG_CIFS_WEAK_PW_HASH=yCONFIG_CIFS_XATTR=yCONFIG_CIFS_POSIX=y
CONFIG_PARTITION_ADVANCED=yCONFIG_MAC_PARTITION=yCONFIG_MSDOS_PARTITION=yCONFIG_LDM_PARTITION=yCONFIG_NLS=yCONFIG_NLS_DEFAULT="utf8"CONFIG_NLS_CODEPAGE_437=yCONFIG_NLS_CODEPAGE_932=yCONFIG_NLS_ASCII=yCONFIG_NLS_ISO8859_1=yCONFIG_NLS_ISO8859_15=yCONFIG_NLS_UTF8=y
CONFIG_TRACE_IRQFLAGS_SUPPORT=yCONFIG_ENABLE_WARN_DEPRECATED=yCONFIG_ENABLE_MUST_CHECK=yCONFIG_FRAME_WARN=1024CONFIG_MAGIC_SYSRQ=yCONFIG_DEBUG_FS=yCONFIG_DEBUG_KERNEL=yCONFIG_TIMER_STATS=yCONFIG_SLUB_STATS=yCONFIG_HAVE_ARCH_KGDB=yCONFIG_NONPROMISC_DEVMEM=yCONFIG_EARLY_PRINTK=yCONFIG_DEBUG_RODATA=yCONFIG_4KSTACKS=yCONFIG_X86_FIND_SMP_CONFIG=yCONFIG_X86_MPPARSE=yCONFIG_DOUBLEFAULT=yCONFIG_IO_DELAY_TYPE_0X80=0CONFIG_IO_DELAY_TYPE_0XED=1CONFIG_IO_DELAY_TYPE_UDELAY=2CONFIG_IO_DELAY_TYPE_NONE=3CONFIG_IO_DELAY_0X80=yCONFIG_DEFAULT_IO_DELAY_TYPE=0
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=yCONFIG_CRYPTO_AEAD=yCONFIG_CRYPTO_BLKCIPHER=yCONFIG_CRYPTO_HASH=yCONFIG_CRYPTO_MANAGER=yCONFIG_CRYPTO_AUTHENC=y
CONFIG_CRYPTO_SEQIV=y
CONFIG_CRYPTO_CBC=yCONFIG_CRYPTO_ECB=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_MD5=yCONFIG_CRYPTO_MICHAEL_MIC=yCONFIG_CRYPTO_SHA1=yCONFIG_CRYPTO_SHA256=y
CONFIG_CRYPTO_AES=yCONFIG_CRYPTO_AES_586=yCONFIG_CRYPTO_ARC4=yCONFIG_CRYPTO_DES=y
CONFIG_CRYPTO_DEFLATE=yCONFIG_CRYPTO_LZO=yCONFIG_HAVE_KVM=yCONFIG_VIRTUALIZATION=yCONFIG_KVM=yCONFIG_KVM_INTEL=yCONFIG_VIRTIO=yCONFIG_VIRTIO_RING=yCONFIG_VIRTIO_PCI=yCONFIG_VIRTIO_BALLOON=y
CONFIG_BITREVERSE=yCONFIG_GENERIC_FIND_FIRST_BIT=yCONFIG_GENERIC_FIND_NEXT_BIT=yCONFIG_CRC_ITU_T=yCONFIG_CRC32=yCONFIG_ZLIB_INFLATE=yCONFIG_ZLIB_DEFLATE=yCONFIG_LZO_COMPRESS=yCONFIG_LZO_DECOMPRESS=yCONFIG_PLIST=yCONFIG_HAS_IOMEM=yCONFIG_HAS_IOPORT=yCONFIG_HAS_DMA=y
CONFIG_ACPI_VIDEO on Thinkpad blanks display.
Quoted 5 lines · carbonated beverage
I just upgraded from 2.6.25.17 to 2.6.26.5 on my Thinkpad Z61t, and found the brightness keys will cause the X server to die. When using the brightness up/down keys, the screen will go blank -- Control+Alt+F# will still switch to a different virtual console, but switching back will not restore the video state.
(Subject changed to match the observed cause)
Figured out what the change was -- in 2.6.25.x, the brightness keys worked without setting CONFIG_ACPI_VIDEO. However, in 2.6.26.x, the brightness keys do not work on the console without that enabled.
If 2.6.25.x has that config option enabled, I still get the same blank screen symptoms -- with the following in the X logs:
(II) PM Event received: Capability Changed
I830PMEvent: Capability change
(II) I810(0): Next ACPI _DGS [0] 0x80000100
(II) I810(0): ACPI Toggle devices 0x1
(II) I810(0): ACPI Toggle to 0x1
(II) I810(0): Hotkey switch to 0x800.
(II) I810(0): Attachable device 0x80000100.
(II) I810(0): Attachable device 0x80000240.
(II) I810(0): Attachable device 0x80000410.
(II) I810(0): Requested display devices 0x800.
(II) I810(0): Toggle (1) 0x1
(II) I810(0): Detected duplicate devices. Toggling (0x1)
(II) I810(0): Detected display change operation (0x0, 0x800, 0x1). (II) I810(0): Clearing Clone mode
(II) I810(0): Primary pipe is now A.
(--) I810(0): A non-CRT device is attached to pipe A.
No refresh rate overrides will be attempted.
(II) I810(0): Display plane A is enabled and connected to Pipe A. (II) I810(0): Display plane B is disabled and connected to Pipe B. (II) I810(0): Enabling plane A.
(II) I810(0): Display plane A is now enabled and connected to Pipe A. (II) I810(0): Display plane B is now disabled and connected to Pipe B. (II) I810(0): PIPEACONF is 0x80000000
(II) I810(0): PIPEBCONF is 0x00000000
(II) I810(0): Mode bandwidth is 58 Mpixel/s
(II) I810(0): maxBandwidth is 1152 Mbyte/s, pipe bandwidths are 48 Mbyte/s, 0 Mb yte/s
(WW) I810(0): Changing XVideo pipe (1 to 0).
Without CONFIG_ACPI_VIDEO, the above message don't appear. From this point, any pointers on figuring out why the ACPI features makes the screen go blank?
-- DN
Daniel
Re: CONFIG_ACPI_VIDEO on Thinkpad blanks display.
Quoted 2 lines · carbonated beverage
Without
CONFIG_ACPI_VIDEO, the above message don't appear. From this point, any pointers on figuring out why the ACPI features makes the screen go blank?
Yes. X assumed that any ACPI key press was a request to switch the video output. Upgrade X.
Signature · 1 line
Matthew Garrett | [email protected]
Re: CONFIG_ACPI_VIDEO on Thinkpad blanks display.
Quoted 5 lines · Matthew Garrett
Quoted 2 lines
Without
CONFIG_ACPI_VIDEO, the above message don't appear. From this point, any pointers on figuring out why the ACPI features makes the screen go blank?Yes. X assumed that any ACPI key press was a request to switch the video output. Upgrade X.
Since CONFIG_ACPI_VIDEO wasn't required before 2.6.26.x to change the LCD brightness, I'd rather the kernel go back to whatever it was doing for 2.6.25.x. Upgrading X past what's currently packaged by the distribution just to get a new kernel working is somewhat of a pain.
What change linked the brightness keys to CONFIG_ACPI_VIDEO?
-- DN
Daniel
Re: CONFIG_ACPI_VIDEO on Thinkpad blanks display.
Quoted 9 lines · carbonated beverage
Quoted 5 lines · Matthew Garrett
Quoted 2 lines
Without
CONFIG_ACPI_VIDEO, the above message don't appear. From this point, any pointers on figuring out why the ACPI features makes the screen go blank?Yes. X assumed that any ACPI key press was a request to switch the video output. Upgrade X.
Since
CONFIG_ACPI_VIDEOwasn't required before 2.6.26.x to change the LCD brightness, I'd rather the kernel go back to whatever it was doing for
Well, we do give you a way out: do not load ACPI video, and load thinkpad-acpi with the proper parameters to enable its backlight control (if it is getting disabled by default). Check the docs.
Quoted 2 lines
2.6.25.x. Upgrading X past what's currently packaged by the distribution just to get a new kernel working is somewhat of a pain.
Your X is broken, and in an extremely hideous way. You could try to get it to disable ACPI key support, or you can make sure nothing EVER sends ACPI video events to it. That means you must not use the ACPI video module in your kernel until you install a fixed X.org.
Signature · 4 lines
"One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
Re: CONFIG_ACPI_VIDEO on Thinkpad blanks display.
Quoted 3 lines · Henrique de Moraes Holschuh
Well, we do give you a way out: do not load ACPI video, and load thinkpad-acpi with the proper parameters to enable its backlight control (if it is getting disabled by default). Check the docs.
Thanks, I'll give this a shot.
Quoted 4 lines
Your X is broken, and in an extremely hideous way. You could try to get it to disable ACPI key support, or you can make sure nothing EVER sends ACPI video events to it. That means you must not use the ACPI video module in your kernel until you install a fixed X.org.
Okay, I'll see what happens.
-- DN
Daniel
Hi!
Quoted 6 lines
I just upgraded from 2.6.25.17 to 2.6.26.5 on my Thinkpad Z61t, and found the brightness keys will cause the X server to die. When using the brightness up/down keys, the screen will go blank -- Control+Alt+F# will still switch to a different virtual console, but switching back will not restore the video state.
Quoted 6 lines
After killing the window manager, I was able to bring up X again without a problem -- but using the brightness keys still causes it to go blank again within X, while the brightness does get changed correctly on the console.
There were no kernel messages, but this appeared in the Xorg log:
Yes, I had similar problems... for me it blanked screen on closing lid. Problem disappeared after upgrading X...
Quoted 2 lines
.config attached -- is this a known issue? In the meantime, I'm starting a bisection to figure out where the problem crops up.
For me CONFIG_ACPI_VIDEO never really worked...
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Quoted 21 lines · Pavel Machek
Hi!
Quoted 6 lines
I just upgraded from 2.6.25.17 to 2.6.26.5 on my Thinkpad Z61t, and found the brightness keys will cause the X server to die. When using the brightness up/down keys, the screen will go blank -- Control+Alt+F# will still switch to a different virtual console, but switching back will not restore the video state.
Quoted 7 lines
After killing the window manager, I was able to bring up X again without a problem -- but using the brightness keys still causes it to go blank again within X, while the brightness does get changed correctly on the console.
There were no kernel messages, but this appeared in the Xorg log:
Yes, I had similar problems... for me it blanked screen on closing lid. Problem disappeared after upgrading X...
Quoted 6 lines
Quoted 3 lines
.config attached -- is this a known issue? In the meantime, I'm starting a bisection to figure out where the problem crops up.
For me
CONFIG_ACPI_VIDEOnever really worked...
On my shiny new X200 running Fedora Rawhide, I'm finding that the brightness control keys work OK, but the backlight remains stuck off after a resume. The machine is working fine but the backlight is just off; I can see the display under a bright light. Switching consoles and poking about in /sys/class/backlight/acpi_video?/ didn't help.
J
Quoted 26 lines · Jeremy Fitzhardinge
Quoted 25 lines · Pavel Machek
Hi!
Quoted 6 lines
I just upgraded from 2.6.25.17 to 2.6.26.5 on my Thinkpad Z61t, and found the brightness keys will cause the X server to die. When using the brightness up/down keys, the screen will go blank -- Control+Alt+F# will still switch to a different virtual console, but switching back will not restore the video state.
Quoted 7 lines
After killing the window manager, I was able to bring up X again without a problem -- but using the brightness keys still causes it to go blank again within X, while the brightness does get changed correctly on the console.
There were no kernel messages, but this appeared in the Xorg log:
Yes, I had similar problems... for me it blanked screen on closing lid. Problem disappeared after upgrading X...
Quoted 3 lines
.config attached -- is this a known issue? In the meantime, I'm starting a bisection to figure out where the problem crops up.
Quoted 8 lines
Quoted 2 lines
For me
CONFIG_ACPI_VIDEOnever really worked...On my shiny new X200 running Fedora Rawhide, I'm finding that the brightness control keys work OK, but the backlight remains stuck off after a resume. The machine is working fine but the backlight is just off; I can see the display under a bright light. Switching consoles and poking about in /sys/class/backlight/acpi_video?/ didn't help.
What are you using for s2ram? s2ram -f -a 3 normally works on thinkpads...
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Quoted 5 lines · Jeremy Fitzhardinge
On my shiny new X200 running Fedora Rawhide, I'm finding that the brightness control keys work OK, but the backlight remains stuck off after a resume. The machine is working fine but the backlight is just off; I can see the display under a bright light. Switching consoles and poking about in /sys/class/backlight/acpi_video?/ didn't help.
Intel graphics, right? The DRM layer should handle full resume on modern Intel hardware, but there's the potential for bugs. This is entirely unrelated to ACPI, though.
Signature · 1 line
Matthew Garrett | [email protected]
Quoted 1 line · Pavel Machek
What are you using for s2ram? s2ram -f -a 3 normally works on thinkpads...
Fedora doesn't use s2ram, and at this point passing any s2ram flags on Intel graphics is just covering up kernel bugs.
Signature · 1 line
Matthew Garrett | [email protected]
Quoted 7 lines · Matthew Garrett
Quoted 2 lines · Jeremy Fitzhardinge
On my shiny new X200 running Fedora Rawhide, I'm finding that the brightness control keys work OK, but the backlight remains stuck off after a resume. The machine is working fine but the backlight is just off; I can see the display under a bright light. Switching consoles and poking about in /sys/class/backlight/acpi_video?/ didn't help.
Intel graphics, right?
Yes. The new, erm , X4500?
Quoted 3 lines
The DRM layer should handle full resume on modern
Intel hardware, but there's the potential for bugs. This is entirely unrelated to ACPI, though.
OK, that's a good clue. I poke at acpi to change the brightness, so I'd assumed that acpi would also handle turning the backlight on/off.
I'm using the rawhide rather than standard kernel, but I'd thought they were fairly similar.
I'm also using the vesa X server; I haven't tried using the intel one yet.
J
Quoted 1 line · Jeremy Fitzhardinge
I'm also using the vesa X server; I haven't tried using the intel one yet.
Ah. In that case, I suspect the DRM module is never binding and may not do its thing.
Signature · 1 line
Matthew Garrett | [email protected]
Quoted 8 lines · Matthew Garrett
Quoted 2 lines · Jeremy Fitzhardinge
I'm also using the vesa X server; I haven't tried using the intel one yet.
Ah. In that case, I suspect the DRM module is never binding and may not do its thing.
OK, great. Simply loading the i915 module makes the backlight come back after resume, even using the vesa X server.
Thanks,
J
Quoted 21 lines · Jeremy Fitzhardinge
Quoted 11 lines · Matthew Garrett
Quoted 7 lines · Jeremy Fitzhardinge
On my shiny new X200 running Fedora Rawhide, I'm finding that the brightness control keys work OK, but the backlight remains stuck off after a resume. The machine is working fine but the backlight is just off; I can see the display under a bright light. Switching consoles and poking about in /sys/class/backlight/acpi_video?/ didn't help.
Quoted 1 line
Intel graphics, right?
Yes. The new, erm , X4500?
Quoted 4 lines
The DRM layer should handle full resume on modern Intel hardware, but
there's the potential for bugs. This is entirely unrelated to ACPI, though.
Quoted 5 lines
OK, that's a good clue. I poke at acpi to change the brightness, so I'd assumed that acpi would also handle turning the backlight on/off.
I'm using the rawhide rather than standard kernel, but I'd thought they were fairly similar.
I believe vanilla and rawhide kernels are _very_ different in this area.
On your config, s2ram -f -a 3 may be the right thing after all ;-).
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html