From nobody@FreeBSD.org Sat Oct 8 08:59:27 2005 Return-Path: Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3AF1E16A41F for ; Sat, 8 Oct 2005 08:59:27 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27EE843D62 for ; Sat, 8 Oct 2005 08:59:26 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id j988xLAF093424 for ; Sat, 8 Oct 2005 08:59:21 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id j988xLXW093423; Sat, 8 Oct 2005 08:59:21 GMT (envelope-from nobody) Message-Id: <200510080859.j988xLXW093423@www.freebsd.org> Date: Sat, 8 Oct 2005 08:59:21 GMT From: Attila Nagy To: freebsd-gnats-submit@FreeBSD.org Subject: Boot problems on a 16 processor AMD64 compatible machine X-Send-Pr-Version: www-2.3 >Number: 87112 >Category: amd64 >Synopsis: Boot problems on a 16 processor AMD64 compatible machine >Confidential: no >Severity: serious >Priority: low >Responsible: peter >State: closed >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Sat Oct 08 09:00:29 GMT 2005 >Closed-Date: Sat Sep 23 20:05:45 GMT 2006 >Last-Modified: Sat Sep 23 20:05:45 GMT 2006 >Originator: Attila Nagy >Release: 7-current >Organization: FSN >Environment: Not available >Description: On a 16 processor/16 GB RAM AMD64 compatible machine FreeBSD halts with "Too many segments in the physical address map, giving up". >How-To-Repeat: I don't know whether it's general, or only limited to this machine, but trying to boot FreeBSD with 16 processors could trigger the problem. >Fix: In src/sys/amd64/amd64/machdep.c: -#define PHYSMAP_SIZE (2 * 8) +#define PHYSMAP_SIZE (2 * 16) After this: FreeBSD/SMP: Multiprocessor System Detected: 16 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 cpu8 (AP): APIC ID: 8 cpu9 (AP): APIC ID: 9 cpu10 (AP): APIC ID: 10 cpu11 (AP): APIC ID: 11 cpu12 (AP): APIC ID: 12 cpu13 (AP): APIC ID: 13 cpu14 (AP): APIC ID: 14 cpu15 (AP): APIC ID: 15 I didn't try with i386, but I guess that has the same problem. >Release-Note: >Audit-Trail: From: "AD" To: "Attila Nagy" , Cc: Subject: Re: amd64/87112: Boot problems on a 16 processor AMD64 compatiblemachine Date: Sat, 8 Oct 2005 14:35:17 +0200 What is the type of computer ? Alain ----- Original Message ----- From: "Attila Nagy" To: Sent: Saturday, October 08, 2005 10:59 AM Subject: amd64/87112: Boot problems on a 16 processor AMD64 compatiblemachine > >>Number: 87112 >>Category: amd64 >>Synopsis: Boot problems on a 16 processor AMD64 compatible machine >>Confidential: no >>Severity: serious >>Priority: low >>Responsible: freebsd-amd64 >>State: open >>Quarter: >>Keywords: >>Date-Required: >>Class: change-request >>Submitter-Id: current-users >>Arrival-Date: Sat Oct 08 09:00:29 GMT 2005 >>Closed-Date: >>Last-Modified: >>Originator: Attila Nagy >>Release: 7-current >>Organization: > FSN >>Environment: > Not available >>Description: > On a 16 processor/16 GB RAM AMD64 compatible machine FreeBSD halts with > "Too many segments in the physical address map, giving up". > >>How-To-Repeat: > I don't know whether it's general, or only limited to this machine, but > trying to boot FreeBSD with 16 processors could trigger the problem. >>Fix: > In src/sys/amd64/amd64/machdep.c: > -#define PHYSMAP_SIZE (2 * 8) > +#define PHYSMAP_SIZE (2 * 16) > > After this: > FreeBSD/SMP: Multiprocessor System Detected: 16 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 2 > cpu3 (AP): APIC ID: 3 > cpu4 (AP): APIC ID: 4 > cpu5 (AP): APIC ID: 5 > cpu6 (AP): APIC ID: 6 > cpu7 (AP): APIC ID: 7 > cpu8 (AP): APIC ID: 8 > cpu9 (AP): APIC ID: 9 > cpu10 (AP): APIC ID: 10 > cpu11 (AP): APIC ID: 11 > cpu12 (AP): APIC ID: 12 > cpu13 (AP): APIC ID: 13 > cpu14 (AP): APIC ID: 14 > cpu15 (AP): APIC ID: 15 > > I didn't try with i386, but I guess that has the same problem. >>Release-Note: >>Audit-Trail: >>Unformatted: > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > From: Attila Nagy To: AD Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: amd64/87112: Boot problems on a 16 processor AMD64 compatiblemachine Date: Sun, 09 Oct 2005 17:44:55 +0200 Sorry, I cannot tell. It's an evaluation platform with an NDA. AD wrote: > What is the type of computer ? > > Alain > ----- Original Message ----- From: "Attila Nagy" > To: > Sent: Saturday, October 08, 2005 10:59 AM > Subject: amd64/87112: Boot problems on a 16 processor AMD64 > compatiblemachine > > >> >>> Number: 87112 >>> Category: amd64 >>> Synopsis: Boot problems on a 16 processor AMD64 compatible machine >>> Confidential: no >>> Severity: serious >>> Priority: low >>> Responsible: freebsd-amd64 >>> State: open >>> Quarter: >>> Keywords: >>> Date-Required: >>> Class: change-request >>> Submitter-Id: current-users >>> Arrival-Date: Sat Oct 08 09:00:29 GMT 2005 >>> Closed-Date: >>> Last-Modified: >>> Originator: Attila Nagy >>> Release: 7-current >>> Organization: >> >> FSN >> >>> Environment: >> >> Not available >> >>> Description: >> >> On a 16 processor/16 GB RAM AMD64 compatible machine FreeBSD halts >> with "Too many segments in the physical address map, giving up". >> >>> How-To-Repeat: >> >> I don't know whether it's general, or only limited to this machine, >> but trying to boot FreeBSD with 16 processors could trigger the problem. >> >>> Fix: >> >> In src/sys/amd64/amd64/machdep.c: >> -#define PHYSMAP_SIZE (2 * 8) >> +#define PHYSMAP_SIZE (2 * 16) >> >> After this: >> FreeBSD/SMP: Multiprocessor System Detected: 16 CPUs >> cpu0 (BSP): APIC ID: 0 >> cpu1 (AP): APIC ID: 1 >> cpu2 (AP): APIC ID: 2 >> cpu3 (AP): APIC ID: 3 >> cpu4 (AP): APIC ID: 4 >> cpu5 (AP): APIC ID: 5 >> cpu6 (AP): APIC ID: 6 >> cpu7 (AP): APIC ID: 7 >> cpu8 (AP): APIC ID: 8 >> cpu9 (AP): APIC ID: 9 >> cpu10 (AP): APIC ID: 10 >> cpu11 (AP): APIC ID: 11 >> cpu12 (AP): APIC ID: 12 >> cpu13 (AP): APIC ID: 13 >> cpu14 (AP): APIC ID: 14 >> cpu15 (AP): APIC ID: 15 >> >> I didn't try with i386, but I guess that has the same problem. >> >>> Release-Note: >>> Audit-Trail: >>> Unformatted: >> >> _______________________________________________ >> freebsd-amd64@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 >> To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" >> > -- Attila Nagy e-mail: Attila.Nagy@fsn.hu Free Software Network (FSN.HU) phone: +3630 306 6758 ISOs: http://www.fsn.hu/?f=download State-Changed-From-To: open->patched State-Changed-By: linimon State-Changed-When: Fri Oct 28 21:22:21 GMT 2005 State-Changed-Why: Should be fixed by commit to sys/amd64/amd64/machdep.c by peter. http://www.freebsd.org/cgi/query-pr.cgi?pr=87112 Responsible-Changed-From-To: freebsd-amd64->peter Responsible-Changed-By: linimon Responsible-Changed-When: Fri Oct 28 21:23:34 GMT 2005 Responsible-Changed-Why: Assign as a possible MFC reminder. http://www.freebsd.org/cgi/query-pr.cgi?pr=87112 State-Changed-From-To: patched->feedback State-Changed-By: delphij State-Changed-When: Sat Sep 23 19:54:52 UTC 2006 State-Changed-Why: Because a change to solve the problem has already committed to RELENG_6, can we close this PR? http://www.freebsd.org/cgi/query-pr.cgi?pr=87112 State-Changed-From-To: feedback->closed State-Changed-By: delphij State-Changed-When: Sat Sep 23 20:05:19 UTC 2006 State-Changed-Why: Submitter confirms that the MFC has solved the issue and this PR can be closed now. http://www.freebsd.org/cgi/query-pr.cgi?pr=87112 >Unformatted: