[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#495793: marked as done (linux-image-2.6.26-1-openvz-686: kernel panic when running netstat)



Your message dated Tue, 2 Sep 2008 12:17:21 +0200
with message-id <20080902101721.GC2509@baikonur.stro.at>
and subject line Re: Bug#495793: linux-image-2.6.26-1-openvz-686: kernel panic when running netstat
has caused the Debian Bug report #495793,
regarding linux-image-2.6.26-1-openvz-686: kernel panic when running netstat
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
495793: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495793
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.26-1-openvz-686
Version: 2.6.26-2~stable0
Severity: important

Hi!

I backported the linux-image-2.6.26-1-openvz-686 package using pbuilder to try openvz on my etch server. It runs ok until I run netstat like this:

alex@atlantis:~$ netstat -ltn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 0.0.0.0:3493            0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.1:6022          0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:3142            0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:139             0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN

It produces several lines and then the machine hangs.
I was able to write down only these lines:

[  870.717682] Stack: f4e29ac0 c04371a0 f7ccdc40 f7430ac0 f4debf40 0000012c c0293cb8 c0372198
[  870.717682]        f7ccdc40 f4d88a40 c019bac7 000003e6 b7fe001a f77098c0 f7ccdc60 0000001a
[  870.717682]        00000008 00000000 00000008 00000000 f7535840 c019b93d fffffffb f77098c0
[  870.717682]  Call Trace:
[  870.717682]  [<c0293cb8>] tcp_seq_next+0x30/0x7b
[  870.717682]  [<c019bac7>] seq_read+0x18a/0x27a
[  870.717682]  [<c019b93d>] seq_read+0x0/0x27a
[  870.717682]  [<c01b2f89>] proc_reg_read+0x58/0x6b
[  870.717682]  [<c01b2f31>] proc_reg_read+0x0/0x6b
[  870.717682]  [<c0184b4d>] vfs_read+0x81/0x11e
[  870.717682]  [<c0184fe1>] sys_read+0x3c/0xa2
[  870.717682]  [<c0108982>] syscall_call+0x7/0xb
[  870.717682]  [<c02c0000>] init_cyrix+0x304/0x4c2
[  870.717682]  =======================
[  870.717682] Code: c0 e9 ac 00 00 00 ff 46 18 83 7e 08 01 75 77 8b 4e 0c 89 0c 24 8b 0a eb 1d 8b 51 18 0f b7 46 04 39 02 75 10 8b 41 1c 8b 54 24 04 <39> 50 24 0f 84 87 00 00 00 8b 09 85 c9 75 df 8b 56 14 42 89 56
[  870.717682] EIP: [<c029241d>] listening_get_next+0x4a/0x185 SS:ESP 0068:f4debf00
[  870.717682] Kernel panic - not syncing: Fatal exception in interrupt

Both linux-image-2.6.18-6-686 and linux-image-2.6.24-etchnhalf.1-686 run ok on the same box.


-- Package-specific info:

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.24-etchnhalf.1-686
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)

Versions of packages linux-image-2.6.26-1-openvz-686 depends on:
ii  debconf [debconf-2.0]        1.5.11etch2 Debian configuration management sy
ii  initramfs-tools [linux-initr 0.85i       tools for generating an initramfs
ii  module-init-tools            3.3-pre4-2  tools for managing Linux kernel mo
ii  vzctl                        3.0.11-14   server virtualization solution - c

Versions of packages linux-image-2.6.26-1-openvz-686 recommends:
ii  libc6-i686             2.3.6.ds1-13etch7 GNU C Library: Shared libraries [i

-- debconf information:
  linux-image-2.6.26-1-openvz-686/preinst/elilo-initrd-2.6.26-1-openvz-686: true
  linux-image-2.6.26-1-openvz-686/postinst/kimage-is-a-directory:
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.26-1-openvz-686/postinst/old-dir-initrd-link-2.6.26-1-openvz-686: true
  linux-image-2.6.26-1-openvz-686/postinst/depmod-error-initrd-2.6.26-1-openvz-686: false
  linux-image-2.6.26-1-openvz-686/prerm/removing-running-kernel-2.6.26-1-openvz-686: true
  linux-image-2.6.26-1-openvz-686/preinst/lilo-initrd-2.6.26-1-openvz-686: true
  linux-image-2.6.26-1-openvz-686/postinst/old-initrd-link-2.6.26-1-openvz-686: true
  linux-image-2.6.26-1-openvz-686/postinst/bootloader-test-error-2.6.26-1-openvz-686:
  linux-image-2.6.26-1-openvz-686/preinst/abort-overwrite-2.6.26-1-openvz-686:
  linux-image-2.6.26-1-openvz-686/postinst/old-system-map-link-2.6.26-1-openvz-686: true
  linux-image-2.6.26-1-openvz-686/postinst/bootloader-error-2.6.26-1-openvz-686:
  linux-image-2.6.26-1-openvz-686/postinst/create-kimage-link-2.6.26-1-openvz-686: true
  linux-image-2.6.26-1-openvz-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.26-1-openvz-686/postinst/depmod-error-2.6.26-1-openvz-686: false
  linux-image-2.6.26-1-openvz-686/preinst/abort-install-2.6.26-1-openvz-686:
  linux-image-2.6.26-1-openvz-686/preinst/initrd-2.6.26-1-openvz-686:
  linux-image-2.6.26-1-openvz-686/preinst/overwriting-modules-2.6.26-1-openvz-686: true
  linux-image-2.6.26-1-openvz-686/prerm/would-invalidate-boot-loader-2.6.26-1-openvz-686: true
  linux-image-2.6.26-1-openvz-686/preinst/failed-to-move-modules-2.6.26-1-openvz-686:
  linux-image-2.6.26-1-openvz-686/preinst/bootloader-initrd-2.6.26-1-openvz-686: true




--- End Message ---
--- Begin Message ---
Version: 2.6.26-4

On Tue, Sep 02, 2008 at 01:52:09PM +0400, Konstantin Khlebnikov wrote:
> already fixed by
> 
> http://git.openvz.org/?p=linux-2.6.26-openvz;a=commit;h=9416cb37ce059d4f4f43c610d70e60d66d609c82

right, thanks, thus already fixed in the unstable linux image,
which will soon migrate to testing. closing

-- 
maks


--- End Message ---

Reply to: