* Re: [Bugme-new] [Bug 10800] New: Hard lock up after removing forcedeth module
[not found] <bug-10800-10286@http.bugzilla.kernel.org/>
@ 2008-05-26 19:11 ` Andrew Morton
0 siblings, 0 replies; only message in thread
From: Andrew Morton @ 2008-05-26 19:11 UTC (permalink / raw)
To: t.artem; +Cc: bugme-daemon, netdev, Ayaz Abdulla
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.
^ permalink raw reply [flat|nested] only message in thread