From: "Michael" <michael.sallaway@gmail.com>
To: <sergio@sergiomb.no-ip.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: PROBLEM: Oops when doing disk heavy disk I/O
Date: Wed, 25 Oct 2006 11:25:07 +1000 [thread overview]
Message-ID: <453ebcfd.615c691e.52ef.2927@mx.google.com> (raw)
In-Reply-To: <1161736906.2922.14.camel@localhost.portugal>
> -----Original Message-----
> From: Sergio Monteiro Basto [mailto:sergio@sergiomb.no-ip.org]
> Sent: Wednesday, 25 October 2006 10:42 AM
>
> well I don't know for sure , but after this initials Lost Timer tick ,
> it appears more after a few time of uptime ?
>
Well, when the machine was just sitting there, I don't get any lost timer
ticks -- it's perfectly happy. However, I started to `dd if=/dev/zero
of=/dev/hda6` again, and after a few minutes, it oops'ed again (below),
losing 2 timer ticks: <4>time.c: Lost 2 timer tick(s)! rip
__do_softirq+0x4a/0xc4)
Also, I rebooted and did the same command, but with bs=512K. It Oops'ed
again (after about 30 seconds?), but this time, with:
<4>time.c: Lost 1 timer tick(s)! rip _spin_unlock_irqrestore+0x8/0x9)
Kernel panic - not syncing: Aiee, killing interrupt handler!
It seems to be related to interrupts, somehow... since I'm not too familiar
with what's happening, would anyone have any suggestions about what I could
do next to troubleshoot?
Thanks!
Michael
Full Oops:
Unable to handle kernel NULL pointer dereference at 000000000000002b RIP:
[<ffffffff8021a6c5>] __block_write_full_page+0xa4/0x2df
PGD 7a312067 PUD 7a374067 PMD 0
Oops: 0000 [1] SMP
CPU 0
Modules linked in:
Pid: 263, comm: pdflush Not tainted 2.6.19-rc3 #1
RIP: 0010:[<ffffffff8021a6c5>] [<ffffffff8021a6c5>]
__block_write_full_page+0xa4/0x2df
RSP: 0018:ffff810037ebbc30 EFLAGS: 00010287
RAX: 0000000000000000 RBX: 000000000000002b RCX: 0000000000000002
RDX: 000000000000000a RSI: 00000000000554a9 RDI: ffff810037cc8440
RBP: ffff8100015f1c30 R08: ffff810037cc8440 R09: ffff810037ebbe70
R10: ffffffff802bee4c R11: ffffffff80440b8b R12: ffff81001b2c9dc8
R13: 00000000001552a7 R14: ffff810037cc8440 R15: 0000000001c42574
FS: 00002b1c6f9536d0(0000) GS:ffffffff807d6000(0000) knlGS:0000000000000000
CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 000000000000002b CR3: 000000007a315000 CR4: 00000000000006e0
Process pdflush (pid: 263, threadinfo ffff810037eba000, task
ffff810037f250e0)
Stack: ffff810037ebbe70 ffffffff802bee4c 00000400015f1c30 ffff8100015f1c30
ffff810037ebbe70 ffff810037cc8550 000000000000000b ffff81007efe9b08
0000000000000000 ffffffff8029db1e 000000000000000e ffffffff802bdff3
Call Trace:
[<ffffffff802bee4c>] blkdev_get_block+0x0/0x46
[<ffffffff8029db1e>] generic_writepages+0x18e/0x2d8
[<ffffffff802bdff3>] blkdev_writepage+0x0/0xf
[<ffffffff8025591f>] do_writepages+0x20/0x2d
[<ffffffff8022cf8c>] __writeback_single_inode+0x1b4/0x38b
[<ffffffff8021f44f>] sync_sb_inodes+0x1d1/0x2b5
[<ffffffff802897e0>] keventd_create_kthread+0x0/0x61
[<ffffffff8024b3b7>] writeback_inodes+0x82/0xd8
[<ffffffff8029dfb4>] background_writeout+0x82/0xb5
[<ffffffff8025108f>] pdflush+0x0/0x1e3
[<ffffffff802511c8>] pdflush+0x139/0x1e3
[<ffffffff8029df32>] background_writeout+0x0/0xb5
[<ffffffff8022f78a>] kthread+0xd1/0x101
[<ffffffff80258ed8>] child_rip+0xa/0x12
[<ffffffff802897e0>] keventd_create_kthread+0x0/0x61
[<ffffffff8022f6b9>] kthread+0x0/0x101
[<ffffffff80258ece>] child_rip+0x0/0x12
Code: 8b 03 a8 20 75 6c 8b 03 a8 02 74 66 8b 44 24 14 48 39 43 20
RIP [<ffffffff8021a6c5>] __block_write_full_page+0xa4/0x2df
RSP <ffff810037ebbc30>
CR2: 000000000000002b
<4>time.c: Lost 2 timer tick(s)! rip __do_softirq+0x4a/0xc4)
next prev parent reply other threads:[~2006-10-25 1:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 15:56 PROBLEM: Oops when doing disk heavy disk I/O Michael Sallaway
2006-10-24 17:26 ` Sergio Monteiro Basto
2006-10-25 0:21 ` Michael
2006-10-25 0:41 ` Sergio Monteiro Basto
2006-10-25 1:25 ` Michael [this message]
2006-10-25 4:12 ` Ray Lee
2006-10-25 12:28 ` Michael
2006-10-25 15:08 ` Ray Lee
2006-10-25 15:24 ` Paulo Marques
2006-10-24 17:43 ` Badari Pulavarty
2006-10-25 0:09 ` Michael
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=453ebcfd.615c691e.52ef.2927@mx.google.com \
--to=michael.sallaway@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sergio@sergiomb.no-ip.org \
/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.