On 09/04/2013 03:24 PM, Helmut Schaa wrote: > Hi Hauke, > > Booting a pretty decent x86 OpenWrt within KVM gives me a bunch of > Symbol errors in b44: > > [ 2.291153] b44: Unknown symbol ssb_device_is_enabled (err 0) > [ 2.294154] b44: Unknown symbol ssb_pcicore_dev_irqvecs_enable (err 0) > [ 2.298384] b44: Unknown symbol ssb_bus_may_powerdown (err 0) > [ 2.302220] b44: Unknown symbol ssb_pcihost_register (err 0) > [ 2.305303] b44: Unknown symbol ssb_device_disable (err 0) > [ 2.308565] b44: Unknown symbol ssb_device_enable (err 0) > [ 2.311455] b44: Unknown symbol ssb_driver_unregister (err 0) > [ 2.314884] b44: Unknown symbol __ssb_driver_register (err 0) > [ 2.318307] b44: Unknown symbol ssb_bus_powerup (err 0) > [ 2.319097] b44: Unknown symbol ssb_clockspeed (err 0) > [ 2.319871] b44: Unknown symbol ssb_dma_translation (err 0) > > Looks as if this was introduced by your commit: > > commit 5e65885775366154675d7ad9c4376f770302555c > Author: hauke <hauke@3c298f89-4303-0410-b956-a3cf2f4a3e73> > Date: Sun Jul 14 12:59:00 2013 +0000 > > brcm47xx: do not load the kernel modules needed for Ethernet manually > > add the boot flag to make the kernel modules needed for Ethernet and > diag load on startup. > > Maybe its enough to just update the Autoload priority of ssb to > something < 19 so > it gets loaded before b44? > > Or should we just use the lower priority on the brcm47xx target? > > Thanks, > Helmut Hi Helmut,
Thanks for reporting this. This was fixed in r37903. Hauke _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
