Bug #198
Slow boot with eeepc-laptop
| Status: | Feedback | Start date: | 10/06/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Corentin Chary |
% Done: | 0% |
|
| Category: | eeepc-laptop | |||
| Target version: | - |
Description
I have an eeepc 1000 and have used eeepc-laptop compiled in with kernel 2.6.38. After I have updated to 2.6.39 there was a pause of about 25s on boot. When I disable eeepc-laptop boot times are back to normal but without the functionality.
I also noticed this problem in the 3.0.4 kernel. I haven't tested anything newer.
I already had issue #2 with an older kernel and it feels similar, because when I remove i2c-801 in the kernel it boots fast again :).
History
Updated by Corentin Chary 8 months ago
Did you try the acpi_enforce_resources=strict parameter ?
Is your BIOS up to date ? If not you should try to update it and use eeepc-wmi instead of eeepc-laptop.
Updated by Anonymous 8 months ago
The problem still exists even with this parameter. My BIOS is up-to-date.
I'm trying to use the eeepc-wmi. This doesn't pause at boot but I have other issues with it as I have written in #199.
Thanks so far for your quick response. As eeepc-wmi is the new way I'd like to get this working preferrably.
Updated by Anonymous 7 months ago
Ok ... let's restart here :'(.
Could you just attach a dmesg with eeepc-laptop loading at boot ?
Do you know since when you have noticed this behavior ? Was it always present ? If not, we should try to do a bissection.
Updated by Anonymous 7 months ago
- File dmesg-eeepc-laptop-with-i2c-801.txt added
- File dmesg-eeepc-laptop-without-i2c-801.txt added
I have noticed this when I updated from linux-2.6.38 to linux-2.6.39
Can you give me link how to do this bisection and what information I should retrieve.
Updated by Anonymous 7 months ago
BTW I don't even now what advantage I have with this enabled. :)
I haven't noticed any change in functionality.
Updated by Corentin Chary 7 months ago
Yeah, a quick solution is to disable it. But it would be actually better to try to fix the bug, so if you got some time to do the bissection that would be great :).
Here is a quick guide: https://wiki.ubuntu.com/Kernel/KernelBisection
But basically, you clone a kernel using git, you start a bissection starting with a known good version and a known bad version, but git ask you to try a version, you test it, and you mark it as bad or good, and doing that 4-5 times should lead you to the offending commit.
Updated by Corentin Chary 4 months ago
- Status changed from New to Feedback