From: Roberto Oppedisano <roppedisano.oppedisano@gmail.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Pierre Ossman <drzeus-list@drzeus.cx>,
LKML <linux-kernel@vger.kernel.org>,
jgarzik@pobox.com
Subject: Re: 2.6.12 breaks 8139cp
Date: Thu, 23 Jun 2005 23:07:21 +0200 [thread overview]
Message-ID: <42BB2489.3060906@gmail.com> (raw)
In-Reply-To: <200506231200.43671.bjorn.helgaas@hp.com>
[-- Attachment #1: Type: text/plain, Size: 602 bytes --]
Bjorn Helgaas wrote:
>>0000:02:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80)
>>0000:02:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20)
>>
>>
>
>You have a VIA device with dev/function == 0, so 2.6.11 will do the
>VIA IRQ fixup for all devices. 2.6.12 will do it only for VIA
>devices. Can you try the attached patch for debugging purposes?
>
Hi!
I applied your patch to a vanilla 2.6.12.1 kernel and the card is still
not working.
Attached dmesg with and without pci=routeirq.
Kind regards,
Roberto Oppedisano
[-- Attachment #2: 2.6.12.1-routeirq.gz --]
[-- Type: application/gzip, Size: 5053 bytes --]
[-- Attachment #3: 2.6.12.1.gz --]
[-- Type: application/gzip, Size: 4999 bytes --]
next prev parent reply other threads:[~2005-06-23 21:12 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-22 21:03 2.6.12 breaks 8139cp Pierre Ossman
2005-06-22 21:34 ` Bjorn Helgaas
2005-06-23 7:50 ` Pierre Ossman
2005-06-23 12:59 ` Felipe W Damasio
2005-06-23 17:43 ` Bjorn Helgaas
2005-06-23 22:14 ` Pierre Ossman
2005-06-25 2:03 ` Ed Sweetman
2005-06-25 2:18 ` Ed Sweetman
2005-06-25 2:32 ` Ed Sweetman
2005-06-25 3:15 ` Jeff Garzik
2005-06-25 10:34 ` Pierre Ossman
2005-06-26 13:31 ` Ed Sweetman
2005-06-28 6:28 ` Pierre Ossman
2005-06-28 12:32 ` Pierre Ossman
2005-06-28 14:09 ` Kylene Jo Hall
2005-06-28 14:40 ` Pierre Ossman
2005-06-28 15:08 ` Kylene Jo Hall
2005-06-28 16:51 ` Pierre Ossman
2005-06-28 17:03 ` Kylene Jo Hall
2005-06-29 7:03 ` Pierre Ossman
2005-06-28 17:23 ` Chris Wright
2005-06-28 20:29 ` 2.6.12 breaks 8139cp [PATCH 1 of 2] Kylene Jo Hall
2005-06-28 20:34 ` Chris Wright
2005-06-28 22:10 ` Kylene Jo Hall
2005-06-29 8:22 ` Pierre Ossman
2005-06-29 14:32 ` Kylene Jo Hall
[not found] ` <20050705153512.GJ9046@shell0.pdx.osdl.net>
2005-07-07 20:01 ` Kylene Jo Hall
2005-07-08 6:14 ` Chris Wright
2005-06-28 20:30 ` 2.6.12 breaks 8139cp [PATCH 2 " Kylene Jo Hall
2005-06-23 17:17 ` 2.6.12 breaks 8139cp Roberto Oppedisano
2005-06-23 18:00 ` Bjorn Helgaas
2005-06-23 20:38 ` Ed Sweetman
2005-06-23 20:55 ` Bjorn Helgaas
2005-06-23 21:14 ` Ed Sweetman
2005-06-23 21:07 ` Roberto Oppedisano [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-26 13:46 Nick Warne
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=42BB2489.3060906@gmail.com \
--to=roppedisano.oppedisano@gmail.com \
--cc=bjorn.helgaas@hp.com \
--cc=drzeus-list@drzeus.cx \
--cc=jgarzik@pobox.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.