From: James Simmons <hidden> Date: 2010-01-06 17:37:24
For a long time I have gotten two pictures of Tux showing up when I
include the Tux display option in my custom kernel builds. I don't
know how many kernel revisions ago it was when I started noticing
this. It seems like it might have been early in the 2.6 series
kernels.
dmesg:
Linux agpgart interface v0.103
agpgart-intel 0000:00:00.0: Intel 945GME Chipset
agpgart-intel 0000:00:00.0: detected 7932K stolen memory
agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000
[drm] Initialized drm 1.1.0 20060810
i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
i915 0000:00:02.0: setting latency timer to 64
[drm] set up 7M of stolen space
integrated sync not supported
ACPI: Battery Slot [BAT0] (battery present)
[drm] initialized overlay support
[drm] LVDS-8: set mode 1024x600 27
Console: switching to colour frame buffer device 128x37
fb0: inteldrmfb frame buffer device
registered panic notifier
[drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
From: Miles Lane <hidden> Date: 2010-01-06 17:43:08
On Wed, Jan 6, 2010 at 12:37 PM, James Simmons [off-list ref] wrote:
quoted
For a long time I have gotten two pictures of Tux showing up when I
include the Tux display option in my custom kernel builds. I don't
know how many kernel revisions ago it was when I started noticing
this. It seems like it might have been early in the 2.6 series
kernels.
From: James Simmons <hidden> Date: 2010-01-06 17:48:22
On Wed, Jan 6, 2010 at 12:37 PM, James Simmons [off-list ref] wrote:
quoted
quoted
For a long time I have gotten two pictures of Tux showing up when I
include the Tux display option in my custom kernel builds. I don't
know how many kernel revisions ago it was when I started noticing
this. It seems like it might have been early in the 2.6 series
kernels.
From: Bruno Prémont <bonbons@linux-vserver.org> Date: 2010-01-06 18:06:20
On Wed, 06 January 2010 Miles Lane [off-list ref] wrote:
For a long time I have gotten two pictures of Tux showing up when I
include the Tux display option in my custom kernel builds. I don't
know how many kernel revisions ago it was when I started noticing
this. It seems like it might have been early in the 2.6 series
kernels.
Unless your system has exactly one CPU without hyperthreading and with
exactly one core this is the correct bahavior, one tux per logical CPU.
If you just want a single tux you can run your kernel on a system with
only one logical CPU, boot it with maxcpus=1 or rebuild it with
CONFIG_SMP=n... though in those case you will not be able to benefit
from all of your CPU's resources..
Bruno
From: Miles Lane <hidden> Date: 2010-01-06 18:06:50
On Wed, Jan 6, 2010 at 12:59 PM, Bruno Prémont
[off-list ref] wrote:
On Wed, 06 January 2010 Miles Lane [off-list ref] wrote:
quoted
For a long time I have gotten two pictures of Tux showing up when I
include the Tux display option in my custom kernel builds. I don't
know how many kernel revisions ago it was when I started noticing
this. It seems like it might have been early in the 2.6 series
kernels.
Unless your system has exactly one CPU without hyperthreading and with
exactly one core this is the correct bahavior, one tux per logical CPU.
If you just want a single tux you can run your kernel on a system with
only one logical CPU, boot it with maxcpus=1 or rebuild it with
CONFIG_SMP=n... though in those case you will not be able to benefit
from all of your CPU's resources..
Bruno
Oh! Well, that explains it. That is truly weird functionality. Is
Tux a de facto
CPU presence indicator? It doesn't make any sense to me, if so.
Miles
From: Miles Lane <hidden> Date: 2010-01-06 18:08:53
On Wed, Jan 6, 2010 at 12:48 PM, James Simmons [off-list ref] wrote:
quoted
On Wed, Jan 6, 2010 at 12:37 PM, James Simmons [off-list ref] wrote:
quoted
quoted
For a long time I have gotten two pictures of Tux showing up when I
include the Tux display option in my custom kernel builds. I don't
know how many kernel revisions ago it was when I started noticing
this. It seems like it might have been early in the 2.6 series
kernels.
Okay. I disabled those two options and still get the two Tuxes. I
gues Bruno's message is correct, and I get two Tuxes because I have an
Atom processor with two cores.
Miles
From: Peter Zijlstra <peterz@infradead.org> Date: 2010-01-06 18:25:47
On Wed, 2010-01-06 at 13:10 -0500, Miles Lane wrote:
On Wed, Jan 6, 2010 at 1:07 PM, Peter Zijlstra [off-list ref] wrote:
quoted
On Wed, 2010-01-06 at 12:16 -0500, Miles Lane wrote:
quoted
For a long time I have gotten two pictures of Tux showing up when I
include the Tux display option in my custom kernel builds.
Doesn't it show one for each cpu in the system?
Apparently so. And, why this should be true is beyond me.
drivers/video/fbmem.c:
int fb_show_logo(struct fb_info *info, int rotate)
{
int y;
y = fb_show_logo_line(info, rotate, fb_logo.logo, 0,
num_online_cpus());
y = fb_show_extra_logos(info, y, rotate);
return y;
}
I guess its just a cute way of showing off how many cpus you've got ;-)