From: "Ingo Korb" <ml@akana.de>
To: linux-kernel@vger.kernel.org
Subject: stallion driver dmesg notice
Date: Sun, 03 Jun 2007 22:08:08 +0200 [thread overview]
Message-ID: <46633BC8.3838.43FB8257@ml.akana.de> (raw)
Hi!
The stallion driver in 2.6.21.3 put this little notice in my dmesg:
=== Cut ===
Stallion Multiport Serial Driver: version 5.6.0
stallion 0000:00:0b.0: please, report this to LKML: 100b/d001/ffffff
ACPI: PCI Interrupt 0000:00:0b.0[A] -> GSI 19 (level, low) -> IRQ 17
stallion: probe of 0000:00:0b.0 failed with error -16
=== Cut ===
The card is a EC8/32-PCI with a single connected panel. It used to work
well with 2.4, mostly well with a patched 2.6.8.1, really bad
(unstable, lost characters) with 2.6.11(?) and doesn't work at all with
2.6.21.3.
Should I test it with an EC8/64-PCI? The /32 (ab)uses an IDE controller
chip as PCI interface, the /64 uses a PLX PCI9050.
lspci -vv for the EC8/32:
=== Cut ===
00:0b.0 Class ffff: National Semiconductor Corporation 87410 IDE (rev
ff) (prog-if ff)
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 17
Region 0: I/O ports at d100 [size=8]
Region 1: I/O ports at d200 [size=4]
Region 2: I/O ports at d300 [size=8]
Region 3: I/O ports at d400 [size=4]
=== Cut ===
-ik
next reply other threads:[~2007-06-03 20:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-03 20:08 Ingo Korb [this message]
2007-06-03 21:14 ` Jiri Slaby
2007-06-03 22:13 ` [PATCH 1/1] Char: stallion, don't fail with less than max panels, " Jiri Slaby
[not found] ` <466362EA.6369.44946011@ingo.akana.de>
2007-06-04 8:44 ` Jiri Slaby
2007-06-04 10:19 ` Ingo Korb
2007-06-04 20:38 ` Ingo Korb
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=46633BC8.3838.43FB8257@ml.akana.de \
--to=ml@akana.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®