* [BUG?] SIS IDE DMA errors
@ 2003-09-26 12:30 Måns Rullgård
2003-09-26 14:08 ` Michael Frank
2003-10-03 8:38 ` [BUG?] lost interrupt (was: SIS IDE DMA errors) David Caldwell
0 siblings, 2 replies; 26+ messages in thread
From: Måns Rullgård @ 2003-09-26 12:30 UTC (permalink / raw)
To: linux-kernel
I reported this a long time ago, but nobody seemed to care, so here it
is again.
With all 2.6.0 versions so far, I get these errors when writing lots
of data to the disk:
hda: dma_timer_expiry: dma status == 0x21
hda: DMA timeout error
hda: dma timeout error: status=0xd0 { Busy }
hda: DMA disabled
ide0: reset: success
hda: dma_timer_expiry: dma status == 0x21
hda: DMA timeout error
hda: dma timeout error: status=0xd0 { Busy }
hda: DMA disabled
ide0: reset: success
Losing too many ticks!
TSC cannot be used as a timesource. (Are you running with SpeedStep?)
Falling back to a sane timesource.
hda: set_drive_speed_status: status=0x58 { DriveReady SeekComplete DataRequest }
hda: lost interrupt
hda: lost interrupt
hda: lost interrupt
hda: lost interrupt
hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hda: drive not ready for command
It only happens when I write more than about 100 MB at more than 5
MB/s or so, never when writing smaller amounts of data.
System details follow.
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 650 Host (rev 01)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SiS 530 Virtual PCI-to-PCI bridge (AGP)
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513 (rev 10)
00:02.1 SMBus: Silicon Integrated Systems [SiS]: Unknown device 0016
00:02.2 USB Controller: Silicon Integrated Systems [SiS] SiS7001 USB Controller (rev 07)
00:02.3 USB Controller: Silicon Integrated Systems [SiS] SiS7001 USB Controller (rev 07)
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0)
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] SiS7012 PCI Audio Accelerator (rev a0)
00:03.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 10/100 Ethernet (rev 90)
00:0a.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev a8)
00:0a.1 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev a8)
00:0a.2 FireWire (IEEE 1394): Ricoh Co Ltd R5C552 IEEE 1394 Controller
00:0c.0 Communication controller: Conexant HSF 56k HSFi Modem (rev 01)
01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] SiS650/651/M650/740 PCI/AGP VGA Display Adapter
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0) (prog-if 80 [Master])
Subsystem: Asustek Computer, Inc.: Unknown device 1688
Flags: bus master, fast devsel, latency 128
I/O ports at b800 [size=16]
Linux version 2.6.0-test5-nick15 (mru@ford) (gcc version 3.3.1) #14 Fri Sep 19 11:26:47 CEST 2003
Video mode to be used for restore is ffff
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000000dffa000 (usable)
BIOS-e820: 000000000dffa000 - 000000000dfff000 (ACPI data)
BIOS-e820: 000000000dfff000 - 000000000e000000 (ACPI NVS)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
223MB LOWMEM available.
On node 0 totalpages: 57338
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 53242 pages, LIFO batch:12
HighMem zone: 0 pages, LIFO batch:1
DMI 2.3 present.
ACPI: RSDP (v000 ASUS ) @ 0x000f6460
ACPI: RSDT (v001 ASUS M2000E 0x42302e31 MSFT 0x31313031) @ 0x0dffa000
ACPI: FADT (v001 ASUS M2000E 0x42302e31 MSFT 0x31313031) @ 0x0dffa080
ACPI: BOOT (v001 ASUS M2000E 0x42302e31 MSFT 0x31313031) @ 0x0dffa040
ACPI: DSDT (v001 ASUS M2000E 0x00001000 MSFT 0x0100000e) @ 0x00000000
ACPI: MADT not present
Building zonelist for node : 0
Kernel command line: root=/dev/hda1 init=/sbin/lvm2/lvmroot video=sisfb:mode:1024x768x8
sisfb: Options mode:1024x768x8
No local APIC present or hardware disabled
Initializing CPU#0
PID hash table entries: 1024 (order 10: 8192 bytes)
Detected 2070.560 MHz processor.
Console: colour VGA+ 80x25
Memory: 223688k/229352k available (1655k kernel code, 4972k reserved, 744k data, 136k init, 0k highmem)
Calibrating delay loop... 4087.80 BogoMIPS
Security Scaffold v1.0.0 initialized
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
-> /dev
-> /dev/console
-> /root
CPU: After generic identify, caps: bfebf9ff 00000000 00000000 00000000
CPU: After vendor identify, caps: bfebf9ff 00000000 00000000 00000000
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: After all inits, caps: bfebf9ff 00000000 00000000 00000080
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU#0: Intel P4/Xeon Extended MCE MSRs (12) available
CPU#0: Thermal monitoring enabled
CPU: Intel Mobile Intel(R) Pentium(R) 4 - M CPU 1.80GHz stepping 07
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xf17c0, last bus=1
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20030813
tbxface-0117 [03] acpi_load_tables : ACPI Tables successfully acquired
Parsing all Control Methods:........................................................................................................................................................................................................
Table [DSDT](id F004) - 585 Objects with 52 Devices 200 Methods 21 Regions
ACPI Namespace successfully loaded at root c038b39c
evxfevnt-0093 [04] acpi_enable : Transition to ACPI mode successful
evgpeblk-0748 [06] ev_create_gpe_block : GPE 00 to 15 [_GPE] 2 regs at 000000000000E420 on int 9
evgpeblk-0748 [06] ev_create_gpe_block : GPE 16 to 31 [_GPE] 2 regs at 000000000000E430 on int 9
Completing Region/Field/Buffer/Package initialization:.............................................. psargs-0352: *** Error: Looking up [\_PR_.CPU0] in namespace, AE_NOT_FOUND
search_node cdf6f8a8 start_node cdf6f8a8 return_node 00000000
psparse-1121: *** Error: , AE_NOT_FOUND
nsinit-0293 [06] ns_init_one_object : Could not execute arguments for [_PSL] (Package), AE_NOT_FOUND
....................
Initialized 21/21 Regions 5/5 Fields 19/19 Buffers 21/21 Packages (593 nodes)
Executing all Device _STA and_INI methods:.....................................................
53 Devices found containing: 53 _STA, 2 _INI methods
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 9 10 *11 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 9 10 *11 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 9 10 *11 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 9 10 *11 15)
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
Enabling SiS 96x SMBus.
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
ACPI: Power Resource [FN0] (on)
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 9
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
PCI: Using ACPI for IRQ routing
PCI: if you experience problems, try using option 'pci=noacpi' or even 'acpi=off'
sisfb: Video ROM found and mapped to c00c0000
sisfb: Framebuffer at 0xf0000000, mapped to 0xce80f000, size 32768k
sisfb: MMIO at 0xe7800000, mapped to 0xd0810000, size 128k
sisfb: Memory heap starting at 12288K
sisfb: Using MMIO queue mode
sisfb: LVDS transmitter detected
sisfb: Default mode is 1024x768x8 (60Hz)
sisfb: Added MTRRs
sisfb: Installed SISFB_GET_INFO ioctl (80046ef8)
sisfb: 2D acceleration is enabled, scrolling mode ypan
fb0: SIS 650/M650/651/740 VGA frame buffer device, Version 1.6.01
sisfb: Change mode to 1024x768x8-60Hz
Console: switching to colour frame buffer device 128x48
pty: 256 Unix98 ptys configured
SBF: Simple Boot Flag extension found and enabled.
SBF: Setting boot flags 0x1
Machine check exception polling timer started.
cpufreq: P4/Xeon(TM) CPU On-Demand Clock Modulation available
Total HugeTLB memory allocated, 0
devfs: v1.22 (20021013) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
ACPI: AC Adapter [AC] (on-line)
ACPI: Battery Slot [BAT0] (battery present)
ACPI: Power Button (FF) [PWRF]
ACPI: Lid Switch [LID]
ACPI: Sleep Button (CM) [SLPB]
ACPI: Fan [FAN0] (on)
ACPI: Processor [CPU] (supports C1 C2, 4 throttling states)
ACPI: Thermal Zone [THRM] (45 C)
Asus Laptop ACPI Extras version 0.24a
M2E model detected, supported
Notify Handler installed successfully
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
SIS5513: IDE controller at PCI slot 0000:00:02.5
SIS5513: chipset revision 208
SIS5513: not 100% native mode: will probe irqs later
SIS5513: SiS 961 MuTIOL IDE UDMA100 controller
ide0: BM-DMA at 0xb800-0xb807, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xb808-0xb80f, BIOS settings: hdc:DMA, hdd:pio
hda: IC25N040ATMR04-0, ATA DISK drive
Using anticipatory scheduling io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: ASUS SCB-2408, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 1024KiB
hda: 78140160 sectors (40007 MB) w/1740KiB Cache, CHS=16383/255/63, UDMA(100)
/dev/ide/host0/bus0/target0/lun0: p1 p2 p3
Console: switching to colour frame buffer device 128x48
mice: PS/2 mouse device common for all mice
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
Synaptics Touchpad, model: 1
Firware: 4.6
180 degree mounted touchpad
Sensor: 18
new absolute packet format
Touchpad has extended capability bits
-> four buttons
-> multifinger detection
-> palm detection
input: Synaptics Synaptics TouchPad on isa0060/serio4
serio: i8042 AUX3 port at 0x60,0x64 irq 12
input: AT Set 2 keyboard on isa0060/serio0
serio: i8042 KBD port at 0x60,0x64 irq 1
device-mapper: 4.0.0-ioctl (2003-06-04) initialised: dm@uk.sistina.com
NET: Registered protocol family 2
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 32768)
NET: Registered protocol family 1
NET: Registered protocol family 17
ACPI: (supports S0 S1 S3 S4 S5)
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 136k freed
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on hda1, internal journal
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Adding 522104k swap on /dev/hda3. Priority:-1 extents:1
EXT3 FS on dm-3, internal journal
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-0, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-4, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-5, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-8, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-9, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Real Time Clock Driver v1.12
Linux Kernel Card Services 3.1.22
options: [pci] [cardbus] [pm]
Yenta: CardBus bridge found at 0000:00:0a.0 [1043:1687]
Yenta: ISA IRQ list 0098, PCI irq10
Socket status: 30000006
Yenta: CardBus bridge found at 0000:00:0a.1 [1043:1687]
Yenta: ISA IRQ list 0098, PCI irq10
Socket status: 30000006
sis900.c: v1.08.06 9/24/2002
eth0: ICS LAN PHY transceiver found at address 1.
eth0: Using transceiver found at address 1 as default
eth0: SiS 900 PCI Fast Ethernet at 0xa000, IRQ 5, 00:0c:6e:40:b0:22.
eth0: Media Link On 100mbps full-duplex
intel8x0: clocking to 48000
drivers/usb/core/usb.c: registered new driver usbfs
drivers/usb/core/usb.c: registered new driver hub
ohci-hcd: 2003 Feb 24 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ohci-hcd: block sizes: ed 64 td 64
ohci-hcd 0000:00:02.2: OHCI Host Controller
ohci-hcd 0000:00:02.2: irq 9, pci mem d08b6000
ohci-hcd 0000:00:02.2: new USB bus registered, assigned bus number 1
hub 1-0:0: USB hub found
hub 1-0:0: 3 ports detected
ohci-hcd 0000:00:02.3: OHCI Host Controller
ohci-hcd 0000:00:02.3: irq 9, pci mem d091e000
ohci-hcd 0000:00:02.3: new USB bus registered, assigned bus number 2
hub 2-0:0: USB hub found
hub 2-0:0: 3 ports detected
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected SiS 650 chipset
agpgart: Maximum main memory to use for agp memory: 176M
agpgart: AGP aperture is 64M @ 0xe8000000
hub 1-0:0: debounce: port 1: delay 100ms stable 4 status 0x301
hub 1-0:0: new USB device on port 1, assigned address 2
input: USB HID v1.10 Mouse [Logitech Optical USB Mouse] on usb-0000:00:02.2-1
drivers/usb/core/usb.c: registered new driver hid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
SCSI subsystem initialized
end_request: I/O error, dev hdc, sector 0
hdc: ATAPI 24X DVD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
EXT3 FS on dm-1, internal journal
vmmon: no version magic, tainting kernel.
vmmon: module license 'unspecified' taints kernel.
/dev/vmmon: Module vmmon: registered with major=10 minor=165
/dev/vmmon: Module vmmon: initialized
/dev/vmmon: Module vmmon: unloaded
vmnet: no version magic, tainting kernel.
vmnet: module license 'unspecified' taints kernel.
vmmon: no version magic, tainting kernel.
vmmon: module license 'unspecified' taints kernel.
/dev/vmmon: Module vmmon: registered with major=10 minor=165
/dev/vmmon: Module vmmon: initialized
vmnet: no version magic, tainting kernel.
vmnet: module license 'unspecified' taints kernel.
/dev/vmnet: open called by PID 1997 (vmnet-bridge)
/dev/vmnet: hub 0 does not exist, allocating memory.
/dev/vmnet: port on hub 0 successfully opened
bridge-eth0: up
bridge-eth0: attached
/dev/vmnet: open called by PID 2015 (vmnet-natd)
/dev/vmnet: hub 8 does not exist, allocating memory.
/dev/vmnet: port on hub 8 successfully opened
/dev/vmnet: open called by PID 2270 (vmnet-netifup)
/dev/vmnet: port on hub 8 successfully opened
/dev/vmnet: open called by PID 2288 (vmnet-dhcpd)
/dev/vmnet: port on hub 8 successfully opened
/dev/vmnet: open called by PID 2342 (vmware-vmx)
/dev/vmnet: port on hub 8 successfully opened
spurious 8259A interrupt: IRQ7.
/dev/vmnet: open called by PID 2407 (vmware-vmx)
/dev/vmnet: port on hub 8 successfully opened
/dev/vmnet: open called by PID 2414 (vmware-vmx)
/dev/vmnet: port on hub 8 successfully opened
/dev/vmnet: open called by PID 2471 (vmware-vmx)
/dev/vmnet: port on hub 8 successfully opened
hda: dma_timer_expiry: dma status == 0x21
hda: DMA timeout error
hda: dma timeout error: status=0xd0 { Busy }
hda: DMA disabled
ide0: reset: success
hda: dma_timer_expiry: dma status == 0x21
hda: DMA timeout error
hda: dma timeout error: status=0xd0 { Busy }
hda: DMA disabled
ide0: reset: success
/dev/vmnet: open called by PID 2509 (vmware-vmx)
/dev/vmnet: port on hub 8 successfully opened
/dev/vmnet: open called by PID 2516 (vmware-vmx)
/dev/vmnet: port on hub 8 successfully opened
/dev/vmnet: open called by PID 2523 (vmware-vmx)
/dev/vmnet: port on hub 8 successfully opened
acpi_bus-0199 [17] acpi_bus_set_power : Device is not power manageable
acpi_thermal-0611 [16] acpi_thermal_active : Unable to turn cooling device [cdf6fd28] 'on'
acpi_bus-0199 [17] acpi_bus_set_power : Device is not power manageable
acpi_thermal-0611 [16] acpi_thermal_active : Unable to turn cooling device [cdf6fd28] 'on'
hda: dma_timer_expiry: dma status == 0x21
hda: DMA timeout error
hda: dma timeout error: status=0xd0 { Busy }
hda: DMA disabled
ide0: reset: success
hda: dma_timer_expiry: dma status == 0x21
hda: DMA timeout error
hda: dma timeout error: status=0xd0 { Busy }
hda: DMA disabled
ide0: reset: success
Losing too many ticks!
TSC cannot be used as a timesource. (Are you running with SpeedStep?)
Falling back to a sane timesource.
hda: set_drive_speed_status: status=0x58 { DriveReady SeekComplete DataRequest }
hda: lost interrupt
hda: lost interrupt
hda: lost interrupt
hda: lost interrupt
hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hda: drive not ready for command
hda: dma_timer_expiry: dma status == 0x21
hda: DMA timeout error
hda: dma timeout error: status=0xd0 { Busy }
hda: DMA disabled
ide0: reset: success
--
Måns Rullgård
mru@users.sf.net
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [BUG?] SIS IDE DMA errors
2003-09-26 14:08 ` Michael Frank
@ 2003-09-26 14:07 ` Måns Rullgård
2003-09-26 15:32 ` Michael Frank
0 siblings, 1 reply; 26+ messages in thread
From: Måns Rullgård @ 2003-09-26 14:07 UTC (permalink / raw)
To: linux-kernel
Michael Frank <mhf@linuxmail.org> writes:
> Suspect chipset related issue which should be looked into.
That's what someone told me three months ago, too. Nothing happened,
though.
> You could try setting udma mode with hdparm -Xudma[12345] and see
> if it helps.
That's the first thing I try when things go wrong. It didn't help
this time.
> I use from a script on startup
>
> sync
> hdparm -S 255 -K1 -c3 -Xudma5 /dev/hda.
I already tried all most combinations. The only thing that helps is
-d0, if you can call that help.
> Note: IME, hdparm should not be used when there is substantial
> disk activity.
I've noticed. It usually causes the system too freeze for a minute or
so.
I'm a little frustrated at not being able copy large files without
considerable trouble.
--
Måns Rullgård
mru@users.sf.net
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [BUG?] SIS IDE DMA errors
2003-09-26 12:30 [BUG?] SIS IDE DMA errors Måns Rullgård
@ 2003-09-26 14:08 ` Michael Frank
2003-09-26 14:07 ` Måns Rullgård
2003-10-03 8:38 ` [BUG?] lost interrupt (was: SIS IDE DMA errors) David Caldwell
1 sibling, 1 reply; 26+ messages in thread
From: Michael Frank @ 2003-09-26 14:08 UTC (permalink / raw)
To: Måns Rullgård, linux-kernel
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> SIS5513: IDE controller at PCI slot 0000:00:02.5
> SIS5513: chipset revision 208
> SIS5513: not 100% native mode: will probe irqs later
> SIS5513: SiS 961 MuTIOL IDE UDMA100 controller
> ide0: BM-DMA at 0xb800-0xb807, BIOS settings: hda:DMA, hdb:pio
> ide1: BM-DMA at 0xb808-0xb80f, BIOS settings: hdc:DMA, hdd:pio
> hda: IC25N040ATMR04-0, ATA DISK drive
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
SIS5513: IDE controller at PCI slot 00:02.5
PCI: Found IRQ 10 for device 00:02.5
SIS5513: chipset revision 0
SIS5513: not 100% native mode: will probe irqs later
SIS5513: SiS 962/963 MuTIOL IDE UDMA133 controller
ide0: BM-DMA at 0x4000-0x4007, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x4008-0x400f, BIOS settings: hdc:pio, hdd:pio
hda: IC35L090AVV207-0, ATA DISK drive
Jul 27 04:22:26 mhfl4 kernel: hda: lost interrupt
Jul 27 04:23:15 mhfl4 kernel: hda: dma_timer_expiry: dma status == 0x24
Jul 27 04:23:25 mhfl4 kernel: hda: DMA interrupt recovery
Running mostly 2.4 on this board, not using ACPI, Got similar problems
with 2.4 and when running occasionally 2.6, but not as bad except with
2.4.22-pre7.
Suspect chipset related issue which should be looked into.
You could try setting udma mode with hdparm -Xudma[12345] and see
if it helps.
I use from a script on startup
sync
hdparm -S 255 -K1 -c3 -Xudma5 /dev/hda.
Note: IME, hdparm should not be used when there is substantial
disk activity.
Regards
Michael
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [BUG?] SIS IDE DMA errors
2003-09-26 14:07 ` Måns Rullgård
@ 2003-09-26 15:32 ` Michael Frank
2003-09-26 15:38 ` Måns Rullgård
2003-09-26 16:59 ` Vojtech Pavlik
0 siblings, 2 replies; 26+ messages in thread
From: Michael Frank @ 2003-09-26 15:32 UTC (permalink / raw)
To: Måns Rullgård; +Cc: andre, linux-kernel
On Friday 26 September 2003 22:07, Måns Rullgård wrote:
> Michael Frank <mhf@linuxmail.org> writes:
>
> > Suspect chipset related issue which should be looked into.
>
> That's what someone told me three months ago, too. Nothing happened,
> though.
>
OK, now that we are two, we copy the IDE maintainer ;)
I guess it is fair to say that we are happy to test patches.
And here is my lspci -vv.
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (prog-if 80 [Master])
Subsystem: Micro-Star International Co., Ltd.: Unknown device 5332
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 128
Interrupt: pin ? routed to IRQ 10
Region 4: I/O ports at 4000 [size=16]
Capabilities: <available only to root>
Regards
Michael
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [BUG?] SIS IDE DMA errors
2003-09-26 15:32 ` Michael Frank
@ 2003-09-26 15:38 ` Måns Rullgård
2003-09-26 19:44 ` Michael Frank
2003-09-26 16:59 ` Vojtech Pavlik
1 sibling, 1 reply; 26+ messages in thread
From: Måns Rullgård @ 2003-09-26 15:38 UTC (permalink / raw)
To: Michael Frank; +Cc: andre, linux-kernel
Michael Frank <mhf@linuxmail.org> writes:
>> > Suspect chipset related issue which should be looked into.
>>
>> That's what someone told me three months ago, too. Nothing happened,
>> though.
>>
>
> OK, now that we are two, we copy the IDE maintainer ;)
>
> I guess it is fair to say that we are happy to test patches.
>
> And here is my lspci -vv.
>
> 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (prog-if 80 [Master])
> Subsystem: Micro-Star International Co., Ltd.: Unknown device 5332
> Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 128
> Interrupt: pin ? routed to IRQ 10
> Region 4: I/O ports at 4000 [size=16]
> Capabilities: <available only to root>
Mine looks rather similar, but there are a few differences. Mine has
Mem+ and DEVSEL=fast.
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0) (prog-if 80 [Master])
Subsystem: Asustek Computer, Inc.: Unknown device 1688
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 128
Region 4: I/O ports at b800 [size=16]
--
Måns Rullgård
mru@users.sf.net
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [BUG?] SIS IDE DMA errors
2003-09-26 15:32 ` Michael Frank
2003-09-26 15:38 ` Måns Rullgård
@ 2003-09-26 16:59 ` Vojtech Pavlik
2003-09-26 17:27 ` Måns Rullgård
2003-09-26 18:22 ` Michael Frank
1 sibling, 2 replies; 26+ messages in thread
From: Vojtech Pavlik @ 2003-09-26 16:59 UTC (permalink / raw)
To: Michael Frank; +Cc: M?ns Rullg?rd, andre, linux-kernel
On Fri, Sep 26, 2003 at 11:32:30PM +0800, Michael Frank wrote:
> On Friday 26 September 2003 22:07, M?ns Rullg?rd wrote:
> > Michael Frank <mhf@linuxmail.org> writes:
> >
> > > Suspect chipset related issue which should be looked into.
> >
> > That's what someone told me three months ago, too. Nothing happened,
> > though.
> >
>
> OK, now that we are two, we copy the IDE maintainer ;)
Actually, it's me who wrote the 961 and 963 support. It works fine for
most people. Did you check you cabling?
>
> I guess it is fair to say that we are happy to test patches.
>
> And here is my lspci -vv.
>
> 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (prog-if 80 [Master])
> Subsystem: Micro-Star International Co., Ltd.: Unknown device 5332
> Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 128
> Interrupt: pin ? routed to IRQ 10
> Region 4: I/O ports at 4000 [size=16]
> Capabilities: <available only to root>
>
>
> Regards
> Michael
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Vojtech Pavlik
SuSE Labs, SuSE CR
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [BUG?] SIS IDE DMA errors
2003-09-26 16:59 ` Vojtech Pavlik
@ 2003-09-26 17:27 ` Måns Rullgård
2003-09-26 17:53 ` Vojtech Pavlik
2003-09-26 18:15 ` Michael Frank
2003-09-26 18:22 ` Michael Frank
1 sibling, 2 replies; 26+ messages in thread
From: Måns Rullgård @ 2003-09-26 17:27 UTC (permalink / raw)
To: Vojtech Pavlik; +Cc: Michael Frank, andre, linux-kernel
Vojtech Pavlik <vojtech@suse.cz> writes:
> Actually, it's me who wrote the 961 and 963 support. It works fine for
> most people. Did you check you cabling?
I'm dealing with a laptop, but I suppose I could wiggle the cables a
bit. I still doubt it's a cable problem, since reading works
flawlessly.
It appears to me that during heavy IO load, some DMA interrupts get
lost, for some reason.
--
Måns Rullgård
mru@users.sf.net
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [BUG?] SIS IDE DMA errors
2003-09-26 17:53 ` Vojtech Pavlik
@ 2003-09-26 17:46 ` Måns Rullgård
2003-09-26 18:33 ` Vojtech Pavlik
2003-09-26 18:29 ` Michael Frank
2003-09-29 11:18 ` Lionel Bouton
2 siblings, 1 reply; 26+ messages in thread
From: Måns Rullgård @ 2003-09-26 17:46 UTC (permalink / raw)
To: Vojtech Pavlik; +Cc: Michael Frank, linux-kernel
Vojtech Pavlik <vojtech@suse.cz> writes:
>> > Actually, it's me who wrote the 961 and 963 support. It works fine for
>> > most people. Did you check you cabling?
>>
>> I'm dealing with a laptop, but I suppose I could wiggle the cables a
>> bit. I still doubt it's a cable problem, since reading works
>> flawlessly.
>
> Hmm, that's indeed interesting and it'd point to a driver problem -
See, I told you :)
> when reading, the drive is dictating the timing, but when writing, it's
> the controllers turn.
>
> So if the controller timing is not correctly programmed, reads function,
> but writes don't.
Furthermore, short writes work just fine. The errors usually start
happening after about 100 MB at full speed. When copying from NFS
over a 100 MB/s network it usually goes a little longer, sometimes
even up to 500 MB. All this could indicate that there is some error
in the timing, and that it takes some time for it build up enough to
trigger the bad things. Or am I wrong?
Why can't the drive give notice when it's ready to accept more data?
That would seem like the simple solution, instead of trying to
synchronize the timers.
> Can you send me the output of 'lspci -vvxxx' of the IDE device?
> I'll take a look to see if it looks correct.
Here you go:
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0) (prog-if 80 [Master])
Subsystem: Asustek Computer, Inc.: Unknown device 1688
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 128
Region 4: I/O ports at b800 [size=16]
00: 39 10 13 55 07 00 00 00 d0 80 01 01 00 80 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 b8 00 00 00 00 00 00 00 00 00 00 43 10 88 16
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 31 81 00 00 31 85 00 00 08 01 e6 51 00 02 00 02
50: 01 00 01 06 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> It appears to me that during heavy IO load, some DMA interrupts get
>> lost, for some reason.
>
> Well, I've got this feeling that not just IDE interrupts get lost under
> heavy IO load with recent kernels ...
Like mouse and keyboard...
--
Måns Rullgård
mru@users.sf.net
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [BUG?] SIS IDE DMA errors
2003-09-26 17:27 ` Måns Rullgård
@ 2003-09-26 17:53 ` Vojtech Pavlik
2003-09-26 17:46 ` Måns Rullgård
` (2 more replies)
2003-09-26 18:15 ` Michael Frank
1 sibling, 3 replies; 26+ messages in thread
From: Vojtech Pavlik @ 2003-09-26 17:53 UTC (permalink / raw)
To: M?ns Rullg?rd; +Cc: Vojtech Pavlik, Michael Frank, andre, linux-kernel
On Fri, Sep 26, 2003 at 07:27:35PM +0200, M?ns Rullg?rd wrote:
> Vojtech Pavlik <vojtech@suse.cz> writes:
>
> > Actually, it's me who wrote the 961 and 963 support. It works fine for
> > most people. Did you check you cabling?
>
> I'm dealing with a laptop, but I suppose I could wiggle the cables a
> bit. I still doubt it's a cable problem, since reading works
> flawlessly.
Hmm, that's indeed interesting and it'd point to a driver problem -
when reading, the drive is dictating the timing, but when writing, it's
the controllers turn.
So if the controller timing is not correctly programmed, reads function,
but writes don't.
Can you send me the output of 'lspci -vvxxx' of the IDE device?
I'll take a look to see if it looks correct.
> It appears to me that during heavy IO load, some DMA interrupts get
> lost, for some reason.
Well, I've got this feeling that not just IDE interrupts get lost under
heavy IO load with recent kernels ...
--
Vojtech Pavlik
SuSE Labs, SuSE CR
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [BUG?] SIS IDE DMA errors
2003-09-26 17:27 ` Måns Rullgård
2003-09-26 17:53 ` Vojtech Pavlik
@ 2003-09-26 18:15 ` Michael Frank
1 sibling, 0 replies; 26+ messages in thread
From: Michael Frank @ 2003-09-26 18:15 UTC (permalink / raw)
To: Måns Rullgård, Vojtech Pavlik; +Cc: andre, linux-kernel
On Saturday 27 September 2003 01:27, Måns Rullgård wrote:
> Vojtech Pavlik <vojtech@suse.cz> writes:
>
> > Actually, it's me who wrote the 961 and 963 support. It works fine for
> > most people. Did you check you cabling?
>
> I'm dealing with a laptop, but I suppose I could wiggle the cables a
> bit. I still doubt it's a cable problem, since reading works
> flawlessly.
And the cables are nicely short...
>
> It appears to me that during heavy IO load, some DMA interrupts get
> lost, for some reason.
Could you cat /proc/interrupts to see if the IDE interrupt is shared
by chance?
Regards
Michael
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [BUG?] SIS IDE DMA errors
2003-09-26 16:59 ` Vojtech Pavlik
2003-09-26 17:27 ` Måns Rullgård
@ 2003-09-26 18:22 ` Michael Frank
1 sibling, 0 replies; 26+ messages in thread
From: Michael Frank @ 2003-09-26 18:22 UTC (permalink / raw)
To: Vojtech Pavlik; +Cc: M?ns Rullg?rd, andre, linux-kernel
On Saturday 27 September 2003 00:59, Vojtech Pavlik wrote:
> On Fri, Sep 26, 2003 at 11:32:30PM +0800, Michael Frank wrote:
> > On Friday 26 September 2003 22:07, M?ns Rullg?rd wrote:
> > > Michael Frank <mhf@linuxmail.org> writes:
> > >
> > > > Suspect chipset related issue which should be looked into.
> > >
> > > That's what someone told me three months ago, too. Nothing happened,
> > > though.
> > >
> >
> > OK, now that we are two, we copy the IDE maintainer ;)
>
> Actually, it's me who wrote the 961 and 963 support. It works fine for
> most people. Did you check you cabling?
It is 80 conductor cable.
2.4.22-pre7 was terrible for me - since pre9 or so it has almost gone away,
the cable is the same. These days I get the message only once a week or so.
Interesting is that we both use IBM drives albeit different generations.
I found the udma setting affects speed but not the dma-timer-expiry problem.
/dev/hda:
ATA device, with non-removable media
powers-up in standby; SET FEATURES subcmd spins-up.
Model Number: IC35L090AVV207-0
Serial Number: VNVC00G3CABSMD
Firmware Revision: V23OA63A
Standards:
Used: ATA/ATAPI-6 T13 1410D revision 3a
Supported: 6 5 4 3
Configuration:
Logical max current
cylinders 16383 65535
heads 16 1
sectors/track 63 63
--
CHS current addressable sectors: 4128705
LBA user addressable sectors: 160836480
LBA48 user addressable sectors: 160836480
device size with M = 1024*1024: 78533 MBytes
device size with M = 1000*1000: 82348 MBytes (82 GB)
Capabilities:
LBA, IORDY(can be disabled)
bytes avail on r/w long: 52 Queue depth: 32
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = 16
Advanced power management level: unknown setting (0x0000)
Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=240ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* NOP cmd
* READ BUFFER cmd
* WRITE BUFFER cmd
* Host Protected Area feature set
Release interrupt
* Look-ahead
* Write cache
* Power Management feature set
Security Mode feature set
* SMART feature set
* FLUSH CACHE EXT command
* Mandatory FLUSH CACHE command
* Device Configuration Overlay feature set
* 48-bit Address feature set
Automatic Acoustic Management feature set
SET MAX security extension
Address Offset Reserved Area Boot
SET FEATURES subcommand required to spinup after power up
Power-Up In Standby feature set
Advanced Power Management feature set
* READ/WRITE DMA QUEUED
* General Purpose Logging feature set
* SMART self-test
* SMART error logging
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
46min for SECURITY ERASE UNIT.
HW reset results:
CBLID- above Vih
Device num = 0 determined by the jumper
Checksum: correct
> > Regards
> > Michael
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [BUG?] SIS IDE DMA errors
2003-09-26 17:53 ` Vojtech Pavlik
2003-09-26 17:46 ` Måns Rullgård
@ 2003-09-26 18:29 ` Michael Frank
2003-09-29 11:18 ` Lionel Bouton
2 siblings, 0 replies; 26+ messages in thread
From: Michael Frank @ 2003-09-26 18:29 UTC (permalink / raw)
To: Vojtech Pavlik, M?ns Rullg?rd; +Cc: Vojtech Pavlik, andre, linux-kernel
On Saturday 27 September 2003 01:53, Vojtech Pavlik wrote:
> On Fri, Sep 26, 2003 at 07:27:35PM +0200, M?ns Rullg?rd wrote:
> > Vojtech Pavlik <vojtech@suse.cz> writes:
> >
> > > Actually, it's me who wrote the 961 and 963 support. It works fine for
> > > most people. Did you check you cabling?
> >
> > I'm dealing with a laptop, but I suppose I could wiggle the cables a
> > bit. I still doubt it's a cable problem, since reading works
> > flawlessly.
>
> Hmm, that's indeed interesting and it'd point to a driver problem -
> when reading, the drive is dictating the timing, but when writing, it's
> the controllers turn.
>
> So if the controller timing is not correctly programmed, reads function,
> but writes don't.
>
> Can you send me the output of 'lspci -vvxxx' of the IDE device?
> I'll take a look to see if it looks correct.
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (prog-if 80 [Master])
Subsystem: Micro-Star International Co., Ltd.: Unknown device 5332
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 128
Interrupt: pin ? routed to IRQ 10
Region 4: I/O ports at 4000 [size=16]
Capabilities: [58] 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: 39 10 13 55 05 00 10 02 00 80 01 01 00 80 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 40 00 00 00 00 00 00 00 00 00 00 62 14 32 53
30: 00 00 00 00 58 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 06 00 00 00 00 00
50: f2 07 f2 07 ea 96 d5 d0 01 00 02 86 00 00 00 00
60: ff aa ff aa 00 00 00 00 00 00 00 00 00 00 00 00
70: 17 21 06 04 00 60 1c 1e 00 60 1c 1e 00 60 1c 1e
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>
> > It appears to me that during heavy IO load, some DMA interrupts get
> > lost, for some reason.
>
> Well, I've got this feeling that not just IDE interrupts get lost under
> heavy IO load with recent kernels ...
Timer interrupts too as clocks seem to run slow only
on a number of machines.
Regards
Michael
Regards
Michael
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [BUG?] SIS IDE DMA errors
2003-09-26 17:46 ` Måns Rullgård
@ 2003-09-26 18:33 ` Vojtech Pavlik
2003-09-26 19:19 ` Michael Frank
2003-09-29 9:22 ` Måns Rullgård
0 siblings, 2 replies; 26+ messages in thread
From: Vojtech Pavlik @ 2003-09-26 18:33 UTC (permalink / raw)
To: M?ns Rullg?rd; +Cc: Vojtech Pavlik, Michael Frank, linux-kernel
On Fri, Sep 26, 2003 at 07:46:03PM +0200, M?ns Rullg?rd wrote:
> Vojtech Pavlik <vojtech@suse.cz> writes:
>
> >> > Actually, it's me who wrote the 961 and 963 support. It works fine for
> >> > most people. Did you check you cabling?
> >>
> >> I'm dealing with a laptop, but I suppose I could wiggle the cables a
> >> bit. I still doubt it's a cable problem, since reading works
> >> flawlessly.
> >
> > Hmm, that's indeed interesting and it'd point to a driver problem -
>
> See, I told you :)
>
> > when reading, the drive is dictating the timing, but when writing, it's
> > the controllers turn.
> >
> > So if the controller timing is not correctly programmed, reads function,
> > but writes don't.
>
> Furthermore, short writes work just fine. The errors usually start
> happening after about 100 MB at full speed. When copying from NFS
> over a 100 MB/s network it usually goes a little longer, sometimes
> even up to 500 MB. All this could indicate that there is some error
> in the timing, and that it takes some time for it build up enough to
> trigger the bad things. Or am I wrong?
Well, yes. There's nothing to build up. There are no two timers to
synchronize - basically the controller sends the data at a certain speed
and the drive must be able to understand the data at that speed. So, if
you configure the controller to UDMA133 and the drive can only do
UDMA100, it'll fail sooner or later. It doesn't necessarily fail
immediately, since the drive has some margin above its engineered speed
that it'll be able to receive.
> Why can't the drive give notice when it's ready to accept more data?
It does, it does. The problem would only occur if the signalling rate
was too high for the driver to receive it. If the drive's buffers are
full, it'll signal the controller to delay sending, but first the data
must reach the buffer.
> That would seem like the simple solution, instead of trying to
> synchronize the timers.
There fortunately are no timers to be synchronized. However, you can't
do the handshake at every single byte, that'd slow down the transfers
considerablt.
>
> > Can you send me the output of 'lspci -vvxxx' of the IDE device?
> > I'll take a look to see if it looks correct.
>
> Here you go:
Thanks.
> 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0) (prog-if 80 [Master])
> Subsystem: Asustek Computer, Inc.: Unknown device 1688
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 128
> Region 4: I/O ports at b800 [size=16]
> 00: 39 10 13 55 07 00 00 00 d0 80 01 01 00 80 80 00
> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 20: 01 b8 00 00 00 00 00 00 00 00 00 00 43 10 88 16
> 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 40: 31 81 00 00 31 85 00 00 08 01 e6 51 00 02 00 02
Ok, this means:
31 - hda: 90ns data active time, 30 ns data recovery time (PIO4)
41 - hda: UDMA enabled, UDMA mode 5 (UDMA100)
00 - hdb: 240ns/360ns (PIO0) - no drive present
00 - hdb: UDMA disabled
31 - hdc: 90ns/30ns PIO4
85 - hdc: UDMA enabled, UDMA mode 2 (UDMA33)
00 - hdd: 240ns/360ns (PIO0) - no drive present
00 - hdd: UDMA disabled
So the config is correct if you have /dev/hda your harddrive, that's
capable of UDMA100 and /dev/hdc a CDROM and capable of UDMA33. Is that
right?
08 - 80-wire cables (needed for UDMA44 and higher) NOT installed.
FIFO threshold set to 3/4 for read and to 1/4 for write.
01 - IDE controller in compatibility mode. Native and test modes
disabled. (normal)
e6 - PCI burst enable, EDB R-R pipeline enable, Fast postwrite enable,
device ID masqueraded as sis5513 (although real is 5517)
channels 0 and 1 enabled in normal mode
51 - Postwrite enabled on hda and hdc, prefetch on hda only
00 02 - 512 bytes prefetch size for hda
00 02 - 512 bytes prefetch size for hdc
All this is OK, possibly except for the 80-wire cable not being present,
but if this is a notebook, there might be a completely different cable
type than what's standard, and the detection might not work there.
> 50: 01 00 01 06 00 00 00 00 00 00 00 00 00 00 00 00
> 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> >> It appears to me that during heavy IO load, some DMA interrupts get
> >> lost, for some reason.
> >
> > Well, I've got this feeling that not just IDE interrupts get lost under
> > heavy IO load with recent kernels ...
>
> Like mouse and keyboard...
Like everything. But only for mouse, keyboard, timer and ide it HURTS.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [BUG?] SIS IDE DMA errors
2003-09-26 18:33 ` Vojtech Pavlik
@ 2003-09-26 19:19 ` Michael Frank
2003-09-27 6:13 ` Vojtech Pavlik
2003-09-29 9:22 ` Måns Rullgård
1 sibling, 1 reply; 26+ messages in thread
From: Michael Frank @ 2003-09-26 19:19 UTC (permalink / raw)
To: Vojtech Pavlik, mru; +Cc: linux-kernel
On Saturday 27 September 2003 02:33, Vojtech Pavlik wrote:
> On Fri, Sep 26, 2003 at 07:46:03PM +0200, M?ns Rullg?rd wrote:
> > Vojtech Pavlik <vojtech@suse.cz> writes:
> >
> > >> > Actually, it's me who wrote the 961 and 963 support. It works fine for
> > >> > most people. Did you check you cabling?
> > >>
> > >> I'm dealing with a laptop, but I suppose I could wiggle the cables a
> > >> bit. I still doubt it's a cable problem, since reading works
> > >> flawlessly.
> > >
> > > Hmm, that's indeed interesting and it'd point to a driver problem -
> >
> > See, I told you :)
> >
> > > when reading, the drive is dictating the timing, but when writing, it's
> > > the controllers turn.
> > >
> > > So if the controller timing is not correctly programmed, reads function,
> > > but writes don't.
> >
> > Furthermore, short writes work just fine. The errors usually start
> > happening after about 100 MB at full speed. When copying from NFS
> > over a 100 MB/s network it usually goes a little longer, sometimes
> > even up to 500 MB. All this could indicate that there is some error
> > in the timing, and that it takes some time for it build up enough to
> > trigger the bad things. Or am I wrong?
>
> Well, yes. There's nothing to build up. There are no two timers to
> synchronize - basically the controller sends the data at a certain speed
> and the drive must be able to understand the data at that speed. So, if
> you configure the controller to UDMA133 and the drive can only do
> UDMA100, it'll fail sooner or later. It doesn't necessarily fail
> immediately, since the drive has some margin above its engineered speed
> that it'll be able to receive.
>
> > Why can't the drive give notice when it's ready to accept more data?
>
> It does, it does. The problem would only occur if the signalling rate
> was too high for the driver to receive it. If the drive's buffers are
> full, it'll signal the controller to delay sending, but first the data
> must reach the buffer.
>
> > That would seem like the simple solution, instead of trying to
> > synchronize the timers.
>
> There fortunately are no timers to be synchronized. However, you can't
> do the handshake at every single byte, that'd slow down the transfers
> considerablt.
>
> >
> > > Can you send me the output of 'lspci -vvxxx' of the IDE device?
> > > I'll take a look to see if it looks correct.
> >
> > Here you go:
>
> Thanks.
>
> > 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0) (prog-if 80 [Master])
> > Subsystem: Asustek Computer, Inc.: Unknown device 1688
> > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> > Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> > Latency: 128
> > Region 4: I/O ports at b800 [size=16]
> > 00: 39 10 13 55 07 00 00 00 d0 80 01 01 00 80 80 00
> > 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 20: 01 b8 00 00 00 00 00 00 00 00 00 00 43 10 88 16
> > 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 40: 31 81 00 00 31 85 00 00 08 01 e6 51 00 02 00 02
>
> Ok, this means:
>
> 31 - hda: 90ns data active time, 30 ns data recovery time (PIO4)
> 41 - hda: UDMA enabled, UDMA mode 5 (UDMA100)
> 00 - hdb: 240ns/360ns (PIO0) - no drive present
> 00 - hdb: UDMA disabled
> 31 - hdc: 90ns/30ns PIO4
> 85 - hdc: UDMA enabled, UDMA mode 2 (UDMA33)
> 00 - hdd: 240ns/360ns (PIO0) - no drive present
> 00 - hdd: UDMA disabled
>
> So the config is correct if you have /dev/hda your harddrive, that's
> capable of UDMA100 and /dev/hdc a CDROM and capable of UDMA33. Is that
> right?
>
> 08 - 80-wire cables (needed for UDMA44 and higher) NOT installed.
> FIFO threshold set to 3/4 for read and to 1/4 for write.
>
> 01 - IDE controller in compatibility mode. Native and test modes
> disabled. (normal)
>
> e6 - PCI burst enable, EDB R-R pipeline enable, Fast postwrite enable,
> device ID masqueraded as sis5513 (although real is 5517)
> channels 0 and 1 enabled in normal mode
>
> 51 - Postwrite enabled on hda and hdc, prefetch on hda only
>
> 00 02 - 512 bytes prefetch size for hda
> 00 02 - 512 bytes prefetch size for hdc
>
> All this is OK, possibly except for the 80-wire cable not being present,
> but if this is a notebook, there might be a completely different cable
> type than what's standard, and the detection might not work there.
>
> > 50: 01 00 01 06 00 00 00 00 00 00 00 00 00 00 00 00
> > 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>
> > >> It appears to me that during heavy IO load, some DMA interrupts get
> > >> lost, for some reason.
> > >
> > > Well, I've got this feeling that not just IDE interrupts get lost under
> > > heavy IO load with recent kernels ...
> >
> > Like mouse and keyboard...
>
> Like everything. But only for mouse, keyboard, timer and ide it HURTS.
>
> --
> Vojtech Pavlik
> SuSE Labs, SuSE CR
>
>
Was running 2.4.22.
Now running 2.6.0-test5. Fresh boot.
00:0f.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RT8139
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (8000ns min, 16000ns max)
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at e000 [size=256]
Region 1: Memory at eb102000 (32-bit, non-prefetchable) [size=256]
Expansion ROM at <unassigned> [disabled] [size=64K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00: ec 10 39 81 07 00 90 02 10 00 00 02 00 20 00 00
10: 01 e0 00 00 00 20 10 eb 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 ec 10 39 81
30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 01 20 40
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
I am surprised at your analysis of the pci bus data. By what you
stated my drive(r) should be doing PIO ;)
50: 01 00 c2 f7 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
/dev/hda:
Timing buffer-cache reads: 128 MB in 0.36 seconds =352.67 MB/sec
Timing buffered disk reads: 64 MB in 1.20 seconds = 53.25 MB/sec
[root@mhfl4 03:10:20 mhf]# v ht
/dev/hda:
Timing buffer-cache reads: 128 MB in 0.37 seconds =346.00 MB/sec
Timing buffered disk reads: 64 MB in 1.20 seconds = 53.21 MB/sec
It does 53MB/s and by earlier drive info as mailed drive reports set to udma5.
Regards
Michael
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [BUG?] SIS IDE DMA errors
2003-09-26 15:38 ` Måns Rullgård
@ 2003-09-26 19:44 ` Michael Frank
2003-09-29 9:23 ` Måns Rullgård
0 siblings, 1 reply; 26+ messages in thread
From: Michael Frank @ 2003-09-26 19:44 UTC (permalink / raw)
To: Måns Rullgård; +Cc: Vojtech Pavlik, linux-kernel
On Friday 26 September 2003 23:38, Måns Rullgård wrote:
> Michael Frank <mhf@linuxmail.org> writes:
>
> >> > Suspect chipset related issue which should be looked into.
> >>
> >> That's what someone told me three months ago, too. Nothing happened,
> >> though.
> >>
> >
> > OK, now that we are two, we copy the IDE maintainer ;)
> >
> > I guess it is fair to say that we are happy to test patches.
> >
> > And here is my lspci -vv.
> >
> > 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (prog-if 80 [Master])
> > Subsystem: Micro-Star International Co., Ltd.: Unknown device 5332
> > Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> > Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> > Latency: 128
> > Interrupt: pin ? routed to IRQ 10
> > Region 4: I/O ports at 4000 [size=16]
> > Capabilities: <available only to root>
>
> Mine looks rather similar, but there are a few differences. Mine has
> Mem+ and DEVSEL=fast.
>
> 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0) (prog-if 80 [Master])
> Subsystem: Asustek Computer, Inc.: Unknown device 1688
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 128
> Region 4: I/O ports at b800 [size=16]
>
>
>
Here is my ATA config of 2.6.0-test5. Could you please send same ex your .config. I will build it and see if anything changes.
#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_IDEDISK_STROKE is not set
CONFIG_BLK_DEV_IDECS=m
CONFIG_BLK_DEV_IDECD=m
# CONFIG_BLK_DEV_IDETAPE is not set
CONFIG_BLK_DEV_IDEFLOPPY=m
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_TASKFILE_IO=y
#
# IDE chipset support/bugfixes
#
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
CONFIG_BLK_DEV_OPTI621=y
CONFIG_BLK_DEV_RZ1000=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDE_TCQ is not set
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_IDEDMA_PCI_WIP is not set
CONFIG_BLK_DEV_ADMA=y
CONFIG_BLK_DEV_AEC62XX=y
CONFIG_BLK_DEV_ALI15X3=y
CONFIG_WDC_ALI15X3=y
CONFIG_BLK_DEV_AMD74XX=y
CONFIG_BLK_DEV_CMD64X=y
CONFIG_BLK_DEV_TRIFLEX=y
CONFIG_BLK_DEV_CY82C693=y
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
CONFIG_BLK_DEV_HPT34X=y
CONFIG_BLK_DEV_HPT366=y
CONFIG_BLK_DEV_SC1200=y
CONFIG_BLK_DEV_PIIX=y
CONFIG_BLK_DEV_NS87415=y
CONFIG_BLK_DEV_PDC202XX_OLD=y
# CONFIG_PDC202XX_BURST is not set
CONFIG_BLK_DEV_PDC202XX_NEW=y
# CONFIG_PDC202XX_FORCE is not set
CONFIG_BLK_DEV_SVWKS=y
CONFIG_BLK_DEV_SIIMAGE=y
CONFIG_BLK_DEV_SIS5513=y
CONFIG_BLK_DEV_SLC90E66=y
CONFIG_BLK_DEV_TRM290=y
CONFIG_BLK_DEV_VIA82CXXX=y
# CONFIG_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_DMA_NONPCI is not set
# CONFIG_BLK_DEV_HD is not set
Regards
Michael
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [BUG?] SIS IDE DMA errors
2003-09-26 19:19 ` Michael Frank
@ 2003-09-27 6:13 ` Vojtech Pavlik
2003-09-27 6:40 ` Michael Frank
0 siblings, 1 reply; 26+ messages in thread
From: Vojtech Pavlik @ 2003-09-27 6:13 UTC (permalink / raw)
To: Michael Frank; +Cc: Vojtech Pavlik, mru, linux-kernel
On Sat, Sep 27, 2003 at 03:19:37AM +0800, Michael Frank wrote:
> > > 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0) (prog-if 80 [Master])
> > > Subsystem: Asustek Computer, Inc.: Unknown device 1688
> > > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> > > Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> > > Latency: 128
> > > Region 4: I/O ports at b800 [size=16]
> > > 00: 39 10 13 55 07 00 00 00 d0 80 01 01 00 80 80 00
> > > 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > 20: 01 b8 00 00 00 00 00 00 00 00 00 00 43 10 88 16
> > > 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > 40: 31 81 00 00 31 85 00 00 08 01 e6 51 00 02 00 02
> >
> > Ok, this means:
> >
> > 31 - hda: 90ns data active time, 30 ns data recovery time (PIO4)
> > 41 - hda: UDMA enabled, UDMA mode 5 (UDMA100)
> > 00 - hdb: 240ns/360ns (PIO0) - no drive present
> > 00 - hdb: UDMA disabled
> > 31 - hdc: 90ns/30ns PIO4
> > 85 - hdc: UDMA enabled, UDMA mode 2 (UDMA33)
> > 00 - hdd: 240ns/360ns (PIO0) - no drive present
> > 00 - hdd: UDMA disabled
>
> Was running 2.4.22.
>
> Now running 2.6.0-test5. Fresh boot.
>
> 00:0f.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
> Subsystem: Realtek Semiconductor Co., Ltd. RT8139
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 32 (8000ns min, 16000ns max)
> Interrupt: pin A routed to IRQ 11
> Region 0: I/O ports at e000 [size=256]
> Region 1: Memory at eb102000 (32-bit, non-prefetchable) [size=256]
> Expansion ROM at <unassigned> [disabled] [size=64K]
> Capabilities: [50] Power Management version 2
> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3hot+,D3cold+)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> 00: ec 10 39 81 07 00 90 02 10 00 00 02 00 20 00 00
> 10: 01 e0 00 00 00 20 10 eb 00 00 00 00 00 00 00 00
> 20: 00 00 00 00 00 00 00 00 00 00 00 00 ec 10 39 81
> 30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 01 20 40
> 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>
> I am surprised at your analysis of the pci bus data. By what you
> stated my drive(r) should be doing PIO ;)
1) You're looking at your ethernet controller config registers,
not at the IDE controller config registers.
2) The 961 and 963 have completely different config register layout.
Actually, there is not much common between the 961 and the 963,
except for the '5513' fake ID. (The 961's real id is 5517, and the
963's is 5518).
--
Vojtech Pavlik
SuSE Labs, SuSE CR
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [BUG?] SIS IDE DMA errors
2003-09-27 6:13 ` Vojtech Pavlik
@ 2003-09-27 6:40 ` Michael Frank
0 siblings, 0 replies; 26+ messages in thread
From: Michael Frank @ 2003-09-27 6:40 UTC (permalink / raw)
To: Vojtech Pavlik; +Cc: Vojtech Pavlik, mru, linux-kernel
On Saturday 27 September 2003 14:13, Vojtech Pavlik wrote:
> On Sat, Sep 27, 2003 at 03:19:37AM +0800, Michael Frank wrote:
>
> > > > 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0) (prog-if 80 [Master])
> > > > Subsystem: Asustek Computer, Inc.: Unknown device 1688
> > > > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> > > > Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> > > > Latency: 128
> > > > Region 4: I/O ports at b800 [size=16]
> > > > 00: 39 10 13 55 07 00 00 00 d0 80 01 01 00 80 80 00
> > > > 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > > 20: 01 b8 00 00 00 00 00 00 00 00 00 00 43 10 88 16
> > > > 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > > 40: 31 81 00 00 31 85 00 00 08 01 e6 51 00 02 00 02
> > >
> > > Ok, this means:
> > >
> > > 31 - hda: 90ns data active time, 30 ns data recovery time (PIO4)
> > > 41 - hda: UDMA enabled, UDMA mode 5 (UDMA100)
> > > 00 - hdb: 240ns/360ns (PIO0) - no drive present
> > > 00 - hdb: UDMA disabled
> > > 31 - hdc: 90ns/30ns PIO4
> > > 85 - hdc: UDMA enabled, UDMA mode 2 (UDMA33)
> > > 00 - hdd: 240ns/360ns (PIO0) - no drive present
> > > 00 - hdd: UDMA disabled
> >
> 1) You're looking at your ethernet controller config registers,
> not at the IDE controller config registers.
Oooooooooops, pasted the wrong one - was 3am ;)
Here it is with 2.4.22:
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (prog-if 80 [Master])
Subsystem: Micro-Star International Co., Ltd.: Unknown device 5332
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 128
Interrupt: pin ? routed to IRQ 10
Region 4: I/O ports at 4000 [size=16]
Capabilities: [58] 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: 39 10 13 55 05 00 10 02 00 80 01 01 00 80 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 40 00 00 00 00 00 00 00 00 00 00 62 14 32 53
30: 00 00 00 00 58 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 06 00 00 00 00 00
50: f2 07 f2 07 ea 96 d5 d0 01 00 02 86 00 00 00 00
60: ff aa ff aa 00 00 00 00 00 00 00 00 00 00 00 00
70: 17 21 06 04 00 60 1c 1e 00 60 1c 1e 00 60 1c 1e
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2.6.0-test5 is same
Regards
Michael
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [BUG?] SIS IDE DMA errors
2003-09-26 18:33 ` Vojtech Pavlik
2003-09-26 19:19 ` Michael Frank
@ 2003-09-29 9:22 ` Måns Rullgård
2003-09-29 10:01 ` Vojtech Pavlik
1 sibling, 1 reply; 26+ messages in thread
From: Måns Rullgård @ 2003-09-29 9:22 UTC (permalink / raw)
To: Vojtech Pavlik; +Cc: Michael Frank, linux-kernel
Vojtech Pavlik <vojtech@suse.cz> writes:
>> > Can you send me the output of 'lspci -vvxxx' of the IDE device?
>> > I'll take a look to see if it looks correct.
>>
>> Here you go:
>
> Thanks.
>
>> 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0) (prog-if 80 [Master])
>> Subsystem: Asustek Computer, Inc.: Unknown device 1688
>> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
>> Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>> Latency: 128
>> Region 4: I/O ports at b800 [size=16]
>> 00: 39 10 13 55 07 00 00 00 d0 80 01 01 00 80 80 00
>> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 20: 01 b8 00 00 00 00 00 00 00 00 00 00 43 10 88 16
>> 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 40: 31 81 00 00 31 85 00 00 08 01 e6 51 00 02 00 02
>
> Ok, this means:
>
> 31 - hda: 90ns data active time, 30 ns data recovery time (PIO4)
> 41 - hda: UDMA enabled, UDMA mode 5 (UDMA100)
> 00 - hdb: 240ns/360ns (PIO0) - no drive present
> 00 - hdb: UDMA disabled
> 31 - hdc: 90ns/30ns PIO4
> 85 - hdc: UDMA enabled, UDMA mode 2 (UDMA33)
> 00 - hdd: 240ns/360ns (PIO0) - no drive present
> 00 - hdd: UDMA disabled
>
> So the config is correct if you have /dev/hda your harddrive, that's
> capable of UDMA100 and /dev/hdc a CDROM and capable of UDMA33. Is that
> right?
That's it.
> 08 - 80-wire cables (needed for UDMA44 and higher) NOT installed.
> FIFO threshold set to 3/4 for read and to 1/4 for write.
>
> 01 - IDE controller in compatibility mode. Native and test modes
> disabled. (normal)
>
> e6 - PCI burst enable, EDB R-R pipeline enable, Fast postwrite enable,
> device ID masqueraded as sis5513 (although real is 5517)
> channels 0 and 1 enabled in normal mode
>
> 51 - Postwrite enabled on hda and hdc, prefetch on hda only
>
> 00 02 - 512 bytes prefetch size for hda
> 00 02 - 512 bytes prefetch size for hdc
>
> All this is OK, possibly except for the 80-wire cable not being present,
> but if this is a notebook, there might be a completely different cable
> type than what's standard, and the detection might not work there.
I've got no idea what the cable is like. Is there anything to be
learned from opening the beast? Anything in particular to look for?
--
Måns Rullgård
mru@users.sf.net
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [BUG?] SIS IDE DMA errors
2003-09-26 19:44 ` Michael Frank
@ 2003-09-29 9:23 ` Måns Rullgård
2003-09-29 13:12 ` Michael Frank
0 siblings, 1 reply; 26+ messages in thread
From: Måns Rullgård @ 2003-09-29 9:23 UTC (permalink / raw)
To: Michael Frank; +Cc: Vojtech Pavlik, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 193 bytes --]
Michael Frank <mhf@linuxmail.org> writes:
> Here is my ATA config of 2.6.0-test5. Could you please send same ex
> your .config. I will build it and see if anything changes.
>
OK, attaching.
[-- Attachment #2: .config --]
[-- Type: text/plain, Size: 23501 bytes --]
#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_STANDALONE=y
CONFIG_BROKEN_ON_SMP=y
#
# General setup
#
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=14
# CONFIG_IKCONFIG is not set
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
CONFIG_KMOD=y
#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
CONFIG_MPENTIUM4=y
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MELAN is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_HUGETLB_PAGE=y
CONFIG_HPET_TIMER=y
# CONFIG_HPET_EMULATE_RTC is not set
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=y
CONFIG_X86_MCE_P4THERMAL=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
CONFIG_HAVE_DEC_LOCK=y
#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
CONFIG_SOFTWARE_SUSPEND=y
#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI_HT=y
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
CONFIG_ACPI_ASUS=y
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_DEBUG=y
CONFIG_ACPI_BUS=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
#
# APM (Advanced Power Management) BIOS Support
#
# CONFIG_APM is not set
#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
# CONFIG_CPU_FREQ_PROC_INTF is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_GOV_POWERSAVE is not set
CONFIG_CPU_FREQ_GOV_USERSPACE=m
# CONFIG_CPU_FREQ_24_API is not set
CONFIG_CPU_FREQ_TABLE=y
#
# CPUFreq processor drivers
#
# CONFIG_X86_ACPI_CPUFREQ is not set
# CONFIG_X86_POWERNOW_K6 is not set
# CONFIG_X86_POWERNOW_K7 is not set
# CONFIG_X86_GX_SUSPMOD is not set
# CONFIG_X86_SPEEDSTEP_ICH is not set
# CONFIG_X86_SPEEDSTEP_CENTRINO is not set
CONFIG_X86_P4_CLOCKMOD=y
# CONFIG_X86_LONGRUN is not set
# CONFIG_X86_LONGHAUL is not set
#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
# CONFIG_PCI_LEGACY_PROC is not set
CONFIG_PCI_NAMES=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
CONFIG_HOTPLUG=y
#
# PCMCIA/CardBus support
#
CONFIG_PCMCIA=m
CONFIG_YENTA=m
CONFIG_CARDBUS=y
# CONFIG_I82092 is not set
# CONFIG_TCIC is not set
#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set
#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
# CONFIG_BINFMT_MISC is not set
#
# Generic Driver Options
#
# CONFIG_FW_LOADER is not set
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
# CONFIG_PARPORT is not set
#
# Plug and Play support
#
# CONFIG_PNP is not set
#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=m
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_BLK_DEV_INITRD is not set
# CONFIG_LBD is not set
#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_IDEDISK_STROKE is not set
# CONFIG_BLK_DEV_IDECS is not set
CONFIG_BLK_DEV_IDECD=m
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_TASKFILE_IO=y
#
# IDE chipset support/bugfixes
#
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_GENERIC is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDE_TCQ is not set
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_IDEDMA_PCI_WIP is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
CONFIG_BLK_DEV_SIS5513=y
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_DMA_NONPCI is not set
# CONFIG_BLK_DEV_HD is not set
#
# SCSI device support
#
CONFIG_SCSI=m
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=m
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=m
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_REPORT_LUNS=y
CONFIG_SCSI_CONSTANTS=y
# CONFIG_SCSI_LOGGING is not set
#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
#
# PCMCIA SCSI adapter support
#
# CONFIG_PCMCIA_AHA152X is not set
# CONFIG_PCMCIA_FDOMAIN is not set
# CONFIG_PCMCIA_NINJA_SCSI is not set
# CONFIG_PCMCIA_QLOGIC is not set
#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
# CONFIG_BLK_DEV_MD is not set
CONFIG_BLK_DEV_DM=y
CONFIG_DM_IOCTL_V4=y
#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
CONFIG_IEEE1394=m
#
# Subsystem Options
#
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
# CONFIG_IEEE1394_OUI_DB is not set
#
# Device Drivers
#
#
# Texas Instruments PCILynx requires I2C bit-banging
#
CONFIG_IEEE1394_OHCI1394=m
#
# Protocol Drivers
#
# CONFIG_IEEE1394_VIDEO1394 is not set
CONFIG_IEEE1394_SBP2=m
# CONFIG_IEEE1394_SBP2_PHYS_DMA is not set
# CONFIG_IEEE1394_ETH1394 is not set
# CONFIG_IEEE1394_DV1394 is not set
CONFIG_IEEE1394_RAWIO=m
# CONFIG_IEEE1394_CMP is not set
#
# I2O device support
#
# CONFIG_I2O is not set
#
# Networking support
#
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
# CONFIG_NETLINK_DEV is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
CONFIG_INET_ECN=y
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_IPV6 is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_NETFILTER is not set
#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IPV6_SCTP__=y
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_LLC is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set
#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
CONFIG_NETDEVICES=y
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_MII is not set
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_B44 is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
CONFIG_SIS900=m
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set
#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set
#
# Token Ring devices (depends on LLC=y)
#
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set
#
# Wan interfaces
#
# CONFIG_WAN is not set
#
# PCMCIA network device support
#
# CONFIG_NET_PCMCIA is not set
#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set
#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set
#
# ISDN subsystem
#
# CONFIG_ISDN_BOOL is not set
#
# Telephony Support
#
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=m
# CONFIG_INPUT_EVBUG is not set
#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set
#
# Serial drivers
#
# CONFIG_SERIAL_8250 is not set
#
# Non-8250 serial port support
#
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
#
# I2C support
#
CONFIG_I2C=m
# CONFIG_I2C_ALGOBIT is not set
# CONFIG_I2C_ALGOPCF is not set
# CONFIG_I2C_CHARDEV is not set
#
# I2C Hardware Sensors Mainboard support
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_PIIX4 is not set
CONFIG_I2C_SIS96X=m
# CONFIG_I2C_VIAPRO is not set
#
# I2C Hardware Sensors Chip support
#
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_I2C_SENSOR is not set
#
# Mice
#
# CONFIG_BUSMOUSE is not set
# CONFIG_QIC02_TAPE is not set
#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set
#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
CONFIG_RTC=m
# CONFIG_GEN_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=m
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
# CONFIG_AGP_INTEL is not set
# CONFIG_AGP_NVIDIA is not set
CONFIG_AGP_SIS=m
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_DRM is not set
#
# PCMCIA character devices
#
# CONFIG_SYNCLINK_CS is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
#
# File systems
#
CONFIG_EXT2_FS=m
CONFIG_EXT2_FS_XATTR=y
# CONFIG_EXT2_FS_POSIX_ACL is not set
# CONFIG_EXT2_FS_SECURITY is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=m
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
# CONFIG_UDF_FS is not set
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
# CONFIG_MSDOS_FS is not set
CONFIG_VFAT_FS=m
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_DEVFS_FS=y
CONFIG_DEVFS_MOUNT=y
# CONFIG_DEVFS_DEBUG is not set
CONFIG_DEVPTS_FS=y
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
# CONFIG_HUGETLBFS is not set
CONFIG_RAMFS=y
#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
#
# Network File Systems
#
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
# CONFIG_NFS_V4 is not set
# CONFIG_NFSD is not set
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
# CONFIG_EXPORTFS is not set
CONFIG_SUNRPC=m
# CONFIG_SUNRPC_GSS is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
# CONFIG_AFS_FS is not set
#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_NLS=y
#
# Native Language Support
#
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=m
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=m
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
CONFIG_NLS_ISO8859_1=m
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set
#
# Graphics support
#
CONFIG_FB=y
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_VESA is not set
# CONFIG_VIDEO_SELECT is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
CONFIG_FB_SIS=y
# CONFIG_FB_SIS_300 is not set
CONFIG_FB_SIS_315=y
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_VIRTUAL is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_PCI_CONSOLE=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
#
# Logo configuration
#
# CONFIG_LOGO is not set
#
# Sound
#
CONFIG_SOUND=m
#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
# CONFIG_SND_SEQUENCER is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_RTCTIMER=m
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
#
# Generic devices
#
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set
#
# PCI devices
#
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
CONFIG_SND_INTEL8X0=m
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VX222 is not set
#
# ALSA USB devices
#
# CONFIG_SND_USB_AUDIO is not set
#
# PCMCIA devices
#
# CONFIG_SND_VXPOCKET is not set
# CONFIG_SND_VXP440 is not set
#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set
#
# USB support
#
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set
#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
CONFIG_USB_BANDWIDTH=y
# CONFIG_USB_DYNAMIC_MINORS is not set
#
# USB Host Controller Drivers
#
# CONFIG_USB_EHCI_HCD is not set
CONFIG_USB_OHCI_HCD=m
# CONFIG_USB_UHCI_HCD is not set
#
# USB Device Class drivers
#
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_BLUETOOTH_TTY is not set
# CONFIG_USB_MIDI is not set
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_HP8200e is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
#
# USB Human Interface Devices (HID)
#
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
# CONFIG_USB_HIDDEV is not set
#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_XPAD is not set
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_SCANNER is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_HPUSBSCSI is not set
#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set
#
# Video4Linux support is needed for USB Multimedia device support
#
#
# USB Network adaptors
#
# CONFIG_USB_AX8817X_STANDALONE is not set
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
#
# USB port drivers
#
#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set
#
# USB Miscellaneous drivers
#
# CONFIG_USB_TIGL is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_BRLVGER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_GADGET is not set
#
# Bluetooth support
#
# CONFIG_BT is not set
#
# Profiling support
#
# CONFIG_PROFILING is not set
#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_IOVIRT is not set
CONFIG_MAGIC_SYSRQ=y
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_FRAME_POINTER is not set
CONFIG_X86_EXTRA_IRQS=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
#
# Security options
#
CONFIG_SECURITY=y
# CONFIG_SECURITY_NETWORK is not set
# CONFIG_SECURITY_CAPABILITIES is not set
# CONFIG_SECURITY_ROOTPLUG is not set
# CONFIG_SECURITY_SELINUX is not set
#
# Cryptographic options
#
# CONFIG_CRYPTO is not set
#
# Library routines
#
# CONFIG_CRC32 is not set
CONFIG_X86_BIOS_REBOOT=y
[-- Attachment #3: Type: text/plain, Size: 37 bytes --]
--
Måns Rullgård
mru@users.sf.net
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [BUG?] SIS IDE DMA errors
2003-09-29 9:22 ` Måns Rullgård
@ 2003-09-29 10:01 ` Vojtech Pavlik
2003-10-02 0:32 ` Michael Frank
0 siblings, 1 reply; 26+ messages in thread
From: Vojtech Pavlik @ 2003-09-29 10:01 UTC (permalink / raw)
To: M?ns Rullg?rd; +Cc: Vojtech Pavlik, Michael Frank, linux-kernel
On Mon, Sep 29, 2003 at 11:22:28AM +0200, M?ns Rullg?rd wrote:
> > 08 - 80-wire cables (needed for UDMA44 and higher) NOT installed.
> > FIFO threshold set to 3/4 for read and to 1/4 for write.
> >
> > 01 - IDE controller in compatibility mode. Native and test modes
> > disabled. (normal)
> >
> > e6 - PCI burst enable, EDB R-R pipeline enable, Fast postwrite enable,
> > device ID masqueraded as sis5513 (although real is 5517)
> > channels 0 and 1 enabled in normal mode
> >
> > 51 - Postwrite enabled on hda and hdc, prefetch on hda only
> >
> > 00 02 - 512 bytes prefetch size for hda
> > 00 02 - 512 bytes prefetch size for hdc
> >
> > All this is OK, possibly except for the 80-wire cable not being present,
> > but if this is a notebook, there might be a completely different cable
> > type than what's standard, and the detection might not work there.
>
> I've got no idea what the cable is like. Is there anything to be
> learned from opening the beast? Anything in particular to look for?
Not really, sorry.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [BUG?] SIS IDE DMA errors
2003-09-26 17:53 ` Vojtech Pavlik
2003-09-26 17:46 ` Måns Rullgård
2003-09-26 18:29 ` Michael Frank
@ 2003-09-29 11:18 ` Lionel Bouton
2 siblings, 0 replies; 26+ messages in thread
From: Lionel Bouton @ 2003-09-29 11:18 UTC (permalink / raw)
To: Vojtech Pavlik; +Cc: M?ns Rullg?rd, Michael Frank, andre, linux-kernel
Vojtech Pavlik said the following on 09/26/2003 07:53 PM:
>On Fri, Sep 26, 2003 at 07:27:35PM +0200, M?ns Rullg?rd wrote:
>
>
>>Vojtech Pavlik <vojtech@suse.cz> writes:
>>
>>
>>
>>>Actually, it's me who wrote the 961 and 963 support. It works fine for
>>>most people. Did you check you cabling?
>>>
>>>
>>I'm dealing with a laptop, but I suppose I could wiggle the cables a
>>bit. I still doubt it's a cable problem, since reading works
>>flawlessly.
>>
>>
>
>Hmm, that's indeed interesting and it'd point to a driver problem -
>when reading, the drive is dictating the timing, but when writing, it's
>the controllers turn.
>
>So if the controller timing is not correctly programmed, reads function,
>but writes don't.
>
>Can you send me the output of 'lspci -vvxxx' of the IDE device?
>I'll take a look to see if it looks correct.
>
>
>
>>It appears to me that during heavy IO load, some DMA interrupts get
>>lost, for some reason.
>>
>>
>
>Well, I've got this feeling that not just IDE interrupts get lost under
>heavy IO load with recent kernels ...
>
>
>
This could explain some odd reports. Amongst the usual causes like flaky
hardware, kernel misconfiguration and the likes, I encountered some
people for which IO-APIC support would throw their data away...
Now I always ask the users to recompile without IO-APIC, this usually
brings other problems (awful ethernet perfs for one user comes to my
mind) but tends to solve IDE instability.
Until today, I've not a single report where lspci -vxxx highlighted any
IDE register misconfiguration, AFAICS your code *is* correct Vojtech.
LB.
--
Lionel Bouton - inet6
---------------------------------------------------------------------
o Siege social: 51, rue de Verdun - 92158 Suresnes
/ _ __ _ Acces Bureaux: 33 rue Benoit Malon - 92150 Suresnes
/ /\ /_ / /_ France
\/ \/_ / /_/ Tel. +33 (0) 1 41 44 85 36
Inetsys S.A. Fax +33 (0) 1 46 97 20 10
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [BUG?] SIS IDE DMA errors
2003-09-29 9:23 ` Måns Rullgård
@ 2003-09-29 13:12 ` Michael Frank
0 siblings, 0 replies; 26+ messages in thread
From: Michael Frank @ 2003-09-29 13:12 UTC (permalink / raw)
To: Måns Rullgård; +Cc: Vojtech Pavlik, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 696 bytes --]
On Monday 29 September 2003 17:23, Måns Rullgård wrote:
> Michael Frank <mhf@linuxmail.org> writes:
>
> > Here is my ATA config of 2.6.0-test5. Could you please send same ex
> > your .config. I will build it and see if anything changes.
> >
>
> OK, attaching.
>
>
I patched your ATA config into my config, built it and tested it
with the attached script. More usage info inside script.
$ tstinter start # creates 2 400MB files
No problems seen, sorry this did not help.
You have no problems with recent 2.4 kernels?
Could you do also lspci -vvxxx using 2.4.22 and see if there is a
difference?, also stress it with the script if you can.
Regards
Michael
[-- Attachment #2: tstinter --]
[-- Type: application/x-shellscript, Size: 5790 bytes --]
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [BUG?] SIS IDE DMA errors
2003-09-29 10:01 ` Vojtech Pavlik
@ 2003-10-02 0:32 ` Michael Frank
0 siblings, 0 replies; 26+ messages in thread
From: Michael Frank @ 2003-10-02 0:32 UTC (permalink / raw)
To: M?ns Rullg?rd; +Cc: linux-kernel, Vojtech Pavlik
On Monday 29 September 2003 18:01, Vojtech Pavlik wrote:
> On Mon, Sep 29, 2003 at 11:22:28AM +0200, M?ns Rullg?rd wrote:
>
> > > 08 - 80-wire cables (needed for UDMA44 and higher) NOT installed.
> > > FIFO threshold set to 3/4 for read and to 1/4 for write.
> > >
> > > 01 - IDE controller in compatibility mode. Native and test modes
> > > disabled. (normal)
> > >
> > > e6 - PCI burst enable, EDB R-R pipeline enable, Fast postwrite enable,
> > > device ID masqueraded as sis5513 (although real is 5517)
> > > channels 0 and 1 enabled in normal mode
> > >
> > > 51 - Postwrite enabled on hda and hdc, prefetch on hda only
> > >
> > > 00 02 - 512 bytes prefetch size for hda
> > > 00 02 - 512 bytes prefetch size for hdc
> > >
> > > All this is OK, possibly except for the 80-wire cable not being present,
> > > but if this is a notebook, there might be a completely different cable
> > > type than what's standard, and the detection might not work there.
> >
> > I've got no idea what the cable is like. Is there anything to be
> > learned from opening the beast? Anything in particular to look for?
>
Notebook drive is plugged streight into a circuit board or connected by a
short cable. The unlikely possibility for hardware is that it is out of spec
and it also could be the drive.
IBM/Hitachi have standalone PCDOS diagnostic floppy disk images and IIRC some
linux based stuff for their drives on their support website. You could run
this diagnostics and see if you learn more.
BTW, as it is in a way an interrupt problem - you tried wo ACPI and IIRC,
you have no APIC?
Regards
Michael
^ permalink raw reply [flat|nested] 26+ messages in thread
* [BUG?] lost interrupt (was: SIS IDE DMA errors)
2003-09-26 12:30 [BUG?] SIS IDE DMA errors Måns Rullgård
2003-09-26 14:08 ` Michael Frank
@ 2003-10-03 8:38 ` David Caldwell
2003-10-03 9:08 ` [BUG?] lost interrupt Måns Rullgård
1 sibling, 1 reply; 26+ messages in thread
From: David Caldwell @ 2003-10-03 8:38 UTC (permalink / raw)
To: linux-kernel
> With all 2.6.0 versions so far, I get these errors when writing lots
> of data to the disk:
I am getting these same errors with 2.6.0-test6. The difference is,
I'm not using a SiS IDE controller. I have a Promise 20276 on my
motherboard which was the controller getting the lost interrupt
error. I am running RAID5 using disks on this controller and on a
Promise 20267 PCI card (note: 67 not 76!). I seemed to start getting
the error when my disks started going with lots of activity.
I had booted with "noapic" at the time. Without "noapic" my
motherboard wouldn't boot at all (it seemed to hang right after
detecting the IDE devices, but I don't know if that is relevant).
> Losing too many ticks!
> TSC cannot be used as a timesource. (Are you running with SpeedStep?)
> Falling back to a sane timesource.
I was definitely getting this same error.
> hda: lost interrupt
> hda: lost interrupt
> hda: lost interrupt
> hda: lost interrupt
I was definitely getting this error, except it was on hdg (my promise
20276).
> hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
>
> hda: drive not ready for command
I don't remember if I was getting this error or not.
Here is my lspci output:
00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333]
00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333 AGP]
00:08.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 04)
00:09.0 Unknown mass storage controller: Promise Technology, Inc. 20267 (rev 02)
00:0a.0 FireWire (IEEE 1394): Lucent Microelectronics FW323 (rev 04)
00:0b.0 Ethernet controller: Linksys Network Everywhere Fast Ethernet 10/100 model NC100 (rev 11)
00:0c.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11)
00:0c.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11)
00:0f.0 RAID bus controller: Promise Technology, Inc. PDC20276 IDE (rev 01)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8233A ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus Master IDE (rev 06)
00:11.2 USB Controller: VIA Technologies, Inc. USB (rev 23)
00:11.3 USB Controller: VIA Technologies, Inc. USB (rev 23)
00:13.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:14.0 USB Controller: VIA Technologies, Inc. USB (rev 50)
00:14.1 USB Controller: VIA Technologies, Inc. USB (rev 50)
00:14.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 51)
01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 86C326 5598/6326 (rev 92)
I didn't have the forethought to save my dmesg output. This screwed up
my RAID pretty bad, so I'm a little reticent about making it happen
again...
I just wanted to let it known that it wasn't just happening to SiS IDE
controllers.
-David
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [BUG?] lost interrupt
2003-10-03 8:38 ` [BUG?] lost interrupt (was: SIS IDE DMA errors) David Caldwell
@ 2003-10-03 9:08 ` Måns Rullgård
2003-10-03 20:07 ` David Caldwell
0 siblings, 1 reply; 26+ messages in thread
From: Måns Rullgård @ 2003-10-03 9:08 UTC (permalink / raw)
To: linux-kernel
David Caldwell <david+kernel@porkrind.org> writes:
>> With all 2.6.0 versions so far, I get these errors when writing lots
>> of data to the disk:
>
> I am getting these same errors with 2.6.0-test6. The difference is,
> I'm not using a SiS IDE controller. I have a Promise 20276 on my
> motherboard which was the controller getting the lost interrupt
> error. I am running RAID5 using disks on this controller and on a
> Promise 20267 PCI card (note: 67 not 76!). I seemed to start getting
> the error when my disks started going with lots of activity.
>
> I had booted with "noapic" at the time. Without "noapic" my
> motherboard wouldn't boot at all (it seemed to hang right after
> detecting the IDE devices, but I don't know if that is relevant).
That doesn't make any difference for me.
>> Losing too many ticks!
>> TSC cannot be used as a timesource. (Are you running with SpeedStep?)
>> Falling back to a sane timesource.
>
> I was definitely getting this same error.
>
>> hda: lost interrupt
>> hda: lost interrupt
>> hda: lost interrupt
>> hda: lost interrupt
>
> I was definitely getting this error, except it was on hdg (my promise
> 20276).
>
>> hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
>>
>> hda: drive not ready for command
>
> I don't remember if I was getting this error or not.
>
>
> I didn't have the forethought to save my dmesg output. This screwed up
> my RAID pretty bad, so I'm a little reticent about making it happen
> again...
In my case, no data is lost. It just takes an awfully long time to
write it.
> I just wanted to let it known that it wasn't just happening to SiS IDE
> controllers.
Could you post your dmesg output for that machine? It might reveal
something, even the error doesn't occur.
--
Måns Rullgård
mru@users.sf.net
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [BUG?] lost interrupt
2003-10-03 9:08 ` [BUG?] lost interrupt Måns Rullgård
@ 2003-10-03 20:07 ` David Caldwell
0 siblings, 0 replies; 26+ messages in thread
From: David Caldwell @ 2003-10-03 20:07 UTC (permalink / raw)
To: linux-kernel
> David Caldwell <david+kernel@porkrind.org> writes:
>
> > I didn't have the forethought to save my dmesg output. This screwed up
> > my RAID pretty bad, so I'm a little reticent about making it happen
> > again...
>
> In my case, no data is lost. It just takes an awfully long time to
> write it.
I'm sorry, I just remembered a crutial point. The lost insterrupt
probably wasn't the thing that screwed up my raid. I had forgotten
when I wrote the first message, but I thought the lost interrupt
message might be because the disk itself was screwed up so I tried to
do an ATA reset with hdparm. That locked my system hard. Oops. Perhaps
if I had just been patient I would have been able to shutdown nicely...
After I locked, I couldn't even boot 2.6.0 because I would get the lost
interrupt almost immediately after it started rebuilding my raid set.
> > I just wanted to let it known that it wasn't just happening to SiS IDE
> > controllers.
>
> Could you post your dmesg output for that machine? It might reveal
> something, even the error doesn't occur.
Sure. Here it is:
Linux version 2.6.0-test6 (david@death.porkrind.org) (gcc version 3.3.2 20030908 (Debian prerelease)) #3 SMP Sun Sep 28 04:15:14 PDT 2003
Video mode to be used for restore is f00
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001fff0000 (usable)
BIOS-e820: 000000001fff0000 - 000000001fff8000 (ACPI data)
BIOS-e820: 000000001fff8000 - 0000000020000000 (ACPI NVS)
BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
user-defined physical RAM map:
user: 0000000000000000 - 000000000009fc00 (usable)
user: 000000000009fc00 - 00000000000a0000 (reserved)
user: 00000000000f0000 - 0000000000100000 (reserved)
user: 0000000000100000 - 000000001fff0000 (usable)
user: 000000001fff0000 - 000000001fff8000 (ACPI data)
user: 000000001fff8000 - 0000000020000000 (ACPI NVS)
user: 00000000fec00000 - 00000000fec01000 (reserved)
user: 00000000fee00000 - 00000000fee01000 (reserved)
user: 00000000fff80000 - 0000000100000000 (reserved)
511MB LOWMEM available.
found SMP MP-table at 000fb0f0
hm, page 000fb000 reserved twice.
hm, page 000fc000 reserved twice.
hm, page 000f6000 reserved twice.
hm, page 000f7000 reserved twice.
On node 0 totalpages: 131056
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 126960 pages, LIFO batch:16
HighMem zone: 0 pages, LIFO batch:1
DMI 2.3 present.
ACPI: RSDP (v000 AMI ) @ 0x000fc0d0
ACPI: RSDT (v001 AMIINT VIA_K7 0x00000011 MSFT 0x00000097) @ 0x1fff0000
ACPI: FADT (v001 AMIINT VIA_K7 0x00000011 MSFT 0x00000097) @ 0x1fff0030
ACPI: MADT (v001 AMIINT 0x00000009 MSFT 0x00000097) @ 0x1fff00b0
ACPI: DSDT (v001 VIA VIA_K7 0x00001000 MSFT 0x0100000d) @ 0x00000000
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 6:6 APIC version 16
ACPI: Skipping IOAPIC probe due to 'noapic' option.
Using ACPI for processor (LAPIC) configuration information
Intel MultiProcessor Specification v1.1
Virtual Wire compatibility mode.
OEM ID: VIA Product ID: KT266 APIC at: 0xFEE00000
I/O APIC #2 Version 2 at 0xFEC00000.
Enabling APIC mode: Flat. Using 1 I/O APICs
Processors: 1
Building zonelist for node : 0
Kernel command line: root=/dev/hda2 ide0=dma ide1=dma ide2=dma ide3=dma acpi=1 apm=0 video=aty128fb:1024x768-32@75 noapic single mem=524224K
ide_setup: ide0=dma
ide_setup: ide1=dma
ide_setup: ide2=dma
ide_setup: ide3=dma
Initializing CPU#0
PID hash table entries: 2048 (order 11: 16384 bytes)
Detected 1600.792 MHz processor.
Console: colour VGA+ 80x25
Memory: 514224k/524224k available (2312k kernel code, 9252k reserved, 912k data, 200k init, 0k highmem)
Calibrating delay loop... 3153.92 BogoMIPS
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: After generic identify, caps: 0383fbff c1cbfbff 00000000 00000000
CPU: After vendor identify, caps: 0383fbff c1cbfbff 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After all inits, caps: 0383fbff c1cbfbff 00000000 00000020
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
CPU0: AMD Athlon(tm) XP 1900+ stepping 02
per-CPU timeslice cutoff: 731.66 usecs.
task migration cache decay timeout: 1 msecs.
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000080
ESR value after enabling vector: 00000000
Error: only one processor found.
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 1599.0810 MHz.
..... host bus clock speed is 266.0635 MHz.
Starting migration thread for cpu 0
CPUS done 8
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xfdb31, last bus=1
PCI: Using configuration type 1
ACPI: Subsystem revision 20030813
ACPI-0269: *** Error: Looking up [\_S1_] in namespace, AE_ALREADY_EXISTS
ACPI-1121: *** Error: , AE_ALREADY_EXISTS
ACPI-0125: *** Error: acpi_load_tables: Could not load namespace: AE_ALREADY_EXISTS
ACPI-0134: *** Error: acpi_load_tables: Could not load tables: AE_ALREADY_EXISTS
ACPI: Unable to load the System Description Tables
SCSI subsystem initialized
drivers/usb/core/usb.c: registered new driver usbfs
drivers/usb/core/usb.c: registered new driver hub
ACPI: ACPI tables contain no PCI IRQ routing entries
PCI: Invalid ACPI-PCI IRQ routing table
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Using IRQ router default [1106/3147] at 0000:00:11.0
PCI: IRQ 0 for device 0000:00:11.1 doesn't match PIRQ mask - try pci=usepirqmask
PCI: Hardcoded IRQ 14 for device 0000:00:11.1
hgafb: HGA card not detected.
vga16fb: initializing
vga16fb: mapped to 0xc00a0000
fb0: VGA16 VGA frame buffer device
Initializing Cryptographic API
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
spurious 8259A interrupt: IRQ7.
Console: switching to colour frame buffer device 80x30
pty: 256 Unix98 ptys configured
Linux agpgart interface v0.100 (c) Dave Jones
Using anticipatory io scheduler
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PDC20267: IDE controller at PCI slot 0000:00:09.0
PDC20267: chipset revision 2
PDC20267: ROM enabled at 0xdffd0000
PDC20267: 100% native mode on irq 12
PDC20267: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
ide2: BM-DMA at 0xcc00-0xcc07, BIOS settings: hde:DMA, hdf:pio
ide3: BM-DMA at 0xcc08-0xcc0f, BIOS settings: hdg:DMA, hdh:pio
hde: Maxtor 6Y120L0, ATA DISK drive
ide2 at 0xdc00-0xdc07,0xd802 on irq 12
hdg: Maxtor 6Y120L0, ATA DISK drive
ide3 at 0xd400-0xd407,0xd002 on irq 12
PDC20276: IDE controller at PCI slot 0000:00:0f.0
PDC20276: chipset revision 1
PDC20276: 100% native mode on irq 10
ide4: BM-DMA at 0xb000-0xb007, BIOS settings: hdi:pio, hdj:pio
ide5: BM-DMA at 0xb008-0xb00f, BIOS settings: hdk:pio, hdl:pio
hdi: Maxtor 6Y120L0, ATA DISK drive
ide4 at 0xc000-0xc007,0xbc02 on irq 10
hdk: WDC WD1200JB-00DUA0, ATA DISK drive
ide5 at 0xb800-0xb807,0xb402 on irq 10
hda: QUANTUM FIREBALL EX6.4A, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hde: max request size: 128KiB
hde: 240121728 sectors (122942 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
hde: hde1
hdg: max request size: 128KiB
hdg: 240121728 sectors (122942 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
hdg: hdg1
hdi: max request size: 128KiB
hdi: 240121728 sectors (122942 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(133)
hdi: hdi1
hdk: max request size: 1024KiB
hdk: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63, UDMA(100)
hdk: hdk1
hda: max request size: 128KiB
hda: 12594960 sectors (6448 MB) w/418KiB Cache, CHS=13328/15/63
hda: hda1 hda2
st: Version 20030811, fixed bufsize 32768, s/g segs 256
Console: switching to colour frame buffer device 80x30
Initializing USB Mass Storage driver...
drivers/usb/core/usb.c: registered new driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
serio: i8042 AUX port at 0x60,0x64 irq 12
input: AT Translated Set 2 keyboard on isa0060/serio0
serio: i8042 KBD port at 0x60,0x64 irq 1
md: linear personality registered as nr 1
md: raid0 personality registered as nr 2
md: raid1 personality registered as nr 3
md: raid5 personality registered as nr 4
raid5: measuring checksumming speed
8regs : 2136.000 MB/sec
8regs_prefetch: 1904.000 MB/sec
32regs : 1640.000 MB/sec
32regs_prefetch: 1628.000 MB/sec
pIII_sse : 4096.000 MB/sec
pII_mmx : 4248.000 MB/sec
p5_mmx : 5684.000 MB/sec
raid5: using function: pIII_sse (4096.000 MB/sec)
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 32768)
ip_conntrack version 2.1 (4095 buckets, 32760 max) - 304 bytes per conntrack
ip_tables: (C) 2000-2002 Netfilter core team
NET: Registered protocol family 1
NET: Registered protocol family 17
md: Autodetecting RAID arrays.
md: autorun ...
md: considering hdk1 ...
md: adding hdk1 ...
md: adding hdi1 ...
md: adding hdg1 ...
md: adding hde1 ...
md: created md1
md: bind<hde1>
md: bind<hdg1>
md: bind<hdi1>
md: bind<hdk1>
md: running: <hdk1><hdi1><hdg1><hde1>
raid5: device hdk1 operational as raid disk 2
raid5: device hdi1 operational as raid disk 3
raid5: device hdg1 operational as raid disk 1
raid5: device hde1 operational as raid disk 0
raid5: allocated 4185kB for md1
raid5: raid level 5 set md1 active with 4 out of 4 devices, algorithm 2
RAID5 conf printout:
--- rd:4 wd:4 fd:0
disk 0, o:1, dev:hde1
disk 1, o:1, dev:hdg1
disk 2, o:1, dev:hdk1
disk 3, o:1, dev:hdi1
md: ... autorun DONE.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 200k freed
version 0 swap is no longer supported. Use mkswap -v1 /dev/hda1
EXT3 FS on hda2, internal journal
drivers/usb/core/usb.c: registered new driver hiddev
drivers/usb/core/usb.c: registered new driver hid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
ns83820.c: National Semiconductor DP83820 10/100/1000 driver.
Linux Tulip driver version 1.1.13 (May 11, 2002)
eth0: ADMtek Comet rev 17 at 0xc400, 00:04:5A:50:1F:85, IRQ 10.
8139too Fast Ethernet driver 0.9.26
eth1: RealTek RTL8139 at 0xe084db00, 00:20:ed:31:8d:b4, IRQ 10
eth1: Identified 8139 chip type 'RTL-8100B/8139D'
kjournald starting. Commit interval 5 seconds
EXT3 FS on md1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
version 0 swap is no longer supported. Use mkswap -v1 /dev/hda1
ehci_hcd 0000:00:14.2: EHCI Host Controller
ehci_hcd 0000:00:14.2: irq 10, pci mem e084fa00
ehci_hcd 0000:00:14.2: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:14.2: USB 2.0 enabled, EHCI 0.95, driver 2003-Jun-13
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 4 ports detected
ohci-hcd: 2003 Feb 24 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ohci-hcd: block sizes: ed 64 td 64
drivers/usb/host/uhci-hcd.c: USB Universal Host Controller Interface driver v2.1
uhci-hcd 0000:00:11.2: UHCI Host Controller
uhci-hcd 0000:00:11.2: irq 10, io base 0000a800
uhci-hcd 0000:00:11.2: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
uhci-hcd 0000:00:11.3: UHCI Host Controller
uhci-hcd 0000:00:11.3: irq 10, io base 0000ac00
uhci-hcd 0000:00:11.3: new USB bus registered, assigned bus number 3
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
uhci-hcd 0000:00:14.0: UHCI Host Controller
uhci-hcd 0000:00:14.0: irq 10, io base 00009c00
uhci-hcd 0000:00:14.0: new USB bus registered, assigned bus number 4
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
uhci-hcd 0000:00:14.1: UHCI Host Controller
uhci-hcd 0000:00:14.1: irq 12, io base 0000a000
uhci-hcd 0000:00:14.1: new USB bus registered, assigned bus number 5
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
hub 2-0:1.0: new USB device on port 1, assigned address 2
hub 2-1:1.0: USB hub found
hub 2-1:1.0: 4 ports detected
hub 2-1:1.0: new USB device on port 3, assigned address 3
input: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:11.2-1.3
hub 2-1:1.0: new USB device on port 4, assigned address 4
input: USB HID v1.00 Keyboard [Griffin Technology, Inc. iMate, USB To ADB Adaptor] on usb-0000:00:11.2-1.4
input: USB HID v1.00 Mouse [Griffin Technology, Inc. iMate, USB To ADB Adaptor] on usb-0000:00:11.2-1.4
eth1: link up, 100Mbps, full-duplex, lpa 0x45E1
So at this point I did some dd's to my raid set as a test and
somewhere between 200-300 MB my screen when blank and my monitor lost
sync. This lasted for 5 seconds and then the picture came back. I
checked dmesg again and got:
Losing too many ticks!
TSC cannot be used as a timesource. (Are you running with SpeedStep?)
Falling back to a sane timesource.
So I kept doing dd's (3 at a time) and adding more and more modules in
but I could never get it to do the "lost interrupt" thing. Even after
booting all the way up into X and playing with myth tv which is what I
was doing when it happened the first time.
Here's my /proc/interrupts:
CPU0
0: 4511238 XT-PIC timer
1: 9786 XT-PIC i8042
2: 0 XT-PIC cascade
10: 724396 XT-PIC ide4, ide5, ehci_hcd, uhci-hcd, uhci-hcd, uhci-hcd, eth1, eth0, bttv0, btaudio
12: 346598 XT-PIC ide2, ide3, uhci-hcd, Ensoniq AudioPCI
14: 964016 XT-PIC ide0
NMI: 0
LOC: 4489849
ERR: 123957
MIS: 0
And just for completeness, my lsmod:
Module Size Used by
sis 52160 0
appletalk 41680 18
psnap 4676 1 appletalk
llc 8660 1 psnap
btaudio 17872 0
tuner 15820 0
tvaudio 22732 0
msp3400 24932 0
bttv 141924 0
video_buf 22148 1 bttv
i2c_algo_bit 10632 1 bttv
btcx_risc 5256 1 bttv
v4l2_common 5056 1 bttv
videodev 10112 1 bttv
snd_pcm_oss 53604 0
snd_mixer_oss 19648 1 snd_pcm_oss
snd_ens1371 26664 0
snd_rawmidi 26080 1 snd_ens1371
snd_seq_device 8776 1 snd_rawmidi
snd_pcm 103840 2 snd_pcm_oss,snd_ens1371
snd_page_alloc 12420 1 snd_pcm
snd_timer 27396 1 snd_pcm
snd_ac97_codec 55044 1 snd_ens1371
snd 54884 8 snd_pcm_oss,snd_mixer_oss,snd_ens1371,snd_rawmidi,snd_seq_device,snd_pcm,snd_timer,snd_ac97_codec
soundcore 9856 3 btaudio,bttv,snd
gameport 5504 1 snd_ens1371
uhci_hcd 34960 0
ohci_hcd 19520 0
ehci_hcd 25540 0
8139too 24448 0
tulip 47456 0
ns83820 20936 0
hid 33664 0
-David
^ permalink raw reply [flat|nested] 26+ messages in thread
end of thread, other threads:[~2003-10-03 20:07 UTC | newest]
Thread overview: 26+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-09-26 12:30 [BUG?] SIS IDE DMA errors Måns Rullgård
2003-09-26 14:08 ` Michael Frank
2003-09-26 14:07 ` Måns Rullgård
2003-09-26 15:32 ` Michael Frank
2003-09-26 15:38 ` Måns Rullgård
2003-09-26 19:44 ` Michael Frank
2003-09-29 9:23 ` Måns Rullgård
2003-09-29 13:12 ` Michael Frank
2003-09-26 16:59 ` Vojtech Pavlik
2003-09-26 17:27 ` Måns Rullgård
2003-09-26 17:53 ` Vojtech Pavlik
2003-09-26 17:46 ` Måns Rullgård
2003-09-26 18:33 ` Vojtech Pavlik
2003-09-26 19:19 ` Michael Frank
2003-09-27 6:13 ` Vojtech Pavlik
2003-09-27 6:40 ` Michael Frank
2003-09-29 9:22 ` Måns Rullgård
2003-09-29 10:01 ` Vojtech Pavlik
2003-10-02 0:32 ` Michael Frank
2003-09-26 18:29 ` Michael Frank
2003-09-29 11:18 ` Lionel Bouton
2003-09-26 18:15 ` Michael Frank
2003-09-26 18:22 ` Michael Frank
2003-10-03 8:38 ` [BUG?] lost interrupt (was: SIS IDE DMA errors) David Caldwell
2003-10-03 9:08 ` [BUG?] lost interrupt Måns Rullgård
2003-10-03 20:07 ` David Caldwell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).