linux-kernel - stallion driver dmesg notice

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <46633BC8.3838.43FB8257@ml.akana.de>
Date:	Sun, 03 Jun 2007 22:08:08 +0200
From:	"Ingo Korb" <ml@...na.de>
To:	linux-kernel@...r.kernel.org
Subject: stallion driver dmesg notice

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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/