Bug#565404: linux-image-2.6.26-2-amd64: atl1e: TSO is broken
JY == Jie Yang jie.y...@atheros.com writes: JY Anders Boström and...@netinsight.net wrote: JY following is my test cese, JY a nfs server server with ar8131chip, device id 1063. export /tmp/ dir as the nfs share directory, JY the client, mount the server_ip:/tmp to local dir /mnt/nfs, ust a python script to write and read data on the JY /mnt/nfs/testnfs.log. it works fine. OK, the device-ID in our NFS-server is 1026, rev. b0. So it is possible that the problem is specific to that chip/version. JY oops, its my mistake in writing, my case is 1026 device ID JY Can you give me some advice on how to reproduce this bug?? The only suggestion I have is to try to find a board with a 1026-chip on it. My test-case is just copy of a 1 Gbyte file from the NFS-server to /dev/null , after making sure that the file isn't cached on the client by reading huge amounts of other data. JY just to check, if the kernel version is 2.6.26-2 ?? I've tested with Debian linux-image-2.6.26-2-amd64 version 2.6.26-19lenny2, Debian linux-image-2.6.30-bpo.2-amd64 version 2.6.30-8~bpo50+2 and kernel.org 2.6.30.10 amd64 with ethtool patch for setting of tso. Same result. / Anders -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: [Pkg-acpi-devel] Bug#566929: acpi: ACPI: I/O resource w83627ehf [0x295-0x296] conflicts with ACPI region HWRE [0x290-0x299]
Processing commands for cont...@bugs.debian.org: reassign 566929 linux-image-2.6.32-trunk-686 Bug #566929 [acpid] acpi: ACPI: I/O resource w83627ehf [0x295-0x296] conflicts with ACPI region HWRE [0x290-0x299] Bug reassigned from package 'acpid' to 'linux-image-2.6.32-trunk-686'. Bug No longer marked as found in versions acpid/1:2.0.0-1. 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#566929: marked as done (acpi: ACPI: I/O resource w83627ehf [0x295-0x296] conflicts with ACPI region HWRE [0x290-0x299])
Your message dated Tue, 26 Jan 2010 10:26:33 +0100 with message-id 20100126092633.ga27...@feivel.credativ.lan and subject line Closing has caused the Debian Bug report #566929, regarding acpi: ACPI: I/O resource w83627ehf [0x295-0x296] conflicts with ACPI region HWRE [0x290-0x299] 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.) -- 566929: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566929 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: acpid Version: 1:2.0.0-1 Severity: important File: acpi w83627ehf: Found W83667HG chip at 0x290 -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU cores) Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages acpid depends on: ii libc6 2.10.2-2 GNU C Library: Shared libraries ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip ii module-init-tools 3.11-1 tools for managing Linux kernel mo Versions of packages acpid recommends: ii acpi-support-base 0.132-1scripts for handling base ACPI eve acpid suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- With the sender's email address not existing there is no way to get badly needed additional information about this bug report, therefore I just close it. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ 179140304, AIM/Yahoo/Skype michaelmeskes, Jabber mes...@jabber.org VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL ---End Message---
Re: Bug#564079: Is this really a screensaver issue?
On Tue, Jan 26, 2010 at 11:21:56AM +0100, Josselin Mouette wrote: Le samedi 23 janvier 2010 à 11:37 +0100, Guido Günther a écrit : Should this really be handled in the screensaver? The user can also kill other processes during boot like accounting daemons and therefore compromise security. The only fix is to disable this feature. I fully concur. Such a “feature” should be disabled by default, and this has to be done in the kernel packages. The OOM killer can always be forced with normal processes as long as over-commitment is enabled. So it is never save to add security measures within processes that can be killed seperately. I’d appreciate if we could have some input from the kernel maintainers. Someone with access to the console have several attack vectors available. Bastian -- Earth -- mother of the most beautiful women in the universe. -- Apollo, Who Mourns for Adonais? stardate 3468.1 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#564079: Is this really a screensaver issue?
Le mardi 26 janvier 2010 à 12:00 +0100, Bastian Blank a écrit : On Tue, Jan 26, 2010 at 11:21:56AM +0100, Josselin Mouette wrote: Le samedi 23 janvier 2010 à 11:37 +0100, Guido Günther a écrit : Should this really be handled in the screensaver? The user can also kill other processes during boot like accounting daemons and therefore compromise security. The only fix is to disable this feature. I fully concur. Such a “feature” should be disabled by default, and this has to be done in the kernel packages. The OOM killer can always be forced with normal processes as long as over-commitment is enabled. So it is never save to add security measures within processes that can be killed seperately. Without the SysRq, it would require at least to be logged on to achieve that. Or do you have examples in mind? Do you also have any ideas of what screensavers should do to be secure wrt. the OOM killer and similar attack vectors? I’d appreciate if we could have some input from the kernel maintainers. Someone with access to the console have several attack vectors available. Indeed but that shouldn’t prevent us from working on mitigating these risks. If your laptop is stolen while not powered down, it should not allow to access your running session. Cheers, -- .''`. Josselin Mouette : :' : `. `' “A handshake with whitnesses is the same `- as a signed contact.” -- Jörg Schilling -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#564079: Is this really a screensaver issue?
Hey, * Bastian Blank wa...@debian.org [2010-01-26 14:44]: On Tue, Jan 26, 2010 at 11:21:56AM +0100, Josselin Mouette wrote: Le samedi 23 janvier 2010 à 11:37 +0100, Guido Günther a écrit : Should this really be handled in the screensaver? The user can also kill other processes during boot like accounting daemons and therefore compromise security. The only fix is to disable this feature. I fully concur. Such a ???feature??? should be disabled by default, and this has to be done in the kernel packages. The OOM killer can always be forced with normal processes as long as over-commitment is enabled. So it is never save to add security measures within processes that can be killed seperately. Of course but this requires either a bug in another application that can be used remotely or access to the system e.g. via an own account. I???d appreciate if we could have some input from the kernel maintainers. Someone with access to the console have several attack vectors available. True, but this one is trivial to exploit and is also fairly easy to prevent so why stick with it? Cheers Nico -- Nico Golde - http://www.ngolde.de - n...@jabber.ccc.de - GPG: 0xA0A0 For security reasons, all text in this mail is double-rot13 encrypted. pgpslxfd4Pocn.pgp Description: PGP signature
Re: Bug#564079: Is this really a screensaver issue?
On Tue, Jan 26, 2010 at 02:15:13PM +0100, Josselin Mouette wrote: Le mardi 26 janvier 2010 à 12:00 +0100, Bastian Blank a écrit : The OOM killer can always be forced with normal processes as long as over-commitment is enabled. So it is never save to add security measures within processes that can be killed seperately. Do you also have any ideas of what screensavers should do to be secure wrt. the OOM killer and similar attack vectors? Move the locking themself into the X server and export the controls as extension. If the control process dies, the screen remains locked and can only be unlocked by a authenticated X connection. Bastian -- Beam me up, Scotty! It ate my phaser! -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 565494
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 565494 + pending Bug #565494 [linux-image-2.6.26-2-amd64] linux-image-2.6.26-2-amd64: does not include CONFIG_INFINIBAND_IPOIB_CM infiniband connected mode Added tag(s) 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 525232
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 525232 + pending Bug #525232 [linux-image-2.6.26-2-amd64] Please enable CONFIG_ITCO_VENDOR_SUPPORT Added tag(s) 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 565494
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 565494 + pending Bug #565494 [linux-image-2.6.26-2-amd64] linux-image-2.6.26-2-amd64: does not include CONFIG_INFINIBAND_IPOIB_CM infiniband connected mode Ignoring request to alter tags of bug #565494 to the same tags previously set 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 478315
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 478315 + pending Bug #478315 [linux-2.6] please enable CONFIG_PM_TRACE for easier debugging of suspend to ram Added tag(s) 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 525232
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 525232 + pending Bug #525232 [linux-image-2.6.26-2-amd64] Please enable CONFIG_ITCO_VENDOR_SUPPORT Ignoring request to alter tags of bug #525232 to the same tags previously set 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#547640: marked as done (linux-image-2.6.30: Please consider deactivating NEW_FAIR_SLEEPERS in kernel/sched_features.h)
Your message dated Tue, 26 Jan 2010 17:54:21 +0100
with message-id 20100126165420.gd18...@stro.at
and subject line Re: linux-image-2.6.30: Please consider deactivating
NEW_FAIR_SLEEPERS in kernel/sched_features.h
has caused the Debian Bug report #547640,
regarding linux-image-2.6.30: Please consider deactivating NEW_FAIR_SLEEPERS in
kernel/sched_features.h
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.)
--
547640: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6.30-1-amd64
Version: 2.6.30-6
Severity: wishlist
File: linux-image-2.6.30
As described in
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=3f2aa307c4d26b4ed6509d0a79e8254c9e07e921
the scheduler improves interactivity. I would like to see this in
Debian's kernel packages 2.6.{26,30} because it deletes the effort to
compile an individual kernel for me and other people.
Thanks,
Ferdinand Ebert
-- Package-specific info:
** Version:
Linux version 2.6.30-1-amd64 (Debian 2.6.30-6) (wa...@debian.org) (gcc version
4.3.4 (Debian 4.3.4-1) ) #1 SMP Sat Aug 15 18:09:19 UTC 2009
** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.30-1-amd64 root=/dev/mapper/vonNeumann-root ro
selinux=0 enforcing=0 quiet
** Not tainted
** Kernel log:
[8.085608] w83627ehf: Found W83627DHG chip at 0x290
[8.099251] coretemp coretemp.0: Using relative temperature scale!
[8.099302] coretemp coretemp.1: Using relative temperature scale!
[9.060238] EXT4-fs: barriers enabled
[9.060425] kjournald2 starting: pid 2316, dev dm-4:8, commit interval 5
seconds
[9.060726] EXT4 FS on dm-4, internal journal on dm-4:8
[9.060729] EXT4-fs: delayed allocation enabled
[9.060731] EXT4-fs: file extents enabled
[9.060912] EXT4-fs: mballoc enabled
[9.060927] EXT4-fs: mounted filesystem dm-4 with ordered data mode
[9.110744] EXT4-fs: barriers enabled
[9.114881] kjournald2 starting: pid 2317, dev dm-3:8, commit interval 5
seconds
[9.115111] EXT4 FS on dm-3, internal journal on dm-3:8
[9.115113] EXT4-fs: delayed allocation enabled
[9.115116] EXT4-fs: file extents enabled
[9.115238] EXT4-fs: mballoc enabled
[9.115250] EXT4-fs: mounted filesystem dm-3 with ordered data mode
[9.135986] EXT4-fs: barriers enabled
[9.136164] kjournald2 starting: pid 2318, dev dm-1:8, commit interval 5
seconds
[9.136436] EXT4 FS on dm-1, internal journal on dm-1:8
[9.136438] EXT4-fs: delayed allocation enabled
[9.136440] EXT4-fs: file extents enabled
[9.136561] EXT4-fs: mballoc enabled
[9.136573] EXT4-fs: mounted filesystem dm-1 with ordered data mode
[9.153307] EXT4-fs: barriers enabled
[9.153479] kjournald2 starting: pid 2319, dev dm-2:8, commit interval 5
seconds
[9.153758] EXT4 FS on dm-2, internal journal on dm-2:8
[9.153760] EXT4-fs: delayed allocation enabled
[9.153762] EXT4-fs: file extents enabled
[9.153873] EXT4-fs: mballoc enabled
[9.153885] EXT4-fs: mounted filesystem dm-2 with ordered data mode
[9.181201] EXT4-fs: barriers enabled
[9.196535] kjournald2 starting: pid 2320, dev sdb1:8, commit interval 5
seconds
[9.196818] EXT4 FS on sdb1, internal journal on sdb1:8
[9.196820] EXT4-fs: delayed allocation enabled
[9.196822] EXT4-fs: file extents enabled
[9.197862] EXT4-fs: mballoc enabled
[9.197876] EXT4-fs: mounted filesystem sdb1 with ordered data mode
[9.231630] EXT4-fs: barriers enabled
[9.240802] kjournald2 starting: pid 2321, dev sdc3:8, commit interval 5
seconds
[9.241119] EXT4 FS on sdc3, internal journal on sdc3:8
[9.241121] EXT4-fs: delayed allocation enabled
[9.241123] EXT4-fs: file extents enabled
[9.242101] EXT4-fs: mballoc enabled
[9.242115] EXT4-fs: mounted filesystem sdc3 with ordered data mode
[9.274448] EXT4-fs: barriers enabled
[9.291735] kjournald2 starting: pid 2322, dev sda1:8, commit interval 5
seconds
[9.292037] EXT4 FS on sda1, internal journal on sda1:8
[9.292039] EXT4-fs: delayed allocation enabled
[9.292041] EXT4-fs: file extents enabled
[9.293119] EXT4-fs: mballoc enabled
[9.293131] EXT4-fs: mounted filesystem sda1 with ordered data mode
[9.491164] Adding 1535992k swap on /dev/mapper/vonNeumann-swap.
Priority:-1 extents:1 across:1535992k
[ 11.525394] Bridge firewalling registered
[ 11.529014] device eth0 entered promiscuous mode
[ 11.536928] r8169: eth0: link up
[ 11.536935] r8169: eth0: link up
[ 11.539321] br0: port 1(eth0) entering
Re: Bug#564079: Is this really a screensaver issue?
On Tue, Jan 26, 2010 at 05:31:23PM +0100, Josselin Mouette wrote: Le mardi 26 janvier 2010 à 16:19 +0100, Guido Günther a écrit : I can only agree here. procps should at least get a: sys.kernel.sysrq = 0 It’s only a workaround, and it’s a bit too much to disable all SysRq since other SysRq combinations are not a security threat. I would accept a default mask that disables SIGNAL and DUMP sysrq requests. The SIGNAL labeled allows to kill processes in various ways, the DUMP labeled ones allows display of various process and systems states that may provide access to private userspace data. Affected sysrq requests: * SIGNAL: Terminate All Tasks, Manual OOM execution, Emergency Thaw of all frozen filesystems, Kill All Tasks * DUMP: Trigger a crash, Show backtrace of all active CPUs, Show Regs, Show State, Show Blocked State, Dump ftrace buffer, Show Memory However we could ship this in the gnome-screensaver/xscreensaver packages if there is no other solution. Please don't try this, this is a decision of the kernel have to make. Bastian -- Vulcans never bluff. -- Spock, The Doomsday Machine, stardate 4202.1 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 565494
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 565494 + pending Bug #565494 [linux-image-2.6.26-2-amd64] linux-image-2.6.26-2-amd64: does not include CONFIG_INFINIBAND_IPOIB_CM infiniband connected mode Ignoring request to alter tags of bug #565494 to the same tags previously set 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 545417
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 545417 + pending Bug #545417 [linux-2.6] linux-image-2.6.30-1-amd64: please enable CONFIG_PCIEASPM Added tag(s) 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
Re: Bug#564079: Is this really a screensaver issue?
On Tue, Jan 26, 2010 at 17:31:23 +0100, Josselin Mouette wrote: Le mardi 26 janvier 2010 à 16:19 +0100, Guido Günther a écrit : True, but this one is trivial to exploit and is also fairly easy to prevent so why stick with it? I can only agree here. procps should at least get a: sys.kernel.sysrq = 0 It’s only a workaround, and it’s a bit too much to disable all SysRq since other SysRq combinations are not a security threat. However we could ship this in the gnome-screensaver/xscreensaver packages if there is no other solution. This would make the obvious and immediate security issue go away. Not really, because everyone will re-enable it anyway. Disabling sysrq system-wise to avoid the X screensaver being killed is too big a hammer, IMO. Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
popping laptop speakers
Hi there, I've got an annoying problem with my laptop which is a Pavilion dv5. I have the latest kernel 2.6.32. The problem is that at reboot the speakers make a loud noise which I fear may damage hardware. This problem existed with somewhat older kernels and it was worse. There used to be sounds generated also at suspend. I don't know whether this should be reported as a bug and if so where it should go. I thought here is the most relevant place so I posted to this list. I have attached the output of lspci and lsmod to this email but I don't know how to get you more data (such as probably logs). I know this is not enough. So please help me. These threads show that already so many people are having such a problem: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/23984 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/352540/+activity lspci: 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03) 00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.3 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03) 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03) 00:1f.6 Signal processing controller: Intel Corporation 82801I (ICH9 Family) Thermal Subsystem (rev 03) 01:00.0 VGA compatible controller: nVidia Corporation G98 [GeForce 9200M GS] (rev a1) 02:00.0 Network controller: Intel Corporation PRO/Wireless 5100 AGN [Shiloh] Network Connection 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) 06:00.0 FireWire (IEEE 1394): JMicron Technology Corp. IEEE 1394 Host Controller 06:00.1 System peripheral: JMicron Technology Corp. SD/MMC Host Controller 06:00.2 SD Host controller: JMicron Technology Corp. Standard SD Host Controller 06:00.3 System peripheral: JMicron Technology Corp. MS Host Controller 06:00.4 System peripheral: JMicron Technology Corp. xD Host Controller lsmod: Module Size Used by nvidia 8783671 41 ppdev 4058 0 lp 5570 0 parport22554 2 ppdev,lp sco 5837 2 bridge 32851 0 stp 996 1 bridge bnep7376 2 rfcomm 25063 4 l2cap 21677 16 bnep,rfcomm crc16 1027 1 l2cap acpi_cpufreq4907 0 cpufreq_userspace 1444 0 cpufreq_conservative 4018 0 cpufreq_powersave602 0 cpufreq_stats 1940 0 kvm_intel 32446 0 kvm 179533 1 kvm_intel fuse 43554 1 loop9721 0 firewire_sbp2 9575 0 snd_hda_codec_nvhdmi 2567 1 snd_hda_codec_idt 35245 1 snd_hda_intel 15263 2 snd_hda_codec 45998 3 snd_hda_codec_nvhdmi,snd_hda_codec_idt,snd_hda_intel snd_hwdep 4054 1 snd_hda_codec snd_pcm_oss28479 0 snd_mixer_oss 10461 1 snd_pcm_oss snd_pcm
Processed: tagging 510593
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 510593 + pending Bug #510593 [linux-image-2.6.26-1-amd64] Support more than 8 sound cards Added tag(s) 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
Re: Bug#564079: Is this really a screensaver issue?
On 2010-01-26 17:31, Josselin Mouette wrote: Le mardi 26 janvier 2010 à 16:19 +0100, Guido Günther a écrit : True, but this one is trivial to exploit and is also fairly easy to prevent so why stick with it? I can only agree here. procps should at least get a: sys.kernel.sysrq = 0 It’s only a workaround, and it’s a bit too much to disable all SysRq since other SysRq combinations are not a security threat. However we could ship this in the gnome-screensaver/xscreensaver packages if there is no other solution. This would make the obvious and immediate security issue go away. Simultaneously, we can forward the issue upstream so that they can work on an appropriate X11 extension as suggested by Bastian. Another solution could be to let the screensaver set /proc/self/oom_adj to -17 to disable the possibility of this process beeing killed by the oom-killer. (linux/Documentation/filesystems/proc.txt) Safest would be to make the kernel default to off though (the user can still reenable this via procps) since there's otherwise still a race until /etc/init.d/procps starts. I don’t think this race condition is relevant. The only thing that can protect you from someone who has access to the console at boot time is to encrypt your data. The screensaver’s lock is here to prevent the data from being accessed without a reboot. Cheers, -- .''`. Josselin Mouette : :' : `. `' “A handshake with whitnesses is the same `- as a signed contact.” -- Jörg Schilling Lars Olav Dybsjord lar...@ping.uio.no -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#564079: Is this really a screensaver issue?
Hi, On Dienstag, 26. Januar 2010, Julien Cristau wrote: Not really, because everyone will re-enable it anyway. I think your definition of everyone is flawed. I assume at least 98% of the users not knowing about sysrq and I'd expect the same percentage to think that it's not possible to kill the screensaver short of rebooting the machine. (Assuming one has local access. cheers, Holger signature.asc Description: This is a digitally signed message part.
Processed: tagging 563161
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 563161 + pending Bug #563161 [linux-2.6] Provide way to distinguish remove and purge in postrm hooks Added tag(s) 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 528834
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 528834 + pending Bug #528834 [linux-2.6] linux-2.6: Mobile IPv6 needs Added tag(s) 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
Re: Bug#543717: Initramfs firmware loading fail due to udev being started too late
it has to be started earlier, that is clear. I haven't had the time to find out how early, aka at which state exactly. init-top so it it will be run early enough that it is present for /etc/initramfs-tools/modules and no one will need to do mknoding. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#543717: Initramfs firmware loading fail due to udev being started too late
On Tue, 26 Jan 2010, maximilian attems wrote: it has to be started earlier, that is clear. I haven't had the time to find out how early, aka at which state exactly. init-top so it it will be run early enough that it is present for /etc/initramfs-tools/modules and no one will need to do mknoding. hmm there is one subtle wish here, please add a pre-requisite on all_generic_ide so that it gets a chance to load bloody IDE device. of course alternatively the udev init-top script could parse that boot param on its own? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#551312: Unitech barcode fix from linux-next git
On Mon, Jan 25, 2010 at 05:06:36PM -0500, Anthony DeRobertis wrote: Package: linux-2.6 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Linux-next commit 4bb950806f10bc3e249dd34375b4a4d6bfc0 contains a fix for this bug. I'd really appreciate it if you'd cherry-pick this for 2.6.32 (which I understand squeeze is going to release with). The diff is dead simple: it just removes the blacklist lines. http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commit;h=4bb950806f10bc3e249dd34375b4a4d6bfc0 [Adding sta...@kernel.org] Greg, above commit seems like a candidate for 2.6.32.x Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#551312: [stable] [PATCH] HID: remove TENX iBuddy from blacklist
On Tue, Jan 26, 2010 at 12:37:57AM +, Ben Hutchings wrote:
This was commit 4bb950806f10bc3e249dd34375b4a4d6bfc0 upstream.
I don't see that commit id, or the patch below, in Linus's tree yet.
Did something get out of sync?
confused,
greg k-h
From 4bb950806f10bc3e249dd34375b4a4d6bfc0 Mon Sep 17 00:00:00 2001
From: Jiri Kosina jkos...@suse.cz
Date: Wed, 23 Dec 2009 14:13:46 +0100
Subject: [PATCH] HID: remove TENX iBuddy from blacklist
There were multiple reports which indicate that vendor messed up horribly
and the same VID/PID combination is used for completely different devices,
some of them requiring the blacklist entry and other not.
Remove the blacklist entry for this combination of VID/PID completely, and let
the user decide and unbind the driver via sysfs eventually, if needed. Proper
fix would be fixing the vendor.
References:
http://lkml.org/lkml/2009/2/10/434
http://bugzilla.kernel.org/show_bug.cgi?id=13411
Signed-off-by: Jiri Kosina jkos...@suse.cz
---
drivers/hid/hid-core.c |2 --
drivers/hid/hid-ids.h |4
2 files changed, 0 insertions(+), 6 deletions(-)
diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
index 056384c..116a346 100644
--- a/drivers/hid/hid-core.c
+++ b/drivers/hid/hid-core.c
@@ -1662,8 +1662,6 @@ static const struct hid_device_id hid_ignore_list[] = {
{ HID_USB_DEVICE(USB_VENDOR_ID_PANJIT, 0x0004) },
{ HID_USB_DEVICE(USB_VENDOR_ID_PHILIPS,
USB_DEVICE_ID_PHILIPS_IEEE802154_DONGLE) },
{ HID_USB_DEVICE(USB_VENDOR_ID_POWERCOM, USB_DEVICE_ID_POWERCOM_UPS) },
- { HID_USB_DEVICE(USB_VENDOR_ID_TENX, USB_DEVICE_ID_TENX_IBUDDY1) },
- { HID_USB_DEVICE(USB_VENDOR_ID_TENX, USB_DEVICE_ID_TENX_IBUDDY2) },
{ HID_USB_DEVICE(USB_VENDOR_ID_VERNIER, USB_DEVICE_ID_VERNIER_LABPRO) },
{ HID_USB_DEVICE(USB_VENDOR_ID_VERNIER, USB_DEVICE_ID_VERNIER_GOTEMP) },
{ HID_USB_DEVICE(USB_VENDOR_ID_VERNIER, USB_DEVICE_ID_VERNIER_SKIP) },
diff --git a/drivers/hid/hid-ids.h b/drivers/hid/hid-ids.h
index b009fd6..064c09a 100644
--- a/drivers/hid/hid-ids.h
+++ b/drivers/hid/hid-ids.h
@@ -406,10 +406,6 @@
#define USB_VENDOR_ID_SUNPLUS0x04fc
#define USB_DEVICE_ID_SUNPLUS_WDESKTOP 0x05d8
-#define USB_VENDOR_ID_TENX 0x1130
-#define USB_DEVICE_ID_TENX_IBUDDY1 0x0001
-#define USB_DEVICE_ID_TENX_IBUDDY2 0x0002
-
#define USB_VENDOR_ID_THRUSTMASTER 0x044f
#define USB_VENDOR_ID_TOPMAX 0x0663
--
1.6.6
___
stable mailing list
sta...@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/stable
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#566543: Info received (Bug#566543: Acknowledgement (ath5k: regression: unable to connect to AP on channel 13))
I reported this to the linux-wireless list, thread available here: http://news.gmane.org/find-root.php?message_id=%3c4B5CB7AB.7010105%40bzz.no%3e One of the replies suggested installing CRDA (RFP #536502), which fixed the problem. According to Luis R. Rodriguez: No, Atheros cards by default abide by a custom strict world regulatory domain if CRDA is not present. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#551312: [stable] Unitech barcode fix from linux-next git
On Tue, Jan 26, 2010 at 07:23:38PM +0100, Moritz Muehlenhoff wrote: On Mon, Jan 25, 2010 at 05:06:36PM -0500, Anthony DeRobertis wrote: Package: linux-2.6 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Linux-next commit 4bb950806f10bc3e249dd34375b4a4d6bfc0 contains a fix for this bug. I'd really appreciate it if you'd cherry-pick this for 2.6.32 (which I understand squeeze is going to release with). The diff is dead simple: it just removes the blacklist lines. http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commit;h=4bb950806f10bc3e249dd34375b4a4d6bfc0 [Adding sta...@kernel.org] Greg, above commit seems like a candidate for 2.6.32.x Great, how about letting me know when it hits Linus's tree, and what the git commit id is then, so that I can apply it to the .32.x queue. I can't take patches unless they are in Linus's tree. thanks, greg k-h -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#563882: git-core FTBFS on ia64: t1001-read-tree-m-2way.sh test fails
reassign 563882 libc6.1 2.10.2-5
severity 563882 critical
retitle 563882 ia64: mmap reading null bytes that should not be there
thanks
Hi libc maintainers,
mmap() on ia64 seems to be totally broken. git does something
like the following to detect binary files:
struct stat st;
lstat(path, st);
int fd = open(path, O_RDONLY);
void *data = mmap(NULL, st.st_size, PROT_READ, MAP_PRIVATE, fd, 0);
close(fd);
binary = !!memchr(data, 0, st.st_size);
munmap(data, st.st_size);
That is, it maps the file into memory and looks for null bytes.
Unfortunately, the test suite when run on merulo and mundy revealed
that this was detecting various text files as binary. When mmapping
two files in sequence, only the first seems to have this problem.
Test case attached. Usage: compile with
gcc -Wall -W -O -o generic-is-binary generic-is-binary.c
Take your favorite text file M.out (see
http://bugs.debian.org/563882 and search for -- % -- M.out for
the example Andreas used to reproduce this) and run
M.out ./generic-is-binary M.out
Then this program would lie to you and say “M.out is binary”
| ametz...@merulo:/tmp$ uname -r
| 2.6.32.2-dsa-ia64-mckinley
| ametz...@merulo:/tmp$ dpkg -l libc6
[...]
| in libc6 none (no description available)
| ametz...@merulo:/tmp$ dpkg -l libc6.1
[...]
| ii libc6.12.10.2-5 Embedded GNU C Library: Shared libraries
| ametz...@merulo:/tmp$ gcc -Wall -W -O -o generic-is-binary generic-is-binary.c
| ametz...@merulo:/tmp$ popd
| /tmp/GIT/git-core-1.6.6-debug/t/trash directory.t1001-read-tree-m-2way
| ametz...@merulo:/tmp/GIT/git-core-1.6.6-debug/t/trash
directory.t1001-read-tree-m-2way$ M.out /tmp/generic-is-binary M.out
| stdin is not binary
| M.out is binary
See http://bugs.debian.org/563882 for the full story.
This regression came in October of last year on caballero. [1] Any ideas?
Andreas Metzler wrote:
okay:
ametz...@merulo:/tmp/GIT/git-core-1.6.6-debug/t/trash
directory.t1001-read-tree-m-2way$ 4.out
/tmp/GIT/git-core-1.6.6-debug/git-is-binary 4.out M.out
static buffer is not binary
stdin is not binary
4.out is binary
M.out is not binary
ametz...@merulo:/tmp/GIT/git-core-1.6.6-debug/t/trash
directory.t1001-read-tree-m-2way$ cp M.out M2.out
ametz...@merulo:/tmp/GIT/git-core-1.6.6-debug/t/trash
directory.t1001-read-tree-m-2way$ 4.out
/tmp/GIT/git-core-1.6.6-debug/git-is-binary M.out M2.out
static buffer is not binary
stdin is not binary
M.out is binary
M2.out is not binary
ametz...@merulo:/tmp/GIT/git-core-1.6.6-debug/t/trash
directory.t1001-read-tree-m-2way$ M2.out
/tmp/GIT/git-core-1.6.6-debug/git-is-binary M.out M2.out
static buffer is not binary
stdin is not binary
M.out is binary
M2.out is not binary
Ugh, so it’s always the first mmap...
If M.out (but not stdin) is reported to be binary, great: git is
exonerated, and we have an independent test case.
You win. ;-)
Thank you!
Reassigning to libc. I will leave the rest of the debugging to someone
more knowledgeable about ia64/libc/linux-2.6. ;-)
Thank you for your help tracking this down. You’ve had the patience
of a saint.
Regards,
Jonathan
[1] https://buildd.debian.org/build.php?pkg=git-corearch=ia64
#include stdlib.h
#include string.h
#include stdarg.h
#include stdio.h
#include errno.h
#include sys/types.h
#include sys/stat.h
#include sys/mman.h
#include unistd.h
#include fcntl.h
static int xprintf(const char *fmt, ...);
static int buffer_is_binary(const char *ptr, size_t size);
static int check_stdin(void);
static int check_file(const char *path);
int main(int argc, const char * const argv[])
{
int result = 0;
if (argc != 2) {
fprintf(stderr, usage: generic-is-binary path path\n);
exit(1);
}
result |= check_stdin();
result |= check_file(argv[1]);
return result;
}
static int buffer_is_binary(const char *ptr, size_t sz)
{
return !!memchr(ptr, 0, sz);
}
static int check_stdin(void)
{
static char in_buf[8000];
char *bufp = in_buf;
char *buf_end = in_buf + sizeof(in_buf);
ssize_t n;
while ((n = read(0, bufp, buf_end - bufp))) {
if (n 0) {
perror(stdin: read);
return -1;
}
bufp += n;
}
return xprintf(stdin is%s binary\n,
buffer_is_binary(in_buf, bufp - in_buf) ?
: not);
}
static ssize_t size(const char *path)
{
struct stat st;
if (lstat(path, st) 0) {
fprintf(stderr, %s: lstat: %s\n,
path, strerror(errno));
return -1;
}
return st.st_size;
}
static int check_file(const char *path)
{
ssize_t sz;
int fd, result;
void *data;
if ((sz = size(path)) 0)
return -1;
if ((fd = open(path, O_RDONLY)) 0) {
fprintf(stderr, %s: open: %s\n,
path, strerror(errno));
return -1;
}
data = mmap(NULL, sz, PROT_READ, MAP_PRIVATE, fd, 0);
if (data == MAP_FAILED) {
fprintf(stderr, %s: mmap: %s\n,
path, strerror(errno));
close(fd);
return -1;
}
if (close(fd)) {
fprintf(stderr, %s: close: %s\n,
path, strerror(errno));
Bug#551312: [stable] [PATCH] HID: remove TENX iBuddy from blacklist
On Tue, Jan 26, 2010 at 08:22:31PM +0100, Uwe Kleine-König wrote: On Tue, Jan 26, 2010 at 10:06:56AM -0800, Greg KH wrote: On Tue, Jan 26, 2010 at 12:37:57AM +, Ben Hutchings wrote: This was commit 4bb950806f10bc3e249dd34375b4a4d6bfc0 upstream. I don't see that commit id, or the patch below, in Linus's tree yet. It's in next and comes from git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git for-next Then I can't take it, sorry. Please let me know when it hits Linus's tree and what the git commit id is for it then. thanks, greg k-h -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#551312: [stable] [PATCH] HID: remove TENX iBuddy from blacklist
On Tue, Jan 26, 2010 at 10:06:56AM -0800, Greg KH wrote: On Tue, Jan 26, 2010 at 12:37:57AM +, Ben Hutchings wrote: This was commit 4bb950806f10bc3e249dd34375b4a4d6bfc0 upstream. I don't see that commit id, or the patch below, in Linus's tree yet. It's in next and comes from git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git for-next Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König| Industrial Linux Solutions| http://www.pengutronix.de/ | -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#567034: [xserver-xorg-video-intel] when using KMS, X puts the monitor directly into power saving mode upon startup[945G]
Processing commands for cont...@bugs.debian.org: reassign 567034 linux-2.6 Bug #567034 [xserver-xorg-video-intel] [xserver-xorg-video-intel] when using KMS, X puts the monitor directly into power saving mode upon startup[945G] Bug reassigned from package 'xserver-xorg-video-intel' to 'linux-2.6'. Bug No longer marked as found in versions xserver-xorg-video-intel/2:2.9.1-2. thank you 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#563882: git-core FTBFS on ia64: t1001-read-tree-m-2way.sh test fails
severity 563882 important
retitle 563882 ia64: memchr overshots
thanks
On Tue, Jan 26, 2010 at 01:48:34PM -0600, Jonathan Nieder wrote:
severity 563882 critical
Please explain. git is neither unrelated to glibc nor does this cause
serious data loss.
That is, it maps the file into memory and looks for null bytes.
No, the kernel always maps complete pages, so this maps several null
bytes.
Then this program would lie to you and say “M.out is binary”
The test program does not properly show what is going on.
The following program shows the cause:
| #include sys/stat.h
| #include sys/mman.h
| #include fcntl.h
|
| int main(int argc, const char * const argv[])
| {
| struct stat st;
| lstat(argv[1], st);
|
| int fd = open(argv[1], O_RDONLY);
| void *data = mmap(NULL, st.st_size, PROT_READ, MAP_PRIVATE, fd, 0);
| void *t = memchr(data, 0, st.st_size);
| printf(ptr: %p, ret: %p, len: 0x%zx\n, data, t, st.st_size);
| return 0;
| }
Example output:
| % ./test /etc/passwd
| ptr: 0x2005, ret: 0x2005040e, len: 0x40e
The found location is already after the buffer. memchr is AFAIK expanded
by gcc.
Bastian
--
Where there's no emotion, there's no motive for violence.
-- Spock, Dagger of the Mind, stardate 2715.1
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#563882: git-core FTBFS on ia64: t1001-read-tree-m-2way.sh test fails
Bastian Blank wrote:
On Tue, Jan 26, 2010 at 01:48:34PM -0600, Jonathan Nieder wrote:
severity 563882 critical
Please explain. git is neither unrelated to glibc nor does this cause
serious data loss.
My mistake, sorry about that.
The test program does not properly show what is going on.
The following program shows the cause:
| #include sys/stat.h
| #include sys/mman.h
| #include fcntl.h
|
| int main(int argc, const char * const argv[])
| {
| struct stat st;
| lstat(argv[1], st);
|
| int fd = open(argv[1], O_RDONLY);
| void *data = mmap(NULL, st.st_size, PROT_READ, MAP_PRIVATE, fd, 0);
| void *t = memchr(data, 0, st.st_size);
| printf(ptr: %p, ret: %p, len: 0x%zx\n, data, t, st.st_size);
| return 0;
| }
Example output:
| % ./test /etc/passwd
| ptr: 0x2005, ret: 0x2005040e, len: 0x40e
The found location is already after the buffer. memchr is AFAIK expanded
by gcc.
Thanks for the clear test case.
Given gcc -S output, I would gladly look it over.
Regards,
Jonathan
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#566543: Info received (Bug#566543: Acknowledgement (ath5k: regression: unable to connect to AP on channel 13))
Hello, On Tue, Jan 26, 2010 at 08:13:33PM +0100, John S. Skogtvedt wrote: I reported this to the linux-wireless list, thread available here: http://news.gmane.org/find-root.php?message_id=%3c4B5CB7AB.7010105%40bzz.no%3e One of the replies suggested installing CRDA (RFP #536502), which fixed the problem. According to Luis R. Rodriguez: No, Atheros cards by default abide by a custom strict world regulatory domain if CRDA is not present. Hmmm, I wonder if this is means that ath5k implements policy by being more strict than the ieee80211_regdom module?! Anyhow, IIRC CRDA isn't packaged as it doesn't easily allow modifications and so it's unclear if it conforms to the DFSG. Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König| Industrial Linux Solutions| http://www.pengutronix.de/ | -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: #496903 also found in 2.6.26-19lenny2
Processing commands for cont...@bugs.debian.org: found 496903 2.6.26-19lenny2 Bug #496903 [linux-image-2.6.26-1-686] linux-image-2.6.26-1-686: crashes when 6710b lid closed There is no source info for the package 'linux-image-2.6.26-1-686' at version '2.6.26-19lenny2' with architecture '' Unable to make a source version for version '2.6.26-19lenny2' Bug Marked as found in versions 2.6.26-19lenny2. 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#563882: git-core FTBFS on ia64: t1001-read-tree-m-2way.sh test fails
Bastian Blank wrote:
The following program shows the cause:
| #include sys/stat.h
| #include sys/mman.h
| #include fcntl.h
|
| int main(int argc, const char * const argv[])
| {
| struct stat st;
| lstat(argv[1], st);
|
| int fd = open(argv[1], O_RDONLY);
| void *data = mmap(NULL, st.st_size, PROT_READ, MAP_PRIVATE, fd, 0);
| void *t = memchr(data, 0, st.st_size);
| printf(ptr: %p, ret: %p, len: 0x%zx\n, data, t, st.st_size);
| return 0;
| }
Example output:
| % ./test /etc/passwd
| ptr: 0x2005, ret: 0x2005040e, len: 0x40e
The found location is already after the buffer. memchr is AFAIK expanded
by gcc.
FYI: http://sourceware.org/bugzilla/show_bug.cgi?id=10162
Maybe glibc 2.11.1 (which includes a cherry-pick of commit 6622141)
will fix this.
I checked gcc’s memchr builtin; there is no ia64-specific version,
and the generic code just deals with constants and delegates the
real work to libc memchr.
Jonathan
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#524003: FTBFS on armel
Processing commands for cont...@bugs.debian.org: reassign 524003 linux-2.6 2.6.32-5 Bug #524003 [tokyocabinet] FTBFS on armel Bug reassigned from package 'tokyocabinet' to 'linux-2.6'. Bug No longer marked as found in versions 1.4.14-2. Bug #524003 [linux-2.6] FTBFS on armel There is no source info for the package 'linux-2.6' at version '2.6.32-5' with architecture '' Unable to make a source version for version '2.6.32-5' Bug Marked as found in versions 2.6.32-5. tags 524003 - help Bug #524003 [linux-2.6] FTBFS on armel Removed tag(s) help. 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: add tokyocabinet to bug title
Processing commands for cont...@bugs.debian.org: retitle 524003 tokyocabinet FTBFS on armel and hppa Bug #524003 [linux-2.6] FTBFS on armel Changed Bug title to 'tokyocabinet FTBFS on armel and hppa' from 'FTBFS on armel' 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#524003: FTBFS on armel
reassign 524003 linux-2.6 2.6.32-5 tags 524003 - help thanks. * Pierre Habouzit | 2009-04-15 01:40:32 [+0200]: Hi Mikio, I'm the Debian maintainer of tokyocabinet, I wanted to report to you that tokyocabinet seems to have issues on armel (and also hppa). You can see the full build logs here: https://buildd.debian.org/fetch.cgi?pkg=tokyocabinetarch=armelver=1.4.14-2stamp=1239676884file=logas=raw https://buildd.debian.org/fetch.cgi?pkg=tokyocabinetarch=hppaver=1.4.14-2stamp=1239662413file=logas=raw I've been looking at the ARM part and I can reproduce this here on my machine. The error message or that part where the test case stopped depends very much on the seed. With seed=0 or 1 (don't remember really) I got an infinite loop. So it looked to me for a while that the test code is buggy. Also comparing the seed with amd64 the armel seed is much higher. However nothing of this true :) I looks now that this a kernel bug. The patch at [0] which I attached seems to fix the issue and I was able to build the package on my arm box after applying the patch. I would be happy if someone could re-test this on ARM and on HPPA. I reassing to package to the kernel team since I thing the user space is fine. I don't patch tag since the two dcache flushes don't look right and upstream did not apply it yet. We will see. Date: Thu, 21 Jan 2010 13:07:57 +0800 Message-ID: 979dd0561001202107v4ddc1eb7xa59a7c16c452f...@mail.gmail.com Subject: [PATCH] Flush dcache before writing into page to avoid alias From: anfei zhou anfei.z...@gmail.com To: linux...@kvack.org, linux-ker...@vger.kernel.org Cc: Andrew Morton a...@linux-foundation.org, KOSAKI Motohiro kosaki.motoh...@jp.fujitsu.com, li...@arm.linux.org.uk, Jamie Lokier ja...@shareable.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-ow...@vger.kernel.org Precedence: bulk List-ID: linux-kernel.vger.kernel.org The cache alias problem will happen if the changes of user shared mapping is not flushed before copying, then user and kernel mapping may be mapped into two different cache line, it is impossible to guarantee the coherence after iov_iter_copy_from_user_atomic. So the right steps should be: flush_dcache_page(page); kmap_atomic(page); write to page; kunmap_atomic(page); flush_dcache_page(page); More precisely, we might create two new APIs flush_dcache_user_page and flush_dcache_kern_page to replace the two flush_dcache_page accordingly. Here is a snippet tested on omap2430 with VIPT cache, and I think it is not ARM-specific: int val = 0x; fd = open(abc, O_RDWR); addr = mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_SHARED, fd, 0); *(addr+0) = 0x; tmp = *(addr+0); *(addr+1) = 0x; write(fd, val, sizeof(int)); close(fd); The results are not always 0x 0x at the beginning as expected. Signed-off-by: Anfei anfei.z...@gmail.com --- fs/fuse/file.c |3 +++ mm/filemap.c |3 +++ 2 files changed, 6 insertions(+), 0 deletions(-) diff --git a/fs/fuse/file.c b/fs/fuse/file.c index c18913a..a9f5e13 100644 --- a/fs/fuse/file.c +++ b/fs/fuse/file.c @@ -828,6 +828,9 @@ static ssize_t fuse_fill_write_pages(struct fuse_req *req, if (!page) break; + if (mapping_writably_mapped(mapping)) + flush_dcache_page(page); + pagefault_disable(); tmp = iov_iter_copy_from_user_atomic(page, ii, offset, bytes); pagefault_enable(); diff --git a/mm/filemap.c b/mm/filemap.c index 96ac6b0..07056fb 100644 --- a/mm/filemap.c +++ b/mm/filemap.c @@ -2196,6 +2196,9 @@ again: if (unlikely(status)) break; + if (mapping_writably_mapped(mapping)) + flush_dcache_page(page); + pagefault_disable(); copied = iov_iter_copy_from_user_atomic(page, i, offset, bytes); pagefault_enable(); -- 1.6.3.1 [0] http://lkml.org/lkml/2010/1/21/3 Sebastian -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#563852: marked as done (thinkpad_acpi: LED restriction does not add safety, please enable CONFIG_THINKPAD_ACPI_UNSAFE_LEDS)
Your message dated Tue, 26 Jan 2010 23:51:53 +0100 with message-id 20100126225152.ga4...@galadriel.inutil.org and subject line Re: thinkpad_acpi: LED restriction does not add safety, please enable CONFIG_THINKPAD_ACPI_UNSAFE_LEDS has caused the Debian Bug report #563852, regarding thinkpad_acpi: LED restriction does not add safety, please enable CONFIG_THINKPAD_ACPI_UNSAFE_LEDS 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.) -- 563852: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563852 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Severity: normal The kernel guys decided it would be a good idea to cripple thinkpad_acpi by not allowing the state of some hardware LEDs to be set, like the dock and battery. They say that allowing these LEDs to be set can make users perform actions dangerous to the hardware because firmware information might get lost. I think that this change does not add safety at all, because the unaware user which they reference in the docs doesn't play around with the LEDs anyway. The LED devices are root writable only anyway, so evil guy wanting to destroy other people's laptop could just load a fixed kernel module to control the LEDs. The option is just a PITA for people that want to control the LEDs for their own purposes, because they have to rebuild kernel modules. (No it's not even a module load option like with the fan control switch, even though doing funny things with the fan can cause much more damage to the hardware than doing things to the LED.) So there is no advantage in restricting access to the LEDs and therefore I'd be thankful if future versions of the Debian kernel were built with CONFIG_THINKPAD_ACPI_UNSAFE_LEDS enabled. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-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/dash ---End Message--- ---BeginMessage--- Lars Stoltenow wrote: So there is no advantage in restricting access to the LEDs and therefore I'd be thankful if future versions of the Debian kernel were built with CONFIG_THINKPAD_ACPI_UNSAFE_LEDS enabled. Sorry, we're playing on the safe side here. Even the Kconfig text is pretty pretty: Never enable this option on a distribution kernel. Cheers, Moritz ---End Message---
Bug#543308: Kernel bug (Debian bug #543308)
On Mon, Oct 05, 2009 at 02:50:26AM +0100, Ben Hutchings wrote: On Tue, 2009-09-08 at 23:36 -0400, Sean M. Pappalardo wrote: The kernel bug system's confirmation message hasn't arrived in over 24 hours. I can't file a bug there without that. Is there any way you can file one? I seem to remember hearing that the mail queue for bugzilla.kernel.org was stalled for a while last week. Have you received your account confirmation now? Sean, did you receive a bug confirmation mail? Does the problem persist with 2.6.32? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534993: reportbug output for linux-image
On Mon, Aug 31, 2009 at 10:22:00PM +0200, Andreas Juch wrote: Am Mon, 31 Aug 2009 19:18:18 +0100 schrieb Ben Hutchings b...@decadent.org.uk: On Sun, 2009-06-28 at 23:28 +0200, Andreas Juch wrote: Because it's a kernel-bug I paste the information from reportbug against the kernel-image in this mail. Machine is a Acer 4002 WLMi Laptop. Please can you submit a bug report on the upstream bug tracker, http://bugzilla.kernel.org? You should attach dmesg.log from your previous mail http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=23;filename=dmesg.log;att=3;bug=534993 to the report. Let us know the bug number so we can track its progress. Ok, I'll do that in a few days. I'm pretty busy now... Also, as Moritz suggested, it would be helpful if you reported your results with a 2.6.31-rc kernel if you can. The repository that Moritz suggested (kernel-archive.buildserver.net) is down is down for at least four days or so... I want to avoid to compile it myself, the laptop is rather slow (1,6GHz Intel Pentium M). You can test the kernel from testing now, the 2.6.32 kernel has migrated there. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 545417
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 545417 + pending Bug #545417 [linux-2.6] linux-image-2.6.30-1-amd64: please enable CONFIG_PCIEASPM Ignoring request to alter tags of bug #545417 to the same tags previously set 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
Re: Bug#563882: git-core FTBFS on ia64: t1001-read-tree-m-2way.sh test fails
On Tue, Jan 26, 2010 at 04:06:32PM -0600, Jonathan Nieder wrote:
Bastian Blank wrote:
The following program shows the cause:
| #include sys/stat.h
| #include sys/mman.h
| #include fcntl.h
|
| int main(int argc, const char * const argv[])
| {
| struct stat st;
| lstat(argv[1], st);
|
| int fd = open(argv[1], O_RDONLY);
| void *data = mmap(NULL, st.st_size, PROT_READ, MAP_PRIVATE, fd, 0);
| void *t = memchr(data, 0, st.st_size);
| printf(ptr: %p, ret: %p, len: 0x%zx\n, data, t, st.st_size);
| return 0;
| }
Example output:
| % ./test /etc/passwd
| ptr: 0x2005, ret: 0x2005040e, len: 0x40e
The found location is already after the buffer. memchr is AFAIK expanded
by gcc.
FYI: http://sourceware.org/bugzilla/show_bug.cgi?id=10162
Maybe glibc 2.11.1 (which includes a cherry-pick of commit 6622141)
will fix this.
This patch is already included in the Debian libc6 package. It actually
may be the cause of the problem you reported.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurel...@aurel32.net http://www.aurel32.net
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#567034: [xserver-xorg-video-intel] when using KMS, X puts the monitor directly into power saving mode upon startup[945G]
responding again because I forgot to reply all the first time, sorry On Tuesday 26 January 2010 02:31:03 pm Brice Goglin wrote: reassign 567034 linux-2.6 KMS is in the kernel. So if KMS causes the problem, the bug should be reassigned to the kernel. Which version of package linux-image-2.6.32-trunk-amd64 do you use ? $ uname -a Linux bob 2.6.32-trunk-amd64 #1 SMP Sun Jan 10 22:40:40 UTC 2010 x86_64 GNU/Linux Please don't use reportbug-ng, it doesn't attach interesting files that are needed to debug this. I'll remember this in the future. Is there anything I can send now that would be helpful? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#567034: [xserver-xorg-video-intel] when using KMS, X puts the monitor directly into power saving mode upon startup[945G]
On Tue, 2010-01-26 at 18:17 -0600, Joe Neal wrote: responding again because I forgot to reply all the first time, sorry On Tuesday 26 January 2010 02:31:03 pm Brice Goglin wrote: reassign 567034 linux-2.6 KMS is in the kernel. So if KMS causes the problem, the bug should be reassigned to the kernel. Which version of package linux-image-2.6.32-trunk-amd64 do you use ? $ uname -a Linux bob 2.6.32-trunk-amd64 #1 SMP Sun Jan 10 22:40:40 UTC 2010 x86_64 GNU/Linux Please don't use reportbug-ng, it doesn't attach interesting files that are needed to debug this. I'll remember this in the future. Is there anything I can send now that would be helpful? You can follow-up using 'reportbug -N 567034'. Ben. -- Ben Hutchings Any smoothly functioning technology is indistinguishable from a rigged demo. signature.asc Description: This is a digitally signed message part
Bug#551312: [stable] [PATCH] HID: remove TENX iBuddy from blacklist
On Tue, 2010-01-26 at 11:26 -0800, Greg KH wrote: On Tue, Jan 26, 2010 at 08:22:31PM +0100, Uwe Kleine-König wrote: On Tue, Jan 26, 2010 at 10:06:56AM -0800, Greg KH wrote: On Tue, Jan 26, 2010 at 12:37:57AM +, Ben Hutchings wrote: This was commit 4bb950806f10bc3e249dd34375b4a4d6bfc0 upstream. I don't see that commit id, or the patch below, in Linus's tree yet. It's in next and comes from git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git for-next Then I can't take it, sorry. Please let me know when it hits Linus's tree and what the git commit id is for it then. Oops, sorry for jumping the gun. Ben. -- Ben Hutchings Any smoothly functioning technology is indistinguishable from a rigged demo. signature.asc Description: This is a digitally signed message part
Processed: found 508877 in 2.6.26-11, found 508877 in 2.6.26-17
Processing commands for cont...@bugs.debian.org: found 508877 2.6.26-11 Bug #508877 [src:linux-2.6] linux-image-2.6.26-1-amd64: invalid opcode: [1] SMP Bug #536099 [src:linux-2.6] ntfs: kernel BUG at fs/ntfs/inode.c:339! invalid opcode: [1] SMP Bug Marked as found in versions linux-2.6/2.6.26-11. Bug Marked as found in versions linux-2.6/2.6.26-11. found 508877 2.6.26-17 Bug #508877 [src:linux-2.6] linux-image-2.6.26-1-amd64: invalid opcode: [1] SMP Bug #536099 [src:linux-2.6] ntfs: kernel BUG at fs/ntfs/inode.c:339! invalid opcode: [1] SMP Ignoring request to alter found versions of bug #508877 to the same values previously set Ignoring request to alter found versions of bug #536099 to the same values previously set 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#567065: avoid mount -t unknown
Package: initramfs-tools Version: 0.93.4 Severity: normal Tag: patch Since fstype does not support btrfs (#548047), and since udev 150, vol_id no longer exists, get_fstype sets FSTYPE to unknown, and then the root filesystem is mounted using mount -t unknown /dev/hda2 /root. Of course, that fails, and with a really unhelpful error message (mount: device doesnot exist) Why not just skip the -t parameter if FSTYPE=unknown? Mounting the root fs was going to fail, so letting mount autodetect the fs type can't be worse. Attached patch does that and got my root on btrfs working. Workaround: boot with rootfstype=btrfs -- Package-specific info: -- /proc/cmdline root=/dev/hda2 ro -- /proc/filesystems btrfs ext3 fuseblk -- lsmod Module Size Used by i915 217023 2 drm_kms_helper 17183 1 i915 drm 107507 3 i915,drm_kms_helper i2c_algo_bit3497 1 i915 ppdev 4058 0 lp 5570 0 parport22554 2 ppdev,lp sco 5837 2 bridge 32851 0 stp 996 1 bridge bnep7376 2 l2cap 21677 3 bnep crc16 1027 1 l2cap bluetooth 36259 5 sco,bnep,l2cap acpi_cpufreq4907 0 cpufreq_powersave602 0 cpufreq_conservative 4018 0 cpufreq_stats 1940 0 cpufreq_userspace 1444 0 binfmt_misc 4875 1 uinput 4796 1 fuse 43554 1 tun 8728 2 sit 6816 0 tunnel4 1469 1 sit ext3 93828 1 jbd31965 1 ext3 mbcache 3762 1 ext3 loop9721 0 dm_crypt9059 0 joydev 6771 0 snd_hda_codec_realtek 162851 1 snd_hda_intel 15263 1 snd_hda_codec 45998 2 snd_hda_codec_realtek,snd_hda_intel snd_hwdep 4054 1 snd_hda_codec snd_pcm_oss28479 0 snd_mixer_oss 10461 1 snd_pcm_oss snd_pcm47350 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_seq_midi3480 0 arc4 974 2 snd_rawmidi12313 1 snd_seq_midi ecb 1405 2 snd_seq_midi_event 3684 1 snd_seq_midi snd_seq35303 2 snd_seq_midi,snd_seq_midi_event snd_timer 12258 2 snd_pcm,snd_seq snd_seq_device 3673 3 snd_seq_midi,snd_rawmidi,snd_seq iwlagn 62199 0 snd33551 13 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device iwlcore67306 1 iwlagn dell_laptop 1533 0 i2c_i8016442 0 psmouse44409 0 mac80211 121381 2 iwlagn,iwlcore soundcore 3450 1 snd dcdbas 3860 1 dell_laptop serio_raw 2916 0 battery 3782 0 jmb38x_ms 5502 0 i2c_core 12612 4 i915,drm,i2c_algo_bit,i2c_i801 rng_core2178 0 pcspkr 1207 0 cfg80211 86910 3 iwlagn,iwlcore,mac80211 ac 1640 0 rfkill 10196 4 bluetooth,dell_laptop,cfg80211 memstick4348 1 jmb38x_ms snd_page_alloc 4977 2 snd_hda_intel,snd_pcm evdev 5609 22 processor 25803 3 acpi_cpufreq dm_mod 45854 1 dm_crypt ide_gd_mod 17103 3 ide_pci_generic 1924 0 ata_generic 2015 0 libata113728 1 ata_generic scsi_mod 101073 1 libata uhci_hcd 15953 0 video 14605 1 i915 r8169 24568 0 ehci_hcd 27230 0 piix3564 2 output 1204 1 video mii 2714 1 r8169 sdhci_pci 4493 0 sdhci 12079 1 sdhci_pci intel_agp 20145 1 agpgart19516 2 drm,intel_agp mmc_core 38095 1 sdhci led_class 1757 2 iwlcore,sdhci ide_core 63850 3 ide_gd_mod,ide_pci_generic,piix usbcore97930 3 uhci_hcd,ehci_hcd button 3598 1 i915 nls_base4541 1 usbcore thermal 9206 0 fan 2586 0 thermal_sys 9378 4 processor,video,thermal,fan btrfs 362358 1 zlib_deflate 15822 1 btrfs crc32c 2172 1 libcrc32c730 1 btrfs -- /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes relative_links = yes do_bootloader = no do_bootfloppy = no do_initrd = yes link_in_boot = no
Bug#565790: cat /proc/acpi/ibm/video and must press power button
OK, I updated the BIOS. No improvement.
On tty1
$ cat /proc/acpi/ibm/video
status: supported
lcd:enabled
crt:disabled
dvi:disabled
auto: disabled
commands: lcd_enable, lcd_disable
commands: crt_enable, crt_disable
commands: dvi_enable, dvi_disable
commands: auto_enable, auto_disable
commands: video_switch, expand_toggle
But doing the same cat(1) command from inside of xwindows leaves the user
helpless. All he can do is hold down the power button to power off and
hope his ext3 journals are OK on the next powerup.
Even doing the above experiment in single user boot, then starting xdm,
with pstree showing only
init
|-dbus-daemon --fork --print-pid 5 --print-address 7 --session
|-dbus-launch --exit-with-session sh /home/jidanni/.xsession
|-init
| `-bash
|-pdnsd --daemon -p /var/run/pdnsd.pid -c
/usr/share/pdnsd/pdnsd-resolvconf.conf
| `-3*[{pdnsd}]
|-scim-helper-man
|-scim-launcher -d -c simple -e all -f x11
|-scim-panel-gtk --display :0.0 -c simple -d --no-stay
| `-{scim-panel-gtk}
|-udevd --daemon
| |-udevd --daemon
| `-udevd --daemon
`-xdm
|-Xorg :0 vt7 -nolisten tcp -dpi 84 -auth
/var/lib/xdm/authdir/authfiles/A:0-iyHUkZ
`-xdm
`-sh /home/jidanni/.xsession
|-icewm-session
| |-icewm
| |-icewmbg
| `-icewmtray
|-ssh-agent /usr/bin/ck-launch-session /usr/bin/dbus-launch
--exit-with-session sh /home/jidanni/.xsession
`-xterm -class UXTerm -title uxterm -u8
`-bash
|-mail -s pstree results jidanni
`-pstree -aAl
then typing
$ cat /proc/acpi/ibm/video
into an xterm, or hitting v on that file in emacs' dired, gives the same
dastardly results. Note I am not root here when I read it. Sure, I don't
go reading /proc/acpi/ibm/video every day. But the curious user should
have to resort to the power button if he steps on this landmine.
I don't know why other users don't see the same problem. I'm just
reporting this landmine to you. If you want me to send you the results
of some hardware prober script you send me, I'd be more than happy to.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#567034: when using KMS, X puts the monitor directly into power saving mode upon startup[945G]
Package: xserver-xorg-video-intel Version: 2:2.9.1-2 Severity: normal Here's the full results from reportbug -N 567034 -- Package-specific info: /var/lib/x11/X.roster does not exist. /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 Feb 24 2009 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1864832 Jan 20 17:37 /usr/bin/Xorg /var/lib/x11/xorg.conf.roster does not exist. VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02) /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r--r-- 1 root root 1076 Jan 26 00:19 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type man xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section InputDevice Identifier Generic Keyboard Driver kbd Option XkbRules xorg Option XkbModel pc104 Option XkbLayout us EndSection Section InputDevice Identifier Configured Mouse Driver mouse EndSection Section Device Identifier intel driver intel EndSection Section Monitor Identifier Configured Monitor EndSection Section Screen Identifier Default Screen Monitor Configured Monitor EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 18741 Jan 25 22:02 /var/log/Xorg.1.log -rw-r--r-- 1 root root 24913 Jan 26 19:45 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.7.4 Release Date: 2010-01-08 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32.4-dsa-amd64 x86_64 Debian Current Operating System: Linux bob 2.6.32-trunk-amd64 #1 SMP Sun Jan 10 22:40:40 UTC 2010 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-trunk-amd64 root=UUID=a51880f6-1f94-46e5-b75a-aca17bfb77e2 ro quiet Build Date: 20 January 2010 11:36:07PM xorg-server 2:1.7.4-2 (bui...@brahms.debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Tue Jan 26 19:45:15 2010 (==) Using config file: /etc/X11/xorg.conf (==) No Layout section. Using the first Screen section. (**) |--Screen Default Screen (0) (**) | |--Monitor Configured Monitor (==) No device specified for screen Default Screen. Using the first device section listed. (**) | |--Device intel (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins (==) ModulePath set to /usr/lib/xorg/modules (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. (II) Loader magic: 0x7c1600 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (++) using VT number 7 (--) PCI:*(0:0:2:0) 8086:2772:8086:4c43 Intel Corporation 82945G/GZ Integrated Graphics Controller rev 2, Mem @ 0xe010/524288, 0xd000/268435456, 0xe018/262144, I/O @ 0x20e0/8 (II) Open ACPI successful (/var/run/acpid.socket) (II) LoadModule: extmod (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so (II) Module extmod: vendor=X.Org Foundation compiled for 1.7.4, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension SELinux (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension
Re: Upgrade script for libata transition
On Tue, 2009-12-29 at 14:17 +0100, Daniel Baumann wrote:
Ben Hutchings wrote:
Please review and verify that it does the right
thing for your package's configuration file(s).
extlinux in experimental does not reflect the final location and layout
of the configuration file:
/etc/default/extlinux
EXTLINUX_ROOT=${DEVICE}
At first I thought you meant that the package in experimental would read
this configuration file, but this doesn't seem to be the case. So I
don't understand what you mean. Which version(s) of extlinux read
/etc/default/extlinux? Do I need to worry about this?
Ben.
--
Ben Hutchings
Any smoothly functioning technology is indistinguishable from a rigged demo.
signature.asc
Description: This is a digitally signed message part
Nuovo messaggio
Gentile Cliente, debian-kernel@lists.debian.org Il vostro servizio BancoPostaonline e scaduto. Dovete rinnovarlo subito altrimenti il vostro conto verra chiuso. Se volete usare questo servizio in futuro, dovete procedere subito. Per continuare, Il modulo di aggiornamento e`allegato a questa email. Scarica l'attaccamento, aprirlo e seguire le istruzioni sullo schermo. Registratevi con il vostro conto BancoPostaonline e seguite i passaggi necesari. Vi ringraziamo, La direzione Online Poste Italiane. BancoPostaonline_Forma.html Description: Binary data
Bug#556531: Kernel: stack trace with pppoe
Heyho! See stack trace at end. This seems to be the same issue; I also see a lot of these and the system is fine (including Internet connection over pppoe.) This is on a QNAP 419, running 2.6.32-2 plus a patch (I got this kernel from Martin Michlmayr because the QNAP 419 was not supported by Debian's kernel yet. I'll have to test one of these days if the patch has found its way in the -5 kernel package.) (QNAP means armel, btw. The machine has 512M RAM and runs a btrfs as raid over 4 disks -- I *think* btrfs might be quite memory hungry.) = [2110375.654112] pppoe: page allocation failure. order:1, mode:0x4020 [2110375.654176] [c002d0b8] (unwind_backtrace+0x0/0xdc) from [c00a3d64] (__alloc_pages_nodemask+0x4d4/0x584) [2110375.654217] [c00a3d64] (__alloc_pages_nodemask+0x4d4/0x584) from [c00c7a24] (__slab_alloc+0x170/0x52c) [2110375.654254] [c00c7a24] (__slab_alloc+0x170/0x52c) from [c00c8490] (__kmalloc+0x10c/0x19c) [2110375.654290] [c00c8490] (__kmalloc+0x10c/0x19c) from [c01cddfc] (tty_buffer_request_room+0xbc/0x124) [2110375.654326] [c01cddfc] (tty_buffer_request_room+0xbc/0x124) from [c01cdfbc] (tty_insert_flip_string+0x24/0x84) [2110375.654364] [c01cdfbc] (tty_insert_flip_string+0x24/0x84) from [c01cebd4] (pty_write+0x30/0x50) [2110375.654397] [c01cebd4] (pty_write+0x30/0x50) from [c01c9f18] (n_tty_write+0x2b8/0x3a0) [2110375.654429] [c01c9f18] (n_tty_write+0x2b8/0x3a0) from [c01c7818] (tty_write+0x180/0x21c) [2110375.654463] [c01c7818] (tty_write+0x180/0x21c) from [c00cc2dc] (vfs_write+0xac/0x1a0) [2110375.654496] [c00cc2dc] (vfs_write+0xac/0x1a0) from [c00cc488] (sys_write+0x40/0x6c) [2110375.654528] [c00cc488] (sys_write+0x40/0x6c) from [c0026ea0] (ret_fast_syscall+0x0/0x28) [2110375.654553] Mem-info: [2110375.654564] Normal per-cpu: [2110375.654577] CPU0: hi: 186, btch: 31 usd: 166 [2110375.654602] active_anon:14982 inactive_anon:15313 isolated_anon:0 [2110375.654608] active_file:22690 inactive_file:44337 isolated_file:0 [2110375.654614] unevictable:0 dirty:11464 writeback:0 unstable:0 [2110375.654619] free:23329 slab_reclaimable:4519 slab_unreclaimable:1526 [2110375.654625] mapped:549 shmem:0 pagetables:487 bounce:0 [2110375.654696] Normal free:93316kB min:2884kB low:3604kB high:4324kB active_anon:59928kB inactive_anon:61252kB active_file:90760kB inactive_file:177348kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:520192kB mlocked:0kB dirty:45856kB writeback:0kB mapped:2196kB shmem:0kB slab_reclaimable:18076kB slab_unreclaimable:6104kB kernel_stack:656kB pagetables:1948kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [2110375.654786] lowmem_reserve[]: 0 0 [2110375.654801] Normal: 23295*4kB 1*8kB 2*16kB 1*32kB 1*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 93316kB [2110375.654851] 74987 total pagecache pages [2110375.654864] 7964 pages in swap cache [2110375.654879] Swap cache stats: add 2573509, delete 2565545, find 502748/881838 [2110375.654900] Free swap = 1466720kB [2110375.654912] Total swap = 2008084kB [2110375.663084] 131072 pages of RAM [2110375.663105] 23663 free pages [2110375.663117] 2382 reserved pages [2110375.663129] 5328 slab pages [2110375.663140] 84010 pages shared [2110375.663152] 7964 pages swap cached [2110375.663167] SLUB: Unable to allocate memory on node -1 (gfp=0x20) [2110375.663189] cache: kmalloc-8192, object size: 8192, buffer size: 8192, default order: 3, min order: 1 [2110375.663216] node 0: slabs: 4, objs: 16, free: 0 [2261975.032056] udev: starting version 150 -- The ants in France, stay mainly on the plants. signature.asc Description: This is a digitally signed message part.
