From: Lee Howard <faxguy@deanox.com>
To: Tim Waugh <twaugh@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: lp oops with kernel 2.4.15-pre2
Date: Tue, 13 Nov 2001 10:24:17 -0700 [thread overview]
Message-ID: <3.0.6.32.20011113102417.00e29540@server.deanox.com> (raw)
In-Reply-To: <20011113113029.N25718@redhat.com>
In-Reply-To: <3.0.6.32.20011112165757.00e404b0@server.deanox.com> <3.0.6.32.20011112165757.00e404b0@server.deanox.com>
At 11:30 AM 11/13/01 +0000, Tim Waugh wrote:
>On Mon, Nov 12, 2001 at 04:57:57PM -0700, Lee Howard wrote:
>
>> Nov 12 12:02:44 zelda kernel: EIP: 0010:[kmem_cache_alloc+100/176]
>[...]
>> Nov 12 12:02:44 zelda kernel: Call Trace: [d_alloc+23/368] [sprintf+18/32]
>> [sock_map_fd+153/352] [unix_create+92/112] [sock_create+214/256]
>> Nov 12 12:02:44 zelda kernel: [dentry_open+346/384] [sys_socket+41/80]
>> [sys_socketcall+96/464] [do_page_fault+0/1200] [error_code+52/60]
>> [system_call+51/56]
>
>This doesn't seem to be lp- or parport-related. What else was the
>machine doing at the time?
This oops occurred at the moment of processing/handling a print job. The
print jobs are processed via a Samba printer share. The system is also
constantly running a MySQL database that is accessed via Apache+PHP.
So, the system is running MySQL, Samba, Apache, PHP, sendmail, lpd, and
various other things standard on an updated RedHat 7.0 system (I'm
upgrading kernels via tarball).
Lee.
prev parent reply other threads:[~2001-11-13 17:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-12 23:57 Lee Howard
2001-11-13 11:30 ` Tim Waugh
2001-11-13 17:03 ` Randy.Dunlap
2001-11-13 17:24 ` Lee Howard [this message]
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=3.0.6.32.20011113102417.00e29540@server.deanox.com \
--to=faxguy@deanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=twaugh@redhat.com \
/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®