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
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
Chuck Ebbert wrote:
Leroy van Logchem wrote:
Bisecting went well, after 13 compiles this commit was found:
a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f is first bad commit
commit a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f
Author: Roland McGrath <[EMAIL PROTECTED]>
Date: Fri Jan 26 00:56:46 2007
Leroy van Logchem wrote:
>
> Bisecting went well, after 13 compiles this commit was found:
>
> a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f is first bad commit
> commit a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f
> Author: Roland McGrath <[EMAIL PROTECTED]>
> Date: Fri Jan 26 00:56:46 2007 -0800
>
>
Andi Kleen wrote:
Where does it hang exactly? Do you have a boot log?
Linux version 2.6.20 ([EMAIL PROTECTED]) (gcc version 3.4.6 20060404 (Red Hat
3.4.6-3)) #1 SMP Thu Mar 15 11:06:29 CET 2007
BIOS-provided physical RAM map:
sanitize start
sanitize end
copy_e820_map() start:
Andi Kleen wrote:
Where does it hang exactly? Do you have a boot log?
Linux version 2.6.20 ([EMAIL PROTECTED]) (gcc version 3.4.6 20060404 (Red Hat
3.4.6-3)) #1 SMP Thu Mar 15 11:06:29 CET 2007
BIOS-provided physical RAM map:
sanitize start
sanitize end
copy_e820_map() start:
Leroy van Logchem wrote:
Bisecting went well, after 13 compiles this commit was found:
a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f is first bad commit
commit a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f
Author: Roland McGrath [EMAIL PROTECTED]
Date: Fri Jan 26 00:56:46 2007 -0800
Chuck Ebbert wrote:
Leroy van Logchem wrote:
Bisecting went well, after 13 compiles this commit was found:
a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f is first bad commit
commit a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f
Author: Roland McGrath [EMAIL PROTECTED]
Date: Fri Jan 26 00:56:46 2007
On Thursday 15 March 2007 02:01, Andrew Morton wrote:
> > On Wed, 14 Mar 2007 17:52:01 + (UTC) Leroy van Logchem <[EMAIL
> > PROTECTED]> wrote:
> > Leroy van Logchem wldelft.nl> writes:
> >
Where does it hang exactly? Do you have a boot log?
> > > > > None whatsoever. Three people are
> On Wed, 14 Mar 2007 17:52:01 + (UTC) Leroy van Logchem <[EMAIL
> PROTECTED]> wrote:
> Leroy van Logchem wldelft.nl> writes:
>
> >
> > > > None whatsoever. Three people are reporting this and it's a drop-dead
> > > > showstopper for a 2.6.21 release so we just have to wait until someone
Leroy van Logchem wldelft.nl> writes:
>
> > > None whatsoever. Three people are reporting this and it's a drop-dead
> > > showstopper for a 2.6.21 release so we just have to wait until someone
> > > wakes up and thinks about it.
>
> The topic should be "when CONFIG_HIGHMEM64G=y" imo.
>
>
Leroy van Logchem leroy.vanlogchem at wldelft.nl writes:
None whatsoever. Three people are reporting this and it's a drop-dead
showstopper for a 2.6.21 release so we just have to wait until someone
wakes up and thinks about it.
The topic should be when CONFIG_HIGHMEM64G=y imo.
On Wed, 14 Mar 2007 17:52:01 + (UTC) Leroy van Logchem [EMAIL
PROTECTED] wrote:
Leroy van Logchem leroy.vanlogchem at wldelft.nl writes:
None whatsoever. Three people are reporting this and it's a drop-dead
showstopper for a 2.6.21 release so we just have to wait until
On Thursday 15 March 2007 02:01, Andrew Morton wrote:
On Wed, 14 Mar 2007 17:52:01 + (UTC) Leroy van Logchem [EMAIL
PROTECTED] wrote:
Leroy van Logchem leroy.vanlogchem at wldelft.nl writes:
Where does it hang exactly? Do you have a boot log?
None whatsoever. Three people are
14 matches
Mail list logo
