[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: IDE disks in Amigas




Geert Uytterhoeven wrote:

Repost to the list as well...

>> Under AmigaOS the performance of the IDE disk was "OK", but under Linux
it's
>> quite slow. hdparm shows all options OFF and trying to set DMA to on
resulted in an error. Is there a reason to not being able to set DMA on
IDE
>> for Amigas or is it a bug in hdparm or something else?
> The Amiga IDE hardware cannot do DMA, only PIO.

*yawn*

> Setting the multiple sector count (`hdparm -m') may help, though.

Will try...

> What figures do you get from `hdparm -tT /dev/hda'?

elgar:~# hdparm -tT /dev/hda

/dev/hda:
 Timing cached reads:    26 MB in  2.01 seconds =  12.93 MB/sec
 Timing buffered disk reads:
Message from syslogd@elgar at Fri Apr  4 12:44:15 2008 ...
elgar kernel: Bad page state in process 'hdparm'

Message from syslogd@elgar at Fri Apr  4 12:44:15 2008 ...
elgar kernel: page:002f0f34 flags:0x00000004 mapping:00000000
mapcount:-2147483648 count:0

Message from syslogd@elgar at Fri Apr  4 12:44:15 2008 ...
elgar kernel: Trying to fix it up, but a reboot is needed

Message from syslogd@elgar at Fri Apr  4 12:44:15 2008 ...
elgar kernel: Backtrace:
  4 MB in  4.06 seconds = 1008.11 kB/sec


Apr  4 12:44:15 elgar kernel: Bad page state in process 'hdparm'
Apr  4 12:44:15 elgar kernel: page:002f0f34 flags:0x00000004
mapping:00000000 ma
pcount:-2147483648 count:0
Apr  4 12:44:15 elgar kernel: Trying to fix it up, but a reboot is needed
Apr  4 12:44:15 elgar kernel: Backtrace:
Apr  4 12:44:15 elgar kernel: Call Trace: [<0004766e>] bad_page+0x52/0x76
Apr  4 12:44:15 elgar kernel:  [<0004791c>]
get_page_from_freelist+0x28a/0x328
Apr  4 12:44:15 elgar kernel:  [<000201d0>] _060_fpsp_effadd+0xca8c/0xd518
Apr  4 12:44:15 elgar kernel:  [<0004827c>] __alloc_pages+0x4a/0x262 Apr 
4 12:44:15 elgar kernel:  [<000201d0>] _060_fpsp_effadd+0xca8c/0xd518 Apr 
4 12:44:15 elgar last message repeated 2 times
Apr  4 12:44:15 elgar kernel:  [<00049c62>]
__do_page_cache_readahead+0x128/0x2a
6
Apr  4 12:44:16 elgar kernel:  [<000201d0>] _060_fpsp_effadd+0xca8c/0xd518
Apr  4 12:44:16 elgar kernel:  [<000438de>] find_get_page+0x0/0x50 Apr  4
12:44:16 elgar kernel:  [<00003ebe>] buserr_c+0x4e2/0x6a4
Apr  4 12:44:16 elgar kernel:  [<00001000>] _stext+0x0/0x1000
Apr  4 12:44:16 elgar kernel:  [<00160000>]
NCR_700_queuecommand+0x400/0x47e Apr  4 12:44:16 elgar kernel: 
[<000438de>] find_get_page+0x0/0x50 Apr  4 12:44:16 elgar kernel: 
[<00049fce>] ondemand_readahead+0xa8/0xfe Apr  4 12:44:16 elgar kernel: 
[<00001000>] _stext+0x0/0x1000
Apr  4 12:44:16 elgar kernel:  [<00001000>] _stext+0x0/0x1000
Apr  4 12:44:16 elgar kernel:  [<0004a07c>]
page_cache_async_readahead+0x58/0x6c
Apr  4 12:44:16 elgar kernel:  [<000440ac>]
do_generic_mapping_read+0x170/0x574
Apr  4 12:44:16 elgar kernel:  [<00045a50>]
generic_file_aio_read+0x9c/0x14c Apr  4 12:44:16 elgar kernel: 
[<000460a4>] file_read_actor+0x0/0xc8 Apr  4 12:44:16 elgar kernel: 
[<000a1000>] ext3_truncate+0x186/0x9f6 Apr  4 12:44:16 elgar kernel: 
[<0015f000>]
process_script_interrupt+0xea0/0x133
8
Apr  4 12:44:16 elgar kernel:  [<00061090>] do_sync_read+0xa2/0x106 Apr  4
12:44:16 elgar kernel:  [<00020c5c>] _060_isp_done+0x0/0x26 Apr  4
12:44:16 elgar kernel:  [<0001ffff>] _060_fpsp_effadd+0xc8bb/0xd518 Apr  4
12:44:16 elgar kernel:  [<000202b0>] _060_fpsp_effadd+0xcb6c/0xd518 Apr  4
12:44:16 elgar kernel:  [<0000b400>] uni_getop+0x1f8/0x40c
Apr  4 12:44:16 elgar kernel:  [<00087d80>] sys_epoll_wait+0x220/0x39c Apr
 4 12:44:16 elgar kernel:  [<0000131d>] _stext+0x31d/0x1000
Apr  4 12:44:16 elgar kernel:  [<0000131d>] _stext+0x31d/0x1000
Apr  4 12:44:16 elgar kernel:  [<000618d4>] vfs_read+0x7a/0x106
Apr  4 12:44:16 elgar kernel:  [<0000131d>] _stext+0x31d/0x1000
Apr  4 12:44:16 elgar kernel:  [<00061bdc>] sys_read+0x42/0x7c
Apr  4 12:44:16 elgar kernel:  [<00002776>] syscall+0x8/0xc
Apr  4 12:44:16 elgar kernel:  [<0000131d>] _stext+0x31d/0x1000
Apr  4 12:44:16 elgar kernel:  [<0000c00a>] res_func+0x612/0x141a

That's with kernel 2.6.23-m68k which is running w/o problems on my other
Amigas. I get this kind of errors when I'm attaching a SCSI disk to the
SCSI module of the CyberStorm1:


00: Phase 5 Blizzard 1220/CyberStorm [Accelerator and SCSI Host Adapter]
01: Hydra Systems Amiganet [Ethernet Card]


Linux version 2.6.23-m68k (root@elgar) (gcc version 4.1.2 20061115
(prerelease)
(Debian 4.1.1-21)) #2 Fri Apr 4 04:41:32 EDT 2008
Enabling workaround for errata I14
Amiga hardware found: [A4000] VIDEO BLITTER AUDIO FLOPPY A4000_IDE
KEYBOARD MOUS
E SERIAL PARALLEL A3000_CLK CHIP_RAM PAULA LISA ALICE_PAL ZORRO3
Ignoring memory chunk at 0x7f00000:0x100000 before the first chunk


SCSI ID 7 Clk 40MHz CCF=8 TOut 167 NCR53C9XF(espfast)
esp0: FAST chip is Emulex FAS236 (family=2, version=3)
ESP: Total of 1 ESP hosts found, 1 actually in use.
scsi0 : CyberStorm SCSI
scsi 0:0:0:0: Direct-Access     IBM      DCAS-34330       S60B PQ: 0 ANSI: 2

esp0: target 0 [period 100ns offset 15 10.00MHz FAST SCSI-II]
sd 0:0:0:0: [sda] 8467200 512-byte hardware sectors (4335 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: b3 00 00 08
sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't
support DPO or FUA
sd 0:0:0:0: [sda] 8467200 512-byte hardware sectors (4335 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: b3 00 00 08
sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't
support DPO or FUA


I think I better remove that SCSI disk for now... ;)
Is there a better SCSI driver in newer kernels? I took a kernel tarball
from one of my other Amigas to reduce built time, but when 2.6.24.x gives
me a working SCSI, it's no problem to built a complete new kernel... :)

-- 
Ciao...
      Ingo




-- 
Ciao...
      Ingo



Reply to: