Kernel spitting out messages during the init process.

Seph64 · 08-02-2009, 12:12 PM

Although I figure it must be due with the kernel config I am using, but during the init process (after the kernel loads), the kernel spits out a big load of messages that mixes with the init messages.

This would not be a problem if I knew everything was initialising ok. But there's a bootscript that is fails to load/work, and I can not tell what it is or why it is failing because of all the kernel messages.

I tried passing quiet through the boot options, but that only keeps the kernel quiet until the init process begins.

I am going to try using the .config the lfs livecd uses and recompile the kernel with that to see if that fixes the problem.

EDIT: Outputs from various commands + the kernel config I used (that booted successfully) have been posted on my blog: http://www.linuxquestions.org/blog/s...25#comment2725

I should've posted them in here in the first place, but that's why I edited this post. I hope I can get some help on making a working config soon.

hoes · 08-02-2009, 05:02 PM

I don't see the actual lines you see when booting.
Could you post them somewhere?
Check the logfiles for them, especially kernel.log.
And there is also a command to read kernel logs, but Ican't quite reminder how it's called.

Seph64 · 08-02-2009, 05:36 PM

http://pastebin.com/m2a44de58

That's from the first working kernel.

I just do not understand why the kernel is just spamming these messages during the init process.

I am going to compile a different kernel version to see if the problem is localized in the version of the kernel I am using.

markor · 08-03-2009, 03:35 AM

It is also a bit of hassle here, I have been using Ubuntu kernel in distribution and after some of kernel updates, it is spitting those messages during boot, with no reason.
(I used to use usb adsl modem).
But after another (small, same version and revision) kernel update,
problem was not there anymore.
It happened again after several automatic upgrades and fixed itself againg with kernel upgrade with same version.

So It seem to me it is like misconfigured something in build options Or some patches where not done right, few times.

hoes · 08-03-2009, 03:40 AM

I don't know what all this hassle is about.
You only get a lot of messages and the aren't even errors.
If you want to decrease the amount of messages, you should configure klogd.
That is the logger for kernel messages.

Have a look at:
http://www.linuxjournal.com/article/4058

i92guboj · 08-03-2009, 06:43 AM

I fail to see the problem either. That's what the kernel does, spit out messages. Nothing wrong with that.

Quote:

Originally Posted by Seph64

http://pastebin.com/m2a44de58

That's from the first working kernel.

I just do not understand why the kernel is just spamming these messages during the init process.

Respectfully, nope

The thing you pasted in that link happens *before* init goes into scene. That's the kernel booting, init comes *after* that.

If you are bothered by these messages I think that you can remove them by correctly configuring the kernel boot line in your grub/lilo.conf by adding the "quiet" option. The framebuffer configuration might have something to do with this as well, I don't know cause I really don't feel any sympathy for all this candy which is designed to hide everything which is happening behind the scenes and confuse me in the way. However, I understand why some people might find that info useless. Still, it's just info, not errors.

Quote:

Originally Posted by hoes

I don't know what all this hassle is about.
You only get a lot of messages and the aren't even errors.
If you want to decrease the amount of messages, you should configure klogd.
That is the logger for kernel messages.

Have a look at:
http://www.linuxjournal.com/article/4058

The system logger is started during init, so, it will have absolutely no effect at all over anything that happens before init, which is the case.

Seph64 · 08-03-2009, 08:59 AM

Quote:

Originally Posted by i92guboj

I fail to see the problem either. That's what the kernel does, spit out messages. Nothing wrong with that.

Respectfully, nope

The thing you pasted in that link happens *before* init goes into scene. That's the kernel booting, init comes *after* that.

Read Below.

hoes · 08-03-2009, 09:01 AM

Quote:

There's no log that includes the init log and these messages together, but yes, the bottom portion of these messages ARE appearing during init.

Can you indicate what is posted during init and what not?

Seph64 · 08-03-2009, 09:03 AM

What? I have photographic memory?

Hmm, actually, maybe this is the wrong log file after all. Lemme check the logs again.

Code:

Aug  2 04:58:48 Sephnix kernel: usb-storage: device scan complete
Aug  2 04:58:48 Sephnix kernel: isa bounce pool size: 16 pages
Aug  2 04:58:48 Sephnix kernel: usb-storage: device scan complete
Aug  2 04:58:48 Sephnix kernel: scsi 6:0:0:0: Direct-Access     Dell     USB Mass Storage  200 PQ: 0 ANSI: 0
Aug  2 04:58:48 Sephnix kernel: scsi 7:0:0:0: Direct-Access     Apple    iPod             1.62 PQ: 0 ANSI: 0
Aug  2 04:58:48 Sephnix kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk
Aug  2 04:58:48 Sephnix kernel: sd 6:0:0:0: Attached scsi generic sg2 type 0
Aug  2 04:58:48 Sephnix kernel: sd 7:0:0:0: [sdc] 19488471 4096-byte hardware sectors: (79.8 GB/74.3 GiB)
Aug  2 04:58:48 Sephnix kernel: sd 7:0:0:0: [sdc] Write Protect is off
Aug  2 04:58:48 Sephnix kernel: sd 7:0:0:0: [sdc] Mode Sense: 68 00 00 08
Aug  2 04:58:48 Sephnix kernel: sd 7:0:0:0: [sdc] Assuming drive cache: write through
Aug  2 04:58:48 Sephnix kernel: sd 7:0:0:0: [sdc] 19488471 4096-byte hardware sectors: (79.8 GB/74.3 GiB)
Aug  2 04:58:48 Sephnix kernel: sd 7:0:0:0: [sdc] Write Protect is off
Aug  2 04:58:48 Sephnix kernel: sd 7:0:0:0: [sdc] Mode Sense: 68 00 00 08
Aug  2 04:58:48 Sephnix kernel: sd 7:0:0:0: [sdc] Assuming drive cache: write through
Aug  2 04:58:48 Sephnix kernel:  sdc: sdc1
Aug  2 04:58:48 Sephnix kernel: sd 7:0:0:0: [sdc] Attached SCSI removable disk
Aug  2 04:58:48 Sephnix kernel: sd 7:0:0:0: Attached scsi generic sg3 type 0
Aug  2 04:58:49 Sephnix kernel: usb-storage: device scan complete
Aug  2 04:58:49 Sephnix kernel: scsi 8:0:0:0: Direct-Access     WD       10EACS External  1.75 PQ: 0 ANSI: 4
Aug  2 04:58:49 Sephnix kernel: sd 8:0:0:0: [sdd] 1953525168 512-byte hardware sectors: (1.00 TB/931 GiB)
Aug  2 04:58:49 Sephnix kernel: sd 8:0:0:0: [sdd] Write Protect is off
Aug  2 04:58:49 Sephnix kernel: sd 8:0:0:0: [sdd] Mode Sense: 23 00 00 00
Aug  2 04:58:49 Sephnix kernel: sd 8:0:0:0: [sdd] Assuming drive cache: write through
Aug  2 04:58:49 Sephnix kernel: sd 8:0:0:0: [sdd] 1953525168 512-byte hardware sectors: (1.00 TB/931 GiB)
Aug  2 04:58:49 Sephnix kernel: sd 8:0:0:0: [sdd] Write Protect is off
Aug  2 04:58:49 Sephnix kernel: sd 8:0:0:0: [sdd] Mode Sense: 23 00 00 00
Aug  2 04:58:49 Sephnix kernel: sd 8:0:0:0: [sdd] Assuming drive cache: write through

I believe this is the stuff that gets spit out during init. I believe it has something to do with external storage devices (External Hard Drive, and iPod).

hoes · 08-03-2009, 09:05 AM

I'd don't presume you have that but you could take a note of the first line you see flashing by during the init and copy from that line onwards from your log files. Just an idea.
But if you can indicate where it gets mixed that would help to pinpoint what is happening

Seph64 · 08-03-2009, 09:10 AM

What I am going to do is disconnect my external storage devices and see if it still spits out these messages.

Alright, I narrowed it down:

Code:

Aug  3 02:12:45 Sephnix kernel: [   22.850117] ACPI: PCI Interrupt 0000:03:02.0[A] -> GSI 18 (level, low) -> IRQ 18
Aug  3 02:12:45 Sephnix kernel: [   22.850276] Model 1003 Rev 00000000 Serial 10031102
Aug  3 02:12:45 Sephnix kernel: [   22.950333] Adding 1951856k swap on /dev/sda7.  Priority:1 extents:1 across:1951856k
Aug  3 02:12:45 Sephnix kernel: [   23.695221] EXT3 FS on sda5, internal journal
Aug  3 02:12:45 Sephnix kernel: [   23.759285] kjournald starting.  Commit interval 5 seconds
Aug  3 02:12:45 Sephnix kernel: [   23.759505] EXT3 FS on sda6, internal journal
Aug  3 02:12:45 Sephnix kernel: [   23.759617] EXT3-fs: mounted filesystem with ordered data mode.
Aug  3 02:12:45 Sephnix kernel: [   24.424806] e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Aug  3 02:12:45 Sephnix kernel: [   24.424921] e1000: eth0: e1000_watchdog: 10/100 speed: disabling TSO
Aug  3 02:12:55 Sephnix kernel: [   34.426189] eth0: no IPv6 routers present

After disconnecting the external storage devices, this is what is left that gets spit out during the init process.

jomen · 08-03-2009, 09:34 AM

These messages are perfectly normal - as hoes and i92guboj said.
Every piece of hardware in your machine which the kernel has built in support for will be recognized and configured - before init.
These messages are shown - unless you have a boot-time splash screen hiding them from you.

It is less messages now because there are less devices now.

You may be used to a "quiet" bootsplash which often is the default - and now are seeing what is normally shown, but what you did not yet see until your bootsplash somehow disappeared or is configured to not be quiet?

HTH

Seph64 · 08-03-2009, 09:38 AM

Yes, lets assume I am using a bootsplash on a brand new LFS installation...

I do not use a bootsplash, and the messages I specified are found during init.

I'll say this in big bold letters,STOP MAKING ASSUMPTIONS!

hoes · 08-03-2009, 09:48 AM

Please, seph64, take some time to read over the posts.
Everyone is saying it is normal you see those messages.
I see similar messages every time I boot.

I could be that this is the first time you see them, because they are normally filtered.
I suggested it could have something to do with klogd and it was also suggested it is because you normally have a bootsplash.

The idea about a bootsplash is that you normally have one configured which makes sure messages are hidden. On a new LFS system no bootsplash is configured and so you see the messages. Hope that makes sense to you.

Please, consider that all these people responding are only trying to help. They are not telling you what the problem is, but what might cause the problem. It is up to you to investigate these cases. Just remember that all these people are only trying to help with their personal experience. If you don't agree with what they are saying, than you can say so and start a discussion about it or ask for a way that you could check whether an assumption is the case or not. People are willing to help.

Seph64 · 08-03-2009, 09:53 AM

Well yes, I am sorry, but I have never seen these messages before, even in previous installed LFS systems when they were freshly installed.

So it's kinda irritating to see these "normal" messages now when they never appeared in previous fresh installs of LFS.

I am sorry.