Does this log look OK? My Empeg has been working fine, no problems, but I see in the log a bunch of read and writes to registers on the IDE interface that don't match. It looks like there's a stuck bit, but the unit works fine. I'm totally confused...

JeffreyB


empeg-car bootstrap v1.02 20001106 ([email protected])
If there is anyone present who wants to upgrade the flash, let them speak now,
or forever hold their peace...it seems not. Let fly the Penguins of Linux!

e000 v1.04
Copying kernel...
Calling linux kernel...
Uncompressing Linux..................................... done, booting the kernel.

Linux version 2.2.17-rmk5-np17-empeg52-hijack-v464 ([email protected]) (gcc version 2.95.3 20010315 (release)) #2 Fri Oct 27 01:00:29 EDT 2006

Processor: Intel StrongARM-1100 revision 11

Checking for extra DRAM:

c1000000: wrote ffffffff, read e28cc001

NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.

empeg-car player (hardware revision 9, serial number 30102985) 16MB DRAM

Command line: mem=16m

Calibrating delay loop... 207.67 BogoMIPS

Memory: 15008k/16M available (988k code, 20k reserved, 364k data, 4k init)

Dentry hash table entries: 2048 (order 2, 16k)

Buffer cache hash table entries: 16384 (order 4, 64k)

Page cache hash table entries: 4096 (order 2, 16k)

POSIX conformance testing by UNIFIX

Linux NET4.0 for Linux 2.2

Based upon Swansea University Computer Society NET3.039

NET4: Linux TCP/IP 1.0 for NET4.0

IP Protocols: ICMP, UDP, TCP

TCP: Hash tables configured (ehash 16384 bhash 16384)

IrDA (tm) Protocols for Linux-2.2 (Dag Brattli)

Starting kswapd v 1.5

SA1100 serial driver version 4.27 with no serial options enabled

ttyS00 at 0xf8010000 (irq = 15) is a SA1100 UART

ttyS01 at 0xf8050000 (irq = 17) is a SA1100 UART

ttyS02 at 0xf8030000 (irq = 16) is a SA1100 UART

Signature is 20706d65 'emp '

Found custom animation at offset 0x9bb84

Tuner: loopback=0, ID=-1

empeg display initialised.

empeg dsp audio initialised

empeg dsp mixer initialised

empeg dsp initialised

empeg audio-in initialised, CS4231A revision a0

empeg remote control/panel button initialised.

empeg usb initialised, PDIUSBD12 id 1012

empeg state support initialised 0089/88c1 (save to d0005e80).

empeg RDS driver initialised

empeg power-pic driver initialised (first boot)

RAM disk driver initialized: 16 RAM disks of 4096K size

empeg single channel IDE

Probing primary interface...

ide_data_test: wrote 0x0000 read 0xff80

ide_data_test: wrote 0xffff read 0xff80

ide_data_test: wrote 0xaaaa read 0xaa80

ide_data_test: wrote 0x5555 read 0x5580

ide_data_test: wrote 0x0000 read 0xff80

ide_data_test: wrote 0xffff read 0xff80

ide_data_test: wrote 0xaaaa read 0xaa80

ide_data_test: wrote 0x5555 read 0x5580

ide_data_test: wrote 0x0000 read 0xff80

ide_data_test: wrote 0xffff read 0xff80

ide_data_test: wrote 0xaaaa read 0xaa80

ide_data_test: wrote 0x5555 read 0x5580

ide_data_test: wrote 0x0000 read 0xff00

ide_data_test: wrote 0xffff read 0xff00

ide_data_test: wrote 0xaaaa read 0xaa00

ide_data_test: wrote 0x5555 read 0x5500

ide_data_test: wrote 0x0000 read 0xff00

ide_data_test: wrote 0xffff read 0xff00

ide_data_test: wrote 0xaaaa read 0xaa00

ide_data_test: wrote 0x5555 read 0x5500

hda: ST9100823A, ATA DISK drive

ide_data_test: wrote 0x0000 read 0xffa5

ide_data_test: wrote 0xffff read 0xffa5

ide_data_test: wrote 0xaaaa read 0xaaa5

ide_data_test: wrote 0x5555 read 0x55a5

hda: ST9100823A, ATA DISK drive

ide_data_test: wrote 0x0000 read 0xffa5

ide_data_test: wrote 0xffff read 0xffa5

ide_data_test: wrote 0xaaaa read 0xaaa5

ide_data_test: wrote 0x5555 read 0x55a5

hda: ST9100823A, ATA DISK drive

ide_data_test: wrote 0x0000 read 0xffa5

ide_data_test: wrote 0xffff read 0xffa5

ide_data_test: wrote 0xaaaa read 0xaaa5

ide_data_test: wrote 0x5555 read 0x55a5

hda: ST9100823A, ATA DISK drive

ide_data_test: wrote 0x0000 read 0xffa5

ide_data_test: wrote 0xffff read 0xffa5

ide_data_test: wrote 0xaaaa read 0xaaa5

ide_data_test: wrote 0x5555 read 0x55a5

hda: ST9100823A, ATA DISK drive

ide_data_test: wrote 0x0000 read 0xffa5

ide_data_test: wrote 0xffff read 0xffa5

ide_data_test: wrote 0xaaaa read 0xaaa5

ide_data_test: wrote 0x5555 read 0x55a5

hda: ST9100823A, ATA DISK drive

