From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Jan Gukelberger <g.u.g.i@gmx.de>
Cc: netdev@vger.kernel.org
Subject: Re: BUG: skge ethernet breakage (PCI: Unable to reserve mem region)
Date: Tue, 11 Sep 2007 10:21:10 +0200 [thread overview]
Message-ID: <20070911102110.1f32fa7e@oldman> (raw)
In-Reply-To: <1189183355.3784.11.camel@localhost>
On Fri, 07 Sep 2007 18:42:35 +0200
Jan Gukelberger <g.u.g.i@gmx.de> wrote:
> Hi,
>
> I originally reported this bug to the Debian BTS:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=441232
> There I was told to talk directly to upstream.
>
> I am pasting the original bug report below. The referenced text files
> can be found at the mentioned BTS URL.
> Additionally, I have just tried Linux 2.6.23-rc5 and am attaching the
> corresponding dmesg output.
>
> Thanks in advance for any help,
> Jan
>
>
> With recent kernels my on-board network adapter does not work any more.
> This is a Marvell Gigabit Ethernet Controller on an Asus P5B-V
> mainboard.
>
> This is the same bug as #428452 reported earlier against
> linux-image-2.6.21-1-amd64. (Sorry for the duplicate, I didn't know how
> to extend the old report to newer kernel versions.)
> In fact, the network adapter hasn't been working since then, i.e. the
> last working kernel image was 2.6.20-1-amd64 (which I am using now). The
> following images 2.6.2[12]-[12]-amd64 have all exposed the same problem.
>
> The key problem seem to be the following lines in dmesg:
> ------------------------------------------------------------------------
> ACPI: PCI Interrupt 0000:04:04.0[A] -> GSI 19 (level, low) -> IRQ 19
> PCI: Unable to reserve mem region #1:4000@ff9f8000 for device 0000:04:04.0
> skge 0000:04:04.0: cannot obtain PCI resources
> ACPI: PCI interrupt for device 0000:04:04.0 disabled
> skge: probe of 0000:04:04.0 failed with error -16
> ------------------------------------------------------------------------
>
> I'm attaching full 'dmesg' output from working (2.6.20-1) and broken
> (2.6.22-2) kernel versions as well as the output of 'lspci -vvv' on the
> most recent kernel.
>
> If you need any other information or I can try something please let me
> know.
There is some kind of device conflict, please provide lspci -vvvxx output.
next prev parent reply other threads:[~2007-09-11 8:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 16:42 BUG: skge ethernet breakage (PCI: Unable to reserve mem region) Jan Gukelberger
2007-09-11 8:21 ` Stephen Hemminger [this message]
2007-09-11 10:58 ` Jan Gukelberger
2007-09-11 12:37 ` Stephen Hemminger
2007-09-11 13:39 ` Jan Gukelberger
2007-09-19 20:57 ` Jan Gukelberger
2007-11-21 22:31 ` Stephen Hemminger
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=20070911102110.1f32fa7e@oldman \
--to=shemminger@linux-foundation.org \
--cc=g.u.g.i@gmx.de \
--cc=netdev@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.