Processed: forcibly merging 595927 600075
Processing commands for cont...@bugs.debian.org: forcemerge 595927 600075 Bug#595927: linux-image-2.6.32-5-amd64: task dpkg blocked for more than 120 seconds Bug#600075: linux-image-2.6.32-5-amd64: Problem with usb Forcibly Merged 595927 600075. thanks Stopping processing here. Please contact me if you need assistance. -- 595927: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595927 600075: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600075 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.128937930217933.transcr...@bugs.debian.org
Bug#602966: linux-source-2.6.36: Oops while unmouning an USB key with FAT filesystem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Ben, Please report this upstream at https://bugzilla.kernel.org under product 'File System', component 'FAT/VFAT/MSDOS'. Attach the same information you provided to us. Let us known the bug number or URL so we can track it. Here is the link: https://bugzilla.kernel.org/show_bug.cgi?id=22602 Regards Jean-Luc -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFM2l7iUdGGXzzGnNARApcHAJ0ZUIOqf7nvhLXZR3uaOIynSeMttACgglbQ kvIPi1KutPTZXlVv/EOehrs= =akfR -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: http://lists.debian.org/4cda5ee3.50...@wanadoo.fr
Processed: severity of 602991 is important
Processing commands for cont...@bugs.debian.org: severity 602991 important Bug #602991 [linux-2.6] (no subject) Severity set to 'important' from 'critical' thanks Stopping processing here. Please contact me if you need assistance. -- 602991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602991 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.128937957919256.transcr...@bugs.debian.org
Processed: bug 602966 is forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=22602
Processing commands for cont...@bugs.debian.org: forwarded 602966 https://bugzilla.kernel.org/show_bug.cgi?id=22602 Bug #602966 [linux-source-2.6.36] linux-source-2.6.36: Oops while unmouning an USB key with FAT filesystem Ignoring request to change the forwarded-to-address of bug#602966 to the same value thanks Stopping processing here. Please contact me if you need assistance. -- 602966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602966 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.128939089916540.transcr...@bugs.debian.org
Processed: reassign 595927 to dpkg, severity of 595927 is critical
Processing commands for cont...@bugs.debian.org: reassign 595927 dpkg Bug #595927 [linux-2.6] linux-image-2.6.32-5-amd64: task dpkg blocked for more than 120 seconds Bug #600075 [linux-2.6] linux-image-2.6.32-5-amd64: Problem with usb Bug reassigned from package 'linux-2.6' to 'dpkg'. Bug reassigned from package 'linux-2.6' to 'dpkg'. Bug No longer marked as found in versions 2.6.32-24, 2.6.32-21, and 2.6.32-23. Bug No longer marked as found in versions 2.6.32-24, 2.6.32-21, and 2.6.32-23. severity 595927 critical Bug #595927 [dpkg] linux-image-2.6.32-5-amd64: task dpkg blocked for more than 120 seconds Bug #600075 [dpkg] linux-image-2.6.32-5-amd64: Problem with usb Severity set to 'critical' from 'important' Severity set to 'critical' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 595927: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595927 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.128937952419058.transcr...@bugs.debian.org
Processed: bug 602966 is forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=22602
Processing commands for cont...@bugs.debian.org: forwarded 602966 https://bugzilla.kernel.org/show_bug.cgi?id=22602 Bug #602966 [linux-source-2.6.36] linux-source-2.6.36: Oops while unmouning an USB key with FAT filesystem Set Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=22602'. thanks Stopping processing here. Please contact me if you need assistance. -- 602966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602966 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.128938073126243.transcr...@bugs.debian.org
Bug#602935: xen-linux-system-2.6.32-5-xen-amd64: domU stack trace error when migrating with xen kernel 2.6.32-27
Hi, Google finds the same crash at http://www.chiark.greenend.org.uk/~xensrcts/logs/2449/test-amd64-amd64-pair/guest-debian.guest.osstest-console which is apparently some sort of testsuite log. It says that the version was 28a160746815. Then in the same directory hierarchy I found that the first non-failing version is http://www.chiark.greenend.org.uk/~xensrcts/logs/2473/test-amd64-amd64-pair/guest-debian.guest.osstest-console which says this 6c72eadd151f6f1b904989532a83988af0ea661a, baseline d0054d672ff0ebf6116cee27bae3fc2591c726af -- I have no idea if the bug was fixed or the test was changed. Ian, I noticed you were hosting the testsuite results so I hope it's ok to Cc you about this bug. Can you enlighten us on whether the failing test has already been fixed? For reference here's the beginning of the failing flight 2449: [ 37.107944] BUG: unable to handle kernel paging request at 7f7f850b0098 [ 37.107944] IP: [8105eb42] fill_pmd+0x13/0xec [ 37.107944] PGD 0 [ 37.107944] Oops: [#1] SMP [ 37.107944] last sysfs file: /sys/kernel/uevent_seqnum [ 37.107944] CPU 0 [ 37.107944] Modules linked in: [last unloaded: scsi_wait_scan] [ 37.107944] Pid: 1509, comm: kstop/0 Not tainted 2.6.32.24 #1 [ 37.107944] RIP: e030:[8105eb42] [8105eb42] fill_pmd+0x13/0xec [ 37.107944] RSP: e02b:88001fd1fd20 EFLAGS: 00010082 [ 37.107944] RAX: 0ff8 RBX: c7f8 RCX: ff57a000 [ 37.107944] RDX: 8000cf4d2063 RSI: ff57a000 RDI: c7f8 [ 37.107944] RBP: 88001fd1fd40 R08: R09: 88001fc64008 [ 37.107944] R10: 0396 R11: 8103bb01 R12: 8000cf4d2063 [ 37.107944] R13: ff57a000 R14: e8fe96c8 R15: 88001fcda5d0 [ 37.107944] FS: 7fb35eb96790() GS:8800026b2000() knlGS: [ 37.107944] CS: e033 DS: ES: CR0: 8005003b [ 37.107944] CR2: 7f7f850b0098 CR3: 204a7000 CR4: 2660 [ 37.107944] DR0: DR1: DR2: [ 37.107944] DR3: DR6: 0ff0 DR7: 0400 [ 37.107944] Process kstop/0 (pid: 1509, threadinfo 88001fd1e000, task 88001fcda5d0) [ 37.107944] Stack: [ 37.107944] 88001fd1fd70 ff57a000 8000cf4d2063 e8fe96c0 [ 37.107944] 0 88001fd1fd70 8105ec40 00012ed2d067 8000cf4d2063 -- 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/84fwv9h31l@sauna.l.org
Bug#602935: xen-linux-system-2.6.32-5-xen-amd64: domU stack trace error when migrating with xen kernel 2.6.32-27
since I cannot dump a core if the machine has already crashed I dumped it right after launching the migration command it's about a 250mb file, if you cannot reproduce the bug let me know how to extract the information from the core cheers -- 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/4cda770e.9050...@siodata.it
Processed: Re: Bug#603061: laptop-mode-tools: Errormessages when activating intel-sata-powermgmt
Processing commands for cont...@bugs.debian.org: reassign 603061 linux-2.6 Bug #603061 [laptop-mode-tools] laptop-mode-tools: Errormessages when activating intel-sata-powermgmt Bug reassigned from package 'laptop-mode-tools' to 'linux-2.6'. Bug No longer marked as found in versions laptop-mode-tools/1.55-1. retitle 603061 sata error msgs when activating ALPM Bug #603061 [linux-2.6] laptop-mode-tools: Errormessages when activating intel-sata-powermgmt Changed Bug title to 'sata error msgs when activating ALPM' from 'laptop-mode-tools: Errormessages when activating intel-sata-powermgmt' thanks Stopping processing here. Please contact me if you need assistance. -- 603061: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603061 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.128941939130221.transcr...@bugs.debian.org
Bug#603083: reorder fs list on partitioning make ext4 toplist
Package: partman-base Version: 144 Severity: normal ext4 is currently listed below ext3 and above ext2, which make it really look inconsistent. ext4 with linux-2.6 = 2.6.32 is a safe choice, so it can be very well be toplisted. -- 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.36-rc6-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/20101110204835.24774.33720.report...@dual.itp.tuwien.ac.at
Bug#603084: ext4 default fs
Package: partman-base Version: 144 Severity: important pledging for: packages/partman/partman-base/debian/rules:DEFAULT_FS=ext4 ext4 is a sane default and valid choice for linux-2.6 = 2.6.32 It is the fs that the linux-2.6 team recommends as default choice for squeeze. ext4 is a safe choice and maintained upstream in the stable 2.6.32 tree. I have been told that current dpkg may be a blocker thus maintainers added to cc. -- 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.36-rc6-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/20101110205252.24825.62400.report...@dual.itp.tuwien.ac.at
Bug#603126: linux-image-2.6.32-5-486: ..post-installation script refuses to quit Running yes., needs ^c.
Package: linux-2.6 Version: 2.6.32-27 Severity: normal ...post-installation script refuses to quit Running yes., needs ^c, box boots ok, but need that damned ^c, what did I miss if I did?: The following partially installed packages will be configured: linux-image-2.6.32-5-486 No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used. Setting up linux-image-2.6.32-5-486 (2.6.32-27) ... debconf: unable to initialize frontend: Dialog debconf: (TERM is not set, so the dialog frontend is not usable.) debconf: falling back to frontend: Readline debconf: unable to initialize frontend: Readline debconf: (This frontend requires a controlling tty.) debconf: falling back to frontend: Teletype Running depmod. Running update-initramfs. update-initramfs: Generating /boot/initrd.img-2.6.32-5-486 cryptsetup: WARNING: failed to detect canonical device of /dev/hda1 cryptsetup: WARNING: could not determine root device from /etc/fstab W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. W: mdadm: no arrays defined in configuration file. Running yes. User postinst hook script [yes] died with signal 15, without coredump dpkg: error processing linux-image-2.6.32-5-486 (--configure): subprocess installed post-installation script returned error exit status 128 configured to not write apport reports Errors were encountered while processing: linux-image-2.6.32-5-486 E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up linux-image-2.6.32-5-486 (2.6.32-27) ... debconf: unable to initialize frontend: Dialog debconf: (TERM is not set, so the dialog frontend is not usable.) debconf: falling back to frontend: Readline debconf: unable to initialize frontend: Readline debconf: (This frontend requires a controlling tty.) debconf: falling back to frontend: Teletype Running depmod. Running update-initramfs. update-initramfs: Generating /boot/initrd.img-2.6.32-5-486 cryptsetup: WARNING: failed to detect canonical device of /dev/hda1 cryptsetup: WARNING: could not determine root device from /etc/fstab W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. W: mdadm: no arrays defined in configuration file. Running yes. User postinst hook script [yes] died with signal 15, without coredump dpkg: error processing linux-image-2.6.32-5-486 (--configure): subprocess installed post-installation script returned error exit status 128 Errors were encountered while processing: linux-image-2.6.32-5-486 Reading package lists... Building dependency tree... Reading state information... Reading extended state information... Initializing package states... Reading task descriptions... -- Package-specific info: ** Version: Linux version 2.6.32-5-486 (Debian 2.6.32-27) (m...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Sat Oct 30 22:14:18 UTC 2010 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-486 root=UUID=e1e5f3c4-9727-4241-978c-9c70ab0437f1 ro ** Not tainted ** Kernel log: [5.682918] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11 [5.683006] PCI: setting IRQ 11 as level-triggered [5.683034] tulip :00:0a.0: PCI INT A - Link[LNKB] - GSI 11 (level, low) - IRQ 11 [5.683704] tulip0: MII transceiver #1 config 1000 status 786d advertising 01e1. [5.703750] eth0: ADMtek Comet rev 17 at Port 0xde00, 00:04:e2:23:01:22, IRQ 11. [5.722587] Floppy drive(s): fd0 is 1.44M [5.892143] FDC 0 is a post-1991 82077 [5.925158] libata version 3.00 loaded. [6.110883] usbcore: registered new interface driver usbfs [6.114085] usbcore: registered new interface driver hub [6.119561] usbcore: registered new device driver usb [6.130634] pata_sis :00:00.1: version 0.5.2 [6.130719] pata_sis :00:00.1: can't derive routing for PCI INT A [6.137519] scsi0 : pata_sis [6.139752] scsi1 : pata_sis [6.141752] ata1: PATA max UDMA/66 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14 [6.141858] ata2: PATA max UDMA/66 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15 [6.166261] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [6.325150] ata1.00: ATA-4: FUJITSU MPE3102AT, ED-03-04, max UDMA/66 [6.325264] ata1.00: 20016348 sectors, multi 16: LBA [6.325415] ata1.00: limited to UDMA/33 due to 40-wire cable [6.340981] ata1.00: configured for UDMA/33 [6.342336] scsi 0:0:0:0: Direct-Access ATA FUJITSU MPE3102A ED-0 PQ: 0 ANSI: 5 [6.901088] ata2.00: ATAPI: SAMSUNG CD-ROM SC-140F, FB07, max UDMA/33 [6.916950] ata2.00: configured for UDMA/33 [6.985008] scsi 1:0:0:0: CD-ROMSAMSUNG CD-ROM SC-140F FB07 PQ: 0 ANSI: 5 [7.030611] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [7.032016] ACPI: PCI Interrupt Link [LNKU] enabled at IRQ 10 [7.032106] PCI: setting IRQ 10 as level-triggered [7.032133] ohci_hcd :00:01.2: PCI INT A - Link[LNKU] - GSI 10
Bug#587215: Info received and FILED only (Bug#587215: [linux-image-2.6.32-5-686])
Hello Ben, Last week I updated my Debian machine and found the Asix USB ethernet device ( 0b95:1780) still not working in Debian. I realize that it took me a long time to send you the pcap dump last time. I was on a long holiday. Anyway as said the device is still not working with the modules provided by Debian. Can you tell me what I should do now to make progress? Since I think it would be very nice if this device works once again in Debian. Best regards, Barry http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587215 On Fri, Aug 6, 2010 at 11:34 AM, ing. Barry B.F. de Graaff (debian) deb...@barrydegraaff.tk wrote: Hello Ben, Here is the pcap dump as you requested. Also the script that I use to reconfigure the network is attached. I had to update my system before I could reconfigure the kernel. Network card still not working. Cheerio Barry On Wed, Jun 30, 2010 at 8:33 AM, Debian Bug Tracking System ow...@bugs.debian.org wrote: Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #587215. If you wish to submit further information on this problem, please send it to 587215-qu...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 587215: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587215 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/aanlktinezdk3r8=gsdrvvs=fdofay_sc26pci...@mail.gmail.com