Re: NATA update

[Petr Janda <elekktretterr@xxxxxxxxxxxxxx>]

I have just started up the system with NATA and I already have something 
to note:

1) My cd/dvd drive is invisible

with old ata I get:

Dec 12 00:53:42 elevator kernel: cd0 at ata1 bus 0 target 0 lun 0
Dec 12 00:53:42 elevator kernel: cd0: <PIONEER DVD-RW  DVR-109 1.57> 
Removable CD-ROM SCSI-0 device
Dec 12 00:53:42 elevator kernel: cd0: 66.000MB/s transfers
Dec 12 00:53:42 elevator kernel: cd0: cd present [2238512 x 2048 byte 
records]


With new one, theres nothing.

2) My ATA-133 drive is invisible too.

with old ata I get:

Dec 12 00:53:42 elevator kernel: ad0: 38166MB <WDC WD400JB-00ENA0> 
[77545/16/63] at ata0-master UDMA100
Dec 12 00:53:42 elevator kernel: ad4: DMA limited to UDMA33, non-ATA66 
cable or device
Dec 12 00:53:42 elevator kernel: ad4: 76319MB <WDC WD800JD-22JNA0> 
[155061/16/63] at ata2-master UDMA33
Dec 12 00:53:42 elevator kernel: ad6: DMA limited to UDMA33, non-ATA66 
cable or device
Dec 12 00:53:42 elevator kernel: ad6: 76293MB <WDC WD800JD-75JNA0> 
[155009/16/63] at ata3-master UDMA33
Dec 12 00:53:42 elevator kernel: acd0: DVD-R <PIONEER DVD-RW DVR-109> at 
ata1-master UDMA66


With NATA, all i get is:

ad0: 76319MB <WDC WD800JD-22JNA0 05.01C05> at ata2-master SATA150
ad1: 76293MB <WDC WD800JD-75JNA0 05.01C05> at ata3-master SATA150


My kernel config is:

# NATA
device          nata
device          natadisk
device          natapicd
# device                natapicam

#options         PCI_MAP_FIXUP

PCI_MAP_FIXUP is commented out because its impossible to compile kernel 
with it (option not found or something). Tried it with and without 
natapicam but i get the same result: no cdrom, no ATA-133 drive.

Cheers,
Petr


Thomas E. Spanjaard wrote:
> Thomas E. Spanjaard wrote:
> > YONETANI Tomokazu wrote:
> > > But sometimes random commands(ls, sysctl, ...) dump core and fail.
> > > Or ld command reports corruption of libraries when I try to build
> > > a new kernel.  On SMP kernel it happens more frequently.  On UP kernel,
> > > if I switch to a UDMAxx mode using natacontrol command, core dumping
> > > occurs more frequently.
> > Hmm, I'm not seeing any corruptions (yet?) on my SCSI test system.
>
> After some pointers from Simon, I tried chrooting to one of the disks. 
> Surprise surprise, I get the same shit you're getting. Also, when 
> booting and mounting root from a{,c}d0, this shit happens randomly. 
> Sometimes it thinks si_drv1 is NULL, sometimes it doesn't. Sometimes 
> it fails the rootmount entirely, giving me the prompt again, and if 
> you type `cd9660:/dev/acd0c` often enough, one of the times it'll 
> work. Then, if you're lucky, /sbin/init works. Then you get rc.d stuff 
> with random segfaults, and then when you're extremely lucky, a login 
> prompt.
>
> Normal reads and writes to partitions are no problem at all. Only when 
> something tries to mmap, it sometimes works, but mostly doesn't. Is 
> there something special supposed to be done by strategy routines in 
> the case of an mmap? Is biodone() called too early somewhere? I don't 
> know yet :/.
>
> Cheers,