Re: Newer kernel for N4100?
On Mon, Jul 14, 2008 at 12:35:21PM -0500, Bill Gatliff wrote:
> I just built mainline 2.6.26 with iop32x_defconfig and arm-linux-gnueabi-gcc
> (GCC) 4.2.4 (Debian 4.2.4-2). Booting on my n4100, I get this:
> RedBoot> exec -c "console=ttyS0,115200 mem=256M@0xa0000000 panic=5 root=nfs
> nfsroot=192.168.2.10:/exports/arm
> ip=192.168.2.8:192.168.2.10:192.168.2.1:255.255.255.0:n4100:eth0:off init=/bin/sh"
> Using base address 0x00200000 and length 0x00200594
> i82544_stop
> i82544_stop 0 flg 17
> Uncompressing Linux...............................................................
> ..................................................................... done,
> booting the kernel.
> Linux version 2.6.26 (bgat@mercury) (gcc version 4.2.4 (Debian 4.2.4-2)) #9 Mon
> Jul 14 11:41:31 CDT 2008
> CPU: XScale-80219 [69052e30] revision 0 (ARMv5TE), cr=0000397f
> Machine: Intel IQ31244
Thats probable the wrong machine. Try prependig the N2100 machine-id
for fixups.
devio > vmlinuz 'wl 0xe3a01c04,4' 'wl 0xe381104d,4'
cat arch/arm/boot/zImage >> vmlinuz
> ...
> scsi0 : sata_vsc
> scsi1 : sata_vsc
> scsi2 : sata_vsc
> scsi3 : sata_vsc
n2100 is sata_sil, so the device is more different from N2100 than I
thought. actually, IQ31244 has sata_vsc, so perhaps thats more correct
after all...
> ata1: SATA max UDMA/133 mmio m4096@0x80080000 port 0x80080200 irq 27
> ata2: SATA max UDMA/133 mmio m4096@0x80080000 port 0x80080400 irq 27
> ata3: SATA max UDMA/133 mmio m4096@0x80080000 port 0x80080600 irq 27
> ata4: SATA max UDMA/133 mmio m4096@0x80080000 port 0x80080800 irq 27
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: qc timeout (cmd 0x27)
> ata1.00: failed to read native max address (err_mask=0x4)
> ata1.00: HPA support seems broken, skipping HPA handling
> ata1: failed to recover some devices, retrying in 5 secs
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: configured for UDMA/100
> ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata2.00: qc timeout (cmd 0x27)
> ata2.00: failed to read native max address (err_mask=0x4)
> ata2.00: HPA support seems broken, skipping HPA handling
> ata2: failed to recover some devices, retrying in 5 secs
> ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata2.00: configured for UDMA/100
> ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata3.00: qc timeout (cmd 0x27)
> ata3.00: failed to read native max address (err_mask=0x4)
> ata3.00: HPA support seems broken, skipping HPA handling
> ata3: failed to recover some devices, retrying in 5 secs
> ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata3.00: configured for UDMA/100
> ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata4.00: qc timeout (cmd 0x27)
> ata4.00: failed to read native max address (err_mask=0x4)
> ata4.00: HPA support seems broken, skipping HPA handling
> ata4: failed to recover some devices, retrying in 5 secs
> ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata4.00: configured for UDMA/100
> scsi 0:0:0:0: Direct-Access ATA WDC WD3000JD-00K 08.0 PQ: 0 ANSI: 5
> sd 0:0:0:0: [sda] 586072368 512-byte hardware sectors (300069 MB)
> sd 0:0:0:0: [sda] Write Protect is off
> sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO
> or FUA
> sd 0:0:0:0: [sda] 586072368 512-byte hardware sectors (300069 MB)
> sd 0:0:0:0: [sda] Write Protect is off
> sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO
> or FUA
> sda:<3>ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
> ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata1.00: status: { DRDY }
> ata1: hard resetting link
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: configured for UDMA/100
> ...
> ...
> ...
>
> It repeats this over and over and over again, as far as I can tell it tries
> UDMA/133, then UDMA/100, ... until it gets to UDMA/33. For each device. It
> takes an *age*.
>
> After that, it apparently gives up and moves through the rest of the boot
> process (which I haven't finished yet--- I had to restart because I forgot the
> ip= parameter needed for nfsroot).
>
> Interestingly, the above does contain the right information for the drive(s) in
> question: WDC WD3000JD-00K. So the drives are at least still talking.
>
> Not knowing much about SATA, though, I can't tell what all the above means---
> either for the kernel's functionality on this platform, or the health of the
> drives running in it.
perhaps you'll want to ask the sata_vsc author. another possibility is
that the pci IRQ map is wrong and the driver isn't recieving interrupts
from the sata controller.
overall seems quite promising. contrast: with the default IQ31244 confing
n2100 dies when probing for second i2c controller :)
--
"rm -rf" only sounds scary if you don't have backups
Reply to: