Package: linux-2.6
Version: 2.6.38-5
Severity: minor
File: /lib/modules/2.6.38-2-686/kernel/sound/pci/hda/snd-hda-intel.ko
Tags: upstream
Got the following lines in my syslog. Can't say I have heard any
clicks, and I don't know how to repro, but the text says I should
report it so I am:
May 22
Package: linux-tools-2.6.38
Version: 2.6.38-3
Severity: normal
File: /usr/bin/perf_2.6.38
Event types listed by "perf list" can't be used for profiling (at
least on my system).
My expectation was that "perf list" would list only events I could
actually use.
For example, note how instructions ar
Package: linux-tools-2.6.38
Version: 2.6.38-3
Severity: normal
File: /usr/bin/perf
"perf" comes with build-in self testing facility, and it fails:
"
johan@johansdator:~$ sudo perf test
[sudo] password for johan:
1: vmlinux symtab matches kallsyms: FAILED!
2: detect open syscall event: FAILED
04:40AM +0200, Johan Walles wrote:
>> Package: linux-image-2.6.16-2-686-smp
>> Version: 2.6.16-17
>> Severity: normal
>> File: /vmlinuz
>>
>>
>> Don't know how important this is, going with "normal".
>>
>> I'm getting thi
reopen 444880
thanks
Re-opening awaiting information about in which kernel this has been fixed.
Regards //Johan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi!
I'll be re-opening this in a short while while waiting for information
about which kernel version this bug has been fixed in. Without
knowing which kernel version has the fix this is really hard for me
to verify.
If this has not been fixed, feel free to just leave this bug open until it is.
Maximillian / Bastian,
on which kernel version does this work for any of you?
For me it's still broken on this kernel, using the repro provided in
the original bug report:
Linux version 2.6.26-1-686 (Debian 2.6.26-5) ([EMAIL PROTECTED]) (gcc
version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23))
gt; -- Vidarebefordrat meddelande --
> From: Bastian Blank <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Date: Mon, 6 Oct 2008 19:16:52 +0200
> Subject: works
> Works here flawless.
>
> Bastian
>
> --
> There are some things worth dying for.
>
Here you go. /J
dmesg.log.gz
Description: GNU Zip compressed data
Package: linux-image-2.6.26-1-686
Version: 2.6.26-3
Severity: minor
Since 2.6.26-1 I'm getting this from the kernel on every boot:
"
kernel: [0.00] NR_CPUS: 8, nr_cpu_ids: 4
"
2.6.25-2 didn't say anything about 8 CPUs.
Here's my /proc/cpuinfo, will attach full dmesg:
processor :
As a workaround for this if you want the kernel symbols for OProfile,
you can use this script instead of opreport:
http://marc.info/?l=oprofile-list&m=121514749918466&q=p3
It fetches kernel symbol information from /proc/kallsyms and lists
them in a format identical to what opreport -l uses.
//J
Package: linux-image-2.6.22-2-686
Version: 2.6.22-4
Severity: normal
When my system boots, it first says twice that the write cache for sda is
enabled. Then it says once that it is
disabled.
What I'd like to get out of this bug report is to know if that last message is
correct, and if so, wh
Package: linux-image-2.6.21-2-686
Version: 2.6.21-6
Severity: normal
File: /boot/vmlinuz-2.6.21-2-686
Try this:
1. At one prompt, do "cat".
Now, switch to another prompt and...
2. Do "pstree -p|grep cat" to find out the PID of your cat command. I
get 20502.
3. Do "cat /proc/20502/wchan". I get
Package: linux-image-2.6.18-3-686
Version: 2.6.18-7
Severity: minor
File: /boot/vmlinuz-2.6.18-3-686
dmesg says this on my SMP system:
...
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
ACPI: Core revision 20060707
CPU0: Intel(R) Pentium(R) D CPU 3.20GHz stepping 04
SMP
Package: linux-image-2.6.16-2-686-smp
Version: 2.6.16-17
Severity: normal
File: /vmlinuz
Don't know how important this is, going with "normal".
I'm getting this in my syslog:
kernel: More than 8 CPUs detected and CONFIG_X86_PC cannot handle it.
kernel: Use CONFIG_X86_GENERICARCH or CONFIG_X86_BI
15 matches
Mail list logo
