All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory Ade <gkade@bigbrother.net>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] strange behavior with 1.0.5 on Linux 2.4.19?
Date: Thu Dec  5 21:35:02 2002	[thread overview]
Message-ID: <1039145680.1069.79.camel@pslgregory> (raw)
In-Reply-To: <20021109130628.B12935@sistina.com>

[-- Attachment #1: Type: text/plain, Size: 9288 bytes --]

On Sat, 2002-11-09 at 04:06, Heinz J . Mauelshagen wrote:
> On Thu, Nov 07, 2002 at 07:44:36PM -0800, Gregory Ade wrote:
> > Okay, I disabled high memory support (only change from production
> > kernel), rebooted with this test kernel, and tried to create a snapshot:
[snip]
> > It worked just fine:
[snip]
> > So I removed it:
[snip]
> > No kernel oops or BUG in the dmesg.
> > 
> > Again, the _ONLY DIFFERENCE_ between this test kernel and the production
> > kernel is the high-memory support option.  On the test kernel, it is
> > off, and on the production kernel, it is set to 64GB.
> > 
> > Hope this helps.

[snip]

> this proves my assumption right that something is fishy with the high
> memory support in your SMP environment.
> 
> I guess that it might work as well in case you make a single processor kernel
> _with_ high memory enabled and repeat the very same test and that it might
> be a highmem/smp problem still to be fixed.

Well, it's not solely an SMP thing.  I finally got an opportunity to
test a non-SMP high-memory kernel tonight, and it's the exact same
failure mode as the original problem report.  Here's a full report,
complete with the Oops and a run through ksymoops.

root@burpr(pts/0):~ 24 # uname -a
Linux burpr 2.4.19-2.burpr.test #1 Thu Dec 5 16:22:49 PST 2002 i686 unknown
root@burpr(pts/0):~ 25 # cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 15
model           : 1
model name      : Intel(R) Xeon(TM) CPU 1.60GHz
stepping        : 1
cpu MHz         : 1595.176
cache size      : 256 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
bogomips        : 3185.04

root@burpr(pts/0):~ 26 # free -tm
             total       used       free     shared    buffers     cached
Mem:          7580        132       7448          0         46         28
-/+ buffers/cache:         57       7523
Swap:         8191          0       8191
Total:       15772        132      15640
root@burpr(pts/0):~ 27 # lvcreate --snapshot --extents 512 --name tmp_snap /dev/vg00/tmp
lvcreate -- INFO: using default snapshot chunk size of 64 KB for "/dev/vg00/tmp_snap"
Segmentation fault

--->8--[ Oops output taken from dmesg ]-->8---

kernel BUG at vmalloc.c:236!
invalid operand: 0000
CPU:    0
EIP:    0010:[<c012caa6>]    Not tainted
EFLAGS: 00010246
eax: ffffffff   ebx: 00000000   ecx: 51eb851f   edx: 00000000
esi: 00000000   edi: f4f51a00   ebp: fffffff4   esp: f3ce9d20
ds: 0018   es: 0018   ss: 0018
Process lvcreate (pid: 740, stackpage=f3ce9000)
Stack: 00000000 00000000 f4f51a00 fffffff4 000001f0 f930f000 00000001 fffffff4
       c02eab14 c02eac7c 000001f0 00000001 c023ad1b 00000000 000001f2 00000163
       f4f51b6c 00000000 f4f51a00 f3ce9df8 c023adc8 f4f51a00 f4f51a00 000bd000
Call Trace:    [<c023ad1b>] [<c023adc8>] [<c0238870>] [<c023614c>] [<c01dad7f>]
  [<c01419f7>] [<c010867b>]

Code: 0f 0b ec 00 20 cb 29 c0 31 c0 e9 bf 01 00 00 6a 02 53 e8 9f

--->8--[ Oops output taken from dmesg ]-->8---

--->8--[ Oops output from ksymoops ]-->8---

ksymoops 2.4.1 on i686 2.4.19-2.burpr.test.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.19-2.burpr.test/ (default)
     -m /boot/System.map-2.4.19-2.burpr.test (default)

Warning: You did not tell me where to find symbol information.  I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc.  ksymoops -h explains the options.

Warning (compare_maps): mismatch on symbol usb_devfs_handle  , usbcore says f922a6f4, /lib/modules/2.4.19-2.burpr.test/kernel/drivers/usb/usbcore.o says f922a1b4.  Ignoring /lib/modules/2.4.19-2.burpr.test/kernel/drivers/usb/usbcore.o entry
Warning (compare_maps): mismatch on symbol icmpv6_socket  , ipv6 says f921ac80, /lib/modules/2.4.19-2.burpr.test/kernel/net/ipv6/ipv6.o says f9218960.  Ignoring /lib/modules/2.4.19-2.burpr.test/kernel/net/ipv6/ipv6.o entry
Warning (compare_maps): mismatch on symbol icmpv6_statistics  , ipv6 says f921ab80, /lib/modules/2.4.19-2.burpr.test/kernel/net/ipv6/ipv6.o says f9218860.  Ignoring /lib/modules/2.4.19-2.burpr.test/kernel/net/ipv6/ipv6.o entry
Warning (compare_maps): mismatch on symbol inet6_dev_count  , ipv6 says f921a7a0, /lib/modules/2.4.19-2.burpr.test/kernel/net/ipv6/ipv6.o says f9218480.  Ignoring /lib/modules/2.4.19-2.burpr.test/kernel/net/ipv6/ipv6.o entry
Warning (compare_maps): mismatch on symbol inet6_ifa_count  , ipv6 says f921a7a4, /lib/modules/2.4.19-2.burpr.test/kernel/net/ipv6/ipv6.o says f9218484.  Ignoring /lib/modules/2.4.19-2.burpr.test/kernel/net/ipv6/ipv6.o entry
Warning (compare_maps): mismatch on symbol inet6_protos  , ipv6 says f921ab00, /lib/modules/2.4.19-2.burpr.test/kernel/net/ipv6/ipv6.o says f92187e0.  Ignoring /lib/modules/2.4.19-2.burpr.test/kernel/net/ipv6/ipv6.o entry
Warning (compare_maps): mismatch on symbol inetsw6  , ipv6 says f921a740, /lib/modules/2.4.19-2.burpr.test/kernel/net/ipv6/ipv6.o says f9218420.  Ignoring /lib/modules/2.4.19-2.burpr.test/kernel/net/ipv6/ipv6.o entry
Warning (compare_maps): mismatch on symbol ip6_ra_chain  , ipv6 says f921aa00, /lib/modules/2.4.19-2.burpr.test/kernel/net/ipv6/ipv6.o says f92186e0.  Ignoring /lib/modules/2.4.19-2.burpr.test/kernel/net/ipv6/ipv6.o entry
Warning (compare_maps): mismatch on symbol ipv6_statistics  , ipv6 says f921a940, /lib/modules/2.4.19-2.burpr.test/kernel/net/ipv6/ipv6.o says f9218620.  Ignoring /lib/modules/2.4.19-2.burpr.test/kernel/net/ipv6/ipv6.o entry
Warning (compare_maps): mismatch on symbol raw_v6_htable  , ipv6 says f921aa80, /lib/modules/2.4.19-2.burpr.test/kernel/net/ipv6/ipv6.o says f9218760.  Ignoring /lib/modules/2.4.19-2.burpr.test/kernel/net/ipv6/ipv6.o entry
Warning (compare_maps): mismatch on symbol rt6_stats  , ipv6 says f921a908, /lib/modules/2.4.19-2.burpr.test/kernel/net/ipv6/ipv6.o says f92185e8.  Ignoring /lib/modules/2.4.19-2.burpr.test/kernel/net/ipv6/ipv6.o entry
Warning (compare_maps): mismatch on symbol udp_stats_in6  , ipv6 says f921aa40, /lib/modules/2.4.19-2.burpr.test/kernel/net/ipv6/ipv6.o says f9218720.  Ignoring /lib/modules/2.4.19-2.burpr.test/kernel/net/ipv6/ipv6.o entry
LAPIC_NMI (acpi_id[0x0007] polarity[0x1] trigger[0x1] lint[0x1])
LAPIC_NMI (acpi_id[0x0008] polarity[0x1] trigger[0x1] lint[0x1])
cpu: 0, clocks: 996964, slice: 498482
kernel BUG at vmalloc.c:236!
invalid operand: 0000
CPU:    0
EIP:    0010:[<c012caa6>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: ffffffff   ebx: 00000000   ecx: 51eb851f   edx: 00000000
esi: 00000000   edi: f4f51a00   ebp: fffffff4   esp: f3ce9d20
ds: 0018   es: 0018   ss: 0018
Process lvcreate (pid: 740, stackpage=f3ce9000)
Stack: 00000000 00000000 f4f51a00 fffffff4 000001f0 f930f000 00000001 fffffff4 
       c02eab14 c02eac7c 000001f0 00000001 c023ad1b 00000000 000001f2 00000163 
       f4f51b6c 00000000 f4f51a00 f3ce9df8 c023adc8 f4f51a00 f4f51a00 000bd000 
Call Trace:    [<c023ad1b>] [<c023adc8>] [<c0238870>] [<c023614c>] [<c01dad7f>]
  [<c01419f7>] [<c010867b>]
Code: 0f 0b ec 00 20 cb 29 c0 31 c0 e9 bf 01 00 00 6a 02 53 e8 9f 

>>EIP; c012caa6 <__vmalloc+26/1fc>   <=====
Trace; c023ad1b <lvm_snapshot_alloc_hash_table+3f/80>
Trace; c023adc8 <lvm_snapshot_alloc+6c/e0>
Trace; c0238870 <lvm_do_lv_create+518/868>
Trace; c023614c <lvm_chr_ioctl+710/81c>
Trace; c01dad7f <locate_hd_struct+27/70>
Trace; c01419f7 <sys_ioctl+16b/184>
Trace; c010867b <system_call+33/38>
Code;  c012caa6 <__vmalloc+26/1fc>
00000000 <_EIP>:
Code;  c012caa6 <__vmalloc+26/1fc>   <=====
   0:   0f 0b                     ud2a      <=====
Code;  c012caa8 <__vmalloc+28/1fc>
   2:   ec                        in     (%dx),%al
Code;  c012caa9 <__vmalloc+29/1fc>
   3:   00 20                     add    %ah,(%eax)
Code;  c012caab <__vmalloc+2b/1fc>
   5:   cb                        lret   
Code;  c012caac <__vmalloc+2c/1fc>
   6:   29 c0                     sub    %eax,%eax
Code;  c012caae <__vmalloc+2e/1fc>
   8:   31 c0                     xor    %eax,%eax
Code;  c012cab0 <__vmalloc+30/1fc>
   a:   e9 bf 01 00 00            jmp    1ce <_EIP+0x1ce> c012cc74 <__vmalloc+1f4/1fc>
Code;  c012cab5 <__vmalloc+35/1fc>
   f:   6a 02                     push   $0x2
Code;  c012cab7 <__vmalloc+37/1fc>
  11:   53                        push   %ebx
Code;  c012cab8 <__vmalloc+38/1fc>
  12:   e8 9f 00 00 00            call   b6 <_EIP+0xb6> c012cb5c <__vmalloc+dc/1fc>


13 warnings issued.  Results may not be reliable.

--->8--[ Oops output from ksymoops ]-->8---


-- 
Gregory K. Ade <gkade@bigbrother.net>
http://bigbrother.net/~gkade
OpenPGP Key ID: EAF4844B  keyserver: pgpkeys.mit.edu

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]

  parent reply	other threads:[~2002-12-05 21:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-02 12:23 [linux-lvm] strange behavior with 1.0.5 on Linux 2.4.19? Gregory K. Ade
2002-10-04  3:54 ` Heinz J . Mauelshagen
2002-10-08 15:07   ` Gregory Ade
2002-10-09  6:38     ` Heinz J . Mauelshagen
2002-10-27 22:30       ` Gregory K. Ade
2002-10-28  3:21         ` Heinz J . Mauelshagen
2002-10-28 22:38           ` Gregory K. Ade
2002-10-29  3:15             ` Heinz J . Mauelshagen
2002-10-29 13:54               ` Gregory K. Ade
2002-10-31  6:52                 ` Heinz J . Mauelshagen
2002-10-31 16:55                   ` Gregory Ade
2002-11-01  9:07                     ` Wolfgang Weisselberg
2002-11-05  8:33                     ` Heinz J . Mauelshagen
2002-11-07 21:45                       ` Gregory Ade
2002-11-09  6:12                         ` Heinz J . Mauelshagen
2002-11-11  5:56                           ` Jon Bendtsen
2002-11-22 15:51                           ` Gregory Ade
2002-12-05 21:35                           ` Gregory Ade [this message]
2002-10-28 14:36         ` jon+lvm
2002-10-28 16:40           ` Gregory K. Ade
2002-10-29 15:21             ` Luca Berra

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=1039145680.1069.79.camel@pslgregory \
    --to=gkade@bigbrother.net \
    --cc=linux-lvm@sistina.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 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.