From: Rob See <rob@rsee.net>
To: xen-devel@lists.xensource.com
Subject: [Fwd: Poweredge 2600] and Timer ISR/0: Time went backwards errors with FC4/xen-unstable
Date: Mon, 08 Aug 2005 11:34:37 -0400 [thread overview]
Message-ID: <42F77B8D.1030009@rsee.net> (raw)
I don't mean to be pushy, but does anyone have any suggestions/comments
on this one. I'm using the same version of the kernel on a Poweredge
1850 without the same timer errors or oopses.
Thanks,
-Rob
-------- Original Message --------
Subject: Poweredge 2600
Date: Thu, 04 Aug 2005 13:49:45 -0400
From: Rob See <rob@rsee.net>
To: xen-users@lists.xensource.com, Xen-devel@lists.xensource.com
All,
I'm running into the following oops with a Poweredge 2600 (also an
E7500 based machine) Does anyone have any suggestions ? The machine
seems to work OK with a standard i386 kernel, and has had a problem
similar to this with Xen 2.0.5-2.0.6 and build 1370 of the FC4 kernel
which I believe is based on xen-unstable from early May. Is this a
problem that the noirqbalance might fix ? Its got 1gig of RAM which I
have swapped out. I also recently added an additional 1gig and I'm still
seeing these problems. The uptime was around 5 days. I believe that my
Amanda nightly tape backup was running at this time (dumps to a LTO tape
drive plugged into an Adaptec AHA-3960D / AIC-7899A U160/m (rev 01)).
Also on a side note I'm seeing the following messages on the same machine:
Timer ISR/0: Time went backwards: delta=-29990000 cpu_delta=20010000
shadow=152010000000 off=11000 processed=152040000000
cpu_processed=151990000000
0: 151990000000
1: 151990000000
2: 152040000000
3: 151990000000
Thanks for any help.
-Rob
Aug 4 04:02:02 hamilton kernel: Modules linked in: nfs lockd bridge md5
ipv6 parport_pc lp parport autofs4 i2c_dev i2c_core sunrpc uhci_hcd
e1000 sg st dm_snapshot dm_zero dm_mirror ext3 jbd dm_mod megaraid_mbox
megaraid_mm aic7xxx scsi_transport_spi sd_mod scsi_mod
Aug 4 04:02:02 hamilton kernel: CPU: 1
Aug 4 04:02:02 hamilton kernel: EIP: 0061:[<c017e384>] Not
tainted VLI
Aug 4 04:02:02 hamilton kernel: EFLAGS: 00010283
(2.6.11-1.1370_FC4.rootxen0)
Aug 4 04:02:02 hamilton kernel: EIP is at iput+0x14/0x70
Aug 4 04:02:02 hamilton kernel: eax: 00000000 ebx: cd3341cc ecx:
cd334100 edx: c03b6f00
Aug 4 04:02:02 hamilton kernel: esi: c4d9cad8 edi: c4d9cae0 ebp:
00000080 esp: c8ad1d7c
Aug 4 04:02:02 hamilton kernel: ds: 0069 es: 0069 ss: 0069
Aug 4 04:02:02 hamilton kernel: Process find (pid: 5685,
threadinfo=c8ad0000 task=cf0f3020)
Aug 4 04:02:02 hamilton kernel: Stack: cd3341cc c017b55f 00000000
0000008a 00000000 c07d5a00 c017b9c4 c014f0ec
Aug 4 04:02:02 hamilton kernel: 0012d900 00000000 0000c7fb
00000018 00000000 000080d2 00000020 0000000a
Aug 4 04:02:02 hamilton kernel: c8ad1de0 c8ad1e48 c0354c20
c01501a7 0000c7fa 00000000 00000000 00000000
Aug 4 04:02:02 hamilton kernel: Call Trace:
Aug 4 04:02:02 hamilton kernel: [<c017b55f>] prune_dcache+0x10f/0x1a0
Aug 4 04:02:02 hamilton kernel: [<c017b9c4>]
shrink_dcache_memory+0x14/0x40
Aug 4 04:02:02 hamilton kernel: [<c014f0ec>] shrink_slab+0xfc/0x160
Aug 4 04:02:02 hamilton kernel: [<c01501a7>] try_to_free_pages+0xe7/0x1d0
Aug 4 04:02:02 hamilton kernel: [<c01507ac>] wakeup_kswapd+0x6c/0xa7
Aug 4 04:02:02 hamilton kernel: [<c0148e4d>] __alloc_pages+0xdd/0x430
Aug 4 04:02:02 hamilton kernel: [<c0153f0a>] do_anonymous_page+0xca/0x200
Aug 4 04:02:02 hamilton kernel: [<c01e2248>] copy_to_user+0x58/0x80
Aug 4 04:02:02 hamilton kernel: [<c01540a8>] do_no_page+0x68/0x340
Aug 4 04:02:02 hamilton kernel: [<c015460c>] handle_mm_fault+0x18c/0x1f0
Aug 4 04:02:02 hamilton kernel: [<c0115417>] do_page_fault+0x1d7/0x65d
Aug 4 04:02:02 hamilton kernel: [<c015659f>] do_mmap_pgoff+0x55f/0x7d0
Aug 4 04:02:02 hamilton kernel: [<c0112dc4>] sys_mmap2+0x94/0xd0
Aug 4 04:02:02 hamilton kernel: [<c010978a>] page_fault+0x4e/0x54
Aug 4 04:02:02 hamilton kernel: Code: fd ff ff 8d 74 26 00 e9 cb fe ff
ff 8d 74 26 00 8d bc 27 00 00 00 00 53 85 c0 89 c3 74 4c 83 bb 44 01 00
00 20 8b 80 ac 00 00 00 <8b> 40 24 74 49 85 c0 74 07 8b 50 14 85 d2 75
31 8d 43 24 ba 74
reply other threads:[~2005-08-08 15:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=42F77B8D.1030009@rsee.net \
--to=rob@rsee.net \
--cc=xen-devel@lists.xensource.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.