ath0 Device Timeout Issues

Adrian Chadd adrian at freebsd.org
Thu Feb 28 17:34:31 UTC 2013


Just experiment with changing the kern.eventtimer.periodic and
kern.timecounter.hardware values.

Thanks,


Adrian


On 28 February 2013 03:20, Derrick Dantavious Edwards
<dantavious313 at gmail.com> wrote:
> On 27 February 2013 18:59, Derrick Dantavious Edwards
> <dantavious313 at gmail.com> wrote:
>>
>>     Yes. When I start the system, I get those messages. Wireless Link fails
> to
>> establish thus causing all services requring link to fail....ie NFS . Soon
>> after I am at the command prompt or GUI, I can ping hosts however, I have to
>> /etc/rc.d/mountlate to get remote filesystems connected. Thanks for your
>> assistance.
>>
>
> right. Well, those network services should only (re)start once the
> network link is up.
>
> But as to why the network link is taking a while to come up; I'm not sure.
>
> The device timeouts are a known race. It's not indicative that a
> device timeout actually did occur. Fixing the watchdog to be actually
> correct is on my TODO list but it's fallen behind in priority.
>
> I have a feeling that the probe requests aren't being given enough
> time to go out. Would you mind trying to change the eventtimer /
> timesource (sysctl kern.eventtimer and sysctl kern.timecounter); see
> if that helps things along?
>
> Thanks,
>
>
>
> adrian
>
>         Sure, I have no problem making a change. I placed the available options
> for my system below. Which do you prefer I use for this test?
>
> Derrick
>
> root at zeus:~ # sysctl kern.eventtimer
> kern.eventtimer.et.LAPIC.flags: 7
> kern.eventtimer.et.LAPIC.frequency: 49887865
> kern.eventtimer.et.LAPIC.quality: 600
> kern.eventtimer.et.HPET.flags: 7
> kern.eventtimer.et.HPET.frequency: 14318180
> kern.eventtimer.et.HPET.quality: 550
> kern.eventtimer.et.HPET1.flags: 3
> kern.eventtimer.et.HPET1.frequency: 14318180
> kern.eventtimer.et.HPET1.quality: 440
> kern.eventtimer.et.HPET2.flags: 3
> kern.eventtimer.et.HPET2.frequency: 14318180
> kern.eventtimer.et.HPET2.quality: 440
> kern.eventtimer.et.HPET3.flags: 3
> kern.eventtimer.et.HPET3.frequency: 14318180
> kern.eventtimer.et.HPET3.quality: 440
> kern.eventtimer.et.HPET4.flags: 3
> kern.eventtimer.et.HPET4.frequency: 14318180
> kern.eventtimer.et.HPET4.quality: 440
> kern.eventtimer.et.RTC.flags: 17
> kern.eventtimer.et.RTC.frequency: 32768
> kern.eventtimer.et.RTC.quality: 0
> kern.eventtimer.et.i8254.flags: 1
> kern.eventtimer.et.i8254.frequency: 1193182
> kern.eventtimer.et.i8254.quality: 100
> kern.eventtimer.choice: LAPIC(600) HPET(550) HPET1(440) HPET2(440) HPET3(440)
> HPET4(440) i8254(100) RTC(0)
> kern.eventtimer.singlemul: 2
> kern.eventtimer.idletick: 0
> kern.eventtimer.activetick: 1
> kern.eventtimer.timer: LAPIC
> kern.eventtimer.periodic: 0
>
> root at zeus:~ # sysctl kern.timecounter
> kern.timecounter.tc.HPET.mask: 4294967295
> kern.timecounter.tc.HPET.counter: 2161173885
> kern.timecounter.tc.HPET.frequency: 14318180
> kern.timecounter.tc.HPET.quality: 950
> kern.timecounter.tc.i8254.mask: 65535
> kern.timecounter.tc.i8254.counter: 20336
> kern.timecounter.tc.i8254.frequency: 1193182
> kern.timecounter.tc.i8254.quality: 0
> kern.timecounter.tc.ACPI-fast.mask: 16777215
> kern.timecounter.tc.ACPI-fast.counter: 3908063
> kern.timecounter.tc.ACPI-fast.frequency: 3579545
> kern.timecounter.tc.ACPI-fast.quality: 900
> kern.timecounter.tc.TSC-low.mask: 4294967295
> kern.timecounter.tc.TSC-low.counter: 2410520996
> kern.timecounter.tc.TSC-low.frequency: 1247196540
> kern.timecounter.tc.TSC-low.quality: 1000
> kern.timecounter.stepwarnings: 0
> kern.timecounter.hardware: TSC-low
> kern.timecounter.choice: TSC-low(1000) ACPI-fast(900) i8254(0) HPET(950)
> dummy(-1000000)
> kern.timecounter.tick: 1
> kern.timecounter.fast_gettime: 1
> kern.timecounter.invariant_tsc: 1
> kern.timecounter.smp_tsc: 1
> kern.timecounter.tsc_shift: 1
>


More information about the freebsd-wireless mailing list