Sync arch/alpha/kernel/entry.S with asm/unistd.h
PATCH 1/1 Sync arch/alpha/kernel/entry.S with asm/unistd.h
This adds some (non-implemented) syscalls to entry.S with the same numbers as in asm/unistd.h
alpha/kernel/entry.S +13 -1
@@ -10,7 +10,7 @@ #define SIGCHLD 20 -#define NR_SYSCALLS 382 +#define NR_SYSCALLS 394 /* * These offsets must match with alpha_mv in <asm/machvec.h>.
@@ -1154,6 +1154,18 @@ .quad sys_readahead .quad sys_ni_syscall /* 380, sys_security */ .quad sys_tkill + .quad sys_ni_syscall /* setxattr */ + .quad sys_ni_syscall /* lsetxattr */ + .quad sys_ni_syscall /* fsetxattr */ + .quad sys_ni_syscall /* 385 getxattr */ + .quad sys_ni_syscall /* lgetxattr */ + .quad sys_ni_syscall /* fgetxattr */ + .quad sys_ni_syscall /* listxattr */ + .quad sys_ni_syscall /* llistxattr */ + .quad sys_ni_syscall /* 390 flistxattr */ + .quad sys_ni_syscall /* removexattr */ + .quad sys_ni_syscall /* lremovexattr */ + .quad sys_ni_syscall /* fremovexattr */ /* Remember to update everything, kids. */ .ifne (. - sys_call_table) - (NR_SYSCALLS * 8)
Signature · 2 lines
Måns Rullgård [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]'s
Quoted 2 lines · [email protected] (Måns Rullgård) writes:
This adds some (non-implemented) syscalls to
entry.Swith the same numbers as inasm/unistd.h
I forgot to say the patch is against 2.4.19.
Signature · 2 lines
Måns Rullgård [email protected]
Re: hpt374 misbehaving
In reply to a message not in the archiveQuoted 4 lines · [email protected] (Måns Rullgård) writes:
I'm having some trouble with an hpt374 based card, the S-ATA version. The chip is detected correctly, but after that the problems start.
hde: lost interrupt
A though just struck me. Could this be caused by the config option "IDE IRQ sharing" being unset? I don't remember if I set it, I'll have to check at home. The hpt374 is really two logical devices in a single chip, isn't it?
Signature · 2 lines
Måns Rullgård [email protected]
hpt374 misbehaving
I'm having some trouble with an hpt374 based card, the S-ATA version. The chip is detected correctly, but after that the problems start.
Here's what linux 2.5.62 has to say:
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
HPT374: IDE controller at PCI slot 01:0a.0
HPT374: chipset revision 7
HPT374: not 100% native mode: will probe irqs later
HPT37X: using 33MHz PCI clock
ide2: BM-DMA at 0x8400-0x8407, BIOS settings: hde:pio, hdf:pio
ide3: BM-DMA at 0x8408-0x840f, BIOS settings: hdg:pio, hdh:pio
HPT37X: using 33MHz PCI clock
ide4: BM-DMA at 0x8800-0x8807, BIOS settings: hdi:pio, hdj:pio
ide5: BM-DMA at 0x8808-0x880f, BIOS settings: hdk:pio, hdl:piohde: ST38641A, ATA DISK drive
hde: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hde: set_drive_speed_status: error=0x04 { DriveStatusError } ide2 at 0x8c00-0x8c07,0x8c22 on irq 44
hda: TOSHIBA CD-ROM XM-5702B, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hde: lost interrupt
hde: lost interrupt
hde: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hde: task_no_data_intr: error=0x04 { DriveStatusError }
hde: 16514064 sectors (8455 MB) w/128KiB Cache, CHS=16383/16/63
/dev/ide/host2/bus0/target0/lun0: p1 p2
After this, booting proceeds normally (from other devices). If I try to access the disk, more 'hde: lost interrupt' messages show up in the log. The disk is inaccessible.
Using linux 2.4.21-pre4, I get these messages:
HPT374: IDE controller at PCI slot 01:0a.0
HPT374: chipset revision 7
HPT374: not 100% native mode: will probe irqs later
HPT37X: using 33MHz PCI clock
ide2: BM-DMA at 0x8400-0x8407, BIOS settings: hde:pio, hdf:pio
ide3: BM-DMA at 0x8408-0x840f, BIOS settings: hdg:pio, hdh:pio
HPT37X: using 33MHz PCI clock
ide4: BM-DMA at 0x8800-0x8807, BIOS settings: hdi:pio, hdj:pio
ide5: BM-DMA at 0x8808-0x880f, BIOS settings: hdk:pio, hdl:piohda: TOSHIBA CD-ROM XM-5702B, ATAPI CD/DVD-ROM drive
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
hde: ST38641A, ATA DISK drive
blk: queue fffffc0000550410, no I/O memory limit
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide2 at 0x8c00-0x8c07,0x8c22 on irq 44
hde: lost interrupt
hde: lost interrupt
hde: lost interrupt
hde: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hde: task_no_data_intr: error=0x04 { DriveStatusError }
hde: 16514064 sectors (8455 MB) w/128KiB Cache, CHS=16383/16/63, UDMA(33) Partition check:
/dev/ide/host2/bus0/target0/lun0:<3>hde: lost interrupt
p1 p3
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 1024 buckets, 8Kbytes
TCP: Hash tables configured (established 16384 bind 16384)
IP-Config: Complete:
device=eth0, addr=192.168.42.3, mask=255.255.255.0, gw=192.168.42.2,
host=192.168.42.3, domain=, nis-domain=(none),
bootserver=192.168.42.2, rootserver=192.168.42.2, rootpath=NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 192.168.42.2
Looking up port of RPC 100005/1 on 192.168.42.2
VFS: Mounted root (nfs filesystem).
Mounted devfs on /dev
Freeing unused kernel memory: 336k freed
eth0: Setting full-duplex based on MII#5 link partner capability of 45e1.
hde: lost interrupt
hde: dma_timer_expiry: dma status == 0x21
hde: timeout waiting for DMA
hde: timeout waiting for DMA
hde: (__ide_dma_test_irq) called while not waiting
hde: status timeout: status=0xd0 { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xd0
hde: status timeout: status=0xd0 { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xd0end_request: I/O error, dev 21:00 (hde), sector 0end_request: I/O error, dev 21:00 (hde), sector 2end_request: I/O error, dev 21:00 (hde), sector 4end_request: I/O error, dev 21:00 (hde), sector 6end_request: I/O error, dev 21:00 (hde), sector 8end_request: I/O error, dev 21:00 (hde), sector 10end_request: I/O error, dev 21:00 (hde), sector 12end_request: I/O error, dev 21:00 (hde), sector 14
Is this caused by the card being the S-ATA version? Is the disk responsible? I'm not that keen on trying with a better disk, since they all contain data I would like to keep. Is there some newer driver available?
I can use hdparm to change settings for the disk, but not read any data from it.
Signature · 2 lines
Måns Rullgård [email protected]