Bug#532115: the joystick bug
Hi, Thank you . I have checked the /dev/input derictory and there's no js0 device in there. sergius-0:/dev/input# ls -l итого 0 drwxr-xr-x 2 root root120 Июн 19 02:19 by-path crw-rw 1 root root 13, 64 Июн 19 02:19 event0 crw-rw 1 root root 13, 65 Июн 19 02:19 event1 crw-rw 1 root root 13, 66 Июн 19 02:19 event2 crw-rw 1 root root 13, 67 Июн 19 02:19 event3 crw-rw 1 root root 13, 68 Июн 19 02:19 event4 crw-rw 1 root root 13, 69 Июн 19 02:19 event5 crw-rw 1 root root 13, 63 Июн 19 02:18 mice crw-rw 1 root root 13, 32 Июн 19 02:19 mouse0 Niether is it in /dev. Even after manual restart of udev. As far as I understand the joystick needs drivers as any device. Is it possible that the drivers simply disabled in the kernel because they are old? Best regards. SY On Friday 19 June 2009 00:54:50 Ben Hutchings wrote: On Thu, Jun 18, 2009 at 11:53:10PM +0400, Sergey Yakimov wrote: Hi. I've tried to do what you've said. Please, see the attached log. I found that the device is correctly found but the system lacks some files to correctly handle it. Or i might be wrong?.. The files reported as missing are optional. Anyway here's a part of it: [...] [15107] udev_node_mknod: mknod(/dev/input/js0, 020664, (13,0)) [15107] udev_node_mknod: chmod(/dev/input/js0, 020664) [15107] udev_node_mknod: chown(/dev/input/js0, 0, 0) [...] This says that /dev/input/js0 is being created, as you wanted. The question now is, why this doesn't happen at boot time. Ben. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#533301: Jerky display
Processing commands for cont...@bugs.debian.org: reassign 533301 linux-2.6 Bug#533301: xserver-xorg: jerky display on bbc iplayer Bug reassigned from package `xserver-xorg' to `linux-2.6'. found 533301 2.6.29-2-686-bigmem Bug#533301: xserver-xorg: jerky display on bbc iplayer Bug marked as found in version 2.6.29-2-686-bigmem. fixed 533301 2.6.30-1-686-bigmem Bug#533301: xserver-xorg: jerky display on bbc iplayer Bug marked as fixed in version 2.6.30-1-686-bigmem. 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
Bug#533574: marked as done (linux-image-2.6.29-2-686: Optoin CONFIG_ACPI_PROCFS_POWER is not set -- battery monitors don't work)
Your message dated Fri, 19 Jun 2009 11:15:44 +0200
with message-id 20090619091544.ga19...@wavehammer.waldi.eu.org
and subject line Re: Bug#533574: linux-image-2.6.29-2-686: Optoin
CONFIG_ACPI_PROCFS_POWER is not set -- battery monitors don't work
has caused the Debian Bug report #533574,
regarding linux-image-2.6.29-2-686: Optoin CONFIG_ACPI_PROCFS_POWER is not set
-- battery monitors don't work
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.)
--
533574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=533574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6.29-2-686
Version: 2.6.29-5
Severity: wishlist
File: /lib/modules/2.6.29-2-686/kernel/drivers/acpi/battery.ko
The ACPI battery module appears to be built with CONFIG_ACPI_PROCFS_POWER
unset. That leaves it pretty useless. Things like gui battery monitors and
even powertop require this file to report the battery usage.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.29-2-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.29-2-686 depends on:
ii debconf [debconf-2.0]1.5.24 Debian configuration management sy
ii initramfs-tools [linux-initr 0.91e tools for generating an initramfs
ii module-init-tools3.3-pre11-4 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.29-2-686 recommends:
ii libc6-i6862.9-16 GNU C Library: Shared libraries [i
-- debconf information:
linux-image-2.6.29-2-686/preinst/overwriting-modules-2.6.29-2-686: true
linux-image-2.6.29-2-686/postinst/bootloader-error-2.6.29-2-686:
linux-image-2.6.29-2-686/preinst/abort-install-2.6.29-2-686:
linux-image-2.6.29-2-686/preinst/failed-to-move-modules-2.6.29-2-686:
linux-image-2.6.29-2-686/preinst/initrd-2.6.29-2-686:
linux-image-2.6.29-2-686/postinst/old-dir-initrd-link-2.6.29-2-686: true
linux-image-2.6.29-2-686/postinst/old-initrd-link-2.6.29-2-686: true
linux-image-2.6.29-2-686/postinst/bootloader-test-error-2.6.29-2-686:
linux-image-2.6.29-2-686/postinst/depmod-error-initrd-2.6.29-2-686: false
linux-image-2.6.29-2-686/preinst/elilo-initrd-2.6.29-2-686: true
linux-image-2.6.29-2-686/preinst/lilo-initrd-2.6.29-2-686: true
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.29-2-686/preinst/lilo-has-ramdisk:
linux-image-2.6.29-2-686/postinst/depmod-error-2.6.29-2-686: false
linux-image-2.6.29-2-686/postinst/kimage-is-a-directory:
linux-image-2.6.29-2-686/postinst/create-kimage-link-2.6.29-2-686: true
linux-image-2.6.29-2-686/prerm/removing-running-kernel-2.6.29-2-686: true
linux-image-2.6.29-2-686/postinst/old-system-map-link-2.6.29-2-686: true
linux-image-2.6.29-2-686/preinst/bootloader-initrd-2.6.29-2-686: true
linux-image-2.6.29-2-686/prerm/would-invalidate-boot-loader-2.6.29-2-686: true
linux-image-2.6.29-2-686/preinst/abort-overwrite-2.6.29-2-686:
--
Gregory Stark
http://mit.edu/~gsstark/resume.pdf
---End Message---
---BeginMessage---
On Thu, Jun 18, 2009 at 11:16:25PM +0100, Gregory Stark wrote:
The ACPI battery module appears to be built with CONFIG_ACPI_PROCFS_POWER
unset. That leaves it pretty useless. Things like gui battery monitors and
even powertop require this file to report the battery usage.
The information is properly exported in the sysfs:
| $ cat /sys/class/power_supply/BAT0/{charge_{full,now},voltage_now}
| 545
| 545
| 8316000
If the tools are not able to use them, it is their bug. No bug in the
kernel.
Bastian
--
There is an order of things in this universe.
-- Apollo, Who Mourns for Adonais? stardate 3468.1
---End Message---
Bug#532115: Bug#518815: Bug#532115: the joystick bug
Hello together, i am glad that you are now looking for this problem. Hi, Thank you . I have checked the /dev/input derictory and there's no js0 device in there. sergius-0:/dev/input# ls -l Niether is it in /dev. Yes. That's what you find in many forum-threads and i could also reproduce it. Most of the forum discussions are from the time before udev, so the dev-entries where made with MAKEDEV js. Of course this entries are lost after reboot now. When i did create them manually they didn't work even. Even after manual restart of udev. As far as I understand the joystick needs drivers as any device. Is it possible that the drivers simply disabled in the kernel because they are old? Is it possible that drivers exist and can be loaded but are disabled? In squeeze the drivers are existent and can be loaded as you can see: r...@pc10:/# modprobe gameport r...@pc10:/# modprobe joydev r...@pc10:/# modprobe analog r...@pc10:/# lsmod | grep gameport gameport 17040 3 analog,snd_ens1371,snd_cs46xx r...@pc10:/# jstest /dev/js0 jstest: No such file or directory jstest is a joystick test program. You can see if the interface is working, even if there is no joystick connected. Regards Karsten -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533574: closed by Bastian Blank wa...@debian.org (Re: Bug#533574: linux-image-2.6.29-2-686: Optoin CONFIG_ACPI_PROCFS_POWER is not set -- battery monitors don't work)
I don't think this is the right way to go about changing interfaces between
packages in Debian.
The correct way to go about this is to propose a new packaging policy that
packages use the sysfs interface. When that's approved then issue bug
reports against all packages using the old interface. Then when all or most
of those packages have switched to the new interface release a package which
disables the old interface.
This is the same process other packages go through, whether things like
Emacs or Apache or Inetd or anything else that has to interface with other
packages. They don't just change interfaces and leave it to people to
discover everything else is broken.
On Fri, Jun 19, 2009 at 10:18 AM, Debian Bug Tracking System
ow...@bugs.debian.org wrote:
This is an automatic notification regarding your Bug report
which was filed against the linux-image-2.6.29-2-686 package:
#533574: linux-image-2.6.29-2-686: Optoin CONFIG_ACPI_PROCFS_POWER is not
set -- battery monitors don't work
It has been closed by Bastian Blank wa...@debian.org.
Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Bastian Blank
wa...@debian.org by
replying to this email.
--
533574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=533574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
-- Forwarded message --
From: Bastian Blank wa...@debian.org
To: 533574-d...@bugs.debian.org
Date: Fri, 19 Jun 2009 11:15:44 +0200
Subject: Re: Bug#533574: linux-image-2.6.29-2-686: Optoin
CONFIG_ACPI_PROCFS_POWER is not set -- battery monitors don't work
On Thu, Jun 18, 2009 at 11:16:25PM +0100, Gregory Stark wrote:
The ACPI battery module appears to be built with CONFIG_ACPI_PROCFS_POWER
unset. That leaves it pretty useless. Things like gui battery monitors
and
even powertop require this file to report the battery usage.
The information is properly exported in the sysfs:
| $ cat /sys/class/power_supply/BAT0/{charge_{full,now},voltage_now}
| 545
| 545
| 8316000
If the tools are not able to use them, it is their bug. No bug in the
kernel.
Bastian
--
There is an order of things in this universe.
-- Apollo, Who Mourns for Adonais? stardate 3468.1
-- Forwarded message --
From: Gregory Stark st...@enterprisedb.com
To: Debian Bug Tracking System sub...@bugs.debian.org
Date: Thu, 18 Jun 2009 23:16:25 +0100
Subject: linux-image-2.6.29-2-686: Optoin CONFIG_ACPI_PROCFS_POWER is not
set -- battery monitors don't work
Package: linux-image-2.6.29-2-686
Version: 2.6.29-5
Severity: wishlist
File: /lib/modules/2.6.29-2-686/kernel/drivers/acpi/battery.ko
The ACPI battery module appears to be built with CONFIG_ACPI_PROCFS_POWER
unset. That leaves it pretty useless. Things like gui battery monitors and
even powertop require this file to report the battery usage.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.29-2-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to
C)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.29-2-686 depends on:
ii debconf [debconf-2.0]1.5.24 Debian configuration
management sy
ii initramfs-tools [linux-initr 0.91e tools for generating an
initramfs
ii module-init-tools3.3-pre11-4 tools for managing Linux
kernel mo
Versions of packages linux-image-2.6.29-2-686 recommends:
ii libc6-i6862.9-16 GNU C Library: Shared
libraries [i
-- debconf information:
linux-image-2.6.29-2-686/preinst/overwriting-modules-2.6.29-2-686: true
linux-image-2.6.29-2-686/postinst/bootloader-error-2.6.29-2-686:
linux-image-2.6.29-2-686/preinst/abort-install-2.6.29-2-686:
linux-image-2.6.29-2-686/preinst/failed-to-move-modules-2.6.29-2-686:
linux-image-2.6.29-2-686/preinst/initrd-2.6.29-2-686:
linux-image-2.6.29-2-686/postinst/old-dir-initrd-link-2.6.29-2-686: true
linux-image-2.6.29-2-686/postinst/old-initrd-link-2.6.29-2-686: true
linux-image-2.6.29-2-686/postinst/bootloader-test-error-2.6.29-2-686:
linux-image-2.6.29-2-686/postinst/depmod-error-initrd-2.6.29-2-686: false
linux-image-2.6.29-2-686/preinst/elilo-initrd-2.6.29-2-686: true
linux-image-2.6.29-2-686/preinst/lilo-initrd-2.6.29-2-686: true
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.29-2-686/preinst/lilo-has-ramdisk:
linux-image-2.6.29-2-686/postinst/depmod-error-2.6.29-2-686: false
linux-image-2.6.29-2-686/postinst/kimage-is-a-directory:
linux-image-2.6.29-2-686/postinst/create-kimage-link-2.6.29-2-686: true
linux-image-2.6.29-2-686/prerm/removing-running-kernel-2.6.29-2-686: true
Bug#533616: linux-image-2.6.29-2-amd64: occasional ext3 filesystem corruption
Package: linux-image-2.6.29-2-amd64 Version: 2.6.29-5 Severity: grave Justification: causes non-serious data loss Yesterday, I found my root filesystem mounted read-only. Dmesg gave the following messages (retyped by hand, which is why the timestamps are missing): EXT3-fs error (device sda3): htree_dirblock_to_tree: bad entry in directory #91119000: directory entry accross blocks - offset=0, inode=2364050278, rec_len=36552, name-len=216 Aborting journal on device sda3. Remounting filesystem read-only __journal_remove_journal_head: freeing b_comitted_data Note the ridiculously large inode number mentioned in the first line. After reboot, I needed to run fsck from the root prompt. An orphaned inode list was fixed, a zero dtime was fixed, block bitmap differences were fixed, free block counts were fixed, free inode counts were fixed. I seem to recall inode bitmap differences were also fixed. -- Package-specific info: ** Version: Linux version 2.6.29-2-amd64 (Debian 2.6.29-5) (wa...@debian.org) (gcc version 4.3.3 (Debian 4.3.3-10) ) #1 SMP Sun May 17 17:15:47 UTC 2009 ** Command line: root=/dev/sda3 ro ** Not tainted ** Kernel log: [10757.264576] firewire_ohci :03:03.0: restoring config space at offset 0x3 (was 0x0, writing 0xf810) [10757.264576] firewire_ohci :03:03.0: restoring config space at offset 0x1 (was 0x290, writing 0x2900216) [10757.264576] Enabling non-boot CPUs ... [10757.264576] SMP alternatives: switching to SMP code [10757.387717] Booting processor 1 APIC 0x1 ip 0x6000 [10757.264016] Initializing CPU#1 [10757.264016] Calibrating delay using timer specific routine.. 4322.66 BogoMIPS (lpj=8645327) [10757.264016] CPU: L1 I cache: 32K, L1 D cache: 32K [10757.264016] CPU: L2 cache: 4096K [10757.264016] CPU 1/0x1 - Node 0 [10757.264016] CPU: Physical Processor ID: 0 [10757.264016] CPU: Processor Core ID: 1 [10757.264016] CPU1: Thermal monitoring enabled (TM2) [10757.476572] CPU1: Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz stepping 06 [10757.476614] CPU0 attaching NULL sched-domain. [10757.477015] Switched to high resolution mode on CPU 1 [10757.488758] CPU0 attaching sched-domain: [10757.488761] domain 0: span 0-1 level MC [10757.488762] groups: 0 1 [10757.488766] CPU1 attaching sched-domain: [10757.488767] domain 0: span 0-1 level MC [10757.488769] groups: 1 0 [10757.492025] CPU1 is up [10757.492027] ACPI: Waking up from system sleep state S3 [10757.696555] ACPI: EC: non-query interrupt received, switching to interrupt mode [10757.859613] pci :00:02.0: PME# disabled [10757.859618] pci :00:02.1: PME# disabled [10757.859621] pci :00:07.0: PME# disabled [10757.859679] HDA Intel :00:1b.0: PCI INT A - GSI 22 (level, low) - IRQ 22 [10757.859685] HDA Intel :00:1b.0: setting latency timer to 64 [10757.859716] pcieport-driver :00:1c.0: setting latency timer to 64 [10757.859725] pcieport-driver :00:1c.1: setting latency timer to 64 [10757.859760] uhci_hcd :00:1d.0: PCI INT A - GSI 21 (level, low) - IRQ 21 [10757.859765] uhci_hcd :00:1d.0: setting latency timer to 64 [10757.859790] usb usb2: root hub lost power or was reset [10757.859850] uhci_hcd :00:1d.1: PCI INT B - GSI 19 (level, low) - IRQ 19 [10757.859855] uhci_hcd :00:1d.1: setting latency timer to 64 [10757.859879] usb usb3: root hub lost power or was reset [10757.859922] uhci_hcd :00:1d.2: PCI INT C - GSI 18 (level, low) - IRQ 18 [10757.859928] uhci_hcd :00:1d.2: setting latency timer to 64 [10757.859951] usb usb4: root hub lost power or was reset [10757.860004] uhci_hcd :00:1d.3: PCI INT D - GSI 16 (level, low) - IRQ 16 [10757.860038] uhci_hcd :00:1d.3: setting latency timer to 64 [10757.860070] usb usb5: root hub lost power or was reset [10757.860140] ehci_hcd :00:1d.7: PME# disabled [10757.860144] ehci_hcd :00:1d.7: PCI INT A - GSI 21 (level, low) - IRQ 21 [10757.860150] ehci_hcd :00:1d.7: setting latency timer to 64 [10757.860156] ehci_hcd :00:1d.7: PME# disabled [10757.860248] pci :00:1e.0: power state changed by ACPI to D0 [10757.860255] pci :00:1e.0: setting latency timer to 64 [10757.860297] PIIX_IDE :00:1f.1: power state changed by ACPI to D0 [10757.860333] PIIX_IDE :00:1f.1: power state changed by ACPI to D0 [10757.860337] PIIX_IDE :00:1f.1: PCI INT A - GSI 18 (level, low) - IRQ 18 [10757.860361] PIIX_IDE :00:1f.1: restoring config space at offset 0x1 (was 0x2880005, writing 0x285) [10757.860370] PIIX_IDE :00:1f.1: setting latency timer to 64 [10757.860415] ata_piix :00:1f.2: PCI INT B - GSI 19 (level, low) - IRQ 19 [10757.860419] ata_piix :00:1f.2: setting latency timer to 64 [10757.860526] sky2 :01:00.0: restoring config space at offset 0x1 (was 0x40100407, writing 0x100407) [10757.860588] sky2 :01:00.0: PME# disabled [10757.860635] ath9k :02:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 [10757.932148] firewire_core: skipped bus generations, destroying all
Bug#532908: Please fix this grave bug
On Thu, 2009-06-18 at 23:25 +0200, maximilian attems wrote: better complain at the kernel-package maintainer who decided this. It is the job of maintainers to include these scripts in initramfs-tools? I can see scripts in the package. The problem is that initramfs-tools scripts are probably outdated. So why not replace them? Kind regards, JM -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#517241: [alsa-devel] Laptop (Samsung Q45) speakers unmute when master channel is unmuted even with headphones connected
On Thu, 2009-05-07 at 17:11 +0200, Takashi Iwai wrote: At Tue, 05 May 2009 11:58:39 +0100, Sam Morris wrote: On Tue, 2009-05-05 at 12:47 +0200, Takashi Iwai wrote: At Sat, 2 May 2009 13:14:42 +0100, Sam Morris wrote: Since Linux 2.6.28 and through to 2.6.30-rc4, the hda-intel driver has had a bug on my laptop (a Samsung Q45). If I connect my headphones, the laptop's internal speakers are muted--fine. But if I then mute and unmute the master mixer channel, the speakers come back to life, even though the headphones are still connected. Could you run alsa-info.sh with --no-upload option, and attach the generated file? Here you go! Thanks. What if you use model=auto option? This is fixed in 2.6.30, but only if I use the model=auto option. :) Takashi -- Sam Morris s...@robots.org.uk -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533550: i915: kernel mode setting -- wrong resolution
On Thu, Jun 18, 2009 at 17:55:17 +0200, Julian Andres Klode wrote: Package: linux-image-2.6.30-1-amd64 Version: 2.6.30-1 Severity: normal When running with kernel modesetting, the resolution of the console is set to 1024x768 although the native resolution is 1280x800. The X server works correctly at 1280x800 and if I recall correctly, kernel 2.6.29 used the correct resolution for consoles. Another point is that the kernel reports: [1.731636] allocated 1280x800 fb: 0x007df000, bo 8800377b3d40 [1.793657] [drm] TV-13: set mode 1024x768 18 [1.873923] [drm] LVDS-8: set mode 1280x800 15 which says that the framebuffer should be 1280x800, AFAIK. Is a TV really connected? If not this should be fixed with: commit 03d6069912babc07a3da20e715dd6a5dc8f0f867 Author: Keith Packard kei...@keithp.com Date: Fri Jun 5 18:19:56 2009 -0700 drm/i915: Hook connector to encoder during load detection (fixes tv/vga detect With the DRM-driven DPMS code, encoders are considered idle unless a connector is hooked to them, so mode setting is skipped. This makes load detection fail as none of the hardware is enabled. Signed-off-by: Keith Packard kei...@keithp.com Signed-off-by: Eric Anholt e...@anholt.net Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 533616 is important, tagging 533616
Processing commands for cont...@bugs.debian.org: severity 533616 important Bug#533616: linux-image-2.6.29-2-amd64: occasional ext3 filesystem corruption Severity set to `important' from `grave' tags 533616 moreinfo Bug#533616: linux-image-2.6.29-2-amd64: occasional ext3 filesystem corruption There were no tags set. Tags added: moreinfo 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: closing 523121
Processing commands for cont...@bugs.debian.org: close 523121 2.6.30-1 Bug#523121: error: conflicting types for 'fd_set' 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug#526581: xgalaga: FTBFS: conflicting types for 'fd_set' Bug marked as fixed in version 2.6.30-1, send any further explanations to Kurt Roeckx k...@roeckx.be 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#533616: linux-image-2.6.29-2-amd64: occasional ext3 filesystem corruption
severity 533616 important tags 533616 moreinfo thanks On Fri, Jun 19, 2009 at 12:38:12PM +0200, Matijs van Zuijlen wrote: Yesterday, I found my root filesystem mounted read-only. Dmesg gave the following messages (retyped by hand, which is why the timestamps are missing): EXT3-fs error (device sda3): htree_dirblock_to_tree: bad entry in directory #91119000: directory entry accross blocks - offset=0, inode=2364050278, rec_len=36552, name-len=216 Aborting journal on device sda3. Remounting filesystem read-only __journal_remove_journal_head: freeing b_comitted_data Note the ridiculously large inode number mentioned in the first line. After reboot, I needed to run fsck from the root prompt. An orphaned inode list was fixed, a zero dtime was fixed, block bitmap differences were fixed, free block counts were fixed, free inode counts were fixed. I seem to recall inode bitmap differences were also fixed. Log from the fsck run? Some of the differences are normal if the journal got aborted. But overall this looks like bad hardware, most likely memory. Bastian -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533574: closed by Bastian Blank wa...@debian.org (Re: Bug#533574: linux-image-2.6.29-2-686: Optoin CONFIG_ACPI_PROCFS_POWER is not set -- battery monitors don't work)
On Fri, 2009-06-19 at 11:26 +0100, Greg Stark wrote: I don't think this is the right way to go about changing interfaces between packages in Debian. The correct way to go about this is to propose a new packaging policy that packages use the sysfs interface. When that's approved then issue bug reports against all packages using the old interface. Then when all or most of those packages have switched to the new interface release a package which disables the old interface. The correct way is for upstream to announce the change in feature-removal-schedule.txt, which they did 2 years ago. Ben. -- Ben Hutchings The generation of random numbers is too important to be left to chance. - Robert Coveyou signature.asc Description: This is a digitally signed message part
Bug#533550: i915: kernel mode setting -- wrong resolution
On Fri, Jun 19, 2009 at 01:35:56PM +0200, Julien Cristau wrote: On Thu, Jun 18, 2009 at 17:55:17 +0200, Julian Andres Klode wrote: [1.793657] [drm] TV-13: set mode 1024x768 18 Is a TV really connected? If not this should be fixed with: I don't even have a TV output, so none can be connected. commit 03d6069912babc07a3da20e715dd6a5dc8f0f867 Author: Keith Packard kei...@keithp.com Date: Fri Jun 5 18:19:56 2009 -0700 drm/i915: Hook connector to encoder during load detection (fixes tv/vga detect With the DRM-driven DPMS code, encoders are considered idle unless a connector is hooked to them, so mode setting is skipped. This makes load detection fail as none of the hardware is enabled. Signed-off-by: Keith Packard kei...@keithp.com Signed-off-by: Eric Anholt e...@anholt.net -- Julian Andres Klode - Free Software Developer Debian Developer - Contributing Member of SPI Ubuntu Member - Fellow of FSFE Website: http://jak-linux.org/ XMPP: juli...@jabber.org Debian: http://www.debian.org/ SPI: http://www.spi-inc.org/ Ubuntu: http://www.ubuntu.com/ FSFE: http://www.fsfe.org/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#517241: [alsa-devel] Laptop (Samsung Q45) speakers unmute when master channel is unmuted even with headphones connected
At Fri, 19 Jun 2009 11:56:29 +0100, Sam Morris wrote: On Thu, 2009-05-07 at 17:11 +0200, Takashi Iwai wrote: At Tue, 05 May 2009 11:58:39 +0100, Sam Morris wrote: On Tue, 2009-05-05 at 12:47 +0200, Takashi Iwai wrote: At Sat, 2 May 2009 13:14:42 +0100, Sam Morris wrote: Since Linux 2.6.28 and through to 2.6.30-rc4, the hda-intel driver has had a bug on my laptop (a Samsung Q45). If I connect my headphones, the laptop's internal speakers are muted--fine. But if I then mute and unmute the master mixer channel, the speakers come back to life, even though the headphones are still connected. Could you run alsa-info.sh with --no-upload option, and attach the generated file? Here you go! Thanks. What if you use model=auto option? This is fixed in 2.6.30, but only if I use the model=auto option. :) What about with the later version, e.g. Linus git tree? Or you can use sound git tree git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git I think this was already fixed there. Takashi -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#517241: [alsa-devel] Laptop (Samsung Q45) speakers unmute when master channel is unmuted even with headphones connected
On Fri, 2009-06-19 at 14:53 +0200, Takashi Iwai wrote: At Fri, 19 Jun 2009 11:56:29 +0100, Sam Morris wrote: On Thu, 2009-05-07 at 17:11 +0200, Takashi Iwai wrote: At Tue, 05 May 2009 11:58:39 +0100, Sam Morris wrote: On Tue, 2009-05-05 at 12:47 +0200, Takashi Iwai wrote: At Sat, 2 May 2009 13:14:42 +0100, Sam Morris wrote: Since Linux 2.6.28 and through to 2.6.30-rc4, the hda-intel driver has had a bug on my laptop (a Samsung Q45). If I connect my headphones, the laptop's internal speakers are muted--fine. But if I then mute and unmute the master mixer channel, the speakers come back to life, even though the headphones are still connected. Could you run alsa-info.sh with --no-upload option, and attach the generated file? Here you go! Thanks. What if you use model=auto option? This is fixed in 2.6.30, but only if I use the model=auto option. :) What about with the later version, e.g. Linus git tree? Or you can use sound git tree git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git I think this was already fixed there. Takashi -- Sam Morris s...@robots.org.uk -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#532908: Please fix this grave bug
On Fri, Jun 19, 2009 at 12:47:28PM +0200, Jean-Michel Pouré wrote: On Thu, 2009-06-18 at 23:25 +0200, maximilian attems wrote: better complain at the kernel-package maintainer who decided this. It is the job of maintainers to include these scripts in initramfs-tools? I can see scripts in the package. The problem is that initramfs-tools scripts are probably outdated. So why not replace them? i'll happily include updates, as i arlready told several times, no one has come forward with a working patch. you shall test *first* against linux-2.6 prebuild, secondly aginst make deb-pkg and last but not least against kernel-package. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#517748: linux-image-2.6.26-1-686 System locks up under heavy disk load (MD Resync e.g.)
I have got the same locks up problem, I believe. I have an NC20 netbook and under heavy hard drive load, the system locks up. This is my lspci: 00:00.0 Host bridge: VIA Technologies, Inc. VX800 Host Bridge (rev 12) 00:00.1 Host bridge: VIA Technologies, Inc. VX800/VX820 Error Reporting 00:00.2 Host bridge: VIA Technologies, Inc. VX800/VX820 Host Bus Control 00:00.3 Host bridge: VIA Technologies, Inc. VX800 PCI to PCI Bridge 00:00.4 Host bridge: VIA Technologies, Inc. VX800/VX820 Power Management Control 00:00.5 PIC: VIA Technologies, Inc. VX800/VX820 APIC and Central Traffic Control 00:00.6 Host bridge: VIA Technologies, Inc. VX800/VX820 Scratch Registers 00:00.7 Host bridge: VIA Technologies, Inc. VX800/VX820 North-South Module Interface Control 00:01.0 VGA compatible controller: VIA Technologies, Inc. Device 1122 (rev 11) 00:03.0 PCI bridge: VIA Technologies, Inc. VX800/VX820 PCI Express Root Port 00:03.1 PCI bridge: VIA Technologies, Inc. VX800/VX820 PCI Express Root Port 00:0d.0 FLASH memory: VIA Technologies, Inc. Secure Digital Memory Card Controller 00:0f.0 IDE interface: VIA Technologies, Inc. VX800 Serial ATA and EIDE Controller 00:10.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev a0) 00:10.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev a0) 00:10.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev a0) 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 90) 00:11.0 ISA bridge: VIA Technologies, Inc. VX800/VX820 Bus Control and Power Management 00:11.7 Host bridge: VIA Technologies, Inc. VX800/VX820 South-North Module Interface Control 00:14.0 Audio device: VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) (rev 20) 01:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller (rev 13) We seem to have the same VX800 IDE interface. Also, I have Ubuntu Jaunty installed with kernel 2.6.28-13-generic. I wanted to post my reply on the Debian bug report page, but I did not understand how. Could you do that? Giulio -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533657: linux-image-2.6.26-2-686: Bug with sata_nv
Package: linux-image-2.6.26-2-686 Version: 2.6.26-16 Severity: important The hardware: A Plextor PX-810SA DVD-writer on a AsRock K8Upgrade-NF3 motherboard. With lenny kernel 2.6.26-2-686 syslog is spammed with tons of messages saying ata2: EH complete each two seconds (or so). This doesn't happen when using backports kernel 2.6.29-bpo.2-686 or backports etch kernel 2.6.22-2-k7. Some websearches revealed that this appears to be an issue with the sata_nv driver (e.g. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/269652), at least I suspect the problems described there are as same as here. Please send me a note if any additional information is required. Regards Michael Lange -- Package-specific info: ** Version: Linux version 2.6.26-2-686 (Debian 2.6.26-16) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Tue Jun 9 16:04:54 UTC 2009 ** Command line: root=LABEL=CRYPTOROOT ro vga=773 ** Not tainted ** Kernel log: [ 416.720042] ata2: EH complete [ 418.720045] ata2: EH complete [ 420.720035] ata2: EH complete [ 422.720045] ata2: EH complete [ 424.720044] ata2: EH complete [ 426.720057] ata2: EH complete [ 428.724038] ata2: EH complete [ 430.724040] ata2: EH complete [ 432.720059] ata2: EH complete [ 434.720069] ata2: EH complete [ 436.720195] ata2: EH complete [ 438.720060] ata2: EH complete [ 440.720059] ata2: EH complete [ 442.720060] ata2: EH complete [ 444.720060] ata2: EH complete [ 446.720203] ata2: EH complete [ 448.720204] ata2: EH complete [ 450.720199] ata2: EH complete [ 452.720198] ata2: EH complete [ 454.720154] ata2: EH complete [ 456.720191] ata2: EH complete [ 458.720214] ata2: EH complete [ 460.720207] ata2: EH complete [ 462.720209] ata2: EH complete [ 464.720220] ata2: EH complete [ 466.720207] ata2: EH complete [ 468.720202] ata2: EH complete [ 470.720065] ata2: EH complete [ 472.720043] ata2: EH complete [ 474.720046] ata2: EH complete [ 476.720046] ata2: EH complete [ 478.720060] ata2: EH complete [ 480.720045] ata2: EH complete [ 482.720043] ata2: EH complete [ 484.720056] ata2: EH complete [ 486.720043] ata2: EH complete [ 488.720039] ata2: EH complete [ 490.720036] ata2: EH complete [ 492.720055] ata2: EH complete [ 494.720038] ata2: EH complete [ 496.720047] ata2: EH complete [ 498.720036] ata2: EH complete [ 500.720039] ata2: EH complete [ 502.720038] ata2: EH complete [ 504.720037] ata2: EH complete [ 506.720068] ata2: EH complete [ 508.720039] ata2: EH complete [ 510.724042] ata2: EH complete [ 512.720060] ata2: EH complete [ 514.720039] ata2: EH complete [ 516.720038] ata2: EH complete [ 518.720053] ata2: EH complete [ 520.720041] ata2: EH complete [ 522.720035] ata2: EH complete [ 524.720049] ata2: EH complete [ 526.720059] ata2: EH complete [ 528.720038] ata2: EH complete [ 530.720063] ata2: EH complete [ 532.720055] ata2: EH complete [ 534.724038] ata2: EH complete [ 536.720037] ata2: EH complete [ 538.720038] ata2: EH complete [ 540.720035] ata2: EH complete [ 542.720038] ata2: EH complete [ 544.720040] ata2: EH complete [ 546.720040] ata2: EH complete [ 548.720037] ata2: EH complete [ 550.720036] ata2: EH complete [ 552.720039] ata2: EH complete [ 554.720040] ata2: EH complete [ 556.720039] ata2: EH complete [ 558.720042] ata2: EH complete [ 560.720065] ata2: EH complete [ 562.720036] ata2: EH complete [ 564.724039] ata2: EH complete [ 566.720038] ata2: EH complete [ 568.720040] ata2: EH complete [ 570.720039] ata2: EH complete [ 572.720036] ata2: EH complete [ 574.720036] ata2: EH complete [ 576.720039] ata2: EH complete [ 578.720038] ata2: EH complete [ 580.720039] ata2: EH complete [ 582.720039] ata2: EH complete [ 584.720038] ata2: EH complete [ 586.720041] ata2: EH complete [ 588.720040] ata2: EH complete [ 590.720037] ata2: EH complete [ 592.720038] ata2: EH complete [ 594.720039] ata2: EH complete [ 596.720038] ata2: EH complete [ 598.720039] ata2: EH complete [ 600.720038] ata2: EH complete [ 602.720039] ata2: EH complete [ 604.720042] ata2: EH complete [ 606.721634] ata2: EH complete [ 608.720038] ata2: EH complete [ 610.720051] ata2: EH complete [ 612.720056] ata2: EH complete [ 614.720043] ata2: EH complete ** Loaded modules: Module Size Used by xt_TCPMSS 3616 1 pppoe 8672 2 pppox 3116 1 pppoe ppp_generic20028 6 pppoe,pppox slhc5376 1 ppp_generic binfmt_misc 7528 1 battery10180 0 ppdev 6500 0 parport_pc 22500 0 lp 8164 0 parport30988 3 ppdev,parport_pc,lp cpufreq_stats 3776 0 cpufreq_conservative 5960 0 cpufreq_powersave 1856 0 cpufreq_ondemand6476 0 ip6table_filter 2432 1 ip6_tables 11376 1 ip6table_filter xt_hashlimit9360 0
Bug#533657: linux-image-2.6.26-2-686: Bug with sata_nv
On Fri, Jun 19, 2009 at 06:19:20PM +0200, Michael Lange wrote: Package: linux-image-2.6.26-2-686 Version: 2.6.26-16 Severity: important The hardware: A Plextor PX-810SA DVD-writer on a AsRock K8Upgrade-NF3 motherboard. With lenny kernel 2.6.26-2-686 syslog is spammed with tons of messages saying ata2: EH complete each two seconds (or so). This doesn't happen when using backports kernel 2.6.29-bpo.2-686 or backports etch kernel 2.6.22-2-k7. Some websearches revealed that this appears to be an issue with the sata_nv driver (e.g. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/269652), at least I suspect the problems described there are as same as here. Please send me a note if any additional information is required. Does this occur with 2.6.26-15lenny3? Regards Michael Lange -- Package-specific info: ** Version: Linux version 2.6.26-2-686 (Debian 2.6.26-16) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Tue Jun 9 16:04:54 UTC 2009 ** Command line: root=LABEL=CRYPTOROOT ro vga=773 ** Not tainted ** Kernel log: [ 416.720042] ata2: EH complete [ 418.720045] ata2: EH complete [ 420.720035] ata2: EH complete [ 422.720045] ata2: EH complete [ 424.720044] ata2: EH complete [ 426.720057] ata2: EH complete [ 428.724038] ata2: EH complete [ 430.724040] ata2: EH complete [ 432.720059] ata2: EH complete [ 434.720069] ata2: EH complete [ 436.720195] ata2: EH complete [ 438.720060] ata2: EH complete [ 440.720059] ata2: EH complete [ 442.720060] ata2: EH complete [ 444.720060] ata2: EH complete [ 446.720203] ata2: EH complete [ 448.720204] ata2: EH complete [ 450.720199] ata2: EH complete [ 452.720198] ata2: EH complete [ 454.720154] ata2: EH complete [ 456.720191] ata2: EH complete [ 458.720214] ata2: EH complete [ 460.720207] ata2: EH complete [ 462.720209] ata2: EH complete [ 464.720220] ata2: EH complete [ 466.720207] ata2: EH complete [ 468.720202] ata2: EH complete [ 470.720065] ata2: EH complete [ 472.720043] ata2: EH complete [ 474.720046] ata2: EH complete [ 476.720046] ata2: EH complete [ 478.720060] ata2: EH complete [ 480.720045] ata2: EH complete [ 482.720043] ata2: EH complete [ 484.720056] ata2: EH complete [ 486.720043] ata2: EH complete [ 488.720039] ata2: EH complete [ 490.720036] ata2: EH complete [ 492.720055] ata2: EH complete [ 494.720038] ata2: EH complete [ 496.720047] ata2: EH complete [ 498.720036] ata2: EH complete [ 500.720039] ata2: EH complete [ 502.720038] ata2: EH complete [ 504.720037] ata2: EH complete [ 506.720068] ata2: EH complete [ 508.720039] ata2: EH complete [ 510.724042] ata2: EH complete [ 512.720060] ata2: EH complete [ 514.720039] ata2: EH complete [ 516.720038] ata2: EH complete [ 518.720053] ata2: EH complete [ 520.720041] ata2: EH complete [ 522.720035] ata2: EH complete [ 524.720049] ata2: EH complete [ 526.720059] ata2: EH complete [ 528.720038] ata2: EH complete [ 530.720063] ata2: EH complete [ 532.720055] ata2: EH complete [ 534.724038] ata2: EH complete [ 536.720037] ata2: EH complete [ 538.720038] ata2: EH complete [ 540.720035] ata2: EH complete [ 542.720038] ata2: EH complete [ 544.720040] ata2: EH complete [ 546.720040] ata2: EH complete [ 548.720037] ata2: EH complete [ 550.720036] ata2: EH complete [ 552.720039] ata2: EH complete [ 554.720040] ata2: EH complete [ 556.720039] ata2: EH complete [ 558.720042] ata2: EH complete [ 560.720065] ata2: EH complete [ 562.720036] ata2: EH complete [ 564.724039] ata2: EH complete [ 566.720038] ata2: EH complete [ 568.720040] ata2: EH complete [ 570.720039] ata2: EH complete [ 572.720036] ata2: EH complete [ 574.720036] ata2: EH complete [ 576.720039] ata2: EH complete [ 578.720038] ata2: EH complete [ 580.720039] ata2: EH complete [ 582.720039] ata2: EH complete [ 584.720038] ata2: EH complete [ 586.720041] ata2: EH complete [ 588.720040] ata2: EH complete [ 590.720037] ata2: EH complete [ 592.720038] ata2: EH complete [ 594.720039] ata2: EH complete [ 596.720038] ata2: EH complete [ 598.720039] ata2: EH complete [ 600.720038] ata2: EH complete [ 602.720039] ata2: EH complete [ 604.720042] ata2: EH complete [ 606.721634] ata2: EH complete [ 608.720038] ata2: EH complete [ 610.720051] ata2: EH complete [ 612.720056] ata2: EH complete [ 614.720043] ata2: EH complete ** Loaded modules: Module Size Used by xt_TCPMSS 3616 1 pppoe 8672 2 pppox 3116 1 pppoe ppp_generic20028 6 pppoe,pppox slhc5376 1 ppp_generic binfmt_misc 7528 1 battery10180 0 ppdev 6500 0 parport_pc 22500 0 lp 8164 0 parport30988 3 ppdev,parport_pc,lp
Bug#533657: linux-image-2.6.26-2-686: Bug with sata_nv
Hi, On Fri, 19 Jun 2009 12:26:17 -0600 dann frazier da...@debian.org wrote: (...) Does this occur with 2.6.26-15lenny3? No, it doesn't! In fact dmesg tells me: m...@debian:~$ dmesg |grep ata2 [6.197265] ata2: SATA max UDMA/133 cmd 0xe80 ctl 0xe00 bmdma 0xe008 irq 21 [7.028025] ata2: SATA link down (SStatus 0 SControl 300) m...@debian:~$ and I guess the missing SATA link down indicated the problem with the other kernel? With 2.6.26-15lenny3 everything seems to be fine. Michael -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#497971: This bugs affects lenny badly
Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-15lenny3 Hi, my girlfriends laptop runs Debian Lenny. With the current kernel in Lenny, she is unable to connect to a channel 13 network, using the iwl3945 module. I did try to set the regdom to EU via a file in /etc/moodprobe.d/, and the parameter gets set (as can be seen in /sys/modules/cfg80211/parameters/ieee80211_regdom), but it does not have an effect on iwl3945 (as can be seen with iwlist wlan0 channel). I think it is a severe issue not to be able to connect to such a channel and, if possible, should be fixed in a lenny point release. Thanks, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Bug#497971: This bugs affects lenny badly
On Fri, Jun 19, 2009 at 08:34:16PM +, Joachim Breitner wrote: my girlfriends laptop runs Debian Lenny. With the current kernel in Lenny, she is unable to connect to a channel 13 network, using the iwl3945 module. Log? Otherwise I assume that you are using a MOW1 card. Bastian -- No one wants war. -- Kirk, Errand of Mercy, stardate 3201.7 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: closing 497971
Processing commands for cont...@bugs.debian.org: close 497971 2.6.26-6 Bug#497971: linux-image-2.6.26-1-686: iwl3945 : Channels 12 and 13 unavailable. 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug#525247: iwl3945 : Channels 12 and 13 unavailable. Bug marked as fixed in version 2.6.26-6, send any further explanations to Hugo Grostabussiat dw23.de...@gmail.com 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#533657: linux-image-2.6.26-2-686: Bug with sata_nv
On Fri, Jun 19, 2009 at 09:21:21PM +0200, Michael Lange wrote: Hi, On Fri, 19 Jun 2009 12:26:17 -0600 dann frazier da...@debian.org wrote: (...) Does this occur with 2.6.26-15lenny3? No, it doesn't! In fact dmesg tells me: m...@debian:~$ dmesg |grep ata2 [6.197265] ata2: SATA max UDMA/133 cmd 0xe80 ctl 0xe00 bmdma 0xe008 irq 21 [7.028025] ata2: SATA link down (SStatus 0 SControl 300) m...@debian:~$ and I guess the missing SATA link down indicated the problem with the other kernel? With 2.6.26-15lenny3 everything seems to be fine. Michael, Thanks for the feedback. Can you try this kernel and report back? http://people.debian.org/~dannf/bugs/533657/ -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533657: linux-image-2.6.26-2-686: Bug with sata_nv
On Fri, 19 Jun 2009 15:22:32 -0600 dann frazier da...@debian.org wrote: (...) Michael, Thanks for the feedback. Can you try this kernel and report back? http://people.debian.org/~dannf/bugs/533657/ -- dann frazier A quick test does not show any problems, dmesg says: debian:/home/pingu# dmesg | grep ata2 [6.181720] ata2: SATA max UDMA/133 cmd 0xe80 ctl 0xe00 bmdma 0xe008 irq 21 debian:/home/pingu# Looks good! Michael -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RE: Applying e1000e patch to the Debian 2.6.26 kernel
Dear Thomas, Good afternoon. I deeply appreciate for this, and I will always try my very best working with you or any customers. Our company web site is www.kingstarusa.com, and yes, my e-mail address is j...@kingstarusa.com. I sincerely look forward to hearing from you for any questions or quote requests. Have a nice weekend. Best Regards! John Wu King Star Computer 1259 Reamwood Avenue Sunnyvale, CA 94089 TEL: 408-736-8590 ex. 107 FAX: 408-736-4151 j...@kingstarusa.com - Supermicro Preferred System Provider. - Asus Tyan Approved System Integrator. - Intel Premier Channel Partner 2009. - AMD Solution Provider. - nVidia Authorized System Integrator, Tesla C1060, S1070, etc. - Lenovo Approved Solution Partner Reseller. - InforTrend FC, SAS, SATA, SCSI, iSCSI Storage Provider. -Original Message- From: Thomas Goirand [mailto:tho...@goirand.fr] Sent: Friday, June 19, 2009 1:52 PM To: Ben Hutchings Cc: dann frazier; debian-kernel@lists.debian.org; i...@gplhost.com; John Wu Subject: Re: Applying e1000e patch to the Debian 2.6.26 kernel Thomas Goirand wrote: Ben Hutchings wrote: On Tue, Jun 16, 2009 at 12:50:34AM +0800, Thomas Goirand wrote: [...] So I'm wondering, did somebody applied some patches for e1000e between the release of Lenny 5.01? Or maybe, the e1000e on the X8STi-3F is different from the one of my Thinkpad t500? Is there even different versions of the board at Intel? [...] There are many slightly different chips handled by the e1000e driver. If it was broken for all of them we would have fixed it before release! You have to test on the specific model which the kernel from lenny doesn't work on. Ben. That is quite what I think as well. Here's what I am up to. 1/ The Debian kernel, which USED to have no support for my Thinkpad e1000e works fully now. Someone MUST have done something to the kernel, because I'm 100% sure that at the time of Lenny, it was not working. 2/ On our last test on the Supermicro board, it did FAIL last week. Now, I have asked my hardware supplier to put one of these X8STi-F online in order to test with it, he has been very nice, and he said he will. I'll be able to do a full test and report here. Thanks to you all for helping me to find out what's going on! Thomas Hi again, Finally, my hardware supplier in California has been VERY nice, and has made it possible for me to have access to a server equipped with the Supermicro X8STi-F motherboard that we want to use later on in production. As the guy is really awesome, I want to name him publicly. If you need any kind of hardware for servers, ask to talk to John Wu at KingstarUSA in California. He will reply to you within minutes, and make reasonable quotes. He will also be able to support you with any issue (like now). Drop him a mail if you need, his is as Cc: here. Give him some business, he deserves it! Anyway, back to the patch. I have tried to apply all the patches that Ben sent to me, and this is NOT ENOUGH to have the e1000e working. In fact, we have to realize that, if it's still the same Ethernet controller name (I mean e1000e), it's quite a different controller. The one on that motherboard is a 82574L, which seems to be a more recent model. The driver source in the kernel has many specificities for it. So if you guys, at the kernel team, decide to add and maintain a patch, this will NOT be a tiny one just adding new PCI IDs... Please read (quickly) the diff file that I have attached, it shows better than anything else what I'm talking about. It was done the wrong way: taking the sources from 2.6.29 (from backports.org), making a diff -r -u of the e1000e folder, and apply corrections until it compiles, including some kernel API changes that I had to backport. It's a bit ugly, but IT DOES work very well, and I'm quite happy that I have at least the solution to apply this patch to the Debian kernel sources. Now, if you still think that there is a possibility to have a patch included (which would be, to my eyes, a very wise decision), I guess that I'd need to apply patches from Git again in order to make it cleaner and smaller. I have searched, and couldn't find the gitweb for the e1000e project. Ben Hutchings, would you be able to do what you did before: give me a patch collection that I can apply one by one, until I can see the driver working? This time I need MORE patches, at least until kernel 2.6.28 (as the driver appeared to work with the backported Debian CD including 2.6.28 kernel). Then I'll do my best to make a much smaller patch than the one that I have attached, and hopefully, have it accepted by you guys. Thanks for your time reading this, and the support of my work here, Thomas -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Applying e1000e patch to the Debian 2.6.26 kernel
dann frazier wrote: oops - sorry, that was the wrong version. updated patches attached. EXCELLENT! That actually seem to work!!! Will that be included in the next Debian kernel release? Thomas -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#519941: Remove Policy permission for packages to modify ld.so.conf
In Policy Bug#519941, it was proposed to remove the Policy permission for packages to modify ld.so.conf in exceptional circumstances. The implication would be that all packages which do this will need to either move their libraries into a standard library directory like /usr/lib if they're really intended to be public or compile with an RPATH setting. Permission for packages to modify the global library search order to include a non-standard directory would be removed. The rationale as stated by Steve Langasek: | This recommendation needs to be elminated entirely. It is *not* ok | for packages that provide libraries to stick extra linker paths in the | global configuration, whether by modifying ld.so.conf or by adding to | /etc/ld.so.conf.d. Either the libraries provided by the packages are | meant to be public, in which case they should be installed to the | standard library path instead of needlessly adding another directory | that's going to be globally visible anyway; or they should not, and | the cooperating packages should use rpath instead. | | Use of rpath should still be discouraged, but if someone is bound and | determined to violate the FHS with their library paths in order to | have private libraries, they should make them really private with | rpath instead of using this compromise solution that takes the worst | of each approach. Note that using a separate directory and modifying ld.so.conf does not usefully resolve name conflicts, since all the libraries end up on the same global search path anyway and one still has to use RPATH to select which of two conflictingly-named libraries one wants to load. This has already recieved the support of six Debian Developers, which is more than enough to make this change in Policy. However, due to the broader effects, I wanted to make sure that people were aware of this discussion and had a chance to review and weigh in. I'm also copying the maintainers of all packages that apt-file says include files in /etc/ld.so.conf.d except for libc6 and friends. I have not individually checked these packages to understand why they include an ld.so.conf.d fragment, and this doesn't include any packages that modify /etc/ld.so.conf. This is the proposed modification to Policy: --- a/policy.sgml +++ b/policy.sgml @@ -7011,17 +7011,6 @@ strip --strip-unneeded varyour-lib/var /p p - Packages containing shared libraries that may be linked to - by other packages' binaries, but which for some - emcompelling/em reason can not be installed in - file/usr/lib/file directory, may install the shared library - files in subdirectories of the file/usr/lib/file directory, - in which case they should arrange to add that directory in - file/etc/ld.so.conf/file in the package's post-installation - script, and remove it in the package's post-removal script. - /p - - p An ever increasing number of packages are using prgnlibtool/prgn to do their linking. The latest GNU libtools (= 1.3a) can take advantage of the metadata in the Please copy 519...@bugs.debian.org on all discussion. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
