Re: 2.6.20.7 locking up hard on boot
I can confirm that reverting commit 7639e962234c76031d1ddf436def7fd9602be560 fixes the problem. Also, there seem to be plenty of other people reporting the same boot locking: http://groups.google.com/group/fa.linux.kernel/msg/cc0453677be44a9e http://bbs.archlinux.org/viewtopic.php?pid=245313 http://bugs.archlinux.org/task/6845 http://www.usenetlinux.com/archive/topic.php/t-757515.html Please consider reverting this patch in upstream. Thank you for your time, Marcos On 4/23/07, Marcos Pinto <[EMAIL PROTECTED]> wrote: On 4/23/07, Jan Beulich <[EMAIL PROTECTED]> wrote: > Given that all of the reports are in cases when the adjustment is *not* > being done (and only a message is being printed), I can only assume that > the breakage results from the adding of PCI_BASE_ADDRESS_SPACE_IO > into the resource flags. I considered this unconditional setting of the flags > odd already in the original code, and added this extra flag only for > consistency reasons (because the settings reported by X indicated that > this was missing). Perhaps the adjustment (original and the added > extra flag) shouldn't be done if IORESOURCE_IO wasn't already set. > Perhaps one of those seeing the issue could try out returning from the > function right after that printk(), without any adjustment to the flags. > > Jan > > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20.7 locking up hard on boot
I'm honestly not sure how to try what you suggested to try, since I'm nothing even remotely close to a kernel geek and it was over my head. However, I'd gladly test anything that you think would be worth testing, if you would please put it in way that I could understand, such as "change line 'foo' in probe.c into 'foolio'" Thanks again for all of your help, Marcos On 4/23/07, Jan Beulich <[EMAIL PROTECTED]> wrote: Given that all of the reports are in cases when the adjustment is *not* being done (and only a message is being printed), I can only assume that the breakage results from the adding of PCI_BASE_ADDRESS_SPACE_IO into the resource flags. I considered this unconditional setting of the flags odd already in the original code, and added this extra flag only for consistency reasons (because the settings reported by X indicated that this was missing). Perhaps the adjustment (original and the added extra flag) shouldn't be done if IORESOURCE_IO wasn't already set. Perhaps one of those seeing the issue could try out returning from the function right after that printk(), without any adjustment to the flags. Jan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20.7 locking up hard on boot
>Considering where it failed and that 2.6.20.3 worked, I would be >extremely surprised if this wasn't one more report of >adjust-legacy-ide-resource-setting.patch breaking booting (and we >already have confirmed reports for this)... > >But AFAIK we still don't understand how this patch managed to break >things. Given that all of the reports are in cases when the adjustment is *not* being done (and only a message is being printed), I can only assume that the breakage results from the adding of PCI_BASE_ADDRESS_SPACE_IO into the resource flags. I considered this unconditional setting of the flags odd already in the original code, and added this extra flag only for consistency reasons (because the settings reported by X indicated that this was missing). Perhaps the adjustment (original and the added extra flag) shouldn't be done if IORESOURCE_IO wasn't already set. Perhaps one of those seeing the issue could try out returning from the function right after that printk(), without any adjustment to the flags. Jan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20.7 locking up hard on boot
On Saturday 21 April 2007 06:54, Marcos Pinto wrote: > It took me several hours, but I just got done combing things over with > bisect as Greg requested. This is what git spit out as the problem > patch in the end: > > 7639e962234c76031d1ddf436def7fd9602be560 is first bad commit > commit 7639e962234c76031d1ddf436def7fd9602be560 > Author: Jan Beulich <[EMAIL PROTECTED]> > Date: Tue Mar 13 14:04:11 2007 -0400 > > adjust legacy IDE resource setting (v2) > > adjust legacy IDE resource setting (v2) > > The change to force legacy mode IDE channels' resources to fixed non-zero > values confuses (at least some versions of) X, because the values reported > by the kernel and those readable from PCI config space aren't consistent > anymore. Therefore, this patch arranges for the respective BARs to also > get updated if possible. > > Signed-off-by: Jan Beulich <[EMAIL PROTECTED]> > Acked-by: Alan Cox <[EMAIL PROTECTED]> > Signed-off-by: Andrew Morton <[EMAIL PROTECTED]> > Signed-off-by: Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]> > Cc: Chuck Ebbert <[EMAIL PROTECTED]> > Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]> > > :04 04 d4ee6822208dc3e205bfc92fd30121e7894e63a9 > 5155044aa75f0d2671e7f5081f5b2999f24034bd M drivers > bisect run success > Looks like others are seeing failures due to this patch also: http://bugzilla.kernel.org/show_bug.cgi?id=7562 -Len - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20.7 locking up hard on boot
On Saturday 21 April 2007, Adrian Bunk wrote: > On Fri, Apr 20, 2007 at 10:34:20PM -0700, Greg KH wrote: > > On Fri, Apr 20, 2007 at 11:30:59PM -0500, Marcos Pinto wrote: > > > Yes, I just tried 2.6.20.3 with ACPI enabled and it booted perfectly. > > > I'm hoping this means you know what's wrong? :-) > > > > Can you do a 'git bisect' on the versions between 2.6.20.3 and 2.6.20.7 > > to try to find the problem patch? > > Considering where it failed and that 2.6.20.3 worked, I would be > extremely surprised if this wasn't one more report of > adjust-legacy-ide-resource-setting.patch breaking booting (and we > already have confirmed reports for this)... > > But AFAIK we still don't understand how this patch managed to break > things. Same here but 2.6.21 is near and we need to do something about this issue. I'm thinking about reverting this patch for 2.6.21-final - having broken X server is better than having broken and not booting kernel. Jan, Alan? Thanks, Bart - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20.7 locking up hard on boot
It took me several hours, but I just got done combing things over with bisect as Greg requested. This is what git spit out as the problem patch in the end: 7639e962234c76031d1ddf436def7fd9602be560 is first bad commit commit 7639e962234c76031d1ddf436def7fd9602be560 Author: Jan Beulich <[EMAIL PROTECTED]> Date: Tue Mar 13 14:04:11 2007 -0400 adjust legacy IDE resource setting (v2) adjust legacy IDE resource setting (v2) The change to force legacy mode IDE channels' resources to fixed non-zero values confuses (at least some versions of) X, because the values reported by the kernel and those readable from PCI config space aren't consistent anymore. Therefore, this patch arranges for the respective BARs to also get updated if possible. Signed-off-by: Jan Beulich <[EMAIL PROTECTED]> Acked-by: Alan Cox <[EMAIL PROTECTED]> Signed-off-by: Andrew Morton <[EMAIL PROTECTED]> Signed-off-by: Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]> Cc: Chuck Ebbert <[EMAIL PROTECTED]> Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]> :04 04 d4ee6822208dc3e205bfc92fd30121e7894e63a9 5155044aa75f0d2671e7f5081f5b2999f24034bd M drivers bisect run success Please let me know if there's more that I can do. Thank you, Marcos On 4/21/07, Adrian Bunk <[EMAIL PROTECTED]> wrote: On Fri, Apr 20, 2007 at 10:34:20PM -0700, Greg KH wrote: > On Fri, Apr 20, 2007 at 11:30:59PM -0500, Marcos Pinto wrote: > > Yes, I just tried 2.6.20.3 with ACPI enabled and it booted perfectly. > > I'm hoping this means you know what's wrong? :-) > > Can you do a 'git bisect' on the versions between 2.6.20.3 and 2.6.20.7 > to try to find the problem patch? Considering where it failed and that 2.6.20.3 worked, I would be extremely surprised if this wasn't one more report of adjust-legacy-ide-resource-setting.patch breaking booting (and we already have confirmed reports for this)... But AFAIK we still don't understand how this patch managed to break things. > thanks, > > greg k-h cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20.7 locking up hard on boot
On Fri, Apr 20, 2007 at 10:34:20PM -0700, Greg KH wrote: > On Fri, Apr 20, 2007 at 11:30:59PM -0500, Marcos Pinto wrote: > > Yes, I just tried 2.6.20.3 with ACPI enabled and it booted perfectly. > > I'm hoping this means you know what's wrong? :-) > > Can you do a 'git bisect' on the versions between 2.6.20.3 and 2.6.20.7 > to try to find the problem patch? Considering where it failed and that 2.6.20.3 worked, I would be extremely surprised if this wasn't one more report of adjust-legacy-ide-resource-setting.patch breaking booting (and we already have confirmed reports for this)... But AFAIK we still don't understand how this patch managed to break things. > thanks, > > greg k-h cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20.7 locking up hard on boot
On Fri, Apr 20, 2007 at 11:30:59PM -0500, Marcos Pinto wrote: > Yes, I just tried 2.6.20.3 with ACPI enabled and it booted perfectly. > I'm hoping this means you know what's wrong? :-) Can you do a 'git bisect' on the versions between 2.6.20.3 and 2.6.20.7 to try to find the problem patch? thanks, greg k-h - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20.7 locking up hard on boot
Yes, I just tried 2.6.20.3 with ACPI enabled and it booted perfectly. I'm hoping this means you know what's wrong? :-) Thanks again, Marcos On 4/20/07, Adrian Bunk <[EMAIL PROTECTED]> wrote: On Fri, Apr 20, 2007 at 07:47:13PM -0500, Marcos Pinto wrote: > I'm not subscribed, so please personally CC me any answers/comments. > Thank you. > > While booting, (AMD64 Turion x2) 2.6.20.7 kernel locks up hard. The > last kernel that I tried, 2.6.18.8, worked perfectly without any > trickery. 2.6.20.7 only boots up with "acpi=off" being added to the > kernel line. Note that 2.6.18.8 works perfectly with acpi on, which > is really the > only way I can run this box because with "acpi=off" it overheats and > freezes. > Please let me know if there's anything else that I could do to help with > this. > > > Here's what's on the screen when it happens: > > Brought up 2 CPUs > testing NMI watchdog ... OK. > Disabling vsyscall due to use of PM timer > time.c: Using 3.579545 MHz WALL PM GTOD PM timer. > time.c: Detected 1808.264 MHz processor. > migration_cost=281 > NET: Registered protocol family 16 > ACPI: bus type pci registered > PCI: Using MMCONFIG at e000 > PCI: No mmconfig possible on device 00:18 > PCI: No mmconfig possible on device 07:05 > ACPI: Interpreter enabled > ACPI: Using IOAPIC for interrupt routing > ACPI: PCI Root Bridge [PCI0] (:00) > ACPI: Assume root bridge [\_SB_.PCI0] bus is 0 > :00:0d.0: cannot adjust BAR0 (not I/O) > :00:0d.0: cannot adjust BAR1 (not I/O) >... Does 2.6.20.3 boot with ACPI enabled? cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20.7 locking up hard on boot
On Fri, Apr 20, 2007 at 07:47:13PM -0500, Marcos Pinto wrote: > I'm not subscribed, so please personally CC me any answers/comments. > Thank you. > > While booting, (AMD64 Turion x2) 2.6.20.7 kernel locks up hard. The > last kernel that I tried, 2.6.18.8, worked perfectly without any > trickery. 2.6.20.7 only boots up with "acpi=off" being added to the > kernel line. Note that 2.6.18.8 works perfectly with acpi on, which > is really the > only way I can run this box because with "acpi=off" it overheats and > freezes. > Please let me know if there's anything else that I could do to help with > this. > > > Here's what's on the screen when it happens: > > Brought up 2 CPUs > testing NMI watchdog ... OK. > Disabling vsyscall due to use of PM timer > time.c: Using 3.579545 MHz WALL PM GTOD PM timer. > time.c: Detected 1808.264 MHz processor. > migration_cost=281 > NET: Registered protocol family 16 > ACPI: bus type pci registered > PCI: Using MMCONFIG at e000 > PCI: No mmconfig possible on device 00:18 > PCI: No mmconfig possible on device 07:05 > ACPI: Interpreter enabled > ACPI: Using IOAPIC for interrupt routing > ACPI: PCI Root Bridge [PCI0] (:00) > ACPI: Assume root bridge [\_SB_.PCI0] bus is 0 > :00:0d.0: cannot adjust BAR0 (not I/O) > :00:0d.0: cannot adjust BAR1 (not I/O) >... Does 2.6.20.3 boot with ACPI enabled? cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
