| Summary: | WARNING: at kernel/trace/ftrace.c:914 ftrace_init_debugfs+0x19b/0x20f() | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | philippe.noroy |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | abrt_hash:390b98b5755adfa8a195d14e17d9faeac175b3d5 | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-09-18 15:26:22 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
philippe.noroy
2012-03-27 07:55:48 UTC
what were you doing to trigger this ? (In reply to comment #1) > what were you doing to trigger this ? It happened after : - a bunch of updates, including kernel update from 3.2.10 to 3.3.0-4 - first reboot ok, all works fine - add a friend's disk, to try to fix a boot error on it - the computer tries to boot, but cycles after grub screen: 5 4 3 2 1, then 4 lines of text, then reboot, 5 4 3 2 1, 4 lines... see ? - remove the fiend's disk - same problem !!! - then I chose the previous kernel at boot, it works (3.2.10) - being curious, I try kernel 3.2.9, works ok - once more 3.2.10 ok - then "normal" reboot (kernel 3.3), works fine, but with the warning for this bug... I hope this is helpful, and I hope you understand my english... Regards, Philippe Noroy do you have anything unusual on your boot command line ? It's curious that you're the only person seeing this. |