From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: "Russell King" <rmk+lkml@arm.linux.org.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0 modules, hotplug, PCMCIA
Date: Mon, 29 Dec 2003 18:13:25 +0900 [thread overview]
Message-ID: <00c001c3cdec$10c3f700$2fee4ca5@DIAMONDLX60> (raw)
I replied to Russell King:
> > > 5. However, file /etc/pcmcia/serial.opts is still getting ignored under
> > > 2.6.0.
> > > The modem is detected as containing a TI 16750 UART, and whatever
> > > the serial driver does then, it causes the modem to hang up. The serial
> > > driver in 2.4.20 defaults to the same thing but 2.4.20 reads file
> > > /etc/pcmcia/serial.opts, obeys the line SERIAL_OPTS="uart 16550A", and lets
> > > the modem operate at 33% of its rated speed instead of hanging up.
> >
> > "hang up"? Do you mean "on-hook" or do you mean "stop working"? Is
> > there anything in /var/log/messages about this
>
> I think both. "on-hook" happens immediately, and the only way to try again
> is to eject the card and reinsert it.
>
> > On my RH systems, cardmgr logs a fair amount to the system messages log,
>
> As far as I can tell, in SuSE 8.2 with SuSE's default version of the 2.4.20
> kernel, this isn't happening, but in 2.6.0 it is happening even when I
> didn't ask for it.
Sorry for misstating that. It's actually the other way around. 2.6.0 is
not giving me a ton of unrequested log syslog messages, but neither is it
giving any reason for the modem to stop working. It only observes that the
modem hung up with no visible reason, and it doesn't even notice that the
modem cannot be retried until ejection and reinsertion. In both 2.4.20 and
2.6.0, the serial_cs driver detects the UART as a TI 16750, which either
means that the UART really is a 16750 but the chip and the driver don't
agree on how the chip should be handled, or that the UART is a 16550A (or
something else) being misdetected.
SuSE's 2.4.20 PCMCIA configuration is writing around 6,000 syslog messages
every time I boot it. I don't think you want that, especially when it's
from 2.4.20 which is obeying my addition in file /etc/pcmcia/serial.opts
saying SERIAL_OPTS="uart 16550A"
next reply other threads:[~2003-12-29 9:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 9:13 Norman Diamond [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-28 2:33 2.6.0 modules, hotplug, PCMCIA Norman Diamond
2003-12-28 11:06 ` Russell King
2003-12-29 2:03 ` Norman Diamond
2003-12-30 2:28 ` Rusty Russell
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='00c001c3cdec$10c3f700$2fee4ca5@DIAMONDLX60' \
--to=ndiamond@wta.att.ne.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@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