We're getting quite a few people posting in this report that may or may not have the same issue. For the benefit of the reporter, kernel team and the other people that are definately experiencing this bug, I want to try and avoid this report becoming like some other reports have done in the past (where they just become too messy to follow).
I want to try and get this report in to a state where I can set it to triaged, and to do that, I will need to ask for some more information (I need a complete set of data off at least one person really). Ed Hargin - Could you please include all of the information requested at https://wiki.ubuntu.com/DebuggingACPI separate attachments? geraldo - It looks like you are seeing the same oops as the original reporter. Could you also please provide any information requested in https://wiki.ubuntu.com/DebuggingACPI which you haven't already provided (I think it is just the output of dmidecode and the contentsof /proc/acpi which is outstanding) Alex Lopez - After comparing your call trace to Ed's and geraldo's, it seems your oops occurs in a slightly different place. I would encourage you to open another report for your problem. Gianfranco - There is no evidence from the data you have given that you are experiencing this problem. Please open up another report with the kernel BUG messages from your /var/log/kern.log Thanks for your co-operation :) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) => Chris Coulson (chrisccoulson) Status: Confirmed => Incomplete -- Soft lockup in native_safe_halt on CPU#0 https://bugs.launchpad.net/bugs/206316 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
