Special Function keys broken after upgrade ( Toshiba Satilite P305D, 2.6.27 kernel)

Bug #294323 reported by Ken Phillis Jr
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
New
Undecided
Unassigned

Bug Description

Special function keys broken in transition from Ubuntu 8.04 to Ubuntu 8.10

Kernel version 2.6.24-21.3 had the special keys working..

FN + Esc- Mute Speakers
FN + F1 - Lock screen ( keycode equivelent of SUPER+L )
FN + F2 - change PowerState ( not working/no visible change )
FN + F3 - Suspend - works
FN + F4 - Hybernate - Works
FN + F5 - toggle internal/external Video - not tested.
FN + F6 - decrease brightness - works
FN + F7 - Increase Brightness - works
FN + F8 - Toggle Wireless - not working.
FN + F8 - Toggle Touchpad - Not working
FN + Space - Toggle Desktop Zoom - not working.

Kernel version 2.6.27-* breaks the following keys...
FN + F6 - Broken, and does not work.
FN + F7 - Broken, and does not work.

These are linked to irq # 9 being disabled, which provides keyboard services.

and the dmesg log holds the following trace: ( in 2.6.27-10.20-generic )
[ 0.000000] ACPI: PM-Timer IO Port: 0x8008
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 2, version 33, address 0xfec00000, GSI 0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 low level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ2 used by override.
[ 0.000000] ACPI: IRQ9 used by override.

[ 1.638843] checking if image is initramfs...<3>irq 9: nobody cared (try boot
ing with the "irqpoll" option)
[ 2.639316] Pid: 1, comm: swapper Not tainted 2.6.27-10-generic #1
[ 2.639320] [<c037c9f6>] ? printk+0x1d/0x1f
[ 2.639329] [<c01781ec>] __report_bad_irq+0x2c/0xa0
[ 2.639335] [<c0178374>] note_interrupt+0x114/0x140
[ 2.639339] [<c01770e1>] ? handle_IRQ_event+0x41/0x80
[ 2.639343] [<c01789c3>] handle_fasteoi_irq+0xb3/0xe0
[ 2.639347] [<c0106c15>] do_IRQ+0x45/0x80
[ 2.639352] [<c04af6bd>] ? huft_build+0x2eb/0x581
[ 2.639357] [<c0105003>] common_interrupt+0x23/0x30
[ 2.639360] [<c04af21f>] ? inflate_codes+0x464/0x4e1
[ 2.639365] [<c04afef9>] inflate_dynamic+0x5a6/0x5c5
[ 2.639368] [<c01789ab>] ? handle_fasteoi_irq+0x9b/0xe0
[ 2.639373] [<c04b01b8>] inflate_block+0x145/0x25f
[ 2.639376] [<c04b0587>] gunzip+0x2b5/0x527
[ 2.639380] [<c04b0a39>] unpack_to_rootfs+0x240/0x282
[ 2.639383] [<c04b11f2>] ? populate_rootfs+0x0/0xf3
[ 2.639387] [<c04b11f2>] ? populate_rootfs+0x0/0xf3
[ 2.639391] [<c04b1255>] populate_rootfs+0x63/0xf3
[ 2.639394] [<c0101120>] _stext+0x30/0x160
[ 2.639397] [<c01378c4>] ? irq_exit+0x44/0x90
[ 2.639401] [<c0106c1a>] ? do_IRQ+0x4a/0x80
[ 2.639405] [<c0105003>] ? common_interrupt+0x23/0x30
[ 2.639409] [<c04ab38d>] kernel_init+0xa9/0x100
[ 2.639413] [<c04ab2e4>] ? kernel_init+0x0/0x100
[ 2.639416] [<c0105297>] kernel_thread_helper+0x7/0x10
[ 2.639420] =======================
[ 2.639422] handlers:
[ 2.639459] [<c02777f8>] (acpi_irq+0x0/0x28)
[ 2.639560] Disabling IRQ #9

also, if i boot with the old kernel, the unresponsive keys start responding again.

Revision history for this message
Ken Phillis Jr (kphillisjr) wrote :
Revision history for this message
Ken Phillis Jr (kphillisjr) wrote :

just attached both dmesg logs for comparison between ubuntu 8.04's proposed kernel (2.6.24-21-generic) and ubuntu 8.10's kernel ( 2.6.27-7-generic)

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

Hi Ken,

This looks to be a duplicate of bug 261318 so I am marking it as such for now. Bug 261318 should be getting fixed as a post Intrepid Stable Release Update. Please continue to monitor this issue using bug 261318. Thanks.

Revision history for this message
Ken Phillis Jr (kphillisjr) wrote :

I did some checking around... and also looked at my system information...

first off, i don't have tlsup loaded in xorg or in the system at all... here's what i got after testing...

