Re: PROBLEM: 2.4.5pre1 will not boot
Gordon Sadler wrote: > > On Fri, May 04, 2001 at 01:28:23AM -0700, Seth Goldberg wrote:Seth Goldberg ><[EMAIL PROTECTED]> > > Gordon Sadler wrote: > > > > > > On Fri, May 04, 2001 at 12:43:22AM -0700, Seth Goldberg wrote: > > > > Hi, > > Hi, > > > > Have you tried compiling ther kernel with Athlon optimiztions turned > I've seen some others reporting some success with K6-II[I] or > Pentium-II[I] configurations. I haven't tried it here as 2.2.19 is > running fine for me. -) I just keep trying the new 2.4.x and reporting > here with hopes someone will find the problem and be able to resolve it. > There could very well be something wrong with my/our hardware. I'm at a > loss as to why none of the developers can reproduce this? Is it possible > none of the 'core' developers have/have access to this hardware? It > isn't all that unusual I think. Yep. I think it's just the fact that the KT133A chipset is so new that very few people have it. And of the people who have it, I think a great majority are running on distributions of Linux whose kernels are NOT athlon optimized. I'd like to ask everyone who has a KT133A to please try a 2.4.x kernel with Athlon optimizations and let us know what percentage are displaying this problem. Thank you! --Seth - 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: 2.4.5pre1 will not boot
On Fri, May 04, 2001 at 01:28:23AM -0700, Seth Goldberg wrote:Seth Goldberg <[EMAIL PROTECTED]> > Gordon Sadler wrote: > > > > On Fri, May 04, 2001 at 12:43:22AM -0700, Seth Goldberg wrote: > > > Hi, > Hi, > > Have you tried compiling ther kernel with Athlon optimiztions turned > off (try > compiling for a K6-II[I])? The has stopped the same thing from > happening on > my system and those of a few other people. > I've seen some others reporting some success with K6-II[I] or Pentium-II[I] configurations. I haven't tried it here as 2.2.19 is running fine for me. -) I just keep trying the new 2.4.x and reporting here with hopes someone will find the problem and be able to resolve it. There could very well be something wrong with my/our hardware. I'm at a loss as to why none of the developers can reproduce this? Is it possible none of the 'core' developers have/have access to this hardware? It isn't all that unusual I think. If anyone needs more info, just ask. Lots of time/hardrive space here available for experimenting. (As long as you don't blow it up -) ). Gordon Sadler - 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: 2.4.5pre1 will not boot
Gordon Sadler wrote: > > On Fri, May 04, 2001 at 12:43:22AM -0700, Seth Goldberg wrote: > > Hi, Hi, Have you tried compiling ther kernel with Athlon optimiztions turned off (try compiling for a K6-II[I])? The has stopped the same thing from happening on my system and those of a few other people. --S > > > >What hardware are you running? > > > AMD Duron 800 > Epox 8KTA3 m/b > VIA KT133A AGPSet (KT133A+VT82C686B) > 128 MB pc100 brandname SDRAM > Inter etherexpress100 > Nvidia Riva TNT (orig.) > Quantum FB LP LM20.5 > > Full details available in previous oops report for 2.4.4. Didn't see > point of posting lspci -vvv, /proc/... again so soon. System here hasn't > changed. > > Thanks > > Gordon Sadler > > - > 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/ - 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: 2.4.5pre1 will not boot
On Fri, May 04, 2001 at 12:43:22AM -0700, Seth Goldberg wrote: > Hi, > >What hardware are you running? > AMD Duron 800 Epox 8KTA3 m/b VIA KT133A AGPSet (KT133A+VT82C686B) 128 MB pc100 brandname SDRAM Inter etherexpress100 Nvidia Riva TNT (orig.) Quantum FB LP LM20.5 Full details available in previous oops report for 2.4.4. Didn't see point of posting lspci -vvv, /proc/... again so soon. System here hasn't changed. Thanks Gordon Sadler - 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: 2.4.5pre1 will not boot
Hi, What hardware are you running? --seth > > Please CC any replies. > Please refer to my previous post 'PROBLEM: 2.4.4 oops, will not boot' > for complete machine details/configuration. > > I'm still working on different 2.4 kernels trying to get just one to > boot normally. Currently I've removed all modules and built everything > into the kernel, that seems to help a 'little'. > > Just tried 2.4.5pre1... > > 1st boot. Got as far as "Checking all file systems...", which is: > fsck -C -R -A -a (Debian Sid). This was followed by numerous (>50) > lines of the form: > memory.c: 83 (something I couldn't read fast enough) > followed by the machine auto-rebooting. > > 2nd boot. Trying to duplicate to read above memory.c ... > Led to the attached oops.txt > ksym.out contained in the tarball. > > 3rd boot. I was actually able to login... for about 5 mins. I attempted > to run the above oops through ksymoops while kernel was running. It > appeared to work, just then machine froze, required my using reset > button on case. This led to booting back into 2.2.19 with duplicate > inodes, manual run of fsck. > > 4th boot. Led to the attached oops2.txt > ksym2.out which was just the > first oops of approx. 20 or more before machine froze. All the > remaining oops (that I looked at) were of the same type/address. > > I really hope someone finds this, Andrew Morton(sp?) was looking into my > 2.4.4 oops, says my slab is being corrupted? Would be kind of > interesting to find out it is hardware related. This m/b and CPU are > brand new, can still take them back -) > > Thanks for your time. > > Gordon Sadler > > > > > Name: 2.4.5pre1.oops.tar.gz >2.4.5pre1.oops.tar.gzType: Unix Tape Archive (application/x-tar) > Encoding: base64 - 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: 2.4.5pre1 will not boot
Please CC any replies. Please refer to my previous post 'PROBLEM: 2.4.4 oops, will not boot' for complete machine details/configuration. I'm still working on different 2.4 kernels trying to get just one to boot normally. Currently I've removed all modules and built everything into the kernel, that seems to help a 'little'. Just tried 2.4.5pre1... 1st boot. Got as far as "Checking all file systems...", which is: fsck -C -R -A -a (Debian Sid). This was followed by numerous (>50) lines of the form: memory.c: 83 (something I couldn't read fast enough) followed by the machine auto-rebooting. 2nd boot. Trying to duplicate to read above memory.c ... Led to the attached oops.txt > ksym.out contained in the tarball. 3rd boot. I was actually able to login... for about 5 mins. I attempted to run the above oops through ksymoops while kernel was running. It appeared to work, just then machine froze, required my using reset button on case. This led to booting back into 2.2.19 with duplicate inodes, manual run of fsck. 4th boot. Led to the attached oops2.txt > ksym2.out which was just the first oops of approx. 20 or more before machine froze. All the remaining oops (that I looked at) were of the same type/address. I really hope someone finds this, Andrew Morton(sp?) was looking into my 2.4.4 oops, says my slab is being corrupted? Would be kind of interesting to find out it is hardware related. This m/b and CPU are brand new, can still take them back -) Thanks for your time. Gordon Sadler 2.4.5pre1.oops.tar.gz
PROBLEM: 2.4.5pre1 will not boot
Please CC any replies. Please refer to my previous post 'PROBLEM: 2.4.4 oops, will not boot' for complete machine details/configuration. I'm still working on different 2.4 kernels trying to get just one to boot normally. Currently I've removed all modules and built everything into the kernel, that seems to help a 'little'. Just tried 2.4.5pre1... 1st boot. Got as far as Checking all file systems..., which is: fsck -C -R -A -a (Debian Sid). This was followed by numerous (50) lines of the form: memory.c: 83 (something I couldn't read fast enough) followed by the machine auto-rebooting. 2nd boot. Trying to duplicate to read above memory.c ... Led to the attached oops.txt ksym.out contained in the tarball. 3rd boot. I was actually able to login... for about 5 mins. I attempted to run the above oops through ksymoops while kernel was running. It appeared to work, just then machine froze, required my using reset button on case. This led to booting back into 2.2.19 with duplicate inodes, manual run of fsck. 4th boot. Led to the attached oops2.txt ksym2.out which was just the first oops of approx. 20 or more before machine froze. All the remaining oops (that I looked at) were of the same type/address. I really hope someone finds this, Andrew Morton(sp?) was looking into my 2.4.4 oops, says my slab is being corrupted? Would be kind of interesting to find out it is hardware related. This m/b and CPU are brand new, can still take them back -) Thanks for your time. Gordon Sadler 2.4.5pre1.oops.tar.gz
Re: PROBLEM: 2.4.5pre1 will not boot
Hi, What hardware are you running? --seth Please CC any replies. Please refer to my previous post 'PROBLEM: 2.4.4 oops, will not boot' for complete machine details/configuration. I'm still working on different 2.4 kernels trying to get just one to boot normally. Currently I've removed all modules and built everything into the kernel, that seems to help a 'little'. Just tried 2.4.5pre1... 1st boot. Got as far as Checking all file systems..., which is: fsck -C -R -A -a (Debian Sid). This was followed by numerous (50) lines of the form: memory.c: 83 (something I couldn't read fast enough) followed by the machine auto-rebooting. 2nd boot. Trying to duplicate to read above memory.c ... Led to the attached oops.txt ksym.out contained in the tarball. 3rd boot. I was actually able to login... for about 5 mins. I attempted to run the above oops through ksymoops while kernel was running. It appeared to work, just then machine froze, required my using reset button on case. This led to booting back into 2.2.19 with duplicate inodes, manual run of fsck. 4th boot. Led to the attached oops2.txt ksym2.out which was just the first oops of approx. 20 or more before machine froze. All the remaining oops (that I looked at) were of the same type/address. I really hope someone finds this, Andrew Morton(sp?) was looking into my 2.4.4 oops, says my slab is being corrupted? Would be kind of interesting to find out it is hardware related. This m/b and CPU are brand new, can still take them back -) Thanks for your time. Gordon Sadler Name: 2.4.5pre1.oops.tar.gz 2.4.5pre1.oops.tar.gzType: Unix Tape Archive (application/x-tar) Encoding: base64 - 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: 2.4.5pre1 will not boot
On Fri, May 04, 2001 at 12:43:22AM -0700, Seth Goldberg wrote: Hi, What hardware are you running? AMD Duron 800 Epox 8KTA3 m/b VIA KT133A AGPSet (KT133A+VT82C686B) 128 MB pc100 brandname SDRAM Inter etherexpress100 Nvidia Riva TNT (orig.) Quantum FB LP LM20.5 Full details available in previous oops report for 2.4.4. Didn't see point of posting lspci -vvv, /proc/... again so soon. System here hasn't changed. Thanks Gordon Sadler - 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: 2.4.5pre1 will not boot
Gordon Sadler wrote: On Fri, May 04, 2001 at 12:43:22AM -0700, Seth Goldberg wrote: Hi, Hi, Have you tried compiling ther kernel with Athlon optimiztions turned off (try compiling for a K6-II[I])? The has stopped the same thing from happening on my system and those of a few other people. --S What hardware are you running? AMD Duron 800 Epox 8KTA3 m/b VIA KT133A AGPSet (KT133A+VT82C686B) 128 MB pc100 brandname SDRAM Inter etherexpress100 Nvidia Riva TNT (orig.) Quantum FB LP LM20.5 Full details available in previous oops report for 2.4.4. Didn't see point of posting lspci -vvv, /proc/... again so soon. System here hasn't changed. Thanks Gordon Sadler - 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/ - 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: 2.4.5pre1 will not boot
On Fri, May 04, 2001 at 01:28:23AM -0700, Seth Goldberg wrote:Seth Goldberg [EMAIL PROTECTED] Gordon Sadler wrote: On Fri, May 04, 2001 at 12:43:22AM -0700, Seth Goldberg wrote: Hi, Hi, Have you tried compiling ther kernel with Athlon optimiztions turned off (try compiling for a K6-II[I])? The has stopped the same thing from happening on my system and those of a few other people. I've seen some others reporting some success with K6-II[I] or Pentium-II[I] configurations. I haven't tried it here as 2.2.19 is running fine for me. -) I just keep trying the new 2.4.x and reporting here with hopes someone will find the problem and be able to resolve it. There could very well be something wrong with my/our hardware. I'm at a loss as to why none of the developers can reproduce this? Is it possible none of the 'core' developers have/have access to this hardware? It isn't all that unusual I think. If anyone needs more info, just ask. Lots of time/hardrive space here available for experimenting. (As long as you don't blow it up -) ). Gordon Sadler - 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: 2.4.5pre1 will not boot
Gordon Sadler wrote: On Fri, May 04, 2001 at 01:28:23AM -0700, Seth Goldberg wrote:Seth Goldberg [EMAIL PROTECTED] Gordon Sadler wrote: On Fri, May 04, 2001 at 12:43:22AM -0700, Seth Goldberg wrote: Hi, Hi, Have you tried compiling ther kernel with Athlon optimiztions turned I've seen some others reporting some success with K6-II[I] or Pentium-II[I] configurations. I haven't tried it here as 2.2.19 is running fine for me. -) I just keep trying the new 2.4.x and reporting here with hopes someone will find the problem and be able to resolve it. There could very well be something wrong with my/our hardware. I'm at a loss as to why none of the developers can reproduce this? Is it possible none of the 'core' developers have/have access to this hardware? It isn't all that unusual I think. Yep. I think it's just the fact that the KT133A chipset is so new that very few people have it. And of the people who have it, I think a great majority are running on distributions of Linux whose kernels are NOT athlon optimized. I'd like to ask everyone who has a KT133A to please try a 2.4.x kernel with Athlon optimizations and let us know what percentage are displaying this problem. Thank you! --Seth - 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/
