Re: [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] <- Bad?
Correcting my previous message, and confirming Leroy's one : linux-2.6.20.tar.gz : bad linux-2.6.20.1.tar.gz: bad linux-2.6.20.2.tar.gz: good linux-2.6.20.3.tar.gz: good With : COMPAT_VDSO=y CONFIG_HIGHMEM64G=y So problem have been solved with 2.6.20.2 Nilshar. 2007/3/15, Leroy van Logchem <[EMAIL PROTECTED]>: > Can you please double check this by trying with/without again -- sometimes bisects go bad. As requested I started to redo the test but now without git using kernel.org tars. The results now are, still using the same .config: linux-2.6.20.tar.gz : bad linux-2.6.20.1.tar.gz: bad (boot log equal) linux-2.6.20.2.tar.gz: good linux-2.6.20.3.tar.gz: good (triple checked) Really strange. Nilshar, please try these kernels too with: COMPAT_VDSO=y CONFIG_HIGHMEM64G=y - 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: [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] - Bad?
Correcting my previous message, and confirming Leroy's one : linux-2.6.20.tar.gz : bad linux-2.6.20.1.tar.gz: bad linux-2.6.20.2.tar.gz: good linux-2.6.20.3.tar.gz: good With : COMPAT_VDSO=y CONFIG_HIGHMEM64G=y So problem have been solved with 2.6.20.2 Nilshar. 2007/3/15, Leroy van Logchem [EMAIL PROTECTED]: Can you please double check this by trying with/without again -- sometimes bisects go bad. As requested I started to redo the test but now without git using kernel.org tars. The results now are, still using the same .config: linux-2.6.20.tar.gz : bad linux-2.6.20.1.tar.gz: bad (boot log equal) linux-2.6.20.2.tar.gz: good linux-2.6.20.3.tar.gz: good (triple checked) Really strange. Nilshar, please try these kernels too with: COMPAT_VDSO=y CONFIG_HIGHMEM64G=y - 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: [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y
Hello, I can confirm that the problem disappear when I disable Compat VDSO support by setting CONFIG_COMPAT_VDSO=n. Thanks Leroy. - 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: [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y
Hello, I can confirm that the problem disappear when I disable Compat VDSO support by setting CONFIG_COMPAT_VDSO=n. Thanks Leroy. - 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: Problem with 2.6.20 and highmem64
Adding [EMAIL PROTECTED] 2007/2/16, Nilshar <[EMAIL PROTECTED]>: I can confirm that it works fine with 2.6.20-rc2. Do you need me to try any other ? do you need any more info ? 2007/2/14, Nilshar <[EMAIL PROTECTED]>: > Hello, > I have an issue with latest 2.6.20 kernel.. > my last kernel was a 2.6.18 and I wanted to upgrade to a 2.6.20, I > copied .config and did a make menuconfig, then save/quit. I compiled > new kernel, all went fine. > I installed it and at boot time, I had a hang just after "Freeing > unused kernel memory" where INIT is supposed to start. > After searching the web, I found that it is usually the case when > wrong process type is configured.. I verified that, but all was fine > there. > After 10ish compiled kernel, I found that it is when I select highmem64. > > Diff between working and non working kernel : > > 181,182c181,182 > < # CONFIG_HIGHMEM4G is not set > < CONFIG_HIGHMEM64G=y > --- > > CONFIG_HIGHMEM4G=y > > # CONFIG_HIGHMEM64G is not set > 185d184 > < CONFIG_X86_PAE=y > 191c190 > < CONFIG_RESOURCES_64BIT=y > --- > > # CONFIG_RESOURCES_64BIT is not set > > (I just witching highmem 4G and highmem64g). > > I'll attach the full .config. > > it used to work fine with highmem64g with a kernel 2.6.18 and 2.6.19 > (I'm sure it was ok with .20-rc2 but I'll double check that). > > Is this a bug ? or something I did wrong ? > > Oh, I probably should add that this hang doesn't occur on all > hardware, but it happen on Dell PE 850 at least. > > If you need additional informations, just ask :) > > - 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: Problem with 2.6.20 and highmem64
I can confirm that it works fine with 2.6.20-rc2. Do you need me to try any other ? do you need any more info ? 2007/2/14, Nilshar <[EMAIL PROTECTED]>: Hello, I have an issue with latest 2.6.20 kernel.. my last kernel was a 2.6.18 and I wanted to upgrade to a 2.6.20, I copied .config and did a make menuconfig, then save/quit. I compiled new kernel, all went fine. I installed it and at boot time, I had a hang just after "Freeing unused kernel memory" where INIT is supposed to start. After searching the web, I found that it is usually the case when wrong process type is configured.. I verified that, but all was fine there. After 10ish compiled kernel, I found that it is when I select highmem64. Diff between working and non working kernel : 181,182c181,182 < # CONFIG_HIGHMEM4G is not set < CONFIG_HIGHMEM64G=y --- > CONFIG_HIGHMEM4G=y > # CONFIG_HIGHMEM64G is not set 185d184 < CONFIG_X86_PAE=y 191c190 < CONFIG_RESOURCES_64BIT=y --- > # CONFIG_RESOURCES_64BIT is not set (I just witching highmem 4G and highmem64g). I'll attach the full .config. it used to work fine with highmem64g with a kernel 2.6.18 and 2.6.19 (I'm sure it was ok with .20-rc2 but I'll double check that). Is this a bug ? or something I did wrong ? Oh, I probably should add that this hang doesn't occur on all hardware, but it happen on Dell PE 850 at least. If you need additional informations, just ask :) - 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: Problem with 2.6.20 and highmem64
I can confirm that it works fine with 2.6.20-rc2. Do you need me to try any other ? do you need any more info ? 2007/2/14, Nilshar [EMAIL PROTECTED]: Hello, I have an issue with latest 2.6.20 kernel.. my last kernel was a 2.6.18 and I wanted to upgrade to a 2.6.20, I copied .config and did a make menuconfig, then save/quit. I compiled new kernel, all went fine. I installed it and at boot time, I had a hang just after Freeing unused kernel memory where INIT is supposed to start. After searching the web, I found that it is usually the case when wrong process type is configured.. I verified that, but all was fine there. After 10ish compiled kernel, I found that it is when I select highmem64. Diff between working and non working kernel : 181,182c181,182 # CONFIG_HIGHMEM4G is not set CONFIG_HIGHMEM64G=y --- CONFIG_HIGHMEM4G=y # CONFIG_HIGHMEM64G is not set 185d184 CONFIG_X86_PAE=y 191c190 CONFIG_RESOURCES_64BIT=y --- # CONFIG_RESOURCES_64BIT is not set (I just witching highmem 4G and highmem64g). I'll attach the full .config. it used to work fine with highmem64g with a kernel 2.6.18 and 2.6.19 (I'm sure it was ok with .20-rc2 but I'll double check that). Is this a bug ? or something I did wrong ? Oh, I probably should add that this hang doesn't occur on all hardware, but it happen on Dell PE 850 at least. If you need additional informations, just ask :) - 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: Problem with 2.6.20 and highmem64
Adding [EMAIL PROTECTED] 2007/2/16, Nilshar [EMAIL PROTECTED]: I can confirm that it works fine with 2.6.20-rc2. Do you need me to try any other ? do you need any more info ? 2007/2/14, Nilshar [EMAIL PROTECTED]: Hello, I have an issue with latest 2.6.20 kernel.. my last kernel was a 2.6.18 and I wanted to upgrade to a 2.6.20, I copied .config and did a make menuconfig, then save/quit. I compiled new kernel, all went fine. I installed it and at boot time, I had a hang just after Freeing unused kernel memory where INIT is supposed to start. After searching the web, I found that it is usually the case when wrong process type is configured.. I verified that, but all was fine there. After 10ish compiled kernel, I found that it is when I select highmem64. Diff between working and non working kernel : 181,182c181,182 # CONFIG_HIGHMEM4G is not set CONFIG_HIGHMEM64G=y --- CONFIG_HIGHMEM4G=y # CONFIG_HIGHMEM64G is not set 185d184 CONFIG_X86_PAE=y 191c190 CONFIG_RESOURCES_64BIT=y --- # CONFIG_RESOURCES_64BIT is not set (I just witching highmem 4G and highmem64g). I'll attach the full .config. it used to work fine with highmem64g with a kernel 2.6.18 and 2.6.19 (I'm sure it was ok with .20-rc2 but I'll double check that). Is this a bug ? or something I did wrong ? Oh, I probably should add that this hang doesn't occur on all hardware, but it happen on Dell PE 850 at least. If you need additional informations, just ask :) - 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/
Problem with 2.6.20 and highmem64
Hello, I have an issue with latest 2.6.20 kernel.. my last kernel was a 2.6.18 and I wanted to upgrade to a 2.6.20, I copied .config and did a make menuconfig, then save/quit. I compiled new kernel, all went fine. I installed it and at boot time, I had a hang just after "Freeing unused kernel memory" where INIT is supposed to start. After searching the web, I found that it is usually the case when wrong process type is configured.. I verified that, but all was fine there. After 10ish compiled kernel, I found that it is when I select highmem64. Diff between working and non working kernel : 181,182c181,182 < # CONFIG_HIGHMEM4G is not set < CONFIG_HIGHMEM64G=y --- CONFIG_HIGHMEM4G=y # CONFIG_HIGHMEM64G is not set 185d184 < CONFIG_X86_PAE=y 191c190 < CONFIG_RESOURCES_64BIT=y --- # CONFIG_RESOURCES_64BIT is not set (I just witching highmem 4G and highmem64g). I'll attach the full .config. it used to work fine with highmem64g with a kernel 2.6.18 and 2.6.19 (I'm sure it was ok with .20-rc2 but I'll double check that). Is this a bug ? or something I did wrong ? Oh, I probably should add that this hang doesn't occur on all hardware, but it happen on Dell PE 850 at least. If you need additional informations, just ask :) config Description: Binary data
Problem with 2.6.20 and highmem64
Hello, I have an issue with latest 2.6.20 kernel.. my last kernel was a 2.6.18 and I wanted to upgrade to a 2.6.20, I copied .config and did a make menuconfig, then save/quit. I compiled new kernel, all went fine. I installed it and at boot time, I had a hang just after Freeing unused kernel memory where INIT is supposed to start. After searching the web, I found that it is usually the case when wrong process type is configured.. I verified that, but all was fine there. After 10ish compiled kernel, I found that it is when I select highmem64. Diff between working and non working kernel : 181,182c181,182 # CONFIG_HIGHMEM4G is not set CONFIG_HIGHMEM64G=y --- CONFIG_HIGHMEM4G=y # CONFIG_HIGHMEM64G is not set 185d184 CONFIG_X86_PAE=y 191c190 CONFIG_RESOURCES_64BIT=y --- # CONFIG_RESOURCES_64BIT is not set (I just witching highmem 4G and highmem64g). I'll attach the full .config. it used to work fine with highmem64g with a kernel 2.6.18 and 2.6.19 (I'm sure it was ok with .20-rc2 but I'll double check that). Is this a bug ? or something I did wrong ? Oh, I probably should add that this hang doesn't occur on all hardware, but it happen on Dell PE 850 at least. If you need additional informations, just ask :) config Description: Binary data
