lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <4BA026AB.2040203@smartchat.net.au>
Date:	Wed, 17 Mar 2010 10:47:39 +1000
From:	Ron House <rhouse@...rtchat.net.au>
To:	linux-kernel@...r.kernel.org
Subject: PROBLEM: 2.6.30 fails to detect hardware limitation requiring "noapic"

Hello, I hope this is the right place to report a kernel bug.

I have an Acer desktop, bog standard system.

My previous kernel 2.6.26 tells me that I need to set option "noapic", 
and then halts. This behaviour is correct.

Although it would be nice if the kernel dealt with noapic automatically, 
the attempt to make this happen in 2.6.30 doesn't work.

Booting with 2.6.30 gives me a bootup with many errors - USB ports not 
responding, failure to set the clock, and others. Then when it has 
finished booting, both the mouse and keyboard are dead. (But the system 
is running and can be accessed via ssh.)

When I reboot 2.6.30 with "noapic", it boots correctly.

My comment on this is that 2.6.26 is actually more useful than 2.6.30, 
because 2.6.30 doesn't give any clue as to what is wrong or how to fix 
it. If I hadn't previously had the experience with 2.6.26, I would have 
been hopelessly lost.

Hope this is useful, and thank you so much for the wonderful software!

-- 
Ron House.
Building Peace: http://peacelegacy.org
Australian Birds: http://wingedhearts.org
Principle of Goodness academic site: http://principleofgoodness.net
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