linux-kernel - Boot failure in 2.6.37

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]

Date:	Thu, 06 Jan 2011 14:43:29 -0500
From:	David Ronis <ronis@...ispc.chem.mcgill.ca>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Boot failure in 2.6.37

I just upgraded 3 machines from version 2.6.36 to 2.6.37.  On one of
them, as it turns out, the oldest machine, rebooting hung (the other 2
are fine).  The last thing I see on the console is:

/dev/ttyS?: No such file or directory
Using /etc/random-seed to initialize /dev/urandom

(normally this is a box without a monitor, keyboard etc).

I couldn't login via ssh (no surprise) but several daemons were up and
running (the machine was pingable, mail was being received).

This is a noname, dual cpu Pentium III box running slackware 11.0.0.

Any ideas?

I don't subscribe to this list and would appreciated a CC on any
responses

Thanks in advance.

--
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/