Bug#618930: High network latency with ralink usb wireless device
On 19/03/2011 22:31, Johannes Stezenbach wrote: I sent a patch to disable power save by default, but then work started to fix it instead, but then stalled. Seems like 2.6.38 shipped with broken power save enabled by default. Plese read the discussion following my RFC patch: http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/2011-January/thread.html#3017 You can test if power saving causes your issue by disabling it with iwconfig wlan0 power off. That does the trick - thanks! richard@sfere:~$ ssh violeer uname -a Linux violeer 2.6.38-1-686 #1 SMP Wed Mar 16 17:37:47 UTC 2011 i686 GNU/Linux richard@sfere:~$ ping -qc10 violeer PING violeer.wlan.anjou.terraraq.org.uk (172.31.59.138) 56(84) bytes of data. --- violeer.wlan.anjou.terraraq.org.uk ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9016ms rtt min/avg/max/mdev = 0.919/0.981/1.089/0.057 ms richard@sfere:~$ ttfn/rjk -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d85c506.1060...@greenend.org.uk
Bug#613536: firmware-realtek: Please include the binary firmware for Realtek
Perhaps it is easier or better to grab the rtlwifi/rtl8192cfw.bin firmware from the linux-firmware repository: http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=summary The corresponding license is included there as LICENCE.rtlwifi_firmware.txt . I've been happily using it for weeks with compat-wireless and linux-image-2.6.32-5-amd64 on my Thinkpad with Linux Mint Debian Edition. Further details at: http://www.thinkwiki.org/wiki/ThinkPad_11b/g/n_Wireless_LAN_Mini-PCI_Express_Adapter_III Recent Dell Minis feature this wifi adapter, too, so I guess it is or will become quite common. I'm just about to switch to the 2.6.38 kernel which includes the corresponding rtl8192ce driver, but unfortunately it is not enabled in the Debian unstable package, yet. However, my manual rebuild of that package with the module enabled works well so far, so maybe I just need to send a request for it. Cheers, Jonas -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTikr2=azrjN6=zb1teb7zpbdqfvzt4s8vsp3r...@mail.gmail.com
Bug#618665: linux-image-2.6.32-5-686: mouse pointer not visible and crashes when playing video files
Am Samstag, den 19.03.2011, 17:52 +1030 schrieb maikkeli: Renaming /etc/modprobe.d/i915.modeset.conf to /etc/modprobe.d/i915.modeset.conf.disabled does not disable modesetting, as confirmed by the output of: # cat /sys/module/i915/parameters/modeset Editing /etc/modprobe.d/i915.modeset.conf to contain the following, did disable modesetting: options i915 modeset=1 ..However, this simply causes the xorg intel driver to fail to load, falling back to vesa which works perfectly but is slow. I just took a look what my i915.modeset.conf, and it contains exactly the line 'options i915 modeset=1', and 'cat /sys/module/i915/parameters/modeset' yields 1 (kernel 2.6.32-31). I changed this to 'options i915 modeset=0' and rebooted. During boot, I noticed that the resolution (the font-size of the boot messages) is much lower, and directly before showing the login screen there is a brief, slightly distorted flash of the BIOS' spash-screen -- BTW, the same as if I live-boot Linux Mint 9. After boot, the mouse pointer was visible (still on kernel version 2.6.32-31) and I could play videos, but the playback was unusably slow. I also tried live-booting Ubuntu 10.04 once more. - if I boot with no parameters, the boot hangs instantly - if I boot with 'nolapic', it boots to a black screen - if I boot with 'nolapic' and 'i915.modeset=1', it boots to the desktop and even has composition enabled (and thus 3D acceleration), but crashes after a few seconds, falling back to reduced graphic settings As a reminder, I can boot Debian with 'nolapic' and with /sys/module/i915/parameters/modeset yielding '1', and everything runs fine (with kernel 2.6.32-30), but no 3D acceleration. I do not expect to get my 3D acceleration fixed here, but maybe this information is of some relevance for fixing the bug. Regards, Tobias -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1300622521.7486.1.camel@tk-laptop.workgroup
Bug#618665: linux-image-2.6.32-5-686: mouse pointer not visible
I experienced too disappearance of mouse pointer right after upgrade to 2.6.32-31 and reboot. My machine is an Acer TM2301 with i855gm graphics and 768 MB ram. Downgrading to 2.6.32-30 resolved the issue. Regards, Lorenzo Masellis -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110320130832.402a32bb@castor
Processed: Re: Bug#618997: Debian 6.01 - Synaptics Touchpad - no cursor after update
Processing commands for cont...@bugs.debian.org: reassign 618997 linux-2.6 2.6.32-31 Bug #618997 [xserver-xorg-input-synaptics] Debian 6.01 - Synaptics Touchpad - no cursor after update Bug reassigned from package 'xserver-xorg-input-synaptics' to 'linux-2.6'. Bug No longer marked as found in versions xserver-xorg-input-synaptics/1.2.2-2. Bug #618997 [linux-2.6] Debian 6.01 - Synaptics Touchpad - no cursor after update There is no source info for the package 'linux-2.6' at version '2.6.32-31' with architecture '' Unable to make a source version for version '2.6.32-31' Bug Marked as found in versions 2.6.32-31. forcemerge 618665 618997 Bug#618665: linux-image-2.6.32-5-686: mouse pointer not visible and crashes when playing video files Bug#618997: Debian 6.01 - Synaptics Touchpad - no cursor after update Forcibly Merged 618665 618997. kthxbye Stopping processing here. Please contact me if you need assistance. -- 618997: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618997 618665: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13006242321211.transcr...@bugs.debian.org
Bug#619010: linux-image-2.6.38-1-686-bigmem: Fails to boot on lvm2/looks system
Package: linux-2.6 Version: 2.6.38-1 Severity: grave Justification: renders package unusable Booting a stock 686-bigmem 2.6.38 kernel hangs after loading the initrd with the message LVM no volumes found and evms_activate failed. Booting an older 2.6.37 stock kernel works on the same system. -- Package-specific info: ** Kernel log: boot messages should be attached (From Memory): LVM no volumes found (repeated twice) evms-activate failed ** Model information not available ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07) Subsystem: Lenovo Device [17aa:20e0] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: access denied Kernel driver in use: agpgart-intel 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:20e4] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 46 Region 0: Memory at f200 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at d000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at 1800 [size=8] Expansion ROM at unassigned [disabled] Capabilities: access denied Kernel driver in use: i915 00:02.1 Display controller [0380]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a43] (rev 07) Subsystem: Lenovo Device [17aa:20e4] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Region 0: Memory at f240 (64-bit, non-prefetchable) [size=1M] Capabilities: access denied 00:03.0 Communication controller [0780]: Intel Corporation Mobile 4 Series Chipset MEI Controller [8086:2a44] (rev 07) Subsystem: Lenovo Device [17aa:20e6] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx+ Latency: 0 Interrupt: pin A routed to IRQ 11 Region 0: Memory at f2826800 (64-bit, non-prefetchable) [size=16] Capabilities: access denied 00:03.2 IDE interface [0101]: Intel Corporation Mobile 4 Series Chipset PT IDER Controller [8086:2a46] (rev 07) (prog-if 85 [Master SecO PriO]) Subsystem: Lenovo Device [17aa:20ea] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin C routed to IRQ 18 Region 0: I/O ports at 1828 [size=8] Region 1: I/O ports at 180c [size=4] Region 2: I/O ports at 1820 [size=8] Region 3: I/O ports at 1808 [size=4] Region 4: I/O ports at 1810 [size=16] Capabilities: access denied Kernel driver in use: ata_generic 00:03.3 Serial controller [0700]: Intel Corporation Mobile 4 Series Chipset AMT SOL Redirection [8086:2a47] (rev 07) (prog-if 02 [16550]) Subsystem: Lenovo Device [17aa:20ec] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin B routed to IRQ 17 Region 0: I/O ports at 1830 [size=8] Region 1: Memory at f2624000 (32-bit, non-prefetchable) [size=4K] Capabilities: access denied Kernel driver in use: serial 00:19.0 Ethernet controller [0200]: Intel Corporation 82567LM Gigabit Network Connection [8086:10f5] (rev 03) Subsystem: Lenovo Device [17aa:20ee] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 43 Region 0: Memory at f260 (32-bit, non-prefetchable) [size=128K] Region 1: Memory at f2625000 (32-bit, non-prefetchable) [size=4K] Region 2: I/O ports at 1840 [size=32] Capabilities: access denied Kernel driver in use: e1000e 00:1a.0 USB
Bug#618976: [linux-2.6] Please support ppc64
On Sun, 2011-03-20 at 13:21 +0900, Hiroyuki Yamamoto wrote: Hi, (2011年03月20日 12:22), Ben Hutchings wrote: Please support ppc64. Is 'ppc64' an official port yet? No, not 'official' port now. However, considerable parts of the environment for ppc64 port still remain in the packaging system. I didn't mean 'is it a release architecture'. Well, I found the answer: http://www.debian.org/ports/#unreleased does list ppc64. Why does this patch add a new config file rather than referring to powerpc/config and powerpc/config.powerpc64? Well, I used the same files as powerpc port for the time being. I think that the same file should be indicated if it is necessary to be managed as the same one for easiness. And I also think that a different file should be indicated if the possibility to be managed as another file is left. This may be likely to discuss it. It would still be possible to override config options. But I think ppc64/powerpc64 should be the same as powerpc/powerpc64. (Just as amd64/amd64 is the same as i386/amd64, and sparc64/sparc64 is the same as sparc/sparc64.) Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#619019: xserver-xorg-video-intel: latest update to debian squeeze made the mouse pointer invisible in my openbox/gdm session
Processing commands for cont...@bugs.debian.org: reassign 619019 linux-2.6 2.6.32-31 Bug #619019 [xserver-xorg-video-intel] xserver-xorg-video-intel: latest update to debian squeeze made the mouse pointer invisible in my openbox/gdm session 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.13.0-6. Bug #619019 [linux-2.6] xserver-xorg-video-intel: latest update to debian squeeze made the mouse pointer invisible in my openbox/gdm session There is no source info for the package 'linux-2.6' at version '2.6.32-31' with architecture '' Unable to make a source version for version '2.6.32-31' Bug Marked as found in versions 2.6.32-31. forcemerge 618665 619019 Bug#618665: linux-image-2.6.32-5-686: mouse pointer not visible and crashes when playing video files Bug#619019: xserver-xorg-video-intel: latest update to debian squeeze made the mouse pointer invisible in my openbox/gdm session Bug#618997: Debian 6.01 - Synaptics Touchpad - no cursor after update Forcibly Merged 618665 618997 619019. affects 618665 + xserver-xorg-video-intel Bug #618665 [linux-2.6] linux-image-2.6.32-5-686: mouse pointer not visible and crashes when playing video files Bug #618997 [linux-2.6] Debian 6.01 - Synaptics Touchpad - no cursor after update Bug #619019 [linux-2.6] xserver-xorg-video-intel: latest update to debian squeeze made the mouse pointer invisible in my openbox/gdm session Added indication that 618665 affects xserver-xorg-video-intel Added indication that 618997 affects xserver-xorg-video-intel Added indication that 619019 affects xserver-xorg-video-intel kthxbye Stopping processing here. Please contact me if you need assistance. -- 618665: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618665 619019: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619019 618997: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618997 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130062929818200.transcr...@bugs.debian.org
Re: Bug#619019: xserver-xorg-video-intel: latest update to debian squeeze made the mouse pointer invisible in my openbox/gdm session
reassign 619019 src:linux-2.6 2.6.32-31 affects 619019 xserver-xorg-video-intel thanks Hi, and thanks for your report. LN2 mbfmau...@gmail.com (20/03/2011): The latest update to debian squeeze seems to have introduced the Bug reported here http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550942 . (Upstream bug report can be found here https://bugs.freedesktop.org/show_bug.cgi?id=29413 .), […] Apparently the fix for this problem that the upstream bug links to was not included in the latest squeeze update. AFAICT from the upstream bug, the guilty commit is on the kernel side: | drm/i915: Add pipe A force quirk for some laptops (Closes: #608148) and that commit got included in the kernel update for the 6.0.1 point release: http://packages.qa.debian.org/l/linux-2.6/news/20110307T195907Z.html So downgrading your kernel to the previous revision (2.6.32-30) should make your cursor become available again. Kernel maintainers, you apparently want this commit to fix that: | commit 897493504addc5609f04a2c4f73c37ab972c29b2 | Author: Chris Wilson ch...@chris-wilson.co.uk | Date: Sun Sep 12 18:25:19 2010 +0100 | | drm/i915: Ensure that the crtcinfo is populated during mode_fixup() | | This should fix the mysterious mode setting failures reported during | boot up and after resume, generally for i8xx class machines. | | Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=16478 | Reported-and-tested-by: Xavier Chantry chantry.xav...@gmail.com | Buzilla: https://bugs.freedesktop.org/show_bug.cgi?id=29413 | Tested-by: Daniel Vetter dan...@ffwll.ch | Signed-off-by: Chris Wilson ch...@chris-wilson.co.uk | Cc: sta...@kernel.org KiBi. signature.asc Description: Digital signature
Processed: Re: Bug#619019: xserver-xorg-video-intel: latest update to debian squeeze made the mouse pointer invisible in my openbox/gdm session
Processing commands for cont...@bugs.debian.org: reassign 619019 src:linux-2.6 2.6.32-31 Bug #619019 [linux-2.6] xserver-xorg-video-intel: latest update to debian squeeze made the mouse pointer invisible in my openbox/gdm session Bug #618665 [linux-2.6] linux-image-2.6.32-5-686: mouse pointer not visible and crashes when playing video files Bug #618997 [linux-2.6] Debian 6.01 - Synaptics Touchpad - no cursor after update Bug reassigned from package 'linux-2.6' to 'src:linux-2.6'. Bug reassigned from package 'linux-2.6' to 'src:linux-2.6'. Bug reassigned from package 'linux-2.6' to 'src:linux-2.6'. Bug No longer marked as found in versions 2.6.32-31. Bug No longer marked as found in versions 2.6.32-31. Bug No longer marked as found in versions 2.6.32-31. Bug #619019 [src:linux-2.6] xserver-xorg-video-intel: latest update to debian squeeze made the mouse pointer invisible in my openbox/gdm session Bug #618665 [src:linux-2.6] linux-image-2.6.32-5-686: mouse pointer not visible and crashes when playing video files Bug #618997 [src:linux-2.6] Debian 6.01 - Synaptics Touchpad - no cursor after update Bug Marked as found in versions linux-2.6/2.6.32-31. Bug Marked as found in versions linux-2.6/2.6.32-31. Bug Marked as found in versions linux-2.6/2.6.32-31. affects 619019 xserver-xorg-video-intel Bug #619019 [src:linux-2.6] xserver-xorg-video-intel: latest update to debian squeeze made the mouse pointer invisible in my openbox/gdm session Bug #618665 [src:linux-2.6] linux-image-2.6.32-5-686: mouse pointer not visible and crashes when playing video files Bug #618997 [src:linux-2.6] Debian 6.01 - Synaptics Touchpad - no cursor after update Added indication that 619019 affects xserver-xorg-video-intel Added indication that 618665 affects xserver-xorg-video-intel Added indication that 618997 affects xserver-xorg-video-intel thanks Stopping processing here. Please contact me if you need assistance. -- 619019: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619019 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130062983320018.transcr...@bugs.debian.org
Processed: severity of 619010 is important
Processing commands for cont...@bugs.debian.org: severity 619010 important Bug #619010 [linux-2.6] linux-image-2.6.38-1-686-bigmem: Fails to boot on lvm2/looks system Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 619010: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130063053922628.transcr...@bugs.debian.org
Bug#619010: linux-image-2.6.38-1-686-bigmem: Fails to boot on lvm2/looks system
On Sun, 2011-03-20 at 13:43 +0100, Volker Schlecht wrote: Package: linux-2.6 Version: 2.6.38-1 Severity: grave Justification: renders package unusable Booting a stock 686-bigmem 2.6.38 kernel hangs after loading the initrd with the message LVM no volumes found and evms_activate failed. [...] Do you mean 'LUKS' rather than 'looks'? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#619022: linux-image-2.6.38-1-686: Screen corruption with i855
On Sun, 2011-03-20 at 15:08 +0100, Cesare Leonardi wrote: Package: linux-2.6 Version: 2.6.38-1 Severity: normal See the attached image. It is usually evident scrolling pages and with changing elements (like Gnome system activities icons). The right part of any window title bar is always corrupted. I've already seen this problem with 2.6.38-rc6 from experimental, get much better with rc7, then regressed with rc8 and the stable release. Reading from upstream changelogs looks like it's a known problem that they think it's solved but evidently not in my case. [...] Please report this upstream on https://bugs.freedesktop.org, under product 'DRI', component 'DRM/Intel'. Let us know the bug URL so we can track it. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#619022: linux-image-2.6.38-1-686: Screen corruption with i855
On 20/03/2011 15:20, Ben Hutchings wrote: Please report this upstream onhttps://bugs.freedesktop.org, under product 'DRI', component 'DRM/Intel'. Let us know the bug URL so we can track it. bugs.freedesktop.org? So do you think it's a bug in X.org and not the kernel? But if i use 2.6.37, as now, the problem is not present. Shouldn't be reported to bugzilla.kernel.org? Cesare. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d8610f1.1080...@gmail.com
Bug#618976: [linux-2.6] Please support ppc64
On Sun, 2011-03-20 at 13:18 +, Ben Hutchings wrote:
On Sun, 2011-03-20 at 13:21 +0900, Hiroyuki Yamamoto wrote:
Hi,
(2011年03月20日 12:22), Ben Hutchings wrote:
Please support ppc64.
Is 'ppc64' an official port yet?
No, not 'official' port now.
However, considerable parts of the environment for ppc64 port still
remain in the packaging system.
I didn't mean 'is it a release architecture'. Well, I found the answer:
http://www.debian.org/ports/#unreleased does list ppc64.
Why does this patch add a new config file rather than referring to
powerpc/config and powerpc/config.powerpc64?
Well, I used the same files as powerpc port for the time being.
I think that the same file should be indicated if it is necessary to
be managed as the same one for easiness.
And I also think that a different file should be indicated if the
possibility to be managed as another file is left.
This may be likely to discuss it.
It would still be possible to override config options. But I think
ppc64/powerpc64 should be the same as powerpc/powerpc64. (Just as
amd64/amd64 is the same as i386/amd64, and sparc64/sparc64 is the same
as sparc/sparc64.)
Please try the attached patch. This avoids the duplication of config
files or rules in debian/rules.real. It also uses the flavour name
'powerpc64' rather than 'ppc64', matching the name used on powerpc.
This should make any future multiarch transition for powerpc users a
little smoother.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
Index: debian/config/ppc64/defines
===
--- debian/config/ppc64/defines (revision 0)
+++ debian/config/ppc64/defines (revision 0)
@@ -0,0 +1,14 @@
+[base]
+flavours:
+ powerpc64
+kernel-arch: powerpc
+
+[image]
+configs: powerpc/config
+suggests: mkvmlinuz
+
+[powerpc64_description]
+hardware: 64-bit PowerPC
+
+[powerpc64_image]
+configs: powerpc/config.powerpc64
Index: debian/config/defines
===
--- debian/config/defines (revision 17075)
+++ debian/config/defines (working copy)
@@ -13,6 +13,7 @@
mips
mipsel
powerpc
+ ppc64
s390
sh4
sparc
Index: debian/rules.real
===
--- debian/rules.real (revision 17070)
+++ debian/rules.real (working copy)
@@ -39,7 +39,7 @@
#
binary-arch-arch: install-headers_$(ARCH)
binary-arch-arch: install-libc-dev_$(ARCH)
-ifneq ($(filter alpha amd64 armel hppa i386 powerpc s390 sh4 sparc sparc64,$(ARCH)),)
+ifneq ($(filter alpha amd64 armel hppa i386 powerpc ppc64 s390 sh4 sparc sparc64,$(ARCH)),)
binary-arch-arch: install-tools_$(ARCH)
endif
binary-arch-featureset: install-headers_$(ARCH)_$(FEATURESET)
@@ -255,7 +255,7 @@
cp -a $(SOURCE_DIR)/{.config,.kernel*,Module.symvers,include} $(DIR)
cp -a $(SOURCE_DIR)/arch/$(KERNEL_ARCH)/kernel/asm-offsets.s $(DIR)/arch/$(KERNEL_ARCH)/kernel
-ifeq ($(ARCH),powerpc)
+ifneq ($(filter powerpc ppc64,$(ARCH)),)
if [ -f $(SOURCE_DIR)/arch/$(KERNEL_ARCH)/lib/crtsavres.o ]; then \
mkdir $(DIR)/arch/$(KERNEL_ARCH)/lib; \
cp -a $(SOURCE_DIR)/arch/$(KERNEL_ARCH)/lib/crtsavres.o $(DIR)/arch/$(KERNEL_ARCH)/lib; \
@@ -385,13 +385,15 @@
install-image_mipsel_$(FEATURESET)_$(FLAVOUR)_plain_image:
install -m644 '$(DIR)/vmlinux' $(INSTALL_DIR)/vmlinux-$(REAL_VERSION)
-install-image_powerpc_$(FEATURESET)_$(FLAVOUR)_plain_image: WRAPPER_INSTALL_DIR = '$(CURDIR)'/$(PACKAGE_DIR)/usr/lib/linux-image-$(REAL_VERSION)
-install-image_powerpc_$(FEATURESET)_$(FLAVOUR)_plain_image:
+ifneq ($(filter powerpc ppc64,$(ARCH)),)
+install-image_$(ARCH)_$(FEATURESET)_$(FLAVOUR)_plain_image: WRAPPER_INSTALL_DIR = '$(CURDIR)'/$(PACKAGE_DIR)/usr/lib/linux-image-$(REAL_VERSION)
+install-image_$(ARCH)_$(FEATURESET)_$(FLAVOUR)_plain_image:
install -m644 '$(DIR)/vmlinux' $(INSTALL_DIR)/vmlinux-$(REAL_VERSION)
+$(MAKE_CLEAN) -C '$(DIR)' bootwrapper_install \
WRAPPER_OBJDIR='$(WRAPPER_INSTALL_DIR)' \
WRAPPER_DTSDIR='$(WRAPPER_INSTALL_DIR)'/dts \
WRAPPER_BINDIR='$(WRAPPER_INSTALL_DIR)'
+endif
install-image_s390_$(FEATURESET)_$(FLAVOUR)_plain_image:
install -m644 '$(DIR)/arch/s390/boot/image' $(INSTALL_DIR)/vmlinuz-$(REAL_VERSION)
@@ -404,7 +406,8 @@
install-image_hppa_$(FEATURESET)_$(FLAVOUR)_plain_templates \
install-image_mips_$(FEATURESET)_$(FLAVOUR)_plain_templates \
install-image_mipsel_$(FEATURESET)_$(FLAVOUR)_plain_templates \
-install-image_powerpc_$(FEATURESET)_$(FLAVOUR)_plain_templates: ARG_KIMAGE = vmlinux
+install-image_powerpc_$(FEATURESET)_$(FLAVOUR)_plain_templates \
+install-image_ppc64_$(FEATURESET)_$(FLAVOUR)_plain_templates: ARG_KIMAGE = vmlinux
install-image_$(ARCH)_$(FEATURESET)_$(FLAVOUR)_plain_templates:
for i in $(wildcard debian/templates/temp.image.plain/*); do \
signature.asc
Description: This is a digitally signed message part
Bug#619022: linux-image-2.6.38-1-686: Screen corruption with i855
On Sun, 2011-03-20 at 15:36 +0100, Cesare Leonardi wrote: On 20/03/2011 15:20, Ben Hutchings wrote: Please report this upstream onhttps://bugs.freedesktop.org, under product 'DRI', component 'DRM/Intel'. Let us know the bug URL so we can track it. bugs.freedesktop.org? So do you think it's a bug in X.org and not the kernel? No. But if i use 2.6.37, as now, the problem is not present. Shouldn't be reported to bugzilla.kernel.org? DRI bugs are tracked on bugs.fd.o, regardless of whether they are in the X, Mesa or kernel part of DRI. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#619022: linux-image-2.6.38-1-686: Screen corruption with i855
On Sun, Mar 20, 2011 at 15:36:33 +0100, Cesare Leonardi wrote: On 20/03/2011 15:20, Ben Hutchings wrote: Please report this upstream onhttps://bugs.freedesktop.org, under product 'DRI', component 'DRM/Intel'. Let us know the bug URL so we can track it. bugs.freedesktop.org? As in where the graphics bugs are tracked, for all pieces of the drivers. Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110320150437.gi12...@radis.liafa.jussieu.fr
Bug#619022: linux-image-2.6.38-1-686: Screen corruption with i855
On 20/03/2011 15:48, Ben Hutchings wrote: DRI bugs are tracked on bugs.fd.o, regardless of whether they are in the X, Mesa or kernel part of DRI. Didn't know. If you and Julien wouldn't had told me, i would have reported to bugzilla.kernel.org. Ok, so i've reported the bug to fdo and this is the report: https://bugs.freedesktop.org/show_bug.cgi?id=35466 And in the meantime Chris Wilson has already kindly replied and closed the bug. In his reply there are interesting infos (that perhaps you already know) on interaction between different version of kernel and driver. Thank you for your support. Cesare. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d86209c.9000...@gmail.com
Processed: closing 484861
Processing commands for cont...@bugs.debian.org: close 484861 Bug#484861: nfs-common: rpc.statd --outgoing-port (-o) option broken 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Richard A Nelson cow...@debian.org thanks Stopping processing here. Please contact me if you need assistance. -- 484861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=484861 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130063919721501.transcr...@bugs.debian.org
Processed: bug 600871 is not forwarded
Processing commands for cont...@bugs.debian.org: # can't find forwarded message notforwarded 600871 Bug #600871 [nfs-common] nfs-common: Very slow and unreliable performance of GUI(KDE) when /home nfs mounted Unset Bug forwarded-to-address thanks Stopping processing here. Please contact me if you need assistance. -- 600871: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600871 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130063931022050.transcr...@bugs.debian.org
Processed: bug 600871 is not forwarded
Processing commands for cont...@bugs.debian.org: # can't find forwarded message notforwarded 600871 Bug #600871 [nfs-common] nfs-common: Very slow and unreliable performance of GUI(KDE) when /home nfs mounted Ignoring request to change the forwarded-to-address of bug#600871 to the same value thanks Stopping processing here. Please contact me if you need assistance. -- 600871: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600871 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130063934022262.transcr...@bugs.debian.org
Bug#619034: linux-image-2.6.38-1-amd64: Problems with udev during boot
Package: linux-2.6 Version: 2.6.38-1 Severity: important During boot of kernel 2.6.38 (and 2.6.37) udev bugs out: Waiting for /dev to be fully populated BUG: Unable to handle kernel paging request at c90013cd8000 axz_probe+ ... [snd_hda_intel] ...lots of output lost... udevadm timeout 180 sec ... udevd[390]: worker [439] failed while handling '/devices/pci:80/:80:01.0' After the timeout the boot continues! Have not yet tested if sound is functional. -- Package-specific info: ** Version: Linux version 2.6.38-1-amd64 (Debian 2.6.38-1) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-14) ) #1 SMP Wed Mar 16 17:38:02 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.38-1-amd64 root=UUID=35609a38-a41d-458e-8ffe-30a00ec832f9 ro quiet ** Tainted: D (128) * Kernel has oopsed before. ** Kernel log: [4.298215] usbcore: registered new interface driver usblp [4.308027] [drm] nouveau :02:00.0: Parsing VBIOS init table 2 at offset 0xD14D [4.308038] [drm] nouveau :02:00.0: Parsing VBIOS init table 3 at offset 0xD23F [4.316095] [drm] nouveau :02:00.0: Parsing VBIOS init table 4 at offset 0xD472 [4.316097] [drm] nouveau :02:00.0: Parsing VBIOS init table at offset 0xD4D7 [4.340021] [drm] nouveau :02:00.0: 0xD4D7: Condition still not met after 20ms, skipping following opcodes [4.358708] [drm] nouveau :02:00.0: 1 available performance level(s) [4.358712] [drm] nouveau :02:00.0: 0: memory 700MHz core 540MHz shader 1188MHz fanspeed 100% [4.358729] [drm] nouveau :02:00.0: c: memory 300MHz core 540MHz shader 1188MHz voltage 1320mV [4.358763] nouveau :02:00.0: PCI: Disallowing DAC for device [4.358809] [TTM] Zone kernel: Available graphics memory: 1030220 kiB. [4.358811] [TTM] Initializing pool allocator. [4.358825] [drm] nouveau :02:00.0: Detected 256MiB VRAM [4.396824] [drm] nouveau :02:00.0: 512 MiB GART (aperture) [4.465612] [drm] nouveau :02:00.0: DCB encoder 1 unknown [4.465614] [drm] nouveau :02:00.0: TV-1 has no encoders, removing [4.466850] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [4.466852] [drm] No driver support for vblank timestamp query. [4.506919] parport_pc 00:0a: reported by Plug and Play ACPI [4.506967] parport0: PC-style at 0x378, irq 7 [PCSPP] [4.636513] input: ImPS/2 Logitech Wheel Mouse as /devices/platform/i8042/serio1/input/input4 [4.641977] [drm] nouveau :02:00.0: allocated 1920x1200 fb: 0x6000, bo 880036d3e800 [4.648564] Console: switching to colour frame buffer device 240x75 [4.650703] fb0: nouveaufb frame buffer device [4.650704] drm: registered panic notifier [4.650710] [drm] Initialized nouveau 0.0.16 20090420 for :02:00.0 on minor 0 [4.650952] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [4.896203] HDA Intel :80:01.0: PCI INT A - GSI 17 (level, low) - IRQ 17 [4.896263] HDA Intel :80:01.0: setting latency timer to 64 [4.896282] BUG: unable to handle kernel paging request at c90013cd8000 [4.896302] IP: [a0657416] azx_probe+0x3ad/0x870 [snd_hda_intel] [4.896320] PGD 7d019067 PUD 7d01a067 PMD 37154067 PTE 80fd0173 [4.896337] Oops: 0009 [#1] SMP [4.896346] last sysfs file: /sys/devices/virtual/net/lo/operstate [4.896357] CPU 0 [4.896361] Modules linked in: snd_hda_intel(+) snd_hda_codec snd_hwdep snd_pcm parport_pc tpm_tis snd_seq tpm snd_timer snd_seq_device tpm_bios snd usblp parport shpchp pci_hotplug nouveau ttm drm_kms_helper k8temp drm edac_core soundcore snd_page_alloc edac_mce_amd i2c_viapro i2c_algo_bit i2c_core power_supply evdev video pcspkr psmouse processor button serio_raw thermal_sys ext3 jbd mbcache sg usbhid sr_mod cdrom hid sd_mod crc_t10dif ata_generic pata_via uhci_hcd sata_via ehci_hcd libata usbcore scsi_mod via_rhine floppy mii nls_base [last unloaded: scsi_wait_scan] [4.896533] [4.896537] Pid: 605, comm: work_for_cpu Not tainted 2.6.38-1-amd64 #1 MICRO-STAR INTERNATIONAL CO., LTD MS-7253/MS-7253 [4.896558] RIP: 0010:[a0657416] [a0657416] azx_probe+0x3ad/0x870 [snd_hda_intel] [4.896574] RSP: 0018:88007a10de50 EFLAGS: 00010286 [4.896581] RAX: c90013cd8000 RBX: 88007a658400 RCX: 0006 [4.896588] RDX: RSI: 0246 RDI: 0246 [4.896596] RBP: 88007c93d000 R08: R09: 0040 [4.896604] R10: 0286 R11: a971 R12: 88007a65a800 [4.896612] R13: R14: R15: 88007c93d090 [4.896620] FS: 7f2fed2e37a0() GS:88007fc0() knlGS: [4.896629] CS: 0010 DS: ES: CR0: 8005003b [4.896635] CR2: c90013cd8000 CR3: 7c7ba000 CR4: 06f0 [4.896643] DR0: DR1: DR2: [
Processed: tagging 618930
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 618930 + pending Bug #618930 [linux-image-2.6.38-1-686] High network latency with ralink usb wireless device Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 618930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130064115328792.transcr...@bugs.debian.org
Bug#619034: linux-image-2.6.38-1-amd64: Problems with udev during boot
On Sun, 2011-03-20 at 18:10 +0100, Svante Signell wrote: Package: linux-2.6 Version: 2.6.38-1 Severity: important During boot of kernel 2.6.38 (and 2.6.37) udev bugs out: Waiting for /dev to be fully populated BUG: Unable to handle kernel paging request at c90013cd8000 axz_probe+ ... [snd_hda_intel] [...] So this is a problem with snd_hda_intel. Not udev. Please report this to alsa-de...@alsa-project.org and cc the bug address (619...@bugs.debian.org). You should include system information as described in http://alsa-project.org/main/index.php/Help_To_Debug. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#446238: nfs-common: Locks when using nfs4 sec=krb5 and user ticket expires
Hi Can you still reproduce this problem or can this old bug be closed? Cheers Luk -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d86384a.5070...@debian.org
Bug#617666: nfs-kernel-server: Periodic nfsd failure - single nfsd process with high CPU and no mounts working
On 10/03/11 12:54, Debian Bug Tracking System wrote: I have some extra information about this problem - the syslog contains some kernel error messages related to nfs and xfs (the filesystem of the /export partition). I have attached the relevant log section... It could be this is a problem with xfs or even with our hardware raid controller. I have rebooted the machine with /export unmounted and am currently running xfs_repair over it to see if that picks up any problems. Hi I guess your xfs_repair finished by now? Did it shed some more light on the issue or should we look more closely into the nfs code? Cheers Luk -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d86374f.5070...@debian.org
Bug#619019: xserver-xorg-video-intel: latest update to debian, squeeze made the mouse pointer invisible in my openbox/gdm session
Thanks for the replies. Yes, it is probably a kernel problem. And yes downgrading does fix it. LN2 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d863d14.1060...@gmail.com
Bug#619010: [Fwd: Re: Bug#619010: linux-image-2.6.38-1-686-bigmem: Fails to boot on lvm2/looks system]
Forwarded Message From: Volker Schlecht vschle...@gmx.net To: Ben Hutchings b...@decadent.org.uk Subject: Re: Bug#619010: linux-image-2.6.38-1-686-bigmem: Fails to boot on lvm2/looks system Date: Sun, 20 Mar 2011 18:42:14 +0100 Absolutely - I noticed the typo the second I sent the bugreport :-) - Ursprüngliche Nachricht - Von: Ben Hutchings Gesendet: 20.03.11 15:18 Uhr An: Volker Schlecht, 619...@bugs.debian.org Betreff: Re: Bug#619010: linux-image-2.6.38-1-686-bigmem: Fails to boot on lvm2/looks system On Sun, 2011-03-20 at 13:43 +0100, Volker Schlecht wrote: Package: linux-2.6 Version: 2.6.38-1 Severity: grave Justification: renders package unusable Booting a stock 686-bigmem 2.6.38 kernel hangs after loading the initrd with the message LVM no volumes found and evms_activate failed. [...] Do you mean 'LUKS' rather than 'looks'? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1300643867.26693.294.camel@localhost
Processed: reassign 619010 to cryptsetup
Processing commands for cont...@bugs.debian.org: reassign 619010 cryptsetup Bug #619010 [linux-2.6] linux-image-2.6.38-1-686-bigmem: Fails to boot on lvm2/looks system Bug reassigned from package 'linux-2.6' to 'cryptsetup'. Bug No longer marked as found in versions 2.6.38-1. thanks Stopping processing here. Please contact me if you need assistance. -- 619010: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13006438885726.transcr...@bugs.debian.org
Bug#562821: nfs-common: Fails to map user id's via idmapd
Hi statd should be started on both the client and the server if you want locking to work correctly. Have you enabled idmapd in /etc/default/nfs-common? Cheers Luk -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d86418b.1040...@debian.org
Processed: closing 611464
Processing commands for cont...@bugs.debian.org: close 611464 Bug#611464: nfs-common: Really could you make NFS client and server working in this distro ?? 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Patrick295767 patrick295...@gmail.com thanks Stopping processing here. Please contact me if you need assistance. -- 611464: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611464 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13006446588749.transcr...@bugs.debian.org
Bug#567546: NFS4: exports options are ignored for subdirs
Hi Can you still reproduce this with the version in squeeze/unstable? Cheers Luk -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d86420e.40...@debian.org
Processed: closing 500071
Processing commands for cont...@bugs.debian.org: close 500071 1:1.2.2-5 Bug#500071: nfs-common: shutdown nfs problems 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 1:1.2.2-5, send any further explanations to Csillag Tamas csta...@digitus.itk.ppke.hu thanks Stopping processing here. Please contact me if you need assistance. -- 500071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500071 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130064517310156.transcr...@bugs.debian.org
Processed: closing 511802
Processing commands for cont...@bugs.debian.org: close 511802 Bug#511802: nfs4 mounting with krb5.. does not work. 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Olaf Till olaf.t...@uni-jena.de thanks Stopping processing here. Please contact me if you need assistance. -- 511802: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511802 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130064572412063.transcr...@bugs.debian.org
Processed: closing 568771
Processing commands for cont...@bugs.debian.org: close 568771 Bug#568771: rpc.gssd: No credentials found 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Friedemann Stoyan fsto...@swapon.de thanks Stopping processing here. Please contact me if you need assistance. -- 568771: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568771 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130064650415433.transcr...@bugs.debian.org
Bug#568288: mount.nfs: mount(2): Invalid argument
Hi Mounting an nfs file system suddenly stopped working with errors like this: -- # mount.nfs exact:/ /mnt/exact -v mount.nfs: timeout set for Wed Feb 3 16:09:00 2010 mount.nfs: trying text-based options 'addr=192.168.0.5,vers=4,clientaddr=192.168.0.3' mount.nfs: mount(2): Invalid argument mount.nfs: an incorrect mount option was specified -- Both systems (that on which the mount was issued and the server) were running testing. They were, however using custom kernels, but these had worked without problems until today. Only the server was set up for nfs version 4 which seems to be the heart of the problem from the message about the text based options above - see below as well. I guess it's an old kernel? The problem was resolved by adding either -o nfsvers=2 or -o nfsvers-3 to the mount command. Thus there seems to be some sort of problem negotiating the nfs version between the client server? And a totally misleading error message? The default changed to version 4, but that does not work with old kernels, so I guess that's the problem? That would also explain the error message. Cheers Luk -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d864a2f@debian.org
Bug#572406: users Mount Option Broken
The users option got broken with the latest release, despite working correctly in 1:1.0.10-6+etch.1 (old stable). Non-root users can mount filesystems listed in /etc/fstab that have users specified, but they will be unable to unmount the filesystem (umount.nfs: You are not permitted to unmount ...). My first thought is someone confused the user (which would need to check who mounted the FS) and users option. Given bug report #501459, part of which sounds like a similar issue with cifs, I'm also wondering if the interface between `mount` and `mount.fstype` got changed slightly. Hi Does adding a trailing slash in /etc/fstab fix the issue for you? Cheers Luk -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d864b4f.1070...@debian.org
Processed: closing 609149
Processing commands for cont...@bugs.debian.org: close 609149 Bug#609149: nfs-kernel-server: after some time, the server nfs is not working, and no client can mount share 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to yellow yellowprot...@gmail.com thanks Stopping processing here. Please contact me if you need assistance. -- 609149: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609149 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130064758518916.transcr...@bugs.debian.org
Bug#590959: idmapd only working in one direction
I tried to set up nfsv4 between two lenny-installations where users have different UIDs. Server: User xyz has UID 1000 Client: User xyz has UID 501 What did you believe that when user xyz writes to the mounted directory it would not end up as belonging to UID 501 on the server? Cheers Luk -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d864dde.1090...@debian.org
Bug#619034: Problems with udev and snd_hda_intel for linux-kernel-2.6.38-1-amd64
See bug 619034 for more information. According to the /proc/asound/cards there are no sound cards. It works properly with 2.6.23-5-amd64 though (and earlier kernels). -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1300651506.4839.179.ca...@hp.my.own.domain
Bug#619051: linux-2.6: Missing Realtek 8188CE pcie wifi support (rtlwifi/rtl8192ce module not built)
Package: linux-2.6 Version: 2.6.38-1 Severity: wishlist Summary: Please enable the new rtlwifi/rtl8192ce drivers in the kernel build config. Full version: I'm sending this email from my wireless Thinkpad Edge using my own rebuild of the linux-image-2.6.38-1-amd64 package with just those two additional modules enabled and the firmware from the linux-firmware git repository in /lib/firmware/rtlwifi/rtl8192cfw.bin. My system runs Linux Mint Debian Edition, but it should apply to all Testing/Unstable systems with the Realtek 8188CE pcie wifi adapter and this kernel. I added the following lines to debian/config/config before building: ~/build diff -Naur config-default config-rtl8192ce --- config-default 2011-03-20 12:26:00.576309324 +0100 +++ config-rtl8192ce2011-03-20 12:40:51.117677926 +0100 @@ -1997,6 +1997,12 @@ CONFIG_RTL8187=m ## +## file: drivers/net/wireless/rtlwifi/Kconfig +## +CONFIG_RTL8192CE=m +CONFIG_RTLWIFI=m + +## ## file: drivers/net/wireless/wl1251/Kconfig ## CONFIG_WL1251=m Please also refer to #613536 for information about the corresponding firmware missing from the firmware-realtek package. Feel free to contact me for further information. Thanks in advance! Cheers, Jonas -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110320153807.6488.70249.reportbug@edge
Bug#619052: rpc.gssd: double free or corruption
Package: nfs-common Version: 1:1.2.2-5 Severity: important When installing nfs-common from sid I reccieve the following stacktrace at every start of the package: * Starting NFS common utilities * *** glibc detected *** /usr/sbin/rpc.gssd: double free or corruption * (!prev): 0x020910d0 *** === Backtrace: = /lib/libc.so.6(+0x71ab6)[0x7f7df3515ab6] /lib/libc.so.6(cfree+0x6c)[0x7f7df351a82c] /lib/libc.so.6(fclose+0x14d)[0x7f7df35069fd] /usr/lib/libgssglue.so.1(+0x46a0)[0x7f7df43426a0] /usr/lib/libgssglue.so.1(+0x47b7)[0x7f7df43427b7] /usr/lib/libgssglue.so.1(gss_indicate_mechs+0x2d)[0x7f7df434218d] /usr/sbin/rpc.gssd[0x403f4e] /usr/sbin/rpc.gssd[0x404368] /lib/libc.so.6(__libc_start_main+0xfd)[0x7f7df34c2c4d] /usr/sbin/rpc.gssd[0x4036f9] === Memory map: 0040-0040e000 r-xp fe:01 83370 /usr/sbin/rpc.gssd 0060e000-00612000 rw-p e000 fe:01 83370 /usr/sbin/rpc.gssd 00612000-00614000 rw-p 00:00 0 02091000-020b2000 rw-p 00:00 0 [heap] 7f7dec00-7f7dec021000 rw-p 00:00 0 7f7dec021000-7f7df000 ---p 00:00 0 7f7df2a52000-7f7df2a67000 r-xp 08:15 561944 /lib/libgcc_s.so.1 7f7df2a67000-7f7df2c67000 ---p 00015000 08:15 561944 /lib/libgcc_s.so.1 7f7df2c67000-7f7df2c68000 rw-p 00015000 08:15 561944 /lib/libgcc_s.so.1 7f7df2c68000-7f7df2c7f000 r-xp 08:15 562192 /lib/libpthread-2.11.2.so 7f7df2c7f000-7f7df2e7e000 ---p 00017000 08:15 562192 /lib/libpthread-2.11.2.so 7f7df2e7e000-7f7df2e7f000 r--p 00016000 08:15 562192 /lib/libpthread-2.11.2.so 7f7df2e7f000-7f7df2e8 rw-p 00017000 08:15 562192 /lib/libpthread-2.11.2.so 7f7df2e8-7f7df2e84000 rw-p 00:00 0 7f7df2e84000-7f7df2e97000 r-xp 08:15 561995 /lib/libresolv-2.11.2.so 7f7df2e97000-7f7df3096000 ---p 00013000 08:15 561995 /lib/libresolv-2.11.2.so 7f7df3096000-7f7df3097000 r--p 00012000 08:15 561995 /lib/libresolv-2.11.2.so 7f7df3097000-7f7df3098000 rw-p 00013000 08:15 561995 /lib/libresolv-2.11.2.so 7f7df3098000-7f7df309a000 rw-p 00:00 0 7f7df309a000-7f7df309c000 r-xp 08:15 561964 /lib/libkeyutils.so.1.3 7f7df309c000-7f7df329b000 ---p 2000 08:15 561964 /lib/libkeyutils.so.1.3 7f7df329b000-7f7df329c000 rw-p 1000 08:15 561964 /lib/libkeyutils.so.1.3 7f7df329c000-7f7df32a3000 r-xp fe:01 50300 /usr/lib/libkrb5support.so.0.1 7f7df32a3000-7f7df34a3000 ---p 7000 fe:01 50300 /usr/lib/libkrb5support.so.0.1 7f7df34a3000-7f7df34a4000 rw-p 7000 fe:01 50300 /usr/lib/libkrb5support.so.0.1 7f7df34a4000-7f7df35fc000 r-xp 08:15 562191 /lib/libc-2.11.2.so 7f7df35fc000-7f7df37fc000 ---p 00158000 08:15 562191 /lib/libc-2.11.2.so 7f7df37fc000-7f7df380 r--p 00158000 08:15 562191 /lib/libc-2.11.2.so 7f7df380-7f7df3801000 rw-p 0015c000 08:15 562191 /lib/libc-2.11.2.so 7f7df3801000-7f7df3806000 rw-p 00:00 0 7f7df3806000-7f7df3809000 r-xp 08:15 562017 /lib/libcom_err.so.2.1 7f7df3809000-7f7df3a08000 ---p 3000 08:15 562017 /lib/libcom_err.so.2.1 7f7df3a08000-7f7df3a09000 rw-p 2000 08:15 562017 /lib/libcom_err.so.2.1 7f7df3a09000-7f7df3a31000 r-xp fe:01 49582 /usr/lib/libk5crypto.so.3.1 7f7df3a31000-7f7df3c3 ---p 00028000 fe:01 49582 /usr/lib/libk5crypto.so.3.1 7f7df3c3-7f7df3c32000 rw-p 00027000 fe:01 49582 /usr/lib/libk5crypto.so.3.1 7f7df3c32000-7f7df3cf4000 r-xp fe:01 49613 /usr/lib/libkrb5.so.3.3 7f7df3cf4000-7f7df3ef3000 ---p 000c2000 fe:01 49613 /usr/lib/libkrb5.so.3.3 7f7df3ef3000-7f7df3efe000 rw-p 000c1000 fe:01 49613 /usr/lib/libkrb5.so.3.3 7f7df3efe000-7f7df3f38000 r-xp fe:01 49585 /usr/lib/libgssapi_krb5.so.2.2 7f7df3f38000-7f7df4137000 ---p 0003a000 fe:01 49585 /usr/lib/libgssapi_krb5.so.2.2 7f7df4137000-7f7df413a000 rw-p 00039000 fe:01 49585 /usr/lib/libgssapi_krb5.so.2.2 7f7df413a000-7f7df413c000 r-xp 08:15 562187 /lib/libdl-2.11.2.so 7f7df413c000-7f7df433c000 ---p 2000 08:15 562187 /lib/libdl-2.11.2.so 7f7df433c000-7f7df433d000 r--p 2000 08:15 562187 /lib/libdl-2.11.2.so 7f7df433d000-7f7df433e000 rw-p 3000 08:15 562187 /lib/libdl-2.11.2.so 7f7df433e000-7f7df4347000 r-xp fe:01 50870 /usr/lib/libgssglue.so.1.0.0 7f7df4347000-7f7df4546000 ---p 9000 fe:01 50870 /usr/lib/libgssglue.so.1.0.0 7f7df4546000-7f7df4547000 rw-p 8000 fe:01 50870 /usr/lib/libgssglue.so.1.0.0 7f7df4547000-7f7df4556000 r-xp fe:01 58365 /usr/lib/librpcsecgss.so.3.0.0 7f7df4556000-7f7df4755000 ---p f000 fe:01 58365 /usr/lib/librpcsecgss.so.3.0.0 7f7df4755000-7f7df4756000 rw-p e000 fe:01 58365 /usr/lib/librpcsecgss.so.3.0.0 7f7df4756000-7f7df4774000 r-xp 08:15 562300 /lib/ld-2.11.2.so 7f7df494a000-7f7df4951000 rw-p 00:00 0 7f7df4971000-7f7df4973000 rw-p 00:00 0 7f7df4973000-7f7df4974000 r--p 0001d000 08:15 562300 /lib/ld-2.11.2.so 7f7df4974000-7f7df4975000 rw-p
Bug#590959: idmapd only working in one direction
On 2011-03-20 19:56, Luk Claes wrote: I tried to set up nfsv4 between two lenny-installations where users have different UIDs. Server: User xyz has UID 1000 Client: User xyz has UID 501 What did you believe that when user xyz writes to the mounted directory it would not end up as belonging to UID 501 on the server? I expect the server to convert it to UID 1000. In consequence during the next access it would be remapped to UID 501 on the server. What else is the concept of idmapd? Cheers, Armin Email secured by Check Point -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d86648f.8010...@beko.at
Bug#613534: Seems to be rather a bug in nvidia, not the kernel
reassign 613536 retitle 613536 Some special keys don't work with nvidia + newer kernel thanks On Ma, 15 feb 11, 16:13:31, Andrei POPESCU wrote: The ThinkVantage button is not producing any reaction at all in xev. This worked fine until now, including on 2.6.36-trunk-amd64. Any other things to try that might help you? Further experiments show that this bug happens only with nvidia and kernel 2.6.37 or newer, it does not happen with nouveau. I tried to test on squeeze (older Xorg), but the kernel module won't compile on 2.6.38 from unstable. acpi_listen is silent as long as I'm in X, but will react to key presses even if I only switch to the console with Ctrl+Alt+F1. Please ask if you need more info, this bug is very annoying for me. Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Processed (with 1 errors): Seems to be rather a bug in nvidia, not the kernel
Processing commands for cont...@bugs.debian.org: reassign 613536 Unknown command or malformed arguments to command. retitle 613536 Some special keys don't work with nvidia + newer kernel Bug #613536 [firmware-realtek] firmware-realtek: Please include the binary firmware for Realtek RTL8188CE Changed Bug title to 'Some special keys don't work with nvidia + newer kernel' from 'firmware-realtek: Please include the binary firmware for Realtek RTL8188CE' thanks Stopping processing here. Please contact me if you need assistance. -- 613536: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613536 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130065788521544.transcr...@bugs.debian.org
Bug#568288: mount.nfs: mount(2): Invalid argument
On Sun, Mar 20, 2011 at 07:40:47PM +0100, Luk Claes wrote: Hi Mounting an nfs file system suddenly stopped working with errors like this: -- # mount.nfs exact:/ /mnt/exact -v mount.nfs: timeout set for Wed Feb 3 16:09:00 2010 mount.nfs: trying text-based options 'addr=192.168.0.5,vers=4,clientaddr=192.168.0.3' mount.nfs: mount(2): Invalid argument mount.nfs: an incorrect mount option was specified -- Both systems (that on which the mount was issued and the server) were running testing. They were, however using custom kernels, but these had worked without problems until today. Only the server was set up for nfs version 4 which seems to be the heart of the problem from the message about the text based options above - see below as well. I guess it's an old kernel? Actually, no. I either run the current Debian kernel, or the latest from stable-git, compiled locally, of course. The problem was resolved by adding either -o nfsvers=2 or -o nfsvers-3 to the mount command. Thus there seems to be some sort of problem negotiating the nfs version between the client server? And a totally misleading error message? The default changed to version 4, but that does not work with old kernels, so I guess that's the problem? I don't think it can be: I was running kernel.org kernels, later then Debian testing. I can't remember what version I was at when I reported the bug: I confess that I had forgotten about the report. Maybe I had something wrong in the kernel configs, but I doubt it. As noted above, I only had version 4 configured in one of them: might that have upset the negotiation/default somehow? ael -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110320221117.GA3806@precise.conquest
Processed: Re: Processed (with 1 errors): Seems to be rather a bug in nvidia, not the kernel
Processing commands for cont...@bugs.debian.org: retitle 613536 firmware-realtek: Please include the binary firmware for Realtek RTL8188CE Bug #613536 [firmware-realtek] Some special keys don't work with nvidia + newer kernel Changed Bug title to 'firmware-realtek: Please include the binary firmware for Realtek RTL8188CE' from 'Some special keys don't work with nvidia + newer kernel' thanks Stopping processing here. Please contact me if you need assistance. -- 613536: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613536 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130065919226660.transcr...@bugs.debian.org
Processed: really reassign :(
Processing commands for cont...@bugs.debian.org: reassign 613534 nvidia-glx Bug #613534 [linux-2.6] Some special keys don't work with nvidia + newer kernel Bug reassigned from package 'linux-2.6' to 'nvidia-glx'. Bug No longer marked as found in versions 2.6.37-1 and 2.6.37-1~experimental.1. thanks Stopping processing here. Please contact me if you need assistance. -- 613534: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130065956127992.transcr...@bugs.debian.org
Bug#619070: linux-image-2.6.38-1-amd64: Please enable CONFIG_B43_PHY_N (no longer BROKEN)
Package: linux-2.6 Version: 2.6.38-1 Severity: wishlist Hello, now that 2.6.38 is out, it would be nice to enable the CONFIG_B43_PHY_N option which is no longer marked as BROKEN. This will allow people like me with a Broadcom BCM4322 (14e4:4322 and 14e4:432b) to use the in-kernel b43 driver instead of the proprietary wl driver. I tested it and it works very well, with two caveats: - the rate seems to be limited to 11M at present - I had to patch b43-fwcutter to be able to extract the necessary firmware Nevertheless, it seems to work better in a lot of ways, so it would be nice to have the option. Thanks, -- Mourad DC -- Package-specific info: ** Kernel log: boot messages should be attached Mar 20 05:47:33 kernel: [ 1431.121689] b43-phy2: Broadcom 4322 WLAN found (core revision 16) Mar 20 05:47:33 kernel: [ 1431.191148] Registered led device: b43-phy2::tx Mar 20 05:47:33 kernel: [ 1431.193662] Registered led device: b43-phy2::rx Mar 20 05:47:33 kernel: [ 1431.193752] Registered led device: b43-phy2::radio Mar 20 05:47:33 kernel: [ 1431.436202] b43-phy2: Loading firmware version 508.1084 (2009-01-14 01:32:01) ** Model information sys_vendor: Apple Inc. product_name: MacBookPro7,1 product_version: 1.0 chassis_vendor: Apple Inc. chassis_version: Mac-F222BEC8 bios_vendor: Apple Inc. bios_version:MBP71.88Z.0039.B0B.1006012305 board_vendor: Apple Inc. board_name: Mac-F222BEC8 board_version: ** PCI devices: 00:00.0 Host bridge [0600]: nVidia Corporation MCP89 HOST Bridge [10de:0d60] (rev a1) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 00:00.1 RAM memory [0500]: nVidia Corporation MCP89 Memory Controller [10de:0d68] (rev a1) Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 00:01.0 RAM memory [0500]: nVidia Corporation Device [10de:0d6d] (rev a1) Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- 00:01.1 RAM memory [0500]: nVidia Corporation Device [10de:0d6e] (rev a1) Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- 00:01.2 RAM memory [0500]: nVidia Corporation Device [10de:0d6f] (rev a1) Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- 00:01.3 RAM memory [0500]: nVidia Corporation Device [10de:0d70] (rev a1) Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- 00:02.0 RAM memory [0500]: nVidia Corporation Device [10de:0d71] (rev a1) Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- 00:02.1 RAM memory [0500]: nVidia Corporation Device [10de:0d72] (rev a1) Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- 00:03.0 ISA bridge [0601]: nVidia Corporation MCP89 LPC Bridge [10de:0d80] (rev a2) Subsystem: Apple Computer Inc. Device [106b:cb89] Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Region 0: I/O ports at 2100 [size=256] 00:03.1 RAM memory [0500]: nVidia Corporation MCP89 Memory Controller [10de:0d7b] (rev a1) Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- 00:03.2 SMBus [0c05]: nVidia Corporation MCP89 SMBus [10de:0d79] (rev a1) Subsystem: nVidia Corporation Device [10de:cb89] Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Interrupt: pin A routed to IRQ 15 Region 0: I/O ports at 2000
Bug#568288: mount.nfs: mount(2): Invalid argument
On 03/20/2011 11:11 PM, ael wrote: On Sun, Mar 20, 2011 at 07:40:47PM +0100, Luk Claes wrote: Hi Mounting an nfs file system suddenly stopped working with errors like this: -- # mount.nfs exact:/ /mnt/exact -v mount.nfs: timeout set for Wed Feb 3 16:09:00 2010 mount.nfs: trying text-based options 'addr=192.168.0.5,vers=4,clientaddr=192.168.0.3' mount.nfs: mount(2): Invalid argument mount.nfs: an incorrect mount option was specified -- Both systems (that on which the mount was issued and the server) were running testing. They were, however using custom kernels, but these had worked without problems until today. Only the server was set up for nfs version 4 which seems to be the heart of the problem from the message about the text based options above - see below as well. I guess it's an old kernel? Actually, no. I either run the current Debian kernel, or the latest from stable-git, compiled locally, of course. The problem was resolved by adding either -o nfsvers=2 or -o nfsvers-3 to the mount command. Thus there seems to be some sort of problem negotiating the nfs version between the client server? And a totally misleading error message? The default changed to version 4, but that does not work with old kernels, so I guess that's the problem? I don't think it can be: I was running kernel.org kernels, later then Debian testing. I can't remember what version I was at when I reported the bug: I confess that I had forgotten about the report. Maybe I had something wrong in the kernel configs, but I doubt it. As noted above, I only had version 4 configured in one of them: might that have upset the negotiation/default somehow? It might if the export was not configured to be for NFSv4 (with an fsid=0 entry etc). Another possibility is a bug in an older version of the Debian package or using an older kernel at the other end AFAICS. Can you still reproduce this issue or are you fine with me closing this bug? Cheers Luk -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d868080.2060...@debian.org
Bug#590959: marked as done (idmapd only working in one direction)
Your message dated Sun, 20 Mar 2011 23:24:51 +0100 with message-id 4d867eb3.3090...@debian.org and subject line Re: Bug#590959: idmapd only working in one direction has caused the Debian Bug report #590959, regarding idmapd only working in one direction 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.) -- 590959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590959 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nfs-common Version: 1:1.1.2-6lenny2 I tried to set up nfsv4 between two lenny-installations where users have different UIDs. Server: User xyz has UID 1000 Client: User xyz has UID 501 /etc/exports (server) contains: /exports with options: rw,fsid=0,insecure,no_subtree_check,sync /exports/home with optione: rw,nohide,insecure,no_subtree_check,sync /etc/default/nfs-common (server+client) NEED_STATD=no STATDOPTS= NEED_IDMAPD=yes NEED_GSSD= /etc/idmapd.conf is identical on server+client mount server:/home /mnt/ -t nfs4 ls -l /mnt translates user and group properly. touch /mnt/xxx creates a file with UID 501 on the server / should be UID 1000 ---End Message--- ---BeginMessage--- On 03/20/2011 09:33 PM, Armin Fuerst wrote: On 2011-03-20 19:56, Luk Claes wrote: I tried to set up nfsv4 between two lenny-installations where users have different UIDs. Server: User xyz has UID 1000 Client: User xyz has UID 501 What did you believe that when user xyz writes to the mounted directory it would not end up as belonging to UID 501 on the server? I expect the server to convert it to UID 1000. In consequence during the next access it would be remapped to UID 501 on the server. What else is the concept of idmapd? It's to map NFSv4 names (of the form user@domain) to local uids and gids and vice versa. So I'm closing this bug as it seems to be a misunderstanding of what idmap is meant for. Cheers Luk ---End Message---
Bug#619019: [PATCH 1/2] i915: Remove 'pipe A force' quirk for 855GM and 845G
Applying this quirk to the 855GM in all systems causes regressions
(Debian bugs #493096, #619019). Instead, apply the quirk to specific
models as listed in the old X driver.
I don't see any explanation for this quirk being applied to the 845G,
except perhaps that VT switching used to hang if pipe A was turned
off. However, that seems to be a problem only when using UMS. So
remove the quirk for the 845G as well.
Signed-off-by: Ben Hutchings b...@decadent.org.uk
---
Needs people to test it, as I can't.
Ben.
drivers/gpu/drm/i915/intel_display.c | 23 +++
1 files changed, 19 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_display.c
b/drivers/gpu/drm/i915/intel_display.c
index 3106c0d..a490f75 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -7345,19 +7345,34 @@ struct intel_quirk intel_quirks[] = {
/* Thinkpad R31 needs pipe A force quirk */
{ 0x3577, 0x1014, 0x0505, quirk_pipea_force },
+ /* Dell Latitude D400 needs pipe A force quirk (LP: #228519) */
+ { 0x3582, 0x1028, 0x0139, quirk_pipea_force },
+ /* Dell Latitude D500 needs pipe A force quirk */
+ { 0x3582, 0x1028, 0x0152, quirk_pipea_force },
+ /* Dell Latitude D505 needs pipe A force quirk (LP: #235643) */
+ { 0x3582, 0x1028, 0x0163, quirk_pipea_force },
+ /* Dell Latitude X300 needs pipe A force quirk */
+ { 0x3582, 0x1028, 0x014f, quirk_pipea_force },
+ /* Dell Inspiron 510m needs pipe A force quirk */
+ { 0x3582, 0x1028, 0x0164, quirk_pipea_force },
+ /* Toshiba Satellite A30 needs pipe A force quirk */
+ { 0x3582, 0x1179, 0xff00, quirk_pipea_force },
/* Toshiba Protege R-205, S-209 needs pipe A force quirk */
{ 0x2592, 0x1179, 0x0001, quirk_pipea_force },
+ /* Intel 855GM hardware (See LP: #216490) */
+ { 0x3582, 0x1028, 0x00c8, quirk_pipea_force },
+ /* Intel 855GM hardware (See Novell Bugzilla #406123) */
+ { 0x3582, 0x10cf, 0x1215, quirk_pipea_force },
+ /* HP Pavilion ze4944ea needs pipe A force quirk (See LP: #242389) */
+ { 0x3582, 0x103c, 0x3084, quirk_pipea_force },
/* ThinkPad X30 needs pipe A force quirk (LP: #304614) */
{ 0x3577, 0x1014, 0x0513, quirk_pipea_force },
/* ThinkPad X40 needs pipe A force quirk */
+ { 0x3582, 0x1014, 0x0557, quirk_pipea_force },
/* ThinkPad T60 needs pipe A force quirk (bug #16494) */
{ 0x2782, 0x17aa, 0x201a, quirk_pipea_force },
-
- /* 855 before need to leave pipe A dpll A up */
- { 0x3582, PCI_ANY_ID, PCI_ANY_ID, quirk_pipea_force },
- { 0x2562, PCI_ANY_ID, PCI_ANY_ID, quirk_pipea_force },
};
static void intel_init_quirks(struct drm_device *dev)
--
1.7.4.1
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1300662425.26693.301.camel@localhost
Processed: tagging 619070
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 619070 + pending Bug #619070 [linux-2.6] linux-image-2.6.38-1-amd64: Please enable CONFIG_B43_PHY_N (no longer BROKEN) Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 619070: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619070 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13006722748504.transcr...@bugs.debian.org
Processed: tagging 619051
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 619051 + pending Bug #619051 [linux-2.6] linux-2.6: Missing Realtek 8188CE pcie wifi support (rtlwifi/rtl8192ce module not built) Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 619051: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619051 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130067314310384.transcr...@bugs.debian.org
Bug#617488: [linux-2.6] No input device for IR remote on Pinnacle PCTV 110i (saa7133) video board
On Sat, 2011-03-19 at 13:09 +0500, Alex Volkov wrote: Version 2.6.38-1 seems to have the same issue. Slightly modifed patch follows: Thanks for the patch, but I am not qualified to review this change myself. Please can you submit it upstream first, with the explanation and the proper sign-off (see Documentation/SubmittingPatches)? You should send mail to Mauro Carvalho Chehab mche...@infradead.org and cc David Hardeman da...@hardeman.nu, linux-me...@vger.kernel.org, 617...@bugs.debian.org. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#618847: linux-image-2.6.38-1-amd64: Does not boot with KMS enabled (Radeon Mobility HD 3650)
On Fri, 2011-03-18 at 18:17 -0400, John Lindgren wrote: Package: linux-2.6 Version: 2.6.38-1 Severity: important Updated to Linux kernel 2.6.38-1 today. System is a Toshiba Satellite A305-S6916 with an ATI Radeon Mobility HD 3650 in it. Using open source radeon driver. Works fine with KMS enabled and kernel 2.6.37-2. With 2.6.38-1, shows a black screen and stops when trying to set the video mode. Video of the boot messages, as reportbug suggested: http://www.box.net/shared/pr2dptkrf7 [...] Please report this upstream at https://bugs.freedesktop.org, under product 'DRI', component 'DRM/Radeon'. Let us know the bug URL so we can track it. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#619052: Reproducible, related to libgssglue1
I can reproduce this bug (i386 sid 2.6.31.13). The system mounts homes from kerberized nfs, so this bug makes it unusable. The bug can be worked around by downgrading libgssglue1 from 0.2-1 to 0.1-4 from testing.
Bug#599615:
Also seeing the exact same thing on two newly installed squeeze boxes. Both hit this bug on reboot. (raid10 md+xen+drbd backends) -- Marcus Furlong -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTi=k9mv5ycolezjaxpzqa4eum-uu3-a2eqc+t...@mail.gmail.com
Processing of tgt_1.0.4-2squeeze1_i386.changes
tgt_1.0.4-2squeeze1_i386.changes uploaded successfully to ftp-master.debian.org along with the files: tgt_1.0.4-2squeeze1_i386.deb Greetings, Your Debian queue daemon (running on host ravel.debian.org) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1q1xk4-00052h...@ravel.debian.org
Processing of tgt_1.0.4-2squeeze1_i386.changes
tgt_1.0.4-2squeeze1_i386.changes uploaded successfully to localhost along with the files: tgt_1.0.4-2squeeze1_i386.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1q1xkp-00021h...@franck.debian.org
Processed: Re: linux-image-2.6.38-1-amd64: Does not boot with KMS enabled (Radeon Mobility HD 3650)
Processing commands for cont...@bugs.debian.org: forwarded 618847 http://marc.info/?l=linux-fbdevm=130068605804870 Bug #618847 [linux-2.6] linux-image-2.6.38-1-amd64: Does not boot with KMS enabled (Radeon Mobility HD 3650) Set Bug forwarded-to-address to 'http://marc.info/?l=linux-fbdevm=130068605804870'. thanks Stopping processing here. Please contact me if you need assistance. -- 618847: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618847 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130068653317109.transcr...@bugs.debian.org
