[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#637974: marked as done (linux-2.6: GDM beeps for Linux kernel versions >=2.6.33)

Your message dated Tue, 16 Aug 2011 15:35:24 +0100
with message-id <1313505324.2981.129.camel@deadeye>
and subject line Re: Bug#637974: linux-2.6: GDM beeps for Linux kernel versions >=2.6.33
has caused the Debian Bug report #637974,
regarding linux-2.6: GDM beeps for Linux kernel versions >=2.6.33
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 owner@bugs.debian.org
immediately.)


-- 
637974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637974
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-2.6
Version: 2.6.33-2-686
Severity: normal

Dear Thomas and dear Debian folks,


I am sorry to submit another report to Debian’s Linux kernel package.

I just picked a version number for the metadata found with a search
engine and containing 2.6.33.

With `linux-image-2.6.32-5-amd64` when GDM starts or the system shuts
down I do not hear any beep from the PC speaker.

        $ dpkg -S /etc/modprobe.d/alsa-base-blacklist.conf 
        alsa-base: /etc/modprobe.d/alsa-base-blacklist.conf
        $ LANG=C dpkg -l alsa-base
        […]
        ii  alsa-base      1.0.23+dfsg-4  ALSA driver configuration files
        $ LANG=C grep pc /etc/modprobe.d/alsa-base-blacklist.conf 
        # Comment this entry in order to load snd-pcsp driver

        $ uname -a
        Linux joe 2.6.32-5-amd64 #1 SMP Tue Mar 8 22:49:26 UTC 2011 x86_64 GNU/Linux
        $ lsmod | grep pcs
        pcspkr                  1699  0
        $ dmesg | grep spk
        [   48.380000] input: PC Speaker as /devices/platform/pcspkr/input/input5

With a Linux kernel at version 2.6.33 the module `pcspkr` is loaded too.

        $ grep spk dmesg.2.6.33-8724fdb53d27d7b59b60c8a399cc67f9abfabb33--with-beep 
        [   58.254983] input: PC Speaker as /devices/platform/pcspkr/input/input4

I tried other revisions and the numbering does not influence the beep.

Could it be related to the following commit [1]?

        $ git log origin/master -- drivers/input/misc/pcspkr.c
	[…]
	commit ced918eb748ce30b3aace549fd17540e40ffdca0
        Author: Thomas Gleixner <tglx@linutronix.de>
        Date:   Wed Feb 17 16:47:10 2010 +0000

            i8253: Convert i8253_lock to raw_spinlock

If yes that would mean, the pcspkr just did not work before and it would
have to be blacklisted in `/etc/modprobe.d/`.


Thanks,

Paul


[1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=ced918eb748ce30b3aace549fd17540e40ffdca0
[2] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Makefile;h=1b24895212d8d198587bed5152b56a2cef8134c3;hb=ced918eb748ce30b3aace549fd17540e40ffdca0

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
--- Begin Message --- 
On Tue, 2011-08-16 at 16:17 +0200, Paul Menzel wrote:
> Am Dienstag, den 16.08.2011, 13:56 +0100 schrieb Ben Hutchings:
> > From all that you've written, I still can't work out what behaviour you
> > think is a bug.  Please explain.
> 
> I am sorry.
> 
> With Linux kernel 2.6.32 `snd-pcsp` is blacklisted and `pcspkr` is
> loaded and I do not hear any sounds from the PC speaker which is what I
> want to have.
> 
> With Linux kernel >= 2.6.33 something changed that I hear the PC speaker
> which I do not want. So that is a regression from my view point and this
> could be called a “bug”.

I seem to remember there are certain cases where the X server can make a
warning beep.  Perhaps something was changed in a kernel driver that
results in such a warning.

> And the question is, if blacklisting `snd-pcsp` is enough or if `pcspkr`
> also has to be blacklisted.

I think you would have to.  It is certainly not a bug that pcspkr is
capable of producing beeps.

Ben.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: