From: Alex Romosan <romosan@sycorax.lbl.gov>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Alex Romosan <romosan@sycorax.lbl.gov>, linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at drivers/serial/core.c:1067 with 2.5.44
Date: 27 Oct 2002 08:43:07 -0800 [thread overview]
Message-ID: <87adkzde90.fsf@sycorax.lbl.gov> (raw)
In-Reply-To: <20021027163307.A9553@flint.arm.linux.org.uk> (message from Russell King on Sun, 27 Oct 2002 16:33:07 +0000)
Russell King <rmk@arm.linux.org.uk> writes:
> On Sun, Oct 27, 2002 at 08:25:53AM -0800, Alex Romosan wrote:
> > Oct 27 07:39:54 trinculo kernel: kernel BUG at drivers/serial/core.c:1067!
>
> Someone called uart_set_termios without the BKL held, violating the locking
> requirements.
>
> Unfortunately:
>
> 1. You appear to be running a klogd that'll translate the addresses.
i am not sure what this means. i am running debian unstable. i just
realized i ran ksymoops with the -x option (if it makes any difference
i can resend the oops without -x).
> 2. your ksymoops doesn't seem to know what modules are loaded.
isn't this the list of modules loaded at the time?
Oct 27 07:39:54 trinculo kernel: 3c574_cs irtty irda autofs4 microcode ppp_async uhci-hcd ohci-hcd usbcore nls_cp437 vfat snd-pcm-oss snd-mixer-oss snd-ymfpci snd-pcm snd-mpu401-uart snd-rawmidi snd-ac97-codec snd-opl3-lib snd-timer snd-hwdep snd-seq-device snd soundcore
--alex--
--
| I believe the moment is at hand when, by a paranoiac and active |
| advance of the mind, it will be possible (simultaneously with |
| automatism and other passive states) to systematize confusion |
| and thus to help to discredit completely the world of reality. |
next prev parent reply other threads:[~2002-10-27 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-27 16:25 kernel BUG at drivers/serial/core.c:1067 with 2.5.44 Alex Romosan
2002-10-27 16:33 ` Russell King
2002-10-27 16:43 ` Alex Romosan [this message]
2002-10-27 17:12 ` Russell King
2002-10-27 19:12 ` Alex Romosan
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=87adkzde90.fsf@sycorax.lbl.gov \
--to=romosan@sycorax.lbl.gov \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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.