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

Hi, On Fri, 6 Apr 2007, Roman Zippel wrote: > > I did test the patch, and it works fine. > > Did you check /proc/sys/kernel/printk? BTW for even more fun check this with "echo 4 > /proc/sys/kernel/sysrq". bye, Roman - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

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

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

Roman Zippel wrote: On Thu, 5 Apr 2007, Martin Bligh wrote: We carefully set loglevel to 7, and print the sysrq messsage as to what event we're doing, but we can't actually see the output as it sets it back before calling the handler, rather than after. Move the assignment down one line. I

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

On Thu, 5 Apr 2007, Martin Bligh wrote: > We carefully set loglevel to 7, and print the sysrq messsage > as to what event we're doing, but we can't actually see > the output as it sets it back before calling the handler, > rather than after. > > Move the assignment down one line. I think you

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

On Thu, 5 Apr 2007, Martin Bligh wrote: We carefully set loglevel to 7, and print the sysrq messsage as to what event we're doing, but we can't actually see the output as it sets it back before calling the handler, rather than after. Move the assignment down one line. I think you have

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

Roman Zippel wrote: On Thu, 5 Apr 2007, Martin Bligh wrote: We carefully set loglevel to 7, and print the sysrq messsage as to what event we're doing, but we can't actually see the output as it sets it back before calling the handler, rather than after. Move the assignment down one line. I

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

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

Hi, On Fri, 6 Apr 2007, Roman Zippel wrote: I did test the patch, and it works fine. Did you check /proc/sys/kernel/printk? BTW for even more fun check this with echo 4 /proc/sys/kernel/sysrq. bye, Roman - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body

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

We carefully set loglevel to 7, and print the sysrq messsage as to what event we're doing, but we can't actually see the output as it sets it back before calling the handler, rather than after. Move the assignment down one line. Signed-off-by: Martin J. Bligh <[EMAIL PROTECTED]> diff -aurpN -X

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

We carefully set loglevel to 7, and print the sysrq messsage as to what event we're doing, but we can't actually see the output as it sets it back before calling the handler, rather than after. Move the assignment down one line. Signed-off-by: Martin J. Bligh [EMAIL PROTECTED] diff -aurpN -X