On Fri, Dec 09, 2011 at 02:41:16PM +0100, Manuel Bouyer wrote:
On Thu, Dec 08, 2011 at 11:24:35PM +0100, Nicolas Joly wrote:
On Thu, Dec 08, 2011 at 11:21:31PM +0100, Joerg Sonnenberger wrote:
On Thu, Dec 08, 2011 at 11:10:41PM +0100, Nicolas Joly wrote:
I do have two machines that fail
On Fri, Dec 09, 2011 at 03:22:45PM +0100, Nicolas Joly wrote:
On Fri, Dec 09, 2011 at 02:41:16PM +0100, Manuel Bouyer wrote:
On Thu, Dec 08, 2011 at 11:24:35PM +0100, Nicolas Joly wrote:
On Thu, Dec 08, 2011 at 11:21:31PM +0100, Joerg Sonnenberger wrote:
On Thu, Dec 08, 2011 at
On Fri, Dec 09, 2011 at 03:30:38PM +0100, Manuel Bouyer wrote:
I'd like to see what mem_clusters[] looks like, especially
mem_clusters[mem_cluster_cnt - 1]
Added the printfs at the end of initx86_parse_memmap(), and got this:
mem_cluster_cnt = 3
0 addr 0x0 size 0x93000
1 addr 0x10
On Fri, Dec 09, 2011 at 03:52:21PM +0100, Nicolas Joly wrote:
On Fri, Dec 09, 2011 at 03:30:38PM +0100, Manuel Bouyer wrote:
I'd like to see what mem_clusters[] looks like, especially
mem_clusters[mem_cluster_cnt - 1]
Added the printfs at the end of initx86_parse_memmap(), and got this:
I found a system which had the crash-at-boot problem and
the change I just checked in fixed it on that box.
if anyone is still seeing crashes with that fix, please let me know.
-Chuck
On Thu, Dec 08, 2011 at 07:47:07AM -0800, Chuck Silvers wrote:
I got another report yesterday morning that this is causing problems.
from the info I've gotten from the other person so far, I'm at a loss
to explain why this doesn't work for some people. I've added back
some code to allow
On Thu, Dec 08, 2011 at 11:10:41PM +0100, Nicolas Joly wrote:
That was me.
I do have two machines that fail to boot with this change.
1) A Dell Optiplex 740 that reboots early after loading the kernel.
Includes 1 AMD Athlon(tm) 64 X2 Dual Core Processor 4800+ CPU.
2) A Supermicro
On Thu, Dec 08, 2011 at 11:10:41PM +0100, Nicolas Joly wrote:
I do have two machines that fail to boot with this change.
1) A Dell Optiplex 740 that reboots early after loading the kernel.
Includes 1 AMD Athlon(tm) 64 X2 Dual Core Processor 4800+ CPU.
2) A Supermicro H8DG6-F motherboard
On 08.12.11 23:17, Manuel Bouyer wrote:
On Thu, Dec 08, 2011 at 11:10:41PM +0100, Nicolas Joly wrote:
That was me.
I do have two machines that fail to boot with this change.
1) A Dell Optiplex 740 that reboots early after loading the kernel.
Includes 1 AMD Athlon(tm) 64 X2 Dual Core
On Thu, Dec 08, 2011 at 11:21:31PM +0100, Joerg Sonnenberger wrote:
On Thu, Dec 08, 2011 at 11:10:41PM +0100, Nicolas Joly wrote:
I do have two machines that fail to boot with this change.
1) A Dell Optiplex 740 that reboots early after loading the kernel.
Includes 1 AMD Athlon(tm) 64
On Thu, Dec 08, 2011 at 11:17:54PM +0100, Manuel Bouyer wrote:
On Thu, Dec 08, 2011 at 11:10:41PM +0100, Nicolas Joly wrote:
That was me.
I do have two machines that fail to boot with this change.
1) A Dell Optiplex 740 that reboots early after loading the kernel.
Includes 1 AMD
On Thu, Dec 08, 2011 at 07:47:07AM -0800, Chuck Silvers wrote:
I'd like to leave the direct-map stuff enabled for now so we can
gather some more data on where it works and where it doesn't.
if you (and anyone who sees this problem) could send me the output from
dmesg and cpuctl identify,
12 matches
Mail list logo
