public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Willy Tarreau <willy@w.ods.org>,
	Jason Papadopoulos <jasonp@boo.net>,
	linux-kernel@vger.kernel.org, marcelo@conectiva.com.br
Subject: Re: Linux 2.4.21-rc3 : IDE pb on Alpha
Date: Wed, 28 May 2003 02:38:51 +0200	[thread overview]
Message-ID: <20030528003851.GA540@alpha.home.local> (raw)
In-Reply-To: <20030527180403.A2292@jurassic.park.msu.ru>

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;



  parent reply	other threads:[~2003-05-28  0:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-27  3:37 Linux 2.4.21-rc3 : IDE pb on Alpha Jason Papadopoulos
2003-05-27  4:53 ` Willy Tarreau
2003-05-27  9:40   ` Ivan Kokshaysky
2003-05-27 12:31     ` Willy Tarreau
2003-05-27 14:04       ` Ivan Kokshaysky
2003-05-27 14:37         ` Willy Tarreau
2003-05-28  0:38         ` Willy Tarreau [this message]
2003-05-28  1:41         ` Jason Papadopoulos
2003-05-28  3:12           ` Jeff Garzik
2003-05-29  0:35             ` Jason Papadopoulos
2003-05-29  1:10               ` Jeff Garzik
2003-05-28 14:45           ` Ivan Kokshaysky
2003-05-31 15:24         ` Ben Collins
2003-06-01 18:40           ` Ivan Kokshaysky
  -- strict thread matches above, loose matches on Subject: below --
2003-05-22 22:19 Linux 2.4.21-rc3 Marcelo Tosatti
2003-05-25 17:36 ` Linux 2.4.21-rc3 : IDE pb on Alpha Willy Tarreau
2003-05-25 17:00   ` Willy Tarreau
2003-05-25 20:37     ` Mike Fedyk
2003-05-25 20:45       ` Bartlomiej Zolnierkiewicz
2003-05-25 20:55         ` Mike Fedyk
2003-05-25 21:23           ` Bartlomiej Zolnierkiewicz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030528003851.GA540@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=ink@jurassic.park.msu.ru \
    --cc=jasonp@boo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox