From: Thomas Svedberg <thsv@am.chalmers.se>
To: Fedor Karpelevitch <fedor@karpelevitch.net>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: Hard lock with recent 2.6.0-test kernels
Date: Thu, 11 Sep 2003 18:48:45 +0200 [thread overview]
Message-ID: <1063298924.9623.22.camel@ampc545.am.chalmers.se> (raw)
In-Reply-To: <200309110725.53649.fedor@karpelevitch.net>
tor 2003-09-11 klockan 16.25 skrev Fedor Karpelevitch:
> Thomas Svedberg wrote:
> > I first experienced total lockup with 2.6.0-test4-mm5 and have now
> > tried a few different ones. -test4-mm4 works, test4-bk2 works,
> > test4-mm5 locks, test4-bk3 locks, test5-mm1 locks.
> > Nothing shows in the logs, and the lock occurs while doing random
> > things but only after a few seconds - minutes after i logged in to
> > X. sysrq don't work either.
> > It is an Compaq Evo 1020v and configs etc. can be found at:
> > http://www.am.chalmers.se/~thsv/laptop/
>
> looks to me like my favorite network-related lockup. do you ever get
> it if you disconnect from network?
Just tried with -bk3 and it stayed stable (did make -j on a project of
mine that made load go to 40) until I connected the network cable and
restarted the network, and then it froze like before.
--
/ Thomas
.......................................................................
Thomas Svedberg
Department of Applied Mechanics
Chalmers University of Technology
Address: SE-412 96 Göteborg, SWEDEN
E-mail : thsv@am.chalmers.se, thsv@bigfoot.com
Phone : +46 31 772 1522
Fax : +46 31 772 3827
.......................................................................
next prev parent reply other threads:[~2003-09-11 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 9:35 Hard lock with recent 2.6.0-test kernels Thomas Svedberg
2003-09-11 14:25 ` Fedor Karpelevitch
2003-09-11 16:48 ` Thomas Svedberg [this message]
2003-10-17 9:12 ` Thomas Svedberg
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=1063298924.9623.22.camel@ampc545.am.chalmers.se \
--to=thsv@am.chalmers.se \
--cc=akpm@osdl.org \
--cc=fedor@karpelevitch.net \
--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;
as well as URLs for NNTP newsgroup(s).