All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rlandley@parallels.com>
To: Jens Axboe <jaxboe@fusionio.com>
Cc: Pete Clements <clem@clem.clem-digital.net>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: Commit 7eaceaccab5f40 causing boot hang.
Date: Wed, 30 Mar 2011 08:52:04 -0500	[thread overview]
Message-ID: <4D933584.5050005@parallels.com> (raw)
In-Reply-To: <4D931634.5030807@fusionio.com>

On 03/30/2011 06:38 AM, Jens Axboe wrote:
> On 2011-03-30 08:06, Rob Landley wrote:
>> On 03/29/2011 10:51 AM, Pete Clements wrote:
>>> Quoting Jens Axboe
>>>   > 
>>>   > On 2011-03-29 16:13, Rob Landley wrote:
>>>   > > On 03/29/2011 08:59 AM, Jens Axboe wrote:
>>>   > >> On 2011-03-29 10:52, Rob Landley wrote:
>>>   > >>> I'm booting all this under kvm or qemu, by the way:
>>>   > >>>
>>>   > >>> qemu-system-x86_64 -m 1024 -kernel arch/x86/boot/bzImage \
>>>   > >>>   -hda ~/sid.ext3 -append "root=/dev/hda rw"
>>>   > >>>
>>>   > >>> Sometimes with init=/bin/bash in that last quoted bit.  The root
>>>   > >>> filesystem's debian sid but that's probably not relevant because it
>>>   > >>> worked fine with .38.
>>>   > >>
>>>   > >> Does this help?
>>>   > >>
>>>   > >> diff --git a/drivers/ide/ide-io.c b/drivers/ide/ide-io.c
>>>   > >> index 0e406d73..ca27d30 100644
>>>   > >> --- a/drivers/ide/ide-io.c
>>>   > >> +++ b/drivers/ide/ide-io.c
>>>   > >> @@ -570,8 +570,7 @@ void ide_requeue_and_plug(ide_drive_t *drive, struct request *rq)
>>>   > >>  	spin_unlock_irqrestore(q->queue_lock, flags);
>>>   > >>  
>>>   > >>  	/* Use 3ms as that was the old plug delay */
>>>   > >> -	if (rq)
>>>   > >> -		blk_delay_queue(q, 3);
>>>   > >> +	blk_delay_queue(q, 3);
>>>   > >>  }
>>>   > >>  
>>>   > >>  static int drive_is_ready(ide_drive_t *drive)
>>>   > >>
>>>   > > 
>>>   > > Nope, still hung the same way.
>>>   > 
>>>   > Funky. I'll try and reproduce this tonight.
>>>   > 
>>>   > -- 
>>>   > Jens Axboe
>>>   > 
>>>
>>> I have had a similiar problem (reported earlier) unable to boot.
>>> With git15-18 hung with IDE drives (hda), git19-21 moved the hang down to
>>> the IDE CDROM (hdc). Applied the above patch and now booted into git21 without
>>> any hang and all appears ok.
>>
>> It may have made it better for me, it's hard to tell.
>>
>> I did a fresh pull, re-applied the patch, and tried again with
>> init=/bin/sh and it booted to the shell prompt... which then hung when I
>> did "ls -l /".
>>
>> If I let it boot normally, init announces itself, gives a spurious
>> warning about a fstab field (which it's been doing for a while, my fault
>> but harmless), then hangs.
>>
>>> This is i386, UP.
>>
>> I'm doing x86-64 SMP.
> 
> I think we have the same issue the other location. How about this, then:
> 
> diff --git a/drivers/ide/ide-io.c b/drivers/ide/ide-io.c
> index 0e406d73..4978ec3 100644
> --- a/drivers/ide/ide-io.c
> +++ b/drivers/ide/ide-io.c
> @@ -549,12 +549,11 @@ plug_device:
>  	spin_unlock_irq(&hwif->lock);
>  	ide_unlock_host(host);
>  plug_device_2:
> +	blk_delay_queue(q, queue_run_ms);
>  	spin_lock_irq(q->queue_lock);
>  
> -	if (rq) {
> +	if (rq)
>  		blk_requeue_request(q, rq);
> -		blk_delay_queue(q, queue_run_ms);
> -	}
>  }
>  
>  void ide_requeue_and_plug(ide_drive_t *drive, struct request *rq)
> @@ -570,8 +569,7 @@ void ide_requeue_and_plug(ide_drive_t *drive, struct request *rq)
>  	spin_unlock_irqrestore(q->queue_lock, flags);
>  
>  	/* Use 3ms as that was the old plug delay */
> -	if (rq)
> -		blk_delay_queue(q, 3);
> +	blk_delay_queue(q, 3);
>  }
>  
>  static int drive_is_ready(ide_drive_t *drive)
> 

Did a fresh pull and applied that patch.  (It conflicts with your
previous one, but looks like it includes it.)

Now it hangs after the "EXT3-fs: barriers not enabled" line, doesn't
make it to init.

Rob

  reply	other threads:[~2011-03-30 13:52 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29  6:19 Commit 7eaceaccab5f40 causing boot hang Rob Landley
2011-03-29  6:19 ` Rob Landley
2011-03-29  6:35 ` Jens Axboe
2011-03-29  8:52   ` Rob Landley
2011-03-29 13:59     ` Jens Axboe
2011-03-29 14:13       ` Rob Landley
2011-03-29 14:16         ` Jens Axboe
2011-03-29 15:51           ` Pete Clements
2011-03-29 15:51             ` Pete Clements
2011-03-30  6:06             ` Rob Landley
2011-03-30 11:38               ` Jens Axboe
2011-03-30 13:52                 ` Rob Landley [this message]
2011-03-31  9:02                   ` Jens Axboe
2011-03-31  9:11                     ` Rob Landley
2011-03-31 10:07                       ` Jens Axboe
2011-03-31 10:37                         ` Jens Axboe
2011-03-31 10:47                           ` Rob Landley
2011-03-31 11:09                             ` Jens Axboe
2011-04-01  3:11                               ` Nicholas A. Bellinger
2011-04-03  7:05                                 ` Andreas Mohr
2011-04-01 12:26                               ` Mark Lord
2011-04-09  2:56                               ` Rob Landley
2011-04-09  3:00                                 ` Jens Axboe
2011-03-31 12:11                           ` Tejun Heo
2011-03-31 12:33                             ` Jens Axboe
2011-03-31 13:09                               ` Richard Kennedy
2011-03-31 13:18                                 ` Jens Axboe
2011-03-31 13:23                                   ` Richard Kennedy
2011-03-31 13:33                                     ` Jens Axboe
2011-03-31 14:49                                       ` Richard Kennedy
2011-04-04 13:47                                         ` Richard Kennedy
2011-04-13 10:25                                           ` Richard Kennedy
2011-04-13 10:36                                             ` Jens Axboe
2011-04-06 11:55                               ` Rob Landley

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=4D933584.5050005@parallels.com \
    --to=rlandley@parallels.com \
    --cc=clem@clem.clem-digital.net \
    --cc=jaxboe@fusionio.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.