I get this error message when I run hdparm -Y /dev/hda, And after this,
I try to access some mounted partition:
System is a cyrix 6x86MX 200Mhz with a Microstar 5146, wich has a Sis
5513 ide chipset Kernel is a 2.4.19-rc1, but is reporducible in the last
-ac tree. So I think it may be related to my IDE chipset.
(NOTE: After the kernel prints the bug, in 2.4.19-rc1 and
2.4.19-pre8-ac3 the drive starts again, but system doesn't seems to work
with the mounted partition of the slept drive, 2.5 doesn't work neither
starts the drive...)
Perhaps this hdparm config is bad and I need to change it?:
/sbin/hdparm -c1 -A1 -a8 -d1 -m16 -p4 -u1 -W1 -X34 /dev/hda
hdparm -I /dev/hda reports:
non-removable ATA device, with non-removable media
Model Number: ST32122A
Serial Number: GJQ18658
Firmware Revision: 0.42
Standards:
Supported: 1 2
Likely used: 4
Configuration:
Logical max current
cylinders 4092 4092
heads 16 16
sectors/track 63 63
bytes/track: 0 (obsolete)
bytes/sector: 0 (obsolete)
current sector capacity: 4124736
LBA user addressable sectors = 4124736
Capabilities:
LBA, IORDY(can be disabled)
Buffer size: 128.0kB ECC bytes: 4 Queue depth: 1
Standby timer values: spec'd by Vendor
r/w multiple sector transfer: Max = 16 Current = 16
DMA: mdma0 mdma1 *mdma2 udma0 udma1 udma2
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=383ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
Power Management feature set
SMART feature set
Outputs:
In 2.4.19-rc1:
Jun 26 13:33:58 localhost kernel: hda: timeout waiting for DMA
Jun 26 13:33:58 localhost kernel: hda: ide_dma_timeout: Lets do it
again!stat = 0xd0, dma_stat = 0x20 Jun 26 13:33:58 localhost kernel:
hda: DMA disabled Jun 26 13:33:58 localhost kernel: hda:
ide_set_handler: handler not null; old=c0193690, new=c0198744 Jun 26
13:33:58 localhost kernel: bug: kernel timer added twice at c0193511.
In 2.4.19-pre8-ac3:
Jun 27 15:38:12 localhost kernel: hda: timeout waiting for DMA
Jun 27 15:38:12 localhost kernel: hda: ide_dma_timeout: Lets do it
again!stat = 0xd0, dma_stat = 0x20 Jun 27 15:38:12 localhost kernel:
hda: DMA disabled Jun 27 15:38:12 localhost kernel: hda:
ide_set_handler: handler not null; old=c0197a40, new=c0195234 Jun 27
15:38:12 localhost kernel: bug: kernel timer added twice at c01978b1.
Jun 27 15:38:12 localhost kernel: hda: ide_set_handler: handler not
null; old=c0195234, new=c01952a0 Jun 27 15:38:12 localhost kernel: bug:
kernel timer added twice at c01978b1.
In 2.5.19 (I'll test newer kernels...if they work)
Jun 27 15:42:52 localhost kernel: ATA: UDMA timeout occured hda!
Jun 27 15:42:52 localhost kernel: hda: status timeout: status=0xd0 {
Busy DriveReady SeekComplete } Jun 27 15:42:52 localhost kernel: hda:
drive not ready for command Jun 27 15:42:52 localhost kernel: hda:
status timeout: status=0xd0 { Busy DriveReady SeekComplete } Jun 27
15:42:52 localhost kernel: hda: drive not ready for command Jun 27
15:42:52 localhost kernel: hda: status timeout: status=0xd0 { Busy
DriveReady SeekComplete } Jun 27 15:42:52 localhost kernel: end_request:
I/O error, dev 03:00, sector 56111 Jun 27 15:42:52 localhost kernel:
Buffer I/O error on device ide0(3,1), logical block 7006 Jun 27 15:42:52
localhost kernel: hda: drive not ready for command Jun 27 15:42:52
localhost kernel: hda: status timeout: status=0xd0 { Busy DriveReady
SeekComplete } Jun 27 15:42:52 localhost kernel: hda: drive not ready
for command Jun 27 15:42:52 localhost kernel: hda: status timeout:
status=0xd0 { Busy DriveReady SeekComplete } Jun 27 15:42:54 localhost
kernel: hda: drive not ready for command Jun 27 15:42:54 localhost
kernel: hda: status timeout: status=0xd0 { Busy DriveReady SeekComplete
} Jun 27 15:42:54 localhost kernel: end_request: I/O error, dev 03:00,
sector 56119 Jun 27 15:42:54 localhost kernel: Buffer I/O error on
device ide0(3,1), logical block 7007 Jun 27 15:42:54 localhost kernel:
hda: drive not ready for command Jun 27 15:42:54 localhost kernel: hda:
status timeout: status=0xd0 { Busy DriveReady SeekComplete } Jun 27
15:42:54 localhost kernel: hda: drive not ready for command Jun 27
15:42:54 localhost kernel: hda: status timeout: status=0xd0 { Busy
DriveReady SeekComplete } Jun 27 15:42:54 localhost kernel: hda: drive
not ready for command Jun 27 15:42:54 localhost kernel: hda: status
timeout: status=0xd0 { Busy DriveReady SeekComplete } Jun 27 15:42:54
localhost kernel: end_request: I/O error, dev 03:00, sector 56127 Jun 27
15:42:56 localhost kernel: Buffer I/O error on device ide0(3,1), logical
block 7008 Jun 27 15:42:56 localhost kernel: hda: drive not ready for
command Jun 27 15:42:56 localhost kernel: journal-601, buffer write
failed Jun 27 15:42:56 localhost kernel: kernel BUG at prints.c:336!
Jun 27 15:42:56 localhost kernel: invalid operand: 0000
Jun 27 15:42:56 localhost kernel: CPU: 0
Jun 27 15:42:56 localhost kernel: EIP: 0010:[reiserfs_panic+41/80]
Not tainted Jun 27 15:42:56 localhost kernel: EFLAGS: 00010282
Jun 27 15:42:56 localhost kernel: eax: 00000024 ebx: c023a880 ecx:
ffffffdc edx: 00000001 Jun 27 15:42:56 localhost kernel: esi: c1e0ec00
edi: 00000000 ebp: c1e3c7c0 esp: c1ffde7c Jun 27 15:42:56
localhost kernel: ds: 0018 es: 0018 ss: 0018 Jun 27 15:42:56
localhost kernel: Process pdflush (pid: 6, threadinfo=c1ffc000
task=c1ffa060) Jun 27 15:42:56 localhost kernel: Stack: c0238a0e
c02ca760 c023a880 c1ffdea0 c1e0ec00 c28bb134 c0171189 c1e0ec00 Jun 27
15:42:56 localhost kernel: c023a880 c1e0ec00 00000001 c1e0ec00
00000000 c28bb0b4 c159a000 c1e3c7c0 Jun 27 15:42:56 localhost kernel:
c28bb168 c28bb15c 00000004 00000000 c06c98a0 c0175386 c1e0ec00
c28bb134 Jun 27 15:42:56 localhost kernel: Call Trace:
[flush_commit_list+821/1092] [do_journal_end+2102/2940]
[flush_old_commits+343/368] [rJun 27 15:42:57 localhost kernel:
[wb_kupdate+9/128] [schedule+579/696] [__pdflush+276/440]
[pdflush+11/20] [wb_kupdate+0/128] [kJun 27 15:42:57 localhost kernel:
Jun 27 15:42:57 localhost kernel: Code: 0f 0b 50 01 14 8a 23 c0 68 60 a7
2c c0 b8 1d 8a 23 c0 85 f6 Jun 27 15:42:57 localhost kernel: <6>note:
pdflush[6] exited with preempt_count 1
Message from syslogd@localhost at Thu Jun 27 15:42:56 2002 ...
localhost kernel: journal-601, buffer write failed
This is the output of lspci:
Root@diego:~# lspci -v
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 5571 (rev 01)
Flags: bus master, medium devsel, latency 255
00:01.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513 (rev
01) Flags: bus master, medium devsel, latency 0
00:01.1 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev
c1) (prog-if 8a [Master SecP PriP]) Subsystem: Unknown device
0040:0000 Flags: bus master, fast devsel, latency 32, IRQ 14
I/O ports at <ignored>
I/O ports at <ignored>
I/O ports at <ignored>
I/O ports at <ignored>
I/O ports at 1000 [size=16]
00:01.2 USB Controller: Silicon Integrated Systems [SiS] 7001 (rev e0)
(prog-if 10 [OHCI]) Flags: bus master, medium devsel, latency 32,
IRQ 10 Memory at e4000000 (32-bit, non-prefetchable) [size=4K]
00:0f.0 VGA compatible controller: 3Dfx Interactive, Inc. Voodoo 3 (rev
01) (prog-if 00 [VGA]) Subsystem: 3Dfx Interactive, Inc.: Unknown
device 0057 Flags: fast devsel, IRQ 11
Memory at e0000000 (32-bit, non-prefetchable) [size=32M]
Memory at e2000000 (32-bit, prefetchable) [size=32M]
I/O ports at 6000 [size=256]
Expansion ROM at <unassigned> [disabled] [size=64K]
Capabilities: [60] Power Management version 1
root@diego:~#
and .config is attached.
Diego Calleja
On Thursday 27 June 2002 21:28, Diego Calleja wrote:
> I get this error message when I run hdparm -Y /dev/hda, And after this,
> I try to access some mounted partition:
<snip/>
from the hdparm manual
-Y Force an IDE drive to immediately enter the lowest power consumption
sleep mode, causing it to shut down completely. A hard or soft reset is
required before the drive can be accessed again (the Linux IDE driver
will automatically handle issuing a reset if/when needed). The current
power mode status can be checked using the -C flag.
so - you need a hard or soft reset to go on ...
roy
--
Roy Sigurd Karlsbakk, Datavaktmester
Computers are like air conditioners.
They stop working when you open Windows.
Diego Calleja wrote:
>I get this error message when I run hdparm -Y /dev/hda, And after this,
>I try to access some mounted partition:
>
>System is a cyrix 6x86MX 200Mhz with a Microstar 5146, wich has a Sis
>5513 ide chipset Kernel is a 2.4.19-rc1, but is reporducible in the last
>-ac tree. So I think it may be related to my IDE chipset.
>
>(NOTE: After the kernel prints the bug, in 2.4.19-rc1 and
>2.4.19-pre8-ac3 the drive starts again, but system doesn't seems to work
>with the mounted partition of the slept drive, 2.5 doesn't work neither
>starts the drive...)
>
>
>
1/ SiS5571 is not in the lookup table used to find the chipset
capabilities. That shouldn't pose problem as from what I could gather
from the web this is a basic EIDE chipset (ATA16 support only) and every
unknown chipset is configured as an ATA16 capable chipset.
2/ timings might be messed up because of the FSB used (75MHz instead of
66MHz) on your configuration.
If you can, underclock your mainboard to 66MHz and see what happens. If
it solves your problem, then dynamically computing timings from the FSB
(in my TODO list but behind ATA133 support) will eventually solve your
problem. Until then you could modify the timings by hand (I could
provide you a patch for your specific configuration).
--
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
On Fri, 28 Jun 2002 12:20:06 +0200
Lionel Bouton <[email protected]> escribi?:
> 2/ timings might be messed up because of the FSB used (75MHz instead
> of 66MHz) on your configuration.
>
> If you can, underclock your mainboard to 66MHz and see what happens.
> If it solves your problem, then dynamically computing timings from the
> FSB (in my TODO list but behind ATA133 support) will eventually solve
> your problem. Until then you could modify the timings by hand (I could
> provide you a patch for your specific configuration).
My mainboard supports 75 mhz of FSB, but strangely, the system can't
boot. The bios stops just before printing the message that says that a
cdrom has been detected. So I'm using 66 mhz FSB.
Diego Calleja
On Mon, 1 Jul 2002 18:44:26 -0400 (EDT)
Mark Hahn <[email protected]> escribi?:
>
> that's a pretty odd device DID. is this a pretty old chipset?
> does lspci -vx show 0x1039:0x5513 as this device's vid:did?
> if so, it should really work with recent kernels, assuming they're
> compiled sanely. have you done the .config yourself, and if so,
> do you have CONFIG_BLK_DEV_SIS5513 and CONFIG_IDEDMA_PCI_AUTO:?
lspci -vx:
00:01.1 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev
c1) (prog-if 8a [Master SecP PriP]) Subsystem: Unknown device 0040:0000
Flags: bus master, fast devsel, latency 32, IRQ 14
I/O ports at <ignored>
I/O ports at <ignored>
I/O ports at <ignored>
I/O ports at <ignored>
I/O ports at 1000 [size=16]
00: 39 10 13 55 07 00 00 00 c1 8a 01 01 00 20 80 00
10: f1 01 00 00 f5 03 00 00 71 01 00 00 75 03 00 00
20: 01 10 00 00 00 00 00 00 00 00 00 00 40 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 0e 01 00 00
CONFIG_BLK_DEV_SIS5513 and CONFIG_IDEDMA_PCI_AUTO are set.
I remember a thing, a message i get on every boot, now i realise why my
ide chipset doesn't work well:(I've cc-ed all people again so they can
read this)
PCI: PCI BIOS revision 2.10 entry at 0xfb3b0, last bus=0
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Cannot allocate resource region 4 of device 00:01.1
-->00:01.1 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
(rev c1) (prog-if 8a [Master SecP PriP])
I guess the matter is here? Where came this error from?
Diego Calleja