[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080117202538.GB7059@balbir.in.ibm.com>
Date: Fri, 18 Jan 2008 01:55:38 +0530
From: Balbir Singh <balbir@...ux.vnet.ibm.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org,
Linux ACPI mailing list <linux-acpi@...r.kernel.org>,
Intel E/100 mailing list <e1000-devel@...ts.sourceforge.net>,
Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>,
Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>
Subject: Re: 2.6.24-rc8-mm1
* Andrew Morton <akpm@...ux-foundation.org> [2008-01-17 10:40:21]:
> On Thu, 17 Jan 2008 18:16:22 +0530 Balbir Singh <balbir@...ux.vnet.ibm.com> wrote:
>
> > * Andrew Morton <akpm@...ux-foundation.org> [2008-01-17 02:35:14]:
> >
> > >
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc8/2.6.24-rc8-mm1/
> > >
> > > - selinux is busted on one of my two selinux-enabled test machines.
> > >
> > > - suspend-to-ram and suspend-to-disk are totally hosed on one of my test
> > > machines. I guess I get to bisect this.
> > >
> > > - git-nfsd is dropped due to conflicts with git-nfs
> > >
> > > - git-newsetup is dropped due to conflicts with git-x86 (I think)
> > >
> > > - git-perfmon is dropped due to conflicts with git-x86 (I think)
> > >
> > > - git-kgdb is dropped due to conflicts with git-damn-near-everything
> > >
> > > - git-block is dropped due to conflicts with the IDE tree
> > >
> > > - kvm probably doesn't work properly because I couldn't be bothered fixing
> > > the conflicts between git-kvm and the driver tree
> > >
> > > - the volume of rejects and build errors which are caused by subsystem
> > > maintainers fiddling with other people's stuff is quite out of control.
> > > Something needs to happen here.
> >
> > Hi, Andrew,
> >
> > May be it was one of the conflicts, but my system fails to get
> > ethernet working with this version. I see
> >
> > e100: Intel(R) PRO/100 Network Driver, 3. 5.23-k4-NAPI
> > e100: Copyright(c) 1999-2006 Intel Corporation
> > ACPI: PCI Interrupt 0000:04:08.0[A] -> GSI 20 (level, low) -> IRQ 20
> > modprobe:2584 conflicting cache attribute 50000000-50001000
> > uncached<->default
> > e100: 0000:04:08.0: e100_probe: Cannot map device registers, aborting.
> > ACPI: PCI interrupt for device 0000:04:08.0 disabled
> > e100: probe of 0000:04:08.0 failed with error -12
> >
> > Other interesting boot information
> >
> > Using ACPI (MADT) for SMP configuration information
> > PM: Registered nosave memory: 000000000008f000 - 00000000000a0000
> > PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000
> > PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
> > PM: Registered nosave memory: 000000003e5d1000 - 000000003e6e5000
> > PM: Registered nosave memory: 000000003f574000 - 000000003f57c000
> > PM: Registered nosave memory: 000000003f62d000 - 000000003f631000
> > PM: Registered nosave memory: 000000003f6a7000 - 000000003f6e9000
> > PM: Registered nosave memory: 000000003f6ed000 - 000000003f6ff000
> > Allocating PCI resources starting at 50000000 (gap: 40000000:bff80000)
> >
> > PCI: Bridge: 0000:00:1c.0
> > IO window: disabled.
> > MEM window:
> > 0x50300000-0x503fffff
> > PREFETCH window: disabled.
> > PCI: Bridge: 0000:00:1c.2
> > IO window: disabled.
> > MEM window:
> > 0x50400000-0x504fffff
> > PREFETCH window: disabled.
> > PCI: Bridge: 0000:00:1c.3
> > IO window: disabled.
> > MEM window:
> > 0x50500000-0x505fffff
> > PREFETCH window: disabled.
> > PCI: Bridge: 0000:00:1e.0
> > IO window: 1000-1fff
> > MEM window:
> > 0x50000000-0x500fffff
> > PREFETCH window: disabled.
> >
> > I am yet to get down to the root cause, thought I'd report it first to
> > the x86 and ACPI list to see if someone has seen the problem before.
> >
>
> It appears that the new PAT code didn't like e100's pci_iomap(). Venki, can you
> take a look please?
>
I tried booting with nopat with no effect.
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
--
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