FS#18445 - [kernel26] lots of unknown symbols without acpi=off
Attached to Project:
Arch Linux
Opened by Ludovic Gasc (GMLudo) - Tuesday, 23 February 2010, 22:37 GMT
Last edited by Andrea Scarpino (BaSh) - Friday, 08 October 2010, 10:55 GMT
Opened by Ludovic Gasc (GMLudo) - Tuesday, 23 February 2010, 22:37 GMT
Last edited by Andrea Scarpino (BaSh) - Friday, 08 October 2010, 10:55 GMT
|
Details
On my Dell Latitude D630, I've several problems with
acpi=on
# HAL crashes at boot, see the logs: http://bbs.archlinux.org/viewtopic.php?pid=713412#p713412 # Xorg crashes randomly without logs. With acpi=off, it works correctly, but without the power management :-/ I can produce some logs or tests. I don't find some pieces of information to resolve my problem. BIOS version: A17 Linux kernel: 2.6.32-ARCH HAL: 0.5.14 Could it be a wrong DSDT ? Thanks for your answer. |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Friday, 08 October 2010, 10:55 GMT
Reason for closing: No response
Additional comments about closing: see last comment
Friday, 08 October 2010, 10:55 GMT
Reason for closing: No response
Additional comments about closing: see last comment
- xorg logs
- dmesg output
- relevant hal logs
A forum topic is not a replacement for this.
This is the logs (dmesg + hal + everything).
Do you need more information ?
hal.output (3.7 KiB)
everything.log (57.9 KiB)
I've a lot of "Unknown symbols" randomly on each boot (sometimes for ext3).
Arch Linux can't mount the root filesystem, it gives a rescue shell.
When I leave the rescue shell, I've a kernel panic, it shows a "not sync" error.
When I disable ACPI, I've nothing in the logs.
Do you think I've a hardware problem ?
I'm installing testing and lts kernel to test other kernels. If you have another idea, I'm interested.
With 2.6.33, I've the same problem as the beginning, but the dmesg is more explict about ACPI issues (see attachment). An idea ?
It's the first time I've the problem, but before I used Gentoo Linux distribution.
I've updated the bios some days ago, could it be the fault of the computer's DSDT ?
Yours.
There are some error/warning messages in your dmesg, and maybe can be safely ignored:
- ACPI Warning: Incorrect checksum in table [TCPA] - B3, should be 57 (20091214/tbutils-314)
- pci_root PNP0A03:00: ignoring host bridge windows from ACPI; boot with "pci=use_crs" to use them
- [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work.
Anyway attach the output of bsdtar -t -f /boot/kernel26.img.
Can you see symbols errors if you boot in fallback mode?
This is the output of bsdtar.
I see also symbols errors with fallback mode, see the other attached file.
dmesg.2.6.33.fallback (41.9 KiB)
> I've a lot of "Unknown symbols" randomly on each boot (sometimes for ext3).
*randomly*, I didn't read this before.
These issues started just when upgrade your BIOS? Is possible to downgrade or fixes an important issue?
Can you reproduce the errors with Arch Linux live CDs or other distro (just to try a different kernel version/configuration)?
PS: I suggest to request close this task and continue the discussion on forum, since this is not a packaging issue. Thanks.
> *randomly*, I didn't read this before.
Now, it's always the same errors.
I've downgraded my BIOS to A15 (like as before my installation of Arch Linux), I've the same problems.
No problems with some other distro, but with Chakra Linux, I've the same problem, with the same errors.
> PS: I suggest to request close this task and continue the discussion on forum, since this is not a packaging issue. Thanks.
I'm not sure that somebody on the forum can help me like you.
Please boot with it, and see at dmesg if something is wrong (unknown symbols) or any other msg (attach here).
It doesn't work, with several unknown symbol and the same crash like my installation.
If I add acpi=off on the CD boot, it works, like my installation.
I've retested the boot with the archlinux-2009.08-netinstall-x86_64.img, I have no problems to boot.
I'm thinking to compile myself a kernel to looking for a solution.
Do you think I could resolve my problem with a custom kernel ?
I can't help more that this. sorry.
I've found a better workaround with the nolapic option.
I've posted a bug report on the bugzilla of Linux: https://bugzilla.kernel.org/show_bug.cgi?id=16331
If they find a solution, I'll post on this issue.
Comment #8 From Ludovic Gasc 2010-09-01 12:42:59 -------
Sorry, I haven't this computer anymore.
I'd made several tests, I'd always the same problem.