linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: linux-kernel@vger.kernel.org
Cc: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
	Andrew Morton <akpm@osdl.org>,
	linux-mm@kvack.org
Subject: Re: 2.6.2-rc3-mm1
Date: Wed, 4 Feb 2004 00:17:43 +0000	[thread overview]
Message-ID: <200402040017.43787.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <200402040100.40682.bzolnier@elka.pw.edu.pl>

On Wednesday 04 February 2004 00:00, Bartlomiej Zolnierkiewicz wrote:
[snip]
> > > > UDMA(133) /dev/ide/host0/bus0/target0/lun0: p1 p2 p3
> > > > hde: max request size: 128KiB
> > > >
> > > > 30 seconds later, I get something like:
> > > >
> > > > hde: lost interrupt
> > > > hde: lost interrupt
> > >
> > > It seems kernel hangs in ide-disk.c,
> > > idedisk_setup()->write_cache()->...
> > >
> > > > The kernel does not recover. Presumably it is a problem specific to
> > > > my PDC IDE controller.
> > >
> > > Do you run with Promise BIOS disabled?  If so please try booting kernel
> > > with "hde=autotune hdg=autotune" parameters.  If still no-go, try this
> > > patch:
> >
> > Neither suggestion changes the behaviour. I've got the BIOS enabled, but
> > in the past it's made no difference. I still see lost interrupts.
>
> Please try this debugging patch to see it hangs on
> idedisk_setup()->write_cache().
>
> --- linux/drivers/ide/ide-disk.c	2004-02-04 00:57:49.000000000 +0100
> +++ linux-2.6.2-rc3-bk3/drivers/ide/ide-disk.c	2004-02-04
> 00:58:58.571025744 +0100 @@ -1668,8 +1668,10 @@
>  #endif	/* CONFIG_IDEDISK_MULTI_MODE */
>  	}
>  	drive->no_io_32bit = id->dword_io ? 1 : 0;
> +	printk(KERN_INFO "%s: before write_cache()\n", drive->name);
>  	if (drive->id->cfs_enable_2 & 0x3000)
>  		write_cache(drive, (id->cfs_enable_2 & 0x3000));
> +	printk(KERN_INFO "%s: after write_cache()\n", drive->name);
>
>  #ifdef CONFIG_BLK_DEV_IDE_TCQ_DEFAULT
>  	if (drive->using_dma)

Tried the patch. I see both before and after messages for hda, but when hde is 
probed I see neither. Briefly looking at the IDE code, I see the max request 
size: printk comes before either of those lines, as as nothing else is 
printed after that line (see original bug report), I can only assume the 
problem is somewhere before the write_cache().

I applied the patch on top of your previous changes, as they seemed innocuous 
enough.

-- 
Cheers,
Alistair.

personal:   alistair()devzero!co!uk
university: s0348365()sms!ed!ac!uk
student:    CS/AI Undergraduate
contact:    7/10 Darroch Court,
            University of Edinburgh.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2004-02-04  0:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-03  7:58 2.6.2-rc3-mm1 Andrew Morton
2004-02-03  9:58 ` 2.6.2-rc3-mm1 Prakash K. Cheemplavam
2004-02-03 10:10   ` 2.6.2-rc3-mm1 Prakash K. Cheemplavam
2004-02-03 10:16 ` 2.6.2-rc3-mm1 Helge Hafting
2004-02-03 10:33 ` 2.6.2-rc3-mm1 Andrew Morton
2004-02-03 17:39 ` 2.6.2-rc3-mm1 Alistair John Strachan
2004-02-03 18:32   ` 2.6.2-rc3-mm1 Bartlomiej Zolnierkiewicz
2004-02-03 23:47     ` 2.6.2-rc3-mm1 Alistair John Strachan
2004-02-04  0:00       ` 2.6.2-rc3-mm1 Bartlomiej Zolnierkiewicz
2004-02-04  0:17         ` Alistair John Strachan [this message]
2004-02-04  0:35           ` 2.6.2-rc3-mm1 Bartlomiej Zolnierkiewicz
2004-02-04  1:03             ` 2.6.2-rc3-mm1 Alistair John Strachan
2004-02-04  1:29               ` 2.6.2-rc3-mm1 Bartlomiej Zolnierkiewicz
     [not found]       ` <Pine.LNX.4.58.0402031941560.665@uberdeity>
2004-02-04 10:05         ` 2.6.2-rc3-mm1 Alistair John Strachan

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=200402040017.43787.s0348365@sms.ed.ac.uk \
    --to=s0348365@sms.ed.ac.uk \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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