From tuxpenguin at austin.rr.com Sun May 2 05:11:23 2004 From: tuxpenguin at austin.rr.com (Jason Knight) Date: Sun, 02 May 2004 00:11:23 -0500 Subject: XMMS Mp3 support Message-ID: <409482FB.5090306@austin.rr.com> How do most of you go about adding mp3 support to xmms? I tried recompiling both the xmms-mp3 src rpm and the xmms from xmms.org to no avail (didn't do anything once installed and errors during compile respectively). What is your method? Error: >.....libsong_change.so.debug()(64bit) libstereo.so.debug()(64bit) libtonegen.so.debug()(64bit) libvoice.so.debug()(64bit) >libvorbis.so.debug()(64bit) libwav.so.debug()(64bit) libxmms.so.1.3.1.debug()(64bit) >Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 >Checking for unpackaged file(s): /usr/lib/rpm/check-files /var/tmp/xmms-1.2.10-root >error: Installed (but unpackaged) file(s) found: > /usr/lib64/xmms/Input/libmikmod.la > /usr/lib64/xmms/Input/libmikmod.so > /usr/lib64/xmms/Input/libvorbis.la > /usr/lib64/xmms/Input/libvorbis.so > > >RPM build errors: > user havardk does not exist - using root > group havardk does not exist - using root > user havardk does not exist - using root > group havardk does not exist - using root > Installed (but unpackaged) file(s) found: > /usr/lib64/xmms/Input/libmikmod.la > /usr/lib64/xmms/Input/libmikmod.so > /usr/lib64/xmms/Input/libvorbis.la > /usr/lib64/xmms/Input/libvorbis.so > -- Jason Knight Fedora Core 2 Test 3 *x86_64* From tuxpenguin at austin.rr.com Sun May 2 06:24:21 2004 From: tuxpenguin at austin.rr.com (Jason Knight) Date: Sun, 02 May 2004 01:24:21 -0500 Subject: Hassle-free movie player recommendations? Message-ID: <40949415.5080501@austin.rr.com> I have just spent the last 2 to 3 hours trying to install xine (dependencies, recompiling etc...) and I was wondering how you all went about installing a movie player to play avi and other types? Is there something I am missing? Thanks in advance. -- Jason Knight Fedora Core 2 Test 3 *x86_64* From ckloiber at ckloiber.com Sun May 2 18:13:13 2004 From: ckloiber at ckloiber.com (Chris Kloiber) Date: Mon, 03 May 2004 02:13:13 +0800 Subject: Hassle-free movie player recommendations? In-Reply-To: <40949415.5080501@austin.rr.com> References: <40949415.5080501@austin.rr.com> Message-ID: <1083521593.10843.2.camel@localhost.localdomain> On Sun, 2004-05-02 at 14:24, Jason Knight wrote: > I have just spent the last 2 to 3 hours trying to install xine > (dependencies, recompiling etc...) and I was wondering how you all went > about installing a movie player to play avi and other types? Is there > something I am missing? Thanks in advance. > > -- > Jason Knight > Fedora Core 2 Test 3 *x86_64* Most people I suspect go to one of the Fedora based repositories (Freshrpms.net, Dag.Wiers.com, Livna.org) for x86 and either get the i386 versions of the software they need, or get the srpms and recompile. -- Chris Kloiber From tuxpenguin at austin.rr.com Sun May 2 22:57:03 2004 From: tuxpenguin at austin.rr.com (Jason Knight) Date: Sun, 02 May 2004 17:57:03 -0500 Subject: XMMS Mp3 support In-Reply-To: <1083503767.2511.7.camel@grendel> References: <409482FB.5090306@austin.rr.com> <1083503767.2511.7.camel@grendel> Message-ID: <40957CBF.1020908@austin.rr.com> Marshall Lewis wrote: >doing a rebuild on the src rpm worked for me.. I got it rpm.livna.org. >Let me know.. if you want I can send you my build and you can try that. >... actually I'm going to be gone most of the day, I'll just post it at >novafoundry.com. Give it a try. > > > ARGH! I should have payed a little more attention :) The reason why it wasn't working is I forgot to check read permissions on my mp3s. Oh well hehe, thanks for the rebuild xmms-mp3 btw. -- Jason Knight Fedora Core 2 Test 3 *x86_64* From marshall at novafoundry.com Wed May 5 19:34:58 2004 From: marshall at novafoundry.com (Marshall Lewis) Date: Wed, 05 May 2004 15:34:58 -0400 Subject: I need help debugging a random lockup Message-ID: <1083785698.2132.22.camel@localhost.localdomain> I'm not sure how to begin debugging this, it's not something that I've ever had happen on a linux system before. I have an opteron workstation here at work, and it locks up more or less randomly... It's a complete system freeze. There are no messages about it in /var/log/messages, and I'm guessing there aren't any messages on the consoles, although I have no real way to confirm. It doesn't seem to be application related (unless maybe it's X itself or the nvidia drivers), and is not load related. .. it can happen while I'm clicking around in firefox, typeing on openoffice, coding in nedit or zend studio, highlighting text, etc.. etc... .. and of course it even happens when my back is turned (probably out of spite). On any other machine I might suspect the ram.. and I guess I'm kinda suspecting the ram here, but it is an opteron, and it's running with ECC ram... so ram really shouldn't be an issue right? or wrong? : ) Any suggestions on how I can determine the cause of the lockup? (or at least narrow it down). BTW these lockups occured in FC1 as well (currently running FC2T3). -- Marshall From Mike.Cooper at reshape.com Wed May 5 20:09:04 2004 From: Mike.Cooper at reshape.com (Mike Cooper) Date: Wed, 05 May 2004 13:09:04 -0700 Subject: ASUS K8V BIOS problem In-Reply-To: <40801602.5090407@reshape.com> References: <407EC9EC.4040303@reshape.com> <407ECF60.60800@btinternet.com> <40801602.5090407@reshape.com> Message-ID: <409949E0.50407@reshape.com> Just a followup.... The problem turned out to be the Kingston memory DIMM. I replaced it and the BIOS problems disappeared. Hopefully nobody else will ever see this problem. mike Mike Cooper wrote: > Thanks! > > This seems to temporarily fix the problem. Whenever I make any BIOS > setting change, it goes into this "blank screen no output mode". If I > pull the power cord out for ~1 minute and plug it back in, it acts > normal (I can get into BIOS setup or boot from any device). However, > once I change any BIOS setting, it goes back into the same mode. > > Curiously, it consistantly says "Checking NVRAM... Update failed!" > during normal BIOS initialization whenever it goes into "blank screen no > output mode". When it boots OK it say "Checking NVRAM...". > > I'm going to try replacing the power supply (the case came with a 350W > Allied power supply) with something better and see if that fixes the > problem. > > mike > > Pete Bradbury wrote: > >> Mike Cooper wrote: >> >>> This isn't Linux specific at all, but ASUS Tech Support is >>> non-existant so I'm hoping someone might have seen this before... >>> >>> I have an ASUS K8V with Athlon64 3000 CPU and a 512MB DIMM (one >>> that's listed in the K8V manual as being approved). >>> >>> The problem is the BIOS never attempts to boot from any device (DVD, >>> IDE disk, or floppy). I never seen any activity light on any boot >>> device. >>> >>> It also almost never goes into BIOS setup mode when I hit . >>> After the BIOS startup screen showing config info, it goes to the >>> RAID initialization screen, then the screen clears and I get >>> absolutely nothing. The monitor is getting a video signal still, but >>> the screen is blank. Sometimes I can hit at this point and >>> I'll get "Entering Setup ...", but nothing happens. >>> >>> If I hit during the initial BIOS "booting" screen I can see it >>> say "Entering Setup ..." mixed in with the normal BIOS boot messages, >>> but it still just goes to the "on, but blank screen" mode. >>> >>> Twice I was able to hit to get the BIOS boot menu. >>> >>> Once I was actually able to get into BIOS SETUP. That was the first >>> time I powered on after building the system. >>> >>> I've replaced the K8V and the replacement has the same problem. >>> >>> Anybody seen anything like this? >>> >>> mike >>> >>> >> I've had similar, odd problems with my Asus card. >> >> Try unplugging the power connector for a few seconds - 10-20 then >> insert and retry. >> >> The MB seems to hold a charge when it gets stuck like this and this >> crude but effective method >> does seem to flush out the gremlins. >> >> >> >> >> > > From marshall at novafoundry.com Wed May 5 20:10:04 2004 From: marshall at novafoundry.com (Marshall Lewis) Date: Wed, 05 May 2004 16:10:04 -0400 Subject: I need help debugging a random lockup In-Reply-To: <1083785698.2132.22.camel@localhost.localdomain> References: <1083785698.2132.22.camel@localhost.localdomain> Message-ID: <1083787804.2075.7.camel@localhost.localdomain> Well.. now I can reproduce it .. sorta.. of course right after sending this email I decide to try and chart some stuff in oo calc, and it has locked 5 times in the last half hour. I'm not any closer to determining the cause though... maybe it's 32 bit apps? (or maybe it's power fluctuations, or the room is too hot, or my monitors are too close together... ) : ) -- Marshall On Wed, 2004-05-05 at 15:34, Marshall Lewis wrote: > I'm not sure how to begin debugging this, it's not something that I've > ever had happen on a linux system before. I have an opteron workstation > here at work, and it locks up more or less randomly... It's a complete > system freeze. There are no messages about it in /var/log/messages, and > I'm guessing there aren't any messages on the consoles, although I have > no real way to confirm. > > It doesn't seem to be application related (unless maybe it's X itself or > the nvidia drivers), and is not load related. .. it can happen while > I'm clicking around in firefox, typeing on openoffice, coding in nedit > or zend studio, highlighting text, etc.. etc... .. and of course it even > happens when my back is turned (probably out of spite). > > On any other machine I might suspect the ram.. and I guess I'm kinda > suspecting the ram here, but it is an opteron, and it's running with ECC > ram... so ram really shouldn't be an issue right? or wrong? : ) > > > Any suggestions on how I can determine the cause of the lockup? (or at > least narrow it down). BTW these lockups occured in FC1 as well > (currently running FC2T3). > > -- > Marshall > From jgriffin at v1data.com Wed May 5 20:27:19 2004 From: jgriffin at v1data.com (John Griffin) Date: Wed, 5 May 2004 13:27:19 -0700 Subject: I need help debugging a random lockup References: <1083785698.2132.22.camel@localhost.localdomain> <1083787804.2075.7.camel@localhost.localdomain> Message-ID: <007a01c432df$5ef31020$0500a8c0@laptop2> we've been struggling w/ a lockup issue and I'm wondering if there is any relationship- we have dual opterons (244s) MSI K8D Master-F. ECC memory we're having a devil of a time getting our CRON scripts to burn backups on a CDRW I should say the isolated issue is on the portion of the script related to the CD Burn program- when the system is at the point of completing the burn (writing the table of contents?), our system locks up. we noticed activity on our eth0 port and SCSI array at the moment the system locks. our thought is there is a conflict w/ our RAID (through our Adaptec 39320A-R). we also have discovered issues in our driver for the Broadcom gig-e on board. We have been unable to implement the updated drivers for the Broadcoms and are still using the Tigon3 drivers. Has anyone had this type of lockup? John Griffin V1 Datacom Inc ----- Original Message ----- From: "Marshall Lewis" To: Sent: Wednesday, May 05, 2004 1:10 PM Subject: Re: I need help debugging a random lockup > Well.. now I can reproduce it .. sorta.. of course right after sending > this email I decide to try and chart some stuff in oo calc, and it has > locked 5 times in the last half hour. I'm not any closer to determining > the cause though... maybe it's 32 bit apps? (or maybe it's power > fluctuations, or the room is too hot, or my monitors are too close > together... ) : ) > > -- > Marshall > > On Wed, 2004-05-05 at 15:34, Marshall Lewis wrote: > > I'm not sure how to begin debugging this, it's not something that I've > > ever had happen on a linux system before. I have an opteron workstation > > here at work, and it locks up more or less randomly... It's a complete > > system freeze. There are no messages about it in /var/log/messages, and > > I'm guessing there aren't any messages on the consoles, although I have > > no real way to confirm. > > > > It doesn't seem to be application related (unless maybe it's X itself or > > the nvidia drivers), and is not load related. .. it can happen while > > I'm clicking around in firefox, typeing on openoffice, coding in nedit > > or zend studio, highlighting text, etc.. etc... .. and of course it even > > happens when my back is turned (probably out of spite). > > > > On any other machine I might suspect the ram.. and I guess I'm kinda > > suspecting the ram here, but it is an opteron, and it's running with ECC > > ram... so ram really shouldn't be an issue right? or wrong? : ) > > > > > > Any suggestions on how I can determine the cause of the lockup? (or at > > least narrow it down). BTW these lockups occured in FC1 as well > > (currently running FC2T3). > > > > -- > > Marshall > > > > > -- > amd64-list mailing list > amd64-list at redhat.com > https://www.redhat.com/mailman/listinfo/amd64-list From bill at cse.ucdavis.edu Wed May 5 20:14:37 2004 From: bill at cse.ucdavis.edu (Bill Broadley) Date: Wed, 5 May 2004 13:14:37 -0700 Subject: I need help debugging a random lockup In-Reply-To: <1083785698.2132.22.camel@localhost.localdomain> References: <1083785698.2132.22.camel@localhost.localdomain> Message-ID: <20040505201437.GB18202@cse.ucdavis.edu> How hot is the air coming out of the case? What are the CPU temperatures? Try turning off the nvidia drivers and use the xfree86 nv driver (2d only) and see if the freezes go away. What kind of disks do you have? IDE? SATA? SCSI? Controller? On Wed, May 05, 2004 at 03:34:58PM -0400, Marshall Lewis wrote: > I'm not sure how to begin debugging this, it's not something that I've > ever had happen on a linux system before. I have an opteron workstation > here at work, and it locks up more or less randomly... It's a complete > system freeze. There are no messages about it in /var/log/messages, and > I'm guessing there aren't any messages on the consoles, although I have > no real way to confirm. > > It doesn't seem to be application related (unless maybe it's X itself or > the nvidia drivers), and is not load related. .. it can happen while > I'm clicking around in firefox, typeing on openoffice, coding in nedit > or zend studio, highlighting text, etc.. etc... .. and of course it even > happens when my back is turned (probably out of spite). > > On any other machine I might suspect the ram.. and I guess I'm kinda > suspecting the ram here, but it is an opteron, and it's running with ECC > ram... so ram really shouldn't be an issue right? or wrong? : ) > > > Any suggestions on how I can determine the cause of the lockup? (or at > least narrow it down). BTW these lockups occured in FC1 as well > (currently running FC2T3). > > -- > Marshall > > > -- > amd64-list mailing list > amd64-list at redhat.com > https://www.redhat.com/mailman/listinfo/amd64-list -- Bill Broadley Computational Science and Engineering UC Davis From marshall at novafoundry.com Thu May 6 00:02:07 2004 From: marshall at novafoundry.com (Marshall Lewis) Date: Wed, 05 May 2004 20:02:07 -0400 Subject: I need help debugging a random lockup In-Reply-To: <007a01c432df$5ef31020$0500a8c0@laptop2> References: <1083785698.2132.22.camel@localhost.localdomain> <1083787804.2075.7.camel@localhost.localdomain> <007a01c432df$5ef31020$0500a8c0@laptop2> Message-ID: <1083801727.11844.19.camel@grendel> My workstation is actually running on a msi k8t master2-far. Single opteron 246 w/1gig ecc ram (2 512 sticks). How'd you notice the activity on the eth port? watching the light? I'm using the onboard sata, and it has an ide dvd-rom, but it's never been running during one of these lockups. I've noticed the some problems with the broadcom nic as well... problems with it being detected by the switch, sometimes I have to drop the interface and bring it backup before the switch will notice it. I've also seen on some of our other opteron boxes (might be a coincidence.. but I do believe the boxes that have had the problem are using the tg3 driver) where the switch won't auto-sense the speed correctly (registers 100mbit instead of 1000mbit) but the nic thinks it's running at full speed.... obviously this leads to issues : ) -- Marshall On Wed, 2004-05-05 at 16:27, John Griffin wrote: > we've been struggling w/ a lockup issue and I'm wondering if there is any > relationship- > we have > dual opterons (244s) > MSI K8D Master-F. > ECC memory > we're having a devil of a time getting our CRON scripts to burn backups on a > CDRW > I should say the isolated issue is on the portion of the script related to > the CD Burn program- when the system is at the point of completing the burn > (writing the table of contents?), our system locks up. > we noticed activity on our eth0 port and SCSI array at the moment the system > locks. > our thought is there is a conflict w/ our RAID (through our Adaptec > 39320A-R). > we also have discovered issues in our driver for the Broadcom gig-e on > board. We have been unable to implement the updated drivers for the > Broadcoms and are still using the Tigon3 drivers. > > Has anyone had this type of lockup? > > John Griffin > V1 Datacom Inc > > > > ----- Original Message ----- > From: "Marshall Lewis" > To: > Sent: Wednesday, May 05, 2004 1:10 PM > Subject: Re: I need help debugging a random lockup > > > > Well.. now I can reproduce it .. sorta.. of course right after sending > > this email I decide to try and chart some stuff in oo calc, and it has > > locked 5 times in the last half hour. I'm not any closer to determining > > the cause though... maybe it's 32 bit apps? (or maybe it's power > > fluctuations, or the room is too hot, or my monitors are too close > > together... ) : ) > > > > -- > > Marshall > > > > On Wed, 2004-05-05 at 15:34, Marshall Lewis wrote: > > > I'm not sure how to begin debugging this, it's not something that I've > > > ever had happen on a linux system before. I have an opteron workstation > > > here at work, and it locks up more or less randomly... It's a complete > > > system freeze. There are no messages about it in /var/log/messages, and > > > I'm guessing there aren't any messages on the consoles, although I have > > > no real way to confirm. > > > > > > It doesn't seem to be application related (unless maybe it's X itself or > > > the nvidia drivers), and is not load related. .. it can happen while > > > I'm clicking around in firefox, typeing on openoffice, coding in nedit > > > or zend studio, highlighting text, etc.. etc... .. and of course it even > > > happens when my back is turned (probably out of spite). > > > > > > On any other machine I might suspect the ram.. and I guess I'm kinda > > > suspecting the ram here, but it is an opteron, and it's running with ECC > > > ram... so ram really shouldn't be an issue right? or wrong? : ) > > > > > > > > > Any suggestions on how I can determine the cause of the lockup? (or at > > > least narrow it down). BTW these lockups occured in FC1 as well > > > (currently running FC2T3). > > > > > > -- > > > Marshall > > > > > > > > > -- > > amd64-list mailing list > > amd64-list at redhat.com > > https://www.redhat.com/mailman/listinfo/amd64-list > From marshall at novafoundry.com Thu May 6 00:02:16 2004 From: marshall at novafoundry.com (Marshall Lewis) Date: Wed, 05 May 2004 20:02:16 -0400 Subject: I need help debugging a random lockup In-Reply-To: <20040505201437.GB18202@cse.ucdavis.edu> References: <1083785698.2132.22.camel@localhost.localdomain> <20040505201437.GB18202@cse.ucdavis.edu> Message-ID: <1083801736.11844.20.camel@grendel> Not sure about the cpu temp, I don't have any monitoring on it, the air blowing out the back is a bit warmer than I expected it to be though.. I'll try and get temp monitoring working tonight or tomorrow (I hadn't really considered it seriously until you mentioned it). I'll try swapping nvidia driver as well. The workstation has one SATA disk, via controller (built into the motherboard. I have virtually the same setup at home (ati card instead of nvidia, opteron 248 instead of 246, different brand of ram), but don't seem to run into the freeze problem at home (that is, I can't remember it happening) .. I'll try the oo calc thing tonight though and see if it works here. Thanks for the suggestions : ) -- Marshall On Wed, 2004-05-05 at 16:14, Bill Broadley wrote: > How hot is the air coming out of the case? What are the CPU temperatures? > > Try turning off the nvidia drivers and use the xfree86 nv driver (2d only) > and see if the freezes go away. > > What kind of disks do you have? IDE? SATA? SCSI? Controller? > > On Wed, May 05, 2004 at 03:34:58PM -0400, Marshall Lewis wrote: > > I'm not sure how to begin debugging this, it's not something that I've > > ever had happen on a linux system before. I have an opteron workstation > > here at work, and it locks up more or less randomly... It's a complete > > system freeze. There are no messages about it in /var/log/messages, and > > I'm guessing there aren't any messages on the consoles, although I have > > no real way to confirm. > > > > It doesn't seem to be application related (unless maybe it's X itself or > > the nvidia drivers), and is not load related. .. it can happen while > > I'm clicking around in firefox, typeing on openoffice, coding in nedit > > or zend studio, highlighting text, etc.. etc... .. and of course it even > > happens when my back is turned (probably out of spite). > > > > On any other machine I might suspect the ram.. and I guess I'm kinda > > suspecting the ram here, but it is an opteron, and it's running with ECC > > ram... so ram really shouldn't be an issue right? or wrong? : ) > > > > > > Any suggestions on how I can determine the cause of the lockup? (or at > > least narrow it down). BTW these lockups occured in FC1 as well > > (currently running FC2T3). > > > > -- > > Marshall > > > > > > -- > > amd64-list mailing list > > amd64-list at redhat.com > > https://www.redhat.com/mailman/listinfo/amd64-list > > -- > Bill Broadley > Computational Science and Engineering > UC Davis > From dsavage at peaknet.net Thu May 6 03:05:29 2004 From: dsavage at peaknet.net (Robert G. (Doc) Savage) Date: Wed, 05 May 2004 22:05:29 -0500 Subject: I need help debugging a random lockup In-Reply-To: <1083801736.11844.20.camel@grendel> References: <1083785698.2132.22.camel@localhost.localdomain> <20040505201437.GB18202@cse.ucdavis.edu> <1083801736.11844.20.camel@grendel> Message-ID: <1083812678.4279.10.camel@lioness> On Wed, 2004-05-05 at 19:02, Marshall Lewis wrote: > Not sure about the cpu temp, I don't have any monitoring on it, the air > blowing out the back is a bit warmer than I expected it to be though.. > I'll try and get temp monitoring working tonight or tomorrow (I hadn't > really considered it seriously until you mentioned it). I'll try > swapping nvidia driver as well. > > The workstation has one SATA disk, via controller (built into the > motherboard. > > I have virtually the same setup at home (ati card instead of nvidia, > opteron 248 instead of 246, different brand of ram), but don't seem to > run into the freeze problem at home (that is, I can't remember it > happening) .. I'll try the oo calc thing tonight though and see if it > works here. > > Thanks for the suggestions : ) Marshall, The last time I had a system with random lockups like yours I eventually traced the cause to an old power supply. Those baby beer can electrolytic capacitors eventually dry up and don't filter the AC ripple voltage the way they did when new. The lockups vanished as soon as I replaced the P/S. Do you have a spare you can try? --Doc Savage Fairview Heights, IL From marshall at novafoundry.com Thu May 6 03:20:58 2004 From: marshall at novafoundry.com (Marshall Lewis) Date: Wed, 05 May 2004 23:20:58 -0400 Subject: I need help debugging a random lockup In-Reply-To: <1083812678.4279.10.camel@lioness> References: <1083785698.2132.22.camel@localhost.localdomain> <20040505201437.GB18202@cse.ucdavis.edu> <1083801736.11844.20.camel@grendel> <1083812678.4279.10.camel@lioness> Message-ID: <1083813658.2876.4.camel@grendel> On Wed, 2004-05-05 at 23:05, Robert G. (Doc) Savage wrote: > The last time I had a system with random lockups like yours I eventually > traced the cause to an old power supply. Those baby beer can > electrolytic capacitors eventually dry up and don't filter the AC ripple > voltage the way they did when new. The lockups vanished as soon as I > replaced the P/S. Do you have a spare you can try? > > --Doc Savage > Fairview Heights, IL > Thanks for the suggestion.... The power supply is just about brand new (installed in november), but that doesn't eliminate it as a potential cause... I'll see what else I can try this week, and if it's still locking up, I'll probably pull the power supply out of my home workstation and try that. Or .. hmmm : ) one of the other developers is having a workstation built right now.. maybe I can borrow his tomorrow... -- Marshall From jgriffin at v1data.com Thu May 6 17:19:19 2004 From: jgriffin at v1data.com (John Griffin) Date: Thu, 6 May 2004 10:19:19 -0700 Subject: I need help debugging a random lockup References: <1083785698.2132.22.camel@localhost.localdomain><1083787804.2075.7.camel@localhost.localdomain><007a01c432df$5ef31020$0500a8c0@laptop2> <1083801727.11844.19.camel@grendel> Message-ID: <001d01c4338e$44dad060$0500a8c0@laptop2> we have been working this issue long enough that we started noticing the eth port and drive lights bumped at the same moment the system locked. try this link for a driver update- http://www.broadcom.com/drivers/downloaddrivers.php I cannot find where I read this, but remember seeing that there were improvements w/ this driver over the tigon3 driver. Does anyone know if the native Redhat tigon3 drivers are better/worse suited for Broadcom 57xx than the provided driver by Broadcom for Linux. I'm experiencing a learning curve on kernel source tree and having issues implementing the driver linked above. ----- Original Message ----- From: "Marshall Lewis" To: "AMD 64 Fedora List" Sent: Wednesday, May 05, 2004 5:02 PM Subject: Re: I need help debugging a random lockup > My workstation is actually running on a msi k8t master2-far. Single > opteron 246 w/1gig ecc ram (2 512 sticks). > > How'd you notice the activity on the eth port? watching the light? > I'm using the onboard sata, and it has an ide dvd-rom, but it's never > been running during one of these lockups. > > I've noticed the some problems with the broadcom nic as well... problems > with it being detected by the switch, sometimes I have to drop the > interface and bring it backup before the switch will notice it. I've > also seen on some of our other opteron boxes (might be a coincidence.. > but I do believe the boxes that have had the problem are using the tg3 > driver) where the switch won't auto-sense the speed correctly (registers > 100mbit instead of 1000mbit) but the nic thinks it's running at full > speed.... obviously this leads to issues : ) > > -- > Marshall > > > On Wed, 2004-05-05 at 16:27, John Griffin wrote: > > we've been struggling w/ a lockup issue and I'm wondering if there is any > > relationship- > > we have > > dual opterons (244s) > > MSI K8D Master-F. > > ECC memory > > we're having a devil of a time getting our CRON scripts to burn backups on a > > CDRW > > I should say the isolated issue is on the portion of the script related to > > the CD Burn program- when the system is at the point of completing the burn > > (writing the table of contents?), our system locks up. > > we noticed activity on our eth0 port and SCSI array at the moment the system > > locks. > > our thought is there is a conflict w/ our RAID (through our Adaptec > > 39320A-R). > > we also have discovered issues in our driver for the Broadcom gig-e on > > board. We have been unable to implement the updated drivers for the > > Broadcoms and are still using the Tigon3 drivers. > > > > Has anyone had this type of lockup? > > > > John Griffin > > V1 Datacom Inc > > > > > > > > ----- Original Message ----- > > From: "Marshall Lewis" > > To: > > Sent: Wednesday, May 05, 2004 1:10 PM > > Subject: Re: I need help debugging a random lockup > > > > > > > Well.. now I can reproduce it .. sorta.. of course right after sending > > > this email I decide to try and chart some stuff in oo calc, and it has > > > locked 5 times in the last half hour. I'm not any closer to determining > > > the cause though... maybe it's 32 bit apps? (or maybe it's power > > > fluctuations, or the room is too hot, or my monitors are too close > > > together... ) : ) > > > > > > -- > > > Marshall > > > > > > On Wed, 2004-05-05 at 15:34, Marshall Lewis wrote: > > > > I'm not sure how to begin debugging this, it's not something that I've > > > > ever had happen on a linux system before. I have an opteron workstation > > > > here at work, and it locks up more or less randomly... It's a complete > > > > system freeze. There are no messages about it in /var/log/messages, and > > > > I'm guessing there aren't any messages on the consoles, although I have > > > > no real way to confirm. > > > > > > > > It doesn't seem to be application related (unless maybe it's X itself or > > > > the nvidia drivers), and is not load related. .. it can happen while > > > > I'm clicking around in firefox, typeing on openoffice, coding in nedit > > > > or zend studio, highlighting text, etc.. etc... .. and of course it even > > > > happens when my back is turned (probably out of spite). > > > > > > > > On any other machine I might suspect the ram.. and I guess I'm kinda > > > > suspecting the ram here, but it is an opteron, and it's running with ECC > > > > ram... so ram really shouldn't be an issue right? or wrong? : ) > > > > > > > > > > > > Any suggestions on how I can determine the cause of the lockup? (or at > > > > least narrow it down). BTW these lockups occured in FC1 as well > > > > (currently running FC2T3). > > > > > > > > -- > > > > Marshall > > > > > > > > > > > > > -- > > > amd64-list mailing list > > > amd64-list at redhat.com > > > https://www.redhat.com/mailman/listinfo/amd64-list > > > > > -- > amd64-list mailing list > amd64-list at redhat.com > https://www.redhat.com/mailman/listinfo/amd64-list From msmiles at agere.com Thu May 6 17:54:37 2004 From: msmiles at agere.com (Smiles, Mark (Mark)) Date: Thu, 6 May 2004 18:54:37 +0100 Subject: amd64-list Digest, Vol 3, Issue 5 Message-ID: <04E6D4BACE356A42AE03B1FBF07BB8172EC0F6@enex2ku01.agere.com> One thing that is missing from this discussion is voltage regulators to the memory on the motherboards, This has been seen on some Opteron systems we have looked at. Regards, Mark Smiles From maurice at harddata.com Fri May 7 03:47:54 2004 From: maurice at harddata.com (Maurice Hilarius) Date: Thu, 06 May 2004 21:47:54 -0600 Subject: amd64-list Digest, Vol 3, Issue 5 In-Reply-To: <04E6D4BACE356A42AE03B1FBF07BB8172EC0F6@enex2ku01.agere.com > References: <04E6D4BACE356A42AE03B1FBF07BB8172EC0F6@enex2ku01.agere.com> Message-ID: <6.0.3.0.2.20040506214700.04169200@mail.harddata.com> With regards to your message at 11:54 AM 5/6/04, Smiles, Mark (Mark). Where you stated: >One thing that is missing from this discussion is voltage regulators to >the memory on the motherboards, >This has been seen on some Opteron systems we have looked at. > >Regards, >Mark Smiles Exactly. Run memtest86 to check the RAM. Let it run overnight and see what it finds. With our best regards, Maurice W. Hilarius Telephone: 01-780-456-9771 Hard Data Ltd. FAX: 01-780-456-9772 11060 - 166 Avenue mailto:maurice at harddata.com Edmonton, AB, Canada http://www.harddata.com/ T5X 1Y3 Waiting for spring in Edmonton.. -------------- next part -------------- An HTML attachment was scrubbed... URL: From marshall at novafoundry.com Sat May 8 17:37:40 2004 From: marshall at novafoundry.com (Marshall Lewis) Date: Sat, 08 May 2004 13:37:40 -0400 Subject: I need help debugging a random lockup In-Reply-To: <1083801736.11844.20.camel@grendel> References: <1083785698.2132.22.camel@localhost.localdomain> <20040505201437.GB18202@cse.ucdavis.edu> <1083801736.11844.20.camel@grendel> Message-ID: <1084037860.5907.27.camel@grendel> Did end up verifying the cpu temp and it was pretty low (under 40 deg C). Kinda stuck on the NVidia driver thing though, it's a dual-head setup, and I'm way to used to actually using both monitors : ) .. the nv driver apparently doesn't support dual-head on a single card. Additionally I was wrong about it not locking up at home.. I've managed to get it to happen twice so far today (that's an ATI card using the driver that comes with xorg). I had tried swapping the power supply at work, but it didn't make a difference (still locks up). I'm fairly convinced that it has to do with running 32-bit apps, because it only seems to happen then (primarily FireFox and OpenOffice). -- Marshall On Wed, 2004-05-05 at 20:02, Marshall Lewis wrote: > Not sure about the cpu temp, I don't have any monitoring on it, the air > blowing out the back is a bit warmer than I expected it to be though.. > I'll try and get temp monitoring working tonight or tomorrow (I hadn't > really considered it seriously until you mentioned it). I'll try > swapping nvidia driver as well. > > The workstation has one SATA disk, via controller (built into the > motherboard. > > I have virtually the same setup at home (ati card instead of nvidia, > opteron 248 instead of 246, different brand of ram), but don't seem to > run into the freeze problem at home (that is, I can't remember it > happening) .. I'll try the oo calc thing tonight though and see if it > works here. > > Thanks for the suggestions : ) > > -- > Marshall > > On Wed, 2004-05-05 at 16:14, Bill Broadley wrote: > > How hot is the air coming out of the case? What are the CPU temperatures? > > > > Try turning off the nvidia drivers and use the xfree86 nv driver (2d only) > > and see if the freezes go away. > > > > What kind of disks do you have? IDE? SATA? SCSI? Controller? > > > > On Wed, May 05, 2004 at 03:34:58PM -0400, Marshall Lewis wrote: > > > I'm not sure how to begin debugging this, it's not something that I've > > > ever had happen on a linux system before. I have an opteron workstation > > > here at work, and it locks up more or less randomly... It's a complete > > > system freeze. There are no messages about it in /var/log/messages, and > > > I'm guessing there aren't any messages on the consoles, although I have > > > no real way to confirm. > > > > > > It doesn't seem to be application related (unless maybe it's X itself or > > > the nvidia drivers), and is not load related. .. it can happen while > > > I'm clicking around in firefox, typeing on openoffice, coding in nedit > > > or zend studio, highlighting text, etc.. etc... .. and of course it even > > > happens when my back is turned (probably out of spite). > > > > > > On any other machine I might suspect the ram.. and I guess I'm kinda > > > suspecting the ram here, but it is an opteron, and it's running with ECC > > > ram... so ram really shouldn't be an issue right? or wrong? : ) > > > > > > > > > Any suggestions on how I can determine the cause of the lockup? (or at > > > least narrow it down). BTW these lockups occured in FC1 as well > > > (currently running FC2T3). > > > > > > -- > > > Marshall > > > > > > > > > -- > > > amd64-list mailing list > > > amd64-list at redhat.com > > > https://www.redhat.com/mailman/listinfo/amd64-list > > > > -- > > Bill Broadley > > Computational Science and Engineering > > UC Davis > > > From marshall at novafoundry.com Wed May 12 02:28:46 2004 From: marshall at novafoundry.com (Marshall Lewis) Date: Tue, 11 May 2004 22:28:46 -0400 Subject: amd64-list Digest, Vol 3, Issue 5 In-Reply-To: <6.0.3.0.2.20040506214700.04169200@mail.harddata.com> References: <04E6D4BACE356A42AE03B1FBF07BB8172EC0F6@enex2ku01.agere.com> <6.0.3.0.2.20040506214700.04169200@mail.harddata.com> Message-ID: <1084328923.4850.5.camel@grendel> Well, I've tried memtest for about 30min, I'm going to set it to run over night once I'm done with this email... 2 questions though.. since it's ecc ram should I be running memtest with ecc turned on? and, any idea why when I have usb enabled on the motherboard memtest would lock the system (I discovered this when while running memtest on the second test, the lights on my usb devices flickered, then the computer locked). In my first pass I did have 5 errors apparently at the same memory address, but they didn't reappear on the second pass... Anyway, I'll continue running it. -- Marshall On Thu, 2004-05-06 at 23:47, Maurice Hilarius wrote: > With regards to your message at 11:54 AM 5/6/04, Smiles, Mark (Mark). > Where you stated: > > One thing that is missing from this discussion is voltage regulators > > to > > the memory on the motherboards, > > This has been seen on some Opteron systems we have looked at. > > > > Regards, > > Mark Smiles > > > Exactly. Run memtest86 to check the RAM. > > Let it run overnight and see what it finds. > > > With our best regards, > > Maurice W. Hilarius Telephone: 01-780-456-9771 > Hard Data Ltd. FAX: 01-780-456-9772 > 11060 - 166 Avenue mailto:maurice at harddata.com > Edmonton, AB, Canada http://www.harddata.com/ > T5X 1Y3 > > Waiting for spring in Edmonton.. > > > > ______________________________________________________________________ > -- > amd64-list mailing list > amd64-list at redhat.com > https://www.redhat.com/mailman/listinfo/amd64-list From marshall at novafoundry.com Wed May 12 02:32:36 2004 From: marshall at novafoundry.com (Marshall Lewis) Date: Tue, 11 May 2004 22:32:36 -0400 Subject: dual opteron board kernel panics on boot with smp kernel Message-ID: <1084329156.4850.9.camel@grendel> Hello, I just put fc2t3 on one of our servers at work to do some testing, and can not get it to boot with any of the smp kernels (up kernels boot just fine). I don't think this is fedora specific, but I'm wondering if anyone else has had the problem. It seems to be happening when it trys to initialize? the second cpu. The machine in question has 6 gigs of ram, and I do seem to remember there being a problem with that in older kernels (2.4 series). I'll try and provide more info on the server tomorrow. .. I'll probably end up running memtest on this box as well, maybe that will show me something. -- Marshall From marshall at novafoundry.com Wed May 12 10:36:52 2004 From: marshall at novafoundry.com (Marshall Lewis) Date: Wed, 12 May 2004 06:36:52 -0400 Subject: dual opteron board kernel panics on boot with smp kernel In-Reply-To: <20040512032837.GC22102@comcast.net> References: <1084329156.4850.9.camel@grendel> <20040512032837.GC22102@comcast.net> Message-ID: <1084358212.4628.2.camel@grendel> Well, the 327 smp kernel didn't work, and the new 358 smp kernel didn't work.... I'll try some of the dev kernels and recompiling a kernel today (along with running memtest). Hopefully I can get the box running with smp : ) -- Marshall On Tue, 2004-05-11 at 23:28, Justin M. Forbes wrote: > On Tue, May 11, 2004 at 10:32:36PM -0400, Marshall Lewis wrote: > > > > I just put fc2t3 on one of our servers at work to do some testing, and > > can not get it to boot with any of the smp kernels (up kernels boot just > > fine). I don't think this is fedora specific, but I'm wondering if > > anyone else has had the problem. It seems to be happening when it trys > > to initialize? the second cpu. The machine in question has 6 gigs of > > ram, and I do seem to remember there being a problem with that in older > > kernels (2.4 series). I'll try and provide more info on the server > > tomorrow. .. I'll probably end up running memtest on this box as well, > > maybe that will show me something. > > > I thought the actual test3 kernel would boot fine, but there was a series > of kernels which would not boot AMD64 after test 3. Current devel kernels > seem fine for UP and SMP opteron. > > Justin > > > From jerrywone at cox.net Fri May 14 12:38:17 2004 From: jerrywone at cox.net (jerry) Date: Fri, 14 May 2004 08:38:17 -0400 Subject: machine hanging FC2T3 release for AMD64 on nForce3 Gigabyte K8N Pro Message-ID: <40A4BDB9.9020106@cox.net> Hi all: In a fit of somewhat misguided inspiration I installed the complete FC2 Test 3 for AMD64 on an Gigabyte K8N Pro mobo with nvidia nforce 3 with AMD64 3000+, 512 meg DDR400, Maxtor 6Y120P0 120 gig hard drive, IO Magic CDRW 5232, Maddog GeForceFX5200 video using NV34, RTL-8169 Gigabit ethernet, TSB43AB23 IEEE-1394a-2000 Controller unused. It's been locking up mysteriously. the hardware was not exactly what i had seen on lists as working before another machine went down and hastened a new machine build. the exact mobo was another $100+ up and already over budget, so i thought i'd have somewhat of a project on my hands. ran NON AMD64 FC1 without these problems. Symptoms include GKrellM system monitor shows little activity but moves along so CPU working and not complete "hang", mouse pointer tracks, but no activity on clicks, control-alt-del doesn't, forcing a reset switch, file system integrity check, etc. The installer may have caused the other grub partitions unbootable unless i've been rooted or somesuch as the older /boot is seen as empty. the other partition data appears accessible luckily so far. FC2T3's K3b burned older FC1 partition data ok. I'd rather go forward to final FC2 than back to FC1, but the hanging is getting annoying... I'm not running much besides vanilla FC2T3. Additions listed below: Compiled and installed Gnotime (a newer name for Gnome Time Tracker) with some policy errors, but appears to runs ok. Mucked with NVIDIA drivers but it's a little fuzzy what exactly I did with NVIDIA in the excitement of a 64 bit release. For some reason i thought i needed the nvidia drivers for better nForce3 support. little did i (and still don't) know... Looking for MP3 support for xmms from GURULabs, one of which killed the regular sound, so I went to the helix player hxplay from helixcommunity (which doesn't give graphical icons, but otherwise seems to work ok for .mp3s if willing to drill down directories repeatedly since it loses your last directory use). the prelink daemon process is somewhat of a surprise when it kicks in. as you might have already guessed, i'm not a kernel hacker yet... and this is a mess, but i thought it would be important to let some people know before general release that there may be a problem here. any other specifics i can look up please let me know. any help in troubleshooting appreciated, jerry From Axel.Thimm at ATrpms.net Fri May 14 12:41:42 2004 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Fri, 14 May 2004 14:41:42 +0200 Subject: Socket-754 Motherboard recommendation? Message-ID: <20040514124142.GA27275@neu.nirvana> Hi, I am looking at setting up an inexpensive Athlon 64 system hopefully with SATA boot support. My primary OS would be FC2, probably later RHEL3/x86_64, too. I understand there are (or were?) issues with different SATA controllers. What are currently well running boards for Socket 754, e.g. Athlon 64, under FC2? Thanks! -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From robert.goshko at axis-dev.ca Fri May 14 13:15:23 2004 From: robert.goshko at axis-dev.ca (Robert Goshko) Date: Fri, 14 May 2004 07:15:23 -0600 Subject: Socket-754 Motherboard recommendation? In-Reply-To: <20040514124142.GA27275@neu.nirvana> References: <20040514124142.GA27275@neu.nirvana> Message-ID: <40A4C66B.1080709@axis-dev.ca> Axel Thimm wrote: > Hi, > > I am looking at setting up an inexpensive Athlon 64 system hopefully > with SATA boot support. My primary OS would be FC2, probably later > RHEL3/x86_64, too. > > I understand there are (or were?) issues with different SATA > controllers. I have the MSI KT8 Neo-FIS2R with two S-ATA drives (no P-ATA HD's) running Mandrake 10.0rc1 for AMD64 no problems. The promise controller built in works great, installed straight from the CD. -- ...Rob -- "Never tell me the odds!" -- Han Solo ===================================================================== Robert Goshko Axis Computer Consulting Services, Inc President Sherwood Park, Alberta, Canada http://www.axis-dev.ca/ Supporting the Revolution In Your World ===================================================================== Registered Linux User #260513 GNU/Linux i686 2.6.3-7mdk-725ca Mandrake Linux 10.0 mobile AMD Athlon(tm) 4 1500+ 07:04:00 up 11 min, 0 users, load average: 0.36, 0.45, 0.29 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 242 bytes Desc: OpenPGP digital signature URL: From marshall at novafoundry.com Fri May 14 19:35:36 2004 From: marshall at novafoundry.com (Marshall Lewis) Date: Fri, 14 May 2004 15:35:36 -0400 Subject: I need help debugging a random lockup In-Reply-To: <007a01c432df$5ef31020$0500a8c0@laptop2> References: <1083785698.2132.22.camel@localhost.localdomain> <1083787804.2075.7.camel@localhost.localdomain> <007a01c432df$5ef31020$0500a8c0@laptop2> Message-ID: <1084563336.2940.5.camel@localhost.localdomain> I found a new beta bios on msi's site, and it seems to have solved the problem for me. I no longer have to disable usb in order to run memtest, and I can't seem to get the box to lock up by running openoffice anymore : ) .. it might fix you're problem as well. I'm going to keep playing with it through the weekend and on monday before I really start believing it's fixed though : ) -- Marshall On Wed, 2004-05-05 at 16:27, John Griffin wrote: > we've been struggling w/ a lockup issue and I'm wondering if there is any > relationship- > we have > dual opterons (244s) > MSI K8D Master-F. > ECC memory > we're having a devil of a time getting our CRON scripts to burn backups on a > CDRW > I should say the isolated issue is on the portion of the script related to > the CD Burn program- when the system is at the point of completing the burn > (writing the table of contents?), our system locks up. > we noticed activity on our eth0 port and SCSI array at the moment the system > locks. > our thought is there is a conflict w/ our RAID (through our Adaptec > 39320A-R). > we also have discovered issues in our driver for the Broadcom gig-e on > board. We have been unable to implement the updated drivers for the > Broadcoms and are still using the Tigon3 drivers. > > Has anyone had this type of lockup? > > John Griffin > V1 Datacom Inc > > > > ----- Original Message ----- > From: "Marshall Lewis" > To: > Sent: Wednesday, May 05, 2004 1:10 PM > Subject: Re: I need help debugging a random lockup > > > > Well.. now I can reproduce it .. sorta.. of course right after sending > > this email I decide to try and chart some stuff in oo calc, and it has > > locked 5 times in the last half hour. I'm not any closer to determining > > the cause though... maybe it's 32 bit apps? (or maybe it's power > > fluctuations, or the room is too hot, or my monitors are too close > > together... ) : ) > > > > -- > > Marshall > > > > On Wed, 2004-05-05 at 15:34, Marshall Lewis wrote: > > > I'm not sure how to begin debugging this, it's not something that I've > > > ever had happen on a linux system before. I have an opteron workstation > > > here at work, and it locks up more or less randomly... It's a complete > > > system freeze. There are no messages about it in /var/log/messages, and > > > I'm guessing there aren't any messages on the consoles, although I have > > > no real way to confirm. > > > > > > It doesn't seem to be application related (unless maybe it's X itself or > > > the nvidia drivers), and is not load related. .. it can happen while > > > I'm clicking around in firefox, typeing on openoffice, coding in nedit > > > or zend studio, highlighting text, etc.. etc... .. and of course it even > > > happens when my back is turned (probably out of spite). > > > > > > On any other machine I might suspect the ram.. and I guess I'm kinda > > > suspecting the ram here, but it is an opteron, and it's running with ECC > > > ram... so ram really shouldn't be an issue right? or wrong? : ) > > > > > > > > > Any suggestions on how I can determine the cause of the lockup? (or at > > > least narrow it down). BTW these lockups occured in FC1 as well > > > (currently running FC2T3). > > > > > > -- > > > Marshall > > > > > > > > > -- > > amd64-list mailing list > > amd64-list at redhat.com > > https://www.redhat.com/mailman/listinfo/amd64-list > From marshall at novafoundry.com Tue May 18 17:18:34 2004 From: marshall at novafoundry.com (Marshall Lewis) Date: Tue, 18 May 2004 13:18:34 -0400 Subject: I need help debugging a random lockup In-Reply-To: <1084563336.2940.5.camel@localhost.localdomain> References: <1083785698.2132.22.camel@localhost.localdomain> <1083787804.2075.7.camel@localhost.localdomain> <007a01c432df$5ef31020$0500a8c0@laptop2> <1084563336.2940.5.camel@localhost.localdomain> Message-ID: <1084900714.7009.6.camel@localhost.localdomain> Well, my random lockups have disappeared. If anyone else is running on a MSI K8T Master motherboard, I suggest installing the beta bios from the MSI site. Thanks for all of your suggestions. -- Marshall On Fri, 2004-05-14 at 15:35, Marshall Lewis wrote: > I found a new beta bios on msi's site, and it seems to have solved the > problem for me. I no longer have to disable usb in order to run > memtest, and I can't seem to get the box to lock up by running > openoffice anymore : ) .. it might fix you're problem as well. I'm > going to keep playing with it through the weekend and on monday before I > really start believing it's fixed though : ) > > -- > Marshall > > On Wed, 2004-05-05 at 16:27, John Griffin wrote: > > we've been struggling w/ a lockup issue and I'm wondering if there is any > > relationship- > > we have > > dual opterons (244s) > > MSI K8D Master-F. > > ECC memory > > we're having a devil of a time getting our CRON scripts to burn backups on a > > CDRW > > I should say the isolated issue is on the portion of the script related to > > the CD Burn program- when the system is at the point of completing the burn > > (writing the table of contents?), our system locks up. > > we noticed activity on our eth0 port and SCSI array at the moment the system > > locks. > > our thought is there is a conflict w/ our RAID (through our Adaptec > > 39320A-R). > > we also have discovered issues in our driver for the Broadcom gig-e on > > board. We have been unable to implement the updated drivers for the > > Broadcoms and are still using the Tigon3 drivers. > > > > Has anyone had this type of lockup? > > > > John Griffin > > V1 Datacom Inc > > > > > > > > ----- Original Message ----- > > From: "Marshall Lewis" > > To: > > Sent: Wednesday, May 05, 2004 1:10 PM > > Subject: Re: I need help debugging a random lockup > > > > > > > Well.. now I can reproduce it .. sorta.. of course right after sending > > > this email I decide to try and chart some stuff in oo calc, and it has > > > locked 5 times in the last half hour. I'm not any closer to determining > > > the cause though... maybe it's 32 bit apps? (or maybe it's power > > > fluctuations, or the room is too hot, or my monitors are too close > > > together... ) : ) > > > > > > -- > > > Marshall > > > > > > On Wed, 2004-05-05 at 15:34, Marshall Lewis wrote: > > > > I'm not sure how to begin debugging this, it's not something that I've > > > > ever had happen on a linux system before. I have an opteron workstation > > > > here at work, and it locks up more or less randomly... It's a complete > > > > system freeze. There are no messages about it in /var/log/messages, and > > > > I'm guessing there aren't any messages on the consoles, although I have > > > > no real way to confirm. > > > > > > > > It doesn't seem to be application related (unless maybe it's X itself or > > > > the nvidia drivers), and is not load related. .. it can happen while > > > > I'm clicking around in firefox, typeing on openoffice, coding in nedit > > > > or zend studio, highlighting text, etc.. etc... .. and of course it even > > > > happens when my back is turned (probably out of spite). > > > > > > > > On any other machine I might suspect the ram.. and I guess I'm kinda > > > > suspecting the ram here, but it is an opteron, and it's running with ECC > > > > ram... so ram really shouldn't be an issue right? or wrong? : ) > > > > > > > > > > > > Any suggestions on how I can determine the cause of the lockup? (or at > > > > least narrow it down). BTW these lockups occured in FC1 as well > > > > (currently running FC2T3). > > > > > > > > -- > > > > Marshall > > > > > > > > > > > > > -- > > > amd64-list mailing list > > > amd64-list at redhat.com > > > https://www.redhat.com/mailman/listinfo/amd64-list > > > From dsievers at ucla.edu Thu May 20 16:58:58 2004 From: dsievers at ucla.edu (Douglas Sievers) Date: Thu, 20 May 2004 09:58:58 -0700 Subject: FC2 - x86-64 and Asus K8V Deluxe motherboard ? Message-ID: <40ACE3D2.5060100@ucla.edu> Hi Fedora fans, I am building a new system based on an AMD Athlon64 3400+ processor. I have an Asus K8V Deluxe mobo on order, but it has not been delivered. Has anyone had experience with this mobo on FC2? Also, those who know, what's a good video card for this system? I'm looking at an eVGA GeForce FX 5700LE, but there might be a voltage level issue with this mobo running it at 8x AGP mode. Thanks all! Doug Sievers dsievers at ucla.edu From ckloiber at ckloiber.com Thu May 20 18:03:34 2004 From: ckloiber at ckloiber.com (Chris Kloiber) Date: Fri, 21 May 2004 02:03:34 +0800 Subject: FC2 - x86-64 and Asus K8V Deluxe motherboard ? In-Reply-To: <40ACE3D2.5060100@ucla.edu> References: <40ACE3D2.5060100@ucla.edu> Message-ID: <1085076214.4351.19.camel@roadrash.rdu.redhat.com> On Fri, 2004-05-21 at 00:58, Douglas Sievers wrote: > Hi Fedora fans, > > I am building a new system based on an AMD Athlon64 3400+ processor. I > have an Asus K8V Deluxe mobo on order, but it has not been delivered. > Has anyone had experience with this mobo on FC2? Direct experience, no. But be sure to search the archives of all the lists. > Also, those who know, what's a good video card for this system? I'm > looking at an eVGA GeForce FX 5700LE, but there might be a voltage level > issue with this mobo running it at 8x AGP mode. Linux AGP does not yet support 8x (perhaps the nVidia drivers do, I'm not sure). Run it at 4x max for now. -- Chris Kloiber From amd64 at purple.dropbear.id.au Fri May 21 06:03:07 2004 From: amd64 at purple.dropbear.id.au (Ashley J Gittins) Date: Fri, 21 May 2004 16:03:07 +1000 Subject: FC2 - x86-64 and Asus K8V Deluxe motherboard ? In-Reply-To: <40ACE3D2.5060100@ucla.edu> References: <40ACE3D2.5060100@ucla.edu> Message-ID: <200405211603.07398.amd64@purple.dropbear.id.au> On Fri, 21 May 2004 02:58 am, Douglas Sievers wrote: > Hi Fedora fans, > > I am building a new system based on an AMD Athlon64 3400+ processor. I > have an Asus K8V Deluxe mobo on order, but it has not been delivered. > Has anyone had experience with this mobo on FC2? Ask me in a week or two :-) I've had no show-stopper issues with that mobo and FC1. I updated to some 2.6 kernels, and have been pretty happy with it. I have a few stability issues (probably from nvidia binary drivers or X), and updatedb cripples the system each night, but on the whole it's been good. I won't be moving to FC2 until nvidia release compatible binary drivers (with 4k stacks support). I would not say that going to amd64 is easy or painless, you have to be prepared to spend time compiling and troubleshooting packages that fedora doesn't include. Some things (like Jack) I still can't get to work, but I'm leaving that 'till I move to a more stable but recent kernel, which in turn is waiting for nvidia (!). > Also, those who know, what's a good video card for this system? I'm > looking at an eVGA GeForce FX 5700LE, but there might be a voltage level > issue with this mobo running it at 8x AGP mode. Doubt I can help you there. FWIW though, I'm running a GeForce4 Ti 4400. Runs UT2004-demo-64bit-linux rather nicely. -- Regards, Ashley J Gittins web: http://www.purple.dropbear.id.au jabber: agittins at purple.dropbear.id.au From ckloiber at ckloiber.com Fri May 21 10:37:43 2004 From: ckloiber at ckloiber.com (Chris Kloiber) Date: Fri, 21 May 2004 18:37:43 +0800 Subject: FC2 - x86-64 and Asus K8V Deluxe motherboard ? In-Reply-To: <200405211603.07398.amd64@purple.dropbear.id.au> References: <40ACE3D2.5060100@ucla.edu> <200405211603.07398.amd64@purple.dropbear.id.au> Message-ID: <1085135862.8091.3.camel@galileo.ckloiber.com> On Fri, 2004-05-21 at 14:03, Ashley J Gittins wrote: > On Fri, 21 May 2004 02:58 am, Douglas Sievers wrote: > > Hi Fedora fans, > > > > I am building a new system based on an AMD Athlon64 3400+ processor. I > > have an Asus K8V Deluxe mobo on order, but it has not been delivered. > > Has anyone had experience with this mobo on FC2? > > Ask me in a week or two :-) > > I've had no show-stopper issues with that mobo and FC1. I updated to some 2.6 > kernels, and have been pretty happy with it. I have a few stability issues > (probably from nvidia binary drivers or X), and updatedb cripples the system > each night, but on the whole it's been good. I won't be moving to FC2 until > nvidia release compatible binary drivers (with 4k stacks support). I could of course be all wet, but I thought x86_64 still uses 8k stacks (because of the different memory model?) and the nVidia driver still works. My eMachines M6807 has the ATI 9600 video, with no 3D acceleration. > I would not say that going to amd64 is easy or painless, you have to be > prepared to spend time compiling and troubleshooting packages that fedora > doesn't include. Some things (like Jack) I still can't get to work, but I'm > leaving that 'till I move to a more stable but recent kernel, which in turn > is waiting for nvidia (!). > > > Also, those who know, what's a good video card for this system? I'm > > looking at an eVGA GeForce FX 5700LE, but there might be a voltage level > > issue with this mobo running it at 8x AGP mode. > > Doubt I can help you there. FWIW though, I'm running a GeForce4 Ti 4400. Runs > UT2004-demo-64bit-linux rather nicely. > > -- > Regards, > Ashley J Gittins > web: http://www.purple.dropbear.id.au > jabber: agittins at purple.dropbear.id.au -- Chris Kloiber From gene at czarc.net Fri May 21 12:01:16 2004 From: gene at czarc.net (Gene Czarcinski) Date: Fri, 21 May 2004 08:01:16 -0400 Subject: FC2 - x86-64 and Asus K8V Deluxe motherboard ? In-Reply-To: <40ACE3D2.5060100@ucla.edu> References: <40ACE3D2.5060100@ucla.edu> Message-ID: <200405210801.16792.gene@czarc.net> On Thursday 20 May 2004 12:58, Douglas Sievers wrote: > I am building a new system based on an AMD Athlon64 3400+ processor. I > have an Asus K8V Deluxe mobo on order, but it has not been delivered. > Has anyone had experience with this mobo on FC2? Similar experience ... I have an ASUS SK8V (940 pins) with an Opteron 140. I have one problem with the BIOS/mobo in that I could not connect my Dell 2000FP display through an analog KVM switch (bios overdrove the display although linux worked fine) ... the solution was to connect this system directly to the DVI interface and use the monitors switching to select this system. The other problem I have had is that the SATA drive has extremely poor performance under FC2 whereas it works fine under FC1 ... this has been bugzilla'ed. Gene From eugen at leitl.org Fri May 21 12:12:54 2004 From: eugen at leitl.org (Eugen Leitl) Date: Fri, 21 May 2004 14:12:54 +0200 Subject: FC2 - x86-64 and Asus K8V Deluxe motherboard ? In-Reply-To: <200405210801.16792.gene@czarc.net> References: <40ACE3D2.5060100@ucla.edu> <200405210801.16792.gene@czarc.net> Message-ID: <20040521121254.GR16732@leitl.org> On Fri, May 21, 2004 at 08:01:16AM -0400, Gene Czarcinski wrote: > The other problem I have had is that the SATA drive has extremely poor > performance under FC2 whereas it works fine under FC1 ... this has been > bugzilla'ed. Does your dmesg say something similiar to libata version 1.02 loaded. sata_promise version 0.92 ata1: SATA max UDMA/133 cmd 0xFFFFFF000003C200 ctl 0xFFFFFF000003C238 bmdma 0x0 irq 5 ata2: SATA max UDMA/133 cmd 0xFFFFFF000003C280 ctl 0xFFFFFF000003C2B8 bmdma 0x0 irq 5 [root at localhost eugen]# /sbin/hdparm /dev/hde /dev/hde: multcount = 16 (on) IO_support = 0 (default 16-bit) unmaskirq = 0 (off) using_dma = 1 (on) keepsettings = 0 (off) readonly = 0 (off) readahead = 256 (on) geometry = 16383/255/63, sectors = 72303840, start = 0 -- Eugen* Leitl leitl ______________________________________________________________ ICBM: 48.07078, 11.61144 http://www.leitl.org 8B29F6BE: 099D 78BA 2FD3 B014 B08A 7779 75B0 2443 8B29 F6BE http://moleculardevices.org http://nanomachines.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From amd64 at purple.dropbear.id.au Fri May 21 13:35:17 2004 From: amd64 at purple.dropbear.id.au (Ashley J Gittins) Date: Fri, 21 May 2004 23:35:17 +1000 Subject: FC2 - x86-64 and Asus K8V Deluxe motherboard ? In-Reply-To: <1085135862.8091.3.camel@galileo.ckloiber.com> References: <40ACE3D2.5060100@ucla.edu> <200405211603.07398.amd64@purple.dropbear.id.au> <1085135862.8091.3.camel@galileo.ckloiber.com> Message-ID: <200405212335.17530.amd64@purple.dropbear.id.au> On Fri, 21 May 2004 08:37 pm, Chris Kloiber wrote: > On Fri, 2004-05-21 at 14:03, Ashley J Gittins wrote: > > I've had no show-stopper issues with that mobo and FC1. I updated to some > > 2.6 kernels, and have been pretty happy with it. I have a few stability > > issues (probably from nvidia binary drivers or X), and updatedb cripples > > the system each night, but on the whole it's been good. I won't be moving > > to FC2 until nvidia release compatible binary drivers (with 4k stacks > > support). > > I could of course be all wet, but I thought x86_64 still uses 8k stacks > (because of the different memory model?) and the nVidia driver still > works. My eMachines M6807 has the ATI 9600 video, with no 3D > acceleration. Humidity is relative - perhaps it is I who is wetter :-) I will look into that, thanks. I had Ass-u-me-d that the 4k problem was pertinant to x86_64 as well, for no good reason! -- Regards, Ashley J Gittins web: http://www.purple.dropbear.id.au jabber: agittins at purple.dropbear.id.au From gene at czarc.net Fri May 21 13:57:56 2004 From: gene at czarc.net (Gene Czarcinski) Date: Fri, 21 May 2004 09:57:56 -0400 Subject: FC2 - x86-64 and Asus K8V Deluxe motherboard ? In-Reply-To: <20040521121254.GR16732@leitl.org> References: <40ACE3D2.5060100@ucla.edu> <200405210801.16792.gene@czarc.net> <20040521121254.GR16732@leitl.org> Message-ID: <200405210957.56735.gene@czarc.net> On Friday 21 May 2004 08:12, Eugen Leitl wrote: > libata version 1.02 loaded. > sata_promise version 0.92 Nope ... I am using a via adapter so I get sata_via. Gene From amd64 at linuxfarms.com Thu May 27 15:02:10 2004 From: amd64 at linuxfarms.com (Arthur Perry) Date: Thu, 27 May 2004 11:02:10 -0400 (EDT) Subject: GART error 11 Message-ID: Hi Dave, I am getting the same problem here, not only with RedHat's 2.4.21-9.0.1EL kernel, but also with SuSE Enterprise 8.0. What I have found is that RedHat has AGP support built into the kernel, and is not a module that can be loaded/unloaded. If your server does not have an AGP bus (as most servers do not), obviously the driver shouldn't do anything. However, this is not the case. After some test, it appears that the errors go away if you recompile the kernel without AGP support. Here is my proposed "root cause": If you boot the stock RedHat kernel, you will find that the GART ARPERTURE CONTROL REGISTER (function 3, offset 0x90) is enabled. If you do not have an AGP bus, this does not make sense to set up and configure. The errors that you see are captured by the Machine Check Architecture (MCA). The Northbridge portion is responsible for capturing these specific errors, and its global enable is in the MCG_CTL register located at MSR 0x017b. Your BIOS will be the one who enables this. You may even have an option for enabling or disabling the MCA. You also can set this in userspace. Anyways, I digress.. The object here is to not set up the GART if you do not have an AGP bus. If the AGP driver is built into the kernel, this whole portion should be skipped. Not just the initialization of the particular AGP bus. This register (function 3, offset 0x90) should not be configured. What I am going to do is test to see if this problem manifests itself with the mainline Linux code. If it does not appear, then I know there just may be a patch that has not been incorperated into the mainline distributions. This can be easily fixed. If it still exists, then I know that it is a implemenation issue that exists in the mainline kernel, and this is why all distributions would be affected. The question really comes down to: Is this problem an oversight of the distributors (silly! the agp driver should not be built into the kernel for server use!) or Kernel code implementation? (well, if no agp bus is present, then let's not go and set up the GART, right?) Thoughts? Best Regards, Art Perry On Wed, Nov 12, 2003 at 11:44:48AM -0500, Owen Scott Medd wrote: > We've just put RHEL3 AS on a newisys 2100 dual opteron (246 cpus) with > 16GB of PC2100 memory, a megaraid controller and the internal mptfusion > controller. Every so often, seemingly coincident with I/O load on the > megaraid controller, we get the following error: > > Northbridge status a40000000005001b > GART error 11 > Lost an northbridge error > NB error address 00000000fbf60000 > Error uncorrected > > The disk writes *appear* okay (we haven't found any errors so far) but > I'm not sure what these mean. These are machine check exceptions. Typically hardware errors. Run memtest, check cooling, PSU etc.. Dave -- AMD64-list mailing list AMD64-list at xxxxxxxxxx https://www.redhat.com/mailman/listinfo/amd64-list From davej at redhat.com Thu May 27 15:06:23 2004 From: davej at redhat.com (Dave Jones) Date: Thu, 27 May 2004 16:06:23 +0100 Subject: GART error 11 In-Reply-To: References: Message-ID: <20040527150623.GP22630@redhat.com> On Thu, May 27, 2004 at 11:02:10AM -0400, Arthur Perry wrote: > The question really comes down to: > Is this problem an oversight of the distributors (silly! the agp driver should not be built into the kernel for server use!) > or > Kernel code implementation? (well, if no agp bus is present, then let's not go and set up the GART, right?) If you don't have an AGP graphics card, there'll be nothing really set up, unless you are using the IOMMU feature of the x86-64 kernel. Setting up of GART tables etc only happens when the graphics drivers (DRI) asks it to. Does booting with iommu=off fix this for you? It may be that some driver is doing something that it shouldn't. If it does make the problem go away, what devices do you have in the system (lspci output please) Dave From arjanv at redhat.com Thu May 27 15:16:27 2004 From: arjanv at redhat.com (Arjan van de Ven) Date: Thu, 27 May 2004 17:16:27 +0200 Subject: GART error 11 In-Reply-To: References: Message-ID: <1085670987.7179.0.camel@laptop.fenrus.com> On Thu, 2004-05-27 at 17:02, Arthur Perry wrote: > Hi Dave, > > I am getting the same problem here, not only with RedHat's 2.4.21-9.0.1EL kernel, but also with SuSE Enterprise 8.0. > What I have found is that RedHat has AGP support built into the kernel, and is not a module that can be loaded/unloaded. > If your server does not have an AGP bus (as most servers do not), obviously the driver shouldn't do anything. > However, this is not the case. The AGP GART is also used as IOMMU ! So "does not do anything" is a incorrect assumption... -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From amd64 at linuxfarms.com Thu May 27 16:13:30 2004 From: amd64 at linuxfarms.com (Arthur Perry) Date: Thu, 27 May 2004 12:13:30 -0400 (EDT) Subject: GART error 11 (fwd) Message-ID: ---------- Forwarded message ---------- Date: Thu, 27 May 2004 12:12:29 -0400 (EDT) From: Arthur Perry To: amd64 at linuxfarms.com Subject: Re: GART error 11 (fwd) Arthur Perry Lead Linux Developer / Linux Systems Architect Validation, CSU Celestica Sair/Linux Gnu Certified Professional Providing professional Linux solutions for 7+ years ---------- Forwarded message ---------- Date: Thu, 27 May 2004 12:05:38 -0400 (EDT) From: Arthur Perry To: Andi Kleen Cc: linux-kernel at vger.kernel.org Subject: Re: GART error 11 (fwd) Thanks for all of your responses! I understand what you are saying. And perhaps this may be the case, maybe the hardware should not report these errors (which may not actually be gart errors after all) just because the GART has been set up. However, my failure mode seems to be that I only get these errors when the agp driver is loaded on a machine that does not have an agp bus. I also have IOMMUs disabled in the BIOS by default. The BIOS is not enabling the GART at all, so it must be done by the kernel. A boot into DOS will show the Gart Aperture Control Register set to all zeros, where a boot to Linux 2.4 w/AGP will boot with them enabled. Again, the failure mode recognised so far is that the "gart errors" appear when this register is set up. What the user sees at this point is even though they have the "GART error reporting enable" disabled, they still see "GART" errors. If you are suggesting that there may be a real hardware error here that is being misinterpreted by the kernel, my next course of action is to collect that real error syndrome and decode it. I can volunteer to assist with fixing this decoding function as well, since I have a good test case here. Arjan also suggested: >> The AGP GART is also used as IOMMU ! >> So "does not do anything" is a incorrect assumption... I am not really sure why this would be the case if I have disabled IOMMUs in the BIOS. But I have to first understand what this particular switch is doing. Are you suggesting that the kernel is going to use the GART for IOMMU purposes, or is the GART a part of the IOMMU? Thanks again for all of your help so far. Here is a lspci -vvv -x (as requested.. sorry it is a very exhaustive list..) 00:06.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8111 PCI (rev 07) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Reset- FastB2B- Capabilities: [c0] #08 [0086] Capabilities: [f0] #08 [8000] 00: 22 10 60 74 17 00 30 02 07 00 04 06 00 73 01 00 10: 00 00 00 00 00 00 00 00 00 01 01 44 20 20 00 22 20: 00 ec f0 ed f0 ff 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 c0 00 00 00 00 00 00 00 ff 00 0e 00 00:07.0 ISA bridge: Advanced Micro Devices [AMD] AMD-8111 LPC (rev 05) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- [disabled] [size=128K] Capabilities: [5c] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00: 02 10 52 47 87 00 90 02 27 00 00 03 10 40 00 00 10: 00 00 00 ed 01 20 00 00 00 20 00 ec 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 02 10 08 80 30: 00 00 00 00 5c 00 00 00 00 00 00 00 0b 01 08 00 08:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Reset- FastB2B- Capabilities: [a0] PCI-X non-bridge device. Command: DPERE+ ERO+ RBC=0 OST=4 Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=0, DMOST=0, DMCRS=0, RSCEM- Capabi lities: [b8] #08 [8000] Capabilities: [c0] #08 [0041] 00: 22 10 50 74 17 00 30 02 12 00 04 06 00 40 81 00 10: 00 00 00 00 00 00 00 00 08 09 0d 40 f1 01 20 22 20: f0 ff 00 00 f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 a0 00 00 00 00 00 00 00 ff 00 04 00 08:01.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01) (prog-if 10 [IO-APIC]) Subsystem: Advanced Micro Devices [AMD]: Unknown device 2b80 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- Reset- FastB2B- Capabilities: [a0] PCI-X non-bridge device. Command: DPERE+ ERO+ RBC=0 OST=0 Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=0, DMOST=0, DMCRS=0, RSCEM- Capabi lities: [b8] #08 [8000] 00: 22 10 50 74 17 00 30 02 12 00 04 06 00 40 81 00 10: 00 00 00 00 00 00 00 00 08 0e 12 80 31 31 20 22 20: 00 f1 00 f1 f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 a0 00 00 00 00 00 00 00 ff 00 04 00 08:02.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01) (prog-if 10 [IO-APIC]) Subsystem: Advanced Micro Devices [AMD]: Unknown device 2b80 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- Reset- FastB2B- Capabilities: [a0] PCI-X non-bridge device. Command: DPERE+ ERO+ RBC=0 OST=4 Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=0, DMOST=0, DMCRS=0, RSCEM- Capabi lities: [b8] #08 [8000] Capabilities: [90] #0c [0009] Capabilities: [98] Power Management version 2 Flags: PMEClk+ DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold-) Status: D0 PME-Enable+ DSel=0 DScale=0 PME- Capabilities: [c0] #08 [0043] 00: 22 10 50 74 17 00 30 02 12 00 04 06 00 40 81 00 10: 04 20 20 ee 00 00 00 00 08 13 1a 40 41 41 20 02 20: 00 ef f0 ef 01 f4 f1 f7 00 00 00 00 00 00 00 00 30: 00 00 00 00 a0 00 00 00 00 00 00 00 0b 01 04 00 08:03.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01) (prog-if 10 [IO-APIC]) Subsystem: Advanced Micro Devices [AMD]: Unknown device 2b80 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- Reset- FastB2B- Capabilities: [a0] PCI-X non-bridge device. Command: DPERE+ ERO+ RBC=0 OST=4 Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=0, DMOST=0, DMCRS=0, RSCEM- Capabi lities: [b8] #08 [8000] Capabilities: [90] #0c [0009] Capabilities: [98] Power Management version 2 Flags: PMEClk+ DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold-) Status: D0 PME-Enable+ DSel=0 DScale=0 PME- 00: 22 10 50 74 17 00 30 02 12 00 04 06 00 40 81 00 10: 04 40 20 ee 00 00 00 00 08 1b 22 40 51 51 20 02 20: 00 f0 f0 f0 01 f8 f1 fb 00 00 00 00 00 00 00 00 30: 00 00 00 00 a0 00 00 00 00 00 00 00 0b 01 04 00 08:04.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01) (prog-if 10 [IO-APIC]) Subsystem: Advanced Micro Devices [AMD]: Unknown device 2b80 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- [disabled] [size=1M] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Address: 0000000000000000 Data: 0000 Capabilities: [68] PCI-X non-bridge device. Command: DPERE- ERO- RBC=2 OST=0 Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=0, DMOST=0, DMCRS=0, RSCEM-00: 00 10 30 00 17 00 30 02 07 00 00 01 10 88 80 00 10: 01 30 00 00 04 00 01 f1 00 00 00 00 04 00 00 f1 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 10 00 10 30: 00 00 00 00 50 00 00 00 00 00 00 00 0a 01 11 12 0e:01.1 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 07) Subsystem: LSI Logic / Symbios Logic: Unknown device 1000 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- [disabled] [size=1M] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Address: 0000000000000000 Data: 0000 Capabilities: [68] PCI-X non-bridge device. Command: DPERE- ERO- RBC=2 OST=0 Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=0, DMOST=0, DMCRS=0, RSCEM-00: 00 10 30 00 17 00 30 02 07 00 00 01 10 88 80 00 10: 01 34 00 00 04 00 03 f1 00 00 00 00 04 00 02 f1 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 10 00 10 30: 00 00 00 00 50 00 00 00 00 00 00 00 05 02 11 12 0e:03.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet (rev 01) Subsystem: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- [disabled] [size=64K] Capabilities: [40] PCI-X non-bridge device. Command: DPERE- ERO- RBC=0 OST=0 Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=0, DMOST=0, DMCRS=0, RSCEM- Capabi lities: [48] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable+ DSel=0 DScale=1 PME- Capabilities: [50] Vital Product Data Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable- Address: 5403540058601a54 Data: 0800 00: e4 14 48 16 06 00 b0 02 01 00 00 02 10 40 80 00 10: 04 00 07 f1 00 00 00 00 04 00 06 f1 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 e4 14 48 16 30: 00 00 00 00 40 00 00 00 00 00 00 00 0b 02 40 00 Arthur Perry Lead Linux Developer / Linux Systems Architect Validation, CSU Celestica Sair/Linux Gnu Certified Professional Providing professional Linux solutions for 7+ years On Thu, 27 May 2004, Andi Kleen wrote: > Arthur Perry writes: > > > Here is a posting that I dropped off in RedHat's amd64-list. > > It is a kernel related issue, so if anybody has any insight or opinion of > > proper implementation here, please jump in! > > Machine Check Exceptions are in front of all hardware issues, not kernel > issues. It is your CPU trying to tell you that something is wrong in the > hardware. > > The 2.4 MCE code tends to label unrelated MCEs as "GART error" because > of bugs in the MCE decoding functions. There is a full fix for that > in the works. > > In some early 2.4 kernels it also managed to trigger a CPU bug > by writing directly nb registers. This should be fixed in later > 2.4 kernels and also in SuSE SLES8-SP3. > > Best alternative is to use 2.6 which has much improved MCE handling. > > -Andi > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo at vger.kernel.org > 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 majordomo at vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ From kernel at linuxfarms.com Thu May 27 17:03:24 2004 From: kernel at linuxfarms.com (Arthur Perry) Date: Thu, 27 May 2004 13:03:24 -0400 (EDT) Subject: GART error 11 In-Reply-To: <20040527150623.GP22630@redhat.com> References: <20040527150623.GP22630@redhat.com> Message-ID: Hi Dave, I have verified that booting the system with iommu=off (with vanilla kernel) does seem to make the problem go away. I apologize for not being fully up to speed with knowing what relationship the iommu has with the gart, but I will find out. I just wanted to post my findings. Thanks again! Best Regards, Arthur Perry Lead Linux Developer / Linux Systems Architect Validation, CSU Celestica Sair/Linux Gnu Certified Professional Providing professional Linux solutions for 7+ years On Thu, 27 May 2004, Dave Jones wrote: > On Thu, May 27, 2004 at 11:02:10AM -0400, Arthur Perry wrote: > > > The question really comes down to: > > Is this problem an oversight of the distributors (silly! the agp driver should not be built into the kernel for server use!) > > or > > Kernel code implementation? (well, if no agp bus is present, then let's not go and set up the GART, right?) > > If you don't have an AGP graphics card, there'll be nothing really > set up, unless you are using the IOMMU feature of the x86-64 kernel. > Setting up of GART tables etc only happens when the graphics > drivers (DRI) asks it to. > > Does booting with iommu=off fix this for you? > It may be that some driver is doing something that it > shouldn't. If it does make the problem go away, what > devices do you have in the system (lspci output please) > > Dave > From dsievers at ucla.edu Thu May 27 17:36:18 2004 From: dsievers at ucla.edu (Douglas Sievers) Date: Thu, 27 May 2004 10:36:18 -0700 Subject: FC2 x86_64 : Greeter program crashing when changing terminals Message-ID: <40B62712.7070002@ucla.edu> Hi all, I just put FC2 on my new Athlon64 computer. I am having a problem that when I go to switch terminals (alt + ctrl + F1, etc.), the screen flickers a bit and then brings up another graphical login screen, with the Fedora logo etc. So, it is not going to a TTY text terminal, which is what I want. When I tried to switch back to my current graphical session by pressing (alt + ctrl + F7), there is a bit more flickering then I receive the message, "The greeter program appears to be crashing. I will attempt to use a different one." Indeed it does, and I get a graphical boot screen, but it is just a gray login window with the following menu options "Session, Language, Actions, Themes". Here is my platform info Linux 2.6.5-1.358 #1 Sat May 8 09:01:26 EDT 2004 x86_64 x86_64 x86_64 GNU/Linux Hardware Asus K8V SE Deluxe mobo Athlon64 3400+ Processor eVGA GeFORCE FX 5700LE video card w/256MB I should point out that though this is an nVidia video card, I haven't got around to trying the official nVidia drivers, which last I heard don't work great. Here are some pertinent sections from my xorg.conf file Section "Module" Load "dbe" Load "extmod" Load "fbdevhw" Load "glx" Load "record" Load "freetype" Load "type1" Load "dri" EndSection Section "Device" Identifier "Videocard0" Driver "vesa" VendorName "Videocard vendor" BoardName "VESA driver (generic)" EndSection Section "DRI" Group 0 Mode 0666 EndSection Is anyone else having this problem? Should I report this as a bug? If so, how do I do that? (I've never reported a bug before). Thanks everyone! Doug Sievers From beaver at jbsys.com Thu May 27 18:56:47 2004 From: beaver at jbsys.com (Beaver) Date: Thu, 27 May 2004 11:56:47 -0700 Subject: ASUS FastTrack 378 controller Message-ID: <000901c4441c$5cf68790$0a01a8c0@jbsys.com> I have an ASUS K8V SE deluxe mother board that has a Promise FastTrack 378 disk controller. It can be set as a RAID controller or as a third IDE controller. I have two 160GB IDE disks attached to it but it seems FC2 will not recognize the controller or the drives no matter what the mode is set to. Is this device supported? How can I get the devices assigned so I can put some data on the disks? From beaver at jbsys.com Thu May 27 20:51:16 2004 From: beaver at jbsys.com (Jim B) Date: Thu, 27 May 2004 13:51:16 -0700 Subject: ASUS FastTrack 378 controller References: <000901c4441c$5cf68790$0a01a8c0@jbsys.com> <20040527194320.GD1105@leitl.org> Message-ID: <000a01c4442c$5b09df80$0a01a8c0@jbsys.com> >----- Original Message ----- >From: "Eugen Leitl" >To: "Beaver" >Sent: Thursday, May 27, 2004 12:43 PM >Subject: Re: ASUS FastTrack 378 controller. >On Thu, May 27, 2004 at 11:56:47AM -0700, Beaver wrote: >> I have an ASUS K8V SE deluxe mother board that has a Promise FastTrack 378 disk >> controller. It can be set as a RAID controller or as a third IDE controller. I >> have two 160GB IDE disks attached to it but it seems FC2 will not recognize the >> controller or the drives no matter what the mode is set to. Is this device >What have you set up in the BIOS? >Does dmesg show something like >Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 >ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx >VIA8237SATA: IDE controller at PCI slot 0000:00:0f.0 >VIA8237SATA: chipset revision 128 >VIA8237SATA: 100% native mode on irq 10 > ide2: BM-DMA at 0xd400-0xd407, BIOS settings: hde:pio, hdf:pio > ide3: BM-DMA at 0xd408-0xd40f, BIOS settings: hdg:pio, hdh:pio >hde: WDC WD360GD-00FNA0, ATA DISK drive >Using cfq io scheduler >ide2 at 0xe800-0xe807,0xe402 on irq 10 >VP_IDE: IDE controller at PCI slot 0000:00:0f.1 >VP_IDE: chipset revision 6 >VP_IDE: not 100% native mode: will probe irqs later >VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on pci0000:00:0f.1 > ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:pio, hdb:DMA > ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:DMA, hdd:pio >hdb: ATAPI DVD+RW 8X4X12, ATAPI CD/DVD-ROM drive >ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 >hdc: Maxtor 7Y250P0, ATA DISK drive >ide1 at 0x170-0x177,0x376 on irq 15 >hde: max request size: 1024KiB >hde: 72303840 sectors (37019 MB) w/8192KiB Cache, CHS=16383/255/63 > hde: hde1 hde2 hde3 >hdc: max request size: 1024KiB >hdc: 490234752 sectors (251000 MB) w/7936KiB Cache, CHS=30515/255/63, >UDMA(133) >hdc: hdc1 >hdb: ATAPI 40X DVD-ROM CD-R/RW drive, 8192kB Cache, UDMA(33) >> supported? How can I get the devices assigned so I can put some data on the >> disks? >> >> >> >> -- >> amd64-list mailing list >> amd64-list at redhat.com >> https://www.redhat.com/mailman/listinfo/amd64-list >-- >Eugen* Leitl leitl >______________________________________________________________ >ICBM: 48.07078, 11.61144 http://www.leitl.org >8B29F6BE: 099D 78BA 2FD3 B014 B08A 7779 75B0 2443 8B29 F6BE >http://moleculardevices.org http://nanomachines.net The BIOS has a setting for 'Onboard Promise Controller" that can be set to 'RAID' or 'Onboard IDE Operate Mode'. The first setting allows RAID for IDE drives. The second effectively allows a third IDE controller. With either setting, FC2 does not see any additional disks. Here is my dmesg (just the disk part) and lspci for my system. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VIA8237SATA: IDE controller at PCI slot 0000:00:0f.0 VIA8237SATA: chipset revision 128 VIA8237SATA: 100% native mode on irq 20 ide2: BM-DMA at 0xd400-0xd407, BIOS settings: hde:pio, hdf:pio ide3: BM-DMA at 0xd408-0xd40f, BIOS settings: hdg:pio, hdh:pio VP_IDE: IDE controller at PCI slot 0000:00:0f.1 VP_IDE: chipset revision 6 VP_IDE: not 100% native mode: will probe irqs later VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on pci0000:00:0f.1 ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:DMA, hdd:DMA hda: Maxtor 6Y080P0, ATA DISK drive hdb: WDC WD300BB-32AUA1, ATA DISK drive Using cfq io scheduler ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hdc: JLMS XJ-HD166S, ATAPI CD/DVD-ROM drive hdd: _NEC DVD_RW ND-2500A, ATAPI CD/DVD-ROM drive ide1 at 0x170-0x177,0x376 on irq 15 hda: max request size: 128KiB hda: 160086528 sectors (81964 MB) w/7936KiB Cache, CHS=65535/16/63, UDMA(133) hda: hda1 hda2 hda3 hda4 < hda5 hda6 > hdb: max request size: 128KiB hdb: 58633344 sectors (30020 MB) w/2048KiB Cache, CHS=58168/16/63, UDMA(100) hdb: hdb1 hdb2 < hdb5 hdb6 hdb7 > hdc: ATAPI 48X DVD-ROM drive, 512kB Cache, UDMA(33) Uniform CD-ROM driver Revision: 3.20 hdd: ATAPI 40X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)