Bug#607484: upgrade-reports: unusable on intel i810
On Mon, Dec 20, 2010 at 22:58:05 +0100, relat...@gmx.net wrote: > the upstream bug is: > https://bugs.freedesktop.org/show_bug.cgi?id=26345 > > as you can see in the report this was reported many times and appears to > affect all 845G chipsets, so please do not ship squeeze without a fix or the > following workaround. it took me about 30 reboots to figure this out. > > the workaround is: > > Option "Shadow" "true" > in the xorg.conf "Device" section. > Shadow is enabled by default on 845, so that shouldn't make any difference. Cheers, Julien signature.asc Description: Digital signature
Bug#607484: upgrade-reports: unusable on intel i810
the upstream bug is: https://bugs.freedesktop.org/show_bug.cgi?id=26345 as you can see in the report this was reported many times and appears to affect all 845G chipsets, so please do not ship squeeze without a fix or the following workaround. it took me about 30 reboots to figure this out. the workaround is: Option "Shadow" "true" in the xorg.conf "Device" section. to reproduce this bug, use: x11perf -range copywinpix10,comppixwin500 -time 1 -repeat 1 this appears to be a xorg bug, not a kernel bug. please change the assignment. -- DEREFER http://www.gmx.net/?status=hinweis";> http://www.gmx.net/?status=hinweis";>Einen Moment bitte, die angeforderte Seite wird geladen... GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt auch mit gratis Notebook-Flat! http://portal.gmx.net/de/go/dsl -- 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/20101220215805.95...@gmx.net
Bug#607669: linux-image-2.6.37-rc5-amd64: Dell Latitude D630 backlight fails to resume to "on"
Package: linux-2.6
Version: 2.6.37~rc5-1~experimental.3
Severity: normal
Tags: experimental
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
when running the 3.6.37-rc5 kernel, I noticed that my screen fails to
"relight" after being suspended by the desktop manager (inactivitiy timeout).
I can reliably reproduce this (and recover) by following these steps:
1) boot, up to a running X
2) $ xset dpms force off
3) move mouse
Now the screen is on, things work, but I cannot light the screen more than a
bare minimum (using the Fn-{up,down} "hardware" keys), while I can before step
2. I can recover from this situation by suspending-to-ram and waking up again.
This is also a regression from the Squeeze-Sid kernel (2.6.32-29), but I think
it worked with 2.6.36.
Cheers,
OdyX
- -- Package-specific info:
** Version:
Linux version 2.6.37-rc5-amd64 (Debian 2.6.37~rc5-1~experimental.3)
(b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-7) ) #1 SMP Sat Dec 11
19:38:02 UTC 2010
** Command line:
BOOT_IMAGE=/vmlinuz-2.6.37-rc5-amd64 root=/dev/mapper/Tamino-Root ro quiet
splash
** Not tainted
** Kernel log:
[ 9368.431655] uhci_hcd :00:1d.1: setting latency timer to 64
[ 9368.431682] usb usb6: root hub lost power or was reset
[ 9368.431694] uhci_hcd :00:1d.2: PCI INT C -> GSI 22 (level, low) -> IRQ 22
[ 9368.431701] uhci_hcd :00:1d.2: setting latency timer to 64
[ 9368.431728] usb usb7: root hub lost power or was reset
[ 9368.431742] ehci_hcd :00:1d.7: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 9368.431748] ehci_hcd :00:1d.7: setting latency timer to 64
[ 9368.431796] pci :00:1e.0: setting latency timer to 64
[ 9368.431808] ata_piix :00:1f.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 9368.431813] ata_piix :00:1f.1: setting latency timer to 64
[ 9368.431864] ahci :00:1f.2: setting latency timer to 64
[ 9368.431980] ata5: port disabled. ignoring.
[ 9368.431989] pci :00:1c.5: wake-up capability disabled by ACPI
[ 9368.432016] tg3 :09:00.0: PME# disabled
[ 9368.432052] i915 :00:02.0: setting latency timer to 64
[ 9368.439031] sd 0:0:0:0: [sda] Starting disk
[ 9368.472278] dell-wmi: Unknown key e043 pressed
[ 9368.484437] firewire_core: skipped bus generations, destroying all nodes
[ 9368.515466] serial 00:09: activated
[ 9368.760091] ata3: SATA link down (SStatus 0 SControl 300)
[ 9368.792078] usb 7-1: reset full speed USB device using uhci_hcd and address 2
[ 9368.984133] firewire_core: rediscovered device fw0
[ 9369.040077] usb 3-2: reset full speed USB device using uhci_hcd and address 2
[ 9369.216013] btusb 3-2:1.0: no reset_resume for driver btusb?
[ 9369.216018] btusb 3-2:1.1: no reset_resume for driver btusb?
[ 9369.216341] ata4.00: configured for UDMA/33
[ 9369.304096] usb 7-2: reset full speed USB device using uhci_hcd and address 3
[ 9369.513976] usb 7-1.2: reset full speed USB device using uhci_hcd and
address 4
[ 9369.620975] usbfs 7-1.2:1.0: no reset_resume for driver usbfs?
[ 9371.188263] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 9371.195573] ata1.00: configured for UDMA/100
[ 9371.205301] dell-wmi: Unknown key e044 pressed
[ 9371.356279] PM: resume of devices complete after 2937.594 msecs
[ 9371.356773] PM: Finishing wakeup.
[ 9371.356775] Restarting tasks ...
[ 9371.358520] usb 7-1.2: usbfs: process 2398 (pcscd) did not claim interface 0
before use
[ 9371.373314] done.
[ 9371.373321] video LNXVIDEO:01: Restoring backlight state
[ 9371.422636] composite sync not supported
[ 9373.495513] cfg80211: Calling CRDA to update world regulatory domain
[ 9373.529139] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection
driver for Linux, in-tree:s
[ 9373.529142] iwl3945: Copyright(c) 2003-2010 Intel Corporation
[ 9373.529227] iwl3945 :0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 9373.529247] iwl3945 :0c:00.0: setting latency timer to 64
[ 9373.582914] iwl3945 :0c:00.0: Tunable channels: 13 802.11bg, 23 802.11a
channels
[ 9373.582918] iwl3945 :0c:00.0: Detected Intel Wireless WiFi Link 3945ABG
[ 9373.583065] iwl3945 :0c:00.0: irq 44 for MSI/MSI-X
[ 9373.583423] ieee80211 phy0: Selected rate control algorithm 'iwl-3945-rs'
[ 9373.825978] btusb_intr_complete: hci0 urb 880024a65f00 failed to
resubmit (1)
[ 9373.826961] btusb_bulk_complete: hci0 urb 880028678f00 failed to
resubmit (1)
[ 9373.827958] btusb_bulk_complete: hci0 urb 880024a659c0 failed to
resubmit (1)
[ 9376.485210] iwl3945 :0c:00.0: loaded firmware version 15.32.2.9
[ 9376.556528] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 9379.591638] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 9379.776553] tg3 :09:00.0: PME# enabled
[ 9379.776575] pci :00:1c.5: wake-up capability enabled by ACPI
[ 9379.801342] pci :00:1c.5: wake-up capability disabled by ACPI
[ 9379.801398] tg3 :09:00.0: PME# disabled
[ 9379.816484] tg3 :09:00.0: irq 42 for MSI/MSI-X
[ 9379.852578] ADDRCONF(NETDEV_UP): eth0: link is not re
Bug#607534: linux-image-2.6.32-5-xen-686: crash upon calling 'startx'
Hi, On Mon, 20.12.2010 at 12:42:50 +, Ian Campbell wrote: > Squeeze is frozen so there is no chance of moving to 2.6.36 for that, if > that was your question. thanks, but that wasn't the question. The question was rather, whether I should be looking at an appropriate backport. > The patches are not in 2.6.37-rc so 2.6.36 isn't helpful for a private > kernel build either. I suppose the patches are likely to land in 2.6.38. Ok, I'll have an eye on that. > Quality Control, n.: > The process of testing one out of every 1,000 units coming off > a production line to make sure that at least one out of 100 works. ;) Kind regards, --Toni++ -- 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/20101220181739.7426.qm...@oak.oeko.net
Bug#604096: Bug#601341: Bug#602418: #601341, #602418 and #604096 seem to be duplicates
> Then I got to eba164ec7e69 "radeon/nouveau/ttm/AGP: Use dma_addr if TTM > has set it." which complained: > CC [M] drivers/gpu/drm/ttm/ttm_agp_backend.o > drivers/gpu/drm/ttm/ttm_agp_backend.c: In function ‘ttm_agp_populate’: > drivers/gpu/drm/ttm/ttm_agp_backend.c:66: error: ‘struct agp_memory’ > has no member named ‘dma_addr’ > and indeed the field is missing both in 2.6.32+drm33 and Linus' tree. Do > I need to cherry pick something from another series or is this commit You can drop that patch. I've rebased the tree to: devel/ttm.pci-api-v2 which is exactly like the older except missing that patch. > something which should be ignored per our previous discussion about PCIe > vs AGP etc? (I'm going with the second option for now) Yup. > > I'll publish my backport in a git tree once I'm happy with it, I need to > tidy it up and correct the cherry-picked from comments etc and then > actually build something which uses it. I'll make Debian packages > available for wider testing once I've done that (with Xmas coming up I > don't know when that will actually be). > > Did the series make any waves upstream? What are the chances that it > will go upstream in something roughly like its current form? I hope so. I am putting the polishing touches on item c) to have it ready for upstream. -- 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/20101220164224.ga15...@dumpdata.com
Re: [PATCH v4] kbuild, deb-pkg: support overriding userland architecture
On Sun, Dec 12, 2010 at 05:39:40PM +, Asbjoern Sloth Toennesen wrote: > Usefull if building for sparc64 userland, because the > sparc and sparc64 userlands use the same 64-bit kernel, > making it impossible to always select the correct userland > architecture for the resulting debian package. > > Might also be usefull, if you want a i386 userland with a amd64 kernel. > > Example usage: > make KBUILD_DEBARCH=i386 deb-pkg > > LKML-reference: > Signed-off-by: Asbjoern Sloth Toennesen > Reviewed-by: WANG Cong > Acked-by: maximilian attems Applied to kbuild-2.6.git#packaging, thanks. Michal -- 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/20101220155356.ge20...@sepie.suse.cz
Re: [PATCHv3] Kbuild: kconfig: Verbose version of --listnewconfig
On 20.12.2010 16:23, Arnaud Lacombe wrote: > Hi, > > On Mon, Dec 20, 2010 at 9:32 AM, Michal Marek wrote: >> On 6.12.2010 01:50, Ben Hutchings wrote: >>> If the KCONFIG_VERBOSE environment variable is set, show the default >>> values of new symbols and not just their names. >>> >>> Based on work by Bastian Blank and >>> maximilian attems . Simplified by Michal Marek >>> . >>> >>> Signed-off-by: Ben Hutchings >>> --- >>> I believe this incorporates all the comments made on v2. >> >> Thanks, applied to kbuild-2.6.git#kconfig. >> > Did you look at the factorization and abstraction of I proposed ? Not yet. OK, I'll have a look at it now and decide what to do. I haven't pushed out the kbuild tree yet. Michal -- 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/4d0f76bc.3040...@suse.cz
Re: [PATCHv3] Kbuild: kconfig: Verbose version of --listnewconfig
Hi, On Mon, Dec 20, 2010 at 9:32 AM, Michal Marek wrote: > On 6.12.2010 01:50, Ben Hutchings wrote: >> If the KCONFIG_VERBOSE environment variable is set, show the default >> values of new symbols and not just their names. >> >> Based on work by Bastian Blank and >> maximilian attems . Simplified by Michal Marek >> . >> >> Signed-off-by: Ben Hutchings >> --- >> I believe this incorporates all the comments made on v2. > > Thanks, applied to kbuild-2.6.git#kconfig. > Did you look at the factorization and abstraction of I proposed ? - Arnaud -- 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/aanlktikwdbwj94lkchtkfhdg6z_sz7ijnbb_sawwj...@mail.gmail.com
Bug#604096: Bug#601341: Bug#602418: #601341, #602418 and #604096 seem to be duplicates
Hi Konrad, On Tue, 2010-12-07 at 11:47 -0500, Konrad Rzeszutek Wilk wrote: > On Tue, Dec 07, 2010 at 11:49:14AM +, Ian Campbell wrote: > > Is the series at https://lkml.org/lkml/2010/12/6/516 sufficient in its > > own right to make Nouveau and ATI work or is more needed? What about NV? > > Both Nouveau and ATI (PCIe) look to work. I did light testing (ATI ES1000, > Radeon 3450, Nvidia 65.. something) and will need to do some more > aggressive ones. Oh, and Intel GTT seems to work without any of these > patches - but I've only tested it on a machine with 4GB so I need to add > more memory to make sure. I decided to try backporting this series to the 2.6.32 + DRM form 2.6.33 tree which is used in Squeeze (maintained in git://git.kernel.org/pub/scm/linux/kernel/git/smb/linux-2.6.32.y-drm33.z.git). This was reasonably non-trivial for the first few commits in the series because 1403b1a38e8b "drm/ttm: add pool wc/uc page allocator V3" is not present in this tree but I think I managed to do the right thing (I might run the patch by you once I've run it up on my machine, if that's ok with you) Then I got to eba164ec7e69 "radeon/nouveau/ttm/AGP: Use dma_addr if TTM has set it." which complained: CC [M] drivers/gpu/drm/ttm/ttm_agp_backend.o drivers/gpu/drm/ttm/ttm_agp_backend.c: In function ‘ttm_agp_populate’: drivers/gpu/drm/ttm/ttm_agp_backend.c:66: error: ‘struct agp_memory’ has no member named ‘dma_addr’ and indeed the field is missing both in 2.6.32+drm33 and Linus' tree. Do I need to cherry pick something from another series or is this commit something which should be ignored per our previous discussion about PCIe vs AGP etc? (I'm going with the second option for now) I'll publish my backport in a git tree once I'm happy with it, I need to tidy it up and correct the cherry-picked from comments etc and then actually build something which uses it. I'll make Debian packages available for wider testing once I've done that (with Xmas coming up I don't know when that will actually be). Did the series make any waves upstream? What are the chances that it will go upstream in something roughly like its current form? Thanks, Ian. -- Ian Campbell Current Noise: Angelcorpse - Reap The Whirlwind Collaboration, n.: A literary partnership based on the false assumption that the other fellow can spell. -- 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/1292858748.4500.284.ca...@zakaz.uk.xensource.com
Re: [PATCHv3] Kbuild: kconfig: Verbose version of --listnewconfig
On 6.12.2010 01:50, Ben Hutchings wrote: > If the KCONFIG_VERBOSE environment variable is set, show the default > values of new symbols and not just their names. > > Based on work by Bastian Blank and > maximilian attems . Simplified by Michal Marek > . > > Signed-off-by: Ben Hutchings > --- > I believe this incorporates all the comments made on v2. Thanks, applied to kbuild-2.6.git#kconfig. Michal -- 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/4d0f68ef.8080...@suse.cz
Bug#607634: linux-image-2.6.32-5-xen-amd64: task blocked for 120s in xen_force_evtchn_callback
On Mon, Dec 20, 2010 at 02:02:51PM +0100, Rik Theys wrote: > I get task blocked for 120s errors (see below). Upgrade dpkg to something newer. 1.15.8.6 or 1.15.8.7. Bastian -- Too much of anything, even love, isn't necessarily a good thing. -- Kirk, "The Trouble with Tribbles", stardate 4525.6 -- 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/20101220141956.ga7...@wavehammer.waldi.eu.org
Bug#606237: linux-kernel: poweroff-button fails on 2.6.32-5-openvz-686
Hi I suspect that the problem is in the openvz patch for the kernel. My suspicion is that the poweroff button signal goes to vzeventd while it should not do that for VE0. So the next step is to check the kernel code. I have forwarded your issue to upstream, but I have not seen any solution yet. But this is only a suspicion. // Ola Quoting "Richard Landsman - Rimote Media" : Hello Ola, After starting vzeventd manually the cat /sys/module/vzevent/parameters/reboot_event has a value of 1 and the kernel module is loaded: testa:~# lsmod | grep vz vzevent 1223 1 vzethdev5593 0 vzrst 108962 0 vzcpt 93505 0 vzdquota 30157 0 [permanent] vzmon 12949 3 vzethdev,vzrst,vzcpt vzdev 1284 3 vzethdev,vzdquota,vzmon I have developed a small formfactor RAID/Samba/VPN/LVM-snapshot/Rdiff-backup/NX-server system for clients and it runs nicely. But would be nice if clients could take down there server with the poweroff-button if they go on vacation. Any idea where to look further for a solution? Many thanks for your help. Richard Op 18-12-2010 11:52, Ola Lundqvist schreef: Hi Richard On Fri, Dec 17, 2010 at 11:26:41PM +0100, Richard Landsman - Rimote Media wrote: Hello Ola, Both commands work like expected. Nothing special. Although the vzeventd is new for me. vzeventd is new in latest kernel and latest vzctl. It is a new (improved) way for a VE to restart itself. Stopping OpenVZ: ..done Starting OpenVZ: ..done Checking vzevent kernel module .done Starting vzeventd: Started Ok. And what was the kernel modules after that? You should have this module loaded "vzevent". You should also have the value 1 in /sys/module/vzevent/parameters/reboot_event. But actually I do not think the power button should use vzevent but I just want to check that things are working as expected anyway. Just to know sure, the powerbutton normally should work on almost any kernel? Is that correct? Yes. // Ola Best regards, Richard Op 17-12-2010 16:21, Ola Lundqvist schreef: /etc/init.d/vzeventd start -- --- Inguza Technology AB --- MSc in Information Technology / o...@inguza.comAnnebergsslingan 37\ | o...@debian.org 654 65 KARLSTAD| | http://inguza.com/Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --- -- 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/20101220134836.19675wihhj5z5...@webmail.inguza.net
Bug#607534: linux-image-2.6.32-5-xen-686: crash upon calling 'startx'
On Mon, 2010-12-20 at 12:55 +0100, Toni Mueller wrote: > > Patches which resolve the issue have been posted upstream, but I don't > > know if the maintainer accepted them yet. The patches also need a > > non-trivial amount of backport to the kernel to be used in Squeeze. > > Hmmm. Would it be reasonable to switch to eg. 2.6.36 or higher? Squeeze is frozen so there is no chance of moving to 2.6.36 for that, if that was your question. The patches are not in 2.6.37-rc so 2.6.36 isn't helpful for a private kernel build either. I suppose the patches are likely to land in 2.6.38. Ian. -- Ian Campbell Current Noise: Raven - All For One Quality Control, n.: The process of testing one out of every 1,000 units coming off a production line to make sure that at least one out of 100 works. -- 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/1292848970.4500.79.ca...@zakaz.uk.xensource.com
initramfs-tools_0.98.7_amd64.changes ACCEPTED into unstable
Accepted: initramfs-tools_0.98.7.dsc to main/i/initramfs-tools/initramfs-tools_0.98.7.dsc initramfs-tools_0.98.7.tar.gz to main/i/initramfs-tools/initramfs-tools_0.98.7.tar.gz initramfs-tools_0.98.7_all.deb to main/i/initramfs-tools/initramfs-tools_0.98.7_all.deb Override entries for your package: initramfs-tools_0.98.7.dsc - source utils initramfs-tools_0.98.7_all.deb - optional utils Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 605824 607509 Thank you for your contribution to Debian. -- 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/e1puefp-0007id...@franck.debian.org
Bug#607631: unblock: initramfs-tools/0.98.7
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package initramfs-tools It contains 2 fixes for specific MODULES=dep root initramfs generation: * AOE device root=/dev/etherd/e0.1p1 * partitioned md raid root=/dev/md1p3 While not beeing critical both fixes are important as there are several usecases for MODULES=dep. The diff is minimal and doesn't affect other pathes: debian/changelog | 11 +++ hook-functions |8 2 files changed, 19 insertions(+), 0 deletions(-) unblock initramfs-tools/0.98.7 thanks -- maks -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.37-rc5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (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/20101220122359.17237.5809.report...@dual.itp.tuwien.ac.at
Bug#605824: marked as done (initramfs-tools: mkinitramfs fails to derrive root block device on partitioned MD RAID (/dev/md1p3 -> /sys/block/md1/md1p3))
Your message dated Mon, 20 Dec 2010 12:17:05 + with message-id and subject line Bug#605824: fixed in initramfs-tools 0.98.7 has caused the Debian Bug report #605824, regarding initramfs-tools: mkinitramfs fails to derrive root block device on partitioned MD RAID (/dev/md1p3 -> /sys/block/md1/md1p3) 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.) -- 605824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: initramfs-tools Version: 0.98.5 Severity: important I've moved fresh squeeze installation onto RAID setup (md0: unpartitioned RAID1 with /boot; md1: partitioned RAID10f2 with root fs on /dev/md1p3). After that, mkinitramfs is no longer able to correctly derrive /sys/block/... path for root. sh -x /usr/sbin/mkinitramfs output attached. # sh -x /usr/sbin/mkinitramfs -o /tmp/foo -v + umask 0022 + export PATH=/usr/bin:/sbin:/bin + keep=n + CONFDIR=/etc/initramfs-tools + verbose=n + test -e /bin/busybox + BUSYBOXDIR=/bin + test -e /usr/lib/initramfs-tools/bin/busybox + export BUSYBOXDIR + getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- -o /tmp/foo -v + OPTIONS= -o '/tmp/foo' -v -- + [ 0 != 0 ] + eval set -- -o '/tmp/foo' -v -- + set -- -o /tmp/foo -v -- + true + outfile=/tmp/foo + shift 2 + true + verbose=y + shift + true + shift + break + . /usr/share/initramfs-tools/scripts/functions + . /usr/share/initramfs-tools/hook-functions + . /etc/initramfs-tools/initramfs.conf + MODULES=most + BUSYBOX=y + KEYMAP=n + COMPRESS=gzip + BOOT=local + DEVICE= + NFSROOT=auto + EXTRA_CONF= + [ -e /usr/share/initramfs-tools/conf.d/* ] + [ -e /etc/initramfs-tools/conf.d/driver-policy ] + basename /etc/initramfs-tools/conf.d/driver-policy + grep ^[[:alnum:]][[:alnum:]\._-]*$ + grep -v \.dpkg-.*$ + EXTRA_CONF= driver-policy + [ -e /etc/initramfs-tools/conf.d/resume ] + basename /etc/initramfs-tools/conf.d/resume + grep ^[[:alnum:]][[:alnum:]\._-]*$ + grep -v \.dpkg-.*$ + EXTRA_CONF= driver-policy resume + [ -e /etc/initramfs-tools/conf.d/driver-policy ] + . /etc/initramfs-tools/conf.d/driver-policy + MODULES=dep + [ -e /etc/initramfs-tools/conf.d/resume ] + . /etc/initramfs-tools/conf.d/resume + RESUME=UUID=027b8648-cfed-41f1-bc02-6b1356edb022 + [ -e /usr/share/initramfs-tools/conf-hooks.d/* ] + [ -n ] + [ -z /tmp/foo ] + touch /tmp/foo + readlink -f /tmp/foo + outfile=/tmp/foo + [ 0 -ne 1 ] + uname -r + version=2.6.32-5-amd64 + check_minkver 2.6.32-5-amd64 + local curversion initdir DPKG_ARCH minversion cm_x tmp + curversion=2.6.32-5-amd64 + initdir= + [ -z ] + minversion=2.6.12 + dpkg --compare-versions 2.6.32-5-amd64 lt 2.6.12 + return 0 + check_minkver 2.6.32-5-amd64 /usr/share/initramfs-tools/hooks + local curversion initdir DPKG_ARCH minversion cm_x tmp + curversion=2.6.32-5-amd64 + initdir=/usr/share/initramfs-tools/hooks + [ -z /usr/share/initramfs-tools/hooks ] + set_initlist + unset initlist + [ /usr/share/initramfs-tools/hooks/busybox = /usr/share/initramfs-tools/hooks/* ] + [ ! -x /usr/share/initramfs-tools/hooks/busybox ] + [ -d /usr/share/initramfs-tools/hooks/busybox ] + sh -n /usr/share/initramfs-tools/hooks/busybox + initlist= busybox + [ /usr/share/initramfs-tools/hooks/dmsetup = /usr/share/initramfs-tools/hooks/* ] + [ ! -x /usr/share/initramfs-tools/hooks/dmsetup ] + [ -d /usr/share/initramfs-tools/hooks/dmsetup ] + sh -n /usr/share/initramfs-tools/hooks/dmsetup + initlist= busybox dmsetup + [ /usr/share/initramfs-tools/hooks/keymap = /usr/share/initramfs-tools/hooks/* ] + [ ! -x /usr/share/initramfs-tools/hooks/keymap ] + [ -d /usr/share/initramfs-tools/hooks/keymap ] + sh -n /usr/share/initramfs-tools/hooks/keymap + initlist= busybox dmsetup keymap + [ /usr/share/initramfs-tools/hooks/klibc = /usr/share/initramfs-tools/hooks/* ] + [ ! -x /usr/share/initramfs-tools/hooks/klibc ] + [ -d /usr/share/initramfs-tools/hooks/klibc ] + sh -n /usr/share/initramfs-tools/hooks/klibc + initlist= busybox dmsetup keymap klibc + [ /usr/share/initramfs-tools/hooks/mdadm = /usr/share/initramfs-tools/hooks/* ] + [ ! -x /usr/share/initramfs-tools/hooks/mdadm ] + [ -d /usr/share/initramfs-tools/hooks/mdadm ] + sh -n /usr/share/initramfs-tools/hooks/mdadm + initlist= busybox dmsetup keymap klibc mdadm + [ /usr/share/initramfs-tools/hooks/thermal = /usr/share/initramfs-tools/hooks/* ] + [ ! -x /usr/share/initramfs-tools/hooks/thermal ] + [ -d /usr/share/initramfs-tools/hooks/thermal ] + sh -n /usr/share/initramfs-tools/hooks/thermal + initlist= busybox dmsetup keymap klibc mdadm thermal + [ /usr/share/initramfs-tools/hooks/udev
Bug#607509: marked as done (initramfs-tools: Does not work if root is on an AOE device)
Your message dated Mon, 20 Dec 2010 12:17:05 +
with message-id
and subject line Bug#607509: fixed in initramfs-tools 0.98.7
has caused the Debian Bug report #607509,
regarding initramfs-tools: Does not work if root is on an AOE device
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.)
--
607509: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607509
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.98.6
Severity: important
-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 2.2M Dec 19 09:50 /boot/initrd.img-2.6.32-5-kirkwood
-- /proc/cmdline
console=ttyS0,115200 root=/dev/etherd/e0.1p1
-- resume
RESUME=UUID=501b84a0-eb7b-464d-895a-23e666058aa1
-- /proc/filesystems
ext3
ext2
-- lsmod
Module Size Used by
ipv6 253826 26
nfsd 247720 2
exportfs3000 1 nfsd
nfs 270232 0
lockd 63145 2 nfsd,nfs
fscache34105 1 nfs
nfs_acl 2277 2 nfsd,nfs
auth_rpcgss33318 2 nfsd,nfs
sunrpc171068 6 nfsd,nfs,lockd,nfs_acl,auth_rpcgss
ext2 55411 1
loop 11419 0
mmc_block 7658 2
ehci_hcd 35579 0
hmac2475 0
usbcore 122183 2 ehci_hcd
sha1_generic1717 0
mvsdio 5318 0
mv_cesa 9262 0
nls_base5367 1 usbcore
mmc_core 50206 2 mmc_block,mvsdio
aes_generic32820 1 mv_cesa
ext3 110992 1
jbd37434 1 ext3
mbcache 4860 2 ext2,ext3
aoe21063 3
mv643xx_eth22562 0
libphy 14836 1 mv643xx_eth
inet_lro5060 1 mv643xx_eth
-- /etc/initramfs-tools/modules
-- /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
do_initrd = yes
link_in_boot = yes
-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
KEYMAP=n
COMPRESS=gzip
BOOT=local
DEVICE=
NFSROOT=auto
-- /etc/initramfs-tools/update-initramfs.conf
update_initramfs=yes
backup_initramfs=no
-- mkinitramfs hooks
/etc/initramfs-tools/hooks/:
aoetools
/usr/share/initramfs-tools/hooks:
busybox
flash_kernel_set_root
keymap
klibc
thermal
udev
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: armel (armv5tel)
Kernel: Linux 2.6.32-5-kirkwood
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages initramfs-tools depends on:
ii cpio 2.11-4 GNU cpio -- a program to manage ar
ii findutils 4.4.2-1+b1 utilities for finding files--find,
ii klibc-utils 1.5.20-1 small utilities built with klibc f
ii module-init-tools 3.12-1 tools for managing Linux kernel mo
ii udev 164-3 /dev/ and hotplug management daemo
Versions of packages initramfs-tools recommends:
ii busybox 1:1.17.1-8 Tiny utilities for small and embed
Versions of packages initramfs-tools suggests:
ii bash-completion 1:1.2-3programmable completion for the ba
-- no debconf information
Problem Description:
r...@squeezeserver:/usr/share/initramfs-tools# mkinitramfs -o /tmp/foo
mkinitramfs: for root /dev/etherd/e0.1p1 missing etherd/e /sys/block/ entry
mkinitramfs: workaround is MODULES=most
mkinitramfs: Error please report the bug
Fix:
--- /usr/share/initramfs-tools/hook-functions_orig 2010-12-19
10:24:44.0 +0100
+++ /usr/share/initramfs-tools/hook-functions 2010-12-19 09:50:16.0
+0100
@@ -338,6 +338,10 @@
block="rd!c${root#/dev/rd/c}"
block=${block%%p[0-9]*}
# etherd device
+elif [ "${root#/dev/etherd/}" != "${root}" ]; then
+block=${root#/dev/etherd/*}
+block="etherd!${block%p*}"
+
# classical root device
else
block=${root#/dev/}
--- End Message ---
--- Begin Message ---
Source: initramfs-tools
Source-Version: 0.98.7
We believe that the bug you reported is fixed in the latest version of
initramfs-tools, which is due to be installed in the Debian FTP archive:
initramfs-tools_0.98.7.dsc
to main/i/initramfs-tools/initramfs-tools_0.98.7.dsc
initramfs-tools_0.98.7.tar
Processing of initramfs-tools_0.98.7_amd64.changes
initramfs-tools_0.98.7_amd64.changes uploaded successfully to localhost along with the files: initramfs-tools_0.98.7.dsc initramfs-tools_0.98.7.tar.gz initramfs-tools_0.98.7_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- 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/e1puetc-0006jv...@franck.debian.org
Bug#607534: linux-image-2.6.32-5-xen-686: crash upon calling 'startx'
Hi Ian, On Mon, 20.12.2010 at 10:38:46 +, Ian Campbell wrote: > This is likely the same underlying issue as 601341 and friends, which is > that the Xen dom0 kernel does not currently fully support DRI/DRM > graphics. thanks for the heads-up. Uhhh... > Patches which resolve the issue have been posted upstream, but I don't > know if the maintainer accepted them yet. The patches also need a > non-trivial amount of backport to the kernel to be used in Squeeze. Hmmm. Would it be reasonable to switch to eg. 2.6.36 or higher? > > The problem appears to occur only with the entry in grub.cfg that I > > marked below, but I only tried the first and the marked entry > > (...XEN 4.0"): > > That is the only entry which would result in you running under Xen so > this is not surprising. Ok. Thank you for the explanation. Kind regards, --Toni++ -- 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/20101220115557.10910.qm...@oak.oeko.net
Bug#607534: linux-image-2.6.32-5-xen-686: crash upon calling 'startx'
On Sun, 2010-12-19 at 16:33 +0100, Toni Mueller wrote: > I wanted to start the GUI, but couldn't. After logging in, I usually say > 'startx'. For this computer, which I have just installed, the command > resulted in the screen going blank, immediately followed by a hard reboot. This is likely the same underlying issue as 601341 and friends, which is that the Xen dom0 kernel does not currently fully support DRI/DRM graphics. Patches which resolve the issue have been posted upstream, but I don't know if the maintainer accepted them yet. The patches also need a non-trivial amount of backport to the kernel to be used in Squeeze. > The problem appears to occur only with the entry in grub.cfg that I > marked below, but I only tried the first and the marked entry > (...XEN 4.0"): That is the only entry which would result in you running under Xen so this is not surprising. Ian. -- Ian Campbell Current Noise: Raven - Hard Ride Another such victory over the Romans, and we are undone. -- Pyrrhus -- 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/1292841526.4500.74.ca...@zakaz.uk.xensource.com
Processed: tagging 580507
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny7 > tags 580507 + pending Bug #580507 [linux-2.6] linux-image-2.6.32-5-openvz-amd64: CONFIG_NF_CONNTRACK_IPV6 is not set Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 580507: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580507 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.12928409986089.transcr...@bugs.debian.org
Bug#607617: src:linux-latest-2.6: no linux-headers-2.6-all package
Package: src:linux-latest-2.6 Version: 2.6.32+28 Severity: wishlist linux-2.6 provides a (versioned) linux-headers-2.6.32-5-all package. It would be nice if the current version of this package was available as linux-headers-2.6-all as well, similar to the other linux-headers-2.6-* packages. Regards, Ansgar -- 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/20101220102148.2219.94217.report...@pc-kmaurisc.mathi.uni-heidelberg.de
