https://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082014-06-16T21:05:44ZDragonFlyBSD bugtrackerDragonFlyBSD - Bug #2685: configuring ath0 freezes the systemhttps://bugs.dragonflybsd.org/issues/2685?journal_id=120882014-06-16T21:05:44Zswildner
<ul></ul><p>Okay, I'm fairly certain that reverting the most recent work on ath(4) (sleep state code synchronization) should fix it. After all, it added the message you see last.</p>
<p>Can you please verify by applying: <a class="external" href="http://leaf.dragonflybsd.org/~swildner/0001-kernel-ath-Revert-881d974b800-and-d98a0bcf56c.patch">http://leaf.dragonflybsd.org/~swildner/0001-kernel-ath-Revert-881d974b800-and-d98a0bcf56c.patch</a></p>
<p>(for example with 'git am <patch>' on the 3.8 branch)</p>
<p>I hope you have some git knowledge to juggle the patches you have locally on your branch.</p> DragonFlyBSD - Bug #2685: configuring ath0 freezes the systemhttps://bugs.dragonflybsd.org/issues/2685?journal_id=120902014-06-17T21:18:09Zxbit
<ul></ul><p>Thanks for your help and the patch. That solved the problem - at least for me. I applied the patch to on top of commit 358af07.</p>
<p>If there is something more to test to include the sleep state synchronization, please let me know.</p> DragonFlyBSD - Bug #2685: configuring ath0 freezes the systemhttps://bugs.dragonflybsd.org/issues/2685?journal_id=120912014-06-20T06:22:30Zswildner
<ul></ul><p>Can you give us a dump in the failing state?</p>
<p>Backup the working kernel by copying the /boot/kernel directory to /boot/kernel.bak. Then, revert the patch, recompile/install the kernel and bring it to the point where it hangs. Then, hit CTL-ALT-ESC to break into ddb. At the "db>" prompt, do "call dumpsys" (it should dump to disk then and countdown numbers on the console). When it is finished do "reset" to reboot. At the loader menu, it will then give you an option (I think it's "b") to boot the previously backed up working kernel.bak. Upon coming up, it will save the dump to /var/crash. Then, tar/xz the kern.XX and vmcore.XX with the highest number from /var/crash and put it up somewhere from where it can be downloaded.</p> DragonFlyBSD - Bug #2685: configuring ath0 freezes the systemhttps://bugs.dragonflybsd.org/issues/2685?journal_id=120922014-06-20T17:10:35Zxbit
<ul></ul><p>I would like to provide that crash dump, but unfortunately my USB keyboard stops works as soon as the system freezes. Neither CTRL-ALT-ESC nor using the NUMLOCK key works.</p>
<p>Is there any other way to trigger creating a crash dump? Will a non-USB keyboard (PS/2) work?</p> DragonFlyBSD - Bug #2685: configuring ath0 freezes the systemhttps://bugs.dragonflybsd.org/issues/2685?journal_id=120932014-06-20T18:44:09Zxbit
<ul></ul><p>I will upgrade my system to 3.8.1 and will test again without the reverted changes. I will also try to create the crash dump, but I expected this won't work due to the not-working USB keyboard.</p> DragonFlyBSD - Bug #2685: configuring ath0 freezes the systemhttps://bugs.dragonflybsd.org/issues/2685?journal_id=122702014-11-08T10:12:28Zxbit
<ul><li><strong>Target version</strong> changed from <i>3.8</i> to <i>4.0</i></li></ul><p>Everything worked fine with the patch reverted.</p>
<p>But with 4.0.0rc.10.g61c13 the problem shows up again. I do not see any output on the console (only the hardware address of the ath0 device), then the system freezes.</p>
<p>I tried to cherry-pick the commit that reverts the old changes mentioned in the patch, but that failed with conflicts. I did not try to solve these conflicts, just aborted the cherry-pick.</p>
<p>Are there any changes I can revert on 4.0.0? Or any other suggestions to find the reason for the freeze?</p>
<p>Thanks.</p> DragonFlyBSD - Bug #2685: configuring ath0 freezes the systemhttps://bugs.dragonflybsd.org/issues/2685?journal_id=126332015-03-29T09:32:38Zxbit
<ul></ul><p>I have checked this issue again and noticed some strange behaviour.</p>
<p>If I change several BIOS (AMI BIOS) settings, the freeze occurs. Below is a list of the settings and how they need to be set.</p>
<p>- Advanced Clock Calibration: Disabled<br />- PCIPnp: Active State Power Management: Enabled<br />- Northbridge Internal Graphics: FB Location: Below 4GB<br />- PCI Express: NB-SB VC1 Traffic Support: Enabled</p>
<p>Whenever I change one of these options, the systems freezes and restarts when running 'wpa_supplicant -Dbsd -iwlan0 -c/etc/wpa_supplicant.conf'.</p>
<p>With the settings above, I can run wpa_supplicant and dhclient and the network seems usables. I just made a quick ping to another machine.</p>
<p>The most strange behaviour is when I start wpa_supplicant in the background (with &), the system immediately hangs and resets.</p>
<p>I upgraded yesterday to 4.0.5.</p> DragonFlyBSD - Bug #2685: configuring ath0 freezes the systemhttps://bugs.dragonflybsd.org/issues/2685?journal_id=127092015-10-09T17:21:52Zxbit
<ul></ul><p>Seems to be fixed with 4.2.x. The device can be configured and used as before.</p>
<p>I don't know if 4.0.x is still affected and if this matters.</p>
<p>So I think the issues resolved.</p> DragonFlyBSD - Bug #2685: configuring ath0 freezes the systemhttps://bugs.dragonflybsd.org/issues/2685?journal_id=129022016-06-01T05:07:05Zswildner
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li></ul><p>Looks like this one was fixed. Closing.</p>