On 24 March 2015 at 09:34, Peer, Ilan <[email protected]> wrote: > Hi, > > This mean u probably do not have crda installed, or it is not properly > configured. These are debug prints so the simplest would be to disable > CONFIG_CFG80211_REG_DEBUG .. unless you are debugging wireless regulatory > flows.
Are you sure? I see lots (one every ~3 seconds) of this after rebasing on latest linux-next and CONFIG_CFG80211_REG_DEBUG isn't enabled: [ 19.382847] cfg80211: Calling CRDA to update world regulatory domain Reverting this patch brings back the old behavior. > Regardless, I'll try to come up with a better solution to handle such cases. Thanks, Tomeu > Thanks, > > Ilan. > >> -----Original Message----- >> From: Huang, Ying >> Sent: Tuesday, March 24, 2015 09:32 >> To: Peer, Ilan >> Cc: Berg, Johannes; LKML; [email protected] >> Subject: [LKP] [cfg80211] eeca9fce1d7: BUG: kernel boot oversize >> >> FYI, we noticed the below changes on >> >> git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git master >> commit eeca9fce1d71a4955855ceb0c3b13c1eb9db27c1 ("cfg80211: >> Schedule timeout for all CRDA calls") >> >> >> +-------------------------+------------+------------+ >> | | 0505075360 | eeca9fce1d | >> +-------------------------+------------+------------+ >> | boot_successes | 9 | 9 | >> | boot_failures | 0 | 1 | >> | BUG:kernel_boot_crashed | 0 | 1 | >> +-------------------------+------------+------------+ >> >> It appears too many like like below in dmesg after applying the patch in a >> virtual machine. >> >> [11223.232543] cfg80211: Kicking the queue [11223.233674] cfg80211: >> Calling CRDA to update world regulatory domain >> >> BUG: kernel boot oversize >> Elapsed time: 11150 >> qemu-system-x86_64 -enable-kvm -cpu Haswell,+smep,+smap -kernel >> /kernel/x86_64-randconfig-n0- >> 03210642/ca2fd9633ed4fe8a5ad56efb2fcef061a19f2e90/vmlinuz-4.0.0-rc4- >> wl-ath-03682-gca2fd963 -append 'user=lkp job=/lkp/scheduled/vm-kbuild- >> 1G-10/rand_boot-1-x86_64-randconfig-n0-03210642- >> ca2fd9633ed4fe8a5ad56efb2fcef061a19f2e90-0.yaml ARCH=x86_64 >> BOOT_IMAGE=/kernel/x86_64-randconfig-n0- >> 03210642/ca2fd9633ed4fe8a5ad56efb2fcef061a19f2e90/vmlinuz-4.0.0-rc4- >> wl-ath-03682-gca2fd963 kconfig=x86_64-randconfig-n0-03210642 >> commit=ca2fd9633ed4fe8a5ad56efb2fcef061a19f2e90 branch=linux- >> devel/devel-hourly-2015032023 root=/dev/ram0 max_uptime=3600 >> RESULT_ROOT=/result/vm-kbuild-1G/boot/1/debian-x86_64-2015-02- >> 07.cgz/x86_64-randconfig-n0- >> 03210642/ca2fd9633ed4fe8a5ad56efb2fcef061a19f2e90/0 ip=::::vm- >> kbuild-1G-10::dhcp earlyprintk=ttyS0,115200 rd.udev.log-priority=err >> systemd.log_target=journal systemd.log_level=warning debug apic=debug >> sysrq_always_enabled rcupdate.rcu_cpu_stall_timeout=100 panic=-1 >> softlockup_panic=1 nmi_watchdog=panic oops=panic load_ramdisk=2 >> prompt_ramdisk=0 console=ttyS0,115200 console=tty0 vga=normal rw' - >> initrd /fs/sdd1/initrd-vm-kbuild-1G-10 -m 1024 -smp 2 -net >> nic,vlan=1,model=e1000 -net user,vlan=1 -boot order=nc -no-reboot - >> watchdog i6300esb -rtc base=localtime -device virtio-scsi-pci,id=scsi0 -drive >> file=/fs/sdd1/disk0-vm-kbuild-1G- >> 10,if=none,id=hd0,media=disk,aio=native,cache=none -device scsi- >> hd,bus=scsi0.0,drive=hd0,scsi-id=1,lun=0 -drive file=/fs/sdd1/disk1-vm- >> kbuild-1G-10,if=none,id=hd1,media=disk,aio=native,cache=none -device scsi- >> hd,bus=scsi0.0,drive=hd1,scsi-id=1,lun=1 -drive file=/fs/sdd1/disk2-vm- >> kbuild-1G-10,if=none,id=hd2,media=disk,aio=native,cache=none -device scsi- >> hd,bus=scsi0.0,drive=hd2,scsi-id=1,lun=2 -drive file=/fs/sdd1/disk3-vm- >> kbuild-1G-10,if=none,id=hd3,media=disk,aio=native,cache=none -device scsi- >> hd,bus=scsi0.0,drive=hd3,scsi-id=1,lun=3 -drive file=/fs/sdd1/disk4-vm- >> kbuild-1G-10,if=none,id=hd4,media=disk,aio=native,cache=none -device scsi- >> hd,bus=scsi0.0,drive=hd4,scsi-id=1,lun=4 -pidfile /dev/shm/kboot/pid-vm- >> kbuild-1G-10 -serial file:/dev/shm/kboot/serial-vm-kbuild-1G-10 -daemonize - >> display none -monitor null >> >> >> >> Thanks, >> Ying Huang > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
