Zwane Mwaikambo írta:
> On Sat, 27 Nov 2004, Zoltan Boszormenyi wrote:
> 
> 
>>Sorry, this last statement is not true, just compare the two error
>>reports above. Both hda and hdc show this error.
> 
> 
> Please provide full dmesg, lspci and if possible state around which kernel 
> version the problems began occuring
> 
> Thanks,
> 	Zwane

They are attached. I am running the linuxconsole.sf.net multiconsole
extension, I patched the Fedora Core 3 original and the second errata
kernel with it and made a custom RPM.

$ rpm -q kernel
kernel-2.6.9-1.667
kernel-2.6.9-1.667ruby.root
kernel-2.6.9-1.681ruby_FC3.root
$ uname -a
Linux wl-193.226.227-37-szolnok.dunaweb.hu 2.6.9-1.681ruby_FC3.root #1 
Wed Nov 24 20:26:05 CET 2004 x86_64 x86_64 x86_64 GNU/Linux

I used my machine this way with my old FC1 installation,
I had linux-2.6.8.1 with the above mentioned patch before
I reinstalled my machine with FC3. It definitely didn't show
this error. It was a 32-bit system, now I have a 64-bit system
installed. I had VMWare installed then and also now. My Realtek 8169
ethernet's (soldered on the mainboard) driver also filled my log up
since it isn't connected to anywhere:

r8169: eth1: PHY reset until link up

But what I haven't seen in my logs at that time is this:

Losing some ticks... checking if CPU frequency changed.

and

warning: many lost ticks.
Your time source seems to be instable or some driver is hogging interupts
rip rtl8169_phy_timer+0x1b2/0x1ba [r8169]

Could it be the cause? I will test whether it helps if I disable
it at boot time.

The mainboard is an MSI K8T Neo FIS2R, all other peripherals you
can find in dmesg and lspci outputs.

Best regards,
Zoltán Böszörményi