From: "Markus Hästbacka" <mhastbacka@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: rcu_kthread hang on 3.0.0-rc1-next-20110602
Date: Sat, 4 Jun 2011 00:43:25 +0300 [thread overview]
Message-ID: <85F46CF9-5433-4623-91FC-9CD890082F69@gmail.com> (raw)
Hello!
After updating my debian squeeze box to 3.0.0-rc1-next-20110602 I'm experiencing a weird problem. If I run dmesg the computer hangs for 15 minutes, and I cannot even login at this time, if I leave top (the top window updates very slowly, like every 5 minutes during this period) running I can see that the process rcu_kthread takes 100% CPU, the computer load average is at around 10.
I also sometimes get these disk errors in syslog:
Jun 4 02:01:39 midi3g kernel: ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Jun 4 02:01:39 midi3g kernel: ata1.01: BMDMA stat 0x44
Jun 4 02:01:39 midi3g kernel: ata1.01: failed command: WRITE DMA
Jun 4 02:01:39 midi3g kernel: ata1.01: cmd ca/00:00:1c:7b:c6/00:00:00:00:00/f0 tag 0 dma 131072 out
Jun 4 02:01:39 midi3g kernel: res 51/84:00:fe:7b:c6/00:00:00:00:00/f0 Emask 0x10 (ATA bus error)
Jun 4 02:01:39 midi3g kernel: ata1.01: status: { DRDY ERR }
Jun 4 02:01:39 midi3g kernel: ata1.01: error: { ICRC ABRT }
Jun 4 02:01:39 midi3g kernel: ata1: soft resetting link
Jun 4 02:01:39 midi3g kernel: ata1.01: configured for UDMA/66
Jun 4 02:01:39 midi3g kernel: ata1: EH complete
but for example the last time I got the hang, I didn't get this error, nor any other error for that matter.
The OS is installed on a CF-card. The computer is a eBox computer with VIA Nehemiah CPU, 256MB RAM.
what more information do you need? Or what more can I test?
M
next reply other threads:[~2011-06-03 21:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 21:43 Markus Hästbacka [this message]
2011-06-04 6:17 ` Manuel Lauss
2011-06-04 15:41 ` Markus Hästbacka
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=85F46CF9-5433-4623-91FC-9CD890082F69@gmail.com \
--to=mhastbacka@gmail.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome