Re: Bug#595223: linux-image-2.6-xen-amd64: channel scanning with b2c2-flexcop-pci
Hello,do you have found the promlem in the meanwhile?Thanks in advance,regardsHerbert Von: "Herbert Lueger" klo...@web.deGesendet: 28.10.2010 17:35:09An: 595...@bugs.debian.org, "Herbert Lueger" klo...@web.de, debian-kernel@lists.debian.orgBetreff: Re: Bug#595223: linux-image-2.6-xen-amd64: channel scanning with b2c2-flexcop-pci Hi,are there any news on this issue? Maybe you have found and fixed the problem in the meanwhile.Thanks in advance,regardsHerbert Neu: WEB.DE De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: https://produkte.web.de/go/demail02 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1669115769.1936079.1288771924346.javamail.fm...@mwmweb020
Re: 2.6.32 with ngene -- traceback
Hi,do you need any further informations?Thanks in advance,regardsherbert Von: "Herbert Lueger" klo...@web.deGesendet: 27.10.2010 18:29:45An: debian-kernel@lists.debian.org, "Herbert Lueger" klo...@web.deBetreff: 2.6.32 with ngene -- traceback Hi,i'm trying to find a solution for a cineS2 dvb-card under a xen DomU. I testet to build the latest v4l-driver modules from mercurial. Building under linux-image-2.6.32-5-xen-amd64 is working without any problems. The CineS2 TV-card is hidden via piback.hide and imported to the domU via the pci command in the domU config file. When i boot the domU i always get a traceback.When i use the same driver under non-xen kernel everything is working. Only under XEN the problem occours.Attached you can find the output of dmesg.IRQ 18 is shared with two usb-controllers.Sorry i'm not sure if i'm right in this mailinglist, or if i should open a troubleticket at debian kernel side. Thanks in advance,regardsHerbert[1.987639] input: PC Speaker as /devices/platform/pcspkr/input/input1[2.308933] nGene PCIE bridge driver, Copyright (C) 2005-2007 Micronas[2.309153] ngene :00:00.0: enabling device ( - 0002)[2.309269] ngene :00:00.0: Xen PCI enabling IRQ: 18[2.309280] alloc irq_desc for 18 on node 0[2.309283] alloc kstat_irqs on node 0[2.309303] ngene: Found Linux4Media cineS2 DVB-S2 Twin Tuner (v5)[2.310004] ngene :00:00.0: setting latency timer to 64[2.310293] ngene: Device version 1[2.310339] ngene :00:00.0: firmware: requesting ngene_15.fw[2.347956] Error: Driver 'pcspkr' is already registered, aborting...[2.373354] ngene: Loading firmware file ngene_15.fw.[4.384106] ngene: Command timeout cmd=11 prev=02[4.384124] host_to_ngene (c000): 00 00 00 00 00 00 00 00[4.384135] ngene_to_host (c100): 00 01 00 00 00 00 00 00[4.384145] dev-hosttongene (88000724a000): 11 01 00 d0 00 04 00 00[4.384154] dev-ngenetohost (88000724a100): 00 00 00 00 00 00 00 00[4.384450] ngene: probe of :00:00.0 failed with error -5[4.385161] BUG: unable to handle kernel paging request at c9097770[4.385174] IP: [8113f18a] sysfs_open_file+0x77/0x2aa[4.385186] PGD 7c42067 PUD 7c43067 PMD 7c44067 PTE 0[4.385198] Oops: [#1] SMP [4.385206] last sysfs file: /sys/devices/pci-0/pci:00/:00:00.0/i2c-0/uevent[4.385214] CPU 0 [4.385219] Modules linked in: ngene snd_pcm snd_timer snd dvb_core soundcore snd_page_alloc i2c_core evdev pcspkr ext3 jbd mbcache xen_netfront xen_blkfront[4.385254] Pid: 156, comm: udevd Not tainted 2.6.32-5-xen-amd64 #1 [4.385261] RIP: e030:[8113f18a] [8113f18a] sysfs_open_file+0x77/0x2aa[4.385271] RSP: e02b:880006c77d78 EFLAGS: 00010286[4.385277] RAX: 8800070160a0 RBX: ffed RCX: [4.385285] RDX: 0001 RSI: 8800078df9c8 RDI: 8800070160a0[4.385291] RBP: 880007748b40 R08: 880007016054 R09: 81676150[4.385298] R10: 880006c77e48 R11: 811533e5 R12: c9097748[4.385305] R13: 8800070160a0 R14: 8800078df9c8 R15: 880007748b40[4.385316] FS: 7f7663b907a0() GS:880003023000() knlGS:[4.385324] CS: e033 DS: ES: CR0: 8005003b[4.385330] CR2: c9097770 CR3: 07112000 CR4: 2620[4.385338] DR0: DR1: DR2: [4.385345] DR3: DR6: 0ff0 DR7: 0400[4.385352] Process udevd (pid: 156, threadinfo 880006c76000, task 880007d34710)[4.385360] Stack:[4.385364] 0024 880007748b40 [4.385375] 0 8800078df9c8 0024 8113f113 810ed986[4.385388] 0 880007486000 8800062feb00 8800078d7840 [4.385404] Call Trace:[4.385410] [8113f113] ? sysfs_open_file+0x0/0x2aa[4.385419] [810ed986] ? __dentry_open+0x19d/0x2bf[4.385427] [810f90d7] ? do_filp_open+0x4e4/0x94b[4.385437] [81250b7e] ? sys_recvfrom+0xb2/0x11a[4.385446] [8100ec5f] ? xen_restore_fl_direct_end+0x0/0x1[4.385454] [81102109] ? alloc_fd+0x67/0x10c[4.385461] [810ed717] ? do_sys_open+0x55/0xfc[4.385469] [81011b42] ? system_call_fastpath+0x16/0x1b[4.385475] Code: ff f2 ae 48 c7 c7 50 61 67 81 48 f7 d1 48 89 ca e8 40 6c 05 00 4c 89 ef bb ed ff ff ff e8 f3 15 00 00 48 85 c0 0f 84 25 02 00 00 49 8b 44 24 28 48 85 c0 74 13 48 8b 68 08 48 85 ed 74 0a 41 8b [4.385576] RIP [8113f18a] sysfs_open_file+0x77/0x2aa[4.385584] RSP 880006c77d78[4.385590] CR2: c9097770[4.385596] ---[ end trace e428cb227937b038 ]---Maybe someone has a solution to fix this problem.Thanks in advance,regardsHerbert WEB.DE DSL Doppel-Flat ab 19,99 /mtl.!
Bug#602273: linux-image-2.6.32-5-686-bigmem: domU hangs during dom0 reboot, recovers when dom0 uptime caught up
Package: linux-image-2.6.32-5-686-bigmem Version: 2.6.32-26 Severity: normal Steps to reproduce: 1) use 64-bit squeeze as dom0 2) use 32-bit squeeze as domU 3) reboot dom0 Expected results: 3) domU's state is saved to disk and then restored Actual results: 2) domU's state is saved to disk but it hangs after restore More info: 1) Saving and restoring the domU with xm save and xm restore worked at least twice. The problem occurs only if dom0 is rebooted. = Is some clock perhaps visible to the domU and which then gets confused when it is reset and thus goes backwards in time? 2) hypervisor and dom0 information: overlord2:~$ dpkg-query -W xen-hypervisor-4.0-amd64 linux-image-$(uname -r) linux-image-2.6.32-5-xen-amd64 2.6.32-27 xen-hypervisor-4.0-amd644.0.1-1 overlord2:~$ sudo xm info host : overlord2 release: 2.6.32-5-xen-amd64 version: #1 SMP Wed Oct 20 02:22:18 UTC 2010 machine: x86_64 nr_cpus: 4 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz: 2394 hw_caps: bfebfbff:20100800::0940:e3bd::0001: virt_caps : hvm hvm_directio total_memory : 8189 free_memory: 3 node_to_cpu: node0:0-3 node_to_memory : node0:3 node_to_dma32_mem : node0:3 max_node_id: 0 xen_major : 4 xen_minor : 0 xen_extra : .1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params: virt_start=0x8000 xen_changeset : unavailable xen_commandline: cc_compiler: gcc version 4.4.5 20100824 (prerelease) (Debian 4.4.4-11) cc_compile_by : waldi cc_compile_domain : debian.org cc_compile_date: Fri Sep 3 15:38:12 UTC 2010 xend_config_format : 4 overlord2:~$ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Quad CPUQ6600 @ 2.40GHz stepping: 11 cpu MHz : 2394.082 cache size : 4096 KB fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu de tsc msr pae mce cx8 apic sep mtrr mca cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good aperfmperf pni est ssse3 cx16 hypervisor lahf_lm bogomips: 4788.16 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Quad CPUQ6600 @ 2.40GHz stepping: 11 cpu MHz : 2394.082 cache size : 4096 KB fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu de tsc msr pae mce cx8 apic sep mtrr mca cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good aperfmperf pni est ssse3 cx16 hypervisor lahf_lm bogomips: 4788.16 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Quad CPUQ6600 @ 2.40GHz stepping: 11 cpu MHz : 2394.082 cache size : 4096 KB fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu de tsc msr pae mce cx8 apic sep mtrr mca cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good aperfmperf pni est ssse3 cx16 hypervisor lahf_lm bogomips: 4788.16 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Quad CPUQ6600 @ 2.40GHz stepping: 11 cpu MHz : 2394.082 cache size : 4096 KB fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu de tsc msr pae mce cx8 apic sep mtrr mca cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good aperfmperf pni est ssse3 cx16 hypervisor lahf_lm bogomips: 4788.16 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: 3) domU information: $ dpkg-query -W linux-image-$(uname -r) linux-image-2.6.32-5-686-bigmem 2.6.32-26 4) We used sudo xm dump-core squeeze32 squeeze32.dump to save the memory of the stuck domU to disk. 5) We used crash -s --no_panic -e emacs vmlinux-2.6.32-5-686-bigmem squeeze32.dump to analyze the
Bug#600846: The problem also exists with linux-image-2.6.36-rc6-amd64 and xserver.xorg 7.5+8
The problem also exists with linux-image-2.6.36-rc6-amd64 and xserver.xorg 7.5+8 . -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cd11e53.8070...@online.de
Bug#602273: linux-image-2.6.32-5-686-bigmem: domU hangs during dom0 reboot, recovers when dom0 uptime caught up
package linux-image-2.6.32-5-686-bigmem found 602273 2.6.32-27 thanks This issue looks a lot like [Xen-devel] DomU clock jumps forward then freezes after Dom0 reboot http://lists.xensource.com/archives/html/xen-devel/2010-10/msg00498.html and [Xen-devel] Migrated domUs hangs http://lists.xensource.com/archives/html/xen-devel/2010-10/msg00057.html We are going to test the patch from http://lists.xensource.com/archives/html/xen-devel/2010-10/msg01261.html -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/84wrou6avn.fsf...@sauna.l.org
Processed: Re: linux-image-2.6.32-5-686-bigmem: domU hangs during dom0 reboot, recovers when dom0 uptime caught up
Processing commands for cont...@bugs.debian.org: package linux-image-2.6.32-5-686-bigmem Limiting to bugs with field 'package' containing at least one of 'linux-image-2.6.32-5-686-bigmem' Limit currently set to 'package':'linux-image-2.6.32-5-686-bigmem' found 602273 2.6.32-27 Bug #602273 [linux-image-2.6.32-5-686-bigmem] linux-image-2.6.32-5-686-bigmem: domU hangs during dom0 reboot, recovers when dom0 uptime caught up Bug Marked as found in versions linux-2.6/2.6.32-27. thanks Stopping processing here. Please contact me if you need assistance. -- 602273: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602273 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.128877477130108.transcr...@bugs.debian.org
Bug#600846: The problem also exists with linux-image-2.6.36-rc6-amd64 and xserver.xorg 7.5+8
On Wed, 03 Nov 2010, hu...@online.de wrote: The problem also exists with linux-image-2.6.36-rc6-amd64 and xserver.xorg 7.5+8 . oh well, please double check with 2.6.36-trunk-amd64. In the likely case of failure please report it upstream in bugzilla.kernel.org and let us know the bug nr so that we can track it. thank you very much. -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101103100627.ga5...@stro.at
Bug#600846: Problem also with linux-image-2.6.36-trunk-amd64, but another interesting detection
As expected, the problem also exists with linux-image-2.6.36-trunk-amd64 . But before putting something into bugzilla I'd like to tell you about another interesting detection I made now during testing: For 6 times in follow the system showed the following absolute constant behavior: After booting, the first Suspend-To-RAM allways worked very fine and the second Suspend-To-RAM allways constantly hung. And after the first Suspend-To-RAM there existed some additional processes in the process list that did not exist after booting: root 3105 2 0 11:40 ?00:00:00 [migration/1] root 3106 2 0 11:40 ?00:00:00 [ksoftirqd/1] root 3107 2 0 11:40 ?00:00:00 [watchdog/1] root 3108 2 0 11:40 ?00:00:00 [kconservative/1] root 3109 2 0 11:40 ?00:00:00 [radeon/1] root 3110 2 0 11:40 ?00:00:00 [ext4-dio-unwrit] root 3111 2 0 11:40 ?00:00:00 [ata/1] root 3112 2 0 11:40 ?00:00:00 [crypto/1] root 3113 2 0 11:40 ?00:00:00 [aio/1] root 3114 2 0 11:40 ?00:00:00 [kondemand/1] root 3115 2 0 11:40 ?00:00:00 [kblockd/1] root 3116 2 0 11:40 ?00:00:00 [kintegrityd/1] root 3117 2 0 11:40 ?00:00:00 [events/1] root 3119 500 0 11:40 ?00:00:00 udevd --daemon root 3120 500 0 11:40 ?00:00:00 udevd --daemon For me it now looks like one (or some) of them might cause the problem. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cd141a5.6040...@online.de
Bug#600846: Different additional processes sometimes
Sometimes there existed different additional processes like these after the first Suspend-To-RAM, but the result was the same: hanging second Suspend-To-RAM root 2932 2 0 11:33 ?00:00:00 [kworker/u:1] root 2933 2 0 11:33 ?00:00:00 [kworker/u:2] root 2934 2 0 11:33 ?00:00:00 [kworker/u:4] root 2935 2 0 11:33 ?00:00:00 [kworker/u:5] root 2936 2 0 11:33 ?00:00:00 [kworker/u:6] root 2937 2 0 11:33 ?00:00:00 [kworker/u:7] root 2938 2 0 11:33 ?00:00:00 [kworker/u:8] root 2939 2 0 11:33 ?00:00:00 [kworker/u:9] root 2940 2 0 11:33 ?00:00:00 [kworker/u:10] root 2941 2 0 11:33 ?00:00:00 [kworker/u:11] root 2942 2 0 11:33 ?00:00:00 [kworker/u:12] root 2943 2 0 11:33 ?00:00:00 [kworker/u:13] root 2946 2 0 11:33 ?00:00:00 [migration/1] root 2947 2 0 11:33 ?00:00:00 [kworker/1:3] root 2948 2 0 11:33 ?00:00:00 [ksoftirqd/1] root 2949 2 0 11:33 ?00:00:00 [watchdog/1] root 2950 2 0 11:33 ?00:00:00 [kworker/u:14] root 2951 2 0 11:33 ?00:00:00 [kworker/u:15] root 2952 2 0 11:33 ?00:00:00 [kworker/u:16] root 2953 2 0 11:33 ?00:00:00 [kworker/u:17] root 2954 2 0 11:33 ?00:00:00 [kworker/u:18] root 2955 2 0 11:33 ?00:00:00 [kworker/u:19] root 2956 2 0 11:33 ?00:00:00 [kworker/u:20] root 2957 2 0 11:33 ?00:00:00 [kworker/u:21] root 2958 2 0 11:33 ?00:00:00 [kworker/u:22] root 2959 2 0 11:33 ?00:00:00 [kworker/u:23] root 2960 2 0 11:33 ?00:00:00 [kworker/1:0] root 2961 2 0 11:33 ?00:00:00 [kworker/0:2] root 2962 2 0 11:33 ?00:00:00 [kworker/1:1] root 2963 2 0 11:33 ?00:00:00 [kworker/1:2] root 2965 495 0 11:33 ?00:00:00 udevd --daemon root 2966 495 0 11:33 ?00:00:00 udevd --daemon -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cd143c4.5020...@online.de
Bug#602273: [PATCH] Re: linux-image-2.6.32-5-686-bigmem: domU hangs during dom0 reboot, recovers when dom0 uptime caught up
package linux-image-2.6.32-5-686-bigmem
tags 602273 patch
thanks
The patch from
http://lists.xensource.com/archives/html/xen-devel/2010-10/msg01261.html
seems to help! Please consider applying this to debian.
For completeness, here's the patch from the email archive (probably
messes up whitespace though):
From: Jeremy Fitzhardinge jeremy.fitzhardi...@xx
Date: Mon, 25 Oct 2010 16:53:46 -0700
Subject: [PATCH] x86/pvclock: zero last_value on resume
If the guest domain has been suspend/resumed or migrated, then the
system clock backing the pvclock clocksource may revert to a smaller
value (ie, can be non-monotonic across the migration/save-restore).
Make sure we zero last_value in that case so that the domain
continues to see clock updates.
Signed-off-by: Jeremy Fitzhardinge jeremy.fitzhardi...@xx
diff --git a/arch/x86/include/asm/pvclock.h b/arch/x86/include/asm/pvclock.h
index cd02f32..6226870 100644
--- a/arch/x86/include/asm/pvclock.h
+++ b/arch/x86/include/asm/pvclock.h
@@ -11,5 +11,6 @@ unsigned long pvclock_tsc_khz(struct pvclock_vcpu_time_info
*src);
void pvclock_read_wallclock(struct pvclock_wall_clock *wall,
struct pvclock_vcpu_time_info *vcpu,
struct timespec *ts);
+void pvclock_resume(void);
#endif /* _ASM_X86_PVCLOCK_H */
diff --git a/arch/x86/kernel/pvclock.c b/arch/x86/kernel/pvclock.c
index 239427c..a4f07c1 100644
--- a/arch/x86/kernel/pvclock.c
+++ b/arch/x86/kernel/pvclock.c
@@ -120,6 +120,11 @@ unsigned long pvclock_tsc_khz(struct
pvclock_vcpu_time_info *src)
static atomic64_t last_value = ATOMIC64_INIT(0);
+void pvclock_resume(void)
+{
+ atomic64_set(last_value, 0);
+}
+
cycle_t pvclock_clocksource_read(struct pvclock_vcpu_time_info *src)
{
struct pvclock_shadow_time shadow;
diff --git a/arch/x86/xen/time.c b/arch/x86/xen/time.c
index b2bb5aa..5da5e53 100644
--- a/arch/x86/xen/time.c
+++ b/arch/x86/xen/time.c
@@ -426,6 +426,8 @@ void xen_timer_resume(void)
{
int cpu;
+ pvclock_resume();
+
if (xen_clockevent != xen_vcpuop_clockevent)
return;
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/84mxpq6480@sauna.l.org
Processed: [PATCH] Re: linux-image-2.6.32-5-686-bigmem: domU hangs during dom0 reboot, recovers when dom0 uptime caught up
Processing commands for cont...@bugs.debian.org: package linux-image-2.6.32-5-686-bigmem Limiting to bugs with field 'package' containing at least one of 'linux-image-2.6.32-5-686-bigmem' Limit currently set to 'package':'linux-image-2.6.32-5-686-bigmem' tags 602273 patch Bug #602273 [linux-image-2.6.32-5-686-bigmem] linux-image-2.6.32-5-686-bigmem: domU hangs during dom0 reboot, recovers when dom0 uptime caught up Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 602273: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602273 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.12887834125947.transcr...@bugs.debian.org
Bug#587905: Re : linux-image-2.6.32-5-openvz-amd64: Starting VZ container on ext4 panics with: BUG: unable to handle kernel NULL pointer dereference
Hi there, I can confirm that bug. Disk quotas are suppose to work with ext4 and openvz 2.6.32 kernels [0] but they oops if enabled. Has any progress been made by the openvz guys on this issue ? Thanks LeTic signature.asc Description: This is a digitally signed message part
Bug#602290: linux-image-kirkwood: Bad machid for Marvell RD-88F6281 Reference Board
Package: linux-image-kirkwood Version: 2.6.32-5 Severity: important The GuruPlug will hand in uboot. It seems there is a small typo in the last kernel : 692 must be 682. Error: unrecognized/unsupported machine ID (r1 = 0x0009). Available machine support: ID (hex)NAME 0690Marvell DB-88F6281-BP Development Board 0691Marvell RD-88F6192-NAS Development Board 0692Marvell RD-88F6281 Reference Board 0831Marvell SheevaPlug Reference Board 085bQNAP TS-119/TS-219 09c6QNAP TS-41x 0915Marvell OpenRD Base Board 0939Marvell OpenRD Client Board Please check your kernel config and/or bootloader. Thanks -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: armel (armv5tel) Kernel: Linux 2.6.32-trunk-kirkwood Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101103114108.1423.79678.report...@mozart.louche
Bug#602290: linux-image-kirkwood: Bad machid for Marvell RD-88F6281 Reference Board
* gand...@gk2.net gand...@gk2.net [2010-11-03 12:41]: The GuruPlug will hand in uboot. It seems there is a small typo in the last kernel : 692 must be 682. The correct ID for the GuruPlug is 2659. You have to a) configure u-boot on your GuruPlug to use 2659 and b) use a newer kernel. I suggest you start with http://lists.debian.org/debian-arm/2010/07/msg00197.html -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101103121805.gz26...@jirafa.cyrius.com
Bug#602290: linux-image-kirkwood: Bad machid for Marvell RD-88F6281 Reference Board
gandalf, see below for my response. Also, you used an invalid email address (gandal_d_@) to submit your bug. * Martin Michlmayr t...@cyrius.com [2010-11-03 12:18]: * gand...@gk2.net gand...@gk2.net [2010-11-03 12:41]: The GuruPlug will hand in uboot. It seems there is a small typo in the last kernel : 692 must be 682. The correct ID for the GuruPlug is 2659. You have to a) configure u-boot on your GuruPlug to use 2659 and b) use a newer kernel. I suggest you start with http://lists.debian.org/debian-arm/2010/07/msg00197.html -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101103121805.gz26...@jirafa.cyrius.com -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101103123818.gb10...@jirafa.cyrius.com
Bug#602290: marked as done (linux-image-kirkwood: Bad machid for Marvell RD-88F6281 Reference Board)
Your message dated Wed, 3 Nov 2010 12:37:28 + with message-id 20101103123728.ga10...@jirafa.cyrius.com and subject line Re: Bug#602290: linux-image-kirkwood: Bad machid for Marvell RD-88F6281 Reference Board has caused the Debian Bug report #602290, regarding linux-image-kirkwood: Bad machid for Marvell RD-88F6281 Reference Board to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 602290: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-kirkwood Version: 2.6.32-5 Severity: important The GuruPlug will hand in uboot. It seems there is a small typo in the last kernel : 692 must be 682. Error: unrecognized/unsupported machine ID (r1 = 0x0009). Available machine support: ID (hex)NAME 0690Marvell DB-88F6281-BP Development Board 0691Marvell RD-88F6192-NAS Development Board 0692Marvell RD-88F6281 Reference Board 0831Marvell SheevaPlug Reference Board 085bQNAP TS-119/TS-219 09c6QNAP TS-41x 0915Marvell OpenRD Base Board 0939Marvell OpenRD Client Board Please check your kernel config and/or bootloader. Thanks -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: armel (armv5tel) Kernel: Linux 2.6.32-trunk-kirkwood Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- I got this response: gand...@gk2.net: host stargate.gk2.net[88.171.131.190] said: 550 5.1.1 gand...@gk2.net: Recipient address rejected: User unknown in virtual mailbox table (in reply to RCPT TO command) -- Martin Michlmayr http://www.cyrius.com/ ---End Message---
Bug#561241: linux-2.6: control the backlight on a number of Samsung laptops
The samsung-laptop staging driver is now in the Debian 2.6.32 source. However, it seems only to include a couple of models. Can this driver be patched to include all models, so that it works in the same way as the related http://code.google.com/p/easy-slow-down-manager/ ? Cheers John -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cd15c38.60...@dpets.co.uk
Re: updated text
On Tue, Nov 02, 2010 at 08:10:09PM -0400, Ben Hutchings wrote: On Tue, 2010-11-02 at 21:35 +0100, Mario Kleinsasser wrote: Hello Dann, I've got your message from the list and would like to ask you what this mean? We are massively using OpenVZ for our containers and this is the base of our weberver farm. The lxc Linux Containers project (http://lxc.sourceforge.net) sounds similar as OpenVZ. Are the kernel patches based upon the work of OpenVZ from Kir Kolyshkin? My colleague and I know Kir Kolyshkin (OpenVZ) since some years and we are in contact from time to time with him. I believe that many of the OpenVZ developers have also been working on Linux Containers. Yes, my understanding is that they are working to redesign pieces to get them excepted upstream, and then altering the OpenVZ patches to make use of the upstreamed code. (This is based upon a talk by Kir at the LF Collaboration Summit in April). I hope to see a mature/upstream LXC implementation for wheezy to which we can migrate OpenVZ/Linux Vserver users. I gather that it isn't currently a problem for us because squeeze will have an OpenVZ kernel image but its good to know whats coming next because we then have to productive migrate a lot of instances. Does anyone know whats the currently status of OpenVZ integration in Debian 6.0 and later is? Whats the plan or vision? [...] It is still supported in Debian 6.0, and the OpenVZ developers are actively maintaining a branch based on Linux 2.6.32 which we are taking fixes from. I'd add that, in my experience, the OpenVZ developers have been very good at working with Debian and our users - this isn't a rebuke of their work, but is part of an effort to reduce the overhead of maintaining several flavors, and to target upstreamed solutions. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101103163857.gf24...@dannf.org
Bug#600846: Definitely: The problem started with kernel 2.6.32
I downloaded three versions of the 2.6.30 kernel from snapshot.debian.org and installed them on my notebook - without doing any other changes to the system. And the Suspend-To-RAM of all of the three 2.6.30 kernels worked perfectly well ! So from my point of view the problem started definitely with the 2.6.32 kernel version. The 2.6.30 kernel packages were: linux-image-2.6.30-1-amd64_2.6.30-1_amd64.deb linux-image-2.6.30-2-amd64_2.6.30-7_amd64.deb linux-image-2.6.30-2-amd64_2.6.30-8squeeze1_amd64.deb (the latest I found) With the 2.6.30 kernel there is the same effect of additional processes coming up after the first Suspend-To-RAM . These are: root 3092 2 0 20:22 ?00:00:00 [migration/1] root 3093 2 0 20:22 ?00:00:00 [ksoftirqd/1] root 3094 2 0 20:22 ?00:00:00 [watchdog/1] root 3095 2 0 20:22 ?00:00:00 [kconservative/1] root 3096 2 0 20:22 ?00:00:00 [ata/1] root 3097 2 0 20:22 ?00:00:00 [crypto/1] root 3098 2 0 20:22 ?00:00:00 [aio/1] root 3099 2 0 20:22 ?00:00:00 [kondemand/1] root 3100 2 0 20:22 ?00:00:00 [kblockd/1] root 3101 2 0 20:22 ?00:00:00 [kintegrityd/1] root 3102 2 0 20:22 ?00:00:00 [events/1] root 3103 718 0 20:22 ?00:00:00 udevd --daemon root 3104 718 0 20:22 ?00:00:00 udevd --daemon As can be seen the 2 processes root 3109 2 0 11:40 ?00:00:00 [radeon/1] root 3110 2 0 11:40 ?00:00:00 [ext4-dio-unwrit] coming up in kernel 2.6.32 are missing. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cd1bb02.7030...@online.de
Bug#600846: Definitely: The problem started with kernel 2.6.32
please let upstream know the 2.6.36 trouble, so that they can work on it. On Wed, Nov 03, 2010 at 08:41:54PM +0100, hu...@online.de wrote: I downloaded three versions of the 2.6.30 kernel from snapshot.debian.org and installed them on my notebook - without doing any other changes to the system. And the Suspend-To-RAM of all of the three 2.6.30 kernels worked perfectly well ! so other datapoints would be 2.6.31-* and the first 2.6.32-[1-4]-amd64 linux packages. thanks. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101103213937.gk15...@vostochny.stro.at
Bug#592943: Confirmed in linux-image-2.6.36-rc6
I just tried linux-image-2.6.36-rc6 from experimental. The problem is still there. A pity -- no wireless without an external device. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/35025.85.178.68.56.1288822684.webm...@portal.zedat.fu-berlin.de
Re: [PATCH] kbuild, deb-pkg: fix Architecture field when cross compiling
On 11/03/2010 10:57 PM, Michal Marek wrote: I know very little about debian packaging, but shouldn't this be done in all cases, regardless of CROSS_COMPILE being set or not? You even show in the above example that in some cases you don't need CROSS_COMPILE to build a kernel for a different architecture. I had a problem earlier with Kbuild ignoring ARCH if CROSS_COMPILE wasn't set, but can't reproduce with the current kernel, but I also started out with upgrading it from .26, since squeezes .32 doesn't work on Soekris net4501. So this is no longer an issue. The other reason for make it dependent on CROSS_COMPILE at least to begin with is that the ARCH - debarch translation table doesn't have to be as complete since it doesn't break anything in the currently working non-cross compile senario. If this doesn't matter then I will send a new patch, that doesn't depend on CROSS_COMPILE being set. I have CC'ed the debian-kernel list, for people not on LKML: https://patchwork.kernel.org/patch/296182/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cd20f85.7040...@asbjorn.biz
[PATCH] kbuild, deb-pkg: fix Architecture field when cross compiling
Attempt to guess the correct value of the Architecture control
field, based on the ARCH environment variable. Fallback to letting
deb-gencontrol use the host platform's architecture.
With this patch the following make command:
make ARCH=i386 deb-pkg
will output an i386 Debian package instead of an amd64 one,
when run on amd64 machine.
Signed-off-by: Asbjoern Sloth Toennesen asbj...@asbjorn.biz
---
scripts/package/builddeb | 18 +-
1 files changed, 17 insertions(+), 1 deletions(-)
diff --git a/scripts/package/builddeb b/scripts/package/builddeb
index 5f1e2fc..02fd63f 100644
--- a/scripts/package/builddeb
+++ b/scripts/package/builddeb
@@ -25,8 +25,24 @@ create_package() {
chown -R root:root $pdir
chmod -R go-w $pdir
+ # Attempt to find correct debian architecture
+ local forcearch= debarch=
+ case $ARCH in
+ x86_64) debarch=amd64 ;;
+ i386|ia64) debarch=$ARCH ;;
+ *)
+ case $SUBARCH in
+ arm) debarch=$(grep -q CONFIG_AEABI=y .config \
+echo armel || echo arm) ;;
+ esac
+ ;;
+ esac
+ if [ -n $debarch ] ; then
+ forcearch=-DArchitecture=$debarch
+ fi
+
# Create the package
- dpkg-gencontrol -isp -p$pname -P$pdir
+ dpkg-gencontrol -isp $forcearch -p$pname -P$pdir
dpkg --build $pdir ..
}
--
1.7.2.3
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/1288838560-6173-1-git-send-email-asbj...@asbjorn.biz
Re: [PATCH] kbuild, deb-pkg: fix Architecture field when cross compiling
On 11/04/2010 02:42 AM, Asbjoern Sloth Toennesen wrote: + case $SUBARCH in + arm) debarch=$(grep -q CONFIG_AEABI=y .config \ + echo armel || echo arm) ;; + esac Hmm, didn't test the ARM part of that patch properly SUBARCH isn't available to builddeb. Will reply to this mail with fixed patch. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cd22acf.1000...@asbjorn.it
[PATCH] kbuild, deb-pkg: fix Architecture field when cross compiling
Attempt to guess the correct value of the Architecture control
field, based on the ARCH environment variable. Fallback to letting
deb-gencontrol use the host platform's architecture.
With this patch the following make command:
make ARCH=i386 deb-pkg
will output an i386 Debian package instead of an amd64 one,
when run on amd64 machine.
Signed-off-by: Asbjoern Sloth Toennesen asbj...@asbjorn.biz
---
scripts/package/builddeb | 17 -
1 files changed, 16 insertions(+), 1 deletions(-)
diff --git a/scripts/package/builddeb b/scripts/package/builddeb
index 5f1e2fc..43b8826 100644
--- a/scripts/package/builddeb
+++ b/scripts/package/builddeb
@@ -25,8 +25,23 @@ create_package() {
chown -R root:root $pdir
chmod -R go-w $pdir
+ # Attempt to find the correct Debian architecture
+ local forcearch= debarch=
+ case $ARCH in
+ i386|ia64)
+ debarch=$ARCH ;;
+ x86_64)
+ debarch=amd64 ;;
+ *)
+ grep -q CONFIG_ARM=y .config
+ debarch=arm$(grep -q CONFIG_AEABI=y .config echo el)
+ esac
+ if [ -n $debarch ] ; then
+ forcearch=-DArchitecture=$debarch
+ fi
+
# Create the package
- dpkg-gencontrol -isp -p$pname -P$pdir
+ dpkg-gencontrol -isp $forcearch -p$pname -P$pdir
dpkg --build $pdir ..
}
--
1.7.2.3
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/1288842244-6863-1-git-send-email-asbj...@asbjorn.biz
