Re: Linux 2.4.21-rc3 : IDE pb on Alpha

Re: Linux 2.4.21-rc3 : IDE pb on Alpha

[Jason Papadopoulos]

 >the system could boot without DMA. It displayed lots of messages, but it 
seems
 >to work :

 >So it seems as the IDE problem is in the ALI 1543 / DMA code. I have an old
 >K6/2 notebook somewhere with the same IDE controller, so I may retry on it.
 >
 >I'm interested in any suggestion, of course ;-)

I have the same system and run into the same problems here. The HD is a
Fujitsu MPD3108AT (10GB ATA33/66 drive, what the machine shipped with)
on hda. Even with the 2.4.21-rc4 kernel, the machine will not boot beyond
the "attached ide-disk driver" message if IDE DMA is compiled in.

Whatever's going wrong doesn't require an older drive to show up.

Let me know how I can help,
jasonp

Re: Linux 2.4.21-rc3 : IDE pb on Alpha

[Willy Tarreau]

On Mon, May 26, 2003 at 11:37:04PM -0400, Jason Papadopoulos wrote:
 
> I have the same system and run into the same problems here. The HD is a
> Fujitsu MPD3108AT (10GB ATA33/66 drive, what the machine shipped with)
> on hda. Even with the 2.4.21-rc4 kernel, the machine will not boot beyond
> the "attached ide-disk driver" message if IDE DMA is compiled in.
> 
> Whatever's going wrong doesn't require an older drive to show up.

I could finally enable DMA, only if I do it at run time :
  - enable "Generic PCI bus master DMA support"
  - disable "Use PCI DMA by default when available"
  - hdparm -d 1 /dev/every_disk

I realized that a "idex=nodma" option is really lacking here. Shouldn't we
disable IDE by default on Alpha at the moment, so that it at least boots ?
The adventurous could always use hdparm to enable it again (it survived my
39 GB save/restore).

Regards,
Willy

Re: Linux 2.4.21-rc3 : IDE pb on Alpha

[Ivan Kokshaysky]

On Tue, May 27, 2003 at 06:53:02AM +0200, Willy Tarreau wrote:
> I realized that a "idex=nodma" option is really lacking here. Shouldn't we
> disable IDE by default on Alpha at the moment, so that it at least boots ?

According to your .config and dmesg output, you didn't have the
chipset driver compiled in (CONFIG_BLK_DEV_ALI15X3).
Naturally, you would have troubles with DMA.

Ivan.

Re: Linux 2.4.21-rc3 : IDE pb on Alpha

[Willy Tarreau]

On Tue, May 27, 2003 at 01:40:17PM +0400, Ivan Kokshaysky wrote:
> On Tue, May 27, 2003 at 06:53:02AM +0200, Willy Tarreau wrote:
> > I realized that a "idex=nodma" option is really lacking here. Shouldn't we
> > disable IDE by default on Alpha at the moment, so that it at least boots ?
> 
> According to your .config and dmesg output, you didn't have the
> chipset driver compiled in (CONFIG_BLK_DEV_ALI15X3).
> Naturally, you would have troubles with DMA.

Sorry, I pasted the .config that I used just after, and which allowed me to
boot. Later I set CONFIG_BLK_DEV_ALI15X3 again and CONFIG_BLK_DEV_IDEDMA_PCI,
but I left CONFIG_IDEDMA_PCI_AUTO disabled. I now can boot and enable DMA
later. That's weird, but it works.

Regards,
Willy

Re: Linux 2.4.21-rc3 : IDE pb on Alpha

[Ivan Kokshaysky]

On Tue, May 27, 2003 at 02:31:52PM +0200, Willy Tarreau wrote:
> Sorry, I pasted the .config that I used just after, and which allowed me to
> boot. Later I set CONFIG_BLK_DEV_ALI15X3 again and CONFIG_BLK_DEV_IDEDMA_PCI,
> but I left CONFIG_IDEDMA_PCI_AUTO disabled. I now can boot and enable DMA
> later. That's weird, but it works.

