Processor-dependent bug in kernel 2.4.0-testX (floating pointexception)

2000-11-15 Thread Giacomo Mulas

I stumbled upon a strange bug in the 2.4.0-test[9-10] kernels,
which only happens on PII (Deschutes) processors: right after boot, it
starts spitting "floating point exception"s all over the place, every time
aborting the program it was executing. This begins to happen very early,
before any modules have been loaded. I do not know whether this bug was
present in previous 2.4.0-test versions.
Notably, the kernels are recompiled with the same source and
options of the one that is currently running without problems on my laptop
and on all other PIIIs I tried it on, except for the processor option,
which is set to "Pentium III" for PIIIs and to
"Pentium-Pro/Celeron/Pentium II" for PIIs. I just did:

cp .config .config.myconfig
make mrproper
mv .config.myconfig .config
make menuconfig

make dep
make bzImage
make modules

floating point exceptions when fscking partitions, when doing depmod...
No oopses.

This happens exactly in the same way on two different computers with the
same hardware configuration, so I don't think it is a hardware bug, and
both work fine with a 2.2.17 kernel. The floating point exceptions are not
deterministic, they do not always happen at the same point in the boot
process, but are random and frequent. Any program that runs for a long
enough time (e.g. a tripwire run) invariably triggers it.

Please ask any more needed information and I will gladly provide it.

Bye
Giacomo Mulas

________

Giacomo Mulas <[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]>


OSSERVATORIO  ASTRONOMICO
Str. 54, Loc. Poggio dei Pini * 09012 Capoterra (CA)

Tel.: +39 070 71180 216 Fax : +39 070 71180 222


"When the storms are raging around you, stay right where you are"
 (Freddy Mercury)


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



BUG in 2.4.0-t10

2000-11-13 Thread Giacomo Mulas
  a:   47inc%edi
Code;  c012a0e5 
   b:   83 c6 0c  add$0xc,%esi
Code;  c012a0e8 
   e:   83 ff 09  cmp$0x9,%edi
Code;  c012a0eb 
  11:   0f 86 ef 00 00 00 jbe106 <_EIP+0x106> c012a1e0 
<__alloc_pages+34/2d0>

invalid operand: 
CPU:0
EIP:0010:[]
EFLAGS: 00010282
eax: 001f   ebx: c1361a04   ecx: c15e8000   edx: 
esi: c1361a20   edi: 5561   ebp:    esp: c15e9f80
ds: 0018   es: 0018   ss: 0018
Process kflushd (pid: 5, stackpage=c15e9000)
Stack: c02190ea c0219398 0054 c1361a04 c1361a20 5561 0007 5561 
   0006  0001 c0128d75 c012a4db c0128f3b  0001 
   c15e8000 0008e000     c013127e 0003 
Call Trace: [] [] [] [] [] 
[] [] 
Code: 0f 0b 83 c4 0c 89 f6 89 d8 2b 05 b8 6e 2e c0 69 c0 f1 f0 f0 

>>EIP; c0129bc9 <__free_pages_ok+49/338>   <=
Trace; c02190ea 
Trace; c0219398 
Trace; c0128d75 
Trace; c012a4db <__free_pages+13/14>
Trace; c0128f3b 
Trace; c013127e 
Trace; c01089cc 
Code;  c0129bc9 <__free_pages_ok+49/338>
 <_EIP>:
Code;  c0129bc9 <__free_pages_ok+49/338>   <=
   0:   0f 0b ud2a  <=
Code;  c0129bcb <__free_pages_ok+4b/338>
   2:   83 c4 0c  add$0xc,%esp
Code;  c0129bce <__free_pages_ok+4e/338>
   5:   89 f6 mov%esi,%esi
Code;  c0129bd0 <__free_pages_ok+50/338>
   7:   89 d8 mov%ebx,%eax
Code;  c0129bd2 <__free_pages_ok+52/338>
   9:   2b 05 b8 6e 2e c0 sub0xc02e6eb8,%eax
Code;  c0129bd8 <__free_pages_ok+58/338>
   f:   69 c0 f1 f0 f0 00 imul   $0xf0f0f1,%eax,%eax

invalid operand: 
CPU:0
EIP:0010:[]
EFLAGS: 00010286
eax: 001c   ebx: c1361a20   ecx: cb88c000   edx: c0360160
esi: c1361a04   edi: c1daccdc   ebp: 01dd   esp: cb88de18
ds: 0018   es: 0018   ss: 0018
Process tripwire (pid: 30247, stackpage=cb88d000)
Stack: c021896a c0218c09 0214 c0270f58 c0271158 0001  c012a178 
   c0270f58  c0271160  0007 c012a2e9 c0271154  
   0001 0001 0040 0007 c144c0c0 0007 0007 0001 
Call Trace: [] [] [] [] [] 
[] [] 
   [] [] [] [] [] [] 
[] [] 
   [] 
Code: 0f 0b 83 c4 0c 31 c0 0f b3 46 18 8d 4e 28 8d 46 2c 39 46 2c 

>>EIP; c0128a9d<=
Trace; c021896a 
Trace; c0218c09 
Trace; c012a178 <__alloc_pages_limit+78/ac>
Trace; c012a2e9 <__alloc_pages+13d/2d0>
Trace; c012a490 <__get_free_pages+14/20>
Trace; c012722a 
Trace; c01273c0 
Trace; c013fca1 
Trace; c013ff66 
Trace; c014fd71 
Trace; c0137083 
Trace; c0137767 
Trace; c0137d4a <__user_walk+3a/54>
Trace; c0134bb1 
Trace; c012d677 
Trace; c010a2f3 
Code;  c0128a9d 
 <_EIP>:
Code;  c0128a9d<=
   0:   0f 0b ud2a  <=
Code;  c0128a9f 
   2:   83 c4 0c  add$0xc,%esp
Code;  c0128aa2 
   5:   31 c0 xor%eax,%eax
Code;  c0128aa4 
   7:   0f b3 46 18   btr%eax,0x18(%esi)
Code;  c0128aa8 
   b:   8d 4e 28  lea0x28(%esi),%ecx
Code;  c0128aab 
   e:   8d 46 2c  lea0x2c(%esi),%eax
Code;  c0128aae 
  11:   39 46 2c  cmp%eax,0x2c(%esi)


1 warning issued.  Results may not be reliable.

I hope I gave enough information to track down the problem. Let me know if
any more information/test are wanted to squash this bug, I will gladly
help. I am a developer, although not a kernel developer.

Thanks in advance

Giacomo Mulas

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



a single fragmented IP packet kills the 2.4.0-t12 kernel

2000-12-16 Thread Giacomo Mulas

It seems that a bad bug (in the netfilter code?) was exposed by
the changes from 2.4.0-t11 to t12. If a box has the ip_tables and
ip_conntrack modules loaded, sending it a single fragmented IP packet
(e.g. with "ping -s 65000") is enough to immediately freeze it. It does
not respond to the keyboard, does not write the oops(es) to disk... Some
people initially stumbled upon this when trying to use nfs, probably
because nfs uses large packets and therefore produces fragmented packets.
I also tried reverting the netfilter code to that of test11, but it dies
exactly in the same way, so that if the bug is in netfilter it was there
already.

By the way, the bug is only triggered when using netfilter in native mode:
the ipchains compatibility mode apparently works fine.

Does anybody have a clue? I need the stateful firewalling capabilities of
netfilter. I will gladly help, if possible. But I cannot connect a console
to the serial port to capture the oops...

And, since we are talking about fragments: where did the ip_always_defrag
switch that used to be in /proc/sys/net/ipv4 (in 2.2.x kernels) go? 

Bye, thanks

____

Giacomo Mulas <[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]>


OSSERVATORIO  ASTRONOMICO
Str. 54, Loc. Poggio dei Pini * 09012 Capoterra (CA)

Tel.: +39 070 71180 216 Fax : +39 070 71180 222


"When the storms are raging around you, stay right where you are"
 (Freddy Mercury)


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



kernel 2.4.4: BUG in ll_rw_blk.c?

2001-05-09 Thread Giacomo Mulas
_bh+87/116] [block_read_full_page+525/548] [add_to_page_cache_unique+198/208] 
[ext2_readpage+15/20] [ext2_get_block+0/1168] [generic_file_readahead+548/668] 
May  9 16:15:22 stampace kernel:[do_generic_file_read+838/1292] 
[generic_file_read+91/120] [file_read_actor+0/84] [sys_read+150/204] 
[system_call+51/56] 
May  9 16:15:22 stampace kernel: 
May  9 16:15:22 stampace kernel: Code: 0f 0b 83 c4 0c 83 7c 24 38 00 74 12 8b 44 24 38 
89 44 24 40 

Bye, thanks
Giacomo Mulas

_____

Giacomo Mulas <[EMAIL PROTECTED], [EMAIL PROTECTED]>
_

OSSERVATORIO  ASTRONOMICO
Str. 54, Loc. Poggio dei Pini * 09012 Capoterra (CA)

Tel.: +39 070 71180 216 Fax : +39 070 71180 222
_

"When the storms are raging around you, stay right where you are"
 (Freddy Mercury)
_

-
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/