Re: [PATCH] leave loglevel at 7 through sysrq output so you can actually read it

Hi,

On Fri, 6 Apr 2007, Martin Bligh wrote:

> > I think you have to tell sysrq_handle_loglevel() about this too...
> 
> Not sure why? That just changes the current loglevel, and seems
> unaffected.

Who's the last to set console_loglevel?

> I did test the patch, and it works fine.

Did you check /proc/sys/kernel/printk?

bye, Roman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [PATCH] leave loglevel at 7 through sysrq output so you can actually read it
  - From: Roman Zippel <[email protected]>

References:
- Re: [PATCH] leave loglevel at 7 through sysrq output so you can actually read it
  - From: Roman Zippel <[email protected]>
- Re: [PATCH] leave loglevel at 7 through sysrq output so you can actually read it
  - From: Martin Bligh <[email protected]>

Prev by Date: restoring x86 BIOS state before reboot
Next by Date: Re: [PATCH] Perverting cciss
Previous by thread: Re: [PATCH] leave loglevel at 7 through sysrq output so you can actually read it
Next by thread: Re: [PATCH] leave loglevel at 7 through sysrq output so you can actually read it
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]