[Bugme-janitors] [Bug 9487] New: Serial port disappears after
Suspend on Toshiba R25
bugme-daemon at bugzilla.kernel.org
bugme-daemon at bugzilla.kernel.org
Sat Dec 1 18:27:39 PST 2007
http://bugzilla.kernel.org/show_bug.cgi?id=9487
Summary: Serial port disappears after Suspend on Toshiba R25
Product: Power Management
Version: 2.5
KernelVersion: v2.6.21-rc3 (362ea087db9d99bb0cf79479544dfafa9e18c300)
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Hibernation/Suspend
AssignedTo: power-management_other at kernel-bugs.osdl.org
ReportedBy: ThJaeger at gmail.com
Most recent kernel where this bug did not occur: v2.6.21-rc3
(908e0a8a265fe8057604a9a30aec3f0be7bb5ebb)
Distribution: Ubuntu 7.10
Hardware Environment: Toshiba Satellite R25 Tablet PC (x86)
Software Environment: Linux tthomas 2.6.21-rc3 #13 SMP Sat Dec 1 20:38:13 EST
2007 i686 GNU/Linux
Problem Description:
Recent kernel versions fail to wake up the serial port after both Suspend to
RAM and Suspend to Disk, which causes the tablet pen to be unusable. Trying to
access the serial port result in a "ttyS0: LSR safety check engaged!" error
message, and operation cannot be restored via "sudo setserial /dev/ttyS0 uart
16550A port 0x0338 irq 4".
Using git bisect, I identified the kernel version where this problem first
appeared, the offending patch is:
Author: Michael Karcher <bugzilla-kernel at mkarcher.dialup.fu-berlin.de>
2007-03-08 23:29:29
Committer: Len Brown <len.brown at intel.com> 2007-03-08 23:29:29
Parent: 908e0a8a265fe8057604a9a30aec3f0be7bb5ebb ([PATCH] ecryptfs: nested
locking annotation)
Branches: remotes/origin/master, master, bisect
Follows: v2.6.21-rc3
Precedes: v2.6.21-rc4
ACPI: fix parallel port IRQ after resume from S3
The PNPACPI resource flags were broken.
This would apply to re-enabling a device any-time after boot,
not just after resume from S3.
http://bugzilla.kernel.org/show_bug.cgi?id=6316
Acked-by: Shaohua Li <shaohua.li at intel.com>
Signed-off-by: Len Brown <len.brown at intel.com>
I'll attach the output of dmesg and my kernel configuration. This uses the
first kernel version where the bug occurs; if you prefer, I can repeat the
process on the latest kernel.
Thank you.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the Bugme-janitors
mailing list