Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754612AbZCNE1J (ORCPT ); Sat, 14 Mar 2009 00:27:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752480AbZCNE0z (ORCPT ); Sat, 14 Mar 2009 00:26:55 -0400 Received: from rv-out-0506.google.com ([209.85.198.238]:61257 "EHLO rv-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751682AbZCNE0y convert rfc822-to-8bit (ORCPT ); Sat, 14 Mar 2009 00:26:54 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=szn76hVEG8ntlqVxRpWsNeLxpXhRgYm5AxoJxC/lvbB8eVE+1rOP9HmmjwxSYi4+f6 5WF0awgvN+sNYNYKM+/sLbCYz12mG7pJx6qIljy6JhwB+YmN567yu2+hydS/AE4hMO9R GXV6YmFQWEAi/InP87LXqMUhm/BZgbO8CJHqs= MIME-Version: 1.0 In-Reply-To: <49BB172D.5060609@gmail.com> References: <200903131642.54925.gene.heskett@gmail.com> <49BB172D.5060609@gmail.com> Date: Fri, 13 Mar 2009 21:26:51 -0700 X-Google-Sender-Auth: 68a6265b37b8f1a1 Message-ID: <86802c440903132126w3738533dn8db7302f202dc4be@mail.gmail.com> Subject: Re: New ASUS 1701 bios for M2N SLI DELUXE From: Yinghai Lu To: Robert Hancock Cc: Gene Heskett , Robin.Laing@drdc-rddc.gc.ca, LKML , David Newall Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 4091 Lines: 89 On Fri, Mar 13, 2009 at 7:32 PM, Robert Hancock wrote: > Gene Heskett wrote: >> >> Hi Robin, David and lkml list; >> >> I said I would report. >> >> I just reinstalled the 1502 version bios after spending the last 2 days >> trying to get an hours worth of uptime without an oops. ?Gave up. >> >> David Newell and I have been trying to find the cause of the oops, but >> when the compile instructions David is sending me don't work, its a bit >> difficult to troubleshoot beyond renaming the function just to see if the >> oops follows the rename, which it does. ?And with the boot girations >> to get a working radeonhd driver now broken again, apparently by the 'make >> mrproper' that David had me do, I'm now stuck on issue drivers for drm, >> radeon, and radeonhd and those are noticably slower. >> >> So I'm back on the 1502 version of the bios, it does an oops as I sent >> before right at entering vmlinuz, which marks me tainted, but the machine is >> dead stable after that. >> >> Here is another snip of that to refresh memories: >> [ ? ?0.000000] DMI 2.4 present. >> [ ? ?0.000000] Phoenix BIOS detected: BIOS may corrupt low RAM, working it >> around. >> [ ? ?0.000000] last_pfn = 0x120000 max_arch_pfn = 0x1000000 >> [ ? ?0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new >> 0x7010600070106 >> [ ? ?0.000000] ------------[ cut here ]------------ >> [ ? ?0.000000] WARNING: at arch/x86/kernel/cpu/mtrr/generic.c:404 >> generic_get_mtrr+0xea/0x120() >> [ ? ?0.000000] mtrr: your BIOS has set up an incorrect mask, fixing it up. >> [ ? ?0.000000] Modules linked in: >> [ ? ?0.000000] Pid: 0, comm: swapper Not tainted 2.6.28.7 #7 >> [ ? ?0.000000] Call Trace: >> [ ? ?0.000000] ?[] warn_slowpath+0x6f/0x90 >> [ ? ?0.000000] ?[] vsnprintf+0x3c0/0x7e0 >> [ ? ?0.000000] ?[] panic+0x15/0xee >> [ ? ?0.000000] ?[] pat_init+0x7c/0xa0 >> [ ? ?0.000000] ?[] post_set+0x1c/0x50 >> [ ? ?0.000000] ?[] dmi_string_nosave+0x4c/0x6d >> [ ? ?0.000000] ?[] up+0x11/0x40 >> [ ? ?0.000000] ?[] generic_get_mtrr+0xea/0x120 >> [ ? ?0.000000] ?[] mtrr_trim_uncached_memory+0x7d/0x374 >> [ ? ?0.000000] ?[] request_resource+0xa3/0x150 >> [ ? ?0.000000] ?[] printk+0x17/0x1f >> [ ? ?0.000000] ?[] e820_end_pfn+0xb5/0xd3 >> [ ? ?0.000000] ?[] setup_arch+0x501/0xb68 >> [ ? ?0.000000] ?[] release_console_sem+0x189/0x1d0 >> [ ? ?0.000000] ?[] reserve_early_overlap_ok+0x3f/0x47 >> [ ? ?0.000000] ?[] start_kernel+0x58/0x314 >> [ ? ?0.000000] ---[ end trace 4eaa2a86a8e2da22 ]--- > > That's not an oops, it's a warning. Those do normally taint the kernel. I > don't think this should really be a WARN, IMHO, as it's a BIOS bug and not > the kernel's fault, and it's fixed up the problem. CCing Yinghai Lu, which > it looks like wrote this warning. need to tone down the warning? > >> >> So based on that, I'll now go build a 2.6.29-rc8 and see how that runs. >> >> The biggest problem with the 2.6.29 series is that apparently, for >> security reasons, they are now doing a PHY disable in a graceful shutdown, >> which none of the previous kernels knows how to re-enable. >> >> So to reboot to the 2.6.28.7 stable, you have to use the front panel reset >> button to reboot or you will not have any onboard ethernet until you do a >> full, pull ALL the power plugs for at least 30 seconds (I go make a cup of >> tea, about 3 minutes) to reset the PHY's back to operational status. TBT, >> the reset button is easier. >> >> Frankly, that seems like a thoroughly busted security idea, but I suppose >> we're stuck with it. > > I doubt it's for security reasons. Could be due to power management or > suspend/resume changes? what is nic? could be put in D3 somehow. YH -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/