Bug#588426: linux-image-2.6.32-5-amd64: fail to boot in a kvm virtual machine
Package: linux-2.6 Version: 2.6.32-16 Severity: important Hi, I tried to install linux-image-2.6.32-5-amd64/2.6.32-16 in a kvm virtual machine. With this kernel, it fails to boot. The virtual machine freeze after the line: [0.324387] Write protecting the kernel read-only data: 4220k (see below the full boot log taken from a serial console) I tried to boot both with a serial console (attached to a tty in the host) and with a vga video emulated screen. Same things happened. The kvm machine is a lenny with a few package from unstable Regards, Vincent PS: the severity can be increased if lots of people experiments the same thing or lowered if this is specific to my configuration. -- Package-specific info: [log of a boot with a serial console with linux-image-2.6.32-5-amd64/2.6.32-16] Booting a command list Loading Linux 2.6.32-5-amd64 ... Loading initial ramdisk ... [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.32-5-amd64 (Debian 2.6.32-16) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-1) ) #1 SMP Tue Jul 6 14:14:38 UTC 2010 [0.00] Command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-amd64 root=/dev/mapper/ran-root ro console=ttyS0,9600n8 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009f000 (usable) [0.00] BIOS-e820: 0009f000 - 000a (reserved) [0.00] BIOS-e820: 000f - 0010 (reserved) [0.00] BIOS-e820: 0010 - 1fffb000 (usable) [0.00] BIOS-e820: 1fffb000 - 2000 (reserved) [0.00] BIOS-e820: fffbc000 - 0001 (reserved) [0.00] DMI 2.4 present. [0.00] last_pfn = 0x1fffb max_arch_pfn = 0x4 [0.00] PAT not supported by CPU. [0.00] init_memory_mapping: -1fffb000 [0.00] RAMDISK: 17cf4000 - 1803b6c6 [0.00] ACPI: RSDP 000f8940 00014 (v00 BOCHS ) [0.00] ACPI: RSDT 1fffde30 00034 (v01 BOCHS BXPCRSDT 0001 BXPC 0001) [0.00] ACPI: FACP 1e70 00074 (v01 BOCHS BXPCFACP 0001 BXPC 0001) [0.00] ACPI: DSDT 1fffdfd0 01E22 (v01 BXPC BXDSDT 0001 INTL 20090123) [0.00] ACPI: FACS 1e00 00040 [0.00] ACPI: SSDT 1fffdf90 00037 (v01 BOCHS BXPCSSDT 0001 BXPC 0001) [0.00] ACPI: APIC 1fffdeb0 00072 (v01 BOCHS BXPCAPIC 0001 BXPC 0001) [0.00] ACPI: HPET 1fffde70 00038 (v01 BOCHS BXPCHPET 0001 BXPC 0001) [0.00] No NUMA configuration found [0.00] Faking a node at -1fffb000 [0.00] Bootmem setup node 0 -1fffb000 [0.00] NODE_DATA [9000 - 00010fff] [0.00] bootmap [00011000 - 00014fff] pages 4 [0.00] (7 early reservations) == bootmem [00 - 001fffb000] [0.00] #0 [00 - 001000] BIOS data page == [00 - 001000] [0.00] #1 [006000 - 008000] TRAMPOLINE == [006000 - 008000] [0.00] #2 [000100 - 0001684754]TEXT DATA BSS == [000100 - 0001684754] [0.00] #3 [0017cf4000 - 001803b6c6] RAMDISK == [0017cf4000 - 001803b6c6] [0.00] #4 [09f000 - 10]BIOS reserved == [09f000 - 10] [0.00] #5 [0001685000 - 0001685071] BRK == [0001685000 - 0001685071] [0.00] #6 [008000 - 009000] PGTABLE == [008000 - 009000] [0.00] found SMP MP-table at [880f8990] f8990 [0.00] kvm-clock: cpu 0, msr 0:14ed701, boot clock [0.00] Zone PFN ranges: [0.00] DMA 0x - 0x1000 [0.00] DMA320x1000 - 0x0010 [0.00] Normal 0x0010 - 0x0010 [0.00] Movable zone start PFN for each node [0.00] early_node_map[2] active PFN ranges [0.00] 0: 0x - 0x009f [0.00] 0: 0x0100 - 0x0001fffb [0.00] ACPI: PM-Timer IO Port: 0xb008 [0.00] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [0.00] ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0]) [0.00] IOAPIC[0]: apic_id 1, version 17, address 0xfec0, GSI 0-23 [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level) [0.00] ACPI: INT_SRC_OVR
Bug#588452: softdep modules not included in initramfs when MODULES=dep is specified
Package: initramfs-tools Version: 0.97 softdep modules are not included in the initial RAM file system when MODULES=dep is specified. Here's an example from the s390 architecture: /etc/modprobe.d/dasd.conf: options dasd_mod dasd=0.0.0200(diag),0.0.0201,0.0.0202-0.0.0203(diag) softdep dasd_eckd_mod pre: dasd_diag_mod softdep dasd_fba_mod pre: dasd_diag_mod (/etc/modprobe.conf does *not* exist) /etc/initramfs-tools/conf.d/driver-policy: MODULES=dep /etc/initramfs-tools/modules: (dasd_diag_mod is *not* listed) dasd_eckd_mod is included in the initial RAM file system. I assume that that is due to matching on the alias ccw:t3990m*dt3390dm*. dasd_mod is also included in the initial RAM file system. I presume that that is due to the fact that dasd_mod is a hard dependency of dasd_eckd_mod. But dasd_diag_mod is *not* included in the initial RAM file system, even though it is listed as a soft dependency of dasd_eckd_mod, which has already been selected for inclusion. On the system above, this prevents the system from booting, as the devices marked for use with the diag driver, including the root file system in this case, cannot be brought online. Therefore, the permanent root file system cannot be mounted. I am able to circumvent the problem by explicitly listing dasd_diag_mod in /etc/initramfs-tools/modules, but this should not be necessary. -- .''`. Stephen Powell : :' : `. `'` `- -- 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/922649436.38679.1278600800110.javamail.r...@md01.wow.synacor.com
Processed: tagging 588409
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 588409 + pending Bug #588409 [linux-2.6] perf (linux-tools-2.6.32) fails to build on many architectures Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 588409: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588409 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.127858885830721.transcr...@bugs.debian.org
Bug#588409: perf (linux-tools-2.6.32) fails to build on many architectures
Package: linux-2.6 Version: 2.6.32-16 Severity: serious Justification: fails to build from source perf fails to build for several reasons. 1. Its default CFLAGS include -fstack-protector which isn't available on all architectures. 2. It has a configuration test which relies on linking with an output file of /dev/null, which doesn't work on HP-PA. 3. The perf events feature requires architecture-specific code in the kernel which hasn't been done for all architectures; thus some don't even have a system call number assigned yet. The first two problems are fairly easy to fix. The third will be addressed by restricting the architectures for which perf is built. Ben. -- System Information: Debian Release: squeeze/sid APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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/20100708021506.23487.46969.report...@localhost
Bug#588433: linux-image-2.6.32-5-686: tries to run update-grub, although grub isn't installed anymore
Package: linux-2.6 Version: 2.6.32-16 Severity: normal Hi, today the linux-image-2.6.32-5-686 (2.6.32-16) package failed for me during the configuration phase. When the postinst script is run manually, the following happens: $ sudo LANG=C /var/lib/dpkg/info/linux-image-`uname -r`.postinst configure Running depmod. Running update-initramfs. update-initramfs: Generating /boot/initrd.img-2.6.32-5-686 initrd.img(/boot/initrd.img-2.6.32-5-686 ) points to /boot/initrd.img-2.6.32-5-686 (/boot/initrd.img-2.6.32-5-686) -- doing nothing at /var/lib/dpkg/info/linux- image-2.6.32-5-686.postinst line 379. vmlinuz(/boot/vmlinuz-2.6.32-5-686 ) points to /boot/vmlinuz-2.6.32-5-686 (/boot/vmlinuz-2.6.32-5-686) -- doing nothing at /var/lib/dpkg/info/linux- image-2.6.32-5-686.postinst line 379. Running update-grub. User postinst hook script [update-grub] failed to execute: No such file or directory So it fails to start update-grub, which is expected as I have purged all grub packages from my system and replaced it with the extlinux bootloader instead. However, grub-pc is still set as postinst_hook in /etc/kernel-img.conf: $ grep grub /etc/kernel-img.conf postinst_hook = update-grub postrm_hook = update-grub Please note that I have never ever touched this file. It should not blindly rely the existance of update-grub. Cheers, Fabian -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-16) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-1) ) #1 SMP Tue Jul 6 14:57:57 UTC 2010 ** Command line: initrd=/boot/initrd.img-2.6.32-5-686 root=UUID=e6445315-c5bf-4e2c-b011-3ed84748fd53 ro quiet BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 ** Not tainted ** Kernel log: [1.267887] ehci_hcd :00:0b.0: irq 19, io mem 0xf0805000 [1.273371] libata version 3.00 loaded. [1.276165] ehci_hcd :00:0b.0: USB 2.0 started, EHCI 1.00 [1.276207] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [1.276208] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.276210] usb usb1: Product: EHCI Host Controller [1.276212] usb usb1: Manufacturer: Linux 2.6.32-5-686 ehci_hcd [1.276213] usb usb1: SerialNumber: :00:0b.0 [1.276533] usb usb1: configuration #1 chosen from 1 choice [1.276596] hub 1-0:1.0: USB hub found [1.276602] hub 1-0:1.0: 8 ports detected [1.278578] ata_piix :00:01.1: version 2.13 [1.278925] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [1.283457] scsi0 : ata_piix [1.283803] scsi1 : ata_piix [1.284000] ata1: PATA max UDMA/33 cmd 0x1f0 ctl 0x3f6 bmdma 0xd000 irq 14 [1.284002] ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0xd008 irq 15 [1.284297] ohci_hcd :00:06.0: PCI INT A - GSI 22 (level, low) - IRQ 22 [1.284348] ohci_hcd :00:06.0: OHCI Host Controller [1.284366] ohci_hcd :00:06.0: new USB bus registered, assigned bus number 2 [1.284443] ohci_hcd :00:06.0: irq 22, io mem 0xf0804000 [1.340199] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 [1.340202] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.340203] usb usb2: Product: OHCI Host Controller [1.340205] usb usb2: Manufacturer: Linux 2.6.32-5-686 ohci_hcd [1.340206] usb usb2: SerialNumber: :00:06.0 [1.340284] usb usb2: configuration #1 chosen from 1 choice [1.340302] hub 2-0:1.0: USB hub found [1.340360] hub 2-0:1.0: 8 ports detected [1.440679] ata2.00: ATAPI: VBOX CD-ROM, 1.0, max UDMA/133 [1.440943] ata1.00: ATA-6: VBOX HARDDISK, 1.0, max UDMA/133 [1.440945] ata1.00: 16777216 sectors, multi 128: LBA [1.441587] ata2.00: configured for UDMA/33 [1.441766] ata1.00: configured for UDMA/33 [1.441985] scsi 0:0:0:0: Direct-Access ATA VBOX HARDDISK1.0 PQ: 0 ANSI: 5 [1.442390] scsi 1:0:0:0: CD-ROMVBOX CD-ROM 1.0 PQ: 0 ANSI: 5 [1.478171] sd 0:0:0:0: [sda] 16777216 512-byte logical blocks: (8.58 GB/8.00 GiB) [1.478202] sd 0:0:0:0: [sda] Write Protect is off [1.478204] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [1.478216] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [1.478336] sda: sda1 sda2 sr0: scsi3-mmc drive: 32x/32x xa/form2 tray [1.481173] Uniform CD-ROM driver Revision: 3.20 [1.481428] sr 1:0:0:0: Attached scsi CD-ROM sr0 [1.485832] sda5 sda6 [1.493719] sd 0:0:0:0: [sda] Attached SCSI disk [1.533184] sd 0:0:0:0: Attached scsi generic sg0 type 0 [1.533486] sr 1:0:0:0: Attached scsi generic sg1 type 5 [1.765793] PM: Starting manual resume from disk [1.765795] PM: Resume from partition 8:5 [1.765796] PM: Checking hibernation image. [1.765982] PM: Error -22 checking image file [1.765983] PM: Resume from disk failed. [1.802971] kjournald starting. Commit interval 5 seconds [1.802979] EXT3-fs: mounted filesystem with ordered data mode. [
Bug#588409: perf (linux-tools-2.6.32) fails to build on many architectures
Regarding the perf tools: Commit 5d7bdab75cd56d2bdc0986ae5546be3b09fea70a upstream should give the -fstack-protector-all test. Regarding the Alpha architecture the following commits that are in v2.6.33 of the kernel upstream provide the performance event interface: Commit fcd14b3203b538dca04a2b065c774c0b57863eec upstream adds the Alpha specific part for perf tools. Commit a582e6f01b90211933e70edcec9bc0bbb1157402 upstream provides minimal support for performance events in the kernel for Alpha. However it probably won't apply cleanly to 2.6.32 without commit 21797c599c710d3851d241c4b50690f2482bf618 which wires up quite a number of missing syscalls, which in turn depends on 6e17e8b9fb74b9fb9f6ea331f7f4a049c5b4c4b8 which wires up the syscall for recvmmsg that is new in 2.6.33. Thus a modified 21797c599 is required for 2.6.32 to do all this; I think I might still have the patch somewhere, but in any case I could regenerate it should you wish to have it. Cheers Michael -- 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/4c35b72d.5000...@orcon.net.nz
Bug#588452: softdep modules not included in initramfs when MODULES=dep is specified
* Stephen Powell zlinux...@wowway.com [Thu Jul 08, 2010 at 10:53:20AM -0400]:
softdep modules are not included in the initial RAM file system
when MODULES=dep is specified. Here's an example from the s390
architecture:
/etc/modprobe.d/dasd.conf:
options dasd_mod dasd=0.0.0200(diag),0.0.0201,0.0.0202-0.0.0203(diag)
softdep dasd_eckd_mod pre: dasd_diag_mod
softdep dasd_fba_mod pre: dasd_diag_mod
(/etc/modprobe.conf does *not* exist)
/etc/initramfs-tools/conf.d/driver-policy:
MODULES=dep
/etc/initramfs-tools/modules:
(dasd_diag_mod is *not* listed)
dasd_eckd_mod is included in the initial RAM file system. I assume that
that is due to matching on the alias ccw:t3990m*dt3390dm*. dasd_mod
is also included in the initial RAM file system. I presume that that
is due to the fact that dasd_mod is a hard dependency of dasd_eckd_mod.
But dasd_diag_mod is *not* included in the initial RAM file system,
even though it is listed as a soft dependency of dasd_eckd_mod, which
has already been selected for inclusion.
On the system above, this prevents the system from booting, as the
devices marked for use with the diag driver, including the root file
system in this case, cannot be brought online. Therefore, the permanent
root file system cannot be mounted.
I am able to circumvent the problem by explicitly listing dasd_diag_mod
in /etc/initramfs-tools/modules, but this should not be necessary.
For MODULES=dep we use modprobe as interface to detect dependencies.
To display the dependencies of dasd_eckd_mod you could run:
modprobe --set-version=$(uname -r) --ignore-install --quiet --show-depends
dasd_eckd_mod | awk '/^insmod/ { print $2 }'
which will not list dasd_diag_mod as a dependency AFAICS.
Quoting:
, [ modprobe.conf(5) ]
| COMPATIBILITY
|
|A future version of module-init-tools will come with a strong
|warning to avoid use of the install as explained above. This
|will happen once support for soft dependencies in the
|kernel is complete. That support will complement the
|existing softdep support within this utility by providing
|such dependencies directly within the modules.
`
I don't want to include any special support for softdep just inside
initramfs-tools, instead I'd like to get an interface from
module-init-tools's modprobe that we could use for dependency
resolution.
Any objections against reassigning this bugreport to
module-init-tools (maks?)?
regards,
-mika-
signature.asc
Description: Digital signature
Bug#588426: linux-image-2.6.32-5-amd64: fail to boot in a kvm virtual machine
On Thu, 08 Jul 2010 10:36:48 +0200 Vincent Danjean vdanj...@debian.org wrote: Package: linux-2.6 Version: 2.6.32-16 Severity: important Hi, I tried to install linux-image-2.6.32-5-amd64/2.6.32-16 in a kvm virtual machine. With this kernel, it fails to boot. The virtual machine freeze after the line: [0.324387] Write protecting the kernel read-only data: 4220k (see below the full boot log taken from a serial console) I tried to boot both with a serial console (attached to a tty in the host) and with a vga video emulated screen. Same things happened. The kvm machine is a lenny with a few package from unstable Regards, Vincent PS: the severity can be increased if lots of people experiments the same thing or lowered if this is specific to my configuration. Hi, I can confirm I had the very same problem with a kvm virtual machine (amd64) upgraded from squeeze to sid. Downgrading to 2.6.32-15 from squeeze made it able to boot again. Thanks, -- Cristian Greco GPG key ID: 0xCF4D32E4 signature.asc Description: PGP signature
Processed: [bts-link] source package linux-2.6
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #571741 (http://bugs.debian.org/571741) # * http://bugzilla.kernel.org/show_bug.cgi?id=13811 # * remote status changed: RESOLVED - NEW # * remote resolution changed: FIXED - (?) # * reopen upstream tags 571741 - fixed-upstream Bug #571741 [linux-2.6] System freezes after pm-hibernate when kms is on Bug #534422 [linux-2.6] Enabling KMS causes lots of segfaults after hibernation resume Bug #545125 [linux-2.6] linux-image-2.6.31-rc6-amd64: freeze and on-disk corruption with KMS and suspend-to-disk Bug #545517 [linux-2.6] linux-image-2.6.31-rc6-amd64: freeze and on-disk corruption with KMS and suspend-to-disk Bug #576800 [linux-2.6] libc6: Cannot create new processes after hibernating Removed tag(s) fixed-upstream. Removed tag(s) fixed-upstream. Removed tag(s) fixed-upstream. Removed tag(s) fixed-upstream. Removed tag(s) fixed-upstream. usertags 571741 - status-RESOLVED resolution-FIXED Bug#571741: System freezes after pm-hibernate when kms is on Usertags were: status-RESOLVED resolution-FIXED. Usertags are now: . usertags 571741 + status-NEW Bug#571741: System freezes after pm-hibernate when kms is on There were no usertags set. Usertags are now: status-NEW. # remote status report for #571741 (http://bugs.debian.org/571741) # * http://bugzilla.kernel.org/show_bug.cgi?id=13811 # * remote status changed: RESOLVED - NEW # * remote resolution changed: FIXED - (?) # * reopen upstream tags 571741 - fixed-upstream Bug #571741 [linux-2.6] System freezes after pm-hibernate when kms is on Bug #534422 [linux-2.6] Enabling KMS causes lots of segfaults after hibernation resume Bug #545125 [linux-2.6] linux-image-2.6.31-rc6-amd64: freeze and on-disk corruption with KMS and suspend-to-disk Bug #545517 [linux-2.6] linux-image-2.6.31-rc6-amd64: freeze and on-disk corruption with KMS and suspend-to-disk Bug #576800 [linux-2.6] libc6: Cannot create new processes after hibernating Ignoring request to alter tags of bug #571741 to the same tags previously set Ignoring request to alter tags of bug #534422 to the same tags previously set Ignoring request to alter tags of bug #545125 to the same tags previously set Ignoring request to alter tags of bug #545517 to the same tags previously set Ignoring request to alter tags of bug #576800 to the same tags previously set usertags 571741 - status-RESOLVED resolution-FIXED Bug#571741: System freezes after pm-hibernate when kms is on Usertags were: status-NEW. Usertags are now: status-NEW. usertags 571741 + status-NEW Bug#571741: System freezes after pm-hibernate when kms is on Usertags were: status-NEW. Usertags are now: status-NEW. # remote status report for #571741 (http://bugs.debian.org/571741) # * http://bugzilla.kernel.org/show_bug.cgi?id=13811 # * remote status changed: RESOLVED - NEW # * remote resolution changed: FIXED - (?) # * reopen upstream tags 571741 - fixed-upstream Bug #571741 [linux-2.6] System freezes after pm-hibernate when kms is on Bug #534422 [linux-2.6] Enabling KMS causes lots of segfaults after hibernation resume Bug #545125 [linux-2.6] linux-image-2.6.31-rc6-amd64: freeze and on-disk corruption with KMS and suspend-to-disk Bug #545517 [linux-2.6] linux-image-2.6.31-rc6-amd64: freeze and on-disk corruption with KMS and suspend-to-disk Bug #576800 [linux-2.6] libc6: Cannot create new processes after hibernating Ignoring request to alter tags of bug #571741 to the same tags previously set Ignoring request to alter tags of bug #534422 to the same tags previously set Ignoring request to alter tags of bug #545125 to the same tags previously set Ignoring request to alter tags of bug #545517 to the same tags previously set Ignoring request to alter tags of bug #576800 to the same tags previously set usertags 571741 - status-RESOLVED resolution-FIXED Bug#571741: System freezes after pm-hibernate when kms is on Usertags were: status-NEW. Usertags are now: status-NEW. usertags 571741 + status-NEW Bug#571741: System freezes after pm-hibernate when kms is on Usertags were: status-NEW. Usertags are now: status-NEW. # remote status report for #571741 (http://bugs.debian.org/571741) # * http://bugzilla.kernel.org/show_bug.cgi?id=13811 # * remote status changed: RESOLVED - NEW # * remote resolution changed: FIXED - (?) # * reopen upstream tags 571741 - fixed-upstream Bug #571741 [linux-2.6] System freezes after pm-hibernate when kms is on Bug #534422 [linux-2.6] Enabling KMS causes lots of segfaults after hibernation resume Bug #545125 [linux-2.6] linux-image-2.6.31-rc6-amd64: freeze and on-disk corruption with KMS and suspend-to-disk Bug #545517
Bug#588426: linux-image-2.6.32-5-amd64: fail to boot in a kvm virtual machine
On Thu, Jul 8, 2010 at 10:36:48 +0200, Vincent Danjean wrote: Package: linux-2.6 Version: 2.6.32-16 Severity: important Hi, I tried to install linux-image-2.6.32-5-amd64/2.6.32-16 in a kvm virtual machine. With this kernel, it fails to boot. The virtual machine freeze after the line: [0.324387] Write protecting the kernel read-only data: 4220k (see below the full boot log taken from a serial console) I tried to boot both with a serial console (attached to a tty in the host) and with a vga video emulated screen. Same things happened. The kvm machine is a lenny with a few package from unstable Regards, Vincent PS: the severity can be increased if lots of people experiments the same thing or lowered if this is specific to my configuration. Likely the same as reported by weasel at http://lkml.indiana.edu/hypermail/linux/kernel/1007.0/02385.html Cheers, Julien signature.asc Description: Digital signature
[bts-link] source package linux-2.6
# # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #571741 (http://bugs.debian.org/571741) # * http://bugzilla.kernel.org/show_bug.cgi?id=13811 # * remote status changed: RESOLVED - NEW # * remote resolution changed: FIXED - (?) # * reopen upstream tags 571741 - fixed-upstream usertags 571741 - status-RESOLVED resolution-FIXED usertags 571741 + status-NEW # remote status report for #571741 (http://bugs.debian.org/571741) # * http://bugzilla.kernel.org/show_bug.cgi?id=13811 # * remote status changed: RESOLVED - NEW # * remote resolution changed: FIXED - (?) # * reopen upstream tags 571741 - fixed-upstream usertags 571741 - status-RESOLVED resolution-FIXED usertags 571741 + status-NEW # remote status report for #571741 (http://bugs.debian.org/571741) # * http://bugzilla.kernel.org/show_bug.cgi?id=13811 # * remote status changed: RESOLVED - NEW # * remote resolution changed: FIXED - (?) # * reopen upstream tags 571741 - fixed-upstream usertags 571741 - status-RESOLVED resolution-FIXED usertags 571741 + status-NEW # remote status report for #571741 (http://bugs.debian.org/571741) # * http://bugzilla.kernel.org/show_bug.cgi?id=13811 # * remote status changed: RESOLVED - NEW # * remote resolution changed: FIXED - (?) # * reopen upstream tags 571741 - fixed-upstream usertags 571741 - status-RESOLVED resolution-FIXED usertags 571741 + status-NEW thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100708163348.2376.83261.btsl...@merkel.debian.org
Bug#587093: link with uswsusp
After complete reinstall of the system it turns out that the problem is link with uswsusp. Without it plymouth don't hang anymore while resuming (althrougt there isn't any plymouth while resuming anymore) -- 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/1278608080.10807.2.ca...@pink
Bug#551821: [nfs-common] directory not mounted at boot-time
Hi, this bug is the same as bug #540291. -- Laurent Bonnaud. -- 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/1278610233.4599.6.ca...@localhost
Bug#588452: softdep modules not included in initramfs when MODULES=dep is specified
On Thu, 08 Jul 2010 12:03:39 -0400 (EDT), Michael Prokop wrote:
For MODULES=dep we use modprobe as interface to detect dependencies.
To display the dependencies of dasd_eckd_mod you could run:
modprobe --set-version=$(uname -r) --ignore-install --quiet --show-depends
dasd_eckd_mod | awk '/^insmod/ { print $2 }'
which will not list dasd_diag_mod as a dependency AFAICS.
Output of the above command on my system:
/lib/modules/2.6.32-custom5b-s390x/kernel/drivers/s390/block/dasd_mod.ko
/lib/modules/2.6.32-custom5b-s390x/kernel/drivers/s390/block/dasd_eckd_mod.ko
In other words, it list only the module itself plus hard dependencies.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
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/1294535410.43811.1278611163548.javamail.r...@md01.wow.synacor.com
Bug#588458: 2.6.32-5-vserver-686
Same kernel configuration is missing also for 2.6.32-5-vserver-686. Please apply the needed change in the upcoming release. Regards, Jan -- Jan Prunk http://www.prunk.si 0x00E80E86 http://pgp.prunk.si -- 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/aanlktinponaqt5f11ybojhzymbgj3sqw6v3d8ydhd...@mail.gmail.com
Bug#588461: Solved
The issue was solved, after running update-grub, the initrd line was missing inside grub.cfg. Boots properly now. Regards, Jan -- Jan Prunk http://www.prunk.si 0x00E80E86 http://pgp.prunk.si -- 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/aanlktimtrcmt0jajdyhtxkcljsg2ruj3uses7dos4...@mail.gmail.com
Bug#573144: Re: Re: Re: Bug#573144: linux-image-2.6-686: kernel freezes related to i915 handle error
So it has been really caused by xserver-xorg-video-radeon. I have downgraded from 6.13.0-2 to previous 6.12.6-1 and freezing gone :) Zbynek On Tue, Jun 29, 2010 at 11:02:55AM +0200, Zbynek Michl wrote: So 2.6.32-3-686 freezes too. I don't know how to debug it, because kernel seems to be completely dead :( Zbynek did you check with latest experimental intel driver? I have tried the latest 2.6.34-1-686_2.6.34-1~experimental.2_i386 with no luck. also we will shortly make 2.6.35-rcX available. the old intel driver support is since some time messy, sorry for that. Do you think intel driver in the kernel? Couldn't be there any connection with x.org driver (xserver-xorg-video-radeon in my case)? Thanks, Zbynek -- 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/4788.619.948-14764-2080684246-1278617...@seznam.cz
Bug#588433: marked as done (linux-image-2.6.32-5-686: tries to run update-grub, although grub isn't installed anymore)
Your message dated Thu, 8 Jul 2010 21:13:11 +0100 with message-id 20100708201311.gg5...@decadent.org.uk and subject line Re: Bug#588433: linux-image-2.6.32-5-686: tries to run update-grub, although grub isn't installed anymore has caused the Debian Bug report #588433, regarding linux-image-2.6.32-5-686: tries to run update-grub, although grub isn't installed anymore 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.) -- 588433: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588433 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-16 Severity: normal Hi, today the linux-image-2.6.32-5-686 (2.6.32-16) package failed for me during the configuration phase. When the postinst script is run manually, the following happens: $ sudo LANG=C /var/lib/dpkg/info/linux-image-`uname -r`.postinst configure Running depmod. Running update-initramfs. update-initramfs: Generating /boot/initrd.img-2.6.32-5-686 initrd.img(/boot/initrd.img-2.6.32-5-686 ) points to /boot/initrd.img-2.6.32-5-686 (/boot/initrd.img-2.6.32-5-686) -- doing nothing at /var/lib/dpkg/info/linux- image-2.6.32-5-686.postinst line 379. vmlinuz(/boot/vmlinuz-2.6.32-5-686 ) points to /boot/vmlinuz-2.6.32-5-686 (/boot/vmlinuz-2.6.32-5-686) -- doing nothing at /var/lib/dpkg/info/linux- image-2.6.32-5-686.postinst line 379. Running update-grub. User postinst hook script [update-grub] failed to execute: No such file or directory So it fails to start update-grub, which is expected as I have purged all grub packages from my system and replaced it with the extlinux bootloader instead. However, grub-pc is still set as postinst_hook in /etc/kernel-img.conf: $ grep grub /etc/kernel-img.conf postinst_hook = update-grub postrm_hook = update-grub Please note that I have never ever touched this file. It should not blindly rely the existance of update-grub. Cheers, Fabian -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-16) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-1) ) #1 SMP Tue Jul 6 14:57:57 UTC 2010 ** Command line: initrd=/boot/initrd.img-2.6.32-5-686 root=UUID=e6445315-c5bf-4e2c-b011-3ed84748fd53 ro quiet BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 ** Not tainted ** Kernel log: [1.267887] ehci_hcd :00:0b.0: irq 19, io mem 0xf0805000 [1.273371] libata version 3.00 loaded. [1.276165] ehci_hcd :00:0b.0: USB 2.0 started, EHCI 1.00 [1.276207] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [1.276208] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.276210] usb usb1: Product: EHCI Host Controller [1.276212] usb usb1: Manufacturer: Linux 2.6.32-5-686 ehci_hcd [1.276213] usb usb1: SerialNumber: :00:0b.0 [1.276533] usb usb1: configuration #1 chosen from 1 choice [1.276596] hub 1-0:1.0: USB hub found [1.276602] hub 1-0:1.0: 8 ports detected [1.278578] ata_piix :00:01.1: version 2.13 [1.278925] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [1.283457] scsi0 : ata_piix [1.283803] scsi1 : ata_piix [1.284000] ata1: PATA max UDMA/33 cmd 0x1f0 ctl 0x3f6 bmdma 0xd000 irq 14 [1.284002] ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0xd008 irq 15 [1.284297] ohci_hcd :00:06.0: PCI INT A - GSI 22 (level, low) - IRQ 22 [1.284348] ohci_hcd :00:06.0: OHCI Host Controller [1.284366] ohci_hcd :00:06.0: new USB bus registered, assigned bus number 2 [1.284443] ohci_hcd :00:06.0: irq 22, io mem 0xf0804000 [1.340199] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 [1.340202] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.340203] usb usb2: Product: OHCI Host Controller [1.340205] usb usb2: Manufacturer: Linux 2.6.32-5-686 ohci_hcd [1.340206] usb usb2: SerialNumber: :00:06.0 [1.340284] usb usb2: configuration #1 chosen from 1 choice [1.340302] hub 2-0:1.0: USB hub found [1.340360] hub 2-0:1.0: 8 ports detected [1.440679] ata2.00: ATAPI: VBOX CD-ROM, 1.0, max UDMA/133 [1.440943] ata1.00: ATA-6: VBOX HARDDISK, 1.0, max UDMA/133 [1.440945] ata1.00: 16777216 sectors, multi 128: LBA [1.441587] ata2.00: configured for UDMA/33 [1.441766] ata1.00: configured for UDMA/33 [1.441985] scsi 0:0:0:0: Direct-Access ATA VBOX HARDDISK1.0 PQ: 0 ANSI: 5 [1.442390] scsi 1:0:0:0: CD-ROMVBOX CD-ROM 1.0 PQ: 0 ANSI: 5 [1.478171] sd 0:0:0:0: [sda] 16777216 512-byte logical blocks: (8.58 GB/8.00 GiB) [
Re: [DRAFT v2] Policy for Linux kernel, initramfs, boot loader update process
Guillem Jover dixit: A bit of background info. For GNU/kFreeBSD the kernel images are named 'kfreebsd-image-*', for GNU/Hurd they are named 'gnumach'. (I should probably rename gnumach to match the current kernel naming convention.) I wonder if there will ever be packages like kmidnightbsd-image-* for Debian GNU/kFreeBSD (it’s a relatively close fork of it, and the few kfreebsd specific patch lines could be applied)… bye, //mirabilos, who’s had beers with the MidnightBSD founder recently -- I believe no one can invent an algorithm. One just happens to hit upon it when God enlightens him. Or only God invents algorithms, we merely copy them. If you don't believe in God, just consider God as Nature if you won't deny existence. -- Coywolf Qi Hunt -- 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/pine.bsm.4.64l.1007082127010.18...@herc.mirbsd.org
Re: [DRAFT v2] Policy for Linux kernel, initramfs, boot loader update process
Hi! So while this was presented as a draft for Linux kernels, it touches interfaces shared with other kernels, so I think it would be nice to try to get it to be kernel agnostic, CCing debian-bsd@ and debian-hurd@ just for that. The complete draft can be found in debian-ker...@. A bit of background info. For GNU/kFreeBSD the kernel images are named 'kfreebsd-image-*', for GNU/Hurd they are named 'gnumach'. (I should probably rename gnumach to match the current kernel naming convention.) GNU/kFreeBSD can boot using either the native FreeBSD boot loader, or grub. GNU/Hurd can boot with any multiboot compliant boot loader. Currently neither make use or need any initrd image to boot, due to using boot loader loadable modules. But there's been talk about adding initrd support to gnumach for d-i. On Sun, 2010-07-04 at 18:48:20 +0100, Ben Hutchings wrote: 4. During a kernel package installation, upgrade or removal, various boot loader hooks may be invoked (in this order): a. A postinst_hook or postrm_hook command set by the user or the installer in /etc/kernel-img.conf kfreebsd-image-* packages honour those hooks. I'll add support for those to gnumach. b. A hook script in /etc/initramfs/post-update.d Neither kfreebsd nor gnumach honour this, not needed yet though. c. A hook script in /etc/kernel/postinst.d or .../postrm.d Neither do honour these, they need support added. I can probably make some time to do that for both. To avoid unnecessary updates, the hooks invoked at step a and b may check whether $DPKG_MAINTSCRIPT_PACKAGE begins with 'linux-image-' and do nothing in this case. Take into account that DPKG_MAINTSCRIPT_PACKAGE is only set if running under dpkg, dpkg-reconfigure (from debconf) does not set this nor other variables yet. See #560317. It would be nice to consider the other kernel package names. But even nicer to just have a centralized place where all currently known package patterns are listed or can be queried so that there's no need to update multiple scripts on new kernel additions, or name convention changes. 5. Kernel packages must not invoke boot loaders except via hooks. If /etc/kernel-img.conf contains 'do_bootloader = yes' or equivalent, maintainer scripts that previously acted on this must warn that they are ignoring it. linux-base must also warn on upgrade that the default has changed. In squeeze+1, this prohibition extends to initramfs builder packages. Neither kfreebsd-image-* nor gnumach packages have ever honoured do_bootloader. thanks, guillem -- 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/20100708075158.gb31...@gaara.hadrons.org
Re: Proposed changes to initramfs-tools hook scripts
On Fri, 02 Jul 2010, maximilian attems wrote: On Wed, 30 Jun 2010, Stephen Powell wrote: Max, As promised, here are my proposed changes to the initramfs-tools hook scripts. /etc/kernel/postinst.d/initramfs-tools: http://www.wowway.com/~zlinuxman/kernel/postinst.d/initramfs-tools /etc/kernel/postrm.d/initramfs-tools: http://www.wowway.com/~zlinuxman/kernel/postrm.d/initramfs-tools I release the changes under the same license as currently used. I did not include the scripts or patches in-line in my e-mail because my e-mail client has the nasty habit of expanding tabs, inserting extra line breaks, etc. So I up-loaded the files to my web site and included links to them in this e-mail. Changes: (1) Does not create an initial RAM file system image for a custom kernel created by make-kpkg if one was not requested by the --initrd flag of make-kpkg. (2) Redirects STDOUT to STDERR when invoking update-initramfs. (Avoids output being swallowed by debconf's redirection of STDOUT.) (3) Postinst.d version always exits with status code zero, even if an error occurs attempting to delete the initramfs. thank you very much. applied your 3 changes to branch maks/hooks on http://git.debian.org/?p=kernel/initramfs-tools.git;a=summary please review before I'd merge into master for next upload. I'm not sure if the indirection to STDERR is needed for make deb-pkg, but it shouldn't hurt there? so mika reviewed http://git.debian.org/?p=kernel/initramfs-tools.git;a=shortlog;h=refs/heads/maks/hooks he critisize the exit 0 without any stdout/stderr message. so rethinking why do you want that anyway? I do not see the point of it, update-initramfs is already told to not care if that initramfs exists with the takeover flag so will not errexit. thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100708132402.gc2...@stro.at
Bug#582826: Oops: 0002 unable to handle kernel paging request
For the record only. - My machine has been occasionally (far too regularly, every couple of weeks) crashing with the same error as reported. Other machines, similar hardware and identical kernel, did not seem affected. - Today I updated the kernels to one based on 2.6.26-24, will monitor whether that helps. Cheers, Paul Paul Szabo p...@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/ School of Mathematics and Statistics University of SydneyAustralia -- 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/201007082254.o68ms066031...@bari.maths.usyd.edu.au
Processed: reassign 588466 to initramfs-tools
Processing commands for cont...@bugs.debian.org: reassign 588466 initramfs-tools Bug #588466 [klibc-utils] klibc-utils: kernel panic when resume failed and normal boot continues Bug reassigned from package 'klibc-utils' to 'initramfs-tools'. Bug No longer marked as found in versions klibc/1.5.18-1. thanks Stopping processing here. Please contact me if you need assistance. -- 588466: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588466 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.12786321153415.transcr...@bugs.debian.org
Re: Proposed changes to initramfs-tools hook scripts
On Thu, 08 Jul 2010 09:24:02 -0400 (EDT), maximilian attems wrote: so mika reviewed http://git.debian.org/?p=kernel/initramfs-tools.git;a=shortlog;h=refs/heads/maks/hooks he critisize the exit 0 without any stdout/stderr message. so rethinking why do you want that anyway? I do not see the point of it, update-initramfs is already told to not care if that initramfs exists with the takeover flag so will not errexit. You're right. With the -t flag, attempting to delete a non-existent initial RAM file system does not cause an error exit. Exit status is zero, even if the file does not exist. The exit 0 is unnecessary. Good catch, Mika! -- .''`. Stephen Powell : :' : `. `'` `- -- 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/1884856145.37359.1278598343367.javamail.r...@md01.wow.synacor.com
Bug#588409: perf (linux-tools-2.6.32) fails to build on many architectures
On Thu, 2010-07-08 at 23:31 +1200, Michael Cree wrote: Regarding the perf tools: Commit 5d7bdab75cd56d2bdc0986ae5546be3b09fea70a upstream should give the -fstack-protector-all test. Thanks; I've applied this and several other upstream build fixes and improvements: perf tools: Display better error messages on missing packages perf tools: Add 'make DEBUG=1' to remove the -O6 cflag perf tools: Test -fstack-protector-all compiler option for inclusion in CFLAGS perf tools: Support static build perf tools: Add V=2 option to help debug config issues perf tools: Suggest static libraries as well perf: Use default compiler mode by default perf tools: Move QUIET_STDERR def to before first use perf tools: Check if /dev/null can be used as the -o gcc argument Regarding the Alpha architecture the following commits that are in v2.6.33 of the kernel upstream provide the performance event interface: Commit fcd14b3203b538dca04a2b065c774c0b57863eec upstream adds the Alpha specific part for perf tools. Commit a582e6f01b90211933e70edcec9bc0bbb1157402 upstream provides minimal support for performance events in the kernel for Alpha. However it probably won't apply cleanly to 2.6.32 without commit 21797c599c710d3851d241c4b50690f2482bf618 which wires up quite a number of missing syscalls, which in turn depends on 6e17e8b9fb74b9fb9f6ea331f7f4a049c5b4c4b8 which wires up the syscall for recvmmsg that is new in 2.6.33. Thus a modified 21797c599 is required for 2.6.32 to do all this; I think I might still have the patch somewhere, but in any case I could regenerate it should you wish to have it. I'll be happy to apply backported patches. However, Alpha is no longer a Debian release architecture and I don't intend to spend any significant time on it. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: your mail
Processing commands for cont...@bugs.debian.org: reassign 583933 linux-image-2.6.32-5-amd64 Bug #583933 [xserver-xorg-video-radeon] xserver-xorg-video-radeon: Latest radeon + KMS ASIC bug error message Bug reassigned from package 'xserver-xorg-video-radeon' to 'linux-image-2.6.32-5-amd64'. Bug No longer marked as found in versions xserver-xorg-video-ati/1:6.13.0-2. End of message, stopping processing here. Please contact me if you need assistance. -- 583933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583933 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.12786510676131.transcr...@bugs.debian.org
