Re: System clock loses time at approx 17 secs per two hours
Have you considered using NTP (Network Time Protocol)?
A.Sajjad Zaidi
Eric Gillespie wrote:
> First off, CC: back to me, as my machine can't handle an estimated 200
> messages a day for me to sign up to the list 8-( - Anyway..
>
> I updated my kernel to 2.4.3 when the patch was released. (Tarballs -
> wonderful things!)
>
> However, I noticed that the kernel timer loses seconds over time with both the
> 2.4.2 and 2.4.3 kernels (seems to be at a steady rate...), and the rate of
> loss is NOT related to the CMOS clock. I compared against a 2.2.18 kernel,
> which lost about 1 second in 14 hours - about what I'd expect with my
> machine).
>
> Now, has anybody else noticed their 2.4.x kernel losing time? If so, and
> anyone knows how I can fix it so it behaves like 2.2.18, I'd be grateful.
>
>
> Can't say I like the April Fools release on "behalf" of Linus.
>
>
> ===
> Some relevant data:
> Linux version 2.4.3 ([EMAIL PROTECTED])
> (gcc version 2.95.3 19991030 (prerelease)) #2 Sat Mar 31 09:52:39 NZST 2001
>
> Software present (among others)
> Gnu C 2.95.3 Gnu make 3.77
> binutils 2.9.5.0.31 Linux C Library2.2.2
> Dynamic linker (ldd) 2.2.2
>
> Processor information (from /proc/cpuinfo) for a Cyrix-M II-300:
> processor : 0
> vendor_id : CyrixInstead
> cpu family : 6
> model : 2
> model name : M II 3.5x Core/Bus Clock
> stepping: 8
> cpu MHz : 233.030
> fdiv_bug: no
> hlt_bug : no
> f00f_bug: no
> coma_bug: no
> fpu : yes
> fpu_exception : yes
> cpuid level : 1
> wp : yes
> flags : fpu de tsc msr cx8 pge cmov mmx cyrix_arr
> bogomips: 465.30
>
> Loaded driver and hardware information (/proc/ioports, /proc/iomem)
> ==Drivers==
> -001f : dma1
> 0020-003f : pic1
> 0040-005f : timer
> 0060-006f : keyboard
> 0080-008f : dma page reg
> 00a0-00bf : pic2
> 00c0-00df : dma2
> 00f0-00ff : fpu
> 0170-0177 : ide1
> 01f0-01f7 : ide0
> 0213-0213 : isapnp read
> 0220-022f : soundblaster
> 02f8-02ff : serial(auto)
> 0300-031f : eth0
> 0376-0376 : ide1
> 0388-038b : Yamaha OPL3
> 03c0-03df : vesafb
> 03f6-03f6 : ide0
> 0a79-0a79 : isapnp write
> 0cf8-0cff : PCI conf1
> 4000-400f : Silicon Integrated Systems [SiS] 5513 [IDE]
> 4000-4007 : ide0
> 4008-400f : ide1
> e000-e07f : Silicon Integrated Systems [SiS] 5597/5598 VGA
> ==memory info==
> -0009efff : System RAM
> 000a-000b : Video RAM area
> 000c-000c7fff : Video ROM
> 000f-000f : System ROM
> 0010-01cf : System RAM
> 0010-001e9c4f : Kernel code
> 001e9c50-002445d7 : Kernel data
> 0800-082f : vesafb
> e100-e13f : Silicon Integrated Systems [SiS] 5597/5598 VGA
> e140-e140 : Silicon Integrated Systems [SiS] 5597/5598 VGA
> e141-e141 : Rockwell International HCF 56k V90 FaxModem
> [7.5.] PCI information ('lspci -vvv' as root)
> ==PCI Information==
>
> 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 5597 [SiS5582] (rev 10)
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
>Stepping- SERR- FastB2B-
> Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Latency: 64 set
>
> 00:01.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513 (rev 01)
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
>Stepping- SERR- FastB2B-
> Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Latency: 0 set
>
> 00:01.1 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0) (prog-if
>8a [Master SecP PriP])
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
>Stepping- SERR- FastB2B-
> Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Latency: 64 set
> Interrupt: pin A routed to IRQ 14
> Region 0: I/O ports at
> Region 1: I/O ports at
> Region 2: I/O ports at
> Region 3: I/O ports at
> Region 4: I/O ports at 4000 [size=16]
>
> 00:0b.0 Serial controller: Rockwell International HCF 56k V90 FaxModem (rev 01)
>(prog-if 00 [8250])
> Subsystem: Aztech System Ltd MDP3858SP-A SVD Modem
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
>Stepping- SERR- FastB2B-
> Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Latency: 64 set
> Interrupt: pin A routed to IRQ 11
>
Promise, DMA and RAID5 problems running 2.4.1
I just built a system that uses a K7V motherboard with the KT133
chipset. It has an onboard Promise PDC20265 ATA-100 controller. Im
running RH6.2.
I built a 2.4.1 kernel with support for the controller and it booted up
fine with the "ide=reverse" parameter. It was when I tried adding new
drives (all IBM-DTLA307045 s) that I realised that the cylinder/head
translation is different and I cant use the whole drive unless its
partitioned while attached to the other IDE ports.
The only option was to attach it to the normal ports and move the drive
back after partitioning. I dont see any jumpers or BIOS options to
change this so it must be a kernel setting, but I dont see anythere
there.
Second, I set up raid mirroring for 4 drives(2 raid, 2spare). Since one
drive isnt available yet, one of the 2 raid partitions are set as
'failed-disk'. All drives are connected to the ATA-100 controller. This
worked fine and I could even boot off of /dev/md0 until I setup raid5.
The main problem started after I setup raid5 on the remaining space
(3raid, 1spare), total space of about 82GB. One of the 3 raid disks were
set to failed, so it included the spare in the array and continued
reconstruction.
After doing hdparm -tT /dev/md4 a couple of times or transfering data to
it, I get the following message:
hda: dma_intr: bad DMA status
hda: dma_intr: status=0x50 { DriveReady SeekComplete }
hda: dma_intr: bad DMA status
hda: dma_intr: status=0x50 { DriveReady SeekComplete }
hda: dma_intr: bad DMA status
hda: dma_intr: status=0x50 { DriveReady SeekComplete }
hda: dma_intr: bad DMA status
hda: dma_intr: status=0x50 { DriveReady SeekComplete }
hda: DMA disabled
hdb: DMA disabled
and the system freezes completely. I have no option, but to do a cold
reboot.
Without DMA support, everything is fine, but hdparm gives me a mere 8.xx
MB/s transfer rate.
Anyone else have very similar problems?
A.Sajjad Zaidi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: Promise, DMA and RAID5 problems running 2.4.1
Mark Hahn wrote: > > drives (all IBM-DTLA307045 s) that I realised that the cylinder/head > > translation is different and I cant use the whole drive unless its > > partitioned while attached to the other IDE ports. > > no, it's just that the bios doesn't perform the LBA geometry lie > outside the hd[abcd]. Hmm, thats weird, because hd[abcd] were the ones without the LBA geometry. Maybe it was because ide was reversed (ide=reverse lilo parameter). > boot with hde=",255,63" (or whatever). Thanks, I was searching for something like that. > > Second, I set up raid mirroring for 4 drives(2 raid, 2spare). Since one > > drive isnt available yet, one of the 2 raid partitions are set as > > 'failed-disk'. All drives are connected to the ATA-100 controller. This > > do you understand that you can't really have raid on ide involving > two drives on the same channel? Is that just because of performance or are there other problems? Its working fine as it is, but Im considering setting up all drives as masters (2x ATA-100, 2x ATA-66). - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Promise, DMA and RAID5 problems running 2.4.1
Petr Vandrovec wrote: > It is known bug which I reported to Andre already. Open > drivers/ide/ide.c in favorite text editor, and replace strange > body of ide_delay_50ms() with simple mdelay(50). Promise driver > invokes ide_delay_50ms with interrupts disabled, so it freezes > here forever. If you have NMI watchdog, you'll get nice oopses. > > As for DMA failure itself, I have no idea what is wrong in your > case, but I found that mine Promise works with Linux only iff there > is master on each channel, slave alone does not work. And I did not > tried master+slave together. > Petr Vandrovec > [EMAIL PROTECTED] Ok, I changed ide.c and stopped getting the freeze, but bad DMA status errors were still showing up. Then I connected all the drives as masters (2x ATA-100, 2x ATA-66) and havent gotten anything yet. Buffered disk reads are still about 36.50 MB/sec on the raid5 device, so its fast enough for what I need. Next step is to see how well Reiserfs works here. Thank you everyone who has helped. A.Sajjad Zaidi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
