OK, I'll join in...
On Friday, 15 בJanuary 2010 16:27:34 Eli Billauer wrote:
Now I get an oops warning every now and then, but nothing really
happens. And I wonder what is going on? Has the dreaded oops become
something one can live with?
Nothing really changed that much. An Oops is caused
Thanks, Oron.
You didn't just join in, but finally gave the full answer I was looking for.
I tried to get a simple explanation on what these macros actually stand
for, and couldn't find a single place where they were explained as
simply as you put it.
Eli
Oron Peled wrote:
OK, I'll
Kohn Emil Dan wrote:
No, it isn't. Crashing is one of the best of the options in some
situations. Imagine a bug in the filesystem that writes a zero byte at
random places on the filesystem or even funnier, on the neighboring
partitions where you have installed another operating system. (yes
On Fri, Jan 15, 2010 at 10:49:41PM +0200, Orna Agmon Ben-Yehuda wrote:
On Fri, Jan 15, 2010 at 4:27 PM, Eli Billauer e...@billauer.co.il wrote:
Hello,
Maybe this is a boker-tov-eliyahu thing, but still. I've installed
Fedora 12, just to find out that it warns me about kernel oopses. In
Hi,
Just to wrap the story up: I checked the source code. The offending
oops comes from a line 390 in hpet.c, which is the WARN_ON_ONCE call
below:
kernel code
/*
* We need to read back the CMP register to make sure that
* what we wrote hit the chip before we compare it to the
On Sun, Jan 17, 2010 at 12:06:27AM +0200, Eli Billauer wrote:
Hi,
Just to wrap the story up: I checked the source code. The offending
oops comes from a line 390 in hpet.c, which is the WARN_ON_ONCE call
below:
kernel code
/*
* We need to read back the CMP register to make
Hello,
Maybe this is a boker-tov-eliyahu thing, but still. I've installed
Fedora 12, just to find out that it warns me about kernel oopses. In my
remote memories, I recall that a kernel oops usually meant that my
hardware was cooking (in those days when Linux was rock solid and
hardware
Thanks, but it looks like I wasn't clear about it: My issue is not to
solve the specific problem. The question is that if I should bother, or
just wait.
In ancient times, an oops meant I had no choice. The computer was dead.
But judging by how the interface communicates with me (something
Try a quick google search for the warning:
http://www.google.co.il/search?q=+WARNING%3A+at+arch%2Fx86%2Fkernel%2Fhpet.c%3A390ie=utf-8oe=utf-8aq=trls=org.mozilla:en-US:officialclient=firefox-a
It might be problem with hpet and freq-scaling not playing nicely with
each other.
--Shachar
On Fri,
this is oops-dependent - but i tihnk this is generaly a software bug.
some oopses cause the machine to freeze and you need to reboot. some
other times, they just cause a user-space process to terminate - and you
can continue working normally.
in general, i think the old myths are not true
Hi,
IIRC in Linux an OOPS will not necessarily freeze the system (though this
can be configured via some /proc entry or at compilation time). If an OOPS
occurs in the context of a process, that process will be killed with a
SEGFAULT, and the system will attempt to continue to work.
Obviously
Hello Eli,
I would not take it cool.
If I understand correctly, some kernel thread had a real
serious error, accessing bad address for example.
Fortunately this event was caught.
But next time, this bad memory access might be disastrous.
-- yotam
On Fri, 15 Jan 2010 16:27:34 +0200
Eli
Hi,
The /proc entry I was talking about is
/proc/sys/kernel/panic_on_oops
Emil
On Fri, 15 Jan 2010, Kohn Emil Dan wrote:
Hi,
IIRC in Linux an OOPS will not necessarily freeze the system (though this
can be configured via some /proc entry or at
On Fri, Jan 15, 2010 at 4:27 PM, Eli Billauer e...@billauer.co.il wrote:
Hello,
Maybe this is a boker-tov-eliyahu thing, but still. I've installed
Fedora 12, just to find out that it warns me about kernel oopses. In my
remote memories, I recall that a kernel oops usually meant that my
Thanks for your answers (on this one and on my other issues).
I realize that the oops is still an oops, only nowadays nobody want to
stop the whole show, just because some kernel code misbehaved. If the
general idea is that the worst thing a kernel can do is to crash, why
crash now? Kill the
On Fri, 15 Jan 2010, Eli Billauer wrote:
Thanks for your answers (on this one and on my other issues).
I realize that the oops is still an oops, only nowadays nobody want to
stop the whole show, just because some kernel code misbehaved. If the
general idea is that the worst thing a kernel
On Fri, Jan 15, 2010 at 04:27:34PM +0200, Eli Billauer wrote:
So, should I just take it cool and wait for a new kernel with this
fixed, ignoring these messages?
Just for the heck of it, the relevant part from /var/log/messages
follows. I am running on a new Gigabyte motherboard. I don't
17 matches
Mail list logo