Perhaps not that weird. From my experience, ALi DMA is sensitive to
some of "PIO timings". That is, if SRM hasn't initialized the chipset
properly (on Nautilus it has, BTW), DMA won't work. When you boot with
DMA disabled, driver has to set right PIO mode, so you can safely
enable DMA later.

Can you (and Jason) try this patch with CONFIG_IDEDMA_PCI_AUTO=y?

Ivan.

--- linux/drivers/ide/pci/alim15x3.c.orig	Tue Apr 22 19:17:22 2003
+++ linux/drivers/ide/pci/alim15x3.c	Tue May 27 17:42:17 2003
@@ -525,10 +525,14 @@ static int ali15x3_config_drive_for_dma(
 
 	drive->init_speed = 0;
 
+	/* Set reasonable PIO timings first - some of them are needed
+	   for DMA as well. */
+	hwif->tuneproc(drive, 255);
+
 	if ((id->capability & 1) != 0 && drive->autodma) {
 		/* Consult the list of known "bad" drives */
 		if (hwif->ide_dma_bad_drive(drive))
-			goto ata_pio;
+			goto no_dma_set;
 		if ((id->field_valid & 4) && (m5229_revision >= 0xC2)) {
 			if (id->dma_ultra & hwif->ultra_mask) {
 				/* Force if Capable UltraDMA */
@@ -550,11 +554,9 @@ try_dma_modes:
 			if (!config_chipset_for_dma(drive))
 				goto no_dma_set;
 		} else {
-			goto ata_pio;
+			goto no_dma_set;
 		}
 	} else {
-ata_pio:
-		hwif->tuneproc(drive, 255);
 no_dma_set:
 		return hwif->ide_dma_off_quietly(drive);
 	}

Re: Linux 2.4.21-rc3 : IDE pb on Alpha

[Willy Tarreau]

On Tue, May 27, 2003 at 06:04:03PM +0400, Ivan Kokshaysky wrote:
> On Tue, May 27, 2003 at 02:31:52PM +0200, Willy Tarreau wrote:
> > Sorry, I pasted the .config that I used just after, and which allowed me to
> > boot. Later I set CONFIG_BLK_DEV_ALI15X3 again and CONFIG_BLK_DEV_IDEDMA_PCI,
> > but I left CONFIG_IDEDMA_PCI_AUTO disabled. I now can boot and enable DMA
> > later. That's weird, but it works.
> 
> Perhaps not that weird. From my experience, ALi DMA is sensitive to
> some of "PIO timings". That is, if SRM hasn't initialized the chipset
> properly (on Nautilus it has, BTW), DMA won't work. When you boot with
> DMA disabled, driver has to set right PIO mode, so you can safely
> enable DMA later.
> 
> Can you (and Jason) try this patch with CONFIG_IDEDMA_PCI_AUTO=y?

Compilation in progress, but it will wait for me to get in touch with the
machine to reboot it (probably this evening).

Cheers,
Willy

Re: Linux 2.4.21-rc3 : IDE pb on Alpha

[Willy Tarreau]

Hi !

On Tue, May 27, 2003 at 06:04:03PM +0400, Ivan Kokshaysky wrote:
> Can you (and Jason) try this patch with CONFIG_IDEDMA_PCI_AUTO=y?

Well, I tried to reboot (blindly, only with a keyboard attached) on the
new kernel, but it behave the same way : "boot -fl 1" (1 is the new kernel)
does a few disk accesses to load the kernel, then hangs, while "0" boots
correctly, so I'm sure my keyboard is correctly plugged and I don't mistype.

Sorry Ivan for such a miserable report, but I couldn't plug either a VT or a
VGA display. I will retry -rc5 (or -rc6) ASAP, but for now I'm going to bed.

Marcelo, the AHA29160 on this system (alpha) spurts lots of debug messages
"blk: queue 0xffff..." at boot with the version in -rc3. Justin pointed me
to drivers/block/ll_rw_blk.c:268 which is responsible for the message. It's
marked as debug, but no KERN_XXX prefix is used. So I think that either
KERN_DEBUG should be added, or the message should simply disappear, since it
sends garbage on the screen which makes SCSI detection a bit hard to read.

Here are two quickly written, completely untested patch proposals.
Please note that this code has not changed since 2.4.20 (which I never tested
on this machine).

Regards,
Willy

######## the most correct one ? ########

--- ./drivers/block/ll_rw_blk.c	Fri May  9 21:33:10 2003
+++ /tmp/ll_rw_blk.c-debug	Wed May 28 02:33:05 2003
@@ -265,7 +265,7 @@
 	 */
 	if (dma_addr != BLK_BOUNCE_HIGH && q != old_q) {
 		old_q = q;
-		printk("blk: queue %p, ", q);
+		printk(KERN_DEBUG "blk: queue %p, ", q);
 		if (dma_addr == BLK_BOUNCE_ANY)
 			printk("no I/O memory limit\n");
 		else


##### this one hides the message. Note that it may lead to a warning
##### with mb defined but not used !

--- ./drivers/block/ll_rw_blk.c	Fri May  9 21:33:10 2003
+++ /tmp/ll_rw_blk.c-nomsg	Wed May 28 02:32:50 2003
@@ -265,12 +265,14 @@
 	 */
 	if (dma_addr != BLK_BOUNCE_HIGH && q != old_q) {
 		old_q = q;
+#ifdef BLK_QUEUE_DEBUG
 		printk("blk: queue %p, ", q);
 		if (dma_addr == BLK_BOUNCE_ANY)
 			printk("no I/O memory limit\n");
 		else
 			printk("I/O limit %luMb (mask 0x%Lx)\n", mb,
 			       (long long) dma_addr);
+#endif
 	}
 
 	q->bounce_pfn = bounce_pfn;

Re: Linux 2.4.21-rc3 : IDE pb on Alpha

[Jason Papadopoulos]

At 06:04 PM 5/27/03 +0400, you wrote:
 >
 >Perhaps not that weird. From my experience, ALi DMA is sensitive to
 >some of "PIO timings". That is, if SRM hasn't initialized the chipset
 >properly (on Nautilus it has, BTW), DMA won't work. When you boot with
 >DMA disabled, driver has to set right PIO mode, so you can safely
 >enable DMA later.
 >
 >Can you (and Jason) try this patch with CONFIG_IDEDMA_PCI_AUTO=y?

Sorry, no change. I do get behavior that matches Willy's though: use
hdparm and you can get DMA turned on. Another clue is that the ALI
controller is capable of udma2 (and older kernels achieve that) but even
with hdparm the best I can get seems to be mode mdma2.

Also, I've found that lately I have to attempt to boot from the hard
drive (dqa0) about three times before the kernel finally gets pulled
off of disk. SRM reports a bootstrap failure each time, but otherwise
the system seems to work fine. Has anyone seen this behavior?

Anything else I can do?
jasonp

Re: Linux 2.4.21-rc3 : IDE pb on Alpha

[Jeff Garzik]

Jason Papadopoulos wrote:
> Sorry, no change. I do get behavior that matches Willy's though: use
> hdparm and you can get DMA turned on. Another clue is that the ALI
> controller is capable of udma2 (and older kernels achieve that) but even
> with hdparm the best I can get seems to be mode mdma2.


FWIW, udma2 is the best you can do without accurate cable detection and 
an 80-conductor cable.

	Jeff

Re: Linux 2.4.21-rc3 : IDE pb on Alpha

[Ivan Kokshaysky]

On Tue, May 27, 2003 at 09:41:12PM -0400, Jason Papadopoulos wrote:
> Also, I've found that lately I have to attempt to boot from the hard
> drive (dqa0) about three times before the kernel finally gets pulled
> off of disk. SRM reports a bootstrap failure each time, but otherwise
> the system seems to work fine. Has anyone seen this behavior?

Yes, it's known problem. Recent 2.4 kernels shutdown the IDE disks
on halt/poweroff, which is extremely annoying on alpha when you return
to SRM prompt to boot another kernel. You'll have to wait until
the disk spins up again.

> Anything else I can do?

Send me please "lspci -vxxx -s 0:d" outputs for
- old (working) kernel;
- new kernel before and after "hdparm -d1".

Ivan.

Re: Linux 2.4.21-rc3 : IDE pb on Alpha

[Jason Papadopoulos]

At 11:12 PM 5/27/03 -0400, Jeff Garzik wrote:
 >
 >FWIW, udma2 is the best you can do without accurate cable detection and
 >an 80-conductor cable.
 >

Well, even with a drive capable of ATA66, an 80-pin cable, and a kernel
configured to force assumption of higher UDMA modes, the best I've ever
done with this stupid ALI controller is udma2. I think it's deliberately
crippled.

jasonp

Re: Linux 2.4.21-rc3 : IDE pb on Alpha

[Jeff Garzik]

Jason Papadopoulos wrote:
> At 11:12 PM 5/27/03 -0400, Jeff Garzik wrote:
>  >
>  >FWIW, udma2 is the best you can do without accurate cable detection and
>  >an 80-conductor cable.
>  >
> 
> Well, even with a drive capable of ATA66, an 80-pin cable, and a kernel
> configured to force assumption of higher UDMA modes, the best I've ever
> done with this stupid ALI controller is udma2. I think it's deliberately
> crippled.


"configured to force the assumption" does no good if the host controller 
driver isn't detecting the cable correctly, or is not programming 80c 
cable info into the host controller correctly.  That's a code change not 
a configuration thing.

	Jeff

Re: Linux 2.4.21-rc3 : IDE pb on Alpha

[Ben Collins]

On Tue, May 27, 2003 at 06:04:03PM +0400, Ivan Kokshaysky wrote:
> On Tue, May 27, 2003 at 02:31:52PM +0200, Willy Tarreau wrote:
> > Sorry, I pasted the .config that I used just after, and which allowed me to
> > boot. Later I set CONFIG_BLK_DEV_ALI15X3 again and CONFIG_BLK_DEV_IDEDMA_PCI,
> > but I left CONFIG_IDEDMA_PCI_AUTO disabled. I now can boot and enable DMA
> > later. That's weird, but it works.
> 
> Perhaps not that weird. From my experience, ALi DMA is sensitive to
> some of "PIO timings". That is, if SRM hasn't initialized the chipset
> properly (on Nautilus it has, BTW), DMA won't work. When you boot with
> DMA disabled, driver has to set right PIO mode, so you can safely
> enable DMA later.
> 
> Can you (and Jason) try this patch with CONFIG_IDEDMA_PCI_AUTO=y?

Dave Miller asked me to try this patch. On sparc64, we've had a never
ending battle with ALi 5229 on Sun Blade 100's. After some time, files
would start to get corrupted (in memory, not on disk, unless the
corruption was saved somehow inadvertently). It exposed itself as two
null bytes at the start of a file.

I just tried this patch, and for the first time in a long time, I've
been able to boot with UDMA(66) enabled and not get the corruption.
Usually I can expose the corruption with kernel compiles within 10-60
minutes. I've been running your patch for almost 2 days now, and so far
have not been able get corruption. I even left a looping 2.5.69 compile
going (make clean; make) for over 10 hours.



-- 
Debian     - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo       - http://www.deqo.com/

Re: Linux 2.4.21-rc3 : IDE pb on Alpha

[Ivan Kokshaysky]

On Sat, May 31, 2003 at 11:24:17AM -0400, Ben Collins wrote:
> I just tried this patch, and for the first time in a long time, I've
> been able to boot with UDMA(66) enabled and not get the corruption.

Excellent, thanks for the report. :-)

Ivan.

Re: Linux 2.4.21-rc3 : IDE pb on Alpha

[Bartlomiej Zolnierkiewicz]

On Sun, 25 May 2003, Mike Fedyk wrote:
> On Sun, May 25, 2003 at 10:45:00PM +0200, Bartlomiej Zolnierkiewicz wrote:
> > On Sun, 25 May 2003, Mike Fedyk wrote:
> >
> > > On Sun, May 25, 2003 at 07:00:46PM +0200, Willy Tarreau wrote:
> > > > hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
> > > > hda: task_no_data_intr: error=0x04 { DriveStatusError }
> > >
> > > Can you revert back to your previous kernel and run badblocks read-only on
> > > it a few times.  Your drive may be going bad.
> >
> >
> >
> > Everything is okay, older drives don't understand some commands.
> > I will fix it, but now its low on my TODO list.

> Bart, is there any chace you could change the printks to show the name of
> the command that caused the drive to produce the error (assuming non
> ide-tcq, with tcq I'd immagine that it'd be a bit harder).

For taskfile based IO its trivial, but IDE is not yet switched to it
(will be soon).

> This way someone who hasn't read the IDE spec might be able to tell that
> this isn't a warning of impending failure.

> BTW, is this information encoded in the two lines above somewhere, and if so
> how would I read it?

Only failed irq handler, drive status and error returned by drive.
"error = 0x04" means command aborted.

Regards,
--
Bartlomiej

> Thanks,
>
> Mike

Re: Linux 2.4.21-rc3 : IDE pb on Alpha

[Mike Fedyk]

On Sun, May 25, 2003 at 10:45:00PM +0200, Bartlomiej Zolnierkiewicz wrote:
> On Sun, 25 May 2003, Mike Fedyk wrote:
> 
> > On Sun, May 25, 2003 at 07:00:46PM +0200, Willy Tarreau wrote:
> > > hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
> > > hda: task_no_data_intr: error=0x04 { DriveStatusError }
> >
> > Can you revert back to your previous kernel and run badblocks read-only on
> > it a few times.  Your drive may be going bad.
> 
> 
> 
> Everything is okay, older drives don't understand some commands.
> I will fix it, but now its low on my TODO list.
> 

Bart, is there any chace you could change the printks to show the name of
the command that caused the drive to produce the error (assuming non
ide-tcq, with tcq I'd immagine that it'd be a bit harder).

This way someone who hasn't read the IDE spec might be able to tell that
this isn't a warning of impending failure.

BTW, is this information encoded in the two lines above somewhere, and if so
how would I read it?

Thanks,

Mike

Re: Linux 2.4.21-rc3 : IDE pb on Alpha

[Bartlomiej Zolnierkiewicz]

Everything is okay, older drives don't understand some commands.
I will fix it, but now its low on my TODO list.

On Sun, 25 May 2003, Mike Fedyk wrote:

> On Sun, May 25, 2003 at 07:00:46PM +0200, Willy Tarreau wrote:
> > hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
> > hda: task_no_data_intr: error=0x04 { DriveStatusError }
>
> Can you revert back to your previous kernel and run badblocks read-only on
> it a few times.  Your drive may be going bad.

Re: Linux 2.4.21-rc3 : IDE pb on Alpha

[Mike Fedyk]

On Sun, May 25, 2003 at 07:00:46PM +0200, Willy Tarreau wrote:
> hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: task_no_data_intr: error=0x04 { DriveStatusError }

Can you revert back to your previous kernel and run badblocks read-only on
it a few times.  Your drive may be going bad.

Linux 2.4.21-rc3 : IDE pb on Alpha

[Willy Tarreau]

Hi all !

I've upgraded my Alpha's kernel to 2.4.21-rc3, but it hangs on IDE at boot.
Same with 2.4.21-rc2. It has been working one year on with 2.4.19-pre7 + Andre
Hedrick's IDE patch. I'm now recompiling without DMA support, just in case.
For info, this is a DS10, EV6/466, 256 MB RAM, with an ALI 1543 IDE controller.
The first IDE controller has an old WD23200 (3.2GB) disk attached, which hosts
the root FS. The second controller has a 120 GB Maxtor drive.

I tried to boot with ide[01]=reset, ide[01]=noprobe, but with no luck. I've
quickly written down the last messages during ide0=noprobe :

hdc: Maxtor 6Y120L0, ATA DISK drive
blk: queue at ffff...?????, no I/O memory limit
ide1 at 0x170-0x177,0x376 on irq 15
hdc: attached ide-disk driver
------ stops here ------

I can play with sysrq during a few seconds, before the keyboard finally locks.
I'll try to get some pointers with SysRq-P.

If I boot with ide0=noprobe ide1=noprobe, it goes further, even detects the SCSI
disks attached to an Adaptec controller, then panics because of a missing root
device, thus proving that IDE really is the culprit here :-)

GCC is 3.2.3. I could revert to an old 2.91.66 which is still installed on this
system, if needed.

The compilation just ended, I'll retry without DMA.

Cheers,
Willy

.config appended with all unset options stripped :


CONFIG_ALPHA=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_EXPERIMENTAL=y
CONFIG_MODULES=y
CONFIG_KMOD=y
CONFIG_ALPHA_DP264=y
CONFIG_ISA=y
CONFIG_EISA=y
CONFIG_PCI=y
CONFIG_ALPHA_EV6=y
CONFIG_ALPHA_TSUNAMI=y
CONFIG_ALPHA_SRM=y
CONFIG_EARLY_PRINTK=y
CONFIG_PCI_NAMES=y
CONFIG_NET=y
CONFIG_SYSVIPC=y
CONFIG_SYSCTL=y
CONFIG_KCORE_ELF=y
CONFIG_SRM_ENV=y
CONFIG_BINFMT_ELF=y
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_PC_CML1=m
CONFIG_PARPORT_SERIAL=m
CONFIG_PARPORT_PC_FIFO=y
CONFIG_PARPORT_PC_SUPERIO=y
CONFIG_PNP=y
CONFIG_ISAPNP=y
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_NBD=m
CONFIG_BLK_DEV_RAM=m
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_LINEAR=y
CONFIG_MD_RAID0=y
CONFIG_MD_RAID1=y
CONFIG_MD_RAID5=y
CONFIG_BLK_DEV_LVM=y
CONFIG_PACKET=y
CONFIG_NETLINK_DEV=y
CONFIG_NETFILTER=y
CONFIG_FILTER=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_FWMARK=y
CONFIG_IP_ROUTE_NAT=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_TOS=y
CONFIG_IP_ROUTE_VERBOSE=y
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_INET_ECN=y
CONFIG_IP_NF_CONNTRACK=m
CONFIG_IP_NF_FTP=m
CONFIG_IP_NF_TFTP=m
CONFIG_IP_NF_IRC=m
CONFIG_IP_NF_QUEUE=y
CONFIG_IP_NF_IPTABLES=y
CONFIG_IP_NF_MATCH_LIMIT=y
CONFIG_IP_NF_MATCH_MAC=y
CONFIG_IP_NF_MATCH_PKTTYPE=y
CONFIG_IP_NF_MATCH_MARK=y
CONFIG_IP_NF_MATCH_MULTIPORT=y
CONFIG_IP_NF_MATCH_TOS=y
CONFIG_IP_NF_MATCH_AH_ESP=y
CONFIG_IP_NF_MATCH_LENGTH=y
CONFIG_IP_NF_MATCH_TTL=y
CONFIG_IP_NF_MATCH_TCPMSS=y
CONFIG_IP_NF_MATCH_HELPER=m
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_CONNTRACK=m
CONFIG_IP_NF_MATCH_UNCLEAN=y
CONFIG_IP_NF_MATCH_OWNER=y
CONFIG_IP_NF_FILTER=y
CONFIG_IP_NF_TARGET_REJECT=y
CONFIG_IP_NF_TARGET_MIRROR=y
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_IP_NF_NAT_LOCAL=y
CONFIG_IP_NF_NAT_SNMP_BASIC=m
CONFIG_IP_NF_NAT_IRC=m
CONFIG_IP_NF_NAT_FTP=m
CONFIG_IP_NF_NAT_TFTP=m
CONFIG_IP_NF_MANGLE=y
CONFIG_IP_NF_TARGET_TOS=y
CONFIG_IP_NF_TARGET_DSCP=m
CONFIG_IP_NF_TARGET_MARK=y
CONFIG_IP_NF_TARGET_LOG=y
CONFIG_IP_NF_TARGET_TCPMSS=y
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_VLAN_8021Q=y
CONFIG_BRIDGE=m
CONFIG_NET_PKTGEN=m
CONFIG_IDE=y
MAX_HWIFS=4
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDESCSI=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_BLK_DEV_GENERIC=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_SCSI=y
CONFIG_BLK_DEV_SD=y
CONFIG_SD_EXTRA_DEVS=40
CONFIG_CHR_DEV_ST=y
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_SR_EXTRA_DEVS=2
CONFIG_CHR_DEV_SG=y
CONFIG_SCSI_AIC7XXX=y
CONFIG_AIC7XXX_CMDS_PER_DEVICE=253
CONFIG_AIC7XXX_RESET_DELAY_MS=5000
CONFIG_SCSI_MEGARAID=m
CONFIG_SCSI_NCR53C8XX=m
CONFIG_SCSI_SYM53C8XX=m
CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=8
CONFIG_SCSI_NCR53C8XX_MAX_TAGS=32
CONFIG_SCSI_NCR53C8XX_SYNC=20
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
CONFIG_BONDING=m
CONFIG_NET_ETHERNET=y
CONFIG_HAPPYMEAL=m
CONFIG_NET_VENDOR_3COM=y
CONFIG_VORTEX=m
CONFIG_NET_PCI=y
CONFIG_PCNET32=m
CONFIG_ADAPTEC_STARFIRE=m
CONFIG_TULIP=m
CONFIG_TULIP_MWI=y
CONFIG_EEPRO100=m
CONFIG_8139TOO=m
CONFIG_ACENIC=m
CONFIG_ACENIC_OMIT_TIGON_I=y
CONFIG_DL2K=m
CONFIG_E1000=m
CONFIG_TIGON3=m
CONFIG_PPP=m
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
CONFIG_PPPOE=m
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_SERIAL=y
CONFIG_SERIAL_CONSOLE=y
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
CONFIG_PRINTER=m
CONFIG_I2C=m
CONFIG_I2C_ALGOBIT=m
CONFIG_I2C_CHARDEV=m
CONFIG_I2C_PROC=m
CONFIG_MOUSE=y
CONFIG_PSMOUSE=y
CONFIG_WATCHDOG=y
CONFIG_ALIM1535_WDT=m
CONFIG_ALIM7101_WDT=m
CONFIG_SOFT_WATCHDOG=m
CONFIG_RTC=y
CONFIG_VIDEO_DEV=m
CONFIG_REISERFS_FS=y
CONFIG_EXT3_FS=y
CONFIG_JBD=y
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_TMPFS=y
CONFIG_RAMFS=y
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_MINIX_FS=m
CONFIG_PROC_FS=y
CONFIG_DEVPTS_FS=y
CONFIG_EXT2_FS=y
CONFIG_CODA_FS=m
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
CONFIG_NFSD_TCP=y
CONFIG_SUNRPC=m
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_ZISOFS_FS=y
CONFIG_PARTITION_ADVANCED=y
CONFIG_OSF_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_850=y
CONFIG_NLS_ISO8859_1=y
CONFIG_NLS_ISO8859_15=y
CONFIG_VGA_CONSOLE=y
CONFIG_FB=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FB_MATROX=y
CONFIG_FB_MATROX_MILLENIUM=y
CONFIG_FBCON_CFB8=y
CONFIG_FBCON_CFB16=y
CONFIG_FBCON_CFB24=y
CONFIG_FBCON_CFB32=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_PCI_CONSOLE=y
CONFIG_SOUND=y
CONFIG_SOUND_ES1371=m
CONFIG_ALPHA_LEGACY_START_ADDRESS=y
CONFIG_DEBUG_KERNEL=y
CONFIG_MATHEMU=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=m

Re: Linux 2.4.21-rc3 : IDE pb on Alpha

[Willy Tarreau]

Hi again !

the system could boot without DMA. It displayed lots of messages, but it seems
to work :


Linux version 2.4.21-rc3 (root@alpha) (gcc version 3.2.3) #4 Sun May 25 19:16:43 CEST 2003
Booting on Tsunami variation Webbrick using machine vector Webbrick from SRM
Command line: root=/dev/hda2 console=tty0 console=ttyS0,9600 bootdevice=scd0 bootfile=2.4.21-rc3/vmlinux
memcluster 0, usage 1, start        0, end      256
memcluster 1, usage 0, start      256, end    32655
memcluster 2, usage 1, start    32655, end    32768
freeing pages 256:384
freeing pages 805:32655
reserving pages 805:806
On node 0 totalpages: 32655
zone(0): 32655 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/hda2 console=tty0 console=ttyS0,9600 bootdevice=scd0 bootfile=2.4.21-rc3/vmlinux
Using epoch = 1952
Console: colour VGA+ 80x25
Calibrating delay loop... 921.84 BogoMIPS
Memory: 252720k/261240k available (2094k kernel code, 6472k reserved, 451k data, 320k init)
Dentry cache hash table entries: 32768 (order: 6, 524288 bytes)
Inode cache hash table entries: 16384 (order: 5, 262144 bytes)
Mount cache hash table entries: 512 (order: 0, 8192 bytes)
Buffer-cache hash table entries: 8192 (order: 3, 65536 bytes)
Page-cache hash table entries: 32768 (order: 5, 262144 bytes)
POSIX conformance testing by UNIFIX
PCI: dev Adaptec AIC-7892A U160/m type 64-bit
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
srm_env: version 0.0.5 loaded successfully
Starting kswapd
Journalled Block Device driver loaded
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
rtc: Digital UNIX epoch (1952) detected
Real Time Clock Driver v1.10e
Floppy drive(s): fd0 is 2.88M
FDC 0 is a post-1991 82077
Uniform Multi-Platform E-IDE driver Revision: 7.00beta3-.2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
hda: WDC AC23200L, ATA DISK drive
hdc: Maxtor 6Y120L0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: attached ide-disk driver.
hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_no_data_intr: error=0x04 { DriveStatusError }
hda: host protected area => 1
hda: 6346368 sectors (3249 MB) w/256KiB Cache, CHS=6296/16/63
hdc: attached ide-disk driver.
hdc: host protected area => 1
hdc: 240121728 sectors (122942 MB) w/2048KiB Cache, CHS=238216/16/63
Partition check:
 hda: hda1 hda2 hda3 hda7
 hdc: hdc1
SCSI subsystem driver Revision: 1.00
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.8
        <Adaptec 29160 Ultra160 SCSI adapter>
        aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs

blk: queue fffffc00002214e8, no I/O memory limit
  Vendor: HP        Model: C1537A            Rev: L706
  Type:   Sequential-Access                  ANSI SCSI revision: 02
blk: queue fffffc00002216e8, no I/O memory limit
  Vendor: COMPAQ    Model: BD01864552        Rev: 3B04
  Type:   Direct-Access                      ANSI SCSI revision: 02
blk: queue fffffc00002218e8, no I/O memory limit
  Vendor: COMPAQ    Model: BD01864552        Rev: 3B04
  Type:   Direct-Access                      ANSI SCSI revision: 02
blk: queue fffffc0000221ae8, no I/O memory limit
  Vendor: COMPAQ    Model: BD01864552        Rev: 3B04
  Type:   Direct-Access                      ANSI SCSI revision: 02
blk: queue fffffc0000221ce8, no I/O memory limit
  Vendor: COMPAQ    Model: BD01864552        Rev: 3B04
  Type:   Direct-Access                      ANSI SCSI revision: 02
blk: queue fffffc000feee128, no I/O memory limit
------
After that, nothing special. I'm amazed by the number of "blk: queue..."
messages. This time, it only appears on SCSI, and not on IDE anymore.

So it seems as the IDE problem is in the ALI 1543 / DMA code. I have an old
K6/2 notebook somewhere with the same IDE controller, so I may retry on it.

I'm interested in any suggestion, of course ;-)

Willy