From: Catalin Bucur <cata@geniusnet.ro>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] 2.4.20 htb3 oops
Date: Fri, 24 Jan 2003 14:29:35 +0000 [thread overview]
Message-ID: <marc-lartc-104341866201429@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104341174125310@msgid-missing>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Mihai RUSU wrote:
| After the oops applications that were trying to write to the /var (xfs)
| partition were hanging in D state. We will reformat it and reboot with a
| vanilla 2.4.20 having the same config except the XFS filesystem.
I don't know if it's about xfs. I've had the same oops with kernel
2.4.19 with patch for HTB applied when I was trying to restart HTB for 3
or 4 times a day. I was very happy when 2.4.20 appeared with HTB
included because all there errors was gone. Now I can restart HTB how
many times I want and there are no problems. I am curious too about this
behavior of kernel with HTB enabled.
- --
Catalin Bucur mailto:cata@geniusnet.ro
NOC @ Genius Network SRL - Galati - Romania
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE+MU3PpDe20wwI9oIRApQwAJ9V+IuZYAjfeDtNYp5CNhK20PdTTwCfV/fi
FObrQbZpI6lK/seMfqESJsA=QTuE
-----END PGP SIGNATURE-----
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-01-24 14:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 12:54 [LARTC] 2.4.20 htb3 oops Mihai RUSU
2003-01-24 14:29 ` Catalin Bucur [this message]
2003-01-25 21:51 ` Alexey Sheshka
2003-03-03 13:22 ` Göran Runfeldt
2003-03-03 13:39 ` Abraham van der Merwe
2003-03-03 14:53 ` Göran Runfeldt
2003-03-03 16:29 ` Abraham van der Merwe
2003-05-06 16:10 ` Kabelweb
2003-05-07 18:31 ` Martin Volf
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=marc-lartc-104341866201429@msgid-missing \
--to=cata@geniusnet.ro \
--cc=lartc@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 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.