Bug 1361614
| Summary: | [abrt] BUG: sleeping function called from invalid context at mm/slab.h:391 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Joachim Frieben <jfrieben> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 25 | CC: | awilliam, bugzilla, gansalmon, iliketurtlesbro, itamar, jonathan, juliux.pigface, kernel-maint, madhu.chinakonda, mchehab, michal.jnn | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/91088472ab3302b5e1d9449eb5841855f7b19096 | ||||||
| Whiteboard: | abrt_hash:97cb95136ac065e29e3a26bbfdf753cc7e27bcc8;VARIANT_ID=workstation; | ||||||
| Fixed In Version: | kernel-4.8.0-0.rc1.git1.1.fc25 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-08-10 20:10:43 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1277285 | ||||||
| Attachments: |
|
||||||
|
Description
Joachim Frieben
2016-07-29 14:10:12 UTC
Created attachment 1185573 [details]
File: dmesg
It looks like that I am seeing the same bug with 4.8.0-0.rc0.git3.1.fc26.x86_64 only with a line number slightly different. Booting that on "Acer Aspire T135/K8VM800MAE, BIOS R01-A3 06/27/2005" I get 33 times: [ 3.231229] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 4.296673] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 5.436395] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 15.887089] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 19.339376] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 25.687549] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 27.185124] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 28.711261] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 29.893191] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 30.928079] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 32.197365] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 33.697918] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 34.732839] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 35.842572] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 36.857164] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 37.915442] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 40.191417] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 43.596287] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 45.108227] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 46.673371] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 47.997747] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 49.103199] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 52.045579] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 53.343135] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 54.683570] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 55.722280] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 56.861133] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 57.877091] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 59.019474] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 64.576782] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 72.171066] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 74.057061] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 75.641668] BUG: sleeping function called from invalid context at mm/slab.h:393 After all this excitement a boot, suprisingly enough, finishes. If somebody wants to see a dmesg output please let me know. It does not seem to be materially different from what is alredy here. (In reply to Michal Jaegermann from comment #2) > It does not > seem to be materially different from what is alredy here. Acutally looking closer there is a small difference. Instead of modprobe from the original report I see: [ 3.231229] BUG: sleeping function called from invalid context at mm/slab.h:393 [ 3.231369] in_atomic(): 1, irqs_disabled(): 0, pid: 235, name: systemd-udevd [ 3.231459] no locks held by systemd-udevd/235. [ 3.231548] CPU: 0 PID: 235 Comm: systemd-udevd Not tainted 4.8.0-0.rc0.git3.1.fc26.x86_64 #1 This is in most of 33 cases mentioned before. In some modprobe shows up too. systemd-udev-231-2.fc26.x86_64, kmod-23-1.fc25.x86_64. I also see this on boot of a system (KVM) freshly installed from today's F25 x86_64 Server DVD nightly: https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20160803.n.0/compose/Server/x86_64/iso/Fedora-Server-dvd-x86_64-25-20160803.n.0.iso booting the system normally seems to fail - it never reaches a login prompt - but booting with console=ttyS0 does give a login prompt on the serial console. All openQA tests seem to have started failing on 2016-07-29. Between 2016-07-25 and 2016-07-29 there were no successful image composes, it seems; on 2016-07-24 most tests were passing. kernel 4.8 packages appeared on 2016-07-28, so this bug looks like a suspect in causing the boot failures, but labbott says it should not, and I *do* see the login prompt on the serial console, so I'll do some more poking around before declaring that this is the culprit for the boot failure. In a qemu-kvm VM I have a seemingly fully functional F25 Workstation installation with kernel-4.8.0-0.rc0.git3.1.fc25 with bunch of these BUG messages. It consistently gets to gdm. But I haven't updated it in perhaps two or three days, so I'd suspect something other than the kernel is causing it to not reach a login prompt. yeah, it seems to be something else, booting a 4.7 kernel stops this bug appearing but tty1 still doesn't get a login prompt. other ttys do, though. So I think it's a bug in systemd or something. (In reply to Adam Williamson from comment #6) Current Fedora 25 Workstation with kernel-4.8.0-0.rc0.git3.1.fc25 indeed still shows this bug but it is not fatal. It appears in the system output and gets reported by the problem reporting utility. Booting in permissive mode might allow the user to reach graphical login for further analysis. *** Bug 1364714 has been marked as a duplicate of this bug. *** Proposing as a freeze exception issue, it seems reasonable to fix this for Alpha as it's pretty visible. Did the kernel team have a plan for what kernel build you want in Alpha? Doesn't happen with 4.8.0-0.rc1.git0.1.fc25.x86_64, even if I boot with slub_debug=F. ah, and that one got in under the freeze. so if others can confirm we can probably just close this. Yeah, no trace of this in an install from today's Server netinst with 4.8.0-0.rc1.git0.1, so that looks like fix confirmed, let's close it. (In reply to Chris Murphy from comment #10) > Doesn't happen with 4.8.0-0.rc1.git0.1.fc25.x86_64, As expected 4.8.0-0.rc1.git1.1.fc26.x86_64 does not sport this bug either. (In reply to Michal Jaegermann from comment #13) > As expected 4.8.0-0.rc1.git1.1.fc26.x86_64 does not sport this bug either. Good to know. I was about to test that since it has more debug stuff enabled than slub_debug, and I can't tell if the BUG messages would have appeared anyway without debug stuff enabled. (In reply to Adam Williamson from comment #12) Kernel 4.8.0-0.rc1.git0.1 is a bad one: on my Lenovo ThinkPad T400, like previous kernels of the 4.8.0 development line, it leads to a kernel panic when shutting down the machine. Kernel 4.8.0-0.rc1.git1.1.fc25 was the first one to fix this issue. It should be included in some later TC if not in the first one. That has nothing to do with this bug. You need to file it separately if you want it considered, we cannot track two completely different issues in one bug report. (In reply to Adam Williamson from comment #16) Of course, but that is why I had not closed the bug report yet; issue filed as bug 1366104. |