Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#23883 - [kernel26] 2.6.38-3 Boot caught in a loop

Attached to Project: Arch Linux
Opened by Michael (bounce775) - Friday, 22 April 2011, 10:01 GMT
Last edited by Andrea Scarpino (BaSh) - Sunday, 01 May 2011, 11:12 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To No-one
Architecture i686
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: A fresh net-install on my laptop (P3 1.26GHz, ACPI 1.0B compliant, an old SiS board). As soon as Arch is booted off the harddrive, it will loop these messages over and over, effectively making the system unusable:

[<c11ecf8f>] ? acpi_add_single_object
[<c11ecf8f>] ? acpi_device_suspend

I'm not sure on the hexadecimals, the messages fly by very fast and they never make it into a log.

Also, I *assume* this happens because of an Arch kernel patch. It started happening once I upgraded. Tried with both 2.6.38-2 and 2.6.38-3. Fedora 15 beta with 2.6.38 boots fine.

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Sunday, 01 May 2011, 11:12 GMT
Reason for closing:  Upstream
Additional comments about closing:  please report upstream
Comment by Michael (bounce775) - Saturday, 30 April 2011, 19:29 GMT
With 2.6.38.4-1, the messages changed slightly to:

[ 0.053330] [<c11ec???>] ? acpi_add_single_object
[ 0.053330] [<c11ed???>] ? unregister_acpi_bus_type

This happens on both the regular kernel and the fallback, again from a fresh net-install.

Loading...