Re: 2.6.24-rc3-mm1 - brick my Dell Latitude D820
* Andrew Morton <[EMAIL PROTECTED]> wrote: > Otherwise, please proceed to work out which diff I need to drop and > hope like hell that it isn't git-x86.. hm? x86.git is fully bisectable - so a more accurate statement would be "and hope that it's x86.git, so that it can be properly bisected" :-) For x86.git bisection, pull the 'mm' branch from: git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git Ingo - 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.24-rc3-mm1 - brick my Dell Latitude D820
On Tue, 27 Nov 2007 16:25:22 +0800, Dave Young said: > does boot_delay helps? It might, if the kernel lived long enough to output a first printk for us to delay after. :) Shooting this one would be *easy* if the problem was an boot-time oops that would otherwise scroll off the screen without a boot_delay... pgpqJlvYAN6Ou.pgp Description: PGP signature
Re: 2.6.24-rc3-mm1 - brick my Dell Latitude D820
On Nov 27, 2007 3:16 PM, <[EMAIL PROTECTED]> wrote: > On Tue, 20 Nov 2007 20:45:25 PST, Andrew Morton said: > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc3/2.6.24-rc3-mm1/ > > Finally got both time and motivation to at least start a bisect.. > > 2.6.23-mm1 works on my D820 (x86_64 kernel, Core2 Duo T7200) > > 24-rc3-mm1 (plus 3 patches from hotfixes/) bricks *instantly* at boot - grub > prints its 3 or 4 lines saying what it loaded, the screen clears, and *blam* > dead. No serial console output, no pair of penguins on the monitor, no > netconsole, no earlyprintk=vga output, no alt-sysrq, only thing that does > *anything* is "hold the power button for 5 seconds". Whatever it is, it > happens *very* early (before we get as far as the 'Linux version 2.6.mumble' > banner), and happens *hard*. > > I've bisected it down this far: > > git-ipwireless_cs.patch GOOD > git-x86.patch > git-x86-fixup.patch > git-x86-thread_order-borkage.patch > git-x86-thread_order-borkage-fix.patch > git-x86-identify_cpu-fix.patch > git-x86-memory_add_physaddr_to_nid-export-for-acpi-memhotplugko.patch > git-x86-memory_add_physaddr_to_nid-export-for-acpi-memhotplugko-checkpatch-fixes.patch > git-x86-inlining-borkage.patch > x86_64-set-cpu_index-to-nr_cpus-instead-of-0.patch > x86_64-make-sparsemem-vmemmap-the-default-memory-model-v2.patch BAD > > Anybody got any good debugging ideas before I go through and do the final > 3 or 4 bisects? I suspect I'll need them once I find the offending patch > to tell *why* said patch dies on my box - I've seen enough traffic regarding > -rc3-mm1 dying *later* to know it's probably a subtle issue and not one > that will be obvious once I finger a specific patch. For example, it's > probably not the IO-APIC panic that people are seeing, because their kernels > live long enough to panic. ;) Hi, does boot_delay helps? Regards dave - 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.24-rc3-mm1 - brick my Dell Latitude D820
On Tue, 27 Nov 2007 02:54:56 -0500 [EMAIL PROTECTED] wrote: > On Mon, 26 Nov 2007 23:27:03 PST, Andrew Morton said: > > > > git-x86.patch > > > git-x86-fixup.patch > > > git-x86-thread_order-borkage.patch > > > git-x86-thread_order-borkage-fix.patch > > > git-x86-identify_cpu-fix.patch > > > git-x86-memory_add_physaddr_to_nid-export-for-acpi-memhotplugko.patch > > > git-x86-memory_add_physaddr_to_nid-export-for-acpi-memhotplugko-checkpatch-fixes.patch > > > git-x86-inlining-borkage.patch > > > x86_64-set-cpu_index-to-nr_cpus-instead-of-0.patch > > > x86_64-make-sparsemem-vmemmap-the-default-memory-model-v2.patch BAD > > > You could try http://userweb.kernel.org/~akpm/mmotm/ - we might have already > > fixed it. > > I suspect that trying -rc3-mm1 but refreshing just the 10 patches above > from -mmotm would be far less likely to pull in other heartburn? All the above are no longer in -mm. They got merged, dropped, otherwise-fixed, etc. > > Otherwise, please proceed to work out which diff I need to drop and hope > > like > > hell that it isn't git-x86.. > > That's a 41,240 line diff, the rest *total* to about 400 lines. I don't have > warm-n-fuzzies about my odds here. ;) No. > I'm a git-idiot, but *do* know how to git-bisect through Linus tree - what > would I need to do to git-bisect through git-x86.patch? (I do *not* know how > to deal with more than 1 source git tree, so if the magic is just 'get a > linus tree, merge git-x86, then bisect as usual", I'm stuck on "merge > git-x86").. umm, I'm minimally git-afflicted hence am the wrong person to ask. Something like: - checkout Linus's tree - echo 'git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git#mm' > .git/branches/git-x86 - git-fetch git-x86 - git-checkout git-x86 - start bisecting. - 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.24-rc3-mm1 - brick my Dell Latitude D820
On Tue, 27 Nov 2007 02:54:56 -0500 [EMAIL PROTECTED] wrote: On Mon, 26 Nov 2007 23:27:03 PST, Andrew Morton said: git-x86.patch git-x86-fixup.patch git-x86-thread_order-borkage.patch git-x86-thread_order-borkage-fix.patch git-x86-identify_cpu-fix.patch git-x86-memory_add_physaddr_to_nid-export-for-acpi-memhotplugko.patch git-x86-memory_add_physaddr_to_nid-export-for-acpi-memhotplugko-checkpatch-fixes.patch git-x86-inlining-borkage.patch x86_64-set-cpu_index-to-nr_cpus-instead-of-0.patch x86_64-make-sparsemem-vmemmap-the-default-memory-model-v2.patch BAD You could try http://userweb.kernel.org/~akpm/mmotm/ - we might have already fixed it. I suspect that trying -rc3-mm1 but refreshing just the 10 patches above from -mmotm would be far less likely to pull in other heartburn? All the above are no longer in -mm. They got merged, dropped, otherwise-fixed, etc. Otherwise, please proceed to work out which diff I need to drop and hope like hell that it isn't git-x86.. That's a 41,240 line diff, the rest *total* to about 400 lines. I don't have warm-n-fuzzies about my odds here. ;) No. I'm a git-idiot, but *do* know how to git-bisect through Linus tree - what would I need to do to git-bisect through git-x86.patch? (I do *not* know how to deal with more than 1 source git tree, so if the magic is just 'get a linus tree, merge git-x86, then bisect as usual, I'm stuck on merge git-x86).. umm, I'm minimally git-afflicted hence am the wrong person to ask. Something like: - checkout Linus's tree - echo 'git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git#mm' .git/branches/git-x86 - git-fetch git-x86 - git-checkout git-x86 - start bisecting. - 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.24-rc3-mm1 - brick my Dell Latitude D820
On Nov 27, 2007 3:16 PM, [EMAIL PROTECTED] wrote: On Tue, 20 Nov 2007 20:45:25 PST, Andrew Morton said: ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc3/2.6.24-rc3-mm1/ Finally got both time and motivation to at least start a bisect.. 2.6.23-mm1 works on my D820 (x86_64 kernel, Core2 Duo T7200) 24-rc3-mm1 (plus 3 patches from hotfixes/) bricks *instantly* at boot - grub prints its 3 or 4 lines saying what it loaded, the screen clears, and *blam* dead. No serial console output, no pair of penguins on the monitor, no netconsole, no earlyprintk=vga output, no alt-sysrq, only thing that does *anything* is hold the power button for 5 seconds. Whatever it is, it happens *very* early (before we get as far as the 'Linux version 2.6.mumble' banner), and happens *hard*. I've bisected it down this far: git-ipwireless_cs.patch GOOD git-x86.patch git-x86-fixup.patch git-x86-thread_order-borkage.patch git-x86-thread_order-borkage-fix.patch git-x86-identify_cpu-fix.patch git-x86-memory_add_physaddr_to_nid-export-for-acpi-memhotplugko.patch git-x86-memory_add_physaddr_to_nid-export-for-acpi-memhotplugko-checkpatch-fixes.patch git-x86-inlining-borkage.patch x86_64-set-cpu_index-to-nr_cpus-instead-of-0.patch x86_64-make-sparsemem-vmemmap-the-default-memory-model-v2.patch BAD Anybody got any good debugging ideas before I go through and do the final 3 or 4 bisects? I suspect I'll need them once I find the offending patch to tell *why* said patch dies on my box - I've seen enough traffic regarding -rc3-mm1 dying *later* to know it's probably a subtle issue and not one that will be obvious once I finger a specific patch. For example, it's probably not the IO-APIC panic that people are seeing, because their kernels live long enough to panic. ;) Hi, does boot_delay helps? Regards dave - 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.24-rc3-mm1 - brick my Dell Latitude D820
On Tue, 27 Nov 2007 16:25:22 +0800, Dave Young said: does boot_delay helps? It might, if the kernel lived long enough to output a first printk for us to delay after. :) Shooting this one would be *easy* if the problem was an boot-time oops that would otherwise scroll off the screen without a boot_delay... pgpqJlvYAN6Ou.pgp Description: PGP signature
Re: 2.6.24-rc3-mm1 - brick my Dell Latitude D820
* Andrew Morton [EMAIL PROTECTED] wrote: Otherwise, please proceed to work out which diff I need to drop and hope like hell that it isn't git-x86.. hm? x86.git is fully bisectable - so a more accurate statement would be and hope that it's x86.git, so that it can be properly bisected :-) For x86.git bisection, pull the 'mm' branch from: git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git Ingo - 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.24-rc3-mm1 - brick my Dell Latitude D820
On Mon, 26 Nov 2007 23:27:03 PST, Andrew Morton said: > > git-x86.patch > > git-x86-fixup.patch > > git-x86-thread_order-borkage.patch > > git-x86-thread_order-borkage-fix.patch > > git-x86-identify_cpu-fix.patch > > git-x86-memory_add_physaddr_to_nid-export-for-acpi-memhotplugko.patch > > git-x86-memory_add_physaddr_to_nid-export-for-acpi-memhotplugko-checkpatch-fixes.patch > > git-x86-inlining-borkage.patch > > x86_64-set-cpu_index-to-nr_cpus-instead-of-0.patch > > x86_64-make-sparsemem-vmemmap-the-default-memory-model-v2.patch BAD > You could try http://userweb.kernel.org/~akpm/mmotm/ - we might have already > fixed it. I suspect that trying -rc3-mm1 but refreshing just the 10 patches above from -mmotm would be far less likely to pull in other heartburn? > Otherwise, please proceed to work out which diff I need to drop and hope like > hell that it isn't git-x86.. That's a 41,240 line diff, the rest *total* to about 400 lines. I don't have warm-n-fuzzies about my odds here. ;) I'm a git-idiot, but *do* know how to git-bisect through Linus tree - what would I need to do to git-bisect through git-x86.patch? (I do *not* know how to deal with more than 1 source git tree, so if the magic is just 'get a linus tree, merge git-x86, then bisect as usual", I'm stuck on "merge git-x86").. pgpxMGUuWzdJd.pgp Description: PGP signature
Re: 2.6.24-rc3-mm1 - brick my Dell Latitude D820
On Tue, 27 Nov 2007 02:16:26 -0500 [EMAIL PROTECTED] wrote: > On Tue, 20 Nov 2007 20:45:25 PST, Andrew Morton said: > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc3/2.6.24-rc3-mm1/ > > Finally got both time and motivation to at least start a bisect.. > > 2.6.23-mm1 works on my D820 (x86_64 kernel, Core2 Duo T7200) > > 24-rc3-mm1 (plus 3 patches from hotfixes/) bricks *instantly* at boot - grub > prints its 3 or 4 lines saying what it loaded, the screen clears, and *blam* > dead. No serial console output, no pair of penguins on the monitor, no > netconsole, no earlyprintk=vga output, no alt-sysrq, only thing that does > *anything* is "hold the power button for 5 seconds". Whatever it is, it > happens *very* early (before we get as far as the 'Linux version 2.6.mumble' > banner), and happens *hard*. > > I've bisected it down this far: > > git-ipwireless_cs.patch GOOD > git-x86.patch > git-x86-fixup.patch > git-x86-thread_order-borkage.patch > git-x86-thread_order-borkage-fix.patch > git-x86-identify_cpu-fix.patch > git-x86-memory_add_physaddr_to_nid-export-for-acpi-memhotplugko.patch > git-x86-memory_add_physaddr_to_nid-export-for-acpi-memhotplugko-checkpatch-fixes.patch > git-x86-inlining-borkage.patch > x86_64-set-cpu_index-to-nr_cpus-instead-of-0.patch > x86_64-make-sparsemem-vmemmap-the-default-memory-model-v2.patch BAD > > Anybody got any good debugging ideas before I go through and do the final > 3 or 4 bisects? I suspect I'll need them once I find the offending patch > to tell *why* said patch dies on my box - I've seen enough traffic regarding > -rc3-mm1 dying *later* to know it's probably a subtle issue and not one > that will be obvious once I finger a specific patch. For example, it's > probably not the IO-APIC panic that people are seeing, because their kernels > live long enough to panic. ;) > You could try http://userweb.kernel.org/~akpm/mmotm/ - we might have already fixed it. Otherwise, please proceed to work out which diff I need to drop and hope like hell that it isn't git-x86.. - 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.24-rc3-mm1 - brick my Dell Latitude D820
On Tue, 20 Nov 2007 20:45:25 PST, Andrew Morton said: > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc3/2.6.24-rc3-mm1/ Finally got both time and motivation to at least start a bisect.. 2.6.23-mm1 works on my D820 (x86_64 kernel, Core2 Duo T7200) 24-rc3-mm1 (plus 3 patches from hotfixes/) bricks *instantly* at boot - grub prints its 3 or 4 lines saying what it loaded, the screen clears, and *blam* dead. No serial console output, no pair of penguins on the monitor, no netconsole, no earlyprintk=vga output, no alt-sysrq, only thing that does *anything* is "hold the power button for 5 seconds". Whatever it is, it happens *very* early (before we get as far as the 'Linux version 2.6.mumble' banner), and happens *hard*. I've bisected it down this far: git-ipwireless_cs.patch GOOD git-x86.patch git-x86-fixup.patch git-x86-thread_order-borkage.patch git-x86-thread_order-borkage-fix.patch git-x86-identify_cpu-fix.patch git-x86-memory_add_physaddr_to_nid-export-for-acpi-memhotplugko.patch git-x86-memory_add_physaddr_to_nid-export-for-acpi-memhotplugko-checkpatch-fixes.patch git-x86-inlining-borkage.patch x86_64-set-cpu_index-to-nr_cpus-instead-of-0.patch x86_64-make-sparsemem-vmemmap-the-default-memory-model-v2.patch BAD Anybody got any good debugging ideas before I go through and do the final 3 or 4 bisects? I suspect I'll need them once I find the offending patch to tell *why* said patch dies on my box - I've seen enough traffic regarding -rc3-mm1 dying *later* to know it's probably a subtle issue and not one that will be obvious once I finger a specific patch. For example, it's probably not the IO-APIC panic that people are seeing, because their kernels live long enough to panic. ;) pgpbW8UIlUa1z.pgp Description: PGP signature
Re: 2.6.24-rc3-mm1 - brick my Dell Latitude D820
On Tue, 20 Nov 2007 20:45:25 PST, Andrew Morton said: ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc3/2.6.24-rc3-mm1/ Finally got both time and motivation to at least start a bisect.. 2.6.23-mm1 works on my D820 (x86_64 kernel, Core2 Duo T7200) 24-rc3-mm1 (plus 3 patches from hotfixes/) bricks *instantly* at boot - grub prints its 3 or 4 lines saying what it loaded, the screen clears, and *blam* dead. No serial console output, no pair of penguins on the monitor, no netconsole, no earlyprintk=vga output, no alt-sysrq, only thing that does *anything* is hold the power button for 5 seconds. Whatever it is, it happens *very* early (before we get as far as the 'Linux version 2.6.mumble' banner), and happens *hard*. I've bisected it down this far: git-ipwireless_cs.patch GOOD git-x86.patch git-x86-fixup.patch git-x86-thread_order-borkage.patch git-x86-thread_order-borkage-fix.patch git-x86-identify_cpu-fix.patch git-x86-memory_add_physaddr_to_nid-export-for-acpi-memhotplugko.patch git-x86-memory_add_physaddr_to_nid-export-for-acpi-memhotplugko-checkpatch-fixes.patch git-x86-inlining-borkage.patch x86_64-set-cpu_index-to-nr_cpus-instead-of-0.patch x86_64-make-sparsemem-vmemmap-the-default-memory-model-v2.patch BAD Anybody got any good debugging ideas before I go through and do the final 3 or 4 bisects? I suspect I'll need them once I find the offending patch to tell *why* said patch dies on my box - I've seen enough traffic regarding -rc3-mm1 dying *later* to know it's probably a subtle issue and not one that will be obvious once I finger a specific patch. For example, it's probably not the IO-APIC panic that people are seeing, because their kernels live long enough to panic. ;) pgpbW8UIlUa1z.pgp Description: PGP signature
Re: 2.6.24-rc3-mm1 - brick my Dell Latitude D820
On Tue, 27 Nov 2007 02:16:26 -0500 [EMAIL PROTECTED] wrote: On Tue, 20 Nov 2007 20:45:25 PST, Andrew Morton said: ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc3/2.6.24-rc3-mm1/ Finally got both time and motivation to at least start a bisect.. 2.6.23-mm1 works on my D820 (x86_64 kernel, Core2 Duo T7200) 24-rc3-mm1 (plus 3 patches from hotfixes/) bricks *instantly* at boot - grub prints its 3 or 4 lines saying what it loaded, the screen clears, and *blam* dead. No serial console output, no pair of penguins on the monitor, no netconsole, no earlyprintk=vga output, no alt-sysrq, only thing that does *anything* is hold the power button for 5 seconds. Whatever it is, it happens *very* early (before we get as far as the 'Linux version 2.6.mumble' banner), and happens *hard*. I've bisected it down this far: git-ipwireless_cs.patch GOOD git-x86.patch git-x86-fixup.patch git-x86-thread_order-borkage.patch git-x86-thread_order-borkage-fix.patch git-x86-identify_cpu-fix.patch git-x86-memory_add_physaddr_to_nid-export-for-acpi-memhotplugko.patch git-x86-memory_add_physaddr_to_nid-export-for-acpi-memhotplugko-checkpatch-fixes.patch git-x86-inlining-borkage.patch x86_64-set-cpu_index-to-nr_cpus-instead-of-0.patch x86_64-make-sparsemem-vmemmap-the-default-memory-model-v2.patch BAD Anybody got any good debugging ideas before I go through and do the final 3 or 4 bisects? I suspect I'll need them once I find the offending patch to tell *why* said patch dies on my box - I've seen enough traffic regarding -rc3-mm1 dying *later* to know it's probably a subtle issue and not one that will be obvious once I finger a specific patch. For example, it's probably not the IO-APIC panic that people are seeing, because their kernels live long enough to panic. ;) You could try http://userweb.kernel.org/~akpm/mmotm/ - we might have already fixed it. Otherwise, please proceed to work out which diff I need to drop and hope like hell that it isn't git-x86.. - 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.24-rc3-mm1 - brick my Dell Latitude D820
On Mon, 26 Nov 2007 23:27:03 PST, Andrew Morton said: git-x86.patch git-x86-fixup.patch git-x86-thread_order-borkage.patch git-x86-thread_order-borkage-fix.patch git-x86-identify_cpu-fix.patch git-x86-memory_add_physaddr_to_nid-export-for-acpi-memhotplugko.patch git-x86-memory_add_physaddr_to_nid-export-for-acpi-memhotplugko-checkpatch-fixes.patch git-x86-inlining-borkage.patch x86_64-set-cpu_index-to-nr_cpus-instead-of-0.patch x86_64-make-sparsemem-vmemmap-the-default-memory-model-v2.patch BAD You could try http://userweb.kernel.org/~akpm/mmotm/ - we might have already fixed it. I suspect that trying -rc3-mm1 but refreshing just the 10 patches above from -mmotm would be far less likely to pull in other heartburn? Otherwise, please proceed to work out which diff I need to drop and hope like hell that it isn't git-x86.. That's a 41,240 line diff, the rest *total* to about 400 lines. I don't have warm-n-fuzzies about my odds here. ;) I'm a git-idiot, but *do* know how to git-bisect through Linus tree - what would I need to do to git-bisect through git-x86.patch? (I do *not* know how to deal with more than 1 source git tree, so if the magic is just 'get a linus tree, merge git-x86, then bisect as usual, I'm stuck on merge git-x86).. pgpxMGUuWzdJd.pgp Description: PGP signature
