Bug 10800
| Summary: | Hard lock up after removing forcedeth module | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Artem S. Tashkinov (aros) |
| Component: | Network | Assignee: | Jeff Garzik (jgarzik) |
| Status: | CLOSED DUPLICATE | ||
| Severity: | high | CC: | aabdulla, bunk, rjw |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.26 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Bug Depends on: | |||
| Bug Blocks: | 7216 | ||
|
Description
Artem S. Tashkinov
2008-05-26 11:42:30 UTC
I'm using vanilla kernel. Reply-To: akpm@linux-foundation.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. > Is the suspend/resume operation a required step to make this occur? Absolutely. Without suspend I can modprobe; rmmod great many times without any problems. > Do you know if this is a regression? In other words, did any earlier kernel perform these steps without crashing the machine? I have never tried to do that before, so no I don't know if it's a regression. A few notes: a hard lock up happens no matter if X server has been started or not; it happens without any proprietary modules loaded (so the kernel is not tainted); after '# rmmod forcedeth' in the first text VT - I get no output - no kernel panic, no oops, just a complete and immediate system lock up. The worst of all is that after computer wake up, the network interface connected to this NIC doesn't work at all. ethtool says that cable is not connected. After reboot everything works fine. 2.6.26 - no changes. Please try the latest forcedeth driver. I had put in a patch to fix MSI issue after suspend. See bug: http://bugzilla.kernel.org/show_bug.cgi?id=10487 |