Created attachment 914232 [details] dmesg log Description of problem: Kernel crashes on boot on a HP workstation xw8200 as long as snd-ctxfi is not blacklisted. Version-Release number of selected component (if applicable): 3.14.8-200.fc20.x86_64 (problem exists with all kernel releases of F20) How reproducible: Almost 100%. Just try to start the machine. Steps to Reproduce: 1. Power-on the machine 2. The machine hangs Actual results: The machine hangs soon after loading snd-ctxfi or when first trying to play a sound (e.g. lightdm startup sound). Expected results: The kernel should not hang, and the soundcard should play the sound. Additional info: Several messages and warnings are printed during boot sequence before the kernel hangs. Sometimes, I could see those very last messages (if I switch back to the text console as soon as lightdm starts): ctxfi: PLL initialization failed!!! ctxfi: Preparing pcm playback failed!!! Attached is a dmesg log of a (very rare) case where the machine did actually not hang on startup, since this time snd_ctxfi failed to load before crashing the kernel. Please note in particular those error/warnings which might or might not related to this issue: [ 0.167257] WARNING: CPU: 0 PID: 1 at mm/page_alloc.c:2496 __alloc_pages_nodemask+0x427/0xb60() [ 0.180524] pci 0000:00:1f.0: address space collision: [io 0xf800-0xf87f] conflicts with ACPI CPU throttle [??? 0x0000f810-0x0000f815 flags 0x80000000] [ 0.180530] pci 0000:00:1f.0: quirk: [io 0xfa00-0xfa3f] claimed by ICH4 GPIO [ 0.210966] pnp 00:0b: disabling [io 0xf800-0xf81f] because it overlaps 0000:00:1f.0 BAR 13 [io 0xf800-0xf87f] [ 0.210970] pnp 00:0b: disabling [io 0xf820-0xf83f] because it overlaps 0000:00:1f.0 BAR 13 [io 0xf800-0xf87f] [ 0.210973] pnp 00:0b: disabling [io 0xf840-0xf85f] because it overlaps 0000:00:1f.0 BAR 13 [io 0xf800-0xf87f] [ 0.210976] pnp 00:0b: disabling [io 0xf860-0xf87f] because it overlaps 0000:00:1f.0 BAR 13 [io 0xf800-0xf87f] [ 0.216033] pnp 00:0f: disabling [mem 0x00000000-0x0009ffff] because it overlaps 0000:02:05.0 BAR 6 [mem 0x00000000-0x000fffff pref] [ 0.216038] pnp 00:0f: disabling [mem 0x000e8000-0x000fffff] because it overlaps 0000:02:05.0 BAR 6 [mem 0x00000000-0x000fffff pref] [ 0.216041] pnp 00:0f: disabling [mem 0x000ce800-0x000e7fff] because it overlaps 0000:02:05.0 BAR 6 [mem 0x00000000-0x000fffff pref] [ 0.216045] pnp 00:0f: disabling [mem 0x00000000-0x0009ffff disabled] because it overlaps 0000:02:05.1 BAR 6 [mem 0x00000000-0x000fffff pref] [ 0.216049] pnp 00:0f: disabling [mem 0x000e8000-0x000fffff disabled] because it overlaps 0000:02:05.1 BAR 6 [mem 0x00000000-0x000fffff pref] [ 0.216053] pnp 00:0f: disabling [mem 0x000ce800-0x000e7fff disabled] because it overlaps 0000:02:05.1 BAR 6 [mem 0x00000000-0x000fffff pref] [ 0.216107] system 00:0f: [mem 0x00100000-0xbfffffff] could not be reserved [ 0.216111] system 00:0f: [mem 0xfec01000-0xffffffff] could not be reserved [ 0.224530] pci 0000:00:1f.0: BAR 13: [io 0xf800-0xf87f] has bogus alignment [ 45.977697] intel_rng: Firmware space is locked read-only. If you can't or intel_rng: don't want to disable this in firmware setup, and if intel_rng: you are certain that your system has a functional intel_rng: RNG, try using the 'no_fwh_detect' option. [ 45.995217] ACPI Warning: SystemIO range 0x000000000000f828-0x000000000000f82f conflicts with OpRegion 0x000000000000f800-0x000000000000f84f (\ICHP) (20131218/utaddress-258) [ 45.995229] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 45.995271] lpc_ich: Resource conflict(s) found affecting gpio_ich [ 46.520466] ALSA sound/pci/ctxfi/ctatc.c:1300 ctxfi: chip 20K1 model Unknown (1102:0021) is found [ 46.520497] genirq: Flags mismatch irq 0. 00000080 (snd_ctxfi) vs. 00015a20 (timer) [ 46.520678] XFi: Cannot get irq 0 [ 46.520686] ctxfi: Something wrong!!! [ 46.520697] snd_ctxfi: probe of 0000:10:00.0 failed with error -16 The Creative Labs SB X-Fi is at pci 0000:10:00.0: [1102:0005]. Blacklisting snd-ctxfi or physically removing the board from the machine "solves" the issue. This machine was working perfectly (including sound played through the SB X-Fi) with Fedora 18. This issue looks quite similar to: https://www.centos.org/forums/viewtopic.php?f=13&t=3372 .
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.17.2-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.
Hi, I confirm this bug still happens with kernels 3.17.2-200.fc20.x86_64 and 3.17.4-200.fc20.x86_64. Typing: # modprobe snd_ctxfi causes either instant freeze of the machine (without any message being printed anywhere on the console, even when doing that from a text console) or either an instant reboot of the machine. 100% reproductible on my machine. Bug was not present with Fedora 18 (working perfectly with snd_ctxfi).
Some more info: Given the instant freeze, abrt cannot collect enough data to file a report. However, I always get the same error message at the next successful boot (always exactly the same line number and hex values): WARNING: CPU: 0 PID: 1 at mm/page_alloc.c:2545 __alloc_pages_nodemask+0x2b7/0xa40() The problem data are incomplete. This usually happens when a problem is detected while computer is shutting down or user is logging out. In order to provide valuable problem reports, ABRT will not allow you to submit this problem. If you have time and want to help the developers in their effort to sort out this problem, please contact them directly.