Bug 12328
Summary: | Low memory corruption on laptop lid close | ||
---|---|---|---|
Product: | ACPI | Reporter: | Gautam Iyer (gi1242) |
Component: | BIOS | Assignee: | acpi_bios |
Status: | CLOSED DUPLICATE | ||
Severity: | normal | CC: | bjorn.helgaas, fengguang.wu |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.28 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Gautam Iyer
2008-12-29 23:37:56 UTC
can you reproduce this problem with boot option "maxcpus=1"? can you reproduce this problem after set /proc/acpi/video/*/DOS to 1? (In reply to comment #1) Sorry for the delayed response. This is my primary computer, and I had to wait till the system was rebootable before I tried this. > can you reproduce this problem with boot option "maxcpus=1"? No. > can you reproduce this problem after set /proc/acpi/video/*/DOS to 1? No. I would add -- Sometimes when the system boots up, it *never* crashes on the lid close. I've recently had the system running for 2 weeks (once even up to 45 days) with repeated lid closes and hibernates with no problems at all. However on a subsequent reboot, it would almost certainly crash on a lid close. Don't know if that helps, GI Hi, Rui How about this bug? It seems that this is a duplicated of bug 12106. Thanks. problem can be solved by an IGD Operegion fix. patch will be attached later. *** This bug has been marked as a duplicate of bug 11259 *** (In reply to comment #4) > problem can be solved by an IGD Operegion fix. > patch will be attached later. > > *** This bug has been marked as a duplicate of bug 11259 *** > Ooh!! Patch? Will it be in GIT upstream? How can I get it? Eagerly waiting, and many many many thanks!! GI > > Ooh!! Patch? Will it be in GIT upstream? No, we just root caused this problem. Using a customized DSDT or optimizing the IGD OpRegion code could help on this issue. But we have not got a solution yet, because of driver some dependency problem. > How can I get it? Eagerly waiting, and > many many many thanks!! > Hah, I'll update as soon as the patch is available. I think this might be related to bug 13751, and I just added a patch to that report. If this is still an issue, Gautam, please test that patch and report the results. (In reply to comment #6) >> Ooh!! Patch? Will it be in GIT upstream? >> > No, we just root caused this problem. Using a customized DSDT or > optimizing the IGD OpRegion code could help on this issue. But we have > not got a solution yet, because of driver some dependency problem. It didn't quite work for me (I tried the patch in 2.6.30), so perhaps this is not related to bug 11259). (In reply to comment #7) > I think this might be related to bug 13751, and I just added a patch > to that report. If this is still an issue, Gautam, please test that > patch and report the results. OK (It'll take a couple of weeks as I'm moving right now). GI |