On Sunday, 31 of August 2008, Yinghai Lu wrote: > On Sat, Aug 30, 2008 at 2:34 PM, Rafael J. Wysocki <rjw@xxxxxxx> wrote: > > On Saturday, 30 of August 2008, Yinghai Lu wrote: > >> On Sat, Aug 30, 2008 at 2:12 PM, Yinghai Lu <yhlu.kernel@xxxxxxxxx> wrote: > >> > On Sat, Aug 30, 2008 at 1:46 PM, Rafael J. Wysocki <rjw@xxxxxxx> wrote: > >> >> On Saturday, 30 of August 2008, Yinghai Lu wrote: > >> >>> please check > >> >>> > >> >>> [PATCH] x86: split e820 reserved entries record to late v4 > >> >>> [PATCH] x86: split e820 reserved entries record to late v4 - fix v6 > >> >> > >> >> What kernel should I apply those to and in what order? > >> > > >> > linus git tree > >> > 1. [PATCH] x86: split e820 reserved entries record to late v4 > >> > 2. [PATCH] x86: split e820 reserved entries record to late v4 - fix v6 > >> > > >> > tip/master > >> > 1. Resource handling: add 'insert_resource_expand_to_fit()' function > >> > 2. [PATCH] x86: split e820 reserved entries record to late v4 - fix v6 > >> > >> actually it is almost the same to tar ball send you for your system... > > > > I've just tested these two patches on top of the current Linus' tree and the > > system works normally. > > > > Can you try attached in addition to those to patches ? > > want to check if the BAR3 get new resource..., and after that what > could happen... Works, dmesg is at: http://www.sisk.pl/kernel/debug/mainline/2.6.27-rc5/2.6.27-rc5-test.log Please let me know if you want it with any more command line options. Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