kphillisjr@kphillis-t64x2:~$ cat /var/log/Xorg.0.log | grep tls
kphillisjr@kphillis-t64x2:~$ cat /var/log/Xorg.0.log | grep evdev
(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
(**) Option "xkb_rules" "evdev"
(**) AT Translated Set 2 keyboard: xkb_rules: "evdev"
(**) Option "xkb_rules" "evdev"
(**) Video Bus: xkb_rules: "evdev"
kphillisjr@kphillis-t64x2:~$ lsmod | grep tosh

kphillisjr@kphillis-t64x2:~$ cat /boot/config-2.6.27-7-generic | grep TOSHIBA
# CONFIG_ACPI_TOSHIBA is not set
# CONFIG_TOSHIBA is not set
CONFIG_TOSHIBA_FIR=m
CONFIG_YENTA_TOSHIBA=y

kphillisjr@kphillis-t64x2:~$ uname -a
Linux kphillis-t64x2 2.6.27-8-generic #1 SMP Thu Nov 6 17:33:54 UTC 2008 i686 GNU/Linux
kphillisjr@kphillis-t64x2:~$ cat /boot/config-2.6.27-8-generic | grep TOSHIBA
# CONFIG_ACPI_TOSHIBA is not set
# CONFIG_TOSHIBA is not set
CONFIG_TOSHIBA_FIR=m
CONFIG_YENTA_TOSHIBA=y

and the kicker... the special function keys and suspend work after i modify the kernel boot flags..

acpi=noirq apic=debug irqpoll

it's worth nothing that these flags fix the issue on 2.6.27-7-generic and 2.6.27-8-generic.

Revision history for this message
Ken Phillis Jr (kphillisjr) wrote :

I'll go ahead and reiterate after the tests what the issues are... the main issue is as following things are broken in the transition from version 2.6.24-21 to 2.6.27-7. ( this is over the past 3 hours )

1) suspend via the special function key and Gnome Power Management applet require me to close the lid right after initializing the command, while suspend via the fast user applet is not affected.
2) the special function keys for brightness don't work ( irq # 9 gets disabled at boot, and requires acpi=noirq and irqpoll kernel parameters to fix )
3) it appears that the battery status is not properly passed to gnome power management applet until after suspend. ( fixed with the fix for brightness keys )

I also confirmed that 2.6.24-21 did not have any toshiba specific changes enabled.
1) lsmod | grep toshiba returns nothing.
2) cat /var/log/Xorg.0.log | grep tlsup also returns nothing.
3) cat /boot/config-$(uname -r) | grep TOSH is identical to 2.6.24-21

description: updated
Revision history for this message
Ken Phillis Jr (kphillisjr) wrote :

The bugs with the special function keys got fixed with the update to the kernel 2.6.28 that andy did, however the suspend does not work at all.

Revision history for this message
Ken Phillis Jr (kphillisjr) wrote :

Upgraded to jaunty, issue still exists... here's the dmesg output on it.

Revision history for this message
Ken Phillis Jr (kphillisjr) wrote :

Another kernel update, this time with the ubuntu 8.04 packages, and just enough deps fixed to install kernel... here's the dmesg report... error changed places on this one.

[ 1.047009] checking if image is initramfs...<3>irq 9: nobody cared (try booting with the "irqpoll" option)
[ 2.073262] Pid: 1, comm: swapper Not tainted 2.6.29-020629rc7-generic #020629rc7
[ 2.073264] Call Trace:
[ 2.073273] [<c01803a7>] __report_bad_irq+0x27/0x90
[ 2.073277] [<c0180524>] note_interrupt+0xe4/0x120
[ 2.073280] [<c017f215>] ? handle_IRQ_event+0x35/0x70
[ 2.073284] [<c0180c45>] handle_fasteoi_irq+0x85/0xe0
[ 2.073288] [<c01050f6>] do_IRQ+0x46/0x90
[ 2.073291] [<c0103b27>] common_interrupt+0x27/0x30
[ 2.073295] [<c072fe32>] ? inflate_codes+0x492/0x4f0
[ 2.073299] [<c0730a13>] inflate_dynamic+0x583/0x5b0
[ 2.073303] [<c07314f0>] inflate_block+0xa0/0xf0
[ 2.073306] [<c0731581>] inflate+0x41/0x90
[ 2.073309] [<c07317e2>] gunzip+0x212/0x420
[ 2.073312] [<c072f608>] ? flush_buffer+0x28/0x70
[ 2.073315] [<c0731b95>] unpack_to_rootfs+0x1a5/0x210
[ 2.073318] [<c0731c00>] ? populate_rootfs+0x0/0x100
[ 2.073322] [<c0731c5b>] populate_rootfs+0x5b/0x100
[ 2.073326] [<c0761e61>] ? inet_init+0x1/0x1e0
[ 2.073329] [<c010111b>] _stext+0x2b/0x160
[ 2.073333] [<c013ff0f>] ? irq_exit+0x3f/0x80
[ 2.073336] [<c01050fb>] ? do_IRQ+0x4b/0x90
[ 2.073339] [<c0103b27>] ? common_interrupt+0x27/0x30
[ 2.073342] [<c075dbe0>] ? acpi_wmi_init+0x0/0x50
[ 2.073345] [<c072b37c>] do_initcalls+0x1c/0x30
[ 2.073348] [<c072ba90>] ? kernel_init+0x0/0xa0
[ 2.073351] [<c072b3ac>] do_basic_setup+0x1c/0x30
[ 2.073354] [<c072baea>] kernel_init+0x5a/0xa0
[ 2.073357] [<c0103da7>] kernel_thread_helper+0x7/0x10
[ 2.073359] handlers:
[ 2.073397] [<c02e8dbe>] (acpi_irq+0x0/0x20)
[ 2.073497] Disabling IRQ #9

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.