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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 13 Dec 2006 15:00:03 -0800 (PST)
From:	dean gaudet <dean@...tic.org>
To:	Chris Wright <chrisw@...s-sol.org>
cc:	Jan Beulich <jbeulich@...ell.com>, Dave Jones <davej@...hat.com>,
	Zwane Mwaikambo <zwane@....linux.org.uk>,
	Michael Buesch <mb@...sch.de>,
	Metathronius Galabant <m.galabant@...glemail.com>,
	stable@...nel.org, Michael Krufky <mkrufky@...uxtv.org>,
	Justin Forbes <jmforbes@...uxtx.org>, alan@...rguk.ukuu.org.uk,
	Theodore Ts'o <tytso@....edu>,
	Chris Wedgwood <reviews@...cw.f00f.org>, akpm@...l.org,
	torvalds@...l.org, Chuck Wolber <chuckw@...ntumlinux.com>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	linux-kernel@...r.kernel.org, Randy Dunlap <rdunlap@...otime.net>
Subject: Re: [stable] [PATCH 46/61] fix Intel RNG detection

On Wed, 13 Dec 2006, Chris Wright wrote:

> * dean gaudet (dean@...tic.org) wrote:
> > just for the public record (i already communicated with Jan in private 
> > mail on this one)... i have a box which hangs hard starting at 2.6.18.2 
> > and 2.6.19 -- hangs hard during the intel hw rng tests (no sysrq 
> > response).  and the hang occurs prior to the printk so it took some 
> > digging to figure out which module was taking out the system.
> > 
> > Jan's patch gets the box past the hang... it seems like this should be in 
> > at least the next 2.6.19.x stable (and if there's going to be another 
> > 2.6.18.x stable then it should be included there as well).
> 
> Thanks for the data point.  I wonder if you get SMI and never come back.
> Do you boot with no_fwh_detect=1 or -1?

with the patch it boots perfectly without any command-line args.

without the patch it crashes after the "4" and before the "5" in this 
hacked up segment of the code:

        if (!(fwh_dec_en1_val & FWH_F8_EN_MASK))
                pci_write_config_byte(dev,
                                      fwh_dec_en1_off,
                                      fwh_dec_en1_val | FWH_F8_EN_MASK);
        if (!(bios_cntl_val &
              (BIOS_CNTL_LOCK_ENABLE_MASK|BIOS_CNTL_WRITE_ENABLE_MASK)))
                pci_write_config_byte(dev,
                                      bios_cntl_off,
                                      bios_cntl_val | BIOS_CNTL_WRITE_ENABLE_MASK);

        printk(KERN_INFO "intel-rng: 4\n");
        writeb(INTEL_FWH_RESET_CMD, mem);
        printk(KERN_INFO "intel-rng: 5\n");

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