From: Andrew Morton <akpm@linux-foundation.org>
To: t.artem@mailcity.com
Cc: bugme-daemon@bugzilla.kernel.org, netdev@vger.kernel.org,
Ayaz Abdulla <aabdulla@nvidia.com>
Subject: Re: [Bugme-new] [Bug 10800] New: Hard lock up after removing forcedeth module
Date: Mon, 26 May 2008 12:11:52 -0700 [thread overview]
Message-ID: <20080526121152.1f9ab044.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-10800-10286@http.bugzilla.kernel.org/>
On Mon, 26 May 2008 11:42:31 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=10800
>
> Summary: Hard lock up after removing forcedeth module
> Product: Networking
> Version: 2.5
> KernelVersion: 2.6.25.4
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: high
> Priority: P1
> Component: Other
> AssignedTo: acme@ghostprotocols.net
> ReportedBy: t.artem@mailcity.com
>
>
> Latest working kernel version: haven't tested
> Earliest failing kernel version: haven't tested
> Distribution: Fedora 8
> Hardware Environment: 00:07.0 Bridge: nVidia Corporation MCP61 Ethernet (rev
> a2), nVidia Corporation MCP61 based mobo
> Software Environment: n/a
> Problem Description: rmmod forcedeth causes instant hard lock-up
>
> Steps to reproduce: boot the PC, put it to the software suspend, wake it up, #
> rmmod forcedeth.
>
Is the suspend/resume operation a required step to make this occur? I
assume so.
Do you know if this is a regression? In other words, did any earlier
kernel perform these steps without crashing the machine?
Thanks.
parent reply other threads:[~2008-05-26 19:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-10800-10286@http.bugzilla.kernel.org/>]
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=20080526121152.1f9ab044.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aabdulla@nvidia.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=t.artem@mailcity.com \
/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;
as well as URLs for NNTP newsgroup(s).