Opened 6 years ago
Last modified 6 years ago
#14282 closed bug
atheroswifi driver causes vm address fault at startup — at Initial Version
Reported by: | v.vill | Owned by: | waddlesplash |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Drivers/Network/atheroswifi | Version: | R1/Development |
Keywords: | Cc: | waddlesplash | |
Blocked By: | Blocking: | ||
Platform: | x86-64 |
Description
After upgrading to hrev52099, thus taking advantage of the updated atheroswifi driver (see #14249), the boot sequence ends in KDL with the following messages:
start_wlan: wlan started. atheroswifi: init_driver(0xffffffff81f155d0) at 12 loaded driver /boot/system/add-ons/kernel/drivers/dev/net/atheroswifi sis19x:00.16.016:init_hardware::SiS19X:init_hardware() slab memory manager: created area 0xffffffffa5001000 (7631) [net/atheroswifi/0] compat_open(0x2) [net/atheroswifi/0] ieee80211_init [net/atheroswifi/0] start running, 1 vaps running [net/atheroswifi/0] ieee80211_start_locked: up parent [net/atheroswifi/0] start running, 1 vaps running [net/atheroswifi/0] iee80211_new_state_locked: INIT -> SCAN (nrunning 0 nscanning 0) net/atheroswifi/0: media change, media 0x200a0 quality 1000 speed 1000000000 vm_page_fault: vm_soft_fault returned error ’Bad address’ on fault at 0xffffffff81f78044, ip 0xffffffff81e06fb7, write 0, user 0, thread 0x437 kdebug>
I’m running Haiku x86_64 (EFI boot) with an AR9565 chipset wifi chip (vendor/device: 168c/036).
Note:
See TracTickets
for help on using tickets.