From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: marco <marco@metm.org>, linux-acpi@vger.kernel.org
Subject: Re: suspend kills serial wacom tablet
Date: Fri, 13 Apr 2007 15:10:26 -0600 [thread overview]
Message-ID: <200704131510.26565.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <d120d5000704131216h7ccabc12uf0e649105fd7b6b0@mail.gmail.com>
On Friday 13 April 2007 13:16, Dmitry Torokhov wrote:
> On 4/13/07, Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> > On Tuesday 20 February 2007 06:52, marco wrote:
> > > I have a thinkpad X41-tablet which uses the linuxwacom serial drivers.
> > > The tablet works perfectly when the laptop first boots, but does not work
> > > at all after resuming from sleep. I posted to the linuxwacom list but
> > > think that the problem might be more general in how acpi resumes the
> > > serial ports.
> > >
> > > As suggested here:
> > > http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_on_a_ThinkPad_X41_Tablet
> > > I have added a script to resume.d which calls the setserial command:
> > > /bin/setserial /dev/ttyS0 port 0x0200 irq 5 autoconfig
> >
> > Using setserial to change port or IRQ usage is a good clue that the
> > kernel is doing something wrong. Usually it's "we KNOW that ttyS0
> > lives at 0x3f8 and IRQ 4, so we'll ignore what ACPI is telling us."
> > But it sounds like this is a tangent and not related to your current
> > problem.
> >
> > Can you post the dmesg log from a boot where the tablet works
> > correctly? That will tell us exactly what kernel you're running
> > and how the kernel detected the serial port. There've been some
> > serial port resume changes in the not-too-distant past, and I
> > don't know whether they're in the Ubuntu kernel yet.
>
> It has nothing to do with changes to serial. Wacom driver for tablets
> connected to serial ports lives completely in userspace (X) and is
> completelyunaware that the box is coming out of sleep and that
> conncted device needs to be reinitialized.
OK, that sounds good, because if it's an X issue, it's Someone Else's
Problem :-)
I'm a little concerned because Marco said that after a resume,
"cat /dev/ttyS0" caused his system to hang, and not even Ctrl-Alt-Del
worked. Can we blame that all on X?
Would stopping the X server before suspend and restarting
it after resume be a workaround?
Bjorn
next prev parent reply other threads:[~2007-04-13 21:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 13:52 suspend kills serial wacom tablet marco
2007-04-13 18:49 ` Bjorn Helgaas
2007-04-13 19:16 ` Dmitry Torokhov
2007-04-13 21:10 ` Bjorn Helgaas [this message]
2007-04-13 21:20 ` Dmitry Torokhov
2007-04-16 19:59 ` marco
2007-04-16 21:10 ` Bjorn Helgaas
2007-04-16 21:18 ` Dmitry Torokhov
2007-04-16 21:25 ` Dmitry Torokhov
2007-04-18 22:00 ` Bjorn Helgaas
2007-04-18 22:13 ` marco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200704131510.26565.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=marco@metm.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox