On 10/09/11 20:36, Mark Panen wrote:
Hi,
I am getting these kernel error messages in my terminal as well as the
pop up window using Squeeze with KDE.
Message from syslogd@mark3 at Sep 9 18:58:46 ...
kernel:[68340.726914] Oops: [#1] SMP
Message from syslogd@mark3 at Sep 9 18:58:46
On Sat, 10 Sep 2011 12:36:56 +0200, Mark Panen wrote:
> I am getting these kernel error messages in my terminal as well as the
> pop up window using Squeeze with KDE.
(...)
> Message from syslogd@mark3 at Sep 9 18:58:46 ...
> kernel:[68340.727092] CR2: fff3
Hum... a
Hi,
I am getting these kernel error messages in my terminal as well as the
pop up window using Squeeze with KDE.
Message from syslogd@mark3 at Sep 9 18:58:46 ...
kernel:[68340.726914] Oops: [#1] SMP
Message from syslogd@mark3 at Sep 9 18:58:46 ...
kernel:[68340.726917] last sysfs file
[EMAIL PROTECTED]:
>
> After futzing around with my kernel config, I've managed to get
> iptables working. The problem is I get a lot of "Inbound IN=ppp0
> OUT= MAC= [etc]" messages on all tty's. I know how to
> eliminate the messages themselves.
That's good, I already forgot that! ;-)
> But, sin
After futzing around with my kernel config, I've managed to get
iptables working. The problem is I get a lot of "Inbound IN=ppp0
OUT= MAC= [etc]" messages on all tty's. I know how to
eliminate the messages themselves. But, since I find them
sometimes useful, I just want to restrict the messages to
On Thu, Sep 16, 2004 at 10:58:02AM -0700, Ross Boylan wrote:
> My logs show stuff like this:
> Sep 16 07:51:30 wheat kernel: Directory sread (sector 0x19) failed
> Sep 16 07:51:30 wheat kernel: Directory sread (sector 0x19) failed
> ...
> Sep 16 07:51:30 wheat kernel: Directory sread (sector 0x20)
My logs show stuff like this:
Sep 16 07:51:30 wheat kernel: Directory sread (sector 0x19) failed
Sep 16 07:51:30 wheat kernel: Directory sread (sector 0x19) failed
...
Sep 16 07:51:30 wheat kernel: Directory sread (sector 0x20) failed
Sep 16 07:51:30 wheat kernel: t=12, limit=4
Sep 16 07:51:30 wh
sorry, that would be /etc/modules
g.
On Wed, Dec 24, 2003 at 06:37:51PM +0100, Grzesiek Sedek wrote:
> hi
> You could check if you have any modules in /etc/modules.conf from last
> instalation
> g.
> On Wed, Dec 24, 2003 at 10:16:49AM -0500, Johann Koenig wrote:
> > I built a new 2.4.23 kernel usi
hi
You could check if you have any modules in /etc/modules.conf from last
instalation
g.
On Wed, Dec 24, 2003 at 10:16:49AM -0500, Johann Koenig wrote:
> I built a new 2.4.23 kernel using kpkg, and not only compiled everything
> in, but went so far as to disable module loading. Therefore, I have no
I built a new 2.4.23 kernel using kpkg, and not only compiled everything
in, but went so far as to disable module loading. Therefore, I have no
/lib/modules/2.4.23 directory. However, I get a bunch of:
modprobe: Can't open dependencies file /lib/modules/2.4.23/modules.dep
(No such file or directory
On Thu, May 02, 2002 at 06:06:41AM -0400, Rick Pasotto wrote:
> I've been getting some errors from the kernel. Should I send them to
> someone and if so, who?
>
> Here is an example:
>
> May 2 06:02:03 tc kernel: Unable to handle kernel NULL pointer dereference
> at virtual address 0008
> M
I've been getting some errors from the kernel. Should I send them to
someone and if so, who?
Here is an example:
May 2 06:02:03 tc kernel: Unable to handle kernel NULL pointer dereference at
virtual address 0008
May 2 06:02:03 tc kernel: printing eip:
May 2 06:02:03 tc kernel: c012aec4
M
Alain Nissen writes:
[snip]
> I suspect an hardware problem, because all is working as expected if the
> system remains several hours power-off; but after 15-30 minutes, the
> program are crashing again.
>
> My configuration is a Pentium 200, running Debian/Linux 2.0.32 with
> latest "hamm" packag
> Hello,
>
> I suspect an hardware problem, because all is working as expected if the
> system remains several hours power-off; but after 15-30 minutes, the
> program are crashing again.
>
> My configuration is a Pentium 200, running Debian/Linux 2.0.32 with
> latest "hamm" packages; I have anoth
Hello,
I just noticed that my Debian Linux 2.0.32 box has some 'unreliable'
behaviour, some programs are crashing more and more often with the
well-known 'segmentation fault' message.
The messages in /var/log/kern.log are actually harmful, I think (I
stripped the time in the following log):
kern
G'day --
I am not sure if my last message has made it to the list (I've gotten
an error message from smtp at aol(?) that debian-user doesn't accept
the mail w. attachments...So, please forgive me if I'm repeating
myself. Now; to the problem at hand:
while browsing the Net, at the one of the GnuPlo
16 matches
Mail list logo
