Thanks for the info, however in this case it is a known VIA issue with this chipset. However, VIAs patch is against a different redhat kernel... I tried applying it to the newer redhat kernel but some of it failed and I'm not going to even try to go through and patch it by hand. The thing that is confusing me though is that I disabled DMA and I'm still having some problems on the server.
Barclay Hambrook ApecTec ([EMAIL PROTECTED]) wrote*: > > >Trevor: I passed on your message to a partner. Not sure, but maybe this >will help you. > >Quote: > >All of our systems run Samba. > >The author is not talking about the processor. He is talking about the >North and South bridge. Not all chipsets support DMA. The chipset we use >doesn't. Therefore, if you try to use DMA, you will have problems. This is >not a problem with VIA, it is what functionality you are willing to pay for. >We don't have problems because we don't enable DMA. > >At 05:19 PM 08/10/02 +0000, you wrote: >>First off, I would like to apologize for missing the last meeting and >>ignoring the >>list for this past week and a bit. Our second child, a little girl was >>stillborn >>on October 1st and I have been busy planning the funeral, and spending >>time with my >>wife. I only started work up yesterday, I've been off since the 1st. >> >>Anyways, I've been having an issue with one of the servers I admin. Samba >>needs to >>be restarted once in a while or it won't allow anyone to log into the domain, >>however people already logged in work just fine. I think this problem has >>to do >>with the motherboard chipset (It's VIA, yes I know VIA is crap but this is the >>hardware I was given to work with :( The server was throwing DMA errors >>which I >>couldn't fix without disabling DMA on the harddrives. I had a feeling >>that DMA was >>causing file system corruption so I disabled DMA and reinstalled Samba. The >>problem seemed to have gone away for a bit but it's happening again. Besides >>having to restart samba to allow people to log in, Samba also shares out / as >>whatever user is set as the guest account in samba. So anyone can go >>to //servername/nobody and browse the root of the server. This for lack of a >>better word is annoying. I've already tried all the obvious things to fix >>it and >>probably most of the not so obvious things. I have about 25 linux servers out >>there, about half of them running Samba with the exact same basic config >>and I've >>never had this problem. I was just wondering if anyone else has seen this >>type of >>issue before? It's an AMD processor with a VIA chipset, I think it's the VIA >>chipset that is the problem here because I can use the exact same config >>files for >>samba on a Intel processor using a SiS or Intel chipset and it works just >>fine. >>Any ideas? >> >>Thanks, >> >>Trevor > >ApecTec Inc. >www.apectec.com >email: [EMAIL PROTECTED] >Phone: (403) 685 1888 >Fax: (403) 685 1880 > >
