All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@mail.ru>
To: e1000-devel@lists.soutceforge.net, "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [2.6.29-rc2 regression] e100: netconsole not functional because of missing firmware
Date: Sat, 17 Jan 2009 19:08:25 +0300	[thread overview]
Message-ID: <200901171908.28533.arvidjaar@mail.ru> (raw)

[-- Attachment #1: Type: text/plain, Size: 924 bytes --]

[    1.958127] e100 0000:00:0a.0: PCI INT A -> Link[LNKD] -> GSI 11 
(level, low)
 -> IRQ 11
[    1.986079] e100 0000:00:0a.0: PME# disabled
[    1.987930] e100: eth0: e100_probe: addr 0xf7efd000, irq 11, MAC addr 
00:00:39:d7:14:a1
[    1.989358] netconsole: local port 6665
[    1.989848] netconsole: local IP 10.0.0.1
[    1.990427] netconsole: interface eth0
[    1.990895] netconsole: remote port 6666
[    1.991382] netconsole: remote IP 10.0.0.2
[    1.991890] netconsole: remote ethernet address 00:17:42:21:27:e4
[    1.992680] netconsole: device eth0 not up yet, forcing it
[    2.008509] e100: eth0: e100_request_firmware: Failed to load 
firmware "e100/d101m_ucode.bin": -22
[    2.010461] netconsole: failed to open eth0
[    2.010996] netconsole: cleaning up

This has been working all the time without requiring any external 
firmware to be present. Why it suddenly refuses to work now?


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2009-01-17 16:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-17 16:08 Andrey Borzenkov [this message]
2009-01-19 18:30 ` [2.6.29-rc2 regression] e100: netconsole not functional because of missing firmware Jesse Brandeburg
2009-01-19 18:30   ` Jesse Brandeburg
2009-01-19 18:43   ` Andrey Borzenkov
2009-01-19 19:20   ` Rafael J. Wysocki

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=200901171908.28533.arvidjaar@mail.ru \
    --to=arvidjaar@mail.ru \
    --cc=e1000-devel@lists.soutceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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.