public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: linuxx <linuxx@eresmas.net>
To: kernel <linux-kernel@vger.kernel.org>
Subject: Hi all, a strange full lock in SMP-kernel 2.4.6 and 2.4.5
Date: Sat, 7 Jul 2001 02:13:56 +0100	[thread overview]
Message-ID: <20010707021356.A2232@eresmas.net> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=es_ES, Size: 2567 bytes --]

Well Full lock in 2.4.5 and .6 when in a SMP intel p III 500mhz when i try to print any file in a epson 760 usb and parport
printer.  
I put in antecedents . With 2.4.3 and before the printer via usb or partport print ok . In 2.4.5-6 when i try to send
anything to /dev/usb/lp0 like cat a.txt > /dev/usb/lp0 the system fail or if i do in lpr same . I have no problem if i use parport whit the sames kernels .I have all right configured. With the same computer in other distribution .Same kernel = same lock .Of course the LPRng and gcc are 
all compiled in this machine and work right for months , both stables versions.I put the only trace y can get for the lock.
I hope help something for any other thing i not subscribed to kernel list so i like to know any answer you can give. THANKS

CPU:    0
EIP:    0010:[<d084acd1>]
EFLAGS: 00000086
eax: cd747600  ebx: cd1d42a0  ecx: 00000001  edx: cd747600
esi: cd1d41fc  edi: 00000000  ebp: 00000004  esp: cd077f34
ds: 0018  es: 0018  ss:0018
Process cat (pid: 378, stackpage=cd077000)
Stack: 0000017a 00000000 00000005 00000000 00000206 cd1d41a0 cd8f0000 00000000
       00000004 d0837aac cd1d41fc d084e411 cd1d41fc 00000000 cdec8c60 ffffffea
       00000000 00000004 c013a1c6 cdec8c60 0804c860 00000004 cdec8c80 00000025

Call Trace: [<013a1c6>] [<c0106ea7>]
Code: 80 7b 24 00 f3 90 7e f8 e9 e0 d0 ff ff 80 bf 80 00 00 00 00
console shuts up ...
<unfinished ...>
+++ killed by SIGSEGV +++
	      


-- 

Lee y algo aprenderás:

#----------------------------------------------------------------------
I used to think romantic love was a neurosis shared by two, a supreme
foolishness.  I no longer thought that.  There's nothing foolish in
loving anyone.  Thinking you'll be loved in return is what's foolish.
		-- Rita Mae Brown
#----------------------------------------------------------------------


 Luis Toro Teijeiro                                       THANKS FOR YOUR TIME.

               ()
               (o_|||
AÑO 3021 del   //\ |   demoniaco.
            <<-V_/_| 

ICQ : 42466380
pasate por http://www.gulic.org  y veras Canarias y los linuxeros
http://jaya.dyndns.org  ------pagina personal
Firma gnupg disponible en https://jaya.dyndns.org/linux/GNUPG/
GnupgFingerprint: 8F06 3E9A F610 89BF 0B09  3DEB 0C7E 9AE1 6CE0 B251 
                              Windows Where do you want to go today?
                              MacOS   Where do you want to be tomorrow?
                              Linux           Are you coming, or what?
    

    

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

             reply	other threads:[~2001-07-07  1:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-07  1:13 linuxx [this message]
2001-07-07  3:53 ` Hi all, a strange full lock in SMP-kernel 2.4.6 and 2.4.5 Pete Toscano
2001-07-07 20:34   ` Pete Toscano

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=20010707021356.A2232@eresmas.net \
    --to=linuxx@eresmas.net \
    --cc=linux-kernel@vger.kernel.org \
    /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