Date: Sat, 8 Nov 2003 13:17:25 -0800
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "Prakash K. Cheemplavam" <prakashpublic@gmx.de>
Cc: piggin@cyberone.com.au, linux-kernel@vger.kernel.org
Subject: Re: 2.9test9-mm1 and DAO ATAPI cd-burning corrupt
Message-Id: <20031108131725.105639a1.rddunlap@osdl.org>
In-Reply-To: <3FACE20A.7060301@gmx.de>
References: <20031106130030.GC1145@suse.de>
	<20031106130553.GD1145@suse.de>
	<3FAA4880.8090600@cyberone.com.au>
	<20031106131141.GE1145@suse.de>
	<3FAA4D48.6040709@gmx.de>
	<20031106133136.GA477@suse.de>
	<3FAA5043.8060907@gmx.de>
	<20031106134713.GA798@suse.de>
	<3FAA5397.6010702@gmx.de>
	<20031106135134.GA1194@suse.de>
	<3FAA5CCB.5030902@gmx.de>
	<3FAB0754.2040209@cyberone.com.au>
	<3FAB7F94.7050504@gmx.de>
	<3FAB82A2.4070907@cyberone.com.au>
	<3FAB8428.7090307@gmx.de>
	<3FAB870D.1050003@cyberone.com.au>
	<3FAB95B9.3020601@gmx.de>
	<3FAB9817.5020502@cyberone.com.au>
	<3FAB9C2B.2040907@gmx.de>
	<3FAB9F97.6050706@cyberone.com.au>
	<3FABA364.9000404@gmx.de>
	<3FABA5A7.904@cyberone.com.au>
	<3FABA6EF.90207@gmx.de>
	<3FABA788.1080000@cyberone.com.au>
	<3FABAB5B.5090105@gmx.de>
	<3FABAE0B.6020601@cyberone.com.au>
	<3FABB08B.3080006@gmx.de>
	<3FABB571.6070804@cyberone.com.au>
	<3FABBEC7.4010702@gmx.de>
	<3FAC51A1.30307@cyberone.com.au>
	<3FACE20A.7060301@gmx.de>
Organization: OSDL
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2177
Lines: 63

On Sat, 08 Nov 2003 13:31:06 +0100 "Prakash K. Cheemplavam" <prakashpublic@gmx.de> wrote:

| Nick Piggin wrote:
| > 
| > 
| > Prakash K. Cheemplavam wrote:
| > 
| >>
| >>> Oh ok. Well whenever you get a chance to... Sorry that last patch
| >>> I sent was empty. Here is the correct one for when you get time.
| >>
| >>
| >> Yeah, runs nicely. (dmesg is quiet, as well.) Seems like it was only a 
| >> minor issue in mm2, lloking at the patch...Very well.
| > 
| > 
| > Thanks a lot for your patience Prakash. Looks like its fixed then.
| 
| Happy I could help. :-)
| 
| > Yeah it was a pretty minor problem: you were triggering lots of warnings,
| > but if you can't see them in dmesg, maybe /proc/sys/kernel/printk is
| > configured to not show them.
| > 
| > Have a look at Documentation/sysctl/kernel.txt if you'd like to fix that
| > up. Thanks again.
| 
| Hmm, the document explains the setting but not exactly how to change 
| them. cat printk gives me:
| 
| 1       4       1       7
| 
| which according to the doc means:
| 
| - console_loglevel: messages with a higher priority than
|    this will be printed to the console
| - default_message_level: messages without an explicit priority
|    will be printed with this priority
| - minimum_console_loglevel: minimum (highest) value to which
|    console_loglevel can be set
| - default_console_loglevel: default value for console_loglevel
| 
| Are my settings not enough? How to change them? Using echo x y z w > 
| bla/printk ?

Yes, that works.  Or to change only console_loglevel, you can use
Alt-SysRq-# (use 9 for # to print/log all messages) [works only if
you have Magic SysRq key enabled].

| Another q: I guess I should enable frame pointers in kernel compilation 
| otherwise I won't get call traces, right?

Frame pointers can help with call traces, but we usually get decent
back traces even without them.  IOW, they aren't required for
back traces.

--
~Randy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/