From: Andrew Morton <akpm@osdl.org>
To: netdev@vger.kernel.org
Cc: "bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>,
prb@du.se
Subject: Fw: [Bugme-new] [Bug 6471] New: sky2 problem with Marvell 88E8055
Date: Mon, 1 May 2006 09:35:08 -0700 [thread overview]
Message-ID: <20060501093508.78e6f4c8.akpm@osdl.org> (raw)
Begin forwarded message:
Date: Mon, 1 May 2006 05:20:30 -0700
From: bugme-daemon@bugzilla.kernel.org
To: bugme-new@lists.osdl.org
Subject: [Bugme-new] [Bug 6471] New: sky2 problem with Marvell 88E8055
http://bugzilla.kernel.org/show_bug.cgi?id=6471
Summary: sky2 problem with Marvell 88E8055
Kernel Version: 2.6.17-rc3
Status: NEW
Severity: high
Owner: jgarzik@pobox.com
Submitter: prb@du.se
Most recent kernel where this bug did not occur: 2.6.17-rc3
Distribution: Gentoo
Hardware Environment: Fujitsu-Siemens E8110, ethernet Card Marvell 88E8055
Software Environment:
Problem Description:
Unable to connect, sometimes kernel hangs
Steps to reproduce:
boot, modprobe sky2, dhclient -d eth1
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
reply other threads:[~2006-05-01 16:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060501093508.78e6f4c8.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=prb@du.se \
/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