Processed: tagging 633738
Processing commands for cont...@bugs.debian.org: tags 633738 + pending Bug #633738 [linux-2.6] ip6_tunnel: kernel BUG at net_namespace.c:497 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 633738: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633738 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.13112317262095.transcr...@bugs.debian.org
Processed: tagging 633738
Processing commands for cont...@bugs.debian.org: tags 633738 + pending Bug #633738 [linux-2.6] ip6_tunnel: kernel BUG at net_namespace.c:497 Ignoring request to alter tags of bug #633738 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 633738: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633738 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.13112317412145.transcr...@bugs.debian.org
Bug#627655: linux-image-2.6.39-1-686-pae: missing NFS4.1 / pNFS support
Hi Ben, On Thursday 21 July 2011 01:01:19 Ben Hutchings wrote: [...] How about we start by enabling NFSv4.1 starting with release candidates for Linux 3.1, and see what feedback we get for that? That sounds OK, I guess, but it does introduce a significant delay. BTW, will the release candidates be available from experimental or from a separate repository? Cheers, Paul. -- 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/201107211213.13684.paul.mil...@desy.de
Bug#633961: linux images must conflict with unfixed input-utils
On Thu, 2011-07-21 at 07:05 +0300, Adrian Bunk wrote: On Thu, Jul 21, 2011 at 01:09:34AM +0200, Ben Hutchings wrote: On Mon, 2011-07-18 at 14:29 +0300, Adrian Bunk wrote: On Fri, Jul 15, 2011 at 06:30:41PM +0100, Ben Hutchings wrote: ... This is wrong on so many levels. 1. There is no way to declare relations to 'all kernel packages'. Why not? 1. There are many different binary packages for different hardware configurations, and we add and remove them quite regularly. 2. Although the binary packages provide virtual packages, virtual packages aren't versioned. That doesn't answer the question Why there are no versioned virtual packages. Policy §7.5: If a relationship field has a version number attached, only real packages will be considered to see whether the relationship is satisfied... [...] After that, a Breaks in all kernel images on the unfixed input-utils would be required. [...] Not going to happen. You need to fix this through a stable update. Why isn't that going to happen? As you said before, input-utils is a niche package. That's the one proper solution in this case. Especially considering that Backports are now more or less an official part of Debian, there are many scenarios where a stable update does not solve the problem. And keep in mind that if the fix for input-utils wasn't that trivial, a stable update would not even be an option. But apparently it was, so it is. 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#627655: linux-image-2.6.39-1-686-pae: missing NFS4.1 / pNFS support
On Thu, 2011-07-21 at 12:13 +0200, Paul Millar wrote: Hi Ben, On Thursday 21 July 2011 01:01:19 Ben Hutchings wrote: [...] How about we start by enabling NFSv4.1 starting with release candidates for Linux 3.1, and see what feedback we get for that? That sounds OK, I guess, but it does introduce a significant delay. Linux 3.1-rc1 should be out in 3 weeks or less. BTW, will the release candidates be available from experimental or from a separate repository? experimental. 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: system hangs during shutdown...
On Wed, 2011-07-20 at 18:34 -0600, Bruce Sass wrote:
...while unmounting an NFS import.
Hi,
[Please Cc me with any replies.]
--- copied from console ---
Asking all remaining processes to terminate... done.
Currently running processes (pstree):
init-+-4*[kded4---{kded4}]
|-rc---startpar---sendsigs---pstree
|-rpc.statd
|-rpcbind
'-rsyslogd---3*[{rsyslogd}]
Killing all remaining processes... Saving random seed... done.
failed.
Stopping enhanced syslogd: rsyslogd
Unmounting remote and non-toplevel virtual filesystems...[285770.720036] nfs:
server satone not responding, still trying
[After about 20 minutes had passed I hit the power button. :( ]
---
Satone is a dual-boot laptop that just happened to have changed from DGL
serving up a user's $HOME via NFS (the only fs it exports) to Windows Vista.
I'm mentioning this fact because I don't know if it matters that the
exporting
server disappeared period, or that it was replaced by a non-unix-like
system
that doesn't run an NFS server.
[...]
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.
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#633961: linux images must conflict with unfixed input-utils
On Thu, Jul 21, 2011 at 12:50:01PM +0200, Ben Hutchings wrote: On Thu, 2011-07-21 at 07:05 +0300, Adrian Bunk wrote: On Thu, Jul 21, 2011 at 01:09:34AM +0200, Ben Hutchings wrote: On Mon, 2011-07-18 at 14:29 +0300, Adrian Bunk wrote: On Fri, Jul 15, 2011 at 06:30:41PM +0100, Ben Hutchings wrote: ... This is wrong on so many levels. 1. There is no way to declare relations to 'all kernel packages'. Why not? 1. There are many different binary packages for different hardware configurations, and we add and remove them quite regularly. 2. Although the binary packages provide virtual packages, virtual packages aren't versioned. That doesn't answer the question Why there are no versioned virtual packages. Policy §7.5: If a relationship field has a version number attached, only real packages will be considered to see whether the relationship is satisfied... And that makes Provides: linux-image-2.6.39 impossible? [...] After that, a Breaks in all kernel images on the unfixed input-utils would be required. [...] Not going to happen. You need to fix this through a stable update. Why isn't that going to happen? As you said before, input-utils is a niche package. You fail to explain where the Breaks would cause any problem for anyone. ... Ben. cu Adrian -- Is there not promise of rain? Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. Only a promise, Lao Er said. Pearl S. Buck - Dragon Seed -- 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/2011072745.ga19...@localhost.pp.htv.fi
Bug#627655: linux-image-2.6.39-1-686-pae: missing NFS4.1 / pNFS support
Hi Ben, On Thursday 21 July 2011 12:51:11 Ben Hutchings wrote: On Thu, 2011-07-21 at 12:13 +0200, Paul Millar wrote: [..] but it does introduce a significant delay. Linux 3.1-rc1 should be out in 3 weeks or less. Ah! OK, that's not too bad. I thought it would be longer. BTW, will the release candidates be available from experimental or from a separate repository? experimental. Great, I'll try deploying 3.1-rc1 when it becomes available. Cheers, Paul. -- 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/201107211412.23371.paul.mil...@desy.de
Bug#577925: Start script
a VERY VERY basic sysv start/stop script attached here, for others to use. tested start and stop. copy in /etc/init.d/ and run something like chmod +x /etc/init.d/tgt update-rc.d tgt enable 2 to enable it at boot. -- Lorenzo Milesi - lorenzo.mil...@yetopen.it YetOpen S.r.l. - http://www.yetopen.it/ Via Carlo Torri Tarelli 19 - 23900 Lecco - ITALY - Tel 0341 220 205 - Fax 178 6070 222 GPG/PGP Key-Id: 0xE704E230 - http://keyserver.linux.it D.Lgs. 196/2003 Si avverte che tutte le informazioni contenute in questo messaggio sono riservate ed a uso esclusivo del destinatario. Nel caso in cui questo messaggio Le fosse pervenuto per errore, La invitiamo ad eliminarlo senza copiarlo, a non inoltrarlo a terzi e ad avvertirci non appena possibile. Grazie. tgt Description: application/shellscript
[PATCH] Add 3.0-rc7-rt0 patch set
It's currently enabled and build tested for amd64/amd64 and armel/versatile. 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 --- Some things I'm unsure about: - should I really add the series file and the disabled patches? (upside: the rt patches dir is nearly identical with the upstream patch queue.) - which platforms to enable the rt featureset for? Note that the diff below doesn't contain the actual rt-patches to make this patch smaller and easier to review. (But I forgot to really remove it on the first try. I assume the mailserver at lists.d.o just discarded it and so resend now with really having removed the patches.) Best regards Uwe --- changelog |4 + config/amd64/defines |2 + config/amd64/rt/defines|3 + config/armel/defines |2 + config/armel/rt/defines|3 + config/defines |4 + config/featureset-rt/config|5 + config/featureset-rt/defines |7 + ...x-build-failure-for-modular-ext3-4-builds.patch | 32 + .../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 + .../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 + .../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 +
Bug#577925: Ubuntu ref
For the record, Ubuntu provides an upstart script in their latest packages. https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/574554 I'm running 1.0.17 from wheezy on squeeze without issues. I agree that porting a more recent version on the latest stable would be VERY useful. In my case, I needed the device-type tg option. -- Lorenzo Milesi - lorenzo.mil...@yetopen.it GPG/PGP Key-Id: 0xE704E230 - http://keyserver.linux.it -- 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/996015139.1302.1311258746500.JavaMail.root@quaglia
Bug#635007: linux-2.6: Removing USB connection crashes usbnet, USB hotplugging
Package: linux-2.6 Version: 3.0.0~rc6-1~experimental.1 Severity: normal Removing the USB cable over which a connection via cdc_ether is established causes the system to produce a call trace and causes hotplugging new devices via USB to stop working without a restart, while existing USB devices such as a mouse remain working. -- Package-specific info: ** Version: Linux version 3.0.0-rc6-amd64 (Debian 3.0.0~rc6-1~experimental.1) (m...@debian.org) (gcc version 4.4.6 (Debian 4.4.6-6) ) #1 SMP Tue Jul 5 09:30:35 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.0.0-rc6-amd64 root=UUID=67091a05-bf38-4136-b876-09e4b81a44bc ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [10659.500857] [8133e560] ? gs_change+0x13/0x13 [10779.259606] INFO: task khubd:128 blocked for more than 120 seconds. [10779.259611] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [10779.259615] khubd D 88014f8583c0 0 128 2 0x [10779.259623] 88014f8583c0 0046 88014f8583c0 880151dd3850 [10779.259630] 00012840 880150323fd8 880150323fd8 00012840 [10779.259636] 88014f8583c0 880150322010 88014f8583c0 88014fb8b6a0 [10779.259642] Call Trace: [10779.259657] [81337362] ? __mutex_lock_common+0x10c/0x172 [10779.259664] [8105b099] ? wait_on_work+0xfd/0x11d [10779.259670] [8133748e] ? mutex_lock+0x1a/0x2c [10779.259712] [a002c2c4] ? usb_hcd_flush_endpoint+0x30/0xea [usbcore] [10779.259739] [a002e5e0] ? usb_set_interface+0x7f/0x202 [usbcore] [10779.259757] [a00300d5] ? usb_unbind_interface+0xa6/0x124 [usbcore] [10779.259767] [81249804] ? __device_release_driver+0x7f/0xca [10779.259773] [81249903] ? device_release_driver+0x1d/0x28 [10779.259779] [a0849059] ? usbnet_cdc_unbind+0x41/0x79 [cdc_ether] [10779.259787] [a0833fe4] ? usbnet_disconnect+0xa6/0xdd [usbnet] [10779.259804] [a003008a] ? usb_unbind_interface+0x5b/0x124 [usbcore] [10779.259813] [81249804] ? __device_release_driver+0x7f/0xca [10779.259820] [81249903] ? device_release_driver+0x1d/0x28 [10779.259828] [81248cea] ? bus_remove_device+0x9f/0xb4 [10779.259835] [81247610] ? device_del+0x129/0x191 [10779.259853] [a002d8ff] ? usb_disable_device+0x4b/0x13a [usbcore] [10779.259871] [a0028e2d] ? usb_disconnect+0x9d/0x149 [usbcore] [10779.259890] [a00296fb] ? hub_thread+0x5f8/0xfa4 [usbcore] [10779.259899] [81041da6] ? perf_event_task_sched_out+0x48/0x54 [10779.259907] [8105ff69] ? wake_up_bit+0x20/0x20 [10779.259920] [a0029103] ? hub_disconnect+0xdf/0xdf [usbcore] [10779.259933] [a0029103] ? hub_disconnect+0xdf/0xdf [usbcore] [10779.259938] [8105fb2d] ? kthread+0x7a/0x82 [10779.259946] [8133e564] ? kernel_thread_helper+0x4/0x10 [10779.259952] [8105fab3] ? kthread_worker_fn+0x147/0x147 [10779.259957] [8133e560] ? gs_change+0x13/0x13 [10899.018629] INFO: task khubd:128 blocked for more than 120 seconds. [10899.018634] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [10899.018638] khubd D 88014f8583c0 0 128 2 0x [10899.018645] 88014f8583c0 0046 88014f8583c0 880151dd3850 [10899.018652] 00012840 880150323fd8 880150323fd8 00012840 [10899.018658] 88014f8583c0 880150322010 88014f8583c0 88014fb8b6a0 [10899.018664] Call Trace: [10899.018678] [81337362] ? __mutex_lock_common+0x10c/0x172 [10899.018686] [8105b099] ? wait_on_work+0xfd/0x11d [10899.018691] [8133748e] ? mutex_lock+0x1a/0x2c [10899.018728] [a002c2c4] ? usb_hcd_flush_endpoint+0x30/0xea [usbcore] [10899.018735] [a002e5e0] ? usb_set_interface+0x7f/0x202 [usbcore] [10899.018741] [a00300d5] ? usb_unbind_interface+0xa6/0x124 [usbcore] [10899.018746] [81249804] ? __device_release_driver+0x7f/0xca [10899.018749] [81249903] ? device_release_driver+0x1d/0x28 [10899.018752] [a0849059] ? usbnet_cdc_unbind+0x41/0x79 [cdc_ether] [10899.018755] [a0833fe4] ? usbnet_disconnect+0xa6/0xdd [usbnet] [10899.018762] [a003008a] ? usb_unbind_interface+0x5b/0x124 [usbcore] [10899.018766] [81249804] ? __device_release_driver+0x7f/0xca [10899.018768] [81249903] ? device_release_driver+0x1d/0x28 [10899.018771] [81248cea] ? bus_remove_device+0x9f/0xb4 [10899.018773] [81247610] ? device_del+0x129/0x191 [10899.018780] [a002d8ff] ? usb_disable_device+0x4b/0x13a [usbcore] [10899.018786] [a0028e2d] ? usb_disconnect+0x9d/0x149 [usbcore] [10899.018793] [a00296fb] ? hub_thread+0x5f8/0xfa4 [usbcore] [10899.018796] [81041da6] ? perf_event_task_sched_out+0x48/0x54 [10899.018800]
Bug#622842: Same problem here
Hello, I'm also facing the same problem of the original reporter: using the same hardware and embedded wifi adapter cannot stay authenticated with the AP. Computer: Compaq Mini CQ10-520 root@stt300:~# lspci -v |grep -i broad 02:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01) Dmesg output (cutted): [ 71.769540] wlan0: direct probe to 00:23:f8:9d:ad:11 (try 1/3) [ 71.968088] wlan0: direct probe to 00:23:f8:9d:ad:11 (try 2/3) [ 72.168098] wlan0: direct probe to 00:23:f8:9d:ad:11 (try 3/3) [ 72.368088] wlan0: direct probe to 00:23:f8:9d:ad:11 timed out [ 82.869180] wlan0: direct probe to 00:23:f8:9d:ad:11 (try 1/3) [ 83.058401] wlan0: direct probe responded [ 83.058492] wlan0: authenticate with 00:23:f8:9d:ad:11 (try 1) [ 83.256081] wlan0: authenticate with 00:23:f8:9d:ad:11 (try 2) [ 83.299250] wlan0: authenticated [ 83.299340] wlan0: associate with 00:23:f8:9d:ad:11 (try 1) [ 83.496118] wlan0: associate with 00:23:f8:9d:ad:11 (try 2) [ 83.696186] wlan0: associate with 00:23:f8:9d:ad:11 (try 3) [ 83.896105] wlan0: association with 00:23:f8:9d:ad:11 timed out [ 93.967403] wlan0: direct probe to 00:23:f8:9d:ad:11 (try 1/3) [ 94.164124] wlan0: direct probe to 00:23:f8:9d:ad:11 (try 2/3) [ 94.364129] wlan0: direct probe to 00:23:f8:9d:ad:11 (try 3/3) [ 94.564124] wlan0: direct probe to 00:23:f8:9d:ad:11 timed out [ 104.269891] wlan0: direct probe to 00:23:f8:9d:ad:11 (try 1/3) [ 104.378142] wlan0: direct probe responded root@stt300:~# iw reg get country 00: (2402 - 2472 @ 40), (6, 20) (2457 - 2482 @ 20), (6, 20), PASSIVE-SCAN, NO-IBSS (2474 - 2494 @ 20), (6, 20), NO-OFDM, PASSIVE-SCAN, NO-IBSS (5170 - 5250 @ 40), (6, 20), PASSIVE-SCAN, NO-IBSS (5735 - 5835 @ 40), (6, 20), PASSIVE-SCAN, NO-IBSS After switching off/on the wifi button and issuing iw reg set EU adapter gets authenticated with the AP but lasts 5 minutes, after that it gets unlinked again. root@stt300:~# dmesg|grep cfg80211 [6.557465] cfg80211: Calling CRDA to update world regulatory domain [ 256.048142] cfg80211: Calling CRDA for country: US [ 357.212262] cfg80211: Calling CRDA for country: EU [ 540.024180] cfg80211: Calling CRDA to update world regulatory domain Nedless to say that using another wifi card work well (tested with rt73 and rt2xxx drivers) and changing the AP to another tx channel makes no difference at all (tested with 1, 3, 6, 9 and 11). P.S. Not sure if I have to set additional CC addresses in thid bug. Greetings, -- Camaleón -- 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/cakprtdf16txrkwud-as_jbovin7c5rt52cswpjrymh8djcn...@mail.gmail.com
Processed: Re: Root-on-LVM setup fails often due to timing issues
Processing commands for cont...@bugs.debian.org: severity 616689 important Bug #616689 [initramfs-tools] Root-on-LVM setup fails often due to timing issues Severity set to 'important' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 616689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616689 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.131127797113444.transcr...@bugs.debian.org
Bug#616689: Root-on-LVM setup fails often due to timing issues
severity 616689 important thanks I'm confirming this bug, and raising the severity to important. Jcristau and I have just finished upgrading a very old server from oldstable to stable. We were hoping to be able to perform the upgrade over ssh. We ended up having to go on-site, and spent the best part of an hour struggling with this issue. (This particular server takes some 5 minutes to reboot, so every change in the initramfs configuration is a pain.) scsi_mod.scan=sync turned out to solve our problem (thanks, Jurij). -- Juliusz -- 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/87sjpz5s3g@trurl.pps.jussieu.fr
Processed: tagging 632929
Processing commands for cont...@bugs.debian.org: tags 632929 - wontfix Bug #632929 [linux-2.6] linux-image-2.6.32-5-amd64: missing aha152x module in amd64 architecture Removed tag(s) wontfix. thanks Stopping processing here. Please contact me if you need assistance. -- 632929: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632929 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.131128278130266.transcr...@bugs.debian.org
Bug#632929: marked as done (linux-image-2.6.32-5-amd64: missing aha152x module in amd64 architecture)
Your message dated Thu, 21 Jul 2011 23:13:44 +0200 with message-id 1311282824.28569.50.camel@localhost and subject line Re: linux-image-2.6.32-5-amd64: missing aha152x module in amd64 architecture has caused the Debian Bug report #632929, regarding linux-image-2.6.32-5-amd64: missing aha152x module in amd64 architecture 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.) -- 632929: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632929 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-34squeeze1 Severity: important the aha152x module exists for 686 architecture, but not for amd64. I need it to use my APA-1460A Adaptec PCMCIA SCSI card. I set the severity as important because it keeps me from using my SCSI scanner. -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-34squeeze1) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed May 18 23:13:22 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=UUID=c46dc908-b1fb-4238-b6ff-d139b11ce5cc ro quiet splash nomodeset video=uvesafb:mode_option=1280x1024-24,mtrr=3,scroll=ywrap ** Not tainted ** Kernel log: [6.229040] pci_bus :05: Raising subordinate bus# of parent bus (#05) from #06 to #09 [6.229050] yenta_cardbus :05:0b.0: pcmcia: parent PCI bridge I/O window: 0x1000 - 0x1fff [6.229054] yenta_cardbus :05:0b.0: pcmcia: parent PCI bridge Memory window: 0xc400 - 0xc9ff [6.229058] yenta_cardbus :05:0b.0: pcmcia: parent PCI bridge Memory window: 0xc000 - 0xc3ff [6.419091] Linux video capture interface: v2.00 [6.451416] uvcvideo: Found UVC 1.00 device CNA7157 (04f2:b096) [6.474314] i915 :00:02.0: power state changed by ACPI to D0 [6.474650] i915 :00:02.0: power state changed by ACPI to D0 [6.474659] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [6.474663] input: CNA7157 as /devices/pci:00/:00:1d.7/usb2/2-3/2-3:1.0/input/input9 [6.474669] i915 :00:02.0: setting latency timer to 64 [6.474762] usbcore: registered new interface driver uvcvideo [6.474942] USB Video Class driver (v0.1.0) [6.493429] alloc irq_desc for 30 on node -1 [6.493433] alloc kstat_irqs on node -1 [6.493444] i915 :00:02.0: irq 30 for MSI/MSI-X [6.493452] [drm] set up 127M of stolen space [6.676035] usb 8-2: reset full speed USB device using uhci_hcd and address 2 [6.848629] usbcore: registered new interface driver speedtch [6.848978] speedtch 8-2:1.0: firmware: requesting speedtch-1.bin.0.00 [7.654521] Console: switching to colour frame buffer device 160x50 [7.657844] fb0: inteldrmfb frame buffer device [7.657846] registered panic notifier [7.660306] acpi device:0d: registered as cooling_device2 [7.660802] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input10 [7.660860] ACPI: Video Device [VGA] (multi-head: yes rom: yes post: no) [7.660887] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [7.748611] speedtch 8-2:1.0: firmware: requesting speedtch-1.bin.0 [7.751096] speedtch 8-2:1.0: firmware: requesting speedtch-1.bin [7.893132] speedtch 8-2:1.0: found stage 1 firmware speedtch-1.bin [7.893137] speedtch 8-2:1.0: firmware: requesting speedtch-2.bin.0.00 [7.895289] speedtch 8-2:1.0: firmware: requesting speedtch-2.bin.0 [7.897527] speedtch 8-2:1.0: firmware: requesting speedtch-2.bin [8.006463] speedtch 8-2:1.0: found stage 2 firmware speedtch-2.bin [8.987815] HDA Intel :00:1b.0: power state changed by ACPI to D0 [8.987859] HDA Intel :00:1b.0: power state changed by ACPI to D0 [8.987866] HDA Intel :00:1b.0: enabling device ( - 0002) [8.987875] HDA Intel :00:1b.0: PCI INT A - GSI 22 (level, low) - IRQ 22 [8.987928] HDA Intel :00:1b.0: setting latency timer to 64 [9.168155] hda_codec: ALC268: BIOS auto-probing. [9.168711] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input11 [ 11.368840] loop: module loaded [ 12.626557] ATM dev 0: ADSL line is synchronising [ 14.047108] fuse init (API version 7.13) [ 14.645759] EXT4-fs (sda9): mounted filesystem with ordered data mode [ 14.681770] EXT4-fs (sda6): mounted filesystem with ordered data mode [ 14.768467] EXT4-fs (sda8): mounted filesystem with ordered data mode [ 14.965721] kjournald starting. Commit interval 5 seconds [ 14.966053] EXT3 FS on sda11, internal journal [ 14.966060]
Processed: tagging 632929
Processing commands for cont...@bugs.debian.org:
tags 632929 + pending
Bug #632929 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-2.6.32-5-amd64: missing aha152x module in amd64 architecture
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
632929: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632929
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.131128310531068.transcr...@bugs.debian.org
Processed: tagging 633516
Processing commands for cont...@bugs.debian.org: tags 633516 + pending Bug #633516 [linux-2.6] linux-image-3.0.0-rc6-686-pae: comedi modules missing 3.0-rc6 Ignoring request to alter tags of bug #633516 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 633516: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633516 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.131128317031227.transcr...@bugs.debian.org
Re: [PATCH] Add 3.0-rc7-rt0 patch set
On Thu, 2011-07-21 at 16:25 +0200, Uwe Kleine-König wrote: It's currently enabled and build tested for amd64/amd64 and armel/versatile. 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 --- Some things I'm unsure about: - should I really add the series file and the disabled patches? (upside: the rt patches dir is nearly identical with the upstream patch queue.) - which platforms to enable the rt featureset for? Let's start with amd64/amd64, and any other flavours you know people are interested in. I'm not convinced armel/versatile is useful other than as proof that it compiles for ARM... [...] diff --git a/changelog b/changelog index 7bf0add..45cebaa 100644 --- a/changelog +++ b/changelog @@ -17,6 +17,10 @@ linux-2.6 (3.0.0~rc7-1~experimental.1) UNRELEASED; urgency=low [ Arnaud Patard ] * Merge ixp4xx build fix and enable ixp4xx back + [ Uwe Kleine-König ] + * add 3.0-rc7-rt0 patch set, currently enabled for amd/amd and amd64/amd64 +armel/versatile + -- maximilian attems m...@debian.org Tue, 05 Jul 2011 14:25:29 +0200 linux-2.6 (3.0.0~rc6-1~experimental.1) experimental; urgency=low [...] diff --git a/config/defines b/config/defines index 9f65ad3..27cac2b 100644 --- a/config/defines +++ b/config/defines @@ -22,6 +22,7 @@ arches: compiler: gcc-4.4 featuresets: none + rt [description] part-long-up: This kernel is not suitable for SMP (multi-processor, @@ -38,6 +39,9 @@ type: plain gcc-4.4: gcc-4.4 gcc-4.5: gcc-4.5 +[featureset-rt] +enabled: true + You are inserting this in the middle of the 'relations' section! Add it at the bottom of the file. # 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. 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). +part-short-rt: PREEMPT_RT +parts: rt [... removed many patches here ...] [...] It would be nice if you would add a script to refresh the patch series, similar to: debian/patches/bugfix/all/stable/gen-patch debian/patches/features/all/aufs2/gen-patch debian/patches/features/all/vserver/gen-patch 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: system hangs during shutdown...
On July 21, 2011 05:02:38 AM Ben Hutchings wrote:
On Wed, 2011-07-20 at 18:34 -0600, Bruce Sass wrote:
...while unmounting an NFS import.
Hi,
[Please Cc me with any replies.]
--- copied from console ---
Asking all remaining processes to terminate... done.
Currently running processes (pstree):
init-+-4*[kded4---{kded4}]
|-rc---startpar---sendsigs---pstree
|-rpc.statd
|-rpcbind
'-rsyslogd---3*[{rsyslogd}]
Killing all remaining processes... Saving random seed... done.
failed.
Stopping enhanced syslogd: rsyslogd
Unmounting remote and non-toplevel virtual filesystems...[285770.720036]
nfs: server satone not responding, still trying
[After about 20 minutes had passed I hit the power button. :( ]
---
Satone is a dual-boot laptop that just happened to have changed from DGL
serving up a user's $HOME via NFS (the only fs it exports) to Windows
Vista. I'm mentioning this fact because I don't know if it matters that
the exporting server disappeared period, or that it was replaced by a
non-unix-like system that doesn't run an NFS server.
[...]
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.
Ben.
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.
- Bruce
--
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/201107211620.35149.bms...@shaw.ca
Re: [PATCH] Add 3.0-rc7-rt0 patch set
On 21/07/11 16:32, Ben Hutchings wrote: Let's start with amd64/amd64, and any other flavours you know people are interested in. I'm not convinced armel/versatile is useful other than as proof that it compiles for ARM... How can i help you? Thanks -- Jacobo -- 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/4e28acd2.2030...@gnu.org
Bug#631166: python2.6-minimal: Package fails to install
I can't reproduce this. Please run 'debsums -c linux-support-2.6.26-1'. 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: squeeze 2.6.32-5-686 doesn´t boot without monitor
On Sun, 2011-07-17 at 20:54 +0100, postbote2009-deb...@yahoo.com wrote: Hello, since upgrading the squeeze kernel from 2.6.26-2-686 to 2.6.32-5-686 I ´ve been unable to boot my HP D510S/845G without attached monitor. If a monitor is attached, booting is successful, if the monitor is disconnected, booting hangs. Attached are the bootlogs from a successful and a failed boot as well a kernel log from a successful boot - unfortunately, without an attached monitor there is no kernel log. I suspect an interaction between xserver-xorg and the new kernel, as booting without monitor is successful when deinstalling the xserver-xorg package. 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? Are there any kernel options to enable booting without monitor? There is no such option, because that should always work. 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
Processed: notfound 634181 in 2.6.39-3, found 634181 in 2.6.39-2, tagging 634181
Processing commands for cont...@bugs.debian.org: notfound 634181 2.6.39-3 Bug #634181 [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 No longer marked as found in versions 2.6.39-3. found 634181 2.6.39-2 Bug #634181 [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-2' with architecture '' Unable to make a source version for version '2.6.39-2' Bug Marked as found in versions 2.6.39-2. tags 634181 - wheezy Bug #634181 [linux-2.6] linux-image-2.6.39-2-amd64: br_netfilter nat pagefault Removed tag(s) wheezy. 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.131128957820233.transcr...@bugs.debian.org
Bug#635035: [s390] doesn't has nbd module available
Package: linux-2.6 Version: 2.6.39-3 Severity: wishlist Tags: d-i Currently there're a development of partman-nbd for integration into Debian Installer and we started pushing the required changes to integrate it. Regarding kernel support, s390 is the only missing architecture. This bug is more a request for comments then a request. We have two possible ways of fixing this bug: * enabling nbd for s390; * documenting into installation manual that s390 lacks it; Either way works for me while the first seems the easier and avoids a divergion regarding feature sets. Thoughts? -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-2-amd64 (SMP w/4 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.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/20110721230347.14953.16181.report...@micro.lab.ossystems.com.br
Bug#634181: marked as done (linux-image-2.6.39-2-amd64: br_netfilter nat pagefault)
Your message dated Fri, 22 Jul 2011 01:19:33 +0200 with message-id 1311290373.28569.89.camel@localhost and subject line Re: Bug#634181: linux-image-2.6.39-2-amd64: br_netfilter nat pagefault has caused the Debian Bug report #634181, regarding linux-image-2.6.39-2-amd64: br_netfilter nat pagefault 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.) -- 634181: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634181 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.39-3 Severity: normal Tags: wheezy Unfortunately I have not found a way to reproduce this problem yet. So the only thing I can give is a describtion what I did. The box has some ethernet interfaces, among them eth0 and eth1. eth0 is part of a bridge, which is created by /etc/network/interfaces. ---/etc/network/interfaces cutout--- auto eth0 iface eth0 inet manual auto br0 iface br0 inet dhcp bridge_ports eth0 ---eof--- The box obtains 172.22.92.28/27 as IP on that bridge via DHCP and gets a default route via 172.22.92.1 via that bridge. On that bridge there are also various tap devices in use by VMs. After bootup, there are no iptables or ebtables rules, and eth1 is down. I use eth1 as something like a test-interface, so I usually configure it manually to fit my needs. What I did before the crash was: # ip link set eth1 up # ip addr add 192.168.1.5/24 dev eth1 # iptables -t nat -I POSTROUTING -o br0 -j MASQUERADE # echo 1 /proc/sys/net/ipv4/ip_forward This did not immediately cause the crash, judging from the backtrace, the crash is later caused by some network traffic, however as I read the backtrace, the crash could not have happened without the nat stuff being loaded. Unfortunately, I do not have a dump of network traffic at that time, on top of that I am not even sure on the path of the traffic which caused the crash in the first place. (routed from eth1 to br0? Originating on that host with default via br0?) To avoid any mixups, it should also be noted that at the time of running reportbug, linux-image-2.6.39-2-amd64 version 2.6.39-3 was running, while the crash occured on linux-image-2.6.39-2-amd64 version 2.6.39-2. -- Package-specific info: ** Version: Linux version 2.6.39-2-amd64 (Debian 2.6.39-2) ** Command line: root=/dev/mapper/storage-root ro intel_iommu=on console=ttyS0,115200 console=tty0 ** Not tainted ** Kernel log: [291476.322390] e1000e: eth1 NIC Link is Up 10 Mbps Half Duplex, Flow Control: None [291476.329865] e1000e :05:00.0: eth1: Autonegotiated half duplex but link partner cannot autoneg. Try forcing full duplex if link gets many collisions. [291476.343738] e1000e :05:00.0: eth1: 10/100 speed: disabling TSO [292453.071471] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [292708.909247] BUG: unable to handle kernel paging request at 88032ef51ffe [292708.916328] IP: [a03626ff] br_nf_pre_routing_finish_bridge+0x66/0xb5 [bridge] [292708.924450] PGD 1604063 PUD 33fffa067 PMD 32ef66063 PTE 80032ef51161 [292708.931305] Oops: 0003 [#1] SMP [292708.934659] last sysfs file: /sys/devices/system/cpu/cpu3/topology/thread_siblings [292708.942316] CPU 0 [292708.944246] Modules linked in: ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 tun ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables acpi_cpufreq mperf cpufreq_stats cpufreq_userspace cpufreq_conservative cpufreq_powersave parport_pc ppdev lp parport rfcomm bnep bluetooth rfkill binfmt_misc fuse nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc bridge stp jfs kvm_intel w83627ehf hwmon_vid kvm loop ftdi_sio cdc_ether usbnet usbserial mii i2c_i801 processor thermal_sys i2c_core ghes button pcspkr evdev hed ext4 mbcache jbd2 crc16 dm_snapshot sha256_generic aesni_intel cryptd aes_x86_64 aes_generic cbc dm_crypt dm_mod raid456 md_mod async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx sd_mod usb_storage usbhid crc_t10dif hid uas ahci libahci libata ehci_hcd scsi_mod acenic usbcore e1000e [last unloaded: scsi_wait_scan] [292709.025588] [292709.027176] Pid: 2919, comm: kvm Not tainted 2.6.39-2-amd64 #1 System manufacturer System Product Name/P7F-M [292709.037143] RIP: 0010:[a03626ff] [a03626ff] br_nf_pre_routing_finish_bridge+0x66/0xb5 [bridge] [292709.047689] RSP: 0018:88033fc03c68 EFLAGS: 00010246 [292709.053091] RAX: RBX: 8801cbd8d180 RCX: 8801fbbe3700 [292709.060311] RDX: 88032d506c80 RSI: 88032d506cd8 RDI: 8801cbd8d180
Bug#634180: [PATCH] ahci: Add JMicron 362 device IDs
The JMicron JMB362 controller supports AHCI only, but some revisions
use the IDE class code. These need to be matched by device ID.
These additions have apparently been included by QNAP in their NAS
devices using these controllers.
Signed-off-by: Ben Hutchings b...@decadent.org.uk
---
This is basically the same change made by unknown persons at QNAP.
However, I think the only copyrightable part (if any) is the comment,
which is my own. Therefore I believe I can sign this off myself.
Ben.
drivers/ata/ahci.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/drivers/ata/ahci.c b/drivers/ata/ahci.c
index fd318ac..67dbd6a 100644
--- a/drivers/ata/ahci.c
+++ b/drivers/ata/ahci.c
@@ -263,6 +263,9 @@ static const struct pci_device_id ahci_pci_tbl[] = {
/* JMicron 360/1/3/5/6, match class to avoid IDE function */
{ PCI_VENDOR_ID_JMICRON, PCI_ANY_ID, PCI_ANY_ID, PCI_ANY_ID,
PCI_CLASS_STORAGE_SATA_AHCI, 0xff, board_ahci_ign_iferr },
+ /* JMicron 362B and 362C have an AHCI function with IDE class code */
+ { PCI_VDEVICE(JMICRON, 0x2362), board_ahci_ign_iferr },
+ { PCI_VDEVICE(JMICRON, 0x236f), board_ahci_ign_iferr },
/* ATI */
{ PCI_VDEVICE(ATI, 0x4380), board_ahci_sb600 }, /* ATI SB600 */
--
1.7.5.4
--
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/1311291802.28569.93.camel@localhost
Bug#627098: linux-image-2.6.32-5-686: rndis_host fails to recognize usb device
Forwarded Message From: Mark Glassberg vzeea...@myfairpoint.net To: Ben Hutchings b...@decadent.org.uk Subject: Re: Bug#627098: linux-image-2.6.32-5-686: rndis_host fails to recognize usb device Date: Sat, 16 Jul 2011 11:59:20 -0400 On Wed, Jul 13, 2011 at 12:55:44PM +, Ben Hutchings wrote: Can you try a newer version (2.6.39 from testing/unstable or 3.0-rc6 from experimental)? I don't know if 2.6.39 can be used on my squeeze system, so I burned the first cd of wheeze and installed it. The installer had problems with my usb modem/router, so I finished the install and rebooted without it. I then connected the usb modem/router, but the kernel and/or rndis_host failed. I then disconnected the usb modem/router and connected the PC Port. Again, it failed. The /var/log/messages file is attached. Please let me know if there are any arguments which should be used with rndis_host or any of the other modules. Also, was it necessary to install wheeze? And finally, how do I go about using 3.0-rc6? Mark Jul 16 11:31:14 hpn2 kernel: imklog 5.8.2, log source = /proc/kmsg started. Jul 16 11:31:14 hpn2 rsyslogd: [origin software=rsyslogd swVersion=5.8.2 x-pid=807 x-info=http://www.rsyslog.com;] start Jul 16 11:31:14 hpn2 kernel: [0.00] Initializing cgroup subsys cpuset Jul 16 11:31:14 hpn2 kernel: [0.00] Initializing cgroup subsys cpu Jul 16 11:31:14 hpn2 kernel: [0.00] Linux version 2.6.39-2-686-pae (Debian 2.6.39-2) (b...@decadent.org.uk) (gcc version 4.4.6 (Debian 4.4.6-3) ) #1 SMP Wed Jun 8 11:33:14 UTC 2011 Jul 16 11:31:14 hpn2 kernel: [0.00] BIOS-provided physical RAM map: Jul 16 11:31:14 hpn2 kernel: [0.00] BIOS-e820: - 0009fc00 (usable) Jul 16 11:31:14 hpn2 kernel: [0.00] BIOS-e820: 0009fc00 - 000a (reserved) Jul 16 11:31:14 hpn2 kernel: [0.00] BIOS-e820: 000e6000 - 0010 (reserved) Jul 16 11:31:14 hpn2 kernel: [0.00] BIOS-e820: 0010 - 3ef2fc00 (usable) Jul 16 11:31:14 hpn2 kernel: [0.00] BIOS-e820: 3ef2fc00 - 3ef3 (ACPI NVS) Jul 16 11:31:14 hpn2 kernel: [0.00] BIOS-e820: 3ef3 - 3ef4 (ACPI data) Jul 16 11:31:14 hpn2 kernel: [0.00] BIOS-e820: 3ef4 - 3eff (ACPI NVS) Jul 16 11:31:14 hpn2 kernel: [0.00] BIOS-e820: 3eff - 3f00 (reserved) Jul 16 11:31:14 hpn2 kernel: [0.00] BIOS-e820: fecf - fecf1000 (reserved) Jul 16 11:31:14 hpn2 kernel: [0.00] BIOS-e820: fed2 - feda (reserved) Jul 16 11:31:14 hpn2 kernel: [0.00] Notice: NX (Execute Disable) protection missing in CPU! Jul 16 11:31:14 hpn2 kernel: [0.00] DMI 2.3 present. Jul 16 11:31:14 hpn2 kernel: [0.00] last_pfn = 0x3ef2f max_arch_pfn = 0x100 Jul 16 11:31:14 hpn2 kernel: [0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 Jul 16 11:31:14 hpn2 kernel: [0.00] found SMP MP-table at [c00ff780] ff780 Jul 16 11:31:14 hpn2 kernel: [0.00] init_memory_mapping: -379fe000 Jul 16 11:31:14 hpn2 kernel: [0.00] RAMDISK: 3773a000 - 37ff Jul 16 11:31:14 hpn2 kernel: [0.00] Allocated new RAMDISK: 36e84000 - 37739883 Jul 16 11:31:14 hpn2 kernel: [0.00] Move RAMDISK from 3773a000 - 37fef882 to 36e84000 - 37739882 Jul 16 11:31:14 hpn2 kernel: [0.00] 117MB HIGHMEM available. Jul 16 11:31:14 hpn2 kernel: [0.00] 889MB LOWMEM available. Jul 16 11:31:14 hpn2 kernel: [0.00] mapped low ram: 0 - 379fe000 Jul 16 11:31:14 hpn2 kernel: [0.00] low ram: 0 - 379fe000 Jul 16 11:31:14 hpn2 kernel: [0.00] Zone PFN ranges: Jul 16 11:31:14 hpn2 kernel: [0.00] DMA 0x0010 - 0x1000 Jul 16 11:31:14 hpn2 kernel: [0.00] Normal 0x1000 - 0x000379fe Jul 16 11:31:14 hpn2 kernel: [0.00] HighMem 0x000379fe - 0x0003ef2f Jul 16 11:31:14 hpn2 kernel: [0.00] Movable zone start PFN for each node Jul 16 11:31:14 hpn2 kernel: [0.00] early_node_map[2] active PFN ranges Jul 16 11:31:14 hpn2 kernel: [0.00] 0: 0x0010 - 0x009f Jul 16 11:31:14 hpn2 kernel: [0.00] 0: 0x0100 - 0x0003ef2f Jul 16 11:31:14 hpn2 kernel: [0.00] Using APIC driver default Jul 16 11:31:14 hpn2 kernel: [0.00] SFI: Simple Firmware Interface v0.81 http://simplefirmware.org Jul 16 11:31:14 hpn2 kernel: [0.00] Intel MultiProcessor Specification v1.4 Jul 16 11:31:14 hpn2 kernel: [0.00] Virtual Wire compatibility mode. Jul 16 11:31:14 hpn2 kernel: [0.00] MPTABLE: OEM ID: Jul 16 11:31:14 hpn2 kernel: [0.00] MPTABLE: Product ID: Springdale-G Jul 16 11:31:14 hpn2 kernel: [0.00] MPTABLE: APIC at: 0xFEE0 Jul 16 11:31:14 hpn2
Bug#627098: linux-image-2.6.32-5-686: rndis_host fails to recognize usb device
On Sat, 2011-07-16 at 11:59 -0400, Mark Glassberg wrote:
On Wed, Jul 13, 2011 at 12:55:44PM +, Ben Hutchings wrote:
Can you try a newer version (2.6.39 from testing/unstable or 3.0-rc6 from
experimental)?
I don't know if 2.6.39 can be used on my squeeze system, so I burned the
first cd of wheeze and installed it. The installer had problems with my
usb modem/router, so I finished the install and rebooted without it. I
then connected the usb modem/router, but the kernel and/or rndis_host
failed.
That's annoying, because we got that device working... but it looks like
I dropped the bug fix from the Debian package of 2.6.39. However the
bug fix will be back again in Linux 3.0.
I then disconnected the usb modem/router and connected the PC Port.
Again, it failed. The /var/log/messages file is attached.
Please let me know if there are any arguments which should be used with
rndis_host or any of the other modules. Also, was it necessary to install
wheeze?
It shouldn't be, but you would need to upgrade initramfs-tools and
linux-base as well as the linux-image-* package.
And finally, how do I go about using 3.0-rc6?
You would first have to add a line to /etc/apt/sources.list referring to
a mirror of the 'experimental' suite.
Please can you test the attached patch against the experimental version,
following the instructions at:
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official.
Ben.
--
Ben Hutchings
Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer
From afa0c8df93e460eabb63aa1afcc044bc000affc5 Mon Sep 17 00:00:00 2001
From: Ben Hutchings b...@decadent.org.uk
Date: Fri, 22 Jul 2011 01:56:57 +0200
Subject: [PATCH] rndis_host: Poll status before control channel on 2Wire PC
Port
Apply the RNDIS_DRIVER_DATA_POLL_STATUS quirk to this device.
Signed-off-by: Ben Hutchings b...@decadent.org.uk
---
drivers/net/usb/rndis_host.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/drivers/net/usb/rndis_host.c b/drivers/net/usb/rndis_host.c
index 255d6a4..067db14 100644
--- a/drivers/net/usb/rndis_host.c
+++ b/drivers/net/usb/rndis_host.c
@@ -610,6 +610,11 @@ static const struct usb_device_id products [] = {
USB_CLASS_COMM, 2 /* ACM */, 0x0ff),
.driver_info = (unsigned long) rndis_poll_status_info,
}, {
+ /* 2Wire PC Port */
+ USB_DEVICE_AND_INTERFACE_INFO(0x1630, 0x0011,
+ USB_CLASS_COMM, 2 /* ACM */, 0x0ff),
+ .driver_info = (unsigned long) rndis_poll_status_info,
+}, {
/* RNDIS is MSFT's un-official variant of CDC ACM */
USB_INTERFACE_INFO(USB_CLASS_COMM, 2 /* ACM */, 0x0ff),
.driver_info = (unsigned long) rndis_info,
--
1.7.5.4
signature.asc
Description: This is a digitally signed message part
Processed: tagging 627098
Processing commands for cont...@bugs.debian.org: tags 627098 + patch Bug #627098 [linux-2.6] linux-image-2.6.32-5-686: rndis_host fails to recognize usb device Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 627098: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627098 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.1311292981859.transcr...@bugs.debian.org
Bug#632734: Strange
Forwarded Message From: Frank McCormick fmccorm...@videotron.ca To: Ben Hutchings b...@decadent.org.uk Subject: Re: Bug#632734: Strange Date: Sat, 16 Jul 2011 09:54:49 -0400 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. I still don't understand why the changes created this problem for me. The strange thing is on multiple tries, on a regular boot and on maintenance boots, the computer will sometimes get to different points before it gives up. The boots usually end up with the num lock and caps lock lights flashing. I guess what I'll do is remove the PAE kernel again and continue with the previous series. Long term I don't know what I'll do - I do know that Ubuntu kernels have not yet been a problem. So if the working kernel in my machine gets too far behind I have a choice. -- 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/1311293076.28569.114.camel@localhost
Bug#632734: Strange
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)? I still don't understand why the changes created this problem for me. The strange thing is on multiple tries, on a regular boot and on maintenance boots, the computer will sometimes get to different points before it gives up. The boots usually end up with the num lock and caps lock lights flashing. 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 in http://www.bitwizard.nl/sig11/. Ben. I guess what I'll do is remove the PAE kernel again and continue with the previous series. Long term I don't know what I'll do - I do know that Ubuntu kernels have not yet been a problem. So if the working kernel in my machine gets too far behind I have a choice. -- 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#634023: linux-source-2.6.32: Kernel panic when inserting usb stick
This oops (and consequent panic) was reported as occurring when a USB stick is inserted, and as being a regression between Debian's package version 2.6.32-34squeeze1 (longterm 2.6.32.39) and 2.6.32-35 (longterm 2.6.32.41). On Sat, 2011-07-16 at 12:22 +0200, Simon Brandmair wrote: Netconsole output: BUG: unable to handle kernel NULL pointer dereference at 0040 IP: [81128b5b] elv_queue_empty+0x1b/0x30 PGD 12a8cc067 PUD 12ae62067 PMD 0 Oops: [#1] sd 6:0:0:0: [sdb] 1994752 512-byte logical blocks: (1.02 GB/974 MiB) SMP last sysfs file: /sys/devices/pci:00/:00:13.5/usb1/1-10/1-10:1.0/host6/scsi_host/host6/uevent CPU 1 Modules linked in: usb_storage uvcvideo videodev v4l1_compat sd 6:0:0:0: [sdb] Write Protect is off sd 6:0:0:0: [sdb] Mode Sense: 43 00 00 00 sd 6:0:0:0: [sdb] Assuming drive cache: write through usb-storage: device scan complete v4l2_compat_ioctl32 netconsole powernow_k8 fuse nfsd exportfs nfs lockd auth_rpcgss sunrpc psmouse sha256_generic ansi_cprng krng eseqiv rng aes_x86_64 aes_generic cbc cryptomgr crypto_hash aead pcompress dm_crypt crypto_blkcipher crypto_algapi crypto dm_mod usbhid snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq sg sd 6:0:0:0: [sdb] Assuming drive cache: write through sdb: snd_timer snd_seq_device sr_mod firewire_ohci firewire_core snd cdrom r8169 bitrev soundcore crc_itu_t crc32 sdb1 ohci_hcd ehci_hcd rtc_cmos snd_page_alloc usbcore pata_atiixp evdev rtc_core mii ide_pci_generic rtc_lib k10temp hwmon button processor sd_mod thermal thermal_sys [last unloaded: nvidia] Pid: 7, comm: ksoftirqd/1 Tainted: P 2.6.32-20110716 #1 MS-7388 This was built from a custom configuration; Simon can presumably provide the configuration if required. The proprietary module is presumably 'nvidia' and hopefully not responsible for messing with block devices. RIP: 0010:[81128b5b] [81128b5b] elv_queue_empty+0x1b/0x30 RSP: 0018:880028283e18 EFLAGS: 00010046 RAX: RBX: 88012ccf71c0 RCX: 88012aafd6d0 RDX: 88012a8e1900 RSI: 0246 RDI: 88012ccf71c0 RBP: 0292 R08: 88012aafd6e0 R09: 88012f8c4c50 R10: R11: R12: 88012ccf71c0 R13: 880028283e68 R14: 88012fbbe900 R15: 88012fa33840 FS: 7f429e058700() GS:88002828() knlGS: CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b CR2: 0040 CR3: 00012e83e000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process ksoftirqd/1 (pid: 7, threadinfo 88012f892000, task 88012f88f1d0) Stack: 88012ccf71c0 8112c22a 88012ccf71c0 8112c438 0 88012fa33840 88012fa33800 880028283e68 811d5e6a 0 88012fa33828 0246 880028283e68 880028283e68 Call Trace: IRQ [8112c22a] ? __blk_run_queue+0x1a/0x150 [8112c438] ? blk_run_queue+0x28/0x50 [811d5e6a] ? scsi_run_queue+0xda/0x360 [811d6e0b] ? scsi_next_command+0x3b/0x60 [811d79cf] ? scsi_io_completion+0x32f/0x510 [8113110d] ? blk_done_softirq+0x6d/0x80 [8104238d] ? __do_softirq+0x9d/0x130 [8100c27c] ? call_softirq+0x1c/0x30 EOI [8100e15d] ? do_softirq+0x4d/0x80 [81041f8f] ? ksoftirqd+0x6f/0xf0 [81041f20] ? ksoftirqd+0x0/0xf0 [8105245e] ? kthread+0x8e/0xa0 [8100c17a] ? child_rip+0xa/0x20 [810523d0] ? kthread+0x0/0xa0 [8100c170] ? child_rip+0x0/0x20 Code: eb 94 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec 08 31 c0 48 3b 3f 48 8b 57 18 74 09 48 83 c4 08 c3 0f 1f 40 00 48 8b 02 48 8b 50 40 b8 01 00 00 00 48 85 d2 74 e6 48 83 c4 08 ff e2 90 RIP [81128b5b] elv_queue_empty+0x1b/0x30 RSP 880028283e18 CR2: 0040 ---[ end trace dd18fad6b2c0435a ]--- [...] I would guess this is related to one of: commit 3b4b7c75885a0acde5ff2e3f66eebe98471c3675 Author: James Bottomley james.bottom...@suse.de Date: Sun May 1 09:42:07 2011 -0500 fix oops in scsi_run_queue() commit c055f5b2614b4f758ae6cc86733f31fa4c2c5844 upstream. commit 0ccd644ce6a803b4f7ae5b3b4da614b8a51037cc Author: James Bottomley james.bottom...@suse.de Date: Fri Apr 22 10:39:59 2011 -0500 put stricter guards on queue dead checks commit 86cbfb5607d4b81b1a993ff689bbd2addd5d3a9b upstream. 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
Processed: bug 634681 is forwarded to linux-s...@vger.kernel.org ...
Processing commands for cont...@bugs.debian.org: forwarded 634681 linux-s...@vger.kernel.org Bug #634681 [linux-2.6] linux-image-2.6.39-2-686-pae: Usb oops with 2.6.39 (elv_put_request) Bug #631187 [linux-2.6] Kernel panics when removing external hard drive Bug #633890 [linux-2.6] [linux-2.6] kernel oops while disconnecting usb cdrom Set Bug forwarded-to-address to 'linux-s...@vger.kernel.org'. Set Bug forwarded-to-address to 'linux-s...@vger.kernel.org'. Set Bug forwarded-to-address to 'linux-s...@vger.kernel.org'. forwarded 634023 linux-s...@vger.kernel.org Bug #634023 [src:linux-2.6] linux-source-2.6.32: Kernel panic when inserting usb stick Set Bug forwarded-to-address to 'linux-s...@vger.kernel.org'. thanks Stopping processing here. Please contact me if you need assistance. -- 634023: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634023 634681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634681 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.13112941254189.transcr...@bugs.debian.org
Bug#609638: include p4-clockmod on linux-image
I have the same problem as Rogério Brito, Tue, 11 Jan 2011 A public school depends on two Fujitsu PRIMERGY Econel 200 servers of 5 (five) years old, containing Xeon 2.8 GHz processors, ... If I compile a custom kernel, then I will miss the security updates, ... hence I open a security hole. The public school has no climate opportunity, therefore the Xeon processor running 2.8 GHz in hot summer turns the ventillators on high speed, risking a cooling failure. Even a fixed 350 MHz setting would be a satisfactory solution for the hot summers. But if the p4-clockmod is not there in the official debian kernel release, then I risk either a cooling failure or a security hole. I can imagine a solution, that p4-clockmod will be included WITHOUT debian guarante, ... that is, a bug report can be accepted only if the bug is still there even if the p4-clockmod module is removed.
Bug#634181: linux-image-2.6.39-2-amd64: br_netfilter nat pagefault
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. 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. Attached, there is a dump of the complete kernel log on 2.6.39-3, I hope this makes it into the bugtracker. :/ Best Regards, Christian Franke [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.39-2-amd64 (Debian 2.6.39-3) (b...@decadent.org.uk) (gcc version 4.4.6 (Debian 4.4.6-6) ) #1 SMP Tue Jul 5 02:51:22 UTC 2011 [0.00] Command line: root=/dev/mapper/storage-root ro intel_iommu=on console=ttyS0,115200 console=tty0 [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: 0100 - 0009e800 (usable) [0.00] BIOS-e820: 0009e800 - 000a (reserved) [0.00] BIOS-e820: 000e4000 - 0010 (reserved) [0.00] BIOS-e820: 0010 - bf77 (usable) [0.00] BIOS-e820: bf77e000 - bf78 (reserved) [0.00] BIOS-e820: bf78 - bf78e000 (ACPI data) [0.00] BIOS-e820: bf78e000 - bf7dc000 (ACPI NVS) [0.00] BIOS-e820: bf7dc000 - c000 (reserved) [0.00] BIOS-e820: e000 - f000 (reserved) [0.00] BIOS-e820: fee0 - fee01000 (reserved) [0.00] BIOS-e820: ffe0 - 0001 (reserved) [0.00] BIOS-e820: 0001 - 00034000 (usable) [0.00] NX (Execute Disable) protection: active [0.00] DMI 2.6 present. [0.00] No AGP bridge found [0.00] last_pfn = 0x34 max_arch_pfn = 0x4 [0.00] x86 PAT enabled: cpu 0, old 0x7010600070106, new 0x7010600070106 [0.00] last_pfn = 0xbf770 max_arch_pfn = 0x4 [0.00] found SMP MP-table at [880ff780] ff780 [0.00] init_memory_mapping: -bf77 [0.00] init_memory_mapping: 0001-00034000 [0.00] RAMDISK: 7f492000 - 7fff4000 [0.00] ACPI: RSDP 000fb6a0 00024 (v02 ACPIAM) [0.00] ACPI: XSDT bf780100 0007C (v01 092410 XSDT1014 20100924 MSFT 0097) [0.00] ACPI: FACP bf780290 000F4 (v03 092410 FACP1014 20100924 MSFT 0097) [0.00] ACPI: DSDT bf7804b0 05814 (v01 S0093 S0093501 0501 INTL 20060113) [0.00] ACPI: FACS bf78e000 00040 [0.00] ACPI: APIC bf780390 000D2 (v01 092410 APIC1014 20100924 MSFT 0097) [0.00] ACPI: MCFG bf780470 0003C (v01 092410 OEMMCFG 20100924 MSFT 0097) [0.00] ACPI: OEMB bf78e040 00072 (v01 092410 OEMB1014 20100924 MSFT 0097) [0.00] ACPI: HPET bf78a4b0 00038 (v01 092410 OEMHPET 20100924 MSFT 0097) [0.00] ACPI: DMAR bf78e0c0 00090 (v01AMI OEMDMAR 0001 MSFT 0097) [0.00] ACPI: SSDT bf78fba0 00363 (v01 DpgPmmCpuPm 0012 INTL 20060113) [0.00] ACPI: EINJ bf78a4f0 00130 (v01 AMIER AMI_EINJ 20100924 MSFT 0097) [0.00] ACPI: BERT bf78a680 00030 (v01 AMIER AMI_BERT 20100924 MSFT 0097) [0.00] ACPI: ERST bf78a6b0 001B0 (v01 AMIER AMI_ERST 20100924 MSFT 0097) [0.00] ACPI: HEST bf78a860 000A8 (v01 AMIER ABC_HEST 20100924 MSFT 0097) [0.00] No NUMA configuration found [0.00] Faking a node at -00034000 [0.00] Initmem setup node 0 -00034000 [0.00] NODE_DATA [00033fffb000 - 00033fff] [0.00] Zone PFN ranges: [0.00] DMA 0x0010 - 0x1000 [0.00] DMA320x1000 - 0x0010 [0.00] Normal 0x0010 - 0x0034 [0.00] Movable zone start PFN for each node [0.00] early_node_map[3] active PFN ranges [0.00] 0: 0x0010 - 0x009e [0.00] 0: 0x0100 - 0x000bf770 [0.00] 0: 0x0010 - 0x0034 [0.00] ACPI: PM-Timer IO Port: 0x808 [0.00] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) [0.00] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x04] enabled) [0.00] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled) [0.00] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x05] enabled) [0.00] ACPI: LAPIC
