RE: VIA Southbridge bug (Was: Crash on boot (2.4.5))
I'd love to help out with testing (alas, my kernel coding skills aren't up to fixing this kind of problem). Heck, if it trashes my linux install, no biggie... I've got it ghosted to an image elsewhere... Anyone wanting to work on this just drop me an email. -- andyw -Original Message- From: Steven Walter [mailto:[EMAIL PROTECTED]] Sent: Monday, June 25, 2001 1:33 AM To: Andy Ward Cc: [EMAIL PROTECTED] Subject: VIA Southbridge bug (Was: Crash on boot (2.4.5)) Great, glad to here it. Who (if anyone) is still attempting to unravel the puzzle of the Via southbridge bug? You, Andy, should try and get in touch with them and help debug this thing, if you're up to it. On Mon, Jun 25, 2001 at 01:17:57AM -0500, Andy Ward wrote: > Well, I have tried your suggestion, and it works beautifully... The > only change I made was to the cpu type (to 686), and everything *just* > works now... Thanks, all!!! > > > From the look of things, you're being bitten by the VIA southbridge > > problem. As I've gathered, its some sort of interaction with that chip > > and the 3DNow! fast copy routines the kernel uses. > > > > If you compile the kernel for a 686, does the problem go away? What > > about 586 or lower? If so, I believe there are some people working on > > finding common aspects of the hardware that experience this problem, > > though I don't remember who. You should get in contact with them, or > > they might get into contact with you. > > > > Good luck on working this out. > > -- > > -Steven > > In a time of universal deceit, telling the truth is a revolutionary act. > > -- George Orwell -- -Steven In a time of universal deceit, telling the truth is a revolutionary act. -- George Orwell - 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: VIA Southbridge bug (Was: Crash on boot (2.4.5))
oh really? I have my memory timings set to 133/cas2/6-4-4-4. One wonders... *ponder* I have noticed some general flakyness (hard to pin down) on the system, though... random program crashes, minor visual corruption in X (which fixes itself when you move things around), etc... Anyone want to take a swing at that? -- andyw -Original Message- From: Alan Cox [mailto:[EMAIL PROTECTED]] Sent: Monday, June 25, 2001 2:07 AM To: Steven Walter Cc: Andy Ward; [EMAIL PROTECTED] Subject: Re: VIA Southbridge bug (Was: Crash on boot (2.4.5)) > Great, glad to here it. Who (if anyone) is still attempting to unravel > the puzzle of the Via southbridge bug? You, Andy, should try and get in > touch with them and help debug this thing, if you're up to it. The IWILL problem seems unrelated. Its the board that more than others people report fails totally when streaming memory copies using movntq instructions. The Athlon optimised kernel places pretty much the absolute maximum load possible on the memory bus. Several people have reported that machines that are otherwise stable on the bios fast options require the proper conservative settings to be stable with the Athlon optimisations Alan - 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: Crash on boot (2.4.5)
Well, I have tried your suggestion, and it works beautifully... The only change I made was to the cpu type (to 686), and everything *just* works now... Thanks, all!!! -- andyw -Original Message- From: Steven Walter [mailto:[EMAIL PROTECTED]] Sent: Sunday, June 24, 2001 3:42 PM To: Andy Ward Cc: [EMAIL PROTECTED] Subject: Re: Crash on boot (2.4.5) On Sun, Jun 24, 2001 at 01:51:09PM -0500, Daniel Fraley wrote: > Hi, everyone.. I'm borrowing my roommate's email, so please send replies to > [EMAIL PROTECTED] Thanks! > > Here's my problem... when I boot anything 2.4, I get several oopsen in a > row, all of which are either (most commonly) kernel paging request could not > be handled, or (much less common) unable to handle kernel Null pointer > dereference. I will send any info on request, but here's my hardware and > kernel config: > > iWill KKR-266R (Via 8363 Northbridge, 686B south) > AMD tbird 1GHz > 256MB cas2 pc133 sdram > ATI Radeon DDR 64MB VIVO > Kingston KNE120TX (Realtek 8139 chip) > SBLive! 5.1 > IBM GXP75 30GB (on the via ide controller) > Pioneer 16x dvd > ls120 > > This happens regardless if I turn on swap or not. When swap is on, it is a > 128MB partition (and yes, I'm aware of the recommendation of 2x RAM, but I > believe I read somewhere that someone was working on that, and I didn't want > to waste the extra 384MB on swap). > > Is there anything I can do to fix this? > > -- andyw > > p.s., booting with devfs=nomount is better, but still causes oopsen (I get > to a login prompt, but if I do much more than mount a disk a copy to it, the > system freaks) >From the look of things, you're being bitten by the VIA southbridge problem. As I've gathered, its some sort of interaction with that chip and the 3DNow! fast copy routines the kernel uses. If you compile the kernel for a 686, does the problem go away? What about 586 or lower? If so, I believe there are some people working on finding common aspects of the hardware that experience this problem, though I don't remember who. You should get in contact with them, or they might get into contact with you. Good luck on working this out. -- -Steven In a time of universal deceit, telling the truth is a revolutionary act. -- George Orwell - 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: Crash on boot (2.4.5)
H... haven't tried changing to non-AMD for the chip type... I'll try pentium later tonight and see if it works better. Thanks for the insight -- andyw -Original Message- From: Steven Walter [mailto:[EMAIL PROTECTED]] Sent: Sunday, June 24, 2001 3:42 PM To: Andy Ward Cc: [EMAIL PROTECTED] Subject: Re: Crash on boot (2.4.5) On Sun, Jun 24, 2001 at 01:51:09PM -0500, Daniel Fraley wrote: > Hi, everyone.. I'm borrowing my roommate's email, so please send replies to > [EMAIL PROTECTED] Thanks! > > Here's my problem... when I boot anything 2.4, I get several oopsen in a > row, all of which are either (most commonly) kernel paging request could not > be handled, or (much less common) unable to handle kernel Null pointer > dereference. I will send any info on request, but here's my hardware and > kernel config: > > iWill KKR-266R (Via 8363 Northbridge, 686B south) > AMD tbird 1GHz > 256MB cas2 pc133 sdram > ATI Radeon DDR 64MB VIVO > Kingston KNE120TX (Realtek 8139 chip) > SBLive! 5.1 > IBM GXP75 30GB (on the via ide controller) > Pioneer 16x dvd > ls120 > > This happens regardless if I turn on swap or not. When swap is on, it is a > 128MB partition (and yes, I'm aware of the recommendation of 2x RAM, but I > believe I read somewhere that someone was working on that, and I didn't want > to waste the extra 384MB on swap). > > Is there anything I can do to fix this? > > -- andyw > > p.s., booting with devfs=nomount is better, but still causes oopsen (I get > to a login prompt, but if I do much more than mount a disk a copy to it, the > system freaks) >From the look of things, you're being bitten by the VIA southbridge problem. As I've gathered, its some sort of interaction with that chip and the 3DNow! fast copy routines the kernel uses. If you compile the kernel for a 686, does the problem go away? What about 586 or lower? If so, I believe there are some people working on finding common aspects of the hardware that experience this problem, though I don't remember who. You should get in contact with them, or they might get into contact with you. Good luck on working this out. -- -Steven In a time of universal deceit, telling the truth is a revolutionary act. -- George Orwell - 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: Crash on boot (2.4.5)
Unfortunatly, the memory is just fine. Both 2.2 *and* two versions of windows run just fine on the same machine, so it's probably not that. -- andyw -Original Message- From: David Brown [mailto:[EMAIL PROTECTED]] Sent: Sunday, June 24, 2001 2:14 PM To: Andy Ward Cc: [EMAIL PROTECTED] Subject: Re: Crash on boot (2.4.5) Daniel: Have you tried swapping in a different stick of RAM and/or running a boot-time memory tester? Does it boot on 2.2 or any other OSs? I had a problem like this once before - turned out one of the two 128MB CAS2 modules were bad. I replaced it and 2.4 booted wonderfully. Good Luck, - Dave [EMAIL PROTECTED] - Original Message - From: "Daniel Fraley" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, June 24, 2001 2:51 PM Subject: Crash on boot (2.4.5) > Hi, everyone.. I'm borrowing my roommate's email, so please send replies to > [EMAIL PROTECTED] Thanks! > > Here's my problem... when I boot anything 2.4, I get several oopsen in a > row, all of which are either (most commonly) kernel paging request could not > be handled, or (much less common) unable to handle kernel Null pointer > dereference. I will send any info on request, but here's my hardware and > kernel config: > > iWill KKR-266R (Via 8363 Northbridge, 686B south) > AMD tbird 1GHz > 256MB cas2 pc133 sdram > ATI Radeon DDR 64MB VIVO > Kingston KNE120TX (Realtek 8139 chip) > SBLive! 5.1 > IBM GXP75 30GB (on the via ide controller) > Pioneer 16x dvd > ls120 > > This happens regardless if I turn on swap or not. When swap is on, it is a > 128MB partition (and yes, I'm aware of the recommendation of 2x RAM, but I > believe I read somewhere that someone was working on that, and I didn't want > to waste the extra 384MB on swap). > > Is there anything I can do to fix this? > > -- andyw > > p.s., booting with devfs=nomount is better, but still causes oopsen (I get > to a login prompt, but if I do much more than mount a disk a copy to it, the > system freaks) > > > - 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/
