Messages in this thread |  | | | Date | Sat, 03 Sep 2005 23:51:45 +1000 | | From | Peter Williams <> | | Subject | Re: 2.6.13-mm1: hangs during boot ... |
| |
Reuben Farrelly wrote: > 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?
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
-- Peter Williams pwil3058@bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious." -- Ambrose Bierce - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |