Re: system hangs during shutdown...
On Thu, Jul 21, 2011 at 04:20:34PM -0600, Bruce Sass wrote: On July 21, 2011 05:02:38 AM Ben Hutchings wrote: [...] This is not a bug. NFS clients are supposed to keep on trying to reach the server, by default. You should have unmounted the directory from the NFS client(s) before shutting down the server. Sounds like a desirable behaviour when the system is coming up, but having the client hang when *going down* because a server disappeared doesn't seem right. The client is still the client with the expected behaviour when it is going down. You should have unmounted the directory from the NFS client(s) before shutting down the server. Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. -- 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/20110722062608.gf2...@gpm.stappers.nl
Re: [PATCH] Add 3.0-rc7-rt0 patch set
Hello, On Thu, Jul 21, 2011 at 11:32:52PM +0200, Ben Hutchings wrote: On Thu, 2011-07-21 at 16:25 +0200, Uwe Kleine-König wrote: # initramfs-generators initramfs-fallback: linux-initramfs-tool initramfs-tools: initramfs-tools (= 0.99) diff --git a/config/featureset-rt/config b/config/featureset-rt/config new file mode 100644 index 000..8136f16 --- /dev/null +++ b/config/featureset-rt/config @@ -0,0 +1,5 @@ +# CONFIG_PREEMPT_VOLUNTARY is not set +CONFIG_PREEMPT_RT_FULL=y +CONFIG_SCHED_TRACER=y +CONFIG_MISSED_TIMER_OFFSETS_HIST=y +CONFIG_WAKEUP_LATENCY_HIST=y I notice that you leave Xen (and other pvops) support enabled. I don't think this makes sense, as virtualisation will add back the latency and jitter that RT is trying to avoid. hmm, it might not make much sense to run Xen on top of an rt kernel, that's right. I'm not sure that disabling Xen (and others) is needed though. There is no exact definition of rt in general, it always depends on your use-case and then you have to verify/test if the machine you want to use is capable to fulfill your requirements. So IMHO it's OK to say: my machine is able to serve my rt requirements as long as it doesn't run (as) a Xen guest. Don't do it then. Or only do it when you're not recording audio. I'm sure there are many things more that increase the maximal latency, I don't want (and cannot) go through all of them and choose if they are still OK or crossed the border. I could still be conviced to disable these, but I don't find how to get rid of the This kernel also runs on a Xen hypervisor. It supports both privileged (dom0) and unprivileged (domU) operation. in the description. Hints welcome. diff --git a/config/featureset-rt/defines b/config/featureset-rt/defines new file mode 100644 index 000..caf2baf --- /dev/null +++ b/config/featureset-rt/defines @@ -0,0 +1,7 @@ +[abi] +ignore-changes: * + +[description] +part-long-rt: This kernel includes the PREEMPT_RT patch set This should be a whole sentence, ending in a full stop (period). I guess just adding a period is good enough? Thanks for your feedback Uwe -- Pengutronix e.K. | Uwe Kleine-König| Industrial Linux Solutions | http://www.pengutronix.de/ | -- 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/20110722094244.ge16...@pengutronix.de
Bug#631945: HFSC warning issue
After bisecting 2.6.39.1 it turned out that the bug is caused independently by two patches: commit b262a5da755cc6ed0cb4fba230cd9bf4037e1096 sch_sfq: fix peek() implementation and commit 9df49f2bfe862573911a080c75a6d81113c5c81d sch_sfq: avoid giving spurious NET_XMIT_CN signals Reverting these patches makes HFSC work again. From: 00bor...@gmail.com I had the same problem when I upgraded to 2.6.38 vanilla (and currently at 2.6.39.1), but I can't remember what the last successful version was (probably greater than 2.6.32). My syslog was full of the WARN_ON trace from sch_hfsc.c:1427. Did you tested 2.6.38 or 2.6.38.8? Because mentioned patches was included in 2.6.38.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/40cb21d3.13a4e2d8.4e2949de.1e...@o2.pl
Re: [PATCH] Add 3.0-rc7-rt0 patch set
On Fri, 2011-07-22 at 11:42 +0200, Uwe Kleine-König wrote: Hello, On Thu, Jul 21, 2011 at 11:32:52PM +0200, Ben Hutchings wrote: On Thu, 2011-07-21 at 16:25 +0200, Uwe Kleine-König wrote: # initramfs-generators initramfs-fallback: linux-initramfs-tool initramfs-tools: initramfs-tools (= 0.99) diff --git a/config/featureset-rt/config b/config/featureset-rt/config new file mode 100644 index 000..8136f16 --- /dev/null +++ b/config/featureset-rt/config @@ -0,0 +1,5 @@ +# CONFIG_PREEMPT_VOLUNTARY is not set +CONFIG_PREEMPT_RT_FULL=y +CONFIG_SCHED_TRACER=y +CONFIG_MISSED_TIMER_OFFSETS_HIST=y +CONFIG_WAKEUP_LATENCY_HIST=y I notice that you leave Xen (and other pvops) support enabled. I don't think this makes sense, as virtualisation will add back the latency and jitter that RT is trying to avoid. hmm, it might not make much sense to run Xen on top of an rt kernel, that's right. I'm not sure that disabling Xen (and others) is needed though. There is no exact definition of rt in general, it always depends on your use-case and then you have to verify/test if the machine you want to use is capable to fulfill your requirements. So IMHO it's OK to say: my machine is able to serve my rt requirements as long as it doesn't run (as) a Xen guest. Don't do it then. Or only do it when you're not recording audio. I'm sure there are many things more that increase the maximal latency, I don't want (and cannot) go through all of them and choose if they are still OK or crossed the border. True. I could still be conviced to disable these, but I don't find how to get rid of the This kernel also runs on a Xen hypervisor. It supports both privileged (dom0) and unprivileged (domU) operation. in the description. Hints welcome. I think you would need to add a 'amd64_description' section in debian/config/amd64/rt/defines, overriding the one in debian/config/amd64/defines. Not sure. diff --git a/config/featureset-rt/defines b/config/featureset-rt/defines new file mode 100644 index 000..caf2baf --- /dev/null +++ b/config/featureset-rt/defines @@ -0,0 +1,7 @@ +[abi] +ignore-changes: * + +[description] +part-long-rt: This kernel includes the PREEMPT_RT patch set This should be a whole sentence, ending in a full stop (period). I guess just adding a period is good enough? Yes. Ben. -- Ben Hutchings Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer signature.asc Description: This is a digitally signed message part
Bug#634181: linux-image-2.6.39-2-amd64: br_netfilter nat pagefault
On Fri, 2011-07-22 at 05:24 +0200, Christian Franke wrote: On Sun, 17 Jul 2011 17:51:14 +0200, Christian Franke wrote: This fault now also occured with version 2.6.39-3 of the linux-image-2.6.39-2-amd64 package. On Fri, 22 Jul 2011 01:19:33 +0200, Ben Hutchings wrote: I think this bug was fixed in 2.6.39-3 along with bug #629932. Let us know if it occurs again. As I see it (upper quote), this bug also occurs in the 2.6.39-3 version. Sorry, I missed your second message. I'll reopen. It do however lack understanding of the package naming and versioning here - the package has the name linux-image-2.6.39-2-amd64, however its version is 2.6.39-3, an aptitude update search also does not show a package with name 2.6.39-3 here. See http://kernel-handbook.alioth.debian.org/ch-versions.html. Ben. Attached, there is a dump of the complete kernel log on 2.6.39-3, I hope this makes it into the bugtracker. :/ -- Ben Hutchings Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer signature.asc Description: This is a digitally signed message part
Processed: found 634181 in 2.6.39-3
Processing commands for cont...@bugs.debian.org:
found 634181 2.6.39-3
Bug #634181 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-2.6.39-2-amd64: br_netfilter nat pagefault
There is no source info for the package 'linux-2.6' at version '2.6.39-3' with
architecture ''
Unable to make a source version for version '2.6.39-3'
Bug Marked as found in versions 2.6.39-3; no longer marked as fixed in versions
2.6.39-3 and reopened.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
634181: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634181
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.131133189031171.transcr...@bugs.debian.org
Problem with slip connections after kernel upgrade on squeeze
I had a debian squeeze with 3 slips connection, sl0, sl1 and sl2 on working VPND solution. Its using the kernel version linux-image-2.6.32-5-amd64_2.6.32-31_amd64 so I upgrade it to linux-image-2.6.32-5-amd64_2.6.32-35_amd64 and the slip interface dont fork to sl1 any more! example: When I start the first connection its works well with sl0 interface so when i start second and third connections its bind interface sl0 too chasing the first one! they dont fork to sl1 and sl2 any more! Maybe this is a BUG on this patch? When I found this problem I stop to upgrade my others squeeze solution using VPND with slip interface! Sorry about my english tks for any help Cesar -- 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/1311334233.1882.35.camel@seronni
Bug#633942: linux-image-2.6.39-2-amd64: occasional freeze after resume
On 2011-07-15 11:23:29 +0200, Vincent Lefevre wrote: Package: linux-2.6 Version: 2.6.39-3 Severity: important My laptop (DELL Latitude E6400) sometimes freezes after resume: I can hear the fan, but the screen remains off and I cannot suspend the laptop again (with Fn+F1). This happened twice in the last 24 hours. I had to switch it off without a clean shutdown. This seems to be specific to 2.6.39. I reverted to: Linux xvii 2.6.38-2-amd64 #1 SMP Sun May 8 13:51:57 UTC 2011 x86_64 GNU/Linux (linux-image-2.6.38-2-amd64 2.6.38-5), and did many suspend/resume for several days, and I didn't have a single freeze. -- Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon) -- 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/20110722133223.ga22...@prunille.vinc17.org
Re: Symbolic links to kernel image files and initial RAM file system image files
On Wed, Jul 20, 2011 at 01:56, Stephen Powell zlinux...@wowway.com wrote: ... o Eliminate symbolic links entirely and require boot loader hook scripts to edit their configuration files ... This seems to be the best alternative for me however IIRC there still arches that depends on those links so I think we could do it case by base (arch specificly) by now. -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- 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/CAP9ODKodxB0xNO=U+vzn3-rPXND_kQSU+s2FT=rEf=j7yna...@mail.gmail.com
Bug#631945: HFSC warning issue
On Fri, Jul 22, 2011 at 2:58 AM, Michal Pokrywka wolfm...@o2.pl wrote: I had the same problem when I upgraded to 2.6.38 vanilla (and currently at 2.6.39.1), but I can't remember what the last successful version was (probably greater than 2.6.32). My syslog was full of the WARN_ON trace from sch_hfsc.c:1427. Did you tested 2.6.38 or 2.6.38.8? Because mentioned patches was included in 2.6.38.8. Sorry, I don't remember for sure. I am only 100% sure that I currently have the issue on 2.6.39.1; anything else I may have remembered incorrectly. -- 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/CAAJ8s-QSoQFhd44KpCoY3wPNkPVh=3QzUM9B-Jbz-grF=v8...@mail.gmail.com
Bug#632734: Strange
On 21/07/11 08:10 PM, Ben Hutchings wrote: Please always cc the bug address when replying to bug-related mails. On Sat, 2011-07-16 at 09:54 -0400, Frank McCormick wrote: On 11/07/11 12:12 AM, Ben Hutchings wrote: On Tue, 2011-07-05 at 17:29 -0400, Frank wrote: On 05/07/11 04:23 PM, Ben Hutchings wrote: On Tue, Jul 05, 2011 at 02:48:26PM -0400, Frank M wrote: I find it strange that the PAE kernel is the ONLY one which gives me any trouble. I guess it could be hardware related, but 2.6.38-1 and 2.6.38-2 have both been booting fine for months. Is there something about the PAE series that would uncover hardware faults which may have existed for a long time ? Have you tried booting those earlier versions recently? Yes I've been booting them everyday for the past month or so - the PAE series is the first time in years, literally, that I have had problems like this. We have provided kernel packages using PAE for a long time, previously labelled as '686-bigmem'. You can test linux-image-2.6.38-2-686-bigmem to check whether this bug is related to use of PAE. However, I think it is probably due to a change between Linux 2.6.38 and 2.6.39. Well I **think** the bigmem kernel now is actually the PAE kernel. I installed the bigmem kernel and it turned out to be the troublesome PAE version. Right. It has been renamed because it is now the only '686' flavour, but has different hardware requirements from the old '686' flavour. I believe the processor in your computer should support this, but could you confirm what model you have (look at the file /proc/cpuinfo)? processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 2 model name : Intel(R) Pentium(R) 4 CPU 2.60GHz stepping : 9 cpu MHz: 2593.138 cache size : 512 KB physical id: 0 siblings : 2 core id: 0 cpu cores : 1 apicid : 0 initial apicid : 0 fdiv_bug : no hlt_bug: no f00f_bug : no coma_bug : no fpu: yes fpu_exception : yes cpuid level: 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe pebs bts cid xtpr bogomips : 5186.27 clflush size : 64 cache_alignment: 128 address sizes : 36 bits physical, 32 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 15 model : 2 model name : Intel(R) Pentium(R) 4 CPU 2.60GHz stepping : 9 cpu MHz: 2593.138 cache size : 512 KB physical id: 0 siblings : 2 core id: 0 cpu cores : 1 apicid : 1 initial apicid : 1 fdiv_bug : no hlt_bug: no f00f_bug : no coma_bug : no fpu: yes fpu_exception : yes cpuid level: 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe pebs bts cid xtpr bogomips : 5187.60 clflush size : 64 cache_alignment: 128 address sizes : 36 bits physical, 32 bits virtual power management: That's it...it alledgedly supports PAE This sounds like there is some sort of hardware fault, but I can't see why it would only occur when using PAE. It is just possible that the circuitry for PAE is faulty, but I think that is only a very small part of the chip. Please do consider the suggestions inhttp://www.bitwizard.nl/sig11/. Will do. -- Cheers Frank -- 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/4e29bba9.8070...@videotron.ca
Re: Problem with slip connections after kernel upgrade on squeeze
On Fri, 2011-07-22 at 08:30 -0300, SUPORTE - Kernel Informática wrote: I had a debian squeeze with 3 slips connection, sl0, sl1 and sl2 on working VPND solution. Its using the kernel version linux-image-2.6.32-5-amd64_2.6.32-31_amd64 so I upgrade it to linux-image-2.6.32-5-amd64_2.6.32-35_amd64 and the slip interface dont fork to sl1 any more! example: When I start the first connection its works well with sl0 interface so when i start second and third connections its bind interface sl0 too chasing the first one! they dont fork to sl1 and sl2 any more! Maybe this is a BUG on this patch? When I found this problem I stop to upgrade my others squeeze solution using VPND with slip interface! vpnd (source: http://vpnd.linuxsys.com/archive/vpnd-1.1.4.tar.gz) expects to get the SLIP unit number when setting SLIP line discipline: /* set line discipline to SLIP, react to errors */ #ifdef LINUX i=N_SLIP; if((anchor-proxy=ioctl(anchor-tty,TIOCSETD,i))0) JUMP(ioctl(TIOCSETD),err3); #elif defined(FreeBSD) || defined(OSNetBSD) || defined(OSOpenBSD) ... /* create interface name */ memset(ifr,0,sizeof(ifr)); sprintf(ifr.ifr_name,sl%u,anchor-proxy); But in commit 057bef938896e6266ae24ec4266d24792d27c29a the behaviour of slip_open() and hence ioctl TIOCSETD was changed so that the unit number is no longer returned. It looks like applications are supposed to use the ioctl SIOCGIFNAME to find the net device name. But clearly the driver was previously returning the unit number and applications did depend on this. So I think this change has to be reverted and the TTY layer will have to accept positive return values from ldisc open(). Ben. -- Ben Hutchings Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer signature.asc Description: This is a digitally signed message part
Re: Problem with slip connections after kernel upgrade on squeeze
On Fri, 2011-07-22 at 08:30 -0300, SUPORTE - Kernel Informática wrote: I had a debian squeeze with 3 slips connection, sl0, sl1 and sl2 on working VPND solution. Its using the kernel version linux-image-2.6.32-5-amd64_2.6.32-31_amd64 so I upgrade it to linux-image-2.6.32-5-amd64_2.6.32-35_amd64 and the slip interface dont fork to sl1 any more! example: When I start the first connection its works well with sl0 interface so when i start second and third connections its bind interface sl0 too chasing the first one! they dont fork to sl1 and sl2 any more! Maybe this is a BUG on this patch? When I found this problem I stop to upgrade my others squeeze solution using VPND with slip interface! vpnd (source: http://vpnd.linuxsys.com/archive/vpnd-1.1.4.tar.gz) expects to get the SLIP unit number when setting SLIP line discipline: /* set line discipline to SLIP, react to errors */ #ifdef LINUX i=N_SLIP; if((anchor-proxy=ioctl(anchor-tty,TIOCSETD,i))0) JUMP(ioctl(TIOCSETD),err3); #elif defined(FreeBSD) || defined(OSNetBSD) || defined(OSOpenBSD) ... /* create interface name */ memset(ifr,0,sizeof(ifr)); sprintf(ifr.ifr_name,sl%u,anchor-proxy); But in commit 057bef938896e6266ae24ec4266d24792d27c29a the behaviour of slip_open() and hence ioctl TIOCSETD was changed so that the unit number is no longer returned. It looks like applications are supposed to use the ioctl SIOCGIFNAME to find the net device name. But clearly the driver was previously returning the unit number and applications did depend on this. So I think this change has to be reverted and the TTY layer will have to accept positive return values from ldisc open(). Ben. -- Ben Hutchings Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer signature.asc Description: Digital signature
Re: squeeze 2.6.32-5-686 doesn´t boot without monitor
Hello Ben, xserver-xorg-video-intel (2:2.13.0-6) is installed on my system. I removed /etc/modprobe.d/i915-kms.conf, but as you already suspected, that didn´t change a bit - the system freezes at the same point if no monitor is attached. Michael - Ursprüngliche Message - This is probably related to configuring video output in the kernel video drivers (KMS) instead of in X video drivers. KMS is disabled by default in the 'squeeze' kernel versions, for compatibility with older versions of the X video drivers. The new version of the X video driver (xserver-xorg-video-intel) works with KMS and installs a configuration file that enables it. You can try disabling it by removing the file /etc/modprobe.d/i915-kms.conf, but I don't think the X video driver will work. Which version of xserver-xorg-video-intel did you install? -- 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/1311362179.54165.yahoomail...@web24615.mail.ird.yahoo.com
[PATCH v2] Add 3.0-rc7-rt0 patch set
Hello, changes since the first submission: - updated patches with some fixes by Thomas Gleixer (you don't see that though, as I skipped the patches again) - add a simple gen-patch script - drop arm/versatile, so it's only amd64/amd64 for now - fix some more things noted by Ben Best regards Uwe -8- It's currently enabled and build tested for amd64/amd64. The rt patches applied as provided by Thomas Gleixner with just one exception: linux-3.0-rc7.patch. That contains the diff of Linus Torvald's tree at the time of the rt release since the v3.0-rc7 tag. Two changes were already in the debian tree, namely bugfix/arm/ixp4xx-build-breakage.patch bugfix/mips/mips-i8259-use-struct-syscore_ops-instead-of-sysdevs.patch The patches also include a first set of fixups posted by Thomas. --- changelog |3 + config/amd64/defines |2 + config/amd64/rt/defines|3 + config/armel/rt/defines|3 + config/defines |4 + config/featureset-rt/config|5 + config/featureset-rt/defines |7 + .../features/all/rt/acpi-convert-c3lock-raw.patch | 54 + .../features/all/rt/acpi-use-local-irq-nort.patch | 27 + .../all/rt/arch-use-pagefault-disabled.patch | 332 ++ .../features/all/rt/arm-allow-irq-threading.patch | 21 + ...t-remove-irq-handler-when-clock-is-unused.patch | 67 + ...-at91-tclib-default-to-tclib-timer-for-rt.patch | 34 + .../all/rt/arm-disable-highmem-on-rt.patch | 22 + .../rt/arm-enable-interrupts-in-signal-code.patch | 23 + .../all/rt/arm-mark-pmu-interupt-no-thread.patch | 24 + .../features/all/rt/arm-raw_lock-conversions.patch | 786 .../all/rt/ata-disable-interrupts-if-non-rt.patch | 66 + .../block-shorten-interrupt-disabled-regions.patch | 120 + .../all/rt/bug-rt-dependend-variants.patch | 45 + ...clocksource-tclib-allow-higher-clockrates.patch | 163 + .../all/rt/cond-resched-lock-rt-tweak.patch| 22 + .../features/all/rt/cond-resched-softirq-rt.patch | 51 + .../features/all/rt/console-make-rt-friendly.patch | 84 + patches/features/all/rt/cpu-rt-variants.patch | 28 + patches/features/all/rt/debugobjects-rt.patch | 36 + .../features/all/rt/dmar-make-qi-lock-raw.patch| 70 + .../all/rt/dmar-make-register-lock-raw.patch | 387 ++ .../all/rt/dmar-mark-dmar-irq-no-thread.patch | 22 + .../rt/drivers-dca-convert-dcalock-to-raw.patch| 239 ++ .../all/rt/drivers-floppy-use-timer-del-sync.patch | 70 + .../all/rt/drivers-ide-fix-irq-flags-madness.patch | 27 + .../rt/drivers-net-8139-disable-irq-nosync.patch | 31 + ...ers-net-at91-make-mdio-protection-rt-safe.patch | 54 + .../drivers-net-ehea-mark-rx-irq-no-thread.patch | 53 + .../all/rt/drivers-net-fix-livelock-issues.patch | 141 + .../all/rt/drivers-net-gianfar-make-rt-aware.patch | 57 + ...drivers-net-tulip-add-missing-pci-disable.patch | 25 + .../rt/drivers-net-vortex-fix-locking-issues.patch | 50 + ...ers-random-reduce-preempt-disabled-region.patch | 40 + ...ial-call-flush_to_ldisc-when-the-irq-is-t.patch | 49 + .../rt/drivers-serial-cleanup-locking-for-rt.patch | 44 + .../features/all/rt/drm-more-moronic-crap.patch| 32 + patches/features/all/rt/drm-sigh.patch | 32 + .../features/all/rt/epoll-use-get-cpu-light.patch | 28 + patches/features/all/rt/filemap-fix-up.patch | 22 + patches/features/all/rt/fixups.patch | 111 + .../all/rt/fs-add-missing-rcu-protection.patch | 42 + patches/features/all/rt/fs-block-rt-support.patch | 44 + ...s-btrfs-locking-workaround-for-preempt-rt.patch | 37 + .../all/rt/fs-convert-i-alloc-sem-to-rw-anon.patch | 270 ++ .../all/rt/fs-jbd-replace-bh_state-lock.patch | 102 + .../all/rt/fs-namespace-preemption-fix.patch | 45 + .../all/rt/fs-ntfs-disable-interrupt-non-rt.patch | 69 + .../rt/fs-replace-bh_uptodate_lock-for-rt.patch| 167 + patches/features/all/rt/ftrace-hash-fix.patch | 126 + .../all/rt/ftrace-migrate-disable-tracing.patch| 81 + patches/features/all/rt/gen-patch |9 + .../all/rt/generic-cmpxchg-use-raw-local-irq.patch | 49 + .../all/rt/genirq-disable-irqpoll-on-rt.patch | 41 + .../genirq-disable-random-call-on-preempt-rt.patch | 29 + .../features/all/rt/genirq-force-threading.patch | 50 + patches/features/all/rt/genirq-nodebug-shirq.patch | 22 + .../rt/highmem-explicitly-disable-preemption.patch | 319 ++ .../all/rt/hotplug-light-get-online-cpus.patch | 213 + .../all/rt/hotplug-use-migrate-disable.patch | 38 + ...up-hrtimer-callback-changes-for-preempt-r.patch | 415 ++
Re: squeeze 2.6.32-5-686 doesn´t boot without monitor
Hello Ben, After my last post I had a look at i814-kms,conf - after changing it to options i915 modeset=0 the system booted without attached monitor. Thanks you very much Michael - Ursprüngliche Message - Von: Michael postbote2009-deb...@yahoo.com An: Ben Hutchings b...@decadent.org.uk Cc: Debian kernel maintainers debian-kernel@lists.debian.org Gesendet: 21:16 Freitag, 22.Juli 2011 Betreff: Re: squeeze 2.6.32-5-686 doesn´t boot without monitor Hello Ben, xserver-xorg-video-intel (2:2.13.0-6) is installed on my system. I removed /etc/modprobe.d/i915-kms.conf, but as you already suspected, that didn´t change a bit - the system freezes at the same point if no monitor is attached. Michael - Ursprüngliche Message - This is probably related to configuring video output in the kernel video drivers (KMS) instead of in X video drivers. KMS is disabled by default in the 'squeeze' kernel versions, for compatibility with older versions of the X video drivers. The new version of the X video driver (xserver-xorg-video-intel) works with KMS and installs a configuration file that enables it. You can try disabling it by removing the file /etc/modprobe.d/i915-kms.conf, but I don't think the X video driver will work. Which version of xserver-xorg-video-intel did you install? -- 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/1311362179.54165.yahoomail...@web24615.mail.ird.yahoo.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/1311363591.15762.yahoomail...@web24605.mail.ird.yahoo.com
Re: [PATCH v2] Add 3.0-rc7-rt0 patch set
On Fri, Jul 22, 2011 at 09:37:26PM +0200, Uwe Kleine-König wrote: --- /dev/null +++ b/config/armel/rt/defines I thought this was dropped. +[description] +part-long-rt: This kernel includes the PREEMPT_RT patch set. +part-short-rt: PREEMPT_RT This does not tell the user why he wants this. ++ features/all/rt/linus-3.0-rc7.patch featureset=rt ++ features/all/rt/ftrace-hash-fix.patch featureset=rt Please merge the patches. Bastian -- All your people must learn before you can reach for the stars. -- Kirk, The Gamesters of Triskelion, stardate 3259.2 -- 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/20110722204956.ga2...@wavehammer.waldi.eu.org
Bug#631166: python2.6-minimal: Package fails to install
En Fri, 22 Jul 2011 00:51:33 +0200 Ben Hutchings b...@decadent.org.uk escribió: I can't reproduce this. Please run 'debsums -c linux-support-2.6.26-1'. Debian:/# debsums -c linux-support-2.6.26-1 debsums: missing file /usr/src/linux-support-2.6.26-1/modules/rules.real.include (from linux-support-2.6.26-1 package) debsums: missing file /usr/src/linux-support-2.6.26-1/modules/gencontrol.py (from linux-support-2.6.26-1 package) debsums: missing file /usr/src/linux-support-2.6.26-1/modules/rules.defs (from linux-support-2.6.26-1 package) debsums: missing file /usr/src/linux-support-2.6.26-1/modules/rules.include (from linux-support-2.6.26-1 package) debsums: missing file /usr/src/linux-support-2.6.26-1/config.defines.dump (from linux-support-2.6.26-1 package) debsums: missing file /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/utils.py (from linux-support-2.6.26-1 package) debsums: missing file /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/kconfig.py (from linux-support-2.6.26-1 package) debsums: missing file /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/patches.py (from linux-support-2.6.26-1 package) debsums: missing file /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/config.py (from linux-support-2.6.26-1 package) debsums: missing file /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/debian.py (from linux-support-2.6.26-1 package) debsums: missing file /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/gencontrol.py (from linux-support-2.6.26-1 package) debsums: missing file /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/__init__.py (from linux-support-2.6.26-1 package) debsums: missing file /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/abi.py (from linux-support-2.6.26-1 package) Regards. Sergio -- Yo uso software libre - I use freedom-based software -- Linux user since 973047600 -- 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/20110722213958.4c64d18e.sver...@gmail.com
Bug#631166: marked as done (python2.6-minimal: Package fails to install)
Your message dated Sat, 23 Jul 2011 03:39:52 +0200 with message-id 1311385192.3268.24.camel@localhost and subject line Re: python2.6-minimal: Package fails to install has caused the Debian Bug report #631166, regarding python2.6-minimal: Package fails to install 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.) -- 631166: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631166 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python2.6-minimal Version: 2.6.6-8+b1 Severity: grave Justification: renders package unusable Problem upgrading from lenny to squeeze. I check that files that does not exist but this files exists. I can not upgrade to squeeze, I must fall back to a backup. Configurando python2.6-minimal (2.6.6-8+b1) ... Linking and byte-compiling packages for runtime python2.6... /usr/lib/python2.6/dist-packages/twisted/web/microdom.py:157: SyntaxWarning: assertion is always true, perhaps remove parentheses? assert (oldChild.parentNode is self, file does not exist: /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/__init__.py file does not exist: /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/abi.py file does not exist: /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/config.py file does not exist: /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/debian.py file does not exist: /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/gencontrol.py file does not exist: /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/kconfig.py file does not exist: /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/patches.py file does not exist: /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/utils.py file does not exist: /usr/src/linux-support-2.6.26-1/modules/gencontrol.py Errors were ignored. Configurando libsqlite3-0 (3.7.3-1) ... Configurando python2.6 (2.6.6-8+b1) ... Configurando python-minimal (2.6.6-3+squeeze6) ... Configurando python (2.6.6-3+squeeze6) ... Linking and byte-compiling packages for runtime python2.6... file does not exist: /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/__init__.py file does not exist: /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/abi.py file does not exist: /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/config.py file does not exist: /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/debian.py file does not exist: /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/gencontrol.py file does not exist: /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/kconfig.py file does not exist: /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/patches.py file does not exist: /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/utils.py file does not exist: /usr/src/linux-support-2.6.26-1/modules/gencontrol.py Errors were ignored. running python rtupdate hooks for python2.6... file does not exist: /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/__init__.py file does not exist: /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/abi.py file does not exist: /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/config.py file does not exist: /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/debian.py file does not exist: /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/gencontrol.py file does not exist: /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/kconfig.py file does not exist: /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/patches.py file does not exist: /usr/src/linux-support-2.6.26-1/lib/python/debian_linux/utils.py file does not exist: /usr/src/linux-support-2.6.26-1/modules/gencontrol.py pycentral: pycentral updatedefault: error byte-compiling files (9) pycentral updatedefault: error byte-compiling files (9) error running python rtupdate hook pycentral Updating *.pc symlinks for python-gtk2-dev... dpkg: error al procesar python (--configure): el subproceso instalado el script post-installation devolvió el código de salida de error 4 dpkg: problemas de dependencias impiden la configuración de python-lxml: python-lxml depende de python (= 1.6.5-11~); sin embargo: El paquete `python' no está configurado todavía. python-lxml depende de python ( 2.7); sin embargo: El paquete `python' no está configurado todavía. dpkg: error al procesar python-lxml (--configure): problemas de dependencias - se deja sin configurar dpkg: problemas de dependencias impiden la configuración de isoquery: isoquery depende de python; sin embargo: El paquete `python' no está configurado todavía. isoquery depende de python-lxml; sin embargo:
