From: Peter Williams <pwil3058@bigpond.net.au>
To: Peter Williams <pwil3058@bigpond.net.au>
Cc: "Brown, Len" <len.brown@intel.com>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
James Bottomley <James.Bottomley@steeleye.com>,
linux-scsi@vger.kernel.org
Subject: Re: 2.6.13-mm1: hangs during boot ...
Date: Sat, 03 Sep 2005 17:18:19 +1000 [thread overview]
Message-ID: <43194E3B.2050609@bigpond.net.au> (raw)
In-Reply-To: <4319403E.4050105@bigpond.net.au>
Peter Williams wrote:
> Brown, Len wrote:
>
>>
>>
>>> Brown, Len wrote:
>>>
>>>>>> [ 279.662960] [<c02d5c74>] wait_for_completion+0xa4/0x110
>>>>
>>>>
>>>>
>>>> possibly a missing interrupt?
>>>>
>>>>
>>>>
>>>>> CONFIG_ACPI=y
>>>>
>>>>
>>>>
>>>> any difference if booted with "acpi=off" or "acpi=noirq"?
>>>
>>>
>>> Yes. In both cases, the system appears to boot normally but I'm
>>> unable to login or connect via ssh. Also there's a "device not
>>> ready" message after the scsi initialization which I don't normally
>>> see. I've attached the scsi initialization output. The PF_NETLINK
>>> error messages after the login prompt in this output are created
>>> whenever I try to log in or connect via ssh.
>>
>>
>>
>> Please confirm that vanilla 2.6.13 has none of these symptoms.
>
>
> That's correct. 2.6.13 exhibits none of these symptoms.
>
>> Please apply just the ACPI part of the 2.6.13-mm1 patch to see if
>> these issues are caused by that or if they are caused by something
>> else in the mm patch.
>>
>> http://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13/2.6.13-mm1/broken-out/git-acpi.patch
>>
>
>
> OK. I'll get back to you shortly.
I am able to confirm that the problem occurs with vanilla 2.5.13 after I
apply the above patch.
Peter
--
Peter Williams pwil3058@bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
next prev parent reply other threads:[~2005-09-03 7:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-03 5:37 Brown, Len
2005-09-03 6:18 ` Peter Williams
2005-09-03 7:18 ` Peter Williams [this message]
2005-09-03 8:19 ` Len Brown
2005-09-03 9:28 ` Peter Williams
2005-09-03 9:48 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2005-09-03 15:57 Brown, Len
2005-09-03 22:48 ` Peter Williams
[not found] <fa.qs5cahs.i2khgm@ifi.uio.no>
[not found] ` <fa.fm9i4v6.1ekchhm@ifi.uio.no>
2005-09-03 13:24 ` Reuben Farrelly
2005-09-03 13:51 ` Peter Williams
2005-09-03 16:14 ` James Bottomley
2005-09-04 16:32 ` James Bottomley
2005-09-05 8:37 ` Reuben Farrelly
2005-09-03 4:22 Brown, Len
2005-09-03 4:58 ` Peter Williams
2005-09-03 5:25 ` Andrew Morton
2005-09-02 12:54 Peter Williams
2005-09-02 20:11 ` Andrew Morton
2005-09-03 3:51 ` Peter Williams
2005-09-03 4:16 ` Andrew Morton
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=43194E3B.2050609@bigpond.net.au \
--to=pwil3058@bigpond.net.au \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®