[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20080419000144.GA24486@sgi.com>
Date: Fri, 18 Apr 2008 19:01:44 -0500
From: Jack Steiner <steiner@....com>
To: Yinghai Lu <yhlu.kernel@...il.com>
Cc: Ingo Molnar <mingo@...e.hu>, tglx@...utronix.de,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
"H. Peter Anvin" <hpa@...or.com>, mike travis <travis@....com>
Subject: Re: [PATCH] - Increase MAX_APICS for large configs
On Fri, Apr 18, 2008 at 03:01:43PM -0700, Yinghai Lu wrote:
> On Fri, Apr 18, 2008 at 2:14 PM, Jack Steiner <steiner@....com> wrote:
> > On Thu, Apr 17, 2008 at 01:07:27PM +0200, Ingo Molnar wrote:
> > >
> > > * Jack Steiner <steiner@....com> wrote:
> > >
> > > > Increase the maximum number of apics when running very large
> > > > configurations. This patch has no affect on most systems.
> > >
> > > x86.git overnight random-qa testing found a boot crash and i bisected it
> > > down to this patch. The config is:
> > >
> > > http://redhat.com/~mingo/misc/config-Thu_Apr_17_10_17_14_CEST_2008.bad
> > >
> > > the failure is attached below. (I needed the exact boot parameters
> > > listed in that bootup log to see this failure.)
> > >
> > > it seems to be CONFIG_MAXSMP=y triggers the new more-apic-ids code and
> > > that causes some breakage elsewhere. [btw., this again shows how useful
> > > the CONFIG_MAXSMP debug feature is!]
> > >
> > > Ingo
> > >
> > > [ 0.000000] Linux version 2.6.25-rc9-sched-devel.git-x86-latest.git (mingo@...ne) (gcc version 4.2.3) #260 SMP Thu Apr 17 10:58:11 CEST 2008
> > > [ 0.000000] Command line: root=/dev/sda6 console=ttyS0,115200 earlyprintk=serial,ttyS0,115200 debug initcall_debug apic=verbose sysrq_always_enabled ignore_loglevel selinux=0 nmi_watchdog=2 profile=0 nosmp highres=0 nolapic_timer hpet=disable idle=poll highmem=512m nopat acpi=off
> > > [ 0.000000] BIOS-provided physical RAM map:
> >
> > Has anyone seen this failure?? (Using git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git
> > from 4/18 AM).
> >
> > I tried to reproduce the above failure on a small system & was not successful.
> >
> > Switched to a larger system (XE310 Intel-based 8p, 6GB). All attempts to boot fail
> > with the following. I backed out the MAX_APIC change, & changed NR_CPUS=8. Still fails.
> >
> > ...
> > [ 32.010000] ehci_hcd 0000:00:1d.7: port 6 high speed
> > [ 32.010000] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001005 POWER sig=se0 PE CONNECT
> > [ 32.054003] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
> > [ 32.058003] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> > [ 32.062003] usb usb2: Product: UHCI Host Controller
> > [ 32.066004] usb usb2: Manufacturer: Linux 2.6.25-x86-latest.git uhci_hcd
> > [ 32.070004] usb usb2: SerialNumber: 0000:00:1d.0
> > [ 32.074004] PCI: Found IRQ 10 for device 0000:00:1d.1
> > [ 32.078004] PCI: Sharing IRQ 10 with 0000:00:1f.2
> > [ 32.082005] PCI: Sharing IRQ 10 with 0000:00:1f.3
> > [ 32.086005] PCI: Sharing IRQ 10 with 0000:04:00.1
> > [ 32.090005] PCI: Setting latency timer of device 0000:00:1d.1 to 64
> > [ 32.094005] uhci_hcd 0000:00:1d.1: UHCI Host Controller
> > [ 32.098006] usb 1-6: new high speed USB device using ehci_hcd and address 2
> > [ 32.102006] nommu_map_single: overflow 1af757720+8
> >
> > Full log:
> >
> >
> > [ 0.000000] Linux version 2.6.25-x86-latest.git (root@...opatra1) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-52)) #2 SMP Fri Apr 18 09:36:33 CDT 2008
> > [ 0.000000] Command line: root=/dev/sda2 console=ttyS1,38400n8 debug initcall_debug apic=verbose sysrq_always_enabled ignore_loglevel selinux=0 nmi_watchdog=2 profile=0 nosmp highres=0 nolapic_timer hpet=disable idle=poll highmem=512m nopat acpi=off
>
> how about without acpi=off?
>
> can you make sure acpi=off works with previous kernel in that box?
Old kernels work with & without "acpi=off".
New kernels fail with & without "acpi=off".
I'll start to narrow down the exact config/boot options that are causing the
failure.
--- jack
--
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