Bug#544692: linux-image-2.6.30-1-686: pcspeaker mute
On Wed, Jul 14, 2010 at 10:23:25PM CEST, Moritz Muehlenhoff j...@inutil.org said: tags 544692 moreinfo thanks On Fri, Feb 05, 2010 at 12:32:09AM +0100, Moritz Muehlenhoff wrote: On Wed, Sep 02, 2009 at 02:07:10PM +0200, Erwan David wrote: Package: linux-image-2.6.30-1-686 Version: 2.6.30-6 Severity: normal Since upgrading to 2.6.30, my pcspeaker is mute, instead beeps are sent to the soundcard which is a regeression since my sound card usually has no speaker, only a headphone from time to time. Hi, The next release of Debian (6.0, code name Squeeze) will be based on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell us whether the problem persists. If so, we should report it upstream to the kernel.org developers. The 2.6.32 kernel is available from packages.debian.org and can be installed in both Debian stable, testing and unstable installations. Did you test current kernels? Thanks, Moritz Linux anticosti 2.6.32-5-686 #1 SMP Tue Jun 1 04:59:47 UTC 2010 i686 GNU/Linux No sound emitted by beep command, either on pcskeaker or on sound card... -- Erwan -- 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/20100715070046.gb13...@trusted-logic.com
Bug#534422: X hangs with blank screen when it is in use
On Thu, Jul 15, 2010 at 10:18:29 +0800, Darren Hoo wrote: I experienced blank screen with only cursor on the screen after resume from suspension now and then before 2.6.32-17, but after I upgraded to 2.6.32-17, X hangs with blank screen when it is in use. I am sure whether it is related to this bug. Please file your own bug. here's part of syslog: Jul 15 09:58:24 debian kernel: [ 3153.980040] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung Jul 15 09:58:24 debian kernel: [ 3153.980055] render error detected, EIR: 0x Jul 15 09:58:24 debian kernel: [ 3153.980119] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 496217 at 496216) Jul 15 09:58:36 debian kernel: [ 3165.549011] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung Jul 15 09:58:36 debian kernel: [ 3165.549017] render error detected, EIR: 0x and Xorg.log: (EE) intel(0): Failed to submit batch buffer, expect rendering corruption or even a frozen display: Input/output error. When filing your own bug, please include the following information: What version of libdrm-intel1 and xserver-xorg-video-intel? Does that still happen with the versions from experimental? What about the kernel from experimental? Does the hang happen on resume, or when doing something else (what?)? If you reproduce with 2.6.34+, please grab i915_error_state from /sys/kernel/debug/dri/0/ and include it in a bug report following instructions at http://intellinuxgraphics.org/how_to_report_bug.html Thanks, Julien signature.asc Description: Digital signature
Bug#588196: b43: does not join multicast groups
Hi, On Wed, Jul 14, 2010 at 02:41:09PM +0200, Michael Büsch wrote: The same applies to receiving. The RX queue is also dropped on switch from DMA to PIO. Sure, but the packet is repeated every ten seconds. The problem is that none of those packets is received, even long after the switch to PIO. advertisement, sent to 33:33:00:00:00:01). I have no idea where the packet is dropped; from my somewhat limited understanding of 802.11, I'd expect the frames to be treated like broadcast frames by the AP, so it'd be the receiver dropping them in the MAC filter. The actual switch from DMA to PIO mode completely reinitializes the hardware and drops all queues. Would it be possible to reinitialize the multicast filter at this point? Simon -- 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/20100715085149.ga9...@richter
Bug#534422: X hangs with blank screen when it is in use
On Thu, Jul 15, 2010 at 4:38 PM, Julien Cristau jcris...@debian.org wrote: On Thu, Jul 15, 2010 at 10:18:29 +0800, Darren Hoo wrote: I experienced blank screen with only cursor on the screen after resume from suspension now and then before 2.6.32-17, but after I upgraded to 2.6.32-17, X hangs with blank screen when it is in use. I am sure whether it is related to this bug. Please file your own bug. Sorry to have provided useless non-related information, Filing my own bug will only waste more of your time to triage or merge of the bug. When filing your own bug, please include the following information: What version of libdrm-intel1 and xserver-xorg-video-intel? Does that still happen with the versions from experimental? What about the kernel from experimental? Does the hang happen on resume, or when doing something else (what?)? If you reproduce with 2.6.34+, please grab i915_error_state from /sys/kernel/debug/dri/0/ and include it in a bug report following instructions at http://intellinuxgraphics.org/how_to_report_bug.html I haven't experienced hang up for a while, Next time if the symptom reappears I shall prepare my own bug report as detailed as possible following your guides above. 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/aanlktinm87klnxrpmtsglz5wyiv_6uwxuxyiiswqf...@mail.gmail.com
Bug#588196: b43: does not join multicast groups
On 07/15/2010 10:51 AM, Simon Richter wrote: The same applies to receiving. The RX queue is also dropped on switch from DMA to PIO. Sure, but the packet is repeated every ten seconds. The problem is that none of those packets is received, even long after the switch to PIO. The filter flags are not updated because (as I already said) the reinit happens without mac80211's knowledge. The actual switch from DMA to PIO mode completely reinitializes the hardware and drops all queues. Would it be possible to reinitialize the multicast filter at this point? Yeah everything is possible. I'd rather like to see the actual _problem_ fixed instead of continuing to waste hours and hours on the hackish workaround. So in the end the workaround (aka PIO fallback) can be removed. If this problem is fixed, the next one will show up. (For example the fact that the PIO fallback won't work on an AP, too, for these reasons). Please work on fixing up the PCI core code, which most likely causes the problem, instead of extending the workaround hack. -- Greetings 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/4c3f10dd.70...@bu3sch.de
Bug#588509: linux-image-2.6.32-5-amd64: hangs under Xen after Write protecting the kernel read-only data: 4220k
Sorry, I forgot to include Xen version number information: $ sudo xm info host : overlord2 release: 2.6.31.12-0.2-xen version: #1 SMP 2010-03-16 21:25:39 +0100 machine: x86_64 nr_cpus: 4 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz: 2394 hw_caps: bfebfbff:20100800::0140:e3bd::0001: virt_caps : hvm total_memory : 8189 free_memory: 16 max_free_memory: 2420 max_para_memory: 2416 max_hvm_memory : 2402 node_to_cpu: node0:0-3 node_to_memory : node0:16 xen_major : 3 xen_minor : 4 xen_extra : .1_19718_04-2.1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params: virt_start=0x8000 xen_changeset : 19718 cc_compiler: gcc version 4.4.1 [gcc-4_4-branch revision 150839] (SUSE Linux) cc_compile_by : abuild cc_compile_domain : cc_compile_date: Tue Oct 27 16:31:01 UTC 2009 xend_config_format : 4 (If these look odd it is because Dom0 runs openSUSE 11.2) -- 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/84fwzkizf2@sauna.l.org
Bug#589178: linux-image-2.6.32-5-amd64: regression: kernel does not boot in kvm after update
Package: linux-2.6 Version: 2.6.32-17 Severity: normal after updating linux-image-2.6.32-5-amd64 from 2.6.32-15 to 2.6.32-17 the kernel doesn't boot in a lenny kvm anymore. the attached info is gathered from the working version! -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-15) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-1) ) #1 SMP Tue Jun 1 04:34:03 UTC 2010 ** Command line: console=ttyS0,115200n8 root=/dev/sda ro verbose debug ** Not tainted ** Kernel log: [0.900948] TCP cubic registered [0.901555] NET: Registered protocol family 10 [0.912884] lo: Disabled Privacy Extensions [0.913630] Mobile IPv6 [0.914055] NET: Registered protocol family 17 [0.924810] PM: Resume from disk failed. [0.925328] registered taskstats version 1 [0.926221] rtc_cmos 00:01: setting system clock to 2010-07-15 14:45:19 UTC (1279205119) [0.937395] Initalizing network drop monitor service [0.948249] Freeing unused kernel memory: 584k freed [0.949063] Write protecting the kernel read-only data: 4208k [0.976066] udev: starting version 158 [0.997972] 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004) [1.051407] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 [1.056672] SCSI subsystem initialized [1.063379] 8139cp :00:03.0: PCI INT A - Link[LNKC] - GSI 11 (level, high) - IRQ 11 [1.074153] libata version 3.00 loaded. [1.076610] FDC 0 is a S82078B [1.081377] eth0: RTL-8139C+ at 0xc95be000, 52:54:00:12:34:56, IRQ 11 [1.092704] 8139cp :00:03.0: setting latency timer to 64 [1.103751] ata_piix :00:01.1: version 2.13 [1.104942] ata_piix :00:01.1: setting latency timer to 64 [1.106323] 8139too Fast Ethernet driver 0.9.28 [1.117807] scsi0 : ata_piix [1.118708] scsi1 : ata_piix [1.129787] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc000 irq 14 [1.131560] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc008 irq 15 [1.296707] ata1.00: ATA-7: QEMU HARDDISK, 0.9.1, max UDMA/100 [1.307723] ata1.00: 20971520 sectors, multi 16: LBA48 [1.308623] ata1.01: ATA-7: QEMU HARDDISK, 0.9.1, max UDMA/100 [1.309440] ata2.00: ATA-7: QEMU HARDDISK, 0.9.1, max UDMA/100 [1.309443] ata2.00: 20971520 sectors, multi 16: LBA48 [1.310065] ata2.00: configured for MWDMA2 [1.332566] ata1.01: 20971520 sectors, multi 16: LBA48 [1.344415] ata1.00: configured for MWDMA2 [1.345691] ata1.01: configured for MWDMA2 [1.346584] scsi 0:0:0:0: Direct-Access ATA QEMU HARDDISK0.9. PQ: 0 ANSI: 5 [1.358465] scsi 0:0:1:0: Direct-Access ATA QEMU HARDDISK0.9. PQ: 0 ANSI: 5 [1.370542] scsi 1:0:0:0: Direct-Access ATA QEMU HARDDISK0.9. PQ: 0 ANSI: 5 [1.392779] sd 0:0:0:0: [sda] 20971520 512-byte logical blocks: (10.7 GB/10.0 GiB) [1.396259] sd 0:0:1:0: [sdb] 20971520 512-byte logical blocks: (10.7 GB/10.0 GiB) [1.396304] sd 0:0:1:0: [sdb] Write Protect is off [1.396306] sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00 [1.396325] sd 0:0:1:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [1.396437] sdb: sdb1 sdb2 [1.397368] sd 1:0:0:0: [sdc] 20971520 512-byte logical blocks: (10.7 GB/10.0 GiB) [1.397410] sd 1:0:0:0: [sdc] Write Protect is off [1.397412] sd 1:0:0:0: [sdc] Mode Sense: 00 3a 00 00 [1.397429] sd 1:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [1.397534] sdc: sdb5 [1.466413] sdc1 [1.466598] sd 0:0:0:0: [sda] Write Protect is off [1.466600] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [1.466623] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [1.489937] sdc2 [1.500510] sda: [1.501850] sd 0:0:0:0: [sda] Attached SCSI disk [1.503037] sd 0:0:1:0: [sdb] Attached SCSI disk [1.520403] sdc5 [1.521726] sd 1:0:0:0: [sdc] Attached SCSI disk [2.069791] kjournald starting. Commit interval 5 seconds [2.069821] EXT3-fs: mounted filesystem with ordered data mode. [3.424379] udev: starting version 158 [4.117523] processor LNXCPU:00: registered as cooling_device0 [4.120759] ACPI Warning for \_PR_.CPU1._MAT: Return type mismatch - found Integer, expected Buffer (20090903/nspredef-1006) [4.136475] processor LNXCPU:01: registered as cooling_device1 [4.148663] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 [4.161483] ACPI: Power Button [PWRF] [4.162320] ACPI Warning for \_PR_.CPU2._MAT: Return type mismatch - found Integer, expected Buffer (20090903/nspredef-1006) [4.175183] ACPI Warning for \_PR_.CPU3._MAT: Return type mismatch - found Integer, expected Buffer (20090903/nspredef-1006) [4.189702] ACPI Warning for \_PR_.CPU4._MAT: Return type mismatch - found Integer, expected Buffer (20090903/nspredef-1006) [4.203816] ACPI Warning for
Processed: forcibly merging 588426 589178
Processing commands for cont...@bugs.debian.org: forcemerge 588426 589178 Bug#588426: linux-image-2.6.32-5-amd64: fail to boot in a kvm virtual machine Bug#589178: linux-image-2.6.32-5-amd64: regression: kernel does not boot in kvm after update Forcibly Merged 588426 589178. thanks Stopping processing here. Please contact me if you need assistance. -- 589178: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589178 588426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588426 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.127920832432642.transcr...@bugs.debian.org
Processed: forcibly merging 588426 589178
Processing commands for cont...@bugs.debian.org: forcemerge 588426 589178 Bug#588426: linux-image-2.6.32-5-amd64: fail to boot in a kvm virtual machine Bug#589178: linux-image-2.6.32-5-amd64: regression: kernel does not boot in kvm after update Forcibly Merged 588426 589178. thanks Stopping processing here. Please contact me if you need assistance. -- 589178: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589178 588426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588426 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.12792087363317.transcr...@bugs.debian.org
Bug#589179: linux-image-2.6.26-2-686: heap base address is not randomised when randomize_va_space is set to 2
Package: linux-2.6
Version: 2.6.26-24
Severity: normal
Hi,
When running the latest stable Debian kernel the base address of a heap is not
randomised regardless of the
setting for randomize_va_space (it is set to 2 by default). This can be
observed by using a simple .c
program (below) or using the paxtest suite available from here:
http://grsecurity.net/~spender/paxtest-0.9.9.tgz
Please bear in mind that I only have tested this within virtualised environment
and I have only tested a x86 system.
sample c program I used:
#include stdio.h
#include stdlib.h
void main() {
char * p = (char *) malloc(40*sizeof(char));
printf(address: %x\n,p);
}
compile and run:
gcc -o heap heap.c
watch -n 1 ./heap
reproducible: always
steps to reproduce:
- compile and run paxtest or simple .c program from above
expected results:
- randomised addressed for heap allocations - address of the malloc'ed var
should be different each time the program is run.
For the paxtest - it should not report 'no randomisation' for 'Heap
randomisation test (ET_EXEC)'
actual results:
- no randomisation of the heap base addresses.
-- Package-specific info:
** Version:
Linux version 2.6.26-2-686 (Debian 2.6.26-24) (da...@debian.org) (gcc version
4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Mon Jun 21 05:58:44 UTC
2010
** Command line:
root=/dev/hda1 ro quiet
** Not tainted
** Kernel log:
[5.227996] usb 1-1: new full speed USB device using uhci_hcd and address 2
[5.485259] PM: Starting manual resume from disk
[5.517670] EXT3-fs: INFO: recovery required on readonly filesystem.
[5.517674] EXT3-fs: write access will be enabled during recovery.
[5.590701] usb 1-1: configuration #1 chosen from 1 choice
[5.643904] usb 1-1: New USB device found, idVendor=0627, idProduct=0001
[5.643909] usb 1-1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[5.643912] usb 1-1: Product: QEMU USB Tablet
[5.643914] usb 1-1: Manufacturer: QEMU 0.12.4
[5.643916] usb 1-1: SerialNumber: 1
[5.710778] usbcore: registered new interface driver hiddev
[5.735324] input: QEMU 0.12.4 QEMU USB Tablet as /class/input/input1
[5.739330] input,hidraw0: USB HID v0.01 Pointer [QEMU 0.12.4 QEMU USB
Tablet] on usb-:00:01.2-1
[5.739330] usbcore: registered new interface driver usbhid
[5.739330] usbhid: v2.6:USB HID core driver
[6.359345] kjournald starting. Commit interval 5 seconds
[6.359345] EXT3-fs: recovery complete.
[6.359345] EXT3-fs: mounted filesystem with ordered data mode.
[9.039926] udevd version 125 started
[9.809803] udev: renamed network interface eth0 to eth6
[ 10.587020] piix4_smbus :00:01.3: Found :00:01.3 device
[ 10.797426] input: Power Button (FF) as /class/input/input2
[ 10.828746] ACPI: Power Button (FF) [PWRF]
[ 11.152352] input: PC Speaker as /class/input/input3
[ 11.368600] input: ImExPS/2 Generic Explorer Mouse as /class/input/input4
[ 11.472414] parport_pc 00:05: reported by Plug and Play ACPI
[ 11.472414] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
[ 12.741775] Adding 489940k swap on /dev/hda5. Priority:-1 extents:1
across:489940k
[ 113.697388] EXT3 FS on hda1, internal journal
[ 114.415953] loop: module loaded
[ 121.243828] NET: Registered protocol family 10
[ 121.246126] lo: Disabled Privacy Extensions
[ 122.529155] lp0: using parport0 (interrupt-driven).
[ 122.667535] ppdev: user-space parallel port driver
[ 126.465548] eth6: link up, 100Mbps, full-duplex, lpa 0x05E1
[ 144.751798] eth6: no IPv6 routers present
[ 808.293430] BUG: soft lockup - CPU#0 stuck for 104s! [swapper:0]
[ 808.293430] Modules linked in: ppdev lp ipv6 cpufreq_ondemand cpufreq_stats
freq_table cpufreq_userspace cpufreq_powersave cpufreq_conservative loop
parport_pc parport pcspkr psmouse serio_raw button i2c_piix4 i2c_core joydev
evdev usbhid hid ff_memless ext3 jbd mbcache ide_cd_mod cdrom ide_disk
ata_generic libata scsi_mod 8139too dock floppy 8139cp mii uhci_hcd piix
ide_pci_generic usbcore ide_core thermal processor fan thermal_sys [last
unloaded: scsi_wait_scan]
[ 808.293430]
[ 808.293430] Pid: 0, comm: swapper Not tainted (2.6.26-2-686 #1)
[ 808.293430] EIP: 0060:[c0114d94] EFLAGS: 0246 CPU: 0
[ 808.293430] EIP is at native_safe_halt+0x2/0x3
[ 808.293430] EAX: c0378000 EBX: c010265b ECX: 0104f000 EDX: 00012276
[ 808.293430] ESI: EDI: c036c000 EBP: 00847007 ESP: c0379fe0
[ 808.293430] DS: 007b ES: 007b FS: 00d8 GS: SS: 0068
[ 808.293430] CR0: 8005003b CR2: 085643ac CR3: 0ae94000 CR4: 06d0
[ 808.293430] DR0: DR1: DR2: DR3:
[ 808.293430] DR6: 0ff0 DR7: 0400
[ 808.293430] [c0102688] ? default_idle+0x2d/0x53
[ 808.293430] [c01025d3] ? cpu_idle+0xb0/0xd0
[ 808.293430] ===
[ 978.033743] BUG: soft lockup - CPU#1 stuck for 158s! [dbus-daemon:2067]
[ 978.033743] Modules linked in: ppdev lp ipv6 cpufreq_ondemand cpufreq_stats
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 #576800 (http://bugs.debian.org/576800) # * http://bugzilla.kernel.org/show_bug.cgi?id=13811 # * remote status changed: (?) - CLOSED # * remote resolution changed: (?) - CODE-FIX # * closed upstream tags 576800 + fixed-upstream Bug #576800 [linux-2.6] libc6: Cannot create new processes after hibernating 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 #571741 [linux-2.6] System freezes after pm-hibernate when kms is on Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. usertags 576800 + status-CLOSED resolution-CODE-FIX Bug#576800: libc6: Cannot create new processes after hibernating There were no usertags set. Usertags are now: resolution-CODE-FIX status-CLOSED. # remote status report for #534904 (http://bugs.debian.org/534904) # * http://bugzilla.kernel.org/show_bug.cgi?id=13591 # * remote status changed: (?) - NEEDINFO usertags 534904 + status-NEEDINFO Bug#534904: linux-image-2.6.26-2-686: acpi_cpufreq and snd_atiixp conflict (was #362708) There were no usertags set. Usertags are now: status-NEEDINFO. # remote status report for #576800 (http://bugs.debian.org/576800) # * http://bugzilla.kernel.org/show_bug.cgi?id=13811 # * remote status changed: (?) - CLOSED # * remote resolution changed: (?) - CODE-FIX # * closed upstream tags 576800 + fixed-upstream Bug #576800 [linux-2.6] libc6: Cannot create new processes after hibernating 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 #571741 [linux-2.6] System freezes after pm-hibernate when kms is on Ignoring request to alter tags of bug #576800 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 #571741 to the same tags previously set usertags 576800 + status-CLOSED resolution-CODE-FIX Bug#576800: libc6: Cannot create new processes after hibernating Usertags were: resolution-CODE-FIX status-CLOSED. Usertags are now: resolution-CODE-FIX status-CLOSED. # remote status report for #576800 (http://bugs.debian.org/576800) # * http://bugzilla.kernel.org/show_bug.cgi?id=13811 # * remote status changed: (?) - CLOSED # * remote resolution changed: (?) - CODE-FIX # * closed upstream tags 576800 + fixed-upstream Bug #576800 [linux-2.6] libc6: Cannot create new processes after hibernating 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 #571741 [linux-2.6] System freezes after pm-hibernate when kms is on Ignoring request to alter tags of bug #576800 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 #571741 to the same tags previously set usertags 576800 + status-CLOSED resolution-CODE-FIX Bug#576800: libc6: Cannot create new processes after hibernating Usertags were: resolution-CODE-FIX status-CLOSED. Usertags are now: resolution-CODE-FIX status-CLOSED. # remote status report for #576800 (http://bugs.debian.org/576800) # * http://bugzilla.kernel.org/show_bug.cgi?id=13811 # * remote status changed: (?) - CLOSED # * remote resolution changed: (?) - CODE-FIX # * closed upstream tags 576800 + fixed-upstream Bug #576800 [linux-2.6] libc6: Cannot create new processes after hibernating 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
[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 #576800 (http://bugs.debian.org/576800) # * http://bugzilla.kernel.org/show_bug.cgi?id=13811 # * remote status changed: (?) - CLOSED # * remote resolution changed: (?) - CODE-FIX # * closed upstream tags 576800 + fixed-upstream usertags 576800 + status-CLOSED resolution-CODE-FIX # remote status report for #534904 (http://bugs.debian.org/534904) # * http://bugzilla.kernel.org/show_bug.cgi?id=13591 # * remote status changed: (?) - NEEDINFO usertags 534904 + status-NEEDINFO # remote status report for #576800 (http://bugs.debian.org/576800) # * http://bugzilla.kernel.org/show_bug.cgi?id=13811 # * remote status changed: (?) - CLOSED # * remote resolution changed: (?) - CODE-FIX # * closed upstream tags 576800 + fixed-upstream usertags 576800 + status-CLOSED resolution-CODE-FIX # remote status report for #576800 (http://bugs.debian.org/576800) # * http://bugzilla.kernel.org/show_bug.cgi?id=13811 # * remote status changed: (?) - CLOSED # * remote resolution changed: (?) - CODE-FIX # * closed upstream tags 576800 + fixed-upstream usertags 576800 + status-CLOSED resolution-CODE-FIX # remote status report for #576800 (http://bugs.debian.org/576800) # * http://bugzilla.kernel.org/show_bug.cgi?id=13811 # * remote status changed: (?) - CLOSED # * remote resolution changed: (?) - CODE-FIX # * closed upstream tags 576800 + fixed-upstream usertags 576800 + status-CLOSED resolution-CODE-FIX # remote status report for #576800 (http://bugs.debian.org/576800) # * http://bugzilla.kernel.org/show_bug.cgi?id=13811 # * remote status changed: (?) - CLOSED # * remote resolution changed: (?) - CODE-FIX # * closed upstream tags 576800 + fixed-upstream usertags 576800 + status-CLOSED resolution-CODE-FIX 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/20100715163254.19205.12647.btsl...@merkel.debian.org
2.6.35-rc5-686, nouveau, stumpwm - cleanest boot
2.6.35-rc5-686 is loading without any errors. at least without any errors that I can find... 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/692095.81192...@web35603.mail.mud.yahoo.com
Bug#589118: `rdev` setting ignored
reopen 589118 quit From: Ben Hutchings b...@decadent.org.uk On Wed, 2010-07-14 at 18:11 -0700, Elliott Mitchell wrote: Package: initramfs-tools Version: 0.92o Subject tells the story. Appears the images generated by initramfs-tools completely ignore the `rdev` setting that the kernel was given to the kernel. While 99% of users may be explicitly passing the root device via passing root=/dev/foo through the bootloader, if that is absent one would think the value from `rdev` would be honored. (yeah, it's an ancient method, but not officially deprecated) If the bootloader passes an initramfs to the kernel, that overrides any rdev parameter. This is nothing to do with the contents of the initramfs. Bzzzt! While the initrd= kernel command-line option and `rdev` kernel settings are not completely orthogonal, they are mostly unrelated. The initrd= option overrides the `rdev` setting in the same fashion the initrd= option overrides the root= and all other kernel command-line options. Mainly, the initramfs can ignore any and all options and use ones built in, or it can implement all those options. It is the root= option that is directly related to `rdev`. Unlike the kernel command-line, I don't know how the `rdev` (and accompanying) setting is passed along to initial ram disks, but I do know it is (or was). I'm unsure whether Debian 4.0/Etch honored the `rdev` setting, but I am pretty certain initial ram disks generated with Debian 3.1/Sage did honor the `rdev` setting unless overridden by the root= option. -- (\___(\___(\__ --= 8-) EHM =-- __/)___/)___/) \BS (| e...@gremlin.m5p.com PGP F6B23DE0 |) / \_CS\ | _ -O #include stddisclaimer.h O- _ | / _/ 2477\___\_|_/DC21 03A0 5D61 985B -PGP- F2BE 6526 ABD2 F6B2\_|_/___/3DE0 -- 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/201007152048.o6fkm7n7071...@m5p.com
Processed: Keep #589118
Processing commands for cont...@bugs.debian.org:
reopen 589118
Bug #589118 {Done: Ben Hutchings b...@decadent.org.uk} [initramfs-tools]
`rdev` setting ignored
quit
Stopping processing here.
Please contact me if you need assistance.
--
589118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589118
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.127922922315559.transcr...@bugs.debian.org
Bug#589231: linux-image-2.6.32-5-powerpc: pmu_battery is not loaded automatically, so ibook battery detection does not work
Package: linux-2.6 Version: 2.6.32-15 Severity: normal The pmu_battery module is not loaded so ibook battery detection does not work (e.g. the GNOME power applet always report that the laptop is connected to the AC adapter and has no battery). To fix the problem just do modprobe pmu_battery. It will be great to have a native detection of ibook g4 battery. FYI this has already been reported by someone else to Ubuntu (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/552597), but I see the exactly same problem in Debian testing (squeeze). -- Package-specific info: ** Version: Linux version 2.6.32-5-powerpc (Debian 2.6.32-15) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-1) ) #1 Tue Jun 1 09:13:17 UTC 2010 ** Command line: root=/dev/hda5 ro ** Not tainted ** Kernel log: [ 1771.242279] ohci_hcd 0001:10:1b.0: restoring config space at offset 0x1 (was 0x210, writing 0x212) [ 1771.242314] ohci_hcd 0001:10:1b.1: restoring config space at offset 0x1 (was 0x210, writing 0x212) [ 1771.242349] ehci_hcd 0001:10:1b.2: restoring config space at offset 0x1 (was 0x210, writing 0x2100012) [ 1771.258170] radeonfb (:00:10.0): resuming from state: 2... [ 1771.978005] agpgart-uninorth :00:0b.0: putting AGP V2 device into 4x mode [ 1771.978014] radeonfb :00:10.0: putting AGP V2 device into 4x mode [ 1773.161978] eth0: resuming [ 1773.226321] PHY ID: 4061e4, addr: 0 [ 1774.360254] hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [ 1774.361760] adb: starting probe task... [ 1774.366033] hda: UDMA/100 mode selected [ 1774.369782] hdc: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [ 1774.369913] hdc: MWDMA2 mode selected [ 1774.387463] adb devices: [2]: 2 c4 [7]: 7 1f [ 1774.392358] ADB keyboard at 2, handler 1 [ 1774.392363] adb: finished probe task... [ 1774.665982] usb 2-2: reset full speed USB device using ohci_hcd and address 3 [ 1774.832993] appletouch: Geyser mode initialized. [ 1774.886061] PM: Finishing wakeup. [ 1774.886067] Restarting tasks ... done. [ 1775.531053] agpgart-uninorth :00:0b.0: putting AGP V2 device into 4x mode [ 1775.531067] radeonfb :00:10.0: putting AGP V2 device into 4x mode [ 1775.531179] [drm] Num pipes: 1 [ 1775.731134] [drm] Num pipes: 1 [ 1776.878455] PM: Syncing filesystems ... done. [ 1777.338054] PM: Preparing system for mem sleep [ 1777.338073] Freezing user space processes ... (elapsed 0.00 seconds) done. [ 1777.342846] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done. [ 1777.342929] PM: Entering mem sleep [ 1777.342933] Suspending console(s) (use no_console_suspend to debug) [ 1777.344032] btusb_intr_complete: hci0 urb eb9cfc00 failed to resubmit (1) [ 1777.344993] btusb_bulk_complete: hci0 urb eb9cf000 failed to resubmit (1) [ 1777.345994] btusb_bulk_complete: hci0 urb eb9cf980 failed to resubmit (1) [ 1778.343137] eth0: suspending, WakeOnLan disabled [ 1778.422073] radeonfb (:00:10.0): suspending for event: 2... [ 1778.422111] agpgart-uninorth :00:0b.0: disabling AGP on device :00:10.0 [ 1778.422132] agpgart-uninorth :00:0b.0: disabling AGP on bridge [ 1778.919597] radeonfb :00:10.0: restoring config space at offset 0xc (was 0x0, writing 0x90020001) [ 1778.919612] radeonfb :00:10.0: restoring config space at offset 0x6 (was 0x0, writing 0x9000) [ 1778.919619] radeonfb :00:10.0: restoring config space at offset 0x5 (was 0x1, writing 0x401) [ 1778.919626] radeonfb :00:10.0: restoring config space at offset 0x4 (was 0x8, writing 0x9808) [ 1778.919633] radeonfb :00:10.0: restoring config space at offset 0x3 (was 0x0, writing 0xff08) [ 1778.919640] radeonfb :00:10.0: restoring config space at offset 0x1 (was 0x2b0, writing 0x2b7) [ 1778.919685] b43-pci-bridge 0001:10:12.0: restoring config space at offset 0x4 (was 0x0, writing 0x80084000) [ 1778.919692] b43-pci-bridge 0001:10:12.0: restoring config space at offset 0x3 (was 0x0, writing 0x1000) [ 1778.919700] b43-pci-bridge 0001:10:12.0: restoring config space at offset 0x1 (was 0x0, writing 0x6) [ 1778.921782] ohci_hcd 0001:10:1b.0: restoring config space at offset 0x1 (was 0x210, writing 0x212) [ 1778.921817] ohci_hcd 0001:10:1b.1: restoring config space at offset 0x1 (was 0x210, writing 0x212) [ 1778.921851] ehci_hcd 0001:10:1b.2: restoring config space at offset 0x1 (was 0x210, writing 0x2100012) [ 1778.937692] radeonfb (:00:10.0): resuming from state: 2... [ 1779.657530] agpgart-uninorth :00:0b.0: putting AGP V2 device into 4x mode [ 1779.657539] radeonfb :00:10.0: putting AGP V2 device into 4x mode [ 1780.841507] eth0: resuming [ 1780.905844] PHY ID: 4061e4, addr: 0 [ 1782.039635] hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [ 1782.041143] adb: starting probe task... [ 1782.045537] hda: UDMA/100 mode selected [ 1782.049192] hdc: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [ 1782.049322] hdc: MWDMA2 mode selected [
[Fwd: Processed: Keep #589118]
Please ban Elliott Mitchell e...@m5p.com from the BTS, as it seems he
likes to play bug ping-pong.
Ben.
Forwarded Message
From: Debian Bug Tracking System ow...@bugs.debian.org
To: Elliott Mitchell e...@m5p.com
Cc: Debian kernel team debian-kernel@lists.debian.org
Subject: Processed: Keep #589118
Date: Thu, 15 Jul 2010 21:30:03 +
Processing commands for cont...@bugs.debian.org:
reopen 589118
Bug #589118 {Done: Ben Hutchings b...@decadent.org.uk} [initramfs-tools]
`rdev` setting ignored
quit
Stopping processing here.
Please contact me if you need assistance.
--
589118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589118
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.127922922315559.transcr...@bugs.debian.org
--
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: closing 589118
Processing commands for cont...@bugs.debian.org: close 589118 Bug#589118: `rdev` setting ignored 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Elliott Mitchell e...@m5p.com thanks Stopping processing here. Please contact me if you need assistance. -- 589118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589118 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.12792320191276.transcr...@bugs.debian.org
nfs-utils_1.2.2-1.1_i386.changes REJECTED
Reject Reasons: nfs-utils_1.2.2-1.1.dsc: old version (1:1.2.2-2) in unstable = new version (1:1.2.2-1.1) targeted at unstable. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. -- 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/e1ozwko-0004xs...@franck.debian.org
Bug#525220: Bluetooth Device: hci_cmd_task: hci0 command tx timeout
Moritz Muehlenhoff wrote: The next release of Debian (6.0, code name Squeeze) will be based on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell us whether the problem persists. Hello Moritz. I am testing with kernel 2.6.32-5-486 I am getting the timeout here, so I reckon this is still broken in Squeeze. # hciconfig -a hci0: Type: BR/EDR Bus: USB BD Address: 00:1F:81:00:01:1C ACL MTU: 1021:4 SCO MTU: 180:1 UP RUNNING RX bytes:330 acl:0 sco:0 events:8 errors:0 TX bytes:24 acl:0 sco:0 commands:16 errors:8 Features: 0xff 0x3e 0x09 0x76 0x80 0x01 0x00 0x80 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: Link mode: SLAVE ACCEPT Can't read local name on hci0: Connection timed out (110) # dmesg [127422.591465] hci_cmd_task: hci0 command tx timeout # lsusb Bus 003 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) I tried updating to bluez-4.69, which I downloaded from an upstream source and compiled myself, but the problem still persists. Mark. -- 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/638868.87901...@web26504.mail.ukl.yahoo.com
Bug#580050: linux-image-2.6.32-3-amd64: kcryptd crashes under , heavy I/O
Can be closed since it was a hardware problem. Hello, this turned out to be a hardware problem after all. With different hardware everything works just fine. Regards, Juha -- 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/4c3f9ca4.8090...@wc3edit.net
Bug#589231: linux-image-2.6.32-5-powerpc: pmu_battery is not loaded automatically, so ibook battery detection does not work
On Thu, 2010-07-15 at 23:46 +0200, Lino Mastrodomenico wrote: Package: linux-2.6 Version: 2.6.32-15 Severity: normal The pmu_battery module is not loaded so ibook battery detection does not work (e.g. the GNOME power applet always report that the laptop is connected to the AC adapter and has no battery). To fix the problem just do modprobe pmu_battery. It will be great to have a native detection of ibook g4 battery. FYI this has already been reported by someone else to Ubuntu (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/552597), but I see the exactly same problem in Debian testing (squeeze). [...] Did this work in an earlier kernel version? 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: tagging 589231
Processing commands for cont...@bugs.debian.org: tags 589231 moreinfo Bug #589231 [linux-2.6] linux-image-2.6.32-5-powerpc: pmu_battery is not loaded automatically, so ibook battery detection does not work Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 589231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589231 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.12792428616558.transcr...@bugs.debian.org
Processed: tagging 589179
Processing commands for cont...@bugs.debian.org: tags 589179 security Bug #589179 [linux-2.6] linux-image-2.6.26-2-686: heap base address is not randomised when randomize_va_space is set to 2 Added tag(s) security. thanks Stopping processing here. Please contact me if you need assistance. -- 589179: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589179 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.12792430617971.transcr...@bugs.debian.org
Processed: tagging 589179
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 589179 + pending Bug #589179 [linux-2.6] linux-image-2.6.26-2-686: heap base address is not randomised when randomize_va_space is set to 2 Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 589179: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589179 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.1279247571581.transcr...@bugs.debian.org
Bug#589179: linux-image-2.6.26-2-686: heap base address is not randomised when randomize_va_space is set to 2
On Thu, 2010-07-15 at 17:18 +0100, Radoslaw Madej wrote: Package: linux-2.6 Version: 2.6.26-24 Severity: normal Hi, When running the latest stable Debian kernel the base address of a heap is not randomised regardless of the setting for randomize_va_space (it is set to 2 by default). This can be observed by using a simple .c program (below) or using the paxtest suite available from here: http://grsecurity.net/~spender/paxtest-0.9.9.tgz Good spot. At the point where heap randomisation should be done, PF_RANDOMIZE has been cleared. This seems to be a regression due to the fix for CVE-2010-0307. We need to apply the follow-up patch: commit 7ab02af428c2d312c0cf8fb0b01cc1eb21131a3d Author: Linus Torvalds torva...@linux-foundation.org Date: Tue Feb 2 12:37:44 2010 -0800 Fix 'flush_old_exec()/setup_new_exec()' split 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
