Latest working kernel version: tested around 2.6.25 (?) kernel Earliest failing kernel version: 2.6.28-rc3 Distribution: Debian testing Hardware Environment: ThinkPad A21m + ThinkPad Dock II Software Environment: Problem Description: devices on dock not present after docking Steps to reproduce: A) boot battery powered laptop, dock B ) boot ac powered docked laptop, undock, dock Data from testing follow.
Created attachment 18873 [details] test data - docking test data from docking -> directory description with log ./acpi_tables - dsdt and fadt table ./dmidecode - dmidecode ./dck_test - dmesg + lspci -tv output TEST A) ./dck_test/dock_battery_powered_boot - 1) boot dock battery powered and dock TEST B) ./dck_test/undock_dock ./dck_test/undock_dock/dock 3) dock ./dck_test/undock_dock/undock 2) undock ./dck_test/undock_dock/booted_docked 1) boot laptop with dock ac powered and docked
please kuill acpid, run "cat /proc/acpi/event", is there any output when dock? please attach the output of "grep . /sys/firmware/acpi/interrupts/*" both before and after dock.
(In reply to comment #2) > please kuill acpid, please kill acpid. sorry
please also make sure if this is a duplicate of bug 10805. the symptom is described here: http://bugzilla.kernel.org/show_bug.cgi?id=10805#c30
Created attachment 18887 [details] debug data Debug data are in .tar attachment Testcase 1) directory dock2 - boot battery powered undocked and dock Testcase 2) directory dock3 - boot ac powered docked, undock and (get data) dock In testcase 2 laptop freeze. Only SysRq key is working. No interrupt information.
Hi Zhang, this bug is not duplicate of bug 10805. I have similar problem in history, but cannot test this problem now. Docking not working and laptop freeze with current kernel, if i docking. More about this and initialization sequence of TI docking bridge described here: http://bugzilla.kernel.org/show_bug.cgi?id=7264#c25
do 2.6.26 or 2.6.27 work?
Ping Pavel Kysilka
reject this bug as there is no response from the bug reporter for several months. please re-open it if the problem still exists in the latest git tree.