Bug #1817

if and snd modules not loaded on startup

Added by elekktretterr over 4 years ago. Updated about 4 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

I'm having a couple of issues that crept in in the last month (running
"master" as of today)

1) I use if_ath has to be loaded manually. It is no longer loaded at
boot-time.

2) snd_hda doesn't load anymore either

3) This is the output of kldload, after loading if_ath

bge0: <Broadcom BCM5906M Fast Ethernet> irq 11 at device 0.0 on pci4
bge0: 0x10000 bytes of rid 0x10 res 3 failed (0, 0xffffffff).
bge0: couldn't map memory
device_probe_and_attach: bge0 attach returned 6
ath0: <Atheros 5424/2424> mem 0xf2100000-0xf210ffff irq 11 at device 0.0
on pci16
intr 11 at 40001/40000 hz, livelocked limit engaged!
sched_ithd: stray interrupt 7 on cpu 0
sched_ithd: stray interrupt 7 on cpu 0
ath0: AR5413 mac 10.3 RF5424 phy 6.1

bge0 never worked on this laptop when ACPI is enabled(without ACPI it
works, but the SMP kernel panics during boot, UP is fine). The weird thing
is that the bge0 lines repeat after loading if_ath, the same happens when
snd_hda gets loaded:

pcm0: <Intel 82801G High Definition Audio Controller> mem
0xf2340000-0xf2343fff irq 11 at device 27.0 on pci0
pcm0: <HDA Codec: Realtek ALC268>
pcm0: <HDA Driver Revision: 20071129_0050>
bge0: <Broadcom BCM5906M Fast Ethernet> irq 11 at device 0.0 on pci4
bge0: 0x10000 bytes of rid 0x10 res 3 failed (0, 0xffffffff).
bge0: couldn't map memory

No changes have been made by me to /boot/loader.conf for a long time.

dsched.policy.da0=fq
if_ath_load="YES"
snd_hda_load="YES"

Thanks

History

#1 Updated by dillon over 4 years ago

:I'm having a couple of issues that crept in in the last month (running
:"master" as of today)
:
:1) I use if_ath has to be loaded manually. It is no longer loaded at
:boot-time.
:
:2) snd_hda doesn't load anymore either
:
:3) This is the output of kldload, after loading if_ath

I fixed a bug a littler earlier today that probably accounts
for this issue, try updating the loader (/usr/src/sys/boot).

-Matt
Matthew Dillon
<>

#2 Updated by alexh about 4 years ago

I guess this was related to dloader or so and is fixed now. Please reopen if not.

Also available in: Atom PDF