From: Corentin Labbe <clabbe.montjoie@gmail.com>
To: linux@dominikbrodowski.net, arnd@arndb.de, linux-kernel@vger.kernel.org
Subject: pcmcia: ti: regression cannot get IRQ
Date: Sun, 1 Jan 2023 19:10:05 +0100 [thread overview]
Message-ID: <Y7HMfUTjuWC+Zudk@Red> (raw)
Hello
I was trying to boot again my old compaq armada 7400 laptop and the network card is unusable.
Last known working kernel is 4.16.18.
First known bad kernel is 4.17.19
The interesting log is:
[ 3.503348] yenta_cardbus 0000:00:0c.0: ISA IRQ mask 0x0698, PCI irq 0
[ 3.503442] yenta_cardbus 0000:00:0c.0: Socket status: 30000006
[ 3.505250] yenta_cardbus 0000:00:0c.1: CardBus bridge found [0e11:b048]
[ 3.505370] yenta_cardbus 0000:00:0c.1: adjusting diagnostic: 60 -> 00
[ 3.505457] yenta_cardbus 0000:00:0c.1: Using INTVAL to route CSC interrupts to PCI
[ 3.505554] yenta_cardbus 0000:00:0c.1: Routing CardBus interrupts to ISA
[ 3.505556] yenta_cardbus 0000:00:0c.1: TI: mfunc 0x00000000, devctl 0x64
[ 3.505556] yenta_cardbus 0000:00:0c.1: TI: no PCI interrupts. Fish. Please report.
[ 3.505556] yenta_cardbus 0000:00:0c.1: no PCI IRQ, CardBus support disabled for this socket.
[ 3.505556] yenta_cardbus 0000:00:0c.1: check your BIOS CardBus, BIOS IRQ or ACPI settings.
[ 3.632323] yenta_cardbus 0000:00:0c.1: ISA IRQ mask 0x0698, PCI irq 0
[ 3.632416] yenta_cardbus 0000:00:0c.1: Socket status: 30000020
Full 4.16.18 log is availlable at: http://kernel.montjoie.ovh/zoo/armada/dmesg-4.16.18.txt
Since 4.17 (and 4.18) is stuck sarting init, I have log for 5.0.29
Full 5.0.29 log is availlable at: http://kernel.montjoie.ovh/zoo/armada/dmesg-5.0.21.txt
Regards
next reply other threads:[~2023-01-01 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-01 18:10 Corentin Labbe [this message]
2023-01-02 8:30 ` pcmcia: ti: regression cannot get IRQ Arnd Bergmann
2023-01-02 15:15 ` Corentin Labbe
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=Y7HMfUTjuWC+Zudk@Red \
--to=clabbe.montjoie@gmail.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
/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