Processed: tagging 529312
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny3 > tags 529312 + pending Bug#529312: linux-image-2.6.26-2-686-bigmem: Does not recognize all CPUs on "summit" SMP machines Tags were: pending Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#532376: r8169: network buffer overflow
On tiisdei 9 Juny 2009, Ben Hutchings wrote: > Package: linux-2.6 > Version: 2.6.29-5 > Severity: critical > Tags: security patch > > Some or all NICs supported by r8169 seem to ignore the buffer sizes in > RX descriptors, and will write up to the global maximum frame size. > This means a remote attacker can overflow RX buffers, probably > allowing for code injection. This should be fixed by the patch posted > in: > > http://article.gmane.org/gmane.linux.network/130114 This is CVE-2009-1389. The severity of this issue is still debated. Thijs signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#532153: [Pkg-samba-maint] Bug#532153: Bug#532153: smbfs: fsetxattr fails with smbmount from Debian/amd64 to Debian/i386
Processing commands for cont...@bugs.debian.org: > reassign 532153 linux-2.6 Bug#532153: smbfs: fsetxattr fails with smbmount from Debian/amd64 to Debian/i386 Bug reassigned from package `smbfs' to `linux-2.6'. > retitle 532153 cifs reports EACCES instead of EOPNOTSUPP for acls Bug#532153: smbfs: fsetxattr fails with smbmount from Debian/amd64 to Debian/i386 Changed Bug title to `cifs reports EACCES instead of EOPNOTSUPP for acls' from `smbfs: fsetxattr fails with smbmount from Debian/amd64 to Debian/i386'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging 524300
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny3 > tags 524300 + pending Bug#524300: linux-image-2.6.26-2-686: cannot turn wireless RF on/off on Asus U3S notebook when asus_acpi module is loaded Tags were: fixed-upstream upstream patch Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging 514268
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny3 > tags 514268 + pending Bug#514268: linux-source-2.6.26: Realtek network card driver (r8169) doesn't handle multicast Tags were: fixed-upstream upstream patch Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging 498271
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny3 > tags 498271 + pending Bug#498271: linux-image-2.6.26-1-amd64: the SATA CDROM isn't detected Tags were: patch Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging 530884
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny3 > tags 530884 + pending Bug#530884: linux-image-2.6.26-2-686: terminals flooded by "Bad: scheduling from hte idle thread" message Tags were: patch fixed-upstream upstream Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#532386: XFS on LVM2 filesystem crashses
Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-15lenny3 Followup-For: Bug #512779 Yesterday we made an upgrade of our samba servers previuosl we had similar configuration but server was build on Intel Server Board and the same PERC controller. Then it was 32 bit Linux (Gentoo) and only one MD1000 array. We had similar issues.. So we upgraded system to 64bits Debian Lenny. WE also extended system with one more array. Main Filesystem is LVM2 based: storage:~# pvs PV VGFmt Attr PSize PFree /dev/sdc storage01 lvm2 a- 1.91T0 /dev/sdd storage01 lvm2 a- 1.91T0 /dev/sde storage01 lvm2 a- 1.91T0 /dev/sdf storage01 lvm2 a- 1.91T0 /dev/sdg storage01 lvm2 a- 1.91T 4.00M /dev/sdh storage01 lvm2 a- 1.91T0 storage:~# vgs VG#PV #LV #SN Attr VSize VFree storage01 6 1 0 wz--n- 11.45T 4.00M storage:~# lvdisplay --- Logical volume --- LV Name/dev/storage01/storage01logical VG Namestorage01 LV UUIDaY42UL-j0NN-8fPa-jwIZ-OH1I-QPWz-Z20jfu LV Write Accessread/write LV Status available # open 1 LV Size11.45 TB Current LE 3000699 Segments 6 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:0 Filesystem on it is XFS: storage:~# xfs_info /dev/mapper/storage01-storage01logical meta-data=/dev/mapper/storage01-storage01logical isize=256 agcount=97, agsize=31983584 blks = sectsz=512 attr=1 data = bsize=4096 blocks=3072715776, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 log =internal bsize=4096 blocks=32768, version=1 = sectsz=512 sunit=0 blks, lazy-count=0 realtime =none extsz=65536 blocks=0, rtextents=0 Hardware is Dell PE 1950 III with 2 PowerVault MD1000 arrays connected to Perc 5/E (30 SAS drives) VDisks configured on controller: storage:~# omreport storage vdisk controller=0 List of Virtual Disks on Controller PERC 5/E Adapter (Slot 1) Controller PERC 5/E Adapter (Slot 1) ID : 0 Status : Ok Name: Array0 State : Ready Progress: Not Applicable Layout : RAID-5 Size: 1,953.12 GB (2097149902848 bytes) Device Name : /dev/sdc Type: SAS Read Policy : Adaptive Read Ahead Write Policy: Write Back Cache Policy: Not Applicable Stripe Element Size : 64 KB Disk Cache Policy : Disabled ID : 1 Status : Ok Name: Array1 State : Ready Progress: Not Applicable Layout : RAID-5 Size: 1,951.13 GB (2095006613504 bytes) Device Name : /dev/sdd Type: SAS Read Policy : Adaptive Read Ahead Write Policy: Write Back Cache Policy: Not Applicable Stripe Element Size : 64 KB Disk Cache Policy : Disabled ID : 2 Status : Ok Name: Array2 State : Ready Progress: Not Applicable Layout : RAID-5 Size: 1,953.12 GB (2097151737856 bytes) Device Name : /dev/sde Type: SAS Read Policy : Adaptive Read Ahead Write Policy: Write Back Cache Policy: Not Applicable Stripe Element Size : 64 KB Disk Cache Policy : Disabled ID : 3 Status : Ok Name: Array3 State : Ready Progress: Not Applicable Layout : RAID-5 Size: 1,953.12 GB (2097151737856 bytes) Device Name : /dev/sdf Type: SAS Read Policy : Adaptive Read Ahead Write Policy: Write Back Cache Policy: Not Applicable Stripe Element Size : 64 KB Disk Cache Policy : Disabled ID : 4 Status : Ok Name: Array4 State : Ready Progress: Not Applicable Layout : RAID-5 Size: 1,953.12 GB (2097151737856 bytes) Device Name : /dev/sdg Type: SAS Read Policy : Adaptive Read Ahead Write Policy: Write Back Cache Policy: Not Applicable Stripe Element Size : 64 KB Disk Cache Policy : Disabled ID : 5 Status : Ok Name: Array5 State : Ready Progress: Not Applicable Layout : RAID-5 Size: 1,957.88 GB (2102253060096 bytes) Device Name : /dev/sdh Type: SAS Read Policy : Adaptive Read Ahead Write Policy: Write Back Cache Policy: Not Applicable Stripe Elem
Bug#512779: linux-image-2.6.26-2-amd64: XFS on LVM2 filesystem crashses
Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-15lenny3 Followup-For: Bug #512779 Yesterday we made an upgrade of our samba servers previuosly we had similar configuration but server was build on Intel Server Board and the same PERC controller. Then it was 32 bit Linux (Gentoo) and only one MD1000 array. We had similar issues.. So we upgraded system to 64bits Debian Lenny. WE also extended system with one more array. Main Filesystem is LVM2 based: storage:~# pvs PV VGFmt Attr PSize PFree /dev/sdc storage01 lvm2 a- 1.91T0 /dev/sdd storage01 lvm2 a- 1.91T0 /dev/sde storage01 lvm2 a- 1.91T0 /dev/sdf storage01 lvm2 a- 1.91T0 /dev/sdg storage01 lvm2 a- 1.91T 4.00M /dev/sdh storage01 lvm2 a- 1.91T0 storage:~# vgs VG#PV #LV #SN Attr VSize VFree storage01 6 1 0 wz--n- 11.45T 4.00M storage:~# lvdisplay --- Logical volume --- LV Name/dev/storage01/storage01logical VG Namestorage01 LV UUIDaY42UL-j0NN-8fPa-jwIZ-OH1I-QPWz-Z20jfu LV Write Accessread/write LV Status available # open 1 LV Size11.45 TB Current LE 3000699 Segments 6 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:0 Filesystem on it is XFS: storage:~# xfs_info /dev/mapper/storage01-storage01logical meta-data=/dev/mapper/storage01-storage01logical isize=256 agcount=97, agsize=31983584 blks = sectsz=512 attr=1 data = bsize=4096 blocks=3072715776, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 log =internal bsize=4096 blocks=32768, version=1 = sectsz=512 sunit=0 blks, lazy-count=0 realtime =none extsz=65536 blocks=0, rtextents=0 Hardware is Dell PE 1950 III with 2 PowerVault MD1000 arrays connected to Perc 5/E (30 SAS drives) VDisks configured on controller: storage:~# omreport storage vdisk controller=0 List of Virtual Disks on Controller PERC 5/E Adapter (Slot 1) Controller PERC 5/E Adapter (Slot 1) ID : 0 Status : Ok Name: Array0 State : Ready Progress: Not Applicable Layout : RAID-5 Size: 1,953.12 GB (2097149902848 bytes) Device Name : /dev/sdc Type: SAS Read Policy : Adaptive Read Ahead Write Policy: Write Back Cache Policy: Not Applicable Stripe Element Size : 64 KB Disk Cache Policy : Disabled ID : 1 Status : Ok Name: Array1 State : Ready Progress: Not Applicable Layout : RAID-5 Size: 1,951.13 GB (2095006613504 bytes) Device Name : /dev/sdd Type: SAS Read Policy : Adaptive Read Ahead Write Policy: Write Back Cache Policy: Not Applicable Stripe Element Size : 64 KB Disk Cache Policy : Disabled ID : 2 Status : Ok Name: Array2 State : Ready Progress: Not Applicable Layout : RAID-5 Size: 1,953.12 GB (2097151737856 bytes) Device Name : /dev/sde Type: SAS Read Policy : Adaptive Read Ahead Write Policy: Write Back Cache Policy: Not Applicable Stripe Element Size : 64 KB Disk Cache Policy : Disabled ID : 3 Status : Ok Name: Array3 State : Ready Progress: Not Applicable Layout : RAID-5 Size: 1,953.12 GB (2097151737856 bytes) Device Name : /dev/sdf Type: SAS Read Policy : Adaptive Read Ahead Write Policy: Write Back Cache Policy: Not Applicable Stripe Element Size : 64 KB Disk Cache Policy : Disabled ID : 4 Status : Ok Name: Array4 State : Ready Progress: Not Applicable Layout : RAID-5 Size: 1,953.12 GB (2097151737856 bytes) Device Name : /dev/sdg Type: SAS Read Policy : Adaptive Read Ahead Write Policy: Write Back Cache Policy: Not Applicable Stripe Element Size : 64 KB Disk Cache Policy : Disabled ID : 5 Status : Ok Name: Array5 State : Ready Progress: Not Applicable Layout : RAID-5 Size: 1,957.88 GB (2102253060096 bytes) Device Name : /dev/sdh Type: SAS Read Policy : Adaptive Read Ahead Write Policy: Write Back Cache Policy: Not Applicable Stripe Ele
Processed: forcibly merging 524199 524311
Processing commands for cont...@bugs.debian.org: > forcemerge 524199 524311 Bug#524199: linux-image-2.6.26-1-686: nfs unusable Bug#524311: linux-image-2.6.26-1-686: nfs unusable Forcibly Merged 524199 524311. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#499527: marked as done (linux-image-2.6.26-1-686: Kernel Oops with Belkin 54g USB wireless network adapter)
Your message dated Tue, 09 Jun 2009 00:24:31 +0100 with message-id <1244503471.21215.206.ca...@deadeye> and subject line Re: linux-image-2.6.26-1-686: Kernel Oops with Belkin 54g USB wireless network adapter has caused the Debian Bug report #499527, regarding linux-image-2.6.26-1-686: Kernel Oops with Belkin 54g USB wireless network adapter 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.) -- 499527: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499527 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.26-1-686 Version: 2.6.26-2 Severity: important Hello, I got an Oops message (see below) when I plugged in a Belkin 54g USB wireless network adapter. Looks like upstream is aware of the problem, but I'm reporting this here so you can track this. http://lkml.org/lkml/2008/8/9/31 Workaround from above link: --- Please note that a workaround is blacklisting rt2500usb and loading rt73usb directly. (The bug is triggered because rt2500usb is loaded for a USB device which does not contain rt 2500usb chipset). --- HTH, George. -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (Debian 2.6.26-2) (wa...@debian.org) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Fri Aug 8 18:51:38 UTC 2008 ** Command line: root=/dev/sda3 ro ** Tainted: G D (128) ** Kernel log: [ 86.265941] usb 5-5: new high speed USB device using ehci_hcd and address 3 [ 86.568746] usb 5-5: configuration #1 chosen from 1 choice [ 86.568746] usb 5-5: New USB device found, idVendor=050d, idProduct=705a [ 86.568746] usb 5-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 86.568746] usb 5-5: Product: Belkin 54g USB Network Adapter [ 86.568746] usb 5-5: Manufacturer: Belkin [ 86.845649] phy1 -> rt2500usb_init_eeprom: Error - Invalid RT chipset detected. [ 86.845649] phy1 -> rt2x00lib_probe_dev: Error - Failed to allocate device. [ 86.845649] BUG: unable to handle kernel NULL pointer dereference at 0010 [ 86.845649] IP: [] flush_workqueue+0xa/0x3f [ 86.845649] *pde = [ 86.845649] Oops: [#1] SMP [ 86.845649] Modules linked in: rt2500usb(+) rt2x00usb rt2x00lib rfkill input_polldev i915 drm ipt_REJECT nf_conntrack_ipv4 xt_state nf_conntrack xt_tcpudp iptable_filter ip_tables x_tables uinput ppdev parport_pc lp parport acpi_cpufreq cpufreq_stats cpufreq_ondemand freq_table cpufreq_powersave cpufreq_userspace cpufreq_conservative nls_utf8 ntfs nls_base fuse sbp2 loop irtty_sir sir_dev snd_hda_intel ipw3945 pcmcia nsc_ircc iTCO_wdt snd_pcm_oss snd_mixer_oss snd_seq_dummy psmouse irda snd_pcm serio_raw crc_ccitt snd_seq_oss rng_core ieee80211 ieee80211_crypt snd_seq_midi i2c_i801 usbhid hid pcspkr battery ac i2c_core arc4 snd_rawmidi snd_seq_midi_event snd_seq ff_memless ecb crypto_blkcipher video output bay snd_timer snd_seq_device iwl3945 firmware_class mac80211 snd thinkpad_acpi yenta_socket rsrc_nonstatic pcmcia_core button cfg80211 soundcore led_class evdev intel_agp agpgart snd_page_alloc nvram ext3 jbd mbcache sd_mod ide_pci_generic ide_core ata_generic ohci1394 i eee1394 sdhci ata_piix libata scsi_mod mmc_core ehci_hcd uhci_hcd usbcore e1000e dock thermal processor fan thermal_sys [ 86.845649] [ 86.845649] Pid: 3890, comm: modprobe Not tainted (2.6.26-1-686 #1) [ 86.845649] EIP: 0060:[] EFLAGS: 00010246 CPU: 0 [ 86.845649] EIP is at flush_workqueue+0xa/0x3f [ 86.845649] EAX: EBX: f69a5020 ECX: 0046 EDX: 0046 [ 86.845649] ESI: c03735ac EDI: EBP: f785f400 ESP: f1833d84 [ 86.845649] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 [ 86.845649] Process modprobe (pid: 3890, ti=f1832000 task=f68b6240 task.ti=f1832000) [ 86.845649] Stack: f69a5020 f69a5020 f69a41a0 f8dea222 ffed f8deac2d f89b5235 f69a40f0 [ 86.845649]f69a41a0 f69a4a5c 0282 f69a5020 f69a5020 f69a5020 f69a41a0 [ 86.845649]f785f400 f8de68c9 f337f400 f785f400 f8dfd970 f8dfd8a0 f88e899a [ 86.845649] Call Trace: [ 86.845649] [] rt2x00lib_remove_dev+0x30/0x51 [rt2x00lib] [ 86.845649] [] rt2x00lib_probe_dev+0x31b/0x337 [rt2x00lib] [ 86.845649] [] wiphy_new+0xdb/0xf4 [cfg80211] [ 86.845649] [] rt2x00usb_probe+0xdd/0x118 [rt2x00usb] [ 86.845649] [] usb_probe_interface+0xad/0xde [usbcore] [ 86.845649] [] __driver_attach+0x0/0x55 [ 86.845649] [] driver_probe_device+0xb5/0x12c [ 86.845649] [] __driver_attach+0x37/0x55 [ 86.845649] [] bus_for_each_dev+0x37/0x59 [ 86.845649] [] driver_attach+0x11/0x13 [ 86.845649] [] __dr
Bug#516374: INFO: task * blocked for more than 120 seconds. in numerous non-SCHED_IDLE workloads
On Fri, Jun 05, 2009 at 03:37:33AM +0100, Ben Hutchings wrote: > Please try the patch I posted here: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=54;bug=517449 > > It includes a fix made between 2.6.26 and .28 that may address this bug. Thanks, Ben. Rebuilt with this patch and threw the resulting kernel on a couple of machines running several KVM VMs. I'll be able to provide confident feedback in a couple of days. john -- John Morrissey _o/\ __o j...@horde.net_-< \_ / \ < \, www.horde.net/__(_)/_(_)/\___(_) /_(_)__ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#532376: r8169: network buffer overflow
Package: linux-2.6 Version: 2.6.29-5 Severity: critical Tags: security patch Some or all NICs supported by r8169 seem to ignore the buffer sizes in RX descriptors, and will write up to the global maximum frame size. This means a remote attacker can overflow RX buffers, probably allowing for code injection. This should be fixed by the patch posted in: http://article.gmane.org/gmane.linux.network/130114 Ben. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (x86_64) Kernel: Linux 2.6.29-2-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/bash -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#475575: [linux-image-2.6] 8139too and 8139cp get loaded at the same time
> I want to see the full output from these commands. I wasn't aware of > rtl8139-diag but it sounds like that would be useful too. > > Ben. > I included all output of rtl8139-diag, ethtool and mii-tool. All options for ethtool wich I didn't paste below showed no output ( weren't supported). Since I am not sure that the change of behavior (dropping of packages) is due to a difference between ubuntu and debian I will include the output of modinfo at the end of this message as well. Sebastian # rtl8139-diag -a -e -m -f rtl8139-diag.c:v2.13 2/28/2005 Donald Becker (bec...@scyld.com) http://www.scyld.com/diag/index.html Index #1: Found a RealTek RTL8139 adapter at 0x4000. RealTek chip registers at 0x4000 0x000: 22d31600 c67e 80008000 4010 0008a042 0008a0a8 0008a0a8 0008a064 0x020: 35d0 35d00600 35d00c00 35d01200 32d6 0d0a 49384928 c07f 0x040: 77400680 f78e f5208a4a 004d1000 0080c110 0010 0x060: 1100f00f 05e1782d 000141e1 0704 000707c8 60f60c59 7b732660. Realtek station address 00:16:d3:22:7e:c6, chip type 'rtl8139C'. Receiver configuration: Normal unicast and hashed multicast Rx FIFO threshold 2048 bytes, maximum burst 2048 bytes, 32KB ring Transmitter enabled with NONSTANDARD! settings, maximum burst 1024 bytes. Tx entry #0 status 0008a042 complete, 66 bytes. Tx entry #1 status 0008a0a8 complete, 168 bytes. Tx entry #2 status 0008a0a8 complete, 168 bytes. Tx entry #3 status 0008a064 complete, 100 bytes. Flow control: Tx disabled Rx disabled. The chip configuration is 0x10 0x4d, MII full-duplex mode. No interrupt sources are pending. Decoded EEPROM contents: PCI IDs -- Vendor 0x10ec, Device 0x8139. PCI Subsystem IDs -- Vendor 0x10ec, Device 0x8139. PCI timer settings -- minimum grant 32, maximum latency 64. General purpose pins -- direction 0xe1 value 0x10. Station Address 00:16:D3:22:7E:C6. Configuration register 0/1 -- 0x4d / 0xc2. EEPROM active region checksum is 09cc. The RTL8139 does not use a MII transceiver. It does have internal MII-compatible registers: Basic mode control register 0x1100. Basic mode status register0x782d. Autonegotiation Advertisement 0x05e1. Link Partner Ability register 0x41e1. Autonegotiation expansion 0x0001. Disconnects 0x. False carrier sense counter 0x. NWay test register0x0704. Receive frame error count 0x. rtl8139-diag -aa -ee -mm rtl8139-diag.c:v2.13 2/28/2005 Donald Becker (bec...@scyld.com) http://www.scyld.com/diag/index.html Index #1: Found a RealTek RTL8139 adapter at 0x4000. The RealTek chip appears to be active, so some registers will not be read. To see all register values use the '-f' flag. RealTek chip registers at 0x4000 0x000: 22d31600 c67e 80008000 4010 0008a03c 0008a064 0008a042 0008a05c 0x020: 35d0 35d00600 35d00c00 35d01200 32d6 0d0a bf30bf20 c07f 0x040: 77400680 f78e 6ab7ac8d 004d1000 0080c110 0010 0x060: 1100f00f 05e1782d 000141e1 0704 000707c8 60f60c59 7b732660. Realtek station address 00:16:d3:22:7e:c6, chip type 'rtl8139C'. Receiver configuration: Normal unicast and hashed multicast Rx FIFO threshold 2048 bytes, maximum burst 2048 bytes, 32KB ring Transmitter enabled with NONSTANDARD! settings, maximum burst 1024 bytes. Tx entry #0 status 0008a03c complete, 60 bytes. Tx entry #1 status 0008a064 complete, 100 bytes. Tx entry #2 status 0008a042 complete, 66 bytes. Tx entry #3 status 0008a05c complete, 92 bytes. Flow control: Tx disabled Rx disabled. The chip configuration is 0x10 0x4d, MII full-duplex mode. No interrupt sources are pending. Decoded EEPROM contents: PCI IDs -- Vendor 0x10ec, Device 0x8139. PCI Subsystem IDs -- Vendor 0x10ec, Device 0x8139. PCI timer settings -- minimum grant 32, maximum latency 64. General purpose pins -- direction 0xe1 value 0x10. Station Address 00:16:D3:22:7E:C6. Configuration register 0/1 -- 0x4d / 0xc2. EEPROM active region checksum is 09cc. EEPROM contents (64 words): 0x00: 8129 10ec 8139 10ec 8139 4020 e110 1600 0x08: 22d3 c67e 4d10 f7c2 8001 b388 58fa 0708 0x10: d843 a438 d843 a438 d843 a438 d843 a438 0x18: 8ec5 3b00 0x20: ... The RTL8139 does not use a MII transceiver. It does have internal MII-compatible registers: Basic mode control register 0x1100. Basic mode status register0x782d. Autonegotiation Advertisement 0x05e1. Link Partner Ability register 0x41e1. Autonegotiation expansion 0x0001. Disconnects 0x. False carrier sense counter 0x. NWay test register0x0704. Receive frame error count 0x. libmii.c:v2.11 2/28/2005 Donald Becker (bec...@scyld.com) http://www.scyld.com/diag/index.html MII PHY #32 transceiver registers: 1100 782d
Re: scheduling upload for 5.0.2
On Sun, Jun 07, 2009 at 03:23:53AM +0100, Ben Hutchings wrote: > On Sat, 2009-06-06 at 16:49 -0600, dann frazier wrote: > > SRM recently announced plans for the upcoming 5.0.2 release, so I'd > > like to schedule an upload for this Monday evening, June 8. > > > > Hopefully we get some feedback on Ben's patch for #517449 before that. > > Given that this patch involved a fair amount of cherry-picking we cannot > rely on upstream testing and should be very wary of regressions. There > is no way I could be confident of it by June 8. I personally haven't > tested it at all, except that it compiles! *nod* - I can ask for a small extension from SRM, but if its anymore than 1 or 2 days, we'll probably just have to postpone for the next point release. fyi, I've been testing this patch on a machine of mine that I thought was hitting #517449. It seems to be running as stable as before. Though the patch didn't solve the issue I was seeing (I now think is unrelated), I haven't had time to dig deeper. Just a data point - I haven't tried testing for regressions. > I identified upstream fixes for some driver bugs that look like good > candidates for a stable update: #498271, #499527, #514268, #524300, > #524311, #530884. All of those fixes look like goodness for a stable update - please feel free to commit to the lenny branch (or I can do it, if you won't have time before release). -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: hint cryptsetup/2:1.0.6+20090405.svn49-1 for debian/squeeze
hey again, On 02/06/2009 Jonas Meurer wrote: > cryptsetup/2:1.0.6+20090405.svn49-1 has been in unstable for 59 days now > without migrating to testing. I guess that this is due to the udeb it > creates. It would be great if you could hint it for migration to > testing/squeeze. > > here's the relevant changelog: is there a reason why this request has been ignored so far? can I do anything about it? i've cc'ed debian-kernel now, as cryptsetup creates a udeb, and their option might be relevant. greetings, jonas -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: hint cryptsetup/2:1.0.6+20090405.svn49-1 for debian/squeeze
On 08/06/2009 Jonas Meurer wrote: > hey again, > > On 02/06/2009 Jonas Meurer wrote: > > cryptsetup/2:1.0.6+20090405.svn49-1 has been in unstable for 59 days now > > without migrating to testing. I guess that this is due to the udeb it > > creates. It would be great if you could hint it for migration to > > testing/squeeze. > > > > here's the relevant changelog: > > is there a reason why this request has been ignored so far? can I do > anything about it? > > i've cc'ed debian-kernel now, as cryptsetup creates a udeb, and their > option might be relevant. shit, that should have been debian-boot instead of debian-kernel. sorry for the noise. greetings, jonas -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#532005: gnome: Bell beep on PC speaker no longer works
On Mon, 8 Jun 2009, Matthew Wakeling wrote: Having had a look over the kernel bugs, it appears that this bug is a duplicate of #520232. Okay, scratch that. I'll try blacklisting the pcspkr module. Just tried blacklisting the pcspkr module and rebooting, and the same problem existed. I then did a modprobe pcspkr, and suddenly the PC speaker worked properly again. This looks like it is an order of loading issue. When the pcspkr module is loaded last, it works, but if it is loaded early, it doesn't. This is on linux-image-2.6.29-2-amd64 Matthew -- If you let your happiness depend upon how somebody else feels about you, now you have to control how somebody else feels about you. -- Abraham Hicks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#532005: gnome: Bell beep on PC speaker no longer works
On Mon, 8 Jun 2009, Josselin Mouette wrote: Le lundi 08 juin 2009 à 14:31 +0100, Matthew Wakeling a écrit : After doing a little bit of rebooting, it seems that it is the kernel that is redirecting the sound to the sound card. I'll file a bug there. Feel free to close this one. Let’s just reassign. Having had a look over the kernel bugs, it appears that this bug is a duplicate of #520232. I'll try blacklisting the pcspkr module. Matthew -- "The problem with defending the purity of the English language is that English is about as pure as a cribhouse whore. We don't just borrow words; on occasion, English has pursued other languages down alleyways to beat them unconscious and rifle their pockets for new vocabulary." - James Nicoll
Bug#529870: marked as done (linux-image-2.6.26-2-686: Kernel panic when using SE Linux)
Your message dated Mon, 08 Jun 2009 13:54:06 + with message-id and subject line Bug#528860: fixed in linux-2.6 2.6.26-15lenny3 has caused the Debian Bug report #528860, regarding linux-image-2.6.26-2-686: Kernel panic when using SE Linux 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.) -- 528860: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528860 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.26-2-686 Version: 2.6.26-15lenny2 Severity: important In my tests the latest 2.6 kernels for i386 (both Xen and non-Xen) and for AMD64 Xen will crash if SE Linux is enabled. The crash occurs even if SE Linux is in permissive mode, so the kernel parameter "selinux=0" is required to boot the machine after installing such a kernel. Here is a back-trace from an AMD64 system: [8.252947] kernel BUG at security/selinux/avc.c:883! [8.252954] invalid opcode: [1] SMP [8.252961] CPU 0 [8.252966] Modules linked in: ext3 jbd mbcache thermal_sys [8.252978] Pid: 0, comm: swapper Not tainted 2.6.26-2-xen-amd64 #1 [8.252985] RIP: e030:[] [] avc_has_perm_noaudit+0x26/0x379 [8.253002] RSP: e02b:80595a00 EFLAGS: 00010246 [8.253008] RAX: RBX: 0011 RCX: [8.253015] RDX: 0011 RSI: 0009 RDI: 0001 [8.253022] RBP: 0009 R08: R09: 80595ab0 [8.253028] R10: 0007 R11: 803e932b R12: 0011 [8.253034] R13: 0001 R14: 0009 R15: 80595b40 [8.253044] FS: 7f7e2649f6e0() GS:80539000() knlGS: [8.253053] CS: e033 DS: ES: [8.253059] DR0: DR1: DR2: [8.253066] DR3: DR6: 0ff0 DR7: 0400 [8.253073] Process swapper (pid: 0, threadinfo 80552000, task 804fe460) [8.253081] Stack: 80595ab0 0012 [8.253095] 00128812 0001000c 804fe460 [8.253106] 0001 80595b90 8026fe3e [8.253115] Call Trace: [8.253122][] ? mod_zone_page_state+0x2c/0x5b [8.253135] [] ? avc_has_perm+0x2b/0x5b [8.253143] [] ? sel_netport_sid+0x13b/0x16b [8.253151] [] ? selinux_ip_postroute+0x1eb/0x38b [8.253160] [] ? nf_iterate+0x41/0x7d [8.253168] [] ? ip_finish_output+0x0/0x241 [8.253175] [] ? nf_hook_slow+0x5d/0xbe [8.253182] [] ? ip_finish_output+0x0/0x241 [8.253189] [] ? ip_output+0x89/0xa1 [8.253196] [] ? ip_local_out+0x9/0x1f [8.253204] [] ? ip_push_pending_frames+0x2bf/0x32e [8.253211] [] ? icmp_send+0x4fc/0x54b [8.253220] [] ? xen_clocksource_read+0xd/0x9c [8.253228] [] ? profile_pc+0x21/0x53 [8.253235] [] ? ipv4_link_failure+0x15/0x45 [8.253242] [] ? arp_error_report+0x24/0x2d [8.253250] [] ? neigh_timer_handler+0x21d/0x313 [8.253257] [] ? neigh_timer_handler+0x0/0x313 [8.253264] [] ? run_timer_softirq+0x190/0x237 [8.253273] [] ? __do_softirq+0x77/0x103 [8.253280] [] ? call_softirq+0x1c/0x28 [8.253287] [] ? do_softirq+0x55/0xbb [8.253294] [] ? do_IRQ+0x7d/0x9a [8.253301] [] ? evtchn_do_upcall+0x13c/0x1fc [8.253309] [] ? do_hypervisor_callback+0x1e/0x30 [8.253315][] ? xen_safe_halt+0x90/0xa6 [8.253326] [] ? xen_idle+0x2e/0x66 [8.253332] [] ? cpu_idle+0x97/0xb9 [8.253338] [8.253342] [8.253346] Code: 41 5e 41 5f c3 41 57 41 56 41 89 f6 41 55 41 89 fd 41 54 55 53 48 83 ec 68 85 c9 89 4c 24 18 44 89 44 24 14 4c 89 4c 24 08 75 04 <0f> 0b eb fe 0f b7 f2 48 c7 c0 50 f6 58 80 46 8d 24 b5 00 00 00 [8.253408] RIP [] avc_has_perm_noaudit+0x26/0x379 [8.253417] RSP [8.253424] ---[ end trace a7e19496a9366ab4 ]--- [8.253431] Kernel panic - not syncing: Aiee, killing interrupt handler! I can provide i386 back-traces if desired. If you want a non-Xen back-trace I could do that too, but getting a serial console going would take a little time so I hope you can track this down without it. -- Package-specific info: -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/bash
Bug#528860: marked as done (linux-image-2.6.26-2-amd64: Kernel panic, not syncing: Aiee, killing interrupt handler)
Your message dated Mon, 08 Jun 2009 13:54:06 + with message-id and subject line Bug#528860: fixed in linux-2.6 2.6.26-15lenny3 has caused the Debian Bug report #528860, regarding linux-image-2.6.26-2-amd64: Kernel panic, not syncing: Aiee, killing interrupt handler 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.) -- 528860: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528860 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-15lenny2 Severity: critical Justification: breaks the whole system Since the kernel bails out before writing to disk, this is pretty much all I know. -- Package-specific info: -- System Information: Debian Release: squeeze/sid APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.26-2-amd64 depends on: ii debconf [debconf-2.0] 1.5.26 Debian configuration management sy ii initramfs-tools [linux-initra 0.93.2 tools for generating an initramfs ii module-init-tools 3.7-pre9-1 tools for managing Linux kernel mo linux-image-2.6.26-2-amd64 recommends no packages. Versions of packages linux-image-2.6.26-2-amd64 suggests: ii grub 0.97-53GRand Unified Bootloader (Legacy v pn linux-doc-2.6.26 (no description available) -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.26-2-amd64/postinst/bootloader-error-2.6.26-2-amd64: linux-image-2.6.26-2-amd64/preinst/lilo-initrd-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/postinst/depmod-error-2.6.26-2-amd64: false linux-image-2.6.26-2-amd64/postinst/old-dir-initrd-link-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/postinst/create-kimage-link-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/preinst/initrd-2.6.26-2-amd64: linux-image-2.6.26-2-amd64/preinst/lilo-has-ramdisk: linux-image-2.6.26-2-amd64/preinst/abort-install-2.6.26-2-amd64: linux-image-2.6.26-2-amd64/postinst/old-initrd-link-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/postinst/depmod-error-initrd-2.6.26-2-amd64: false linux-image-2.6.26-2-amd64/postinst/bootloader-test-error-2.6.26-2-amd64: linux-image-2.6.26-2-amd64/preinst/overwriting-modules-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/postinst/kimage-is-a-directory: linux-image-2.6.26-2-amd64/preinst/failed-to-move-modules-2.6.26-2-amd64: linux-image-2.6.26-2-amd64/prerm/would-invalidate-boot-loader-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/postinst/old-system-map-link-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/preinst/abort-overwrite-2.6.26-2-amd64: linux-image-2.6.26-2-amd64/preinst/bootloader-initrd-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/preinst/elilo-initrd-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/prerm/removing-running-kernel-2.6.26-2-amd64: true --- End Message --- --- Begin Message --- Source: linux-2.6 Source-Version: 2.6.26-15lenny3 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: linux-2.6_2.6.26-15lenny3.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.26-15lenny3.diff.gz linux-2.6_2.6.26-15lenny3.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.26-15lenny3.dsc linux-doc-2.6.26_2.6.26-15lenny3_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.26_2.6.26-15lenny3_all.deb linux-headers-2.6.26-2-486_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-486_2.6.26-15lenny3_i386.deb linux-headers-2.6.26-2-686-bigmem_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-686-bigmem_2.6.26-15lenny3_i386.deb linux-headers-2.6.26-2-686_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-686_2.6.26-15lenny3_i386.deb linux-headers-2.6.26-2-all-i386_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-all-i386_2.6.26-15lenny3_i386.deb linux-headers-2.6.26-2-all_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-all_2.6.26-15lenny3_i386.deb linux-headers-2.6.26-2-amd64_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-amd64_2.6.26-15lenny3_i386.deb linux-headers-2.6.26-2-common-openvz_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-common-op
linux-2.6_2.6.26-15lenny3_i386.changes ACCEPTED
Accepted: linux-2.6_2.6.26-15lenny3.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.26-15lenny3.diff.gz linux-2.6_2.6.26-15lenny3.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.26-15lenny3.dsc linux-doc-2.6.26_2.6.26-15lenny3_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.26_2.6.26-15lenny3_all.deb linux-headers-2.6.26-2-486_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-486_2.6.26-15lenny3_i386.deb linux-headers-2.6.26-2-686-bigmem_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-686-bigmem_2.6.26-15lenny3_i386.deb linux-headers-2.6.26-2-686_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-686_2.6.26-15lenny3_i386.deb linux-headers-2.6.26-2-all-i386_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-all-i386_2.6.26-15lenny3_i386.deb linux-headers-2.6.26-2-all_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-all_2.6.26-15lenny3_i386.deb linux-headers-2.6.26-2-amd64_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-amd64_2.6.26-15lenny3_i386.deb linux-headers-2.6.26-2-common-openvz_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-common-openvz_2.6.26-15lenny3_i386.deb linux-headers-2.6.26-2-common-vserver_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-common-vserver_2.6.26-15lenny3_i386.deb linux-headers-2.6.26-2-common-xen_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-common-xen_2.6.26-15lenny3_i386.deb linux-headers-2.6.26-2-common_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-common_2.6.26-15lenny3_i386.deb linux-headers-2.6.26-2-openvz-686_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-openvz-686_2.6.26-15lenny3_i386.deb linux-headers-2.6.26-2-vserver-686-bigmem_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-vserver-686-bigmem_2.6.26-15lenny3_i386.deb linux-headers-2.6.26-2-vserver-686_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-vserver-686_2.6.26-15lenny3_i386.deb linux-headers-2.6.26-2-xen-686_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-xen-686_2.6.26-15lenny3_i386.deb linux-image-2.6.26-2-486_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.26-2-486_2.6.26-15lenny3_i386.deb linux-image-2.6.26-2-686-bigmem_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.26-2-686-bigmem_2.6.26-15lenny3_i386.deb linux-image-2.6.26-2-686_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.26-2-686_2.6.26-15lenny3_i386.deb linux-image-2.6.26-2-amd64_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.26-2-amd64_2.6.26-15lenny3_i386.deb linux-image-2.6.26-2-openvz-686_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.26-2-openvz-686_2.6.26-15lenny3_i386.deb linux-image-2.6.26-2-vserver-686-bigmem_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.26-2-vserver-686-bigmem_2.6.26-15lenny3_i386.deb linux-image-2.6.26-2-vserver-686_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.26-2-vserver-686_2.6.26-15lenny3_i386.deb linux-image-2.6.26-2-xen-686_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.26-2-xen-686_2.6.26-15lenny3_i386.deb linux-libc-dev_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-libc-dev_2.6.26-15lenny3_i386.deb linux-manual-2.6.26_2.6.26-15lenny3_all.deb to pool/main/l/linux-2.6/linux-manual-2.6.26_2.6.26-15lenny3_all.deb linux-modules-2.6.26-2-xen-686_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/linux-modules-2.6.26-2-xen-686_2.6.26-15lenny3_i386.deb linux-patch-debian-2.6.26_2.6.26-15lenny3_all.deb to pool/main/l/linux-2.6/linux-patch-debian-2.6.26_2.6.26-15lenny3_all.deb linux-source-2.6.26_2.6.26-15lenny3_all.deb to pool/main/l/linux-2.6/linux-source-2.6.26_2.6.26-15lenny3_all.deb linux-support-2.6.26-2_2.6.26-15lenny3_all.deb to pool/main/l/linux-2.6/linux-support-2.6.26-2_2.6.26-15lenny3_all.deb linux-tree-2.6.26_2.6.26-15lenny3_all.deb to pool/main/l/linux-2.6/linux-tree-2.6.26_2.6.26-15lenny3_all.deb xen-linux-system-2.6.26-2-xen-686_2.6.26-15lenny3_i386.deb to pool/main/l/linux-2.6/xen-linux-system-2.6.26-2-xen-686_2.6.26-15lenny3_i386.deb Override entries for your package: linux-2.6_2.6.26-15lenny3.dsc - optional devel linux-doc-2.6.26_2.6.26-15lenny3_all.deb - optional doc linux-headers-2.6.26-2-486_2.6.26-15lenny3_i386.deb - optional devel linux-headers-2.6.26-2-686-bigmem_2.6.26-15lenny3_i386.deb - optional devel linux-headers-2.6.26-2-686_2.6.26-15lenny3_i386.deb - optional devel linux-headers-2.6.26-2-all-i386_2.6.26-15lenny3_i386.deb - optional devel linux-headers-2.6.26-2-all_2.6.26-15lenny3_i386.deb - optional devel linux-headers-2.6.26-2-amd64_2.6.26-15lenny3_i386.deb - optional devel linux-headers-2.6.26-2-common-openvz_2.
Processed: Re: Bug#532005: gnome: Bell beep on PC speaker no longer works
Processing commands for cont...@bugs.debian.org: > reassign 532005 linux-2.6 2.6.29-5 Bug#532005: gnome: Bell beep on PC speaker no longer works Bug reassigned from package `gnome' to `linux-2.6'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#532005: gnome: Bell beep on PC speaker no longer works
reassign 532005 linux-2.6 2.6.29-5 thanks Le lundi 08 juin 2009 à 14:31 +0100, Matthew Wakeling a écrit : > After doing a little bit of rebooting, it seems that it is the kernel that > is redirecting the sound to the sound card. I'll file a bug there. Feel > free to close this one. Let’s just reassign. -- .''`. Josselin Mouette : :' : `. `' “I recommend you to learn English in hope that you in `- future understand things” -- Jörg Schilling signature.asc Description: Ceci est une partie de message numériquement signée
Bug#532237: marked as done (Failure to both enable proto=exps and detect ALPS touchpad on ThinkPad X301)
Your message dated Mon, 8 Jun 2009 09:29:10 -0400 with message-id <20090608132910.ga5...@eep.dnsalias.org> and subject line Re: Bug#532237: Failure to both enable proto=exps and detect ALPS touchpad on ThinkPad X301 has caused the Debian Bug report #532237, regarding Failure to both enable proto=exps and detect ALPS touchpad on ThinkPad X301 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.) -- 532237: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=532237 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.29-5 Severity: normal I have a ThinkPad X301 that has an ALPS touchpad. I've found that tap-to-drag (a double tap on the touchpad, but without releasing the finger from the touchpad after the second tap, which lets you drag using just the touchpad and not any physical buttons) works only if the psmouse module is loaded with the option "proto=exps". Unfortunately, if I place "options psmouse proto=exps" into /etc/modprobe.d/psmouse.conf so that this option is automatically enabled when the module is initially loaded, HAL fails to recognize the touchpad as a touchpad anymore, making X.Org fail to load the Synaptics input driver to enable more specialized features like edge scrolling. (Tap to click and tap-to-drag work even with just the X.Org generic PS/2 input driver, though.) Thus, there are two things I'd expect: 1) the kernel should automatically recognize that my touchpad deserves proto=exps, and 2) with proto=exps, the kernel shouldn't confuse HAL into not recognizing that my touchpad is a touchpad. Please let me know if there's any hardware information that you need in order to fix this. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash --- End Message --- --- Begin Message --- On Sun, Jun 07, 2009 at 10:44:09PM +0100, Ben Hutchings wrote: > On Sun, 2009-06-07 at 15:06 -0400, EspeonEefi wrote: > [...] > > Thus, there are two things I'd expect: 1) the kernel should > > automatically recognize that my touchpad deserves proto=exps, > > If you have an ALPS touchpad then I believe the psmouse driver should > use the "alps" protocol variant, not "exps". Please try using "options > proto=alps" instead. Actually, proto=alps is not a legal option, but I've figured out that the problem is with the X.Org Synaptics driver, not the kernel (probably). Playing with the MaxTapTime and MaxDoubleTapTime settings of the X.Org Synaptics driver brought back dragging. Unfortunately, it looks like the model that the X.Org Synaptics driver is using to process taps and taps and drags is worse than whatever the hardware does on its own; there's a delay in response time to taps from X.Org Synaptics that using proto=exps doesn't have. (Also, the defaults for the X.Org Synaptics driver make tap-and-drag really, really hard to trigger.) But these are bugs for xserver-xorg-input-synaptics, not linux-2.6. Thanks for the prompting to investigate this more closely myself. Hopefully this will show up higher on Google (I got the mistaken impression that proto=exps was the correct fix from Googling for alps and tap to drag.) Closing the bug now. --- End Message ---
Processed: closing 455468
Processing commands for cont...@bugs.debian.org: > # as requested by submitter > close 455468 Bug#455468: linux-image-2.6.18-5-xen-686: kernel BUG on drbd disconnect 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Rene Mayrhofer > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#532159: [iwlagn] Does not take kill switch changes into account
Le dimanche 07 juin 2009 à 09:08 +0200, Josselin Mouette a écrit : > > When the iwlagn module is loaded, it takes into account the kill switch > status; radio is disabled when the switch is off. However, it doesn’t > take into account any changes in the switch status. To enable radio, I > have to unload the module, change the switch state, and load the module > again. > Maybe this exhibits the same problem as I reported in #530554 although I'm not so sure if the context is exactly the same (hardware, versions...) :-/ In any case, my 2 cents. Best regards, -- Olivier BERGER http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 1024D/6B829EEC Ingénieur Recherche - Dept INF Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#532115: Please help to solve this bug
> Debian doesn't patch this drivers, so if it works in other distributions > this is not a kernel bug. Yes - i also could not understand this. The analog.ko is very old and there would be no need to change it. On the other hand i did found a forum entry with a tip that the analog module have to be patched, because something is wrong. Sorry but i have lost the link and the content. So has this kernel-module been changed in the past? At least i also can't believe that the kernel-module is the problem, and so i investigated in the problem of the kernel-message registering "/class/input/input1" instead of "/dev/input/js0". I assumed that must have to do with udev, which seems to be responsible for that ? But the maintainer of udev says that everything is fine and there can't be a problem. (See bug 518815) I don't understand the interaction of udev and the kernel and so i need help to understand the mechanism of inserting kernel-modules. We need help, because there are many users outside, that still wants to use this good old analog gameport for gaming or simple as input for external signals. Can you please give some advice for further analysis? Regards Karsten -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
