There is no options of sleep or suspend in my UEFI.
[UNSOLVED] ventoy UEFI causing system to freeze.
- Thread starter price1221
- Start date
Condobloke
Well-Known Member
I have not waded through the 3 pages leading up to this....hope the below helps.
Systemd has suspend and hibernate functions. They can be checked with the following, then stopped and disabled at will:
Code:
systemctl status systemd-hibernate.service
systemctl status systemd-suspend-then-hibernate.service
systemctl status systemd-suspend.service
See if you can do something with this?
I have seen this blog and if you see the page 3 then you'll see an YouTube video of my laptop which is totally different from the bios in this blog
Guys I still don't know what's causing this tpm error but I think you guys understood by reading the logs. But I think I missed to mention that tpm error does cause it to freeze the device but before the tpm error shows in journald application one by one starts to crash. Like browser and terminal then tpm error shows. So I'm suspecting the root cause is not tpm?
It isn't quite clear since the stack trace doesn't actually show what process is the problem. But my guess would be that something to do with this line.
And then there's this line.
Which makes me thing it could have something to do with your filesystem, since there was a bug sometime ago with ext4 and the kernel.
Would it be possible to get a clearer picture the pictures you orginally post, since that looks like kernel dump which might provide some more information than in the stack trace in the log file output you shared?
Just of curiosity how does your laptop react when live-booting a distribution such as Linux Mint or Ubuntu, do you experience the same crashes/freezes then?
I have not started an live disk yet.. but before debian I used Manjaro and it didn't caused any errorIt isn't quite clear since the stack trace doesn't actually show what process is the problem. But my guess would be that something to do with this line.
And then there's this line.
Which makes me thing it could have something to do with your filesystem, since there was a bug sometime ago with ext4 and the kernel.
Would it be possible to get a clearer picture the pictures you orginally post, since that looks like kernel dump which might provide some more information than in the stack trace in the log file output you shared?
Just of curiosity how does your laptop react when live-booting a distribution such as Linux Mint or Ubuntu, do you experience the same crashes/freezes then?
@price1221:
A speculative look at the logs throw up a number of issues, which may or may not be to do with TPM at all. It's possible that the TPM focus is a red herring.
Logs in post #55 show the graphics card failing:
For the error with exit_code=11 the only hint of a solution I could find in a brief search was this:
This suggests that you try to disable hardware acceleration. Not being a user of wayland, I can't say how to do that in wayland. In X it's very straight forward for the intel GPU by adding a configuration snippet in /usr/share/X11/xorg.conf.d/. But, perhaps if you were running X instead of wayland, it may not be necessary because wayland is still software in development and these issues may be wayland specific. I can't say.
In the logs of post #48 there are some serious indicators:
The SIGSEGV is a segmentation fault which means that some function in a program has accessed an invalid memory address. This sort of fault is commonly involved in freezes and crashes. One can imagine how one program improperly uses memory addresses for another which would result in the other program being unable to run properly causing unpredictable results.
There's a similar fault in the log here which I take to be associated with the microsoft-edge browser:
It gives the address 0x0008a3890. Whatever the function is at that address, is particular to your machine so it's not identifiable.
These problems do not appear prima facie to be concerned with TPM.
You might like to consider running X to see if the same freezes occur, and perhaps with another browser.
These remarks are speculative and investigative rather definitive, but since the issue persists, it's probably worth looking at these things.
A speculative look at the logs throw up a number of issues, which may or may not be to do with TPM at all. It's possible that the TPM focus is a red herring.
Logs in post #55 show the graphics card failing:
Code:
ERROR:gpu_processs_host.cc(1030)] GPU process exited unexpectedly: exit_code=11For the error with exit_code=11 the only hint of a solution I could find in a brief search was this:
This suggests that you try to disable hardware acceleration. Not being a user of wayland, I can't say how to do that in wayland. In X it's very straight forward for the intel GPU by adding a configuration snippet in /usr/share/X11/xorg.conf.d/. But, perhaps if you were running X instead of wayland, it may not be necessary because wayland is still software in development and these issues may be wayland specific. I can't say.
In the logs of post #48 there are some serious indicators:
Code:
gsd-media-keys |SIGSEGV ...
fatal error: faultThe SIGSEGV is a segmentation fault which means that some function in a program has accessed an invalid memory address. This sort of fault is commonly involved in freezes and crashes. One can imagine how one program improperly uses memory addresses for another which would result in the other program being unable to run properly causing unpredictable results.
There's a similar fault in the log here which I take to be associated with the microsoft-edge browser:
Code:
msedge[49251]: segfault <at a number of addresses>It gives the address 0x0008a3890. Whatever the function is at that address, is particular to your machine so it's not identifiable.
These problems do not appear prima facie to be concerned with TPM.
You might like to consider running X to see if the same freezes occur, and perhaps with another browser.
These remarks are speculative and investigative rather definitive, but since the issue persists, it's probably worth looking at these things.
Last edited:
Brickwizard
Well-Known Member
On an ASUS with an INTEL i series CPU, the TPM toggle should be in the BIOS/UEFI in either advanced or security settings, listed as Intel trusted platform module
I'm getting the feeling it might be kernel related, since you weren't having this with Manjaro. Would you mind trying to install a kernel that is not provided by Debian, that way we have another thing to rule out?
Thanks for sticking with thread for this long time I really appreciate your helpI'm getting the feeling it might be kernel related, since you weren't having this with Manjaro. Would you mind trying to install a kernel that is not provided by Debian, that way we have another thing to rule out?
. Like I previously mentioned I haven't worked with kernel manually previously. Could you kindly provide some resources blogs or which distro kernel you want me to install?
Brickwizard
Well-Known Member
I am only quoting from the ASUS general work notes.
I have used Firefox, chromium (with hardware acceleration disabled in browser) and even switched to X environment manager. But in x I didn't disabled hardware acceleration. The issue was persistent. Do you want me to move to x and disable hardware acceleration?
If you see post #29 someone looked into the Asus model manual of my laptop and he found in the bios section of manual there is no mention of tpm
You can run the command on the page I linked.Thanks for sticking with thread for this long time I really appreciate your help
Code:
curl -s 'https://liquorix.net/install-liquorix.sh' | sudo bashAh sorry I'm on walk that's why I missed the link. I'll do this as soon as I reach my laptop thanks again
Code:
[INFO ] Liquorix repository added successfully to /etc/apt/sources.list.d/liquorix.list
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libelf1t64 : Breaks: libelf1 (< 0.191-1)
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.should i just remove libelf1t64 ?
