lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Mon, 26 May 2008 12:11:52 -0700
From:	Andrew Morton <>
	Ayaz Abdulla <>
Subject: Re: [Bugme-new] [Bug 10800] New: Hard lock up after removing
 forcedeth module

On Mon, 26 May 2008 11:42:31 -0700 (PDT) wrote:

>            Summary: Hard lock up after removing forcedeth module
>            Product: Networking
>            Version: 2.5
>      KernelVersion:
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: high
>           Priority: P1
>          Component: Other
>         AssignedTo:
>         ReportedBy:
> 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?

To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists