FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 11-18-2011, 08:25 PM
Marcus Osdoba
 
Default Bug#649211: linux-image-486: /sys/devices/system/cpu/cpu0/crash_notes and no topology

Package: linux-image-486
Version: 3.1.1
Severity: important

Hi,
I have tested virt-manager on my Debian Squeeze on several installations.
Unfortunatly it does not work with 486 variant of the kernel [1]. When running
the 686 variant, the topology is found in /sys/devices/system/cpu/cpu0/ , but
not with 486 [2].

In some situtuations the user is not able or does not want to use the 686-pae
version (e.g. my lovely testing platform X40 has no PAE capable processor and
in VirtualBox the performance suffers when activating PAE and one does usually
not need PAE for 32bit testing vms).

I have found and old bugreport, which describes a similar problem.
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.17/+bug/66812
When crawling the net, most of this errors were solved by choosing the 686
variant of the kernel, which is not available anymore (not beyond Squeeze). The
Squeeze kernel does not have cgroup_memory built in, which prevents virt-
manager from working with LXC.

The 486 kernel from wheezy and sid (3.0.0 and 3.1.1) didn't boot proper on my
X40, but in VirtualBox, I was able to verify, that these versions still don't
show cputopology in /sys/devices/system.

Regards,
Marcus

[1]
Error polling connection 'qemu:///system': cannot open
/sys/devices/system/cpu/cpu0/topology/physical_package_id: No such file or
directory
Error polling connection 'lxc:///': cannot open
/sys/devices/system/cpu/cpu0/topology/physical_package_id: No such file or
directory

[2]
root@thinkpad:/home/ossy# ls -l /sys/devices/system/cpu/cpu0/
insgesamt 0
drwxr-xr-x 3 root root 0 18. Nov 21:34 cpufreq
drwxr-xr-x 7 root root 0 18. Nov 21:34 cpuidle
-r-------- 1 root root 4096 18. Nov 21:38 crash_notes
root@thinkpad:/home/ossy# cat /sys/devices/system/cpu/cpu0/crash_notes
377f1e5c



-- System Information:
Debian Release: 6.0.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.39-bpo.2-486
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20111118212539.3304.56929.reportbug@thinkpad.fritz .box">http://lists.debian.org/20111118212539.3304.56929.reportbug@thinkpad.fritz .box
 
Old 11-18-2011, 09:55 PM
Ben Hutchings
 
Default Bug#649211: linux-image-486: /sys/devices/system/cpu/cpu0/crash_notes and no topology

On Fri, Nov 18, 2011 at 10:25:39PM +0100, Marcus Osdoba wrote:
> Package: linux-image-486
> Version: 3.1.1
> Severity: important
>
> Hi,
> I have tested virt-manager on my Debian Squeeze on several installations.
> Unfortunatly it does not work with 486 variant of the kernel [1]. When running
> the 686 variant, the topology is found in /sys/devices/system/cpu/cpu0/ , but
> not with 486 [2].

The 486 flavour only supports a single processor (since all SMP-
capable processors also support PAE) so the CPU topology is never
very interesting and the code to expose it in sysfs is not built.
Maybe it should be, for consistency.

[...]
> The 486 kernel from wheezy and sid (3.0.0 and 3.1.1) didn't boot proper on my
> X40, but in VirtualBox, I was able to verify, that these versions still don't
> show cputopology in /sys/devices/system.

This is far more important. Please can you explain further how it
fails. Does it hang or crash? Can you provide the kernel log
messages? (Use netconsole or boot without the 'quiet' option and send
a photo of the screen.)

Ben.

--
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
- Albert Camus



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20111118225538.GN3366@decadent.org.uk">http://lists.debian.org/20111118225538.GN3366@decadent.org.uk
 
Old 11-20-2011, 09:49 AM
Marcus Osdoba
 
Default Bug#649211: linux-image-486: /sys/devices/system/cpu/cpu0/crash_notes and no topology

Am 18.11.2011 23:55, schrieb Ben Hutchings:

On Fri, Nov 18, 2011 at 10:25:39PM +0100, Marcus Osdoba wrote:

Package: linux-image-486
Version: 3.1.1
Severity: important

Hi,
I have tested virt-manager on my Debian Squeeze on several installations.
Unfortunatly it does not work with 486 variant of the kernel [1]. When running
the 686 variant, the topology is found in /sys/devices/system/cpu/cpu0/ , but
not with 486 [2].


The 486 flavour only supports a single processor (since all SMP-
capable processors also support PAE) so the CPU topology is never
very interesting and the code to expose it in sysfs is not built.
Maybe it should be, for consistency.

Beyond Squeeze, one is forced to use 486 for systems without PAE
(physically not available or not choosen to be activated for some
reason). On these 32bit systems it is still possible to test and create
qemu-vms and lxc-containers with virt-manager.


But the standard kernel is not able to do so. If possible, please enable
memory_cgroup controller in Squeeze kernel (activated with kernel
commandline like in 2.6.39+) -> so it is possible to use 686 from
Squeeze then.


I think, one should know, that the 486 does not provide cputopology
anymore (for consistency it should, yes). Since some of my boxes are not
able/not want to use 686-PAE, I'm in a gap.


Marcus

P.S.: Booting version 3.1.1-486 on X40 is another bug for me ;-)



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4EC8DB3C.2010907@googlemail.com">http://lists.debian.org/4EC8DB3C.2010907@googlemail.com
 

Thread Tools




All times are GMT. The time now is 01:05 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org