The following reply was made to PR kern/124127; it has been noted by GNATS.
From: Pyun YongHyeon
To: Andrew Bliznak
Cc: bug-follo...@freebsd.org, skyl...@linkline.ru
Subject: Re: kern/124127: [msk] watchdog timeout (missed Tx interrupts) --
recovering
Date: Wed, 8 Jul 2009 14:03:58 +0900
On M
The following reply was made to PR kern/124127; it has been noted by GNATS.
From: Pyun YongHyeon
To: "Dmitry A.Deineka"
Cc: bug-follo...@freebsd.org
Subject: Re: kern/124127: [msk] watchdog timeout (missed Tx interrupts) --
recovering
Date: Wed, 8 Jul 2009 13:58:02 +0900
On Wed, Jul 01, 2009
In case you hadn't seen it, the code that fixes this is now checked into
the tip, so the latest em driver should work for you.
Jack
On Sun, Jun 28, 2009 at 9:52 AM, Jack Vogel wrote:
> Sigh.. both windows and linux have frozen drivers for this old hardware,
> therefore they never see the regre
Yes, this was fixed a couple of months ago.
-- Qing
> -Original Message-
> From: owner-freebsd-...@freebsd.org [mailto:owner-freebsd-
> n...@freebsd.org] On Behalf Of Lawrence Stewart
> Sent: Friday, July 03, 2009 4:51 AM
> To: Qing Li
> Cc: freebsd-net@freebsd.org; qin...@freebsd.org
> S
Louis Mamakos wrote:
> > Shouldn't ntpd have figured out by now that the clock is gone (I
> > unplugged it yesterday) and have switched into orphan mode?
>
> It seems like orphan mode is something that you'd run on an ensemble
> of local machines to ensure that they continue to be synchronized w
Paul B. Mahol wrote:
The only way to handle hardware RF switch is via devd(8).
ACPI notify devd(8) about state change and devd than can react on that change.
iwn(8) can do nothing about this.
What notebook do you have?
Dell XPS M1330
Thanks,
Aragon
Aragon Gouveia wrote:
> Hi,
>
> Is it just me, or does the iwn driver in -CURRENT not play well with
> hardware RF switches on notebooks? For me the only resemblence of an
> event I see is when I switch off RF - the kernel sends a log to syslog.
> wpa_supplicant doesn't pick it up, and neither d
Weongyo Jeong wrote:
I'm happy to see your device is successfully associated with AP.
However it seems it's a bad news that you sometimes meet crashes. Does
a random crash mean a OS hang (e.g. could not type any keys) or no more
work of network operations?
It hangs, I cannot use the keyboard a
