Bug#590105: Buffalo LS-CHL not supported yet
Hello, I'm sorry to tell that the bug is still there. I have just test the new installer from http://http.us.debian.org/debian/dists/stable/main/installer-armel/current/images/orion5x/network-console/buffalo/lspro/ . The same things happened as when I previously opened the bug (SATA link down in dmesg). Did I miss something or can we reopen the bug ? thanks
Bug#590105: Buffalo LS-CHL not supported yet
* Sébastien LALLEMAND sebastien.lallem...@gmail.com [2011-04-03 08:44]: The same things happened as when I previously opened the bug (SATA link down in dmesg). Did I miss something or can we reopen the bug ? It's supported in the kernel now. It's not supported in the installer yet (there are open bugs for this already). -- Martin Michlmayr http://www.cyrius.com/ -- 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/20110403073829.gn6...@jirafa.cyrius.com
Bug#597489: Kswapd hanging: patch available from lkml
On Sun, 2011-04-03 at 05:43 +0100, Ben Hutchings wrote: I really don't think that deals with the same bug you are seeing. Since now I have a test case for the problem, I'll compile 2.6.38.2 and try to see if recent modifications to MM do help in our situation, or if something else is causing the kernel hang (maybe nfs3 client, as Matteo was suggesting?) Perhaps, if Mel or one of the upstream developers does it. I don't believe anyone in the Debian kernel team is sufficiently familiar with the VMM to backport this significant change. Yes, I took a shot at applying the patch by myself but it wouldn't be anybody's cup of tea. MM has radically changed since 2.6.32 Please provide the full log messages for this error. If the messages seem to be produced continually then send all messages produced in 1 second (the numbers on the left are time in seconds). The messages are produced at 60 seconds interval. Sorry for the bad stack trace in the first posting, I hope the full 1-minute stack trace in my second posting was enough. I'll keep you posted with results of my tests, so that anyone else running in the same problem can follow my steps, in case. G. -- Giuseppe Lavagetto, Ph.d. Systems Manager and Developer - Gruppo Immobiliare.it s.r.l. -- 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/1301817049.5670.318.camel@bunny
Re: Stable update of linux-2.6
* dann frazier da...@dannf.org [2011-04-02 11:23:03]:
2.6.32.36 also fails to build on powerpc/SMP:
CC arch/powerpc/kernel/crash.o
arch/powerpc/kernel/crash.c: In function 'crash_kexec_wait_realmode':
arch/powerpc/kernel/crash.c:176: error: 'paca' undeclared (first use in this
function)
arch/powerpc/kernel/crash.c:176: error: (Each undeclared identifier is
reported only once
arch/powerpc/kernel/crash.c:176: error: for each function it appears in.)
make[1]: *** [arch/powerpc/kernel/crash.o] Error 1
make: *** [arch/powerpc/kernel] Error 2
Hi Dann,
Can you please try the following patch, which adds the changes
introduced by Kumar Gala to the commit b3df895aeb to my previous patch.
powerpc: Fix default_machine_crash_shutdown #ifdef build failure
Introducing #ifdef to fix the build failure caused by
crash_kexec_wait_realmode(), with powerpc build with !SMP.
Reported-by: Ben Hutchings b...@decadent.org.uk
Reported-by: dann frazier da...@dannf.org
Signed-off-by: Kamalesh Babulal kamal...@linux.vnet.ibm.com
cc: Paul E. McKenney paul...@linux.vnet.ibm.com
cc: Michael Neuling mi...@neuling.org
cc: Benjamin Herrenschmidt b...@kernel.crashing.org
cc: Anton Blanchard an...@samba.org
cc: Kumar Gala ga...@kernel.crashing.org
--
arch/powerpc/kernel/crash.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/kernel/crash.c b/arch/powerpc/kernel/crash.c
index fe02e71..175d1a7 100644
--- a/arch/powerpc/kernel/crash.c
+++ b/arch/powerpc/kernel/crash.c
@@ -163,6 +163,7 @@ static void crash_kexec_prepare_cpus(int cpu)
}
/* wait for all the CPUs to hit real mode but timeout if they don't come in */
+#ifdef CONFIG_PPC_STD_MMU_64
static void crash_kexec_wait_realmode(int cpu)
{
unsigned int msecs;
@@ -187,6 +188,7 @@ static void crash_kexec_wait_realmode(int cpu)
}
mb();
}
+#endif
/*
* This function will be called by secondary cpus or by kexec cpu
@@ -445,7 +447,9 @@ void default_machine_crash_shutdown(struct pt_regs *regs)
crash_kexec_prepare_cpus(crashing_cpu);
cpu_set(crashing_cpu, cpus_in_crash);
crash_kexec_stop_spus();
+#if defined(CONFIG_PPC_STD_MMU_64) defined(CONFIG_SMP)
crash_kexec_wait_realmode(crashing_cpu);
+#endif
if (ppc_md.kexec_cpu_down)
ppc_md.kexec_cpu_down(1, 0);
}
Kamalesh
--
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/20110403075103.gb4...@linux.vnet.ibm.com
Bug#620652: linux-image-2.6.38-2-686-bigmem: fails to disable error beep
Package: linux-2.6 Version: 2.6.38-2 Severity: normal Tags: sid Usually as a last resort removing the pc speaker modules pcspkr and snd_pscp effectively disables the error beep. Not with this kernel. In the according directories I removed `pcspkr.ko` and `snd_pcsp.ko`, then executed `depmod -a`, then built initird with: update-initramfs -u -k all. Nevertheless the beep on error is still there... -- Package-specific info: ** Version: Linux version 2.6.38-2-686-bigmem (Debian 2.6.38-2) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-14) ) #1 SMP Tue Mar 29 18:09:13 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.38-2-686-bigmem root=/dev/mapper/argon-root ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [ 14.002820] ext3_orphan_cleanup: deleting unreferenced inode 26983 [ 14.002840] ext3_orphan_cleanup: deleting unreferenced inode 26982 [ 14.002846] ext3_orphan_cleanup: deleting unreferenced inode 26981 [ 14.002859] ext3_orphan_cleanup: deleting unreferenced inode 26980 [ 14.002867] EXT3-fs (dm-1): 4 orphan inodes deleted [ 14.002869] EXT3-fs (dm-1): recovery complete [ 14.019147] EXT3-fs (dm-1): mounted filesystem with ordered data mode [ 15.783843] udev[387]: starting version 166 [ 16.117114] ACPI: acpi_idle registered with cpuidle [ 16.119366] Monitor-Mwait will be used to enter C-1 state [ 16.119397] Monitor-Mwait will be used to enter C-2 state [ 16.119402] Marking TSC unstable due to TSC halts in idle [ 16.120636] Switching to clocksource hpet [ 16.367628] input: Ideapad extra buttons as /devices/platform/ideapad/input/input4 [ 16.371209] input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input5 [ 16.396031] ACPI: Lid Switch [LID0] [ 16.396107] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input6 [ 16.396168] ACPI: Power Button [PWRB] [ 16.396231] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input7 [ 16.396269] ACPI: Sleep Button [SLPB] [ 16.396339] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input8 [ 16.396374] ACPI: Power Button [PWRF] [ 16.721254] i801_smbus :00:1f.3: PCI INT C - GSI 19 (level, low) - IRQ 19 [ 16.721260] ACPI: resource :00:1f.3 [io 0x1c00-0x1c1f] conflicts with ACPI region SMBI [io 0x1c00-0x1c0f] [ 16.721263] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 16.807884] [drm] Initialized drm 1.1.0 20060810 [ 16.874109] ACPI: AC Adapter [ACAD] (on-line) [ 17.382353] Linux video capture interface: v2.00 [ 17.463368] ACPI: Battery Slot [BAT1] (battery present) [ 17.504494] uvcvideo: Found UVC 1.00 device Lenovo EasyCamera (064e:a127) [ 17.547767] input: Lenovo EasyCamera as /devices/pci:00/:00:1d.7/usb2/2-3/2-3:1.0/input/input9 [ 17.547845] usbcore: registered new interface driver uvcvideo [ 17.547847] USB Video Class driver (v1.0.0) [ 17.600722] input: PS/2 Mouse as /devices/platform/i8042/serio1/input/input10 [ 17.664668] input: AlpsPS/2 ALPS GlidePoint as /devices/platform/i8042/serio1/input/input11 [ 17.734412] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 17.734417] i915 :00:02.0: setting latency timer to 64 [ 17.773100] i915 :00:02.0: irq 46 for MSI/MSI-X [ 17.773106] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 17.773108] [drm] Driver supports precise vblank timestamp query. [ 17.857757] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 17.858085] fixme: max PWM is zero. [ 17.972152] Console: switching to colour frame buffer device 170x48 [ 17.976165] fb0: inteldrmfb frame buffer device [ 17.976166] drm: registered panic notifier [ 17.979330] acpi device:08: registered as cooling_device2 [ 17.979598] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/input/input12 [ 17.979713] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [ 17.979960] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [ 17.980068] HDA Intel :00:1b.0: power state changed by ACPI to D0 [ 17.980073] HDA Intel :00:1b.0: power state changed by ACPI to D0 [ 17.980088] HDA Intel :00:1b.0: PCI INT A - GSI 22 (level, low) - IRQ 22 [ 17.980165] HDA Intel :00:1b.0: irq 47 for MSI/MSI-X [ 17.980197] HDA Intel :00:1b.0: setting latency timer to 64 [ 18.175066] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input13 [ 18.176621] input: HDA Intel Mic as /devices/pci:00/:00:1b.0/sound/card0/input14 [ 18.176715] input: HDA Intel Mic as /devices/pci:00/:00:1b.0/sound/card0/input15 [ 18.176793] input: HDA Intel Headphone as /devices/pci:00/:00:1b.0/sound/card0/input16 [ 19.107854] EXT3-fs (dm-1): using internal journal [ 19.327407] loop: module loaded [ 19.819845] Adding 5963772k swap
Bug#562737: seems to be back
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 With the upgrade to nfs-common 1:1.2.3-1 this problem seems to be back. Using rpcbind instead of portmap (6.0.0-3) nfs-common starts cleanly. nfs-common version 1:1.2.2-5 + portmap didn't show this problem either. rpc.statd -dF shows (using portmap): rpc.statd: Version 1.2.3 starting rpc.statd: Flags: No-Daemon Log-STDERR TI-RPC sm-notify: Version 1.2.3 starting sm-notify: Already notifying clients; Exiting! rpc.statd: Local NSM state number: 3 rpc.statd: Failed to unregister program 100024, version 1 rpc.statd: Effective UID, GID: 101, 0 rpc.statd: Failed to register (statd, 1, udp) rpc.statd: Failed to register (statd, 1, tcp) rpc.statd: Failed to register (statd, 1, udp6) rpc.statd: Failed to register (statd, 1, tcp6) rpc.statd: failed to create RPC listeners, exiting rpc.statd -dF shows (using rpcbind): rpc.statd: Version 1.2.3 starting rpc.statd: Flags: No-Daemon Log-STDERR TI-RPC sm-notify: Version 1.2.3 starting sm-notify: Already notifying clients; Exiting! rpc.statd: Local NSM state number: 3 rpc.statd: Effective UID, GID: 101, 0 rpc.statd: Waiting for client connections The old rpc.statd -dF (version 1:1.2.2-5) shows together with portmap: rpc.statd: Version 1.2.2 starting rpc.statd: Flags: No-Daemon Log-STDERR sm-notify: Version 1.2.2 starting sm-notify: Already notifying clients; Exiting! rpc.statd: Local NSM state number: 3 rpc.statd: Failed to unregister program 100024, version 1 rpc.statd: Effective UID, GID: 101, 0 rpc.statd: Waiting for client connections Please mail if I can help to track this down. Regards Harri -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2YdzYACgkQUTlbRTxpHjcA3ACfajDYwO8qgYPDxlZH6sknjCZr rd4AoIedQJo+BWeY50F9uH5d7huLAwxK =ZGNO -END PGP SIGNATURE- -- 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/4d98773b.8060...@afaics.de
Bug#620694: /lib/modules/2.6.32-5-686/kernel/drivers/staging/rt2860/rt2860sta.ko: frequent reconnects, sometimes driver is unusable
Package: linux-2.6 Version: 2.6.32-31 Severity: important File: /lib/modules/2.6.32-5-686/kernel/drivers/staging/rt2860/rt2860sta.ko Ralink driver causes frequent WiFi reconnects. Sometimes it could just disconnect and never connect back again, untill laptop is rebooted or hardware WiFi on/off button is pressed. -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-31) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Tue Mar 8 21:36:00 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-686 root=/dev/mapper/lappy-root ro quiet ** Tainted: C (1024) * Module from drivers/staging has been loaded. ** Kernel log: [82.865022] usb 2-1.3: USB disconnect, address 3 [113803.809094] r8169: eth0: link down [113811.308042] r8169: eth0: link up [113821.336481] ERROR! BBP write R63=0xa3e37 fail. BusyCnt= 100.bPCIclkOff = 0. [113821.336956] ERROR! BBP write R64=0xa3e37 fail. BusyCnt= 100.bPCIclkOff = 0. [113821.337427] ERROR! BBP write R86=0xa3e37 fail. BusyCnt= 100.bPCIclkOff = 0. [113821.337932] ERROR! BBP write R82=0xa3e37 fail. BusyCnt= 100.bPCIclkOff = 0. [113821.338406] ERROR! BBP write R75=0xa3e37 fail. BusyCnt= 100.bPCIclkOff = 0. [113821.338895] ERROR! BBP write R66=0xa3e37 fail. BusyCnt= 100.bPCIclkOff = 0. [113821.340469] ERROR! BBP write R3=0xa3e37 fail. BusyCnt= 100.bPCIclkOff = 0. [113821.700846] eth0: no IPv6 routers present [113822.028391] usb 1-1.4: new full speed USB device using ehci_hcd and address 4 [113822.302135] ERROR! BBP read R66=0xa3e37 fail [113822.302597] ERROR! BBP write R66=0xa3e37 fail. BusyCnt= 100.bPCIclkOff = 0. [113822.303063] ERROR! BBP read R4=0xa3e37 fail [113822.303524] ERROR! BBP write R4=0xa3e37 fail. BusyCnt= 100.bPCIclkOff = 0. [113822.304160] ERROR! BBP write R62=0xa3e37 fail. BusyCnt= 100.bPCIclkOff = 0. [113822.304623] ERROR! BBP write R63=0xa3e37 fail. BusyCnt= 100.bPCIclkOff = 0. [113822.305095] ERROR! BBP write R64=0xa3e37 fail. BusyCnt= 100.bPCIclkOff = 0. [113822.305558] ERROR! BBP write R86=0xa3e37 fail. BusyCnt= 100.bPCIclkOff = 0. [113822.306023] ERROR! BBP write R82=0xa3e37 fail. BusyCnt= 100.bPCIclkOff = 0. [113822.306488] ERROR! BBP write R75=0xa3e37 fail. BusyCnt= 100.bPCIclkOff = 0. [113822.306967] ERROR! BBP write R66=0xa3e37 fail. BusyCnt= 100.bPCIclkOff = 0. [113822.447956] ERROR! BBP write R62=0xa3e37 fail. BusyCnt= 100.bPCIclkOff = 0. [113822.448418] ERROR! BBP write R63=0xa3e37 fail. BusyCnt= 100.bPCIclkOff = 0. [113822.448882] ERROR! BBP write R64=0xa3e37 fail. BusyCnt= 100.bPCIclkOff = 0. [113822.449367] ERROR! BBP write R86=0xa3e37 fail. BusyCnt= 100.bPCIclkOff = 0. [113822.449832] ERROR! BBP write R82=0xa3e37 fail. BusyCnt= 100.bPCIclkOff = 0. [113822.449839] Reset BBP Agent busy bit! [113823.028289] usb 1-1.4: New USB device found, idVendor=148f, idProduct=1000 [113823.028294] usb 1-1.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [113823.028413] usb 1-1.4: configuration #1 chosen from 1 choice [113823.120034] Bluetooth: Generic Bluetooth USB driver ver 0.6 [113823.122081] usbcore: registered new interface driver btusb [113828.783093] ===rt_ioctl_giwscan. 6(6) BSS returned, data-length = 897 [113833.880641] ===rt_ioctl_giwscan. 6(6) BSS returned, data-length = 866 [113833.880910] ==rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1) [113888.673758] ===rt_ioctl_giwscan. 7(7) BSS returned, data-length = 1041 [113928.593953] ===rt_ioctl_giwscan. 4(4) BSS returned, data-length = 657 [113988.474461] ===rt_ioctl_giwscan. 6(6) BSS returned, data-length = 897 [114068.315984] ===rt_ioctl_giwscan. 7(7) BSS returned, data-length = 1041 [114168.116809] ===rt_ioctl_giwscan. 7(7) BSS returned, data-length = 1041 [114287.878453] ===rt_ioctl_giwscan. 6(6) BSS returned, data-length = 866 [114407.640499] ===rt_ioctl_giwscan. 7(7) BSS returned, data-length = 1041 [114527.401432] ===rt_ioctl_giwscan. 7(7) BSS returned, data-length = 1041 [114579.955005] RX DESC f2fce000 size = 2048 [114579.955166] -- RTMPAllocTxRxRingMemory, Status=0 [114579.958453] 1. Phy Mode = 0 [114579.958456] 2. Phy Mode = 0 [114579.958460] NVM is Efuse and its size =2d[2d0-2fc] [114579.960446] 3. Phy Mode = 0 [114579.962952] MCS Set = 00 00 00 00 00 [114579.983103] rt28xx_init, Status=0 [114579.983210] 0x1300 = 000a4260 [114579.983237] AUX_CTRL = 0x1d42 [114579.983244] Read AUX_CTRL = 0x1d42 [114579.983249] Write AUX_CTRL = 0x1d42 [114579.983254] OSC_CTRL = 0x3ff11 [114579.983399] rt30xx Read PowerLevelMode = 0x3. [114579.983402] rt30xx F Write 0x83 Command = 0x3. [114585.007811] ===rt_ioctl_giwscan. 7(7) BSS returned, data-length = 1041 [114585.008031] ==rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1) [114590.131437] wlan0: no IPv6 routers present [114647.163672] ===rt_ioctl_giwscan. 7(7) BSS returned, data-length = 1041 [114687.082353] ===rt_ioctl_giwscan. 7(7) BSS returned, data-length = 1041 [114746.965364] ===rt_ioctl_giwscan. 6(6) BSS
Processed: your mail
Processing commands for cont...@bugs.debian.org: retitle 620234 kernel crashes after /dev (6.0.1 amd64) Bug #620234 [installation-reports] installation-reports: AMD64 does not boot on Opteron 170 Changed Bug title to 'kernel crashes after /dev (6.0.1 amd64)' from 'installation-reports: AMD64 does not boot on Opteron 170' severity 620234 important Bug #620234 [installation-reports] kernel crashes after /dev (6.0.1 amd64) Severity set to 'important' from 'critical' reassign 620234 linux-2.6 Bug #620234 [installation-reports] kernel crashes after /dev (6.0.1 amd64) Bug reassigned from package 'installation-reports' to 'linux-2.6'. thanks Stopping processing here. Please contact me if you need assistance. -- 620234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620234 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.130184579824205.transcr...@bugs.debian.org
Re: [Pkg-alsa-devel] Processed: reassign 617743 alsa-driver
On Sun, Apr 03, 2011 at 04:25:16AM +0100, Ben Hutchings wrote: On Fri, 2011-04-01 at 01:03 -0500, Tarek Soliman wrote: On Thu, Mar 31, 2011 at 08:01:37PM +0100, Ben Hutchings wrote: On Thu, Mar 31, 2011 at 08:30:23PM +0200, Elimar Riesebieter wrote: * Debian Bug Tracking System [110331 03:39 +]: Processing commands for cont...@bugs.debian.org: reassign 617743 alsa-driver Bug #617743 [linux-2.6] linux-image-2.6.37-2-686: found another USB midi cable with a 4 byte limit Bug reassigned from package 'linux-2.6' to 'alsa-driver'. Bug No longer marked as found in versions 2.6.37-2. This can be fixed easy to the alsa-source package. The fix will then be valid for users who build their alsa-drivers from alsa-source. But people using alsa drivers from Debian's kernel won't, though. I agree it should be fixed in linux-2.6. But it should be accepted upstream first, and filing a bug in the upstream bug tracker is probably not the way to get this done! What is the correct way to get this accepted upstream? Add a 'signed-off-by' statement to your patch as explained in section 12 of http://www.kernel.org/doc/Documentation/SubmittingPatches, then send it to Clemens Ladisch clem...@ladisch.de and the ALSA developer list alsa-de...@alsa-project.org. Done. Thanks for the advice. -- Tarek -- 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/20110403155933.GA29612@zeus.olympus
Bug#620287: [Pkg-xfce-devel] Bug#620287: xfce4-power-manager: Kernel Oops / NULL pointer deref. while pressing sleep button (Fn-F4 in this case)
Forwarded Message From: Martin Hettich kuj...@mathphys.fsk.uni-heidelberg.de To: Ben Hutchings b...@decadent.org.uk Subject: Re: Bug#620287: [Pkg-xfce-devel] Bug#620287: xfce4-power-manager: Kernel Oops / NULL pointer deref. while pressing sleep button (Fn-F4 in this case) Date: Sun, 3 Apr 2011 17:56:52 +0200 Hi there, Sun, Apr 03, 2011 at 05:16:36AM +0100, Ben Hutchings wrote: On Thu, 2011-03-31 at 23:10 +0200, Yves-Alexis Perez wrote: [...] This looks like a kernel (or machine) bug so reassigning. This is correct. Martin, which version of linux-image-2.6.32-5-686 do you have installed? neuromancer /home/mhettich uname -a Linux neuromancer 2.6.32-5-686 #1 SMP Tue Mar 8 21:36:00 UTC 2011 i686 GNU/Linux neuromancer /home/mhettich dpkg -l linux-image-2.6.32\* ii linux-image-2.6.32-5-686 2.6.32-31 Linux 2.6.32 for modern PCs Hope that helps. If u need additional info or want me to try something, dont hesitate to email me. My machine is an Acer Aspire One AOA 150-Ac Model No ZG5 Thanks have a nice one, -- Martin Hettich, cand. phys. email: hett...@uni-hd.de -- 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/1301847491.4157.66.camel@localhost
Processed: reassign 620287 to linux-2.6
Processing commands for cont...@bugs.debian.org: reassign 620287 linux-2.6 2.6.32-31 Bug #620287 [linux-image-2.6.32-5-686] xfce4-power-manager: Kernel Oops / NULL pointer deref. while pressing sleep button (Fn-F4 in this case) Bug reassigned from package 'linux-image-2.6.32-5-686' to 'linux-2.6'. Bug #620287 [linux-2.6] xfce4-power-manager: Kernel Oops / NULL pointer deref. while pressing sleep button (Fn-F4 in this case) 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. thanks Stopping processing here. Please contact me if you need assistance. -- 620287: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620287 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.130184746528298.transcr...@bugs.debian.org
Processed: tagging 620234, found 620234 in 2.6.32-31
Processing commands for cont...@bugs.debian.org: tags 620234 - d-i Bug #620234 [linux-2.6] kernel crashes after /dev (6.0.1 amd64) Removed tag(s) d-i. found 620234 2.6.32-31 Bug #620234 [linux-2.6] kernel crashes after /dev (6.0.1 amd64) 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. thanks Stopping processing here. Please contact me if you need assistance. -- 620234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620234 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.13018507867195.transcr...@bugs.debian.org
Bug#620234: installation-reports: AMD64 does not boot on Opteron 170
On Thu, 2011-03-31 at 11:56 +0200, Alexander Abt wrote: Package: installation-reports Severity: critical Tags: d-i Justification: breaks the whole system After the installation of Debian GNU/linux 6.0.0.1 AMD64 the kernel crashes after /dev. The monitor goes in standby and nothing happend, i can only press the reset button. The used hardware is ok, WindowsXP SP3 runs and Slackware64 13.1 too. I have the detailed hardware on sysprofile http://www.sysprofile.de/id40682. I'm sorry, but the information that site collects is not very useful. For some reason you have sent a hardware summary for a 32-bit Intel system: [...] == Installer hardware-summary: == uname -a: Linux Amnesiac 2.6.32-5-486 #1 Fri Dec 10 15:32:53 UTC 2010 i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface [8086:2560] (rev 03) lspci -knn: Subsystem: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface [8086:2560] lspci -knn: Kernel driver in use: agpgart-intel lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE Host-to-AGP Bridge [8086:2561] (rev 03) [...] Please send the output of 'lspci -knn' on the system that actually has this problem (I assume you can do this under Slackware). Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: tagging 620234
Processing commands for cont...@bugs.debian.org: tags 620234 + moreinfo Bug #620234 [linux-2.6] kernel crashes after /dev (6.0.1 amd64) Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 620234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620234 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.13018512709386.transcr...@bugs.debian.org
Bug#615598: I get this error accompanied by a black screen
I have DPMS set to on, the machine is always up and will come out of DPMS with a mouse movement 90% of the time. The other 10% of the time the screen remains black and in power save mode. The only way out of it is to switch to a console (ALT-SHIFT-Fn) and back to gdm (ALT-SHIFT-F7), but I didn't know that the first couple of times the error happened. What is worse than the syslog spam is the absolute terror of having what appears to be an unresponsive system as I've had two machines die recently because of graphics adapter failure and or BIOS / motherboard failures. I have what could be termed PTSD from black screens, so coming out of DPMS sleep should work 100% of the time, EDID checksum be damned. I've seen other reports about this error which contained patch suggestions varying from not polling or probing every connector to remembering the EDID data and not probing at all but I can't recall where these were or which distribution, I know they were on launchpad. I am running wheezy/sid with Intel 945GME video controller and an ACER P191W monitor. I believe the connection protocol is TMDS-8 but not sure now because the output from DRM no longer reports that information on a mode switch from console to X and vice versa. Previously these messages appeared: /var/log/kern.log.1.gz:Nov 6 13:08:23 asusb202 kernel: [717721.609526] [drm] TMDS-8: set mode 1440x900 19 /var/log/kern.log.1.gz:Nov 7 14:26:04 asusb202 kernel: [717723.773204] [drm] TMDS-8: set mode 1440x900 19 /var/log/kern.log.1.gz:Nov 7 14:26:04 asusb202 kernel: [717727.653623] [drm] TMDS-8: set mode 2a /var/log/kern.log.3.gz:Nov 3 08:58:48 asusb202 kernel: [538812.916458] [drm] TMDS-8: set mode 1440x900 19 /var/log/kern.log.3.gz:Nov 4 11:26:48 asusb202 kernel: [538820.074848] [drm] TMDS-8: set mode 1440x900 19 /var/log/kern.log.3.gz:Nov 4 11:26:58 asusb202 kernel: [538834.523321] [drm] TMDS-8: set mode 29 Also note that these messages just started becoming a problem in the last couple of months, and while I can't pinpoint the exact release of the kernel I have been running 2.6.32 for at least the last year I believe. 'get-edid | parse-edid' and 'xset q' for DPMS settings. Keyboard Control: auto repeat: onkey click percent: 0LED mask: XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: off auto repeat delay: 500repeat rate: 30 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 10 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 600cycle: 600 Colors: default colormap: 0x20BlackPixel: 0WhitePixel: 16777215 Font Path: unix/:7100,/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 DPMS (Energy Star): Standby: 1201Suspend: 1801Off: 2401 DPMS is Enabled Monitor is On parse-edid: parse-edid version 2.0.0 parse-edid: EDID checksum passed. # EDID version 1 revision 3 Section Monitor # Block type: 2:0 3:ff # Block type: 2:0 3:fd # Block type: 2:0 3:fc Identifier P191W VendorName ACR ModelName P191W # Block type: 2:0 3:ff # Block type: 2:0 3:fd HorizSync 30-82 VertRefresh 50-75 # Max dot clock (video bandwidth) 140 MHz # Block type: 2:0 3:fc # DPMS capabilities: Active off:yes Suspend:yes Standby:yes Mode1440x900 # vfreq 59.887Hz, hfreq 55.935kHz DotClock106.50 HTimings1440 1520 1672 1904 VTimings900 903 909 934 Flags +HSync -VSync EndMode # Block type: 2:0 3:ff # Block type: 2:0 3:fd # Block type: 2:0 3:fc EndSection
Bug#620652: linux-image-2.6.38-2-686-bigmem: fails to disable error beep
tags 620652 - sid quit Hi Henry, henry atting wrote: Usually as a last resort removing the pc speaker modules pcspkr and snd_pscp effectively disables the error beep. Not with this kernel. In the according directories I removed `pcspkr.ko` and `snd_pcsp.ko`, then executed `depmod -a`, then built initird with: update-initramfs -u -k all. Nevertheless the beep on error is still there... Could you be more specific? What version did not have this problem? What do you do to provoke the beep? (I have to ask since on a desktop there are some situations where a sound file containing a recorded beep sound is played.) [ 18.175066] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input13 Hmm, this is interesting. What happens if you unload snd_hda_intel and reload it with beep_mode=0? # modprobe -r snd_hda_intel # modprobe snd_hda_intel beep_mode=0 If that works, maybe 2 (mutable using the software mixer) would be a good default for SND_HDA_INPUT_BEEP_MODE. Thanks for reporting, Jonathan -- 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/20110403184415.GC3830@elie
Processed: Re: linux-image-2.6.38-2-686-bigmem: fails to disable error beep
Processing commands for cont...@bugs.debian.org: tags 620652 - sid Bug #620652 [linux-2.6] linux-image-2.6.38-2-686-bigmem: fails to disable error beep Removed tag(s) sid. quit Stopping processing here. Please contact me if you need assistance. -- 620652: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620652 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.130185626524759.transcr...@bugs.debian.org
Bug#574758: marked as done (dkms postinst script called before headers are set up)
Your message dated Sun, 03 Apr 2011 19:59:31 +0100 with message-id 1301857171.2935.17.camel@localhost and subject line Re: dkms postinst script called before headers are set up has caused the Debian Bug report #574758, regarding dkms postinst script called before headers are set up 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.) -- 574758: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: linux-image-2.6.32-4-amd64 Version: 2.6.32-10 It seems that /etc/kernel/postinst.d/dkms is called to rebuild additional kernel modules before the kernel headers are set up. Sample session: Setting up linux-image-2.6.32-4-amd64 (2.6.32-10) ... Running depmod. Running update-initramfs. update-initramfs: Generating /boot/initrd.img-2.6.32-4-amd64 Running /usr/sbin/update-grub. Generating grub.cfg ... Found linux image: /boot/vmlinuz-2.6.32-4-amd64 Found initrd image: /boot/initrd.img-2.6.32-4-amd64 Found memtest86 image: /boot/memtest86.bin Found Ubuntu lucid (development branch) (10.04) on /dev/sda1 done Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/dkms 2.6.32-4-amd64 /boot/vmlinuz-2.6.32-4-amd64 run-parts: executing /etc/kernel/postinst.d/initramfs-tools 2.6.32-4-amd64 /boot/vmlinuz-2.6.32-4-amd64 run-parts: executing /etc/kernel/postinst.d/pm-utils 2.6.32-4-amd64 /boot/vmlinuz-2.6.32-4-amd64 Setting up linux-headers-2.6.32-4-common (2.6.32-10) ... Setting up linux-kbuild-2.6.32 (2.6.32-1) ... Setting up linux-headers-2.6.32-4-amd64 (2.6.32-10) ... This looks weird. Regards Harri -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkulLT4ACgkQUTlbRTxpHjd/ygCfRIYpBeB2b+4F33BSohG83UT4 esoAoJFW92dhI8I5vHpnInPkPyL2MT8d =L+6e -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- On Sat, 2010-03-20 at 21:17 +0100, Harald Dunkel wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: linux-image-2.6.32-4-amd64 Version: 2.6.32-10 It seems that /etc/kernel/postinst.d/dkms is called to rebuild additional kernel modules before the kernel headers are set up. [...] This is the intended behaviour. 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 ---End Message---
Bug#620745: linux-image-2.6.38-2-686: nouveau : i2c error in dmesg
Package: linux-2.6 Version: 2.6.38-2 Severity: normal Hi, when using nouveau driver, kernel log are filled with : Apr 3 21:19:06 mat-pc kernel: [ 1456.128011] i2c i2c-3: sendbytes: error -110 Apr 3 21:19:07 mat-pc kernel: [ 1456.828010] i2c i2c-3: sendbytes: error -110 Apr 3 21:19:16 mat-pc kernel: [ 1465.680015] i2c i2c-3: sendbytes: error -110 Apr 3 21:19:57 mat-pc kernel: [ 1507.361150] i2c i2c-3: sendbytes: NAK bailout. Apr 3 21:20:18 mat-pc kernel: [ 1528.022190] i2c i2c-3: sendbytes: NAK bailout. Apr 3 21:21:41 mat-pc kernel: [ 1610.722247] i2c i2c-3: sendbytes: NAK bailout. Apr 3 21:21:51 mat-pc kernel: [ 1620.936458] i2c i2c-3: sendbytes: NAK bailout. Apr 3 21:22:01 mat-pc kernel: [ 1631.033488] i2c i2c-3: sendbytes: NAK bailout. Apr 3 21:22:11 mat-pc kernel: [ 1641.153186] i2c i2c-3: sendbytes: NAK bailout. Apr 3 21:22:21 mat-pc kernel: [ 1651.249634] i2c i2c-3: sendbytes: NAK bailout. Apr 3 21:23:02 mat-pc kernel: [ 1692.340220] i2c i2c-3: sendbytes: NAK bailout. Apr 3 21:23:12 mat-pc kernel: [ 1702.458999] i2c i2c-3: sendbytes: NAK bailout. Apr 3 21:23:43 mat-pc kernel: [ 1733.109599] i2c i2c-3: sendbytes: NAK bailout. Apr 3 21:24:04 mat-pc kernel: [ 1753.564524] i2c i2c-3: sendbytes: NAK bailout. [...] -- Package-specific info: ** Version: Linux version 2.6.38-2-686 (Debian 2.6.38-2) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-14) ) #1 SMP Tue Mar 29 17:27:45 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.38-2-686 root=UUID=f93d9440-a1e0-4e30-9a7b-4ed4eac6f21d ro ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [ 11.733874] i2c-core: driver [msp3400] using legacy resume method [ 11.780646] nvidia: module license 'NVIDIA' taints kernel. [ 12.344742] nvidia :01:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 12.344820] vgaarb: device changed decodes: PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem [ 12.346224] NVRM: loading NVIDIA Linux x86 Kernel Module 96.43.19 Wed Oct 27 19:01:34 PDT 2010 [ 12.370668] bttv0: audio absent, no audio device found! [ 12.384947] i2c-core: driver [tuner] using legacy suspend method [ 12.385012] i2c-core: driver [tuner] using legacy resume method [ 12.443145] All bytes are equal. It is not a TEA5767 [ 12.443341] tuner 0-0060: chip found @ 0xc0 (bt878 #0 [sw]) [ 12.500869] tuner-simple 0-0060: creating new instance [ 12.500935] tuner-simple 0-0060: type set to 3 (Philips (SECAM+PAL_BG) (FI1216MF, FM1216MF, FR1216MF)) [ 12.501917] bttv0: registered device video0 [ 12.502105] bttv0: registered device vbi0 [ 12.502178] bttv0: PLL: 28636363 = 35468950 .. ok [ 12.535446] Bt87x :00:0a.1: PCI INT A - GSI 17 (level, low) - IRQ 17 [ 12.535993] bt87x0: Using board 1, analog, digital (rate 32000 Hz) [ 12.536849] EMU10K1_Audigy :00:08.0: PCI INT A - GSI 19 (level, low) - IRQ 19 [ 12.606222] ACPI: resource vt596_smbus [io 0x0400-0x0407] conflicts with ACPI region SMOV [io 0x400-0x406] [ 12.606302] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 12.606729] VIA 82xx Audio :00:11.5: PCI INT C - GSI 22 (level, low) - IRQ 22 [ 12.614673] VIA 82xx Audio :00:11.5: setting latency timer to 64 [ 14.162941] Adding 00k swap on /dev/sdb1. Priority:-1 extents:1 across:00k [ 14.352210] EXT3-fs (sdb3): using internal journal [ 14.533266] w83627hf: w83627hf: Found W83697HF chip at 0x290 [ 20.531450] EXT3-fs: barriers not enabled [ 20.538952] kjournald starting. Commit interval 5 seconds [ 20.539037] EXT3-fs (sdb2): mounted filesystem with ordered data mode [ 20.547324] EXT3-fs: barriers not enabled [ 20.549005] kjournald starting. Commit interval 5 seconds [ 20.549226] EXT3-fs (sdb5): using internal journal [ 20.549285] EXT3-fs (sdb5): mounted filesystem with ordered data mode [ 20.616939] REISERFS (device sdb6): found reiserfs format 3.6 with standard journal [ 20.617090] REISERFS (device sdb6): using ordered data mode [ 20.624562] REISERFS (device sdb6): journal params: device sdb6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 [ 20.627317] REISERFS (device sdb6): checking transaction log (sdb6) [ 20.671370] REISERFS (device sdb6): Using r5 hash to sort names [ 20.696151] EXT3-fs: barriers not enabled [ 20.698039] kjournald starting. Commit interval 5 seconds [ 20.698265] EXT3-fs (sdb7): using internal journal [ 20.698325] EXT3-fs (sdb7): mounted filesystem with ordered data mode [ 20.758022] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [ 20.829061] EXT3-fs: barriers not enabled [ 20.831518] kjournald starting. Commit interval 5 seconds [ 20.831649] EXT3-fs (sdb9): warning: maximal mount count reached, running e2fsck is recommended [ 20.831896] EXT3-fs (sdb9): using
Bug#620652: linux-image-2.6.38-2-686-bigmem: fails to disable error beep
Jonathan Nieder jrnie...@gmail.com writes: tags 620652 - sid quit Hi Henry, Hi Jonathan, henry atting wrote: Usually as a last resort removing the pc speaker modules pcspkr and snd_pscp effectively disables the error beep. Not with this kernel. In the according directories I removed `pcspkr.ko` and `snd_pcsp.ko`, then executed `depmod -a`, then built initird with: update-initramfs -u -k all. Nevertheless the beep on error is still there... Could you be more specific? What version did not have this problem? What do you do to provoke the beep? (I have to ask since on a desktop there are some situations where a sound file containing a recorded beep sound is played.) The beep sounds on error (or on shutdown) E.g. I enter `sldj`, hit TAB for completion - it beeps. No matter if I am on a virtual console or in a terminal emulator. (I know that I can disable it on X with the appropriate xset setting) I use gnome with awesome as a WM. The beep sound is definitively this painful hardware beep and not a sound file. Before this kernel removing the mentioned modules always helped, my last kernel before 2.6.38.* was 2.6.32-5-686-bigmem [ 18.175066] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input13 Hmm, this is interesting. What happens if you unload snd_hda_intel and reload it with beep_mode=0? # modprobe -r snd_hda_intel # modprobe snd_hda_intel beep_mode=0 If that works, maybe 2 (mutable using the software mixer) would be a good default for SND_HDA_INPUT_BEEP_MODE. This works indeed. Becaus I could not unload it (got a message that it is still in use) I put these two lines in /etc/rc.local... and the beep is gone. Thanks for reporting, Jonathan Thanks, henry -- http://literaturlatenight.de -- 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/87zko7gkjj@online.de
Bug#620745: linux-image-2.6.38-2-686: nouveau : i2c error in dmesg
On Sun, 2011-04-03 at 21:40 +0200, matthieu castet wrote: Package: linux-2.6 Version: 2.6.38-2 Severity: normal Hi, when using nouveau driver, kernel log are filled with : [...] Please report this upstream at https://bugs.freedesktop.org under product 'xorg', component 'Driver/Nouveau' (yes, even though this is a kernel driver). Let us know the 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#620652: linux-image-2.6.38-2-686-bigmem: fails to disable error beep
henry atting wrote: Jonathan Nieder jrnie...@gmail.com writes: # modprobe -r snd_hda_intel # modprobe snd_hda_intel beep_mode=0 If that works, maybe 2 (mutable using the software mixer) would be a good default for SND_HDA_INPUT_BEEP_MODE. This works indeed. Becaus I could not unload it (got a message that it is still in use) I put these two lines in /etc/rc.local... and the beep is gone. Thanks. One final test: if you use beep_mode=2 (instead of beep_mode=0) and use your usual mixing app, can you cause the beep to go away (i.e., is there a control for that)? Depending on the answer, I think we should: * use beep_mode=2 and find some way to advertise (release notes?) that the mixer can be used to turn the beep on and off, or * keep using beep_mode=1 and find some way to advertise that adding a .conf file to /etc/modprobe.d with options snd_hda_intel beep_mode=0 will turn the beep off. And if there is some sysfs way to change the setting at runtime, that would be worth advertising, too. Meanwhile I also think it would be a good idea to turn pc speaker beeps in general off by default, but that's a separate story (and probably should be filed as a separate bug). -- 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/20110403211056.GI3830@elie
Re: Bug#617511: udev didn't create new device node when plug a memory card
reassign 617511 linux-2.6 thanks Probably not, if you insert the memory card and the kernel does not react then this is a kernel problem. I think that the same is happening on my Latitude E6400 (I inserted an SD card and nothing happened, so I tought that the reader was broken), but I do not have anymore an SD card around to test this. 03:01.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 21) 03:01.2 0805: 1180:0822 (rev 21) (prog-if 01) Subsystem: 1028:0233 Flags: bus master, medium devsel, latency 64, IRQ 18 Memory at f68ff700 (32-bit, non-prefetchable) [size=256] Capabilities: [80] Power Management version 2 Kernel driver in use: sdhci-pci On Mar 09, Viet Nguyen meta...@gmail.com wrote: Sorry but nothing printed, neither dmesg. Did i miss anything? On Wed, Mar 9, 2011 at 9:18 PM, Marco d'Itri m...@linux.it wrote: On Mar 09, vietnq meta...@gmail.com wrote: I have a Dell Inspiron 1464. When I plug a memory card into the internal card reader, a device node sdc1 is created. But after doing dist-upgrade, no new one is created. Please get an events log with udevadm monitor --kernel --udev --property while you plug in the card. -- ciao, Marco -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk13jD8ACgkQFGfw2OHuP7E4xgCcC3x4jb/w6CGyAEppu0ot/9zN pNsAoKFkCFwxLsvGwL66uO/QEObQlQ4I =ajUK -END PGP SIGNATURE- -- ciao, Marco signature.asc Description: Digital signature
Processed: Re: Bug#617511: udev didn't create new device node when plug a memory card
Processing commands for cont...@bugs.debian.org: reassign 617511 linux-2.6 Bug #617511 [udev] udev didn't create new device node when plug a memory card Bug reassigned from package 'udev' to 'linux-2.6'. Bug No longer marked as found in versions udev/166-1. thanks Stopping processing here. Please contact me if you need assistance. -- 617511: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617511 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.130187884528732.transcr...@bugs.debian.org
Bug#620652: linux-image-2.6.38-2-686-bigmem: fails to disable error beep
Jonathan Nieder jrnie...@gmail.com writes: henry atting wrote: Jonathan Nieder jrnie...@gmail.com writes: # modprobe -r snd_hda_intel # modprobe snd_hda_intel beep_mode=0 If that works, maybe 2 (mutable using the software mixer) would be a good default for SND_HDA_INPUT_BEEP_MODE. This works indeed. Becaus I could not unload it (got a message that it is still in use) I put these two lines in /etc/rc.local... and the beep is gone. Thanks. One final test: if you use beep_mode=2 (instead of beep_mode=0) and use your usual mixing app, can you cause the beep to go away (i.e., is there a control for that)? As far as I remember there is no control for the beep in alsamixer. As I use pulseaudio maybe there is one in pavucontrol but I can not test it until tomorrow... Depending on the answer, I think we should: * use beep_mode=2 and find some way to advertise (release notes?) that the mixer can be used to turn the beep on and off, or * keep using beep_mode=1 and find some way to advertise that adding a .conf file to /etc/modprobe.d with options snd_hda_intel beep_mode=0 will turn the beep off. And if there is some sysfs way to change the setting at runtime, that would be worth advertising, too. Meanwhile I also think it would be a good idea to turn pc speaker beeps in general off by default, but that's a separate story (and probably should be filed as a separate bug). In my mind that would be great. -- http://literaturlatenight.de -- 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/86mxk6egrg@online.de
