From: "Torsten Kaiser" <just.for.lkml@googlemail.com>
To: "Gene Heskett" <gene.heskett@gmail.com>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.29-rc1 MAJOR advisory
Date: Sun, 11 Jan 2009 22:06:37 +0100 [thread overview]
Message-ID: <64bb37e0901111306sf1efbachbeb5ad523fa17e26@mail.gmail.com> (raw)
In-Reply-To: <200901111510.30064.gene.heskett@gmail.com>
On Sun, Jan 11, 2009 at 9:10 PM, Gene Heskett <gene.heskett@gmail.com> wrote:
> I don't believe it is. MAJOR problem. I have an ASUS M2N-SLI Deluxe
> motherboard I paid about $275 for in late Sept 2008, and one attempt to boot
> the 2.6.29-rc1 I had built destroyed the MCP55 eth0 port, no power on the
> port at all now, and I've rebooted to 2.6.28, still no eth0, so I have now
> enabled in the bios and am using the 2nd & last eth1 port on this mobo.
I have also an ASUS MCP55 board, a KFN5-D.
To save the crash I reported in the "[git pull] x86 fixes" thread, I
had to boot the patch -rc1 a second time.
After saving the Oops on my second pc I rebooted my test system (the
one with the MCP55) into 2.6.28 and the boot process hung as it wanted
to mount its NFS filesystems. Trying to connect from the second system
failed, not even a ping reply.
But: Just removing the ethernet cable and immediately reconnecting it
seemed to have kicked my MCP55 ethernet port back in working order.
No fishy things in the syslog...
Jan 11 17:14:15 treogen [ 61.412278] tg3 0000:03:00.0: irq 379 for MSI/MSI-X
Jan 11 17:14:15 treogen [ 61.790728] tg3 0000:02:00.0: irq 378 for MSI/MSI-X
Jan 11 17:14:15 treogen [ 64.481794] tg3: eth1: Link is up at 1000
Mbps, full duplex.
Jan 11 17:14:15 treogen [ 64.481802] tg3: eth1: Flow control is on
for TX and on for RX.
Jan 11 17:14:21 treogen mdadm[2934]: NewArray event detected on md
device /dev/md0
Jan 11 17:14:21 treogen mdadm[2934]: NewArray event detected on md
device /dev/md1
Jan 11 17:14:26 treogen ntpdate[2945]: no server suitable for
synchronization found
Jan 11 17:14:26 treogen /etc/init.d/ntp-client[2937]: ERROR:
ntp-client failed to start
Jan 11 17:14:27 treogen rpc.statd[2972]: Version 1.1.4 Starting
Jan 11 17:14:27 treogen rpc.statd[2972]: Flags:
Jan 11 17:14:27 treogen rpc.statd[2972]: statd running as root. chown
/var/lib/nfs/sm to choose different user
Jan 11 17:14:28 treogen [ 86.282514] RPC: failed to contact local
rpcbind server (errno 5).
-> here the boot hung until I disconnected/reconnected the cable...
Jan 11 17:16:25 treogen [ 203.592837] tg3: eth1: Link is down.
Jan 11 17:16:28 treogen [ 206.255079] tg3: eth1: Link is up at 1000
Mbps, full duplex.
Jan 11 17:16:28 treogen [ 206.255086] tg3: eth1: Flow control is on
for TX and on for RX.
Jan 11 17:17:57 treogen postfix/postfix-script[3067]: starting the
Postfix mail system
Torsten
next prev parent reply other threads:[~2009-01-11 21:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 0:13 Linux 2.6.29-rc1 Linus Torvalds
2009-01-11 8:04 ` Willy Tarreau
2009-01-11 10:18 ` Paul Rolland
2009-01-11 12:07 ` David Miller
2009-01-11 12:23 ` Petr Titera
2009-01-11 13:23 ` Jaswinder Singh Rajput
2009-01-11 13:54 ` Ingo Molnar
2009-01-11 14:56 ` Petr Titera
2009-01-11 17:29 ` Gene Heskett
2009-01-11 17:55 ` Paul Rolland
2009-01-11 18:03 ` Ingo Molnar
2009-01-11 19:46 ` Paul Rolland
2009-01-11 20:10 ` Linux 2.6.29-rc1 MAJOR advisory Gene Heskett
2009-01-11 21:06 ` Torsten Kaiser [this message]
2009-01-12 2:50 ` Gene Heskett
2009-01-12 6:57 ` Torsten Kaiser
2009-01-12 7:15 ` Justin P. Mattock
2009-01-11 21:28 ` Linux 2.6.29-rc1 Maciej Rutecki
2009-01-11 21:35 ` Jesper Juhl
2009-01-11 21:38 ` Maciej Rutecki
2009-01-12 22:05 ` Simon Holm Thøgersen
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=64bb37e0901111306sf1efbachbeb5ad523fa17e26@mail.gmail.com \
--to=just.for.lkml@googlemail.com \
--cc=gene.heskett@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox