Re: crash on boot since the first .327... kernel update
I encountered a crash-on-boot problem with some AMD-based desktops; I got it working by adding the kernel parameter initcall_blacklist=clocksource_done_booting It's described in this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1285235 Steve Gaarder System Administrator, Dept of Mathematics Cornell University, Ithaca, NY, USA gaar...@math.cornell.edu On Mon, 1 Feb 2016, Robert Blair wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have an old compaq f700 laptop that I installed SL7 on. It ran fine until three kernel updates ago. All of the 327 patches cause it to crash on boot. I have had to blacklist the new kernels in order to get it back up. Is this something others have encountered? This system I suspect has ACPI issues since it is not supported by most OS's (windows 10 and ubuntu all fail to install and the video memory is shared and seems to be misidentified by X.org on startup). Any suggestions on what might be a workaround (boot options?) or what changed in the last three kernel patches that might cause this would be appreciated. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJWr3h5AAoJEPQM1KNWz8QaGtIH/R5/7KFIxCwGV0IBxMJ0WaGY MWEynk1hzPV8Ry7ioPGUnbuXhKl4DxT8A3nJBjPzR5284dqgAosBBpHFZdEH7L69 5UKRoK+mqwG4P2nXHzjZf09cbKrdzTs4wBiLZBydmUE9YW4ATRajPFNw++Nj1as3 POEJq9p9lCjK7iJTNv+awAabyDHJZNfrHWzEGtrVUflwSdrWa1HkoZ0S20bnNMAU CaQBU2+Fern27Jcp4GgHKxOmVXMgSJGfcJcjYglowWhzaWhV7azVuPPjci3SJ3K0 kEyCxy+FndQGpNuOvcOXN3yJodnQ8oShxaAL+GD3P5rAGQVFYyErMDR0jDMUe9E= =ZKsN -END PGP SIGNATURE-
Re: crash on boot since the first .327... kernel update
On 1 February 2016 at 08:23, Robert Blair wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I have an old compaq f700 laptop that I installed SL7 on. It ran fine
> until three kernel updates ago. All of the 327 patches cause it to
> crash on boot. I have had to blacklist the new kernels in order to get
> it back up. Is this something others have encountered? This system I
> suspect has ACPI issues since it is not supported by most OS's (windows
> 10 and ubuntu all fail to install and the video memory is shared and
> seems to be misidentified by X.org on startup). Any suggestions on what
> might be a workaround (boot options?) or what changed in the last three
> kernel patches that might cause this would be appreciated.
acpi= [HW,ACPI,X86,ARM64]
Advanced Configuration and Power Interface
Format: { force | off | strict | noirq | rsdt |
copy_dsdt }
force -- enable ACPI if default was off
off -- disable ACPI if default was on
noirq -- do not use ACPI for IRQ routing
strict -- Be less tolerant of platforms that are not
strictly ACPI specification compliant.
rsdt -- prefer RSDT over (default) XSDT
copy_dsdt -- copy DSDT to memory
For ARM64, ONLY "acpi=off" or "acpi=force" are available
See also Documentation/power/runtime_pm.txt, pci=noacpi
I would try off first and see if that does things. The 327 has a large
amount of backports from I think 4.0 kernel so I expect that the
hardware is saying things which are not there are. There isn't much
which can be done to fix that...
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.14 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJWr3h5AAoJEPQM1KNWz8QaGtIH/R5/7KFIxCwGV0IBxMJ0WaGY
> MWEynk1hzPV8Ry7ioPGUnbuXhKl4DxT8A3nJBjPzR5284dqgAosBBpHFZdEH7L69
> 5UKRoK+mqwG4P2nXHzjZf09cbKrdzTs4wBiLZBydmUE9YW4ATRajPFNw++Nj1as3
> POEJq9p9lCjK7iJTNv+awAabyDHJZNfrHWzEGtrVUflwSdrWa1HkoZ0S20bnNMAU
> CaQBU2+Fern27Jcp4GgHKxOmVXMgSJGfcJcjYglowWhzaWhV7azVuPPjci3SJ3K0
> kEyCxy+FndQGpNuOvcOXN3yJodnQ8oShxaAL+GD3P5rAGQVFYyErMDR0jDMUe9E=
> =ZKsN
> -END PGP SIGNATURE-
--
Stephen J Smoogen.
