Package: linux-image-2.6.18-6-xen-686
Version: 2.6.18.dfsg.1-18etch5
Severity: important


Hi,

the maschine runs on a CentOS box. I've got four other instances running on that box and none of them had that problems. It should run the backuppc stuff but crashes while backuping. Here is a dump i took when the error occured to myself while I chanced the mods of a file.

I have to say that this is the only instance with an extra virtual drive.
On that drive lie the files on which the error happens.

backup:/var/lib/backuppc/pc/localhost# chmod backuppc.backuppc config.pl

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: Oops: 0000 [#1]

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: SMP

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: CPU: 0

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: EIP is at __handle_mm_fault+0x292/0xfa3

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: eax: 26d57a20 ebx: 00000000 ecx: 66d57000 edx: 00000a20

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: esi: 00066d57 edi: 00000000 ebp: c1000000 esp: cb6f7d08

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: ds: 007b es: 007b ss: 0069

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: Process chmod (pid: 1690, ti=cb6f6000 task=dfaf9aa0 task.ti=cb6f6000)

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: Stack: c03a1400 c0d17ca4 b7f44458 d3e9d544 d84d2040 00000000 00000000 00000000

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: 00000000 00000000 00000000 cb7b6df8 26d57a20 c0d17d50 c0d17ca4 00000015

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: 000000f4 00000001 00000001 00000a20 00015864 00000000 00000000 00000fcc

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: Call Trace:

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: Code: 89 f0 c1 e0 05 8d 44 05 00 e8 a6 d5 ff ff 8b 54 24 08 c1 ea 09 81 e2 f8 0f 00 00 01 d0 89 54 24 4c 89 44 24 30 0f 84 b7 0c 00 00 <8b> 08 8b 68 04 f6 c1 81 89 8c 24 e0 00 00 00 0f 85 9a 0b 00 00

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: EIP: [<c0147f38>] __handle_mm_fault+0x292/0xfa3 SS:ESP 0069:cb6f7d08

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: kernel BUG at arch/i386/mm/pgtable-xen.c:572!

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: invalid opcode: 0000 [#2]

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: SMP

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: CPU: 0

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: EIP is at pgd_walk+0x250/0x2ec

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: eax: ffffffea ebx: 26d57000 ecx: 00021063 edx: 80000000

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: esi: 00000000 edi: ffffffff ebp: 80000000 esp: cb6f7b58

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: ds: 007b es: 007b ss: 0069

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: Process chmod (pid: 1690, ti=cb6f6000 task=dfaf9aa0 task.ti=cb6f6000)

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: Stack: d84d2040 cbbb3000 0b7b6000 cbbb3010 00000002 000001bf 00101347 00000063

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: 80000000 ac857001 00000000 00177660 cbbb3000 d84d2040 dfaf9aa0 c010fee5

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: d84d2040 00007ff0 c010ff0f cb6f7bb0 c011007d d84d2040 00000005 000c5bbf

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: Call Trace:

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: Code: 0c e0 31 c0 c1 ed 14 0b 4c 24 1c 89 d0 09 c5 21 f1 89 fe 21 f5 31 f6 c1 e3 0c 89 ea 81 eb 00 00 00 40 e8 7b 16 ff ff 85 c0 74 08 <0f> 0b 3c 02 38 e4 29 c0 ff 44 24 14 81 7c 24 14 00 02 00 00 0f

Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
backup kernel: EIP: [<c010fb49>] pgd_walk+0x250/0x2ec SS:ESP 0069:cb6f7b58


-- 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.18-6-xen-686
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)

Versions of packages linux-image-2.6.18-6-xen-686 depends on:
ii initramfs-tools 0.85h tools for generating an initramfs
ii linux-modules-2.6. 2.6.18.dfsg.1-18etch5 Linux 2.6.18 modules on i686

Versions of packages linux-image-2.6.18-6-xen-686 recommends:
ii libc6-xen 2.3.6.ds1-13etch5 GNU C Library: Shared libraries [X

-- no debconf information



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Hi Axel,

Axel Rüweler wrote:

> Package: linux-image-2.6.18-6-xen-686
> Version: 2.6.18.dfsg.1-18etch5
[...]
> the maschine runs on a CentOS box. I've got four other instances
> running on that box and none of them had that problems. It should
> run the backuppc stuff but crashes while backuping. Here is a dump i
> took when the error occured to myself while I chanced the mods of a
> file.
>
> I have to say that this is the only instance with an extra virtual drive.
> On that drive lie the files on which the error happens.
>
> backup:/var/lib/backuppc/pc/localhost# chmod backuppc.backuppc config.pl
>
> Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
> backup kernel: Oops: 0000 [#1]
[...]
> Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
> backup kernel: EIP is at __handle_mm_fault+0x292/0xfa3
>
> Message from syslogd@backup at Fri May 30 14:00:53 2008 ...
> backup kernel: eax: 26d57a20 ebx: 00000000 ecx: 66d57000 edx: 00000a20
[...]

Sorry we missed this years ago. What filesystem were you using? Was
this reproducible? Do you still have access to this setup? Did the
problem ever go away? If this kept on happening, do you have full
logs (including backtrace) from when this happened with a more recent
kernel?

Curious,
Jonathan



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120417053919.GA18732@burratino">http://lists.debian.org/20120417053919.GA18732@burratino