From: Reuben Farrelly <reuben-lkml@reub.net>
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: Sun, 04 Sep 2005 01:24:18 +1200 [thread overview]
Message-ID: <4319A402.7030705@reub.net> (raw)
In-Reply-To: <fa.fm9i4v6.1ekchhm@ifi.uio.no>
Hi Peter,
On 3/09/2005 4:59 a.m., Peter Williams 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
Are you seeing this "Device not ready" message appear over and over, or just
the once?
I am seeing it fill up my messages log as it is logging 1 or so messages each
minute. I've emailed the SCSI maintainer James Bottomley twice about it but
had no response either time.
The SCSI device I have is:
Sep 3 22:14:40 tornado kernel: Vendor: SONY Model: CD-RW CRX145S Rev: 1.0b
As for the inability to log in, this bug may be relevant, given I also had
that problem:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=166422
There are fixes in the pipeline for util-linux audit interaction in Fedora as
well. I know because I reported those too ;)
> 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.
The workaround by enabling audit support, but obviously a better fix is in the
pipeline..
I'm surprised more people aren't discovering these 'interactions' due to
having audit not turned on. Does everyone build audit into their kernels?
reuben
next parent reply other threads:[~2005-09-03 13:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.qs5cahs.i2khgm@ifi.uio.no>
[not found] ` <fa.fm9i4v6.1ekchhm@ifi.uio.no>
2005-09-03 13:24 ` Reuben Farrelly [this message]
2005-09-03 13:51 ` 2.6.13-mm1: hangs during boot 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 15:57 Brown, Len
2005-09-03 22:48 ` Peter Williams
-- strict thread matches above, loose matches on Subject: below --
2005-09-03 5:37 Brown, Len
2005-09-03 6:18 ` Peter Williams
2005-09-03 7:18 ` Peter Williams
2005-09-03 8:19 ` Len Brown
2005-09-03 9:28 ` Peter Williams
2005-09-03 9:48 ` Andrew Morton
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=4319A402.7030705@reub.net \
--to=reuben-lkml@reub.net \
--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 \
--cc=pwil3058@bigpond.net.au \
/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