Re: XFS or Kernel Problem / Bug

[Stefan Priebe - FH <studium@profihost.com>]

Hi!

Any News?

Stefan

Stefan Priebe - FH schrieb:
> Hi!
> 
> OK - i rechecked everything. We've 22 Servers with the DFI PM-12 
> Mainboard with VIA Chipset.
> 
> But only the 5 oldest of them (before 2004 / 01 / 20) (we've buyed all 
> in a range of 10 month) have this problem.
> 
> So i think it is a mixture of software and hardware problem. Perhaps DFI 
> changed something on the mainboard (e.g. new revision) or there was a 
> new BIOS Version on it.
> 
> But there must also changed something in the kernel.
> 
>  > OK, can you post configs for one that works and one that doesn't?
> You mean Kernel .configs?
> 
>  > And which C compiler(s) do you use? The same for all, I hope...
> On all 32bit Machines:
> 
> gcc -v
> Reading specs from /usr/lib/gcc-lib/i486-linux/3.3.5/specs
> Configured with: ../src/configure -v 
> --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr 
> --mandir=/usr/share/man --infodir=/usr/share/info 
> --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared 
> --enable-__cxa_atexit --with-system-zlib --enable-nls 
> --without-included-gettext --enable-clocale=gnu --enable-debug 
> --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc i486-linux
> Thread model: posix
> gcc version 3.3.5 (Debian 1:3.3.5-13)
> 
> Stefan
> 
> 
> Chuck Ebbert schrieb:
>> Stefan Priebe - FH wrote:
>>
>>>> What is different about these servers?
>>>
>>> All 300 machines are mostly different. We have Dual Opteron, single P4
>>> with HT, single P4 without HT, Dual Xeon, Athlon 64 X2, and many
>>> more... different mainboards etc.
>>>
>>> The only thing i found out is, that all these servers (where the
>>> problem exist) are using a DFI PM-12 Mainboard with a VIA Chipset.
>>
>> Any others with VIA chipsets?
>>
>>>> Are you building different kernels for them, or is it just different
>>>> drivers loaded?
>>>
>>> No every machine builds it's own kernel.
>>>
>>
>> OK, can you post configs for one that works and one that doesn't?
>>
>> And which C compiler(s) do you use? The same for all, I hope...
>>
> 
>