From: Ingo Molnar <mingo@elte.hu>
To: Mark_H_Johnson@raytheon.com
Cc: Bill Huey <bhuey@lnxw.com>, Adam Heath <doogie@debian.org>,
"K.R. Foley" <kr@cybsft.com>,
linux-kernel@vger.kernel.org,
Florian Schmidt <mista.tapas@gmx.net>,
Fernando Pablo Lopez-Lezcano <nando@ccrma.Stanford.EDU>,
Lee Revell <rlrevell@joe-job.com>,
Rui Nuno Capela <rncbc@rncbc.org>,
Thomas Gleixner <tglx@linutronix.de>,
Michal Schmidt <xschmi00@stud.feec.vutbr.cz>
Subject: Re: [patch] Real-Time Preemption, -RT-2.6.9-rc4-mm1-U6
Date: Tue, 19 Oct 2004 19:40:50 +0200 [thread overview]
Message-ID: <20041019174050.GA18998@elte.hu> (raw)
In-Reply-To: <OF684A90CB.5A611764-ON86256F32.005DA19F@raytheon.com>
* Mark_H_Johnson@raytheon.com <Mark_H_Johnson@raytheon.com> wrote:
> Booted to single user and was able to get some network operations
> going with this version (w/ previously mentioned update). However, at
> the step where I start CUPS, I got a number of traces on the display
> referring to parport_pc related function calls [but I don't use a
> parallel printer...]. It ended with:
thanks for the logs - there are some semaphore assumptions in
ieee1284.c, it should use completions & wait_for_completion_timeout()
too. The workaround is to disable CONFIG_PARPORT_1284. (or
CONFIG_PARPORT altogether.)
Ingo
next prev parent reply other threads:[~2004-10-19 17:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 17:14 Mark_H_Johnson
2004-10-19 17:40 ` Ingo Molnar [this message]
2004-10-19 18:05 ` K.R. Foley
-- strict thread matches above, loose matches on Subject: below --
2004-10-12 9:15 [patch] VP-2.6.9-rc4-mm1-T6 Ingo Molnar
2004-10-12 12:33 ` Ingo Molnar
2004-10-12 19:54 ` [patch] VP-2.6.9-rc4-mm1-T8 Ingo Molnar
2004-10-13 6:15 ` [patch] VP-2.6.9-rc4-mm1-T9 Ingo Molnar
2004-10-14 0:24 ` [patch] Real-Time Preemption, -VP-2.6.9-rc4-mm1-U0 Ingo Molnar
2004-10-14 14:31 ` [patch] Real-Time Preemption, -VP-2.6.9-rc4-mm1-U1 Ingo Molnar
2004-10-14 23:42 ` [patch] Real-Time Preemption, -VP-2.6.9-rc4-mm1-U2 Ingo Molnar
2004-10-15 10:26 ` [patch] Real-Time Preemption, -VP-2.6.9-rc4-mm1-U3 Ingo Molnar
2004-10-16 15:33 ` [patch] Real-Time Preemption, -VP-2.6.9-rc4-mm1-U4 Ingo Molnar
2004-10-18 14:50 ` [patch] Real-Time Preemption, -RT-2.6.9-rc4-mm1-U5 Ingo Molnar
2004-10-19 12:46 ` [patch] Real-Time Preemption, -RT-2.6.9-rc4-mm1-U6 Ingo Molnar
2004-10-19 14:46 ` Ingo Molnar
2004-10-19 15:23 ` Rui Nuno Capela
2004-10-19 15:44 ` Thomas Gleixner
2004-10-19 15:57 ` Ingo Molnar
2004-10-19 16:44 ` Thomas Gleixner
2004-10-19 17:58 ` Thomas Gleixner
2004-10-19 18:26 ` Ingo Molnar
2004-10-19 20:04 ` Thomas Gleixner
2004-10-19 15:50 ` Ingo Molnar
2004-10-19 16:01 ` K.R. Foley
2004-10-19 16:20 ` Ingo Molnar
2004-10-19 16:28 ` Ingo Molnar
2004-10-19 16:31 ` Ingo Molnar
2004-10-19 17:17 ` Ingo Molnar
2004-10-19 16:50 ` Florian Schmidt
2004-10-19 16:56 ` Ingo Molnar
2004-10-19 17:49 ` Florian Schmidt
2004-10-19 15:48 ` Thomas Gleixner
2004-10-19 16:26 ` Ingo Molnar
2004-10-19 16:39 ` Thomas Gleixner
2004-10-19 17:22 ` Adam Heath
2004-10-19 17:35 ` Ingo Molnar
2004-10-19 18:52 ` Adam Heath
2004-10-19 20:59 ` Lee Revell
2004-10-19 18:54 ` Adam Heath
2004-10-19 20:52 ` Michal Schmidt
2004-10-20 16:31 ` Adam Heath
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=20041019174050.GA18998@elte.hu \
--to=mingo@elte.hu \
--cc=Mark_H_Johnson@raytheon.com \
--cc=bhuey@lnxw.com \
--cc=doogie@debian.org \
--cc=kr@cybsft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mista.tapas@gmx.net \
--cc=nando@ccrma.Stanford.EDU \
--cc=rlrevell@joe-job.com \
--cc=rncbc@rncbc.org \
--cc=tglx@linutronix.de \
--cc=xschmi00@stud.feec.vutbr.cz \
/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
Powered by JetHome