Bug#783620: initramfs-tools: initramfs broken on first boot into Jessie, "Unable to mount root fs on unknown-block(0, 0)"
Package: initramfs-tools Followup-For: Bug #783620 Hi, from the debian-user mailinglist ... Bernhard Schmidt wrote: > Don Armstrong wrote: > > > > > > Hi Don, > > > > > >>> has anyone observed something similar to >>> >>> >>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783620 on their >>> >>> >>> Upgrade from Wheezy to Jessie? I'm still trying to figure out what's >>> >>> >>> happening, and I don't really know where to look. >>> >>> >>> >>> >>> >>> I was unable to attach the screenshot so far (mail is accepted but >>> >>> >>> never makes it to the BTS), I've put the screenshot here: >>> >>> >>> >>> >>> >>> http://users.birkenwald.de/~berni/volatile/783620.png >>> >>> >> >> >> >> Could you run something like this on the initrds? >> >> >> >> >> >> diff -u <( zcat workinginitrd) <( zcat brokeninitrd); >> >> >> >> >> >> It's possible that something has corrupted the initrds in some subtle >> >> >> way, or some part of the cpio archive has been truncated which causes as >> >> >> issue for the kernel but is ignored by cpio. >> >> >
Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks
On Apr 28, 2015, at 8:02 PM, Fabio Estevam wrote: > On Fri, Apr 10, 2015 at 9:08 PM, Ben Hutchings wrote: > >>> Whenever I reset my cubox-i4Pro by disconnecting the power plug, the >>> hardware real-time-clock gets >>> reset to midnight UTC, Dec 31, 1970. >>> Even though the SolidRun literature says that the i4Pro has a battery >>> backed RTC. > >> If this RTC is not battery backed, it seems like it ought to be disabled >> in this board's device tree. > > Agreed. Just sent a patch for this. > >>> # CONFIG_RTC_DRV_PCF8523 is not set >>> >>> and >>> >>> CONFIG_RTC_DRV_SNVS=y > > And also a patch for turning on this option as well. > > Regards, > > Fabio Estevam I don’t know if this makes any difference, but please remember that this box comes in several flavors. Only the i4pro flavor has the battery-backed clock turned on in the hardware. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/74d54565-f9ae-4be5-b48d-ffc8903ce...@pobox.com
Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks
On Apr 28, 2015, at 8:02 PM, Fabio Estevam wrote: > On Fri, Apr 10, 2015 at 9:08 PM, Ben Hutchings wrote: > >>> Whenever I reset my cubox-i4Pro by disconnecting the power plug, the >>> hardware real-time-clock gets >>> reset to midnight UTC, Dec 31, 1970. >>> Even though the SolidRun literature says that the i4Pro has a battery >>> backed RTC. > >> If this RTC is not battery backed, it seems like it ought to be disabled >> in this board's device tree. > > Agreed. Just sent a patch for this. > >>> # CONFIG_RTC_DRV_PCF8523 is not set >>> >>> and >>> >>> CONFIG_RTC_DRV_SNVS=y > > And also a patch for turning on this option as well. > > Regards, > > Fabio Estevam Cool… Thanks! Any idea when we’ll see it in the kernel from Sid/Unstable repo’s? Rick -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/b77ed00a-c66e-4ed8-b10d-6b5e8a885...@pobox.com
Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks
On Fri, Apr 10, 2015 at 9:08 PM, Ben Hutchings wrote: >> Whenever I reset my cubox-i4Pro by disconnecting the power plug, the >> hardware real-time-clock gets >> reset to midnight UTC, Dec 31, 1970. >> Even though the SolidRun literature says that the i4Pro has a battery backed >> RTC. > If this RTC is not battery backed, it seems like it ought to be disabled > in this board's device tree. Agreed. Just sent a patch for this. >> # CONFIG_RTC_DRV_PCF8523 is not set >> >> and >> >> CONFIG_RTC_DRV_SNVS=y And also a patch for turning on this option as well. Regards, Fabio Estevam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAOMZO5BrWbxarSEEC52Kb7=qr4k2e1qyammz3rx+nq9r1vb...@mail.gmail.com
Bug#783620: initramfs-tools: initramfs broken on first boot into Jessie, "Unable to mount root fs on unknown-block(0, 0)"
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Ben, On 28.04.2015 22:01, Ben Hutchings wrote: > On Tue, 2015-04-28 at 21:39 +0200, Bernhard Schmidt wrote: >> Hi, >> >> I have tried two times to send the screenshot to this bug, but it >> was always eaten (delivered to @bugs.debian.org, but never made >> it to the BTS). I have put it online at >> http://users.birkenwald.de/~berni/volatile/783620.png >> >> Note that there is a bit of local integration work in these >> systems (a few additional packages, and the upgrade procedure >> switches from the legacy VMware tools to open-vm-tools), but >> nothing that deep that should affect initramfs. Also 90% of the >> upgrades go through without any issues. >> >> And the initrd content is binary-identical, so ... > > This is a kernel panic, which usually means the initramfs wasn't > loaded at all. > > Which boot loader is used on this system? GRUB or something else? Thanks for the feedback. Standard grub2 installation, nothing special about it. Grub did not print any errors about not finding a file and I only ran update-initramfs and rebooted. I hope the next time it happens it will be with a less critical machine and I can keep it down a bit to debug further. Best Regards, Bernhard -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVP+3cAAoJEHdQeeW4ULyT1g8QAJO1isSoXTkMDDz71UDVqX6A KBSF0itWhgN2EIis4at2GtydGT8agtknRpRi7lOeML0ROPWcPhZkkE5LmoSCx+pV wh4tMvNp8xzR7qINJ2ncCtmeSc/sy44FU4vBxYs/jbZA3xt3QH4YPow2gzMzIU+Z 47ByFCygI+rcu6ZEYVPViD6xTA7LoZ2MulsBr7QPIA/l7iX8uqKH3Qpgq4iRuaD3 Ww+zVN7nOrLCrpfQi0plRrO3wI62HieVeRkvZ10yCS7gFavjXxldu8V5ZVvfU33S Y17IM0zbdl3FSi7lQ2pIwrSC6Yvz9EE1x0qygVk8HYeEEWsgcuu4Xp3TEJ1Y412M ovsX+xREh7YzJP9HUZgX1DToI7Gp+91pBbVP3yEGt71oY16ezysRVlbkzKV2nTKo AZv0euhS+SJHDEPCjEbJj/VvQD/1QrTSKMkuu5Dy+tqcNDIV2DSTfbtuLlGvmtqU /0VIc6mSIYAof80vUKEkgt7MLvy8BamwtSBbB7cGyneJTq2o4uwRcifunjcHbbKn 7KcGtcGNZ0tUHhaK5dPFjLEwyLE75ei1mivE+kDigZgqlCT3SQpsimp7/MHtYYvo yk265JIOW+r6uHwEWFjCNSYJrNX/jPbTpurxb19PnnkY/qhfs4WyD3RRbXt5KmJD n5qaAfislxUubVfEs0tW =lBoI -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/553feddc.4050...@birkenwald.de
Bug#774576: linux-image-3.16.0-4-amd64: SATA errors with non-faulty disks
Had the same SATA error messages after changing OS from Wheezy 32-Bit to Jessie 64-Bit, saw them when copying big (some 100 MBs) files. But the MD5-Sums of copied files where the same as the of the original files, so there seemed to be no real impact. Had the SATA disk (Samsung SSD 830 series) in use for years without problem before. SMART was also looking good. Solution for me was replacing the SATA cable with another one from another producer (saw that solution somewhere on the internet). Just grabbed in the hardware box and took that other cable- the mentioned error messages did not occur anymore. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150428214158.4139e...@koog.heimnetz.zone
Processed: tagging 783620
Processing commands for cont...@bugs.debian.org: > tags 783620 + moreinfo Bug #783620 [initramfs-tools] initramfs-tools: initramfs broken on first boot into Jessie, "Unable to mount root fs on unknown-block(0, 0)" Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 783620: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783620 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: https://lists.debian.org/handler.s.c.14302513214579.transcr...@bugs.debian.org
Bug#783620: initramfs-tools: initramfs broken on first boot into Jessie, "Unable to mount root fs on unknown-block(0, 0)"
On Tue, 2015-04-28 at 21:39 +0200, Bernhard Schmidt wrote: > Hi, > > I have tried two times to send the screenshot to this bug, but it was > always eaten (delivered to @bugs.debian.org, but never made it to the > BTS). I have put it online at > http://users.birkenwald.de/~berni/volatile/783620.png > > Note that there is a bit of local integration work in these systems (a > few additional packages, and the upgrade procedure switches from the > legacy VMware tools to open-vm-tools), but nothing that deep that should > affect initramfs. Also 90% of the upgrades go through without any issues. > > And the initrd content is binary-identical, so ... This is a kernel panic, which usually means the initramfs wasn't loaded at all. Which boot loader is used on this system? GRUB or something else? Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Brandwein signature.asc Description: This is a digitally signed message part
Bug#783620: initramfs-tools: initramfs broken on first boot into Jessie, "Unable to mount root fs on unknown-block(0, 0)"
Hi, I have tried two times to send the screenshot to this bug, but it was always eaten (delivered to @bugs.debian.org, but never made it to the BTS). I have put it online at http://users.birkenwald.de/~berni/volatile/783620.png Note that there is a bit of local integration work in these systems (a few additional packages, and the upgrade procedure switches from the legacy VMware tools to open-vm-tools), but nothing that deep that should affect initramfs. Also 90% of the upgrades go through without any issues. And the initrd content is binary-identical, so ... Best Regards, Bernhard
Bug#783620: initramfs-tools: initramfs broken on first boot into Jessie, "Unable to mount root fs on unknown-block(0, 0)"
> The uncompressed size is the same > > root@lxmhs63:/tmp# zcat /boot/initrd.img-3.16.0-4-amd64.broken > > initrd.img-3.16.0-4-amd64.broken > root@lxmhs63:/tmp# zcat /boot/initrd.img-3.16.0-4-amd64.broken > > /tmp/initrd.img-3.16.0-4-amd64.broken > root@lxmhs63:/tmp# ls -la /tmp/initrd.img-3.16.0-4-amd64* > -rw-r--r-- 1 root root 45304832 Apr 28 14:44 /tmp/initrd.img-3.16.0-4-amd64 > -rw-r--r-- 1 root root 45304832 Apr 28 14:44 > /tmp/initrd.img-3.16.0-4-amd64.broken Err wrong paste zcat /boot/initrd.img-3.16.0-4-amd64.broken > /tmp/initrd.img-3.16.0-4-amd64.broken zcat /boot/initrd.img-3.16.0-4-amd64 > /tmp/initrd.img-3.16.0-4-amd64 Bernhard -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/553f850a.10...@birkenwald.de
Bug#783620: initramfs-tools: initramfs broken on first boot into Jessie, "Unable to mount root fs on unknown-block(0, 0)"
Package: initramfs-tools Version: 0.120 Severity: important Dear Maintainer, I have a hard time wrapping my head around this bug, feel free to assign somewhere else. We have started upgrading some of our production VMs to Jessie. The testsystems worked fine, but I have hit the following bug for the second time on a production VM now. - dist-upgrade works flawlessly - on first boot into Jessie I get an immediate (<1s) kernel-panic (see attached screenshot) about being unable to find the root fs. Unfortunately I'm unable to get the full boot log, since I don't have a serial console there and kernel messages scroll by too fast. - To fix the issue I have to boot into the old Wheezy kernel (3.2.0-4-amd64) in grub and regenerate the initrd for the Jessie kernel # update-initramfs -k 3.16.0-4-amd64 -u Then it works fine. Now comes the interesting part ... I have saved the broken initrd for later analysis The compressed size is marginally different (broken being 3k smaller) -rw-r--r-- 1 root root 14339199 Apr 28 13:59 initrd.img-3.16.0-4-amd64 -rw-r--r-- 1 root root 14338898 Apr 28 13:58 initrd.img-3.16.0-4-amd64.broken The uncompressed size is the same root@lxmhs63:/tmp# zcat /boot/initrd.img-3.16.0-4-amd64.broken > initrd.img-3.16.0-4-amd64.broken root@lxmhs63:/tmp# zcat /boot/initrd.img-3.16.0-4-amd64.broken > /tmp/initrd.img-3.16.0-4-amd64.broken root@lxmhs63:/tmp# ls -la /tmp/initrd.img-3.16.0-4-amd64* -rw-r--r-- 1 root root 45304832 Apr 28 14:44 /tmp/initrd.img-3.16.0-4-amd64 -rw-r--r-- 1 root root 45304832 Apr 28 14:44 /tmp/initrd.img-3.16.0-4-amd64.broken The checksum is different root@lxmhs63:/tmp# md5sum /tmp/initrd.img-3.16.0-4-amd64* 7b24aa901b697dc5dfdbad03bd199072 /tmp/initrd.img-3.16.0-4-amd64 5e467c0a49afa4ddae315cc6e818d7ac /tmp/initrd.img-3.16.0-4-amd64.broken Now comes the puzzling part ... the _content_ of the initrd is exactly the same root@lxmhs63:/tmp# mkdir broken && cd broken && cpio -id < ../initrd.img-3.16.0-4-amd64.broken 88486 blocks root@lxmhs63:/tmp/broken# cd .. root@lxmhs63:/tmp# mkdir ok && cd ok && cpio -id < ../initrd.img-3.16.0-4-amd64 88486 blocks root@lxmhs63:/tmp/ok# cd .. root@lxmhs63:/tmp# diff -urN broken ok I will try to capture a screenlog on the next upgrades, maybe there is something interesting in there. Bernhard -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150428125306.20837.15594.report...@badwlrz-clbsc01.ws.lrz.de
linux_3.16.7-ckt9-3~deb8u1~bpo70+1_multi.changes ACCEPTED into wheezy-backports->backports-policy, wheezy-backports
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 27 Apr 2015 20:13:07 +0100 Source: linux Binary: linux-source-3.16 linux-doc-3.16 linux-manual-3.16 linux-support-3.16.0-0.bpo.4 linux-libc-dev linux-headers-3.16.0-0.bpo.4-all linux-headers-3.16.0-0.bpo.4-all-amd64 kernel-image-3.16.0-0.bpo.4-amd64-di nic-modules-3.16.0-0.bpo.4-amd64-di nic-wireless-modules-3.16.0-0.bpo.4-amd64-di nic-shared-modules-3.16.0-0.bpo.4-amd64-di serial-modules-3.16.0-0.bpo.4-amd64-di usb-serial-modules-3.16.0-0.bpo.4-amd64-di ppp-modules-3.16.0-0.bpo.4-amd64-di pata-modules-3.16.0-0.bpo.4-amd64-di cdrom-core-modules-3.16.0-0.bpo.4-amd64-di firewire-core-modules-3.16.0-0.bpo.4-amd64-di scsi-core-modules-3.16.0-0.bpo.4-amd64-di scsi-modules-3.16.0-0.bpo.4-amd64-di scsi-common-modules-3.16.0-0.bpo.4-amd64-di scsi-extra-modules-3.16.0-0.bpo.4-amd64-di loop-modules-3.16.0-0.bpo.4-amd64-di btrfs-modules-3.16.0-0.bpo.4-amd64-di ext4-modules-3.16.0-0.bpo.4-amd64-di isofs-modules-3.16.0-0.bpo.4-amd64-di jfs-modules-3.16.0-0.bpo.4-amd64-di ntfs-modules-3.16.0-0.bpo.4-amd64-di xfs-modules-3.16.0-0.bpo.4-amd64-di fat-modules-3.16.0-0.bpo.4-amd64-di md-modules-3.16.0-0.bpo.4-amd64-di multipath-modules-3.16.0-0.bpo.4-amd64-di usb-modules-3.16.0-0.bpo.4-amd64-di usb-storage-modules-3.16.0-0.bpo.4-amd64-di pcmcia-storage-modules-3.16.0-0.bpo.4-amd64-di fb-modules-3.16.0-0.bpo.4-amd64-di input-modules-3.16.0-0.bpo.4-amd64-di event-modules-3.16.0-0.bpo.4-amd64-di mouse-modules-3.16.0-0.bpo.4-amd64-di nic-pcmcia-modules-3.16.0-0.bpo.4-amd64-di pcmcia-modules-3.16.0-0.bpo.4-amd64-di nic-usb-modules-3.16.0-0.bpo.4-amd64-di sata-modules-3.16.0-0.bpo.4-amd64-di core-modules-3.16.0-0.bpo.4-amd64-di acpi-modules-3.16.0-0.bpo.4-amd64-di i2c-modules-3.16.0-0.bpo.4-amd64-di crc-modules-3.16.0-0.bpo.4-amd64-di crypto-modules-3.16.0-0.bpo.4-amd64-di crypto-dm-modules-3.16.0-0.bpo.4-amd64-di efi-modules-3.16.0-0.bpo.4-amd64-di ata-modules-3.16.0-0.bpo.4-amd64-di mmc-core-modules-3.16.0-0.bpo.4-amd64-di mmc-modules-3.16.0-0.bpo.4-amd64-di nbd-modules-3.16.0-0.bpo.4-amd64-di squashfs-modules-3.16.0-0.bpo.4-amd64-di speakup-modules-3.16.0-0.bpo.4-amd64-di virtio-modules-3.16.0-0.bpo.4-amd64-di uinput-modules-3.16.0-0.bpo.4-amd64-di sound-modules-3.16.0-0.bpo.4-amd64-di hyperv-modules-3.16.0-0.bpo.4-amd64-di udf-modules-3.16.0-0.bpo.4-amd64-di fuse-modules-3.16.0-0.bpo.4-amd64-di linux-headers-3.16.0-0.bpo.4-common linux-image-3.16.0-0.bpo.4-amd64 linux-headers-3.16.0-0.bpo.4-amd64 linux-image-3.16.0-0.bpo.4-amd64-dbg xen-linux-system-3.16.0-0.bpo.4-amd64 linux-headers-3.16.0-0.bpo.4-all-armel kernel-image-3.16.0-0.bpo.4-kirkwood-di nic-modules-3.16.0-0.bpo.4-kirkwood-di nic-shared-modules-3.16.0-0.bpo.4-kirkwood-di usb-serial-modules-3.16.0-0.bpo.4-kirkwood-di ppp-modules-3.16.0-0.bpo.4-kirkwood-di cdrom-core-modules-3.16.0-0.bpo.4-kirkwood-di scsi-core-modules-3.16.0-0.bpo.4-kirkwood-di loop-modules-3.16.0-0.bpo.4-kirkwood-di btrfs-modules-3.16.0-0.bpo.4-kirkwood-di ext4-modules-3.16.0-0.bpo.4-kirkwood-di isofs-modules-3.16.0-0.bpo.4-kirkwood-di jfs-modules-3.16.0-0.bpo.4-kirkwood-di fat-modules-3.16.0-0.bpo.4-kirkwood-di minix-modules-3.16.0-0.bpo.4-kirkwood-di md-modules-3.16.0-0.bpo.4-kirkwood-di multipath-modules-3.16.0-0.bpo.4-kirkwood-di usb-modules-3.16.0-0.bpo.4-kirkwood-di usb-storage-modules-3.16.0-0.bpo.4-kirkwood-di fb-modules-3.16.0-0.bpo.4-kirkwood-di input-modules-3.16.0-0.bpo.4-kirkwood-di event-modules-3.16.0-0.bpo.4-kirkwood-di mouse-modules-3.16.0-0.bpo.4-kirkwood-di nic-usb-modules-3.16.0-0.bpo.4-kirkwood-di sata-modules-3.16.0-0.bpo.4-kirkwood-di core-modules-3.16.0-0.bpo.4-kirkwood-di crc-modules-3.16.0-0.bpo.4-kirkwood-di crypto-modules-3.16.0-0.bpo.4-kirkwood-di crypto-dm-modules-3.16.0-0.bpo.4-kirkwood-di mmc-modules-3.16.0-0.bpo.4-kirkwood-di nbd-modules-3.16.0-0.bpo.4-kirkwood-di squashfs-modules-3.16.0-0.bpo.4-kirkwood-di uinput-modules-3.16.0-0.bpo.4-kirkwood-di leds-modules-3.16.0-0.bpo.4-kirkwood-di udf-modules-3.16.0-0.bpo.4-kirkwood-di fuse-modules-3.16.0-0.bpo.4-kirkwood-di kernel-image-3.16.0-0.bpo.4-orion5x-di nic-modules-3.16.0-0.bpo.4-orion5x-di nic-shared-modules-3.16.0-0.bpo.4-orion5x-di usb-serial-modules-3.16.0-0.bpo.4-orion5x-di ppp-modules-3.16.0-0.bpo.4-orion5x-di cdrom-core-modules-3.16.0-0.bpo.4-orion5x-di scsi-core-modules-3.16.0-0.bpo.4-orion5x-di loop-modules-3.16.0-0.bpo.4-orion5x-di ipv6-modules-3.16.0-0.bpo.4-orion5x-di btrfs-modules-3.16.0-0.bpo.4-orion5x-di ext4-modules-3.16.0-0.bpo.4-orion5x-di isofs-modules-3.16.0-0.bpo.4-orion5x-di jffs2-modules-3.16.0-0.bpo.4-orion5x-di jfs-modules-3.16.0-0.bpo.4-orion5x-di fat-modules-3.16.0-0.bpo.4-orion5x-di minix-modules-3.16.0-0.bpo.4-orion5x-di md-modules-3.16.0-0.bpo.4-orion5x-di multipath-modules-3.16.0-0.bpo.4-orion5x-di usb-modules-3.16.0-0.bpo.4-orion5x-di usb-storage-modules-3.16.0-0.bpo.4-orion5x-di event-modules-3.16.0-0.bpo.4-orion5x-di nic-u
linux_3.2.68-1+deb7u1~bpo60+1_multi.changes ACCEPTED into squeeze-backports->backports-policy, squeeze-backports
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 27 Apr 2015 18:07:48 +0100 Source: linux Binary: linux-source-3.2 linux-doc-3.2 linux-manual-3.2 linux-support-3.2.0-0.bpo.4 linux-libc-dev linux-headers-3.2.0-0.bpo.4-all linux-headers-3.2.0-0.bpo.4-all-alpha linux-headers-3.2.0-0.bpo.4-common linux-image-3.2.0-0.bpo.4-alpha-generic linux-headers-3.2.0-0.bpo.4-alpha-generic linux-image-3.2.0-0.bpo.4-alpha-smp linux-headers-3.2.0-0.bpo.4-alpha-smp linux-image-3.2.0-0.bpo.4-alpha-legacy linux-headers-3.2.0-0.bpo.4-alpha-legacy linux-headers-3.2.0-0.bpo.4-all-amd64 linux-image-3.2.0-0.bpo.4-amd64 linux-headers-3.2.0-0.bpo.4-amd64 linux-image-3.2.0-0.bpo.4-amd64-dbg xen-linux-system-3.2.0-0.bpo.4-amd64 linux-headers-3.2.0-0.bpo.4-common-rt linux-image-3.2.0-0.bpo.4-rt-amd64 linux-headers-3.2.0-0.bpo.4-rt-amd64 linux-image-3.2.0-0.bpo.4-rt-amd64-dbg linux-headers-3.2.0-0.bpo.4-all-armel linux-image-3.2.0-0.bpo.4-iop32x linux-headers-3.2.0-0.bpo.4-iop32x linux-image-3.2.0-0.bpo.4-ixp4xx linux-headers-3.2.0-0.bpo.4-ixp4xx linux-image-3.2.0-0.bpo.4-kirkwood linux-headers-3.2.0-0.bpo.4-kirkwood linux-image-3.2.0-0.bpo.4-mv78xx0 linux-headers-3.2.0-0.bpo.4-mv78xx0 linux-image-3.2.0-0.bpo.4-orion5x linux-headers-3.2.0-0.bpo.4-orion5x linux-image-3.2.0-0.bpo.4-versatile linux-headers-3.2.0-0.bpo.4-versatile linux-headers-3.2.0-0.bpo.4-all-armhf linux-image-3.2.0-0.bpo.4-mx5 linux-headers-3.2.0-0.bpo.4-mx5 linux-image-3.2.0-0.bpo.4-omap linux-headers-3.2.0-0.bpo.4-omap linux-image-3.2.0-0.bpo.4-vexpress linux-headers-3.2.0-0.bpo.4-vexpress linux-headers-3.2.0-0.bpo.4-all-hppa linux-image-3.2.0-0.bpo.4-parisc linux-headers-3.2.0-0.bpo.4-parisc linux-image-3.2.0-0.bpo.4-parisc-smp linux-headers-3.2.0-0.bpo.4-parisc-smp linux-image-3.2.0-0.bpo.4-parisc64 linux-headers-3.2.0-0.bpo.4-parisc64 linux-image-3.2.0-0.bpo.4-parisc64-smp linux-headers-3.2.0-0.bpo.4-parisc64-smp linux-headers-3.2.0-0.bpo.4-all-i386 linux-image-3.2.0-0.bpo.4-486 linux-headers-3.2.0-0.bpo.4-486 linux-image-3.2.0-0.bpo.4-686-pae linux-headers-3.2.0-0.bpo.4-686-pae linux-image-3.2.0-0.bpo.4-686-pae-dbg xen-linux-system-3.2.0-0.bpo.4-686-pae linux-image-3.2.0-0.bpo.4-rt-686-pae linux-headers-3.2.0-0.bpo.4-rt-686-pae linux-image-3.2.0-0.bpo.4-rt-686-pae-dbg linux-headers-3.2.0-0.bpo.4-all-ia64 linux-image-3.2.0-0.bpo.4-itanium linux-headers-3.2.0-0.bpo.4-itanium linux-image-3.2.0-0.bpo.4-mckinley linux-headers-3.2.0-0.bpo.4-mckinley linux-headers-3.2.0-0.bpo.4-all-m68k linux-image-3.2.0-0.bpo.4-amiga linux-headers-3.2.0-0.bpo.4-amiga linux-image-3.2.0-0.bpo.4-atari linux-headers-3.2.0-0.bpo.4-atari linux-image-3.2.0-0.bpo.4-bvme6000 linux-headers-3.2.0-0.bpo.4-bvme6000 linux-image-3.2.0-0.bpo.4-mac linux-headers-3.2.0-0.bpo.4-mac linux-image-3.2.0-0.bpo.4-mvme147 linux-headers-3.2.0-0.bpo.4-mvme147 linux-image-3.2.0-0.bpo.4-mvme16x linux-headers-3.2.0-0.bpo.4-mvme16x linux-headers-3.2.0-0.bpo.4-all-mips linux-image-3.2.0-0.bpo.4-r4k-ip22 linux-headers-3.2.0-0.bpo.4-r4k-ip22 linux-image-3.2.0-0.bpo.4-r5k-ip32 linux-headers-3.2.0-0.bpo.4-r5k-ip32 linux-image-3.2.0-0.bpo.4-sb1-bcm91250a linux-headers-3.2.0-0.bpo.4-sb1-bcm91250a linux-image-3.2.0-0.bpo.4-sb1a-bcm91480b linux-headers-3.2.0-0.bpo.4-sb1a-bcm91480b linux-image-3.2.0-0.bpo.4-4kc-malta linux-headers-3.2.0-0.bpo.4-4kc-malta linux-image-3.2.0-0.bpo.4-5kc-malta linux-headers-3.2.0-0.bpo.4-5kc-malta linux-image-3.2.0-0.bpo.4-octeon linux-headers-3.2.0-0.bpo.4-octeon linux-headers-3.2.0-0.bpo.4-all-mipsel linux-image-3.2.0-0.bpo.4-r5k-cobalt linux-headers-3.2.0-0.bpo.4-r5k-cobalt linux-image-3.2.0-0.bpo.4-loongson-2f linux-headers-3.2.0-0.bpo.4-loongson-2f linux-headers-3.2.0-0.bpo.4-all-powerpc linux-image-3.2.0-0.bpo.4-powerpc linux-headers-3.2.0-0.bpo.4-powerpc linux-image-3.2.0-0.bpo.4-powerpc-smp linux-headers-3.2.0-0.bpo.4-powerpc-smp linux-image-3.2.0-0.bpo.4-powerpc64 linux-headers-3.2.0-0.bpo.4-powerpc64 linux-headers-3.2.0-0.bpo.4-all-ppc64 linux-headers-3.2.0-0.bpo.4-all-s390 linux-image-3.2.0-0.bpo.4-s390x linux-headers-3.2.0-0.bpo.4-s390x linux-image-3.2.0-0.bpo.4-s390x-dbg linux-image-3.2.0-0.bpo.4-s390x-tape linux-headers-3.2.0-0.bpo.4-all-s390x linux-headers-3.2.0-0.bpo.4-all-sh4 linux-image-3.2.0-0.bpo.4-sh7751r linux-headers-3.2.0-0.bpo.4-sh7751r linux-image-3.2.0-0.bpo.4-sh7785lcr linux-headers-3.2.0-0.bpo.4-sh7785lcr linux-headers-3.2.0-0.bpo.4-all-sparc linux-image-3.2.0-0.bpo.4-sparc64 linux-headers-3.2.0-0.bpo.4-sparc64 linux-image-3.2.0-0.bpo.4-sparc64-smp linux-headers-3.2.0-0.bpo.4-sparc64-smp linux-headers-3.2.0-0.bpo.4-all-sparc64 Architecture: all source Version: 3.2.68-1+deb7u1~bpo60+1 Distribution: squeeze-backports Urgency: high Maintainer: Debian Kernel Team Changed-By: Ben Hutchings Closes: 731439 732689 758264 781548 782561 Description: linux-doc-3.2 - Linux kernel specific documentation for version 3.2 linux-headers-3.2.0-0.bpo.4-486 - Header files for Linux 3.2.0-
Geen watervoorraad meer te voorzien dankzij een waterfontein bij Dupont J
Steeds kwaliteitsvol fris water ter beschikking, zonder voortdurend naar de winkel te moeten rijden om de voorraad aan te vullen Vind de beste leverancier: http://www.debesteleverancier.be/waterkoeler/gratis-offerte.htm?lng=nl&tg=h2o&utm_campaign=h2o&utm_source=admr&utm_medium=email&you=debian-kernel@lists.debian.org Op kamertemperatuur of koud, bruisend of plat, flessenwater of stromend water, met een waterfontein kan iedereen op tijd en stond zijn dorst lessen. Verkrijgbaar in verschillende modellen, van design tot meer klassiek, gemakkelijk in gebruik en perfect integrerend in uw werkomgeving. Een waterfontein wordt meestal als een aangenaam voordeel ervaren door zowel uw medewerkers als uw bezoekers. Onderhoud, levering van water, installatie, onze leveranciers doen het allemaal voor u! --- Online versie: http://mailing.fb.bb1.mailbb.be/c7590/e47053177/hdcff4/l227581/index.html Deze e-mail werd verstuurd naar debian-kernel@lists.debian.org. Profiel aanpassen: http://mailing.fb.bb1.mailbb.be/c7590/e47053177/hdcff4/l227583/index.html Uitschrijven: http://mailing.fb.bb1.mailbb.be/c7590/e47053177/hdcff4/l227582/index.html Privacy policy: http://mailing.fb.bb1.mailbb.be/c7590/e47053177/hdcff4/l227584/index.html
