From: Dinolinux <anton.slack@tele2.no>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [PATCH] arch/i386/kernel/doublefault.c
Date: Sat, 08 Oct 2005 14:09:48 +0000 [thread overview]
Message-ID: <43480D56.408@tele2.no> (raw)
In-Reply-To: <20051003110453.GA10630@rhum.iomeda.fr>
Alexey Dobriyan wrote:
>On Mon, Oct 03, 2005 at 04:54:41PM +0000, slackfan@users.sourceforge.net wrote:
>
>
>>--- linux-2.6.14-rc2.orig/arch/i386/kernel/doublefault.c
>>+++ linux-2.6.14-rc2/arch/i386/kernel/doublefault.c
>>
>>
>
>
>
>>- printk("double fault, gdt at %08lx [%d bytes]\n", gdt, gdt_desc.size);
>>+ printk(KERN_ALERT "double fault, gdt at %08lx [%d bytes]\n", gdt, gdt_desc.size);
>>
>> if (ptr_ok(gdt)) {
>> gdt += GDT_ENTRY_TSS << 3;
>> tss = *(u16 *)(gdt+2);
>> tss += *(u8 *)(gdt+4) << 16;
>> tss += *(u8 *)(gdt+7) << 24;
>>- printk("double fault, tss at %08lx\n", tss);
>>+ printk(KERN_CRIT "double fault, tss at %08lx\n", tss);
>>
>>
>
>Different priorities?
>
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Kernel-janitors mailing list
>Kernel-janitors@lists.osdl.org
>https://lists.osdl.org/mailman/listinfo/kernel-janitors
>
>
Will it be better if I put KERN_CRIT on all printk lines?
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
prev parent reply other threads:[~2005-10-08 14:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-03 11:04 [KJ] [PATCH] arch/i386/kernel/doublefault.c Christophe Lucas
2005-10-03 11:12 ` Christophe Lucas
2005-10-03 12:06 ` slackfan
2005-10-03 12:40 ` Christophe Lucas
2005-10-03 12:47 ` Dinolinux
2005-10-03 15:07 ` slackfan
2005-10-08 13:32 ` Alexey Dobriyan
2005-10-08 14:09 ` Dinolinux [this message]
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=43480D56.408@tele2.no \
--to=anton.slack@tele2.no \
--cc=kernel-janitors@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.