Bug #2625
closed
dhclient alc0 freezes the system if no cable is connected
0%
Description
It just halts the system. No message is printed at all. Note that if the cable is plugged in, everything works as expected.
Updated by sepherosa almost 11 years ago
On Wed, Jan 8, 2014 at 8:34 PM, <bugtracker-admin@leaf.dragonflybsd.org> wrote:
Issue #2625 has been reported by mneumann.
----------------------------------------
Bug #2625: dhclient alc0 freezes the system if no cable is connected
http://bugs.dragonflybsd.org/issues/2625
- Author: mneumann
- Status: New
- Priority: Normal
- Assignee:
- Category:
- Target version:
----------------------------------------
It just halts the system. No message is printed at all. Note that if the cable is plugged in, everything works as expected.
On the 3.6 release or the master?
Best Regards,
sephe
--
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
--
Tomorrow Will Never Die
Updated by mneumann almost 11 years ago
This happens on master. But I guess, it also fails on 3.6, but I haven't tried!
IIRC, I had a similar problem with "ale" on an ASUS EEE book a few years ago, but I might be completely wrong here.
Updated by mneumann over 10 years ago
- Status changed from New to Resolved
The commit fixes this bug:
http://gitweb.dragonflybsd.org/dragonfly.git/commit/a45385fec09b660facc3bf5e0abcdfbef1ee216e
Tested on Lenovo X121e with Atheros AR8151 v2.0 PCIe Gigabit Ethernet controller.
Untested on ASUS EEE as it's no longer around.
Updated by mneumann over 10 years ago
Note that on the Lenovo the AR8151 controller would hang the system a few seconds after the cable is unplugged. Unplugging the cable and replugging it now works :)
Updated by
Updated by mneumann over 10 years ago
yes, it should be safe to MFC. but probably there are not many alc0 users out there :)