ide0 at 0x000-0x007,0x038 on irq 6

hda: ST9100823A, 95396MB w/8192kB Cache, CHS=12161/255/63

empeg-flash driver initialized

smc chip id/revision 0x3349

smc9194.c:v0.12 03/06/96 by Erik Stahlman ([email protected])


SMC9194: SMC91C94(r:9) at 0x4008000 IRQ:7 INTF:TP MEM:6144b MAC 00:02:d7:26:0b:a9

Partition check:

hda: hda1 < hda5 hda6 > hda2 hda3 hda4

RAMDISK: ext2 filesystem found at block 0

RAMDISK: Loading 320 blocks [1 disk] into ram disk... | / - \ | / - \ | / - \ | / - \ | / - \ done.

VFS: Mounted root (ext2 filesystem).
empeg-pump v0.03 (19980601)
Press Ctrl-A to enter pump...VFS: Mounted root (ext2 filesystem) readonly.

change_root: old root has d_count=1

Trying to unmount old root ... okay
Freeing unused kernel memory: 4k initempeg init 0.8
I see this is a developer image!
Mounting proc
Mounting first music partition
Tried to mount /dev/hda4 as reiserfs but got error 19
Mounting second music partition
Tried to mount /dev/hdc4 but got error 6
Error mounting partitions (possibly already mounted)
Remounting first music partition read-only
Remounting second music partition read-only
No secondary hard disk
Press 'q' now to go into development mode. You Have Zero Seconds To Comply...
Starting player
Timezone: EST

Hijack: intercepting config.ini

/drive0/var/ttsclock: getopts: `Option': not a valid identifier
Saved AC volume was 74
Volume=74
hijack: removed menu entry: "Serial Port Assignment"

khttpd: listening on port 80

kftpd: listening on port 21
player.cpp : 385:empeg-car 2.01 2004/07/06.
Prolux 4 empeg car - 2.1434 Jul 5 2004
Vcb: 0x4086d000

It's fine. The IDE messages are only meaningful when the player is obviously broken (not working).

Cheers

Thanks Mark!

Jeff

mutter, mutter

The FAQ says:

Quote:
The last four ide_data_test lines should have the same wrote and read values if things are working correctly. For example, here is a screen showing a normal 'good' boot:

Code:

---

ide_data_test: wrote 0x5555 read 0x0080
ide_data_test: wrote 0x0000 read 0x0000
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xaaaa
ide_data_test: wrote 0x5555 read 0x5555
hda: IBM-DJSA-230, ATA DISK drive

---

And yet JeffreyB has:
Code:

---

ide_data_test: wrote 0x0000 read 0xffa5
ide_data_test: wrote 0xffff read 0xffa5
ide_data_test: wrote 0xaaaa read 0xaaa5
ide_data_test: wrote 0x5555 read 0x55a5
hda: ST9100823A, ATA DISK drive

---

and both our empegs say:
Code:

---

ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xaaaa
ide_data_test: wrote 0x5555 read 0x5555
hda: FUJITSU MHL2300AT, ATA DISK drive

---

It's easy to miss the bit of the FAQ that suggests that this is only a problem if you're having HD problems.

So may I ask:
* why do I get wrote 0x0000 read 0xffff on both my machines?
* should the FAQ emphasise that ide_data_test is not an error but only a diagnostic for other symptoms. In other words don't start pulling your ide cables apart just to cure odd ide_data_test messages?

Possibly replace:

However, if you are having hard disk trouble, these messages can be used to help diagnose the problem.

with:

However, if (and only if) you are having hard disk trouble, these messages can be used to help diagnose the problem. You should not treat these messages as a problem even if the last few wrote/read pairs show different values and certainly shouldn't start playing with IDE cables (and potentially causing real damage) without real symptoms.

I read Marks posts on the subject and looked at the code in ide-probe but was none the wiser.
I also changed the udelay(1) to udelay(2) and added in an extra call to ide_data_test(drive, 0x0000) after the others.

I always get
ide_data_test: wrote 0x0000 read 0xffff
but now I get more random values between the outw() and inw() so I'm putting it back --- eek!

I reverted the udelay change and left the extra ide_data_test call.

Now I get:
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xaaaa
ide_data_test: wrote 0x5555 read 0x5555
ide_data_test: wrote 0x0000 read 0x0000

so my last 4 match so I'm happy

If our resident expert and master of all things IDE (Mark) confirms that your suggested wording for the FAQ is accurate, then I'll update it.

Mark?

Yes I know - I read it

However I didn't come straight here.... being a good boy the first thing I did when I saw this odd mismatch for real on my systems was to read the FAQ.

Then after reading the FAQ I thought I had a problem that simply hadn't tripped up the player.

In particular "if you are having hard disk trouble" came across as "if your hard disks are flakey then you may get these messages".

Then I did some research before following the FAQ suggestion of taking my empeg to bits...

Then I found this post.
And there was just this short "it's fine" message which left me a bit confused since it *looked* broken.

Then I checked all your other posts about this message.

Then I looked at the source.
Then I played a bit.

THEN I asked my followup question.

Okay?

Oh, and since I thought others may see these messages and be confused I drafted a modification to the wording - but since there's no info about this (even in the code) I thought Tony's suggestion of asking you was sensible - but since it sounds like you're feeling grumpy and it "works for me" I can just drop it.... ?

FAQ updated. Thanks BlueThing and Mark.