Re: Hi all, a strange full lock in SMP-kernel 2.4.6 and 2.4.5

2001-07-07 Thread Pete Toscano

Just to follow up to myself, after futher testing, it looks like it's an
SMP-related problem.  I'm not yet sure if it's an SMP-Via chipset
problem or just an SMP problem.  I've heard from two people with this
same problem.  I think one of them has a Via chipset and I'm not sure
about the other one.  

Can anybody look into this or give me a good brain dump on how I can fix
it?

Thanks,
pete

On Fri, 06 Jul 2001, Pete Toscano wrote:

> I think I've seen this same problem, at least with regards to USB
> printing.  Yesterday, I traced the problem down to a patch to usb-uhci.c
> in the transition from 2.4.3 to 2.4.4.  The problem persists today.  A
> work around for this problem is to use the alternate UHCI driver
> (uhci.o).
> 
> What motherboard and chipset are you using.  I use the Tyan Tiger 133
> motherboard with the VIA Apollo Pro 133a chipset.  Someone else who I
> heard from uses another VIA-based chipset (I think, he never replied to
> my question).  Maybe this is a VIA-related problem, like the APIC
> problem is.  (Do you use "noapic" when you boot?  He and I both have SMP
> systems too)
> 
> I posted something on the linux-usb list yesterday about this problem
> and with all the info I was able to track down, but I have yet to see
> any response.  I've taken this as far as I can by myself.  I don't know
> enough about kernel programming or about USB to check the code in
> usb-uhci.c, but I'm more than happy to help by providing information
> and/or testing potential patches/fixes.
> 
> pete
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



Re: Hi all, a strange full lock in SMP-kernel 2.4.6 and 2.4.5

2001-07-07 Thread Pete Toscano

Just to follow up to myself, after futher testing, it looks like it's an
SMP-related problem.  I'm not yet sure if it's an SMP-Via chipset
problem or just an SMP problem.  I've heard from two people with this
same problem.  I think one of them has a Via chipset and I'm not sure
about the other one.  

Can anybody look into this or give me a good brain dump on how I can fix
it?

Thanks,
pete

On Fri, 06 Jul 2001, Pete Toscano wrote:

 I think I've seen this same problem, at least with regards to USB
 printing.  Yesterday, I traced the problem down to a patch to usb-uhci.c
 in the transition from 2.4.3 to 2.4.4.  The problem persists today.  A
 work around for this problem is to use the alternate UHCI driver
 (uhci.o).
 
 What motherboard and chipset are you using.  I use the Tyan Tiger 133
 motherboard with the VIA Apollo Pro 133a chipset.  Someone else who I
 heard from uses another VIA-based chipset (I think, he never replied to
 my question).  Maybe this is a VIA-related problem, like the APIC
 problem is.  (Do you use noapic when you boot?  He and I both have SMP
 systems too)
 
 I posted something on the linux-usb list yesterday about this problem
 and with all the info I was able to track down, but I have yet to see
 any response.  I've taken this as far as I can by myself.  I don't know
 enough about kernel programming or about USB to check the code in
 usb-uhci.c, but I'm more than happy to help by providing information
 and/or testing potential patches/fixes.
 
 pete
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



Re: Hi all, a strange full lock in SMP-kernel 2.4.6 and 2.4.5

2001-07-06 Thread Pete Toscano

I think I've seen this same problem, at least with regards to USB
printing.  Yesterday, I traced the problem down to a patch to usb-uhci.c
in the transition from 2.4.3 to 2.4.4.  The problem persists today.  A
work around for this problem is to use the alternate UHCI driver
(uhci.o).

What motherboard and chipset are you using.  I use the Tyan Tiger 133
motherboard with the VIA Apollo Pro 133a chipset.  Someone else who I
heard from uses another VIA-based chipset (I think, he never replied to
my question).  Maybe this is a VIA-related problem, like the APIC
problem is.  (Do you use "noapic" when you boot?  He and I both have SMP
systems too)

I posted something on the linux-usb list yesterday about this problem
and with all the info I was able to track down, but I have yet to see
any response.  I've taken this as far as I can by myself.  I don't know
enough about kernel programming or about USB to check the code in
usb-uhci.c, but I'm more than happy to help by providing information
and/or testing potential patches/fixes.

