From: "Paolo Ciarrocchi" <ciarrocchi@linuxmail.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [2.5.54 - Oops] CPUFreq [Was: Re: [2.5.54] OOPS: unable to handle kernel paging request]
Date: Mon, 06 Jan 2003 02:00:04 +0800 [thread overview]
Message-ID: <20030105180004.28298.qmail@linuxmail.org> (raw)
I get the same oops+reboot with ifdown lo
I get the same oops+ halt of the machine with
"/usr/sbin/usernetctl lo down
Hope it helps.
Ciao,
Paolo
--
______________________________________________
http://www.linuxmail.org/
Now with POP3/IMAP access for only US$19.95/yr
Powered by Outblaze
next reply other threads:[~2003-01-05 17:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-05 18:00 Paolo Ciarrocchi [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-05 17:43 [2.5.54 - Oops] CPUFreq [Was: Re: [2.5.54] OOPS: unable to handle kernel paging request] Steven Barnhart
2003-01-03 21:05 [2.5.54] OOPS: unable to handle kernel paging request Steven Barnhart
2003-01-05 9:25 ` [2.5.54 - Oops] CPUFreq [Was: Re: [2.5.54] OOPS: unable to handle kernel paging request] Paul Rolland
2003-01-05 10:43 ` Paul Rolland
2003-01-05 16:47 ` Steven Barnhart
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=20030105180004.28298.qmail@linuxmail.org \
--to=ciarrocchi@linuxmail.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