On Sat, Mar 13, 2021 at 03:01:45AM -0500, Michael Grant wrote:
> > I'd say it is a Linode problem, unless you run custom kernel modules.
> > It looks like a "memory" corruption to me and since it is virtualized
> > system,
> > you should check if host system is ok.
> > Memory in quotes because thi
> I'd say it is a Linode problem, unless you run custom kernel modules.
> It looks like a "memory" corruption to me and since it is virtualized system,
> you should check if host system is ok.
> Memory in quotes because this issue could be also related to a storage
> sub-system (local or network at
On 13.03.2021 11:31, Michael Grant wrote:
I'm seeing lots of errors like this in my kern.log on 2 of 3 of my
deban Linodes running testing on Linode's provided kerne 5.10.13. Is
this a problem in Debian or is this a Linode issue?
Mar 12 19:32:18 strange kernel: [10849.820363] BUG: Bad page stat
I'm seeing lots of errors like this in my kern.log on 2 of 3 of my
deban Linodes running testing on Linode's provided kerne 5.10.13. Is
this a problem in Debian or is this a Linode issue?
Mar 12 19:32:18 strange kernel: [10849.820363] BUG: Bad page state in process
kworker/0:3 pfn:10902f
Mar 12
Curt writes:
> On 2015-07-08, Rodolfo Medina wrote:
It seems it is `0x6000': with it, the message didn't appear any more.
>>>
>>> What were the consequences of the message appearing (besides the message
>>> appearing)?
>>
>> Actually, none at all. But the start off has sometimes its o
On 2015-07-08, Rodolfo Medina wrote:
>>>
>>> It seems it is `0x6000': with it, the message didn't appear any more.
>>
>> What were the consequences of the message appearing (besides the message
>> appearing)?
>
> Actually, none at all. But the start off has sometimes its own form of
> `aesthetics
Curt writes:
> On 2015-07-07, Rodolfo Medina wrote:
>>>
>>> Thanks, I will. The file should be modesetting.conf. But how do I know
>>> what the appropriate parameter for `0xaddr' will be?
>>>
>>> Rodolfo
>>
>> It seems it is `0x6000': with it, the message didn't appear any more.
>
> What were
On 2015-07-07, Rodolfo Medina wrote:
>>
>> Thanks, I will. The file should be modesetting.conf. But how do I know what
>> the appropriate parameter for `0xaddr' will be?
>>
>> Rodolfo
>
> It seems it is `0x6000': with it, the message didn't appear any more.
What were the consequences of the mes
Rodolfo Medina writes:
> Darac Marjal writes:
>
>> On Tue, Jul 07, 2015 at 01:23:01PM +0100, Rodolfo Medina wrote:
>>> Hi all.
>>>
>>> On my old Pentiium III, at boot the following message appears:
>>>
>>> via686a :00:04.4: base address not set - upgrade BIOS or use
>>> force_addr=0xaddr
>
Darac Marjal writes:
> On Tue, Jul 07, 2015 at 01:23:01PM +0100, Rodolfo Medina wrote:
>> Hi all.
>>
>> On my old Pentiium III, at boot the following message appears:
>>
>> via686a :00:04.4: base address not set - upgrade BIOS or use
>> force_addr=0xaddr
>>
>> How can I eliminate it?
>
> F
On Tue, Jul 07, 2015 at 01:23:01PM +0100, Rodolfo Medina wrote:
> Hi all.
>
> On my old Pentiium III, at boot the following message appears:
>
> via686a :00:04.4: base address not set - upgrade BIOS or use
> force_addr=0xaddr
>
> How can I eliminate it?
From the Kernel Documentation:
https
Hi all.
On my old Pentiium III, at boot the following message appears:
via686a :00:04.4: base address not set - upgrade BIOS or use
force_addr=0xaddr
How can I eliminate it?
Thanks for any help,
Rodolfo
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of
Hi,
just in case anyone comes across this thread: I have filed a bug report
for this issue under #639453.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639453
Dirk
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas.
Hello list,
I am experiencing the following issue with a Debian squeeze based server
and the most recent squeeze-backports kernel:
I realized that some vstfpd daemons randomly drop connections (sending a
FIN right after the initial TCP hand shake was completed). Furthermore,
a "Failed to cre
On Thu, Apr 22, 2010 at 07:24:38PM -0400, Nick Lidakis wrote:
> This popped up in one of my xterms after my Thinkpad came out of hibernation
> today. The machine has beeped a few times as this message was repeated.
> Does not sound good. Call Trace? That's, like, bad? Right?
>
>
> Message from sy
On Thu, 22 Apr 2010 19:24:38 -0400, Nick Lidakis wrote:
> This popped up in one of my xterms after my Thinkpad came out of
> hibernation today. The machine has beeped a few times as this message
> was repeated. Does not sound good. Call Trace? That's, like, bad? Right?
>
>
> Message from sysl...
This popped up in one of my xterms after my Thinkpad came out of hibernation
today. The machine has beeped a few times as this message was repeated.
Does not sound good. Call Trace? That's, like, bad? Right?
Message from sysl...@thinkpad at Apr 22 18:52:20 ...
kernel:[42926.069917] Oops: [#
> Sun, 11 Apr 2010 00:20:54 -0400
>
> Hello,
>
> I was hoping to get some feedback or tips on how to setup a PCI serial card
> (not onboard) for kernel message log capturing. I am using Debian Lenny x64
> with the grub2 bootloader.
>
> This might sound like
Hello,
I was hoping to get some feedback or tips on how to setup a PCI serial card
(not onboard) for kernel message log capturing. I am using Debian Lenny x64
with the grub2 bootloader.
This might sound like an easy question, but does the Linux kernel module have
to be compiled with the
I am using debian testing 2.6.5-1-686-smp kernel. In /var/log/kern.log,
I see the following messages.
May 22 12:03:05 kusumanchi kernel: apm: BIOS version 1.2 Flags 0x03
(Driver version 1.16ac)
May 22 12:03:05 kusumanchi kernel: apm: disabled - APM is not SMP safe.
May 22 12:03:05 kusumanchi ker
Hi,
I got some strange kernel message recently. I did not do anything
to my init besides setting up the xfstt. Below are the strange messages I
am getting:
bmap of 39a,block 83 is 44f4
super 200
bmap 84
result 44f5
bmap of 39a,block 84 is 44f5
super 200
bmap 85
result 44f6
bmap of
I saw a test patch on linux-kernel this morning, for what sounds like
the same problem you're having. I'll take a look and see if I can find
it again.
On Mon, Feb 15, 1999 at 10:15:26PM +0100, Björn Elwhagen wrote:
> Hello!
>
> I'm having some strange problems. I can't eject my CDROM even tho it
Hello!
I'm having some strange problems. I can't eject my CDROM even tho it's
unmounted according to mtab and all other places that i can think of.
The message i get is simply:
1 21:59:52 marwin $ cdctrl eject
cd_doEject[CDROMEJECT]: Device or resource busy
Pressing the eject-button on the CD do
Hello!
The last few days i've been noticing strange messages in the kernel-log
(kern.log). The message goes like this:
Feb 10 06:28:14 arwen kernel: khm
and repeats about 5 times every minute. I haven't got a single clue what
it means and would appreciate an answer. I'm using kernel 2.2.1.
Rega
I received a kernel message this morning that was simply:
Couldn't get a free page.
what does this mean???
Thanks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>From: Dany Dionne <[EMAIL PROTECTED]>
>X-Sender: [EMAIL PROTECTED]
>To: debian-user@lists.debian.org
>Subject: kernel message : Possible flooding ???
>Message-ID: <[EMAIL PROTECTED]>
>MIME-Version: 1.0
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>Resent-Message-
think that the crash was a strike back. So, the kernel message about a
possible flooding could be related to our hacker war?
Dany Dionne
Physics Department
Laval University
Canada
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble?
'Unable to load interpreter.'
anyone ever seen this?
m*
--
"The Shining One"
--
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
mike horansky writes:
> Looking through /var/log/messages, I see
>
> Jan 18 18:23:34 bigbox kernel: ICMP redirect from
> Jan 18 18:23:34 bigbox last message repeated 3 times
>
> every few days.
>
> Is that an indication of Ping Of Death? Some other problem?
ICMP redirects are sent by y
Looking through /var/log/messages, I see
Jan 18 18:23:34 bigbox kernel: ICMP redirect from
Jan 18 18:23:34 bigbox last message repeated 3 times
every few days.
Is that an indication of Ping Of Death? Some other problem?
--
-Mike Horansky, Leland Consultant (http://consult.stanford.edu/)
[EMA
30 matches
Mail list logo