pete

On Sat, 07 Jul 2001, linuxx wrote:

> 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:[]
> EFLAGS: 0086
> eax: cd747600  ebx: cd1d42a0  ecx: 0001  edx: cd747600
> esi: cd1d41fc  edi:   ebp: 0004  esp: cd077f34
> ds: 0018  es: 0018  ss:0018
> Process cat (pid: 378, stackpage=cd077000)
> Stack: 017a  0005  0206 cd1d41a0 cd8f 
>0004 d0837aac cd1d41fc d084e411 cd1d41fc  cdec8c60 ffea
> 0004 c013a1c6 cdec8c60 0804c860 0004 cdec8c80 0025
> 
> Call Trace: [<013a1c6>] []
> Code: 80 7b 24 00 f3 90 7e f8 e9 e0 d0 ff ff 80 bf 80 00 00 00 00
> console shuts up ...
> 
> +++ killed by SIGSEGV +++
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



Hi all, a strange full lock in SMP-kernel 2.4.6 and 2.4.5

2001-07-06 Thread linuxx

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:[]
EFLAGS: 0086
eax: cd747600  ebx: cd1d42a0  ecx: 0001  edx: cd747600
esi: cd1d41fc  edi:   ebp: 0004  esp: cd077f34
ds: 0018  es: 0018  ss:0018
Process cat (pid: 378, stackpage=cd077000)
Stack: 017a  0005  0206 cd1d41a0 cd8f 
   0004 d0837aac cd1d41fc d084e411 cd1d41fc  cdec8c60 ffea
    0004 c013a1c6 cdec8c60 0804c860 0004 cdec8c80 0025

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

+++ 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?




 PGP signature


Hi all, a strange full lock in SMP-kernel 2.4.6 and 2.4.5

2001-07-06 Thread linuxx

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: 0086
eax: cd747600  ebx: cd1d42a0  ecx: 0001  edx: cd747600
esi: cd1d41fc  edi:   ebp: 0004  esp: cd077f34
ds: 0018  es: 0018  ss:0018
Process cat (pid: 378, stackpage=cd077000)
Stack: 017a  0005  0206 cd1d41a0 cd8f 
   0004 d0837aac cd1d41fc d084e411 cd1d41fc  cdec8c60 ffea
    0004 c013a1c6 cdec8c60 0804c860 0004 cdec8c80 0025

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?




 PGP signature


Re: Hi all, a strange full lock in SMP-kernel 2.4.6 and 2.4.5

2001-07-06 Thread Pete Toscano

I think I've seen this same problem, at least with regards to USB
printing.  Yesterday, I traced the problem down to a patch to usb-uhci.c
in the transition from 2.4.3 to 2.4.4.  The problem persists today.  A
work around for this problem is to use the alternate UHCI driver
(uhci.o).

What motherboard and chipset are you using.  I use the Tyan Tiger 133
motherboard with the VIA Apollo Pro 133a chipset.  Someone else who I
heard from uses another VIA-based chipset (I think, he never replied to
my question).  Maybe this is a VIA-related problem, like the APIC
problem is.  (Do you use noapic when you boot?  He and I both have SMP
systems too)

I posted something on the linux-usb list yesterday about this problem
and with all the info I was able to track down, but I have yet to see
any response.  I've taken this as far as I can by myself.  I don't know
enough about kernel programming or about USB to check the code in
usb-uhci.c, but I'm more than happy to help by providing information
and/or testing potential patches/fixes.

pete

On Sat, 07 Jul 2001, linuxx wrote:

 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: 0086
 eax: cd747600  ebx: cd1d42a0  ecx: 0001  edx: cd747600
 esi: cd1d41fc  edi:   ebp: 0004  esp: cd077f34
 ds: 0018  es: 0018  ss:0018
 Process cat (pid: 378, stackpage=cd077000)
 Stack: 017a  0005  0206 cd1d41a0 cd8f 
0004 d0837aac cd1d41fc d084e411 cd1d41fc  cdec8c60 ffea
 0004 c013a1c6 cdec8c60 0804c860 0004 cdec8c80 0025
 
 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 +++
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/