From: maximilian attems <debian@sternwelten.at>
To: Jefferson Cowart <jeff@cowart.net>
Cc: 270376@bugs.debian.org, linux-pcmcia@lists.infradead.org,
rmk@arm.linux.org.uk, daniel.ritz@gmx.ch,
linux-kernel@vger.kernel.org
Subject: Re: Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8
Date: Fri, 1 Apr 2005 11:43:44 +0200 [thread overview]
Message-ID: <20050401094344.GA2755@sputnik.stro.at> (raw)
In-Reply-To: <20050331101612.B3B5B1012F@P450.internal.cowart.net>
cc'ing the pcmcia maintainer and the author of
the patch for interrupt routing for TI bridges.
concerning a bug report about non working irq routing since 2.6.6-rc1
up until 2.6.12-rc1-mm3
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=270376
(lspci, dmesg)
hope you can help to resolve that issue.
i volountary test build kernels for bug reporter with proposed patches.
On Thu, 31 Mar 2005, Jefferson Cowart wrote:
> (For reference my primary card is a 3C574. My secondary is a 3C589.)
..
> ========
>
> (I put that card into a Windows XP laptop and it worked fine there so the
> card itself is fine.)
>
> Now I'm trying to see if I have these same problems on 2.5.5
>
> First, Booting with the secondary card plugged in had the same failure as
> above.
> Next booting with the primary plugged in. It worked (as expected). Then I
> was able to pull and re-insert the card without problems. However pulling
> the primary and inserting the secondary killed the network (as expected).
>
> Now I'm going back to 2.4.27 to figure out if my secondary card will work
> there. It failed. I got a hard lock when I inserted the card. (Reboot button
> needed.)
>
> I'm 99.9% certain that my testing of 2.6.6-2.6.10 was using my primary nic,
> but I'm booting 2.6.10 now to be sure. (I know the kernels I tested for you
> yesterday used my primary nic.) As expected no networking.
>
> It looks like we may have 2 different bugs here: one in the yenta_socket
> driver starting somewhere after 2.6.5-bk1 and before 2.6.6-rc1 and one in
> the 3c589 driver in I don't know what versions. (I seem to remember that
> 2.4.18 worked, but I'm not sure. If you want me to try that nic under and
> older kernel let me know, however I think fixing the first bug is more
> important.) If you need any further log info let me know.
indeed there is a change in the irq handling in the yenta code.
it went in after 2.6.5-bk2 and is in 2.6.6-rc1.
in the context could you send please the ouput of a pre
2.6.6-rc1 kernel on your box:
cat /proc/interrupts
regarding your other pcmcia i don't know if it's supported.
thanks for your feedback.
--
maks
parent reply other threads:[~2005-04-01 9:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20050331101612.B3B5B1012F@P450.internal.cowart.net>]
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=20050401094344.GA2755@sputnik.stro.at \
--to=debian@sternwelten.at \
--cc=270376@bugs.debian.org \
--cc=daniel.ritz@gmx.ch \
--cc=jeff@cowart.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--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
all inboxes | Powered by JetHome®