* Problems with disk + network on 2.6.25.11-60.fc8
@ 2008-08-04 17:39 David Stuart
2008-08-04 17:42 ` Alan Cox
0 siblings, 1 reply; 9+ messages in thread
From: David Stuart @ 2008-08-04 17:39 UTC (permalink / raw)
To: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 22852 bytes --]
Hello everyone,
I have trawled the depths of the Internet, scoured the innermost reaches
of the Usenet, and finally I arrive, beaten and bruised, at the steps to
the Linux kernel mailing list, to seek advice from the penguins
themselves. I humbly prostrate myself .. :)
My first request: Please CC me directly on replies as I am not
subscribed to the list.
Now to the meat of it; I have been experiencing a lot of trouble with
system freezes; but these are not crippling freezes in the sense that
they come back after a few seconds. They are always accompanied by the
following log in /var/log/messages:
----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<
Aug 3 21:44:34 localhost kernel: ata1.00: exception Emask 0x0 SAct 0x0
SErr 0x0 action 0x2 frozen
Aug 3 21:44:34 localhost kernel: ata1.00: cmd
ca/00:40:b8:c9:f3/00:00:00:00:00/e8 tag 0 dma 32768 out
Aug 3 21:44:34 localhost kernel: res
40/00:78:00:00:00/00:00:00:00:00/50 Emask 0x4 (timeout)
Aug 3 21:44:34 localhost kernel: ata1.00: status: { DRDY }
Aug 3 21:44:39 localhost kernel: ata1: port is slow to respond, please
be patient (Status 0x80)
Aug 3 21:44:44 localhost kernel: ata1: device not ready (errno=-16),
forcing hardreset
Aug 3 21:44:44 localhost kernel: ata1: soft resetting link
Aug 3 21:44:45 localhost kernel: ata1.00: configured for UDMA/100
Aug 3 21:44:45 localhost kernel: ata1.01: configured for UDMA/100
Aug 3 21:44:45 localhost kernel: ata1: EH complete
Aug 3 21:44:45 localhost kernel: sd 0:0:0:0: [sda] 160086528 512-byte
hardware sectors (81964 MB)
Aug 3 21:44:45 localhost kernel: sd 0:0:0:0: [sda] Write Protect is off
Aug 3 21:44:45 localhost kernel: sd 0:0:0:0: [sda] Write cache:
enabled, read cache: enabled, doesn't support DPO or FUA
Aug 3 21:44:45 localhost kernel: sd 0:0:1:0: [sdb] 488397168 512-byte
hardware sectors (250059 MB)
Aug 3 21:44:45 localhost kernel: sd 0:0:1:0: [sdb] Write Protect is off
Aug 3 21:44:45 localhost kernel: sd 0:0:1:0: [sdb] Write cache:
enabled, read cache: enabled, doesn't support DPO or FUA
Aug 3 21:44:45 localhost kernel: sd 0:0:0:0: [sda] 160086528 512-byte
hardware sectors (81964 MB)
Aug 3 21:44:45 localhost kernel: sd 0:0:0:0: [sda] Write Protect is off
Aug 3 21:44:45 localhost kernel: sd 0:0:0:0: [sda] Write cache:
enabled, read cache: enabled, doesn't support DPO or FUA
Aug 3 21:44:45 localhost kernel: sd 0:0:1:0: [sdb] 488397168 512-byte
hardware sectors (250059 MB)
Aug 3 21:44:45 localhost kernel: sd 0:0:1:0: [sdb] Write Protect is off
Aug 3 21:44:45 localhost kernel: sd 0:0:1:0: [sdb] Write cache:
enabled, read cache: enabled, doesn't support DPO or FUA
----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<
Now, I know what you're thinking, this problem has been reported a lot
already. But, as I mentioned I have done a lot of searching online
looking for answers. There are a number of posts which seem like related
problems, especially if you search Google for "Exception emask". Most of
these suggest a work-around of putting the following boot options:
noapic acpi=off
Let me assure you already that this workaround did not fix my problems.
Nor does the flag "combined_mode=libata"; which was suggested elsewhere.
Another post suggests that smartd is the culprit; not only do I have the
latest version of smartd (which was supposed to fix the issue), but even
if I disable smartd I still see the same problem.
Yet another post indicates a problem with CD-ROM firmware. I have tried
disconnecting my CD-ROM from the system, swapping it with another, all
to no avail.
Yet another another post suggests that the skge (or its predecessor) was
to blame; so I replaced the network card with another I have, using the
8139cp driver. I still see the same problem.
Somewhere around this point, I gouged out my eyes and tore out my hair.
Thank goodness I am good at touch-typing.
What I have noticed, is that I only receive this exception (which seems
related to disk activity) when my machine is under heavy NETWORK LOAD;
i.e. when I am downloading the latest kernel (to pick a random example).
If there is no network activity the machine seems to be fine.
The hard drive which experiences the problems is running off a Maxtor
Ultra100 IDE controller card (promise-based). It's possible that this is
the culprit, but I am having a hard time moving the drive off this card
because I have setup my main partition using LVM (possible, but
non-obvious). I upgraded its firmware just in case, but that didn't help.
I do not believe that the drive itself has hardware problems because it
behaves fine when network traffic is not present. Also I did not notice
this problem until I upgraded to Fedora 7, which I believe was the first
Fedora distro to change the way the hard drives were represented (from
the old /dev/hdx system). I also use the following hdparms on the drive:
hdparm -S 120 /dev/sdb
At some point I thought this was the problem, but through trial and
error I believe it is OK. However it is possible that my sleuthing
abilities in this department are not up to snuff.
I am looking for any advice which will help me to workaround the
problem. I am not a kernel developer but I am fine with advanced system
configuration. I just want to have my smoothly running Linux box back again.
What follows is the usual system information:
===================================
[dave@localhost ~]$ uname -a
Linux localhost.localdomain 2.6.25.11-60.fc8 #1 SMP Mon Jul 21 01:40:51
EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
[dave@localhost ~]$ lspci -vv
00:00.0 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
Subsystem: ASUSTeK Computer Inc. A8V Deluxe
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort+ >SERR- <PERR- INTx-
Latency: 64
Region 0: Memory at <ignored> (32-bit, prefetchable)
Capabilities: <access denied>
Kernel driver in use: agpgart-amd64
00:00.1 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
00:00.2 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
00:00.3 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
00:00.4 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
00:00.7 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge
[K8T800/K8T890 South] (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: faf00000-fbffffff
Prefetchable memory behind bridge: e0000000-f9ffffff
Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR+ NoISA- VGA+ MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: <access denied>
Kernel modules: shpchp
00:0d.0 Mass storage controller: Promise Technology, Inc. PDC20267
(FastTrak100/Ultra100) (rev 02)
Subsystem: Promise Technology, Inc. Ultra100
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64
Interrupt: pin A routed to IRQ 18
Region 0: I/O ports at a800 [size=8]
Region 1: I/O ports at a400 [size=4]
Region 2: I/O ports at a000 [size=8]
Region 3: I/O ports at 9800 [size=4]
Region 4: I/O ports at 9400 [size=64]
Region 5: Memory at fab00000 (32-bit, non-prefetchable) [size=128K]
Expansion ROM at faa00000 [disabled] [size=64K]
Capabilities: <access denied>
Kernel driver in use: pata_pdc202xx_old
Kernel modules: pata_pdc202xx_old
00:0e.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- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64 (8000ns min, 16000ns max)
Interrupt: pin A routed to IRQ 19
Region 0: I/O ports at b000 [size=256]
Region 1: Memory at fac00000 (32-bit, non-prefetchable) [size=256]
Capabilities: <access denied>
Kernel driver in use: 8139too
Kernel modules: 8139too, 8139cp
00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID
Controller (rev 80)
Subsystem: ASUSTeK Computer Inc. A7V600/K8V Deluxe/K8V-X/A8V
Deluxe motherboard
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64
Interrupt: pin B routed to IRQ 20
Region 0: I/O ports at d000 [size=8]
Region 1: I/O ports at c800 [size=4]
Region 2: I/O ports at c400 [size=8]
Region 3: I/O ports at c000 [size=4]
Region 4: I/O ports at b800 [size=16]
Region 5: I/O ports at b400 [size=256]
Capabilities: <access denied>
Kernel driver in use: sata_via
Kernel modules: sata_via
00:0f.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
(prog-if 8a [Master SecP PriP])
Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X/A8V Deluxe motherboard
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32
Interrupt: pin A routed to IRQ 20
Region 0: [virtual] Memory at 000001f0 (32-bit,
non-prefetchable) [size=8]
Region 1: [virtual] Memory at 000003f0 (type 3,
non-prefetchable) [size=1]
Region 2: [virtual] Memory at 00000170 (32-bit,
non-prefetchable) [size=8]
Region 3: [virtual] Memory at 00000370 (type 3,
non-prefetchable) [size=1]
Region 4: I/O ports at fc00 [size=16]
Capabilities: <access denied>
Kernel driver in use: pata_via
Kernel modules: pata_via, ata_generic, pata_acpi
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X/A8V Deluxe motherboard
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 21
Region 4: I/O ports at d400 [size=32]
Capabilities: <access denied>
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X/A8V Deluxe motherboard
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 21
Region 4: I/O ports at d800 [size=32]
Capabilities: <access denied>
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X/A8V Deluxe motherboard
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64, Cache Line Size: 64 bytes
Interrupt: pin B routed to IRQ 21
Region 4: I/O ports at e000 [size=32]
Capabilities: <access denied>
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X/A8V Deluxe motherboard
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64, Cache Line Size: 64 bytes
Interrupt: pin B routed to IRQ 21
Region 4: I/O ports at e400 [size=32]
Capabilities: <access denied>
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) (prog-if
20 [EHCI])
Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X/A8V Deluxe motherboard
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64, Cache Line Size: 64 bytes
Interrupt: pin C routed to IRQ 21
Region 0: Memory at fae00000 (32-bit, non-prefetchable) [size=256]
Capabilities: <access denied>
Kernel driver in use: ehci_hcd
Kernel modules: ehci-hcd
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge
[KT600/K8T800/K8T890 South]
Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X/A8V Deluxe motherboard
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping+ SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Capabilities: <access denied>
Kernel modules: i2c-viapro
00:11.5 Multimedia audio controller: VIA Technologies, Inc.
VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
Subsystem: ASUSTeK Computer Inc. A8V Deluxe motherboard (Realtek
ALC850 codec)
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin C routed to IRQ 22
Region 0: I/O ports at e800 [size=256]
Capabilities: <access denied>
Kernel driver in use: VIA 82xx Audio
Kernel modules: snd-via82xx
00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem
Controller (rev 80)
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin C routed to IRQ 22
Region 0: I/O ports at 1000 [size=256]
Capabilities: <access denied>
Kernel modules: snd-via82xx-modem
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
HyperTransport Technology Configuration
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Capabilities: <access denied>
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Address Map
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
DRAM Controller
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Miscellaneous Control
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Kernel driver in use: k8temp
Kernel modules: k8temp
01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX
5500] (rev a1) (prog-if 00 [VGA controller])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 248 (1250ns min, 250ns max)
Interrupt: pin A routed to IRQ 16
Region 0: Memory at fb000000 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at e0000000 (32-bit, prefetchable) [size=256M]
[virtual] Expansion ROM at faf00000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: nvidia
Kernel modules: nvidia, nvidiafb
[dave@localhost ~]$ lsmod
Module Size Used by
autofs4 28745 2
fuse 51329 1
nf_conntrack_netbios_ns 11073 0
nf_conntrack_ipv4 17481 4
xt_multiport 11713 1
iptable_filter 11585 1
ip_tables 25681 1 iptable_filter
nf_conntrack_ipv6 23337 2
xt_state 10817 6
nf_conntrack 64849 4
nf_conntrack_netbios_ns,nf_conntrack_ipv4,nf_conntrack_ipv6,xt_state
xt_tcpudp 11841 4
ip6table_filter 11457 1
ip6_tables 26961 1 ip6table_filter
x_tables 26185 5
xt_multiport,ip_tables,xt_state,xt_tcpudp,ip6_tables
cpufreq_ondemand 15825 1
powernow_k8 24133 0
freq_table 13633 2 cpufreq_ondemand,powernow_k8
loop 23365 0
dm_multipath 25425 0
ipv6 277801 25 nf_conntrack_ipv6
snd_via82xx_modem 20685 0
sr_mod 23813 0
cdrom 40809 1 sr_mod
nvidia 8109360 24
snd_seq_dummy 11589 0
snd_via82xx 33385 4
snd_seq_oss 38081 0
snd_seq_midi_event 15297 1 snd_seq_oss
gameport 20049 1 snd_via82xx
snd_seq 58273 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_ac97_codec 119705 2 snd_via82xx_modem,snd_via82xx
ac97_bus 10305 1 snd_ac97_codec
snd_pcm_oss 46657 0
snd_mpu401_uart 15681 1 snd_via82xx
snd_mixer_oss 22977 2 snd_pcm_oss
snd_rawmidi 29249 1 snd_mpu401_uart
snd_pcm 79561 4
snd_via82xx_modem,snd_via82xx,snd_ac97_codec,snd_pcm_oss
pata_via 18629 0
snd_seq_device 15189 4
snd_seq_dummy,snd_seq_oss,snd_seq,snd_rawmidi
i2c_viapro 16729 0
snd_timer 28625 2 snd_seq,snd_pcm
ata_generic 14917 0
snd 62217 18
snd_via82xx_modem,snd_via82xx,snd_seq_oss,snd_seq,snd_ac97_codec,snd_pcm_oss,snd_mpu401_uart,snd_mixer_oss,snd_rawmidi,snd_pcm,snd_seq_device,snd_timer
i2c_core 28769 2 nvidia,i2c_viapro
pata_acpi 14145 0
8139too 32065 0
k8temp 13377 0
8139cp 28225 0
hwmon 11145 1 k8temp
soundcore 15073 2 snd
parport_pc 34793 0
mii 13377 2 8139too,8139cp
pcspkr 11329 0
button 15841 0
snd_page_alloc 16593 3 snd_via82xx_modem,snd_via82xx,snd_pcm
parport 43121 1 parport_pc
shpchp 38365 0
sg 40865 0
floppy 66153 0
sata_via 17989 0
dm_snapshot 23817 0
dm_zero 10433 0
dm_mirror 31557 0
dm_mod 62201 9 dm_multipath,dm_snapshot,dm_zero,dm_mirror
pata_pdc202xx_old 15297 2
libata 148593 5
pata_via,ata_generic,pata_acpi,sata_via,pata_pdc202xx_old
sd_mod 33665 3
scsi_mod 151737 4 sr_mod,sg,libata,sd_mod
ext3 131025 2
jbd 52585 1 ext3
mbcache 15940 1 ext3
uhci_hcd 29921 0
ohci_hcd 29381 0
ehci_hcd 40141 0
(Yes, it's true I have the proprietary nvidia module installed, my
kernel is unfortunately tainted. I don't think this is the problem but
if it will help to get to the bottom of things, I will be happy to
disable it for investigative purposes).
Thank you for any help you may offer.
David
--
The only way to keep your health is to eat what you don't want, drink
what you don't like, and do what you'd rather not.
-- Mark Twain
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3254 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Problems with disk + network on 2.6.25.11-60.fc8
2008-08-04 17:39 Problems with disk + network on 2.6.25.11-60.fc8 David Stuart
@ 2008-08-04 17:42 ` Alan Cox
2008-08-04 20:31 ` David Stuart
0 siblings, 1 reply; 9+ messages in thread
From: Alan Cox @ 2008-08-04 17:42 UTC (permalink / raw)
To: David Stuart; +Cc: linux-kernel
To start with can I have a dmesg after boot and a description of what is
plugged into where (disks and CD wise)
Alan
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Problems with disk + network on 2.6.25.11-60.fc8
2008-08-04 17:42 ` Alan Cox
@ 2008-08-04 20:31 ` David Stuart
2008-08-04 20:44 ` Alan Cox
0 siblings, 1 reply; 9+ messages in thread
From: David Stuart @ 2008-08-04 20:31 UTC (permalink / raw)
To: Alan Cox; +Cc: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 22878 bytes --]
Alan Cox wrote:
> To start with can I have a dmesg after boot and a description of what is
> plugged into where (disks and CD wise)
>
> Alan
>
Hi Alain,
Sure, no problem. First the description, I'll append the dmesg output at
the end.
I have an ASUS A8V motherboard, with a Maxtor Ultra100 IDE controller
card on one of the PCI ports. On the mainboard:
- Primary IDE Master : 13GB Quantum Fireball HD (Where Windows resides,
not that I use it).
- Primary IDE Slave : LG CD-ROM, 52X
- Secondary IDE : Nothing
On the IDE controller card:
- "IDE1 slot" Master : 80GB Maxtor
- "IDE1 slot" Slave : 250GB Western Digital
- "IDE2 slot" : Nothing
The output of dmesg (after booting) follows:
==================================
Initializing cgroup subsys cpuset
Linux version 2.6.25.11-60.fc8 (mockbuild@x86-7) (gcc version 4.1.2
20070925 (Red Hat 4.1.2-33)) #1 SMP Mon Jul 21 01:40:51 EDT 2008
Command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000003ffb0000 (usable)
BIOS-e820: 000000003ffb0000 - 000000003ffc0000 (ACPI data)
BIOS-e820: 000000003ffc0000 - 000000003fff0000 (ACPI NVS)
BIOS-e820: 000000003fff0000 - 0000000040000000 (reserved)
BIOS-e820: 00000000ff780000 - 0000000100000000 (reserved)
Entering add_active_range(0, 0, 159) 0 entries of 3200 used
Entering add_active_range(0, 256, 262064) 1 entries of 3200 used
end_pfn_map = 1048576
DMI 2.3 present.
ACPI: RSDP 000FA810, 0021 (r2 ACPIAM)
ACPI: XSDT 3FFB0100, 003C (r1 A M I OEMXSDT 5000729 MSFT 97)
ACPI: FACP 3FFB0290, 00F4 (r3 A M I OEMFACP 5000729 MSFT 97)
ACPI: DSDT 3FFB03F0, 391B (r1 A0277 A0277001 1 MSFT 100000D)
ACPI: FACS 3FFC0000, 0040
ACPI: APIC 3FFB0390, 0052 (r1 A M I OEMAPIC 5000729 MSFT 97)
ACPI: OEMB 3FFC0040, 003F (r1 A M I OEMBIOS 5000729 MSFT 97)
Scanning NUMA topology in Northbridge 24
No NUMA configuration found
Faking a node at 0000000000000000-000000003ffb0000
Entering add_active_range(0, 0, 159) 0 entries of 3200 used
Entering add_active_range(0, 256, 262064) 1 entries of 3200 used
Bootmem setup node 0 0000000000000000-000000003ffb0000
NODE_DATA [000000000000b000 - 0000000000012fff]
bootmap [0000000000013000 - 000000000001aff7] pages 8
early res: 0 [0-fff] BIOS data page
early res: 1 [6000-7fff] SMP_TRAMPOLINE
early res: 2 [200000-756aeb] TEXT DATA BSS
early res: 3 [37c20000-37fef4f7] RAMDISK
early res: 4 [9f000-9ffff] EBDA
early res: 5 [8000-afff] PGTABLE
[ffffe20000000000-ffffe200001fffff] PMD ->ffff810001200000 on node 0
[ffffe20000200000-ffffe200003fffff] PMD ->ffff810001600000 on node 0
[ffffe20000400000-ffffe200005fffff] PMD ->ffff810001a00000 on node 0
[ffffe20000600000-ffffe200007fffff] PMD ->ffff810001e00000 on node 0
[ffffe20000800000-ffffe200009fffff] PMD ->ffff810002200000 on node 0
[ffffe20000a00000-ffffe20000bfffff] PMD ->ffff810002600000 on node 0
[ffffe20000c00000-ffffe20000dfffff] PMD ->ffff810002a00000 on node 0
Zone PFN ranges:
DMA 0 -> 4096
DMA32 4096 -> 1048576
Normal 1048576 -> 1048576
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
0: 0 -> 159
0: 256 -> 262064
On node 0 totalpages: 261967
DMA zone: 56 pages used for memmap
DMA zone: 1375 pages reserved
DMA zone: 2568 pages, LIFO batch:0
DMA32 zone: 3526 pages used for memmap
DMA32 zone: 254442 pages, LIFO batch:31
Normal zone: 0 pages used for memmap
Movable zone: 0 pages used for memmap
Detected use of extended apic ids on hypertransport bus
ACPI: PM-Timer IO Port: 0x808
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 (Bootup-CPU)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x81] disabled)
ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 1, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Setting APIC routing to flat
Using ACPI (MADT) for SMP configuration information
PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
PM: Registered nosave memory: 00000000000a0000 - 00000000000e4000
PM: Registered nosave memory: 00000000000e4000 - 0000000000100000
Allocating PCI resources starting at 50000000 (gap: 40000000:bf780000)
SMP: Allowing 2 CPUs, 1 hotplug CPUs
PERCPU: Allocating 43072 bytes of per cpu data
Built 1 zonelists in Node order, mobility grouping on. Total pages: 257010
Policy zone: DMA32
Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
Extended CMOS year: 2000
TSC calibrated against PM_TIMER
time.c: Detected 2202.814 MHz processor.
Console: colour VGA+ 80x25
console [tty0] enabled
Checking aperture...
Node 0: aperture @ dc000000 size 64 MB
Memory: 1023824k/1048256k available (2630k kernel code, 24044k reserved,
1408k data, 348k init)
CPA: page pool initialized 1 of 1 pages preallocated
SLUB: Genslabs=13, HWalign=64, Order=0-1, MinObjects=4, CPUs=2, Nodes=1
Calibrating delay using timer specific routine.. 4409.62 BogoMIPS
(lpj=2204812)
Security Framework initialized
SELinux: Initializing.
SELinux: Starting in permissive mode
selinux_register_security: Registering secondary module capability
Capability LSM initialized as secondary
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
Mount-cache hash table entries: 256
Initializing cgroup subsys ns
Initializing cgroup subsys cpuacct
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU 0/0 -> Node 0
ACPI: Core revision 20070126
Using local APIC timer interrupts.
APIC timer calibration result 12515985
Detected 12.515 MHz APIC timer.
Brought up 1 CPUs
sizeof(vma)=176 bytes
sizeof(page)=56 bytes
sizeof(inode)=560 bytes
sizeof(dentry)=208 bytes
sizeof(ext3inode)=760 bytes
sizeof(buffer_head)=104 bytes
sizeof(skbuff)=224 bytes
sizeof(task_struct)=6224 bytes
CPU0 attaching sched-domain:
domain 0: span 00000000,00000001
groups: 00000000,00000001
net_namespace: 1016 bytes
Time: 20:15:35 Date: 08/04/08
NET: Registered protocol family 16
No dock devices found.
ACPI: bus type pci registered
PCI: Using configuration type 1
ACPI: EC: Look up EC in DSDT
ACPI: Interpreter enabled
ACPI: (supports S0 S1 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
pci 0000:00:11.0: Enabled onboard AC97/MC97 devices
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 10 *11 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 *10 11 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 7 10 11 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 7 10 11 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 10 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 10 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 10 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 10 11 14 15) *0, disabled.
ACPI Warning (tbutils-0217): Incorrect checksum in table [OEMB] - ED,
should be E0 [20070126]
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 13 devices
ACPI: ACPI bus type pnp unregistered
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a
report
PCI: Cannot allocate resource region 0 of device 0000:00:00.0
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
agpgart: Detected AGP bridge 0
agpgart: AGP aperture is 64M @ 0xdc000000
system 00:08: ioport range 0x680-0x6ff has been reserved
system 00:08: ioport range 0x290-0x297 has been reserved
system 00:09: ioport range 0x3e1-0x3e7 has been reserved
system 00:09: ioport range 0x4d0-0x4d1 has been reserved
system 00:09: ioport range 0x800-0x87f has been reserved
system 00:09: ioport range 0x400-0x41f has been reserved
system 00:0a: iomem range 0xfec00000-0xfec00fff has been reserved
system 00:0a: iomem range 0xfee00000-0xfee00fff could not be reserved
system 00:0a: iomem range 0xfff80000-0xffffffff could not be reserved
system 00:0c: iomem range 0x0-0x9ffff could not be reserved
system 00:0c: iomem range 0xc0000-0xdffff has been reserved
system 00:0c: iomem range 0xe0000-0xfffff could not be reserved
system 00:0c: iomem range 0x100000-0x3ffeffff could not be reserved
system 00:0c: iomem range 0x0-0x0 could not be reserved
PCI: Bridge: 0000:00:01.0
IO window: disabled.
MEM window: 0xfaf00000-0xfbffffff
PREFETCH window: 0x00000000e0000000-0x00000000f9ffffff
PCI: Setting latency timer of device 0000:00:01.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 6, 262144 bytes)
TCP established hash table entries: 131072 (order: 9, 2097152 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 3901k freed
audit: initializing netlink socket (disabled)
type=2000 audit(1217880935.367:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
SELinux: Registering netfilter hooks
ksign: Installing public key data
Loading keyring
- Added public key 23D29F0AA2F12253
- User ID: Red Hat, Inc. (Kernel Module GPG key)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
PCI: VIA PCI bridge detected. Disabling DAC.
Switched to high resolution mode on CPU 0
pci 0000:00:10.4: EHCI: BIOS handoff failed (BIOS bug?) 01010001
pci 0000:01:00.0: Boot video device
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
ACPI: ACPI0007:00 is registered as cooling_device0
Real Time Clock Driver v1.12ac
Non-volatile memory driver v1.2
Linux agpgart interface v0.103
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:0b: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
brd: module loaded
input: Macintosh mouse button emulation as /class/input/input0
PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
PNP: PS/2 appears to have AUX port disabled, if this is incorrect please
boot with i8042.nopnp
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard as /class/input/input1
cpuidle: using governor ladder
cpuidle: using governor menu
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
registered taskstats version 1
Magic number: 4:154:295
hash matches device tty28
Freeing unused kernel memory: 348k freed
Write protecting the kernel read-only data: 1128k
ACPI: PCI Interrupt 0000:00:10.4[C] -> GSI 21 (level, low) -> IRQ 21
ehci_hcd 0000:00:10.4: EHCI Host Controller
ehci_hcd 0000:00:10.4: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:10.4: irq 21, io mem 0xfae00000
ehci_hcd 0000:00:10.4: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.25.11-60.fc8 ehci_hcd
usb usb1: SerialNumber: 0000:00:10.4
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:10.0[A] -> GSI 21 (level, low) -> IRQ 21
uhci_hcd 0000:00:10.0: UHCI Host Controller
uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:10.0: irq 21, io base 0x0000d400
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: UHCI Host Controller
usb usb2: Manufacturer: Linux 2.6.25.11-60.fc8 uhci_hcd
usb usb2: SerialNumber: 0000:00:10.0
ACPI: PCI Interrupt 0000:00:10.1[A] -> GSI 21 (level, low) -> IRQ 21
uhci_hcd 0000:00:10.1: UHCI Host Controller
uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:10.1: irq 21, io base 0x0000d800
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
hub 1-0:1.0: unable to enumerate USB device on port 2
usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb3: Product: UHCI Host Controller
usb usb3: Manufacturer: Linux 2.6.25.11-60.fc8 uhci_hcd
usb usb3: SerialNumber: 0000:00:10.1
ACPI: PCI Interrupt 0000:00:10.2[B] -> GSI 21 (level, low) -> IRQ 21
uhci_hcd 0000:00:10.2: UHCI Host Controller
uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:10.2: irq 21, io base 0x0000e000
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb4: Product: UHCI Host Controller
usb usb4: Manufacturer: Linux 2.6.25.11-60.fc8 uhci_hcd
usb usb4: SerialNumber: 0000:00:10.2
ACPI: PCI Interrupt 0000:00:10.3[B] -> GSI 21 (level, low) -> IRQ 21
uhci_hcd 0000:00:10.3: UHCI Host Controller
uhci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:10.3: irq 21, io base 0x0000e400
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb5: Product: UHCI Host Controller
usb usb5: Manufacturer: Linux 2.6.25.11-60.fc8 uhci_hcd
usb usb5: SerialNumber: 0000:00:10.3
SCSI subsystem initialized
Driver 'sd' needs updating - please use bus_type methods
libata version 3.00 loaded.
ACPI: PCI Interrupt 0000:00:0d.0[A] -> GSI 18 (level, low) -> IRQ 18
scsi0 : pata_pdc202xx_old
scsi1 : pata_pdc202xx_old
ata1: PATA max UDMA/100 cmd 0xa800 ctl 0xa400 bmdma 0x9400 irq 18
ata2: PATA max UDMA/100 cmd 0xa000 ctl 0x9800 bmdma 0x9408 irq 18
usb 2-2: new low speed USB device using uhci_hcd and address 2
ata1.00: ATA-7: Maxtor 6Y080L0, YAR41BW0, max UDMA/133
ata1.00: 160086528 sectors, multi 16: LBA
ata1.01: ATA-6: WDC WD2500JB-98GVA0, 08.02D08, max UDMA/100
ata1.01: 488397168 sectors, multi 16: LBA48
ata1.00: configured for UDMA/100
ata1.01: configured for UDMA/100
usb 2-2: configuration #1 chosen from 1 choice
input: Logitech USB Receiver as /class/input/input2
input,hidraw0: USB HID v1.10 Mouse [Logitech USB Receiver] on
usb-0000:00:10.0-2
usb 2-2: New USB device found, idVendor=046d, idProduct=c50d
usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-2: Product: USB Receiver
usb 2-2: Manufacturer: Logitech
scsi 0:0:0:0: Direct-Access ATA Maxtor 6Y080L0 YAR4 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 160086528 512-byte hardware sectors (81964 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 0:0:0:0: [sda] 160086528 512-byte hardware sectors (81964 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sda: sda1 sda2
sd 0:0:0:0: [sda] Attached SCSI disk
scsi 0:0:1:0: Direct-Access ATA WDC WD2500JB-98G 08.0 PQ: 0 ANSI: 5
sd 0:0:1:0: [sdb] 488397168 512-byte hardware sectors (250059 MB)
sd 0:0:1:0: [sdb] Write Protect is off
sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00
sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 0:0:1:0: [sdb] 488397168 512-byte hardware sectors (250059 MB)
sd 0:0:1:0: [sdb] Write Protect is off
sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00
sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sdb: sdb1
sd 0:0:1:0: [sdb] Attached SCSI disk
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised:
dm-devel@redhat.com
sata_via 0000:00:0f.0: version 2.3
ACPI: PCI Interrupt 0000:00:0f.0[B] -> GSI 20 (level, low) -> IRQ 20
sata_via 0000:00:0f.0: routed to hard irq line 10
scsi2 : sata_via
scsi3 : sata_via
ata3: SATA max UDMA/133 cmd 0xd000 ctl 0xc800 bmdma 0xb800 irq 20
ata4: SATA max UDMA/133 cmd 0xc400 ctl 0xc000 bmdma 0xb808 irq 20
ata3: SATA link down 1.5 Gbps (SStatus 0 SControl 300)
ata4: SATA link down 1.5 Gbps (SStatus 0 SControl 300)
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
SELinux: Disabled at runtime.
SELinux: Unregistering netfilter hooks
type=1404 audit(1217880948.630:2): selinux=0 auid=4294967295 ses=4294967295
input: PC Speaker as /class/input/input3
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
ACPI: PCI Interrupt 0000:00:0f.1[A] -> GSI 20 (level, low) -> IRQ 20
ACPI: PCI interrupt for device 0000:00:0f.1 disabled
8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
8139cp 0000:00:0e.0: This (id 10ec:8139 rev 10) is not an 8139C+
compatible chip
8139cp 0000:00:0e.0: Try the "8139too" driver instead.
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:0:1:0: Attached scsi generic sg1 type 0
8139too Fast Ethernet driver 0.9.28
ACPI: PCI Interrupt 0000:00:0e.0[A] -> GSI 19 (level, low) -> IRQ 19
eth0: RealTek RTL8139 at 0xffffc200004ec000, 00:50:fc:f4:c8:59, IRQ 19
eth0: Identified 8139 chip type 'RTL-8100B/8139D'
parport_pc 00:07: reported by Plug and Play ACPI
parport0: PC-style at 0x378, irq 7 [PCSPP]
input: Power Button (FF) as /class/input/input4
ACPI: Power Button (FF) [PWRF]
input: Power Button (CM) as /class/input/input5
ACPI: Power Button (CM) [PWRB]
input: Sleep Button (CM) as /class/input/input6
ACPI: Sleep Button (CM) [SLPB]
pata_via 0000:00:0f.1: version 0.3.3
ACPI: PCI Interrupt 0000:00:0f.1[A] -> GSI 20 (level, low) -> IRQ 20
scsi4 : pata_via
scsi5 : pata_via
ata5: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xfc00 irq 14
ata6: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xfc08 irq 15
ata5.00: ATA-4: QUANTUM FIREBALL CR13.0A, A5U.1200, max UDMA/66
ata5.00: 25429824 sectors, multi 16: LBA
ata5.01: ATAPI: GCR-8523B, LNUX, max MWDMA2
ata5.00: limited to UDMA/33 due to 40-wire cable
ata5.00: configured for UDMA/33
udev: renamed network interface eth0 to eth2
ata5.01: configured for MWDMA2
scsi 4:0:0:0: Direct-Access ATA QUANTUM FIREBALL A5U. PQ: 0 ANSI: 5
sd 4:0:0:0: [sdc] 25429824 512-byte hardware sectors (13020 MB)
sd 4:0:0:0: [sdc] Write Protect is off
sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 4:0:0:0: [sdc] 25429824 512-byte hardware sectors (13020 MB)
sd 4:0:0:0: [sdc] Write Protect is off
sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sdc: sdc1
sd 4:0:0:0: [sdc] Attached SCSI disk
sd 4:0:0:0: Attached scsi generic sg2 type 0
scsi 4:0:1:0: CD-ROM HL-DT-ST CD-ROM GCR-8523B LNUX PQ: 0 ANSI: 5
scsi 4:0:1:0: Attached scsi generic sg3 type 5
ACPI: PCI Interrupt 0000:00:11.5[C] -> GSI 22 (level, low) -> IRQ 22
PCI: Setting latency timer of device 0000:00:11.5 to 64
nvidia: module license 'NVIDIA' taints kernel.
ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
NVRM: loading NVIDIA UNIX x86_64 Kernel Module 173.14.12 Thu Jul 17
18:10:24 PDT 2008
PCI: Enabling device 0000:00:11.6 (0000 -> 0001)
ACPI: PCI Interrupt 0000:00:11.6[C] -> GSI 22 (level, low) -> IRQ 22
Driver 'sr' needs updating - please use bus_type methods
sr0: scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 4:0:1:0: Attached scsi CD-ROM sr0
PCI: Setting latency timer of device 0000:00:11.6 to 64
ACPI: PCI interrupt for device 0000:00:11.6 disabled
VIA 82xx Modem: probe of 0000:00:11.6 failed with error -13
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
device-mapper: multipath: version 1.0.5 loaded
loop: module loaded
EXT3 FS on dm-0, internal journal
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 1933304k swap on /dev/mapper/VolGroup00-LogVol01. Priority:-1
extents:1 across:1933304k
warning: process `kudzu' used the deprecated sysctl system call with 1.23.
powernow-k8: Found 1 AMD Athlon(tm) 64 Processor 3500+ processors (1 cpu
cores) (version 2.20.00)
powernow-k8: 0 : fid 0xe (2200 MHz), vid 0x2
powernow-k8: 1 : fid 0xc (2000 MHz), vid 0x6
powernow-k8: 2 : fid 0xa (1800 MHz), vid 0xa
powernow-k8: 3 : fid 0x2 (1000 MHz), vid 0x12
ip6_tables: (C) 2000-2006 Netfilter Core Team
nf_conntrack version 0.5.0 (8192 buckets, 32768 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
Marking TSC unstable due to cpufreq changes
Clocksource tsc unstable (delta = -64000180 ns)
eth2: link up, 100Mbps, full-duplex, lpa 0x45E1
fuse init (API version 7.9)
warning: `dbus-daemon' uses 32-bit capabilities (legacy support in use)
eth2: no IPv6 routers present
agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
--
The only way to keep your health is to eat what you don't want, drink
what you don't like, and do what you'd rather not.
-- Mark Twain
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3254 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Problems with disk + network on 2.6.25.11-60.fc8
2008-08-04 20:31 ` David Stuart
@ 2008-08-04 20:44 ` Alan Cox
2008-08-04 23:27 ` David Stuart
0 siblings, 1 reply; 9+ messages in thread
From: Alan Cox @ 2008-08-04 20:44 UTC (permalink / raw)
To: David Stuart; +Cc: linux-kernel
Ok so the pdc202xx_old hardware flakes out when you have very high
network load (I'd guess in fact very high bus traffic).
The actual log is the disk I/O timing out, then the drive being busy
(probably due to the timeout and a DMA transfer getting stuck). We reset
it and carry on.
Libata happens to log this a lot more visibly than old kernels which is
useful but does mean people sometimes don't notice.
The rest then fits - the freeze I'd expect as we block I/O while trying
to get the drive back.
Doubt the Nvidia module is involved as I'd then expect problems under
high graphical load but you can certainly test that. I don't suppose
you've got a spare PCI network card you could try instead to see if it is
the network card bits ?
Alan
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Problems with disk + network on 2.6.25.11-60.fc8
2008-08-04 23:27 ` David Stuart
@ 2008-08-04 23:13 ` Alan Cox
2008-08-04 23:58 ` David Stuart
0 siblings, 1 reply; 9+ messages in thread
From: Alan Cox @ 2008-08-04 23:13 UTC (permalink / raw)
To: David Stuart; +Cc: linux-kernel
O> around the problem (originally I thought it was the on-board
> controller), so I have my doubts as to whether switching back would help.
>
> Nonetheless, I will give it a try again and let you know the result.
That would be great - if it makes no difference, yet high network traffic
is the key factor then it mostly eliminates bugs in the network drivers
from suspicion. At that point its time to dig deeper into the chip config.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Problems with disk + network on 2.6.25.11-60.fc8
2008-08-04 20:44 ` Alan Cox
@ 2008-08-04 23:27 ` David Stuart
2008-08-04 23:13 ` Alan Cox
0 siblings, 1 reply; 9+ messages in thread
From: David Stuart @ 2008-08-04 23:27 UTC (permalink / raw)
To: Alan Cox; +Cc: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1472 bytes --]
Alan Cox wrote:
> Ok so the pdc202xx_old hardware flakes out when you have very high
> network load (I'd guess in fact very high bus traffic).
>
> The actual log is the disk I/O timing out, then the drive being busy
> (probably due to the timeout and a DMA transfer getting stuck). We reset
> it and carry on.
>
> Libata happens to log this a lot more visibly than old kernels which is
> useful but does mean people sometimes don't notice.
>
> The rest then fits - the freeze I'd expect as we block I/O while trying
> to get the drive back.
>
> Doubt the Nvidia module is involved as I'd then expect problems under
> high graphical load but you can certainly test that. I don't suppose
> you've got a spare PCI network card you could try instead to see if it is
> the network card bits ?
>
> Alan
>
Hi Alan,
Actually I do not really have another PCI network card, but I could
switch the computer back to the other interface which is on the
motherboard (does that one function as a PCI device?). As I mentioned in
my first post, the current card I am using is an attempt to try to work
around the problem (originally I thought it was the on-board
controller), so I have my doubts as to whether switching back would help.
Nonetheless, I will give it a try again and let you know the result.
Thanks,
David
--
The only way to keep your health is to eat what you don't want, drink
what you don't like, and do what you'd rather not.
-- Mark Twain
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3254 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Problems with disk + network on 2.6.25.11-60.fc8
2008-08-04 23:13 ` Alan Cox
@ 2008-08-04 23:58 ` David Stuart
2008-08-07 1:43 ` David Stuart
0 siblings, 1 reply; 9+ messages in thread
From: David Stuart @ 2008-08-04 23:58 UTC (permalink / raw)
To: Alan Cox; +Cc: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
Alan Cox wrote:
> That would be great - if it makes no difference, yet high network traffic
> is the key factor then it mostly eliminates bugs in the network drivers
> from suspicion. At that point its time to dig deeper into the chip config.
>
Hi Alan,
So I switched back to my old on-board network card (removing the prior
card altogether from the case). I tried my test-case, which involves
downloading some big files while simultaneously running a find command.
I *was* able to reproduce the issue fairly quickly.
The key difference is that this time I was using the skge kernel module
for networking. So, I tend to agree that it is most likely not a network
driver problem.
Please let me know if there is anything further I can do to assist in
debugging.
Thanks,
David
--
The only way to keep your health is to eat what you don't want, drink
what you don't like, and do what you'd rather not.
-- Mark Twain
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3254 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Problems with disk + network on 2.6.25.11-60.fc8
2008-08-04 23:58 ` David Stuart
@ 2008-08-07 1:43 ` David Stuart
2008-08-07 10:36 ` Alan Cox
0 siblings, 1 reply; 9+ messages in thread
From: David Stuart @ 2008-08-07 1:43 UTC (permalink / raw)
To: David Stuart; +Cc: Alan Cox, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]
David Stuart wrote:
> Alan Cox wrote:
>> That would be great - if it makes no difference, yet high network
>> traffic
>> is the key factor then it mostly eliminates bugs in the network drivers
>> from suspicion. At that point its time to dig deeper into the chip
>> config.
>>
>
> Hi Alan,
>
> So I switched back to my old on-board network card (removing the prior
> card altogether from the case). I tried my test-case, which involves
> downloading some big files while simultaneously running a find command.
>
> I *was* able to reproduce the issue fairly quickly.
>
> The key difference is that this time I was using the skge kernel
> module for networking. So, I tend to agree that it is most likely not
> a network driver problem.
Hello,
It occurs to me that you might be implying there is some "chip config"
that I can retrieve and give to you. Is there anything I can/should do
in order to give you more information, or is this pretty much out of my
hands at this point?
Should I be filing a bug report for this?
--
The only way to keep your health is to eat what you don't want, drink
what you don't like, and do what you'd rather not.
-- Mark Twain
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3254 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Problems with disk + network on 2.6.25.11-60.fc8
2008-08-07 1:43 ` David Stuart
@ 2008-08-07 10:36 ` Alan Cox
0 siblings, 0 replies; 9+ messages in thread
From: Alan Cox @ 2008-08-07 10:36 UTC (permalink / raw)
To: David Stuart; +Cc: David Stuart, linux-kernel
> It occurs to me that you might be implying there is some "chip config"
> that I can retrieve and give to you. Is there anything I can/should do
> in order to give you more information, or is this pretty much out of my
> hands at this point?
There are two things you can play with. One is the UDMA burst mode on the
chip which should be getting set, the other is PCI latencies (which the
BIOS should have set up but you can play with)
> Should I be filing a bug report for this?
Probably a good idea
Next things to try are
1. edit drivers/ata/pata_pdc202xx_old.c
after the line
iowrite8(burst | 0x01, bmdma + 0x1f);
add
printk(KERN_ERR "BURST was %02X\n", burst);
build/install/boot that kernel and see what it says.
The second (sledgehammer) approach would be to use setpci to set the
LATENCY_TIMER value on the pdc202xx_old and network card differently.
Alan
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2008-08-07 13:15 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-08-04 17:39 Problems with disk + network on 2.6.25.11-60.fc8 David Stuart
2008-08-04 17:42 ` Alan Cox
2008-08-04 20:31 ` David Stuart
2008-08-04 20:44 ` Alan Cox
2008-08-04 23:27 ` David Stuart
2008-08-04 23:13 ` Alan Cox
2008-08-04 23:58 ` David Stuart
2008-08-07 1:43 ` David Stuart
2008-08-07 10:36 ` Alan Cox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox