From: Tarkan Erimer <tarkane@gmail.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG]: Software compiling occasionlly hangs under 2.6.15-rc1/rc2 and 2.6.15-rc1-mm2
Date: Sun, 27 Nov 2005 19:08:23 +0000 [thread overview]
Message-ID: <9611fa230511271108m46389ee6w7ec6b5b40b1e23dd@mail.gmail.com> (raw)
In-Reply-To: <1133092701.2853.0.camel@laptopd505.fenrus.org>
[-- Attachment #1: Type: text/plain, Size: 653 bytes --]
Hi again,
On 11/27/05, Arjan van de Ven <arjan@infradead.org> wrote:
> which process again was hanging?
>
> (and maybe also post an lsmod output just to get an idea of which
> modules/drivers are in play)
I investigated the issue a bit more. When the system under heavy load
(%100 cpu usage), hard lock up/complete freeze occures a few minutes later.
For example, compiling a software or issuing "updatedb" causes this.
At this point, system responds anything. I just hardly caught this
event while freezing:
~#>echo "t" > /proc/sysrq-trigger
[ 849.651134 ] SysRq : Show State
My syslog and lsmod output attached
Regards
[-- Attachment #2: lsmod.out --]
[-- Type: application/octet-stream, Size: 2008 bytes --]
Module Size Used by
pcmcia 40736 2
yenta_socket 29324 2
rsrc_nonstatic 13440 1 yenta_socket
pcmcia_core 44320 3 pcmcia,yenta_socket,rsrc_nonstatic
rfcomm 41236 0
l2cap 27520 5 rfcomm
snd_pcm_oss 55968 0
snd_mixer_oss 20224 1 snd_pcm_oss
snd_seq_dummy 4100 0
snd_seq_oss 36096 0
snd_seq_midi_event 7808 1 snd_seq_oss
snd_seq 56464 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 9740 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_intel8x0m 18700 0
snd_intel8x0 35100 0
snd_ac97_codec 97952 2 snd_intel8x0m,snd_intel8x0
snd_ac97_bus 2688 1 snd_ac97_codec
snd_pcm 95876 4 snd_pcm_oss,snd_intel8x0m,snd_intel8x0,snd_ac97_codec
snd_timer 27396 2 snd_seq,snd_pcm
snd 59748 10 snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq,snd_seq_device,snd_intel8x0m,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
soundcore 10464 1 snd
snd_page_alloc 11784 3 snd_intel8x0m,snd_intel8x0,snd_pcm
ntfs 224016 1
ieee80211_crypt_tkip 11392 0
ieee80211_crypt_ccmp 7680 0
ieee80211_crypt_wep 5376 0
usbhid 41504 0
ipw2100 146660 0
ieee80211 46312 1 ipw2100
ieee80211_crypt 6532 4 ieee80211_crypt_tkip,ieee80211_crypt_ccmp,ieee80211_crypt_wep,ieee80211
firmware_class 11392 2 pcmcia,ipw2100
e100 41220 0
mii 6400 1 e100
bluetooth 51556 4 rfcomm,l2cap
uhci_hcd 35344 0
ehci_hcd 37128 0
ohci_hcd 22276 0
usb_storage 78528 0
usbcore 136836 6 usbhid,uhci_hcd,ehci_hcd,ohci_hcd,usb_storage
scsi_mod 103976 1 usb_storage
as_iosched 20740 1
agpgart 36312 0
[-- Attachment #3: syslog.bz2 --]
[-- Type: application/x-bzip2, Size: 25961 bytes --]
next prev parent reply other threads:[~2005-11-27 19:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-25 11:12 Tarkan Erimer
2005-11-25 11:19 ` Arjan van de Ven
2005-11-27 11:17 ` Tarkan Erimer
2005-11-27 11:58 ` Arjan van de Ven
2005-11-27 19:08 ` Tarkan Erimer [this message]
2005-11-27 19:12 ` Arjan van de Ven
2005-11-27 19:18 ` Tarkan Erimer
2005-11-28 0:57 ` Andrew Morton
2005-11-29 21:57 ` Tarkan Erimer
2005-11-29 23:10 ` Andrew Morton
2005-11-30 13:53 ` Anton Altaparmakov
2005-12-01 20:47 ` Tarkan Erimer
2005-12-01 20:42 ` Tarkan Erimer
2005-12-02 12:49 ` Tarkan Erimer
2005-12-05 14:30 ` Tarkan Erimer
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=9611fa230511271108m46389ee6w7ec6b5b40b1e23dd@mail.gmail.com \
--to=tarkane@gmail.com \
--cc=arjan@infradead.org \
--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
all inboxes | Powered by JetHome®