On Sun, Jan 04, 2015 at 10:18:10AM -0800, Paul Rogers wrote: > So, my LFS-7.2 install is complete, and apparently functional. Last > month I asked about updating the kernel in the LFS-7.2 I've been > building. Ken suggested going fro the 3.5.2 up to 3.14. I decided to > make that in two jumps, stopping first at 3.10.62-LTS. > > There were interruptions. I've built that now, but during boot there > appears to be something dumping some data on the console about once a > second! It's hard to tell exactly when it starts. When it gets to the > Login prompt, I've only got about one second to use Shift-PgUp before > the next console write jerks me back. At that point it's "00 00 00 00 > 00 00"; no identifier of who's doing it or what it means I've seen. It > might be after udev starts, but I'm not sure. It's got to be something > introduced in the 3.10.62 kernel, because I don't see this with 3.5.2. > So I've a few questions: >
It is possible that one of the drivers is dumping this rubbish. On my netbook, I started with ubuntu, and sanitised their config enough to boot before I ever tried to put LFS on it. But with LFS I was getting similar messages in my log (so, the log was huge). In that case, dropping an unnecessary driver fixed it (something in the network or wifi area, built as a module). More generally, setting LOGLEVEL in /etc/sysconfig/console is the way to quieten the log. From a quick look at old bootscripts, and the output from 'dmesg --help' you can set the loglevel using 'dmesg -n N' where N is from 1 to 8. I normally run with LOGLEVEL="4" in /etc/sysconfig/console, but you might need to tweak it if a driver acquired a silly default setting. So, try your choice of 1 emerg 2 alert 3 crit 4 err 5 warn 6 notice 7 info 8 debug (i.e. use the highest setting which gives what you need without an unusable console - for most people, 4 or less is probably the way to go). If it is indeed a very noisy driver, you might need to temporarily set a lower level until you are able to read dmesg or the log to see where it is coming from. I also have to doubt what you say about "introduced in the 3.10.62 kernel" - what we know is that it did not happen in 3.5.2, but did happen in 3.10.62. If you *had to* bisect what changed (for excessive logging, I doubt that will be necessary!) you would probably need to check 3.10.0 (and then bisect between 3.5.0 (sic) and 3.10.0 from Linus' tree if it showed up in 3.10.0), or else bisect between 3.10.0 and 3.10.62 in the stable 3.10 tree if it is indeed new during 3.10. In 3.18.1 the kernel has a setting for the default loglevel, CONFIG_MESSAGE_LOGLEVEL_DEFAULT : for me, that is set to =4 which matches my sysconfig setting. I do not recall when that option first appeared, but it is possible that you might have it, but with a larger value. ĸen -- Nanny Ogg usually went to bed early. After all, she was an old lady. Sometimes she went to bed as early as 6 a.m. -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
