This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 129] New: x86_64 - Kernel BUG at "fs/fs-writeback.c":363

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 129] New: x86_64 - Kernel BUG at "fs/fs-writeback.c":363
From: dbarrera@xxxxxxxxxx
Date: Fri, 29 Jul 2005 20:29:19 +0000
Delivery-date: Fri, 29 Jul 2005 20:29:23 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           Summary: x86_64 - Kernel BUG at "fs/fs-writeback.c":363
           Product: Xen
           Version: unstable
          Platform: x86-64
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: dbarrera@xxxxxxxxxx
                CC: hohnbaum@xxxxxxxxxx

FC4 based Dom0, x86_64. Had a DomU up but not running any workloads. File system
is ext3.

I was editing a text file, when i saw a message appear on the console:
kernel: invalid operand: 0000 [1]

dmesg on Dom0 shows this trace:

----------- [cut here ] --------- [please bite here ] ---------
Kernel BUG at "fs/fs-writeback.c":363
invalid operand: 0000 [1]
Modules linked in: video thermal processor fan button battery ac
Pid: 131, comm: pdflush Not tainted 2.6.12-xen0
RIP: e030:[<ffffffff8018b399>] <ffffffff8018b399>{sync_sb_inodes+489}
RSP: e02b:ffff88000f079de8  EFLAGS: 00010202
RAX: 0000000000000001 RBX: ffff88000d2d9800 RCX: ffff88000bbba100
RDX: ffff88000b128000 RSI: ffff880008038c80 RDI: ffff88000b008ed0
RBP: ffff880008038c70 R08: 0000000000000003 R09: 0000000000000040
R10: 0000000000000001 R11: 0000000000000000 R12: ffff88000b008ed0
R13: ffff88000f079e48 R14: ffff88000d2d98e8 R15: 000000010000083c
FS:  00002aaaaaabcf20(0000) GS:ffffffff8053b200(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process pdflush (pid: 131, threadinfo ffff88000f078000, task ffff88000f0262b0)
Stack: 0000000000000032 ffff88000d2d9800 ffff88000d2d9878 ffff88000f079e48
       ffffffff801503a0 ffffffff8013f850 ffff88000f8067d0 ffffffff8018b63f
       00000000000018b8 0000000000000000
Call Trace:<ffffffff801503a0>{pdflush+0}
       <ffffffff801504cf>{pdflush+303} <ffffffff8014f980>{wb_kupdate+0}
       <ffffffff8013fa7d>{kthread+205} <ffffffff8010e59f>{child_rip+8}

Code: 0f 0b b0 63 3e 80 ff ff ff ff 6b 01 48 89 ef e8 b3 71 ff ff
RIP <ffffffff8018b399>{sync_sb_inodes+489} RSP <ffff88000f079de8>

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 129] New: x86_64 - Kernel BUG at "fs/fs-writeback.c":363, dbarrera <=