From: Ben Greear <greearb@candelatech.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
rmk@arm.linux.org.uk, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] NULL pointer dereference in uart_write_room().
Date: Tue, 06 May 2008 09:03:09 -0700 [thread overview]
Message-ID: <4820813D.6050608@candelatech.com> (raw)
In-Reply-To: <20080505113055.5284052e@core>
Alan Cox wrote:
>> (5) uart_remove_one_port() is called by serial8250_register_port()
>> since ttyS0 is already in use but it is requested to be once removed.
>>
>
> That means 8250_pnp is taking over and then trying to delete the console,
> so its breakage in the serial layer glue. Perhaps Russell has some ideas
> as its hard to tell what he intended to happen originally.
>
For what it's worth, I've been seeing this problem since about 2.6.23 on
several
different systems, and will be happy to test patches. The work-around
of changing
the .config file will be fine in the meantime, it seems.
Thanks,
Ben
> Alan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2008-05-06 16:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <261636618@web.de>
[not found] ` <200805022300.GIB30385.FJOVHQSMFtOOFL@I-love.SAKURA.ne.jp>
2008-05-04 8:16 ` [BUG] NULL pointer dereference in uart_write_room() Tetsuo Handa
2008-05-05 10:30 ` Alan Cox
2008-05-06 16:03 ` Ben Greear [this message]
2008-05-06 21:23 ` Russell King
2008-05-07 15:23 ` Tetsuo Handa
2008-05-07 19:19 ` Russell King
2008-05-02 5:35 Tetsuo Handa
-- strict thread matches above, loose matches on Subject: below --
2008-04-22 7:49 Tetsuo Handa
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=4820813D.6050608@candelatech.com \
--to=greearb@candelatech.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=rmk@arm.linux.org.uk \
/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