Bug #16715
rewrite the workaround about Soft Lockup
100%
Description
the “soft lockup - CPU#X stuck for 22s” is affecting several computers (some of them are listed in the comment of Bug #15774, but there are more, like the MSI Ghost GS60). usually the workarounds proposed for the xps 9560 are working on those computers, but the users are having trouble finding it by themselves due to the lack of details in the known issue entry (https://tails.boum.org/support/known_issues/index.en.html#index14h3).
it would be really great if, at least, the error message was specified, and if there was an anchor to that specific entry.
Subtasks
Related issues
|
Blocks Tails - |
Resolved | 2018-09-11 |
History
#1 Updated by sajolida 2019-05-14 16:14:33
- blocks
Feature #15941: Core work 2018Q4 → 2019Q2: Technical writing added
#2 Updated by sajolida 2019-05-14 16:14:48
- Assignee changed from sajolida to goupille
- Target version set to Tails_3.14
- QA Check set to Ready for QA
Please have a look at a16336e66c.
Can you confirm that:
- This issue is better placed in known_issues/graphics than known_issues.
- The “soft lockup” error is somehow displayed before the screen goes black.
#3 Updated by goupille 2019-05-14 18:21:54
sajolida wrote:
> Can you confirm that:
>
> * This issue is better placed in known_issues/graphics than known_issues.
as far as I know, the users facing the issues listed in known_issues/graphics are shown the custom error message linking to tails.boum.org/gdm. the users facing the soft lockup thing are not shown this issue, so I think it would be better to put it in known_issues
> * The “soft lockup” error is somehow displayed before the screen goes black.
as far as I understand, the users are shown this error and the boot process is stopped, (i can’t remember if the user needs to do something like removing quiet to see it or if the message is shown anyway)
#4 Updated by goupille 2019-05-14 19:14:50
regarding to a16336e66c:
- IIRC, it was the first workaround we found that broke the backlight for some laptops, given the other workarounds (including the one we document on the known issues page) it seems to be more of an ACPI issue than a graphic issue.
- sorry to insist, but I’d love to have an id= to link it to users, as I think that even if it is in the known issues, we will still need to point it to some people
#5 Updated by goupille 2019-05-14 19:15:43
- Assignee changed from goupille to sajolida
#6 Updated by sajolida 2019-05-14 20:39:51
> the issues listed in known_issues/graphics are shown the custom error message linking to tails.boum.org/gdm
Only the 1st part of the page (“Error starting GDM”) is about /gdm. The
rest of the page (“Other issues”) is about other graphics issues.
> as far as I understand, the users are shown this error and the boot process is stopped, (i can’t remember if the user needs to do something like removing quiet to see it or if the message is shown anyway)
Ok, so my slightly generic phrasing should work fine :)
I’m merging then. Thanks for the quick turnaround!
#7 Updated by sajolida 2019-05-14 20:43:54
- Status changed from Confirmed to Resolved
- % Done changed from 0 to 100
Applied in changeset commit:tails|8153596853b96291ba0d3bf3955799d57b8779d9.
#8 Updated by sajolida 2019-05-20 14:26:12
> - IIRC, it was the first workaround we found that broke the backlight for some laptops, given the other workarounds (including the one we document on the known issues page) it seems to be more of an ACPI issue than a graphic issue.
Ok, then I moved it back to /support/known_issues.
> - sorry to insist, but I’d love to have an id= to link it to users, as I think that even if it is in the known issues, we will still need to point it to some people
Here you go:
#9 Updated by sajolida 2019-05-20 14:26:49
- Assignee deleted (
sajolida) - QA Check deleted (
Ready for QA)