public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Karol Kozimor <sziwan@hell.org.pl>,
	linux-kernel@vger.kernel.org, rmk@arm.linux.org.uk
Subject: Re: kernel BUG at drivers/serial/8250.c:1256!
Date: Wed, 2 Mar 2005 22:33:19 +0100	[thread overview]
Message-ID: <20050302213319.GA11320@isilmar.linta.de> (raw)
In-Reply-To: <20050301233720.B17470@flint.arm.linux.org.uk>

On Tue, Mar 01, 2005 at 11:37:20PM +0000, Russell King wrote:
> On Wed, Mar 02, 2005 at 12:09:46AM +0100, Karol Kozimor wrote:
> > I've finally got around to test latest kernels and managed to find a bug in 
> > the serial subsystem, which happens during suspend.
> 
> Yes, serial_cs is claiming that we don't have a device associated with
> the port, so we're treating it as a legacy port.  However, serial_cs is
> implementing the suspend/resume methods.  This is wrong, since that
> means the port will be suspended twice, and hence causes this bug.
> 
> serial_cs needs to register the ports along with the PCMCIA device with
> which the port belongs to.  This will stop it being treated as a legacy
> serial port.
> 
> Unfortunately, it's too late tonight for me to dig into PCMCIA to work
> out how we get at the device structure - I can't find any examples off
> hand either.

For the time being:

{
	client_handle_t handle = ...
	struct device *dev;

	dev = &handle_to_dev(handle);
}


	Dominik

  reply	other threads:[~2005-03-02 21:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-01 23:09 kernel BUG at drivers/serial/8250.c:1256! Karol Kozimor
2005-03-01 23:37 ` Russell King
2005-03-02 21:33   ` Dominik Brodowski [this message]
2005-03-10 22:43   ` Russell King
2005-03-10 23:28     ` Karol Kozimor

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=20050302213319.GA11320@isilmar.linta.de \
    --to=linux@dominikbrodowski.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=sziwan@hell.org.pl \
    /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