Bug#484239: linux-image-2.6.25-2-686: kadahat in zalahat

2008-06-03 Thread maximilian attems
On Tue, Jun 03, 2008 at 10:19:05AM +0300, Shai Berger wrote:
 
 Subject: linux-image-2.6.25-2-686: sound breaks on second login to main X 
 session (vt7)
 Package: linux-image-2.6.25-2-686
 Version: 2.6.25-4
 Severity: normal
 
 
 This report corrects my misdiagnosis of the problem as
 reported in bug #483664.
 
 I use a desktop machine with multiple X sessions in virtual terminals.
 with kernel 2.6.25, I have this scenario, reproducibly:
 
 - After boot, first user logs into X session on vt7
 - First user logs out 
 - Again, a user logs in on vt7 (I used same user, but I don't think that 
 matters)
 - Sound dies

again missing vital info, like dmesg output when that happen.
we need more info then Sound dies

what sound application are you using?
 

-- 
maks



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#484239: linux-image-2.6.25-2-686: kadahat in zalahat

2008-06-03 Thread Shai Berger
Package: linux-image-2.6.25-2-686
Version: 2.6.25-4
Severity: normal


Subject: linux-image-2.6.25-2-686: sound breaks on second login to main X 
session (vt7)
Package: linux-image-2.6.25-2-686
Version: 2.6.25-4
Severity: normal


This report corrects my misdiagnosis of the problem as
reported in bug #483664.

I use a desktop machine with multiple X sessions in virtual terminals.
with kernel 2.6.25, I have this scenario, reproducibly:

- After boot, first user logs into X session on vt7
- First user logs out 
- Again, a user logs in on vt7 (I used same user, but I don't think that 
matters)
- Sound dies

This happens whether or not there are other users in other vt's, and
sound dies for all sessions (including sessions which opened before
on other vt's and had sound).

running alsaconf at this point restores sound, but only until the next
login on vt7.

2.6.24 doesn't have the problem at all, and all I can see in dmesg or
/var/log/syslog is the device being restarted by alsaconf (that is,
no errors).

I realize that my use of an nvidia blob makes my kernel unsupported;
I will try later, when I have more time, to see if I can reproduce
the problem without it. What seemed before (in #483664) like an
upgrade problem, appears now to be an actual problem with the
new kernel, so I will make more of an effort to pinpoint it; I wanted
to report it anyway in case the better description rings a bell.

I have gone back to 2.6.24 to let the other users of this computer
enjoy sound -- I'm attaching the 2.6.25 kernel info (from my earlier
report) after the 2.6.24 info.

-- Package-specific info:

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.25-2-686 depends on:
ii  debconf [debconf-2.0] 1.5.22 Debian configuration management sy
ii  initramfs-tools [linux-initra 0.92a  tools for generating an initramfs
ii  module-init-tools 3.4-1  tools for managing Linux kernel mo

Versions of packages linux-image-2.6.25-2-686 recommends:
ii  libc6-i6862.7-11 GNU C Library: Shared libraries [i

-- debconf information:
  linux-image-2.6.25-2-686/preinst/abort-install-2.6.25-2-686:
  linux-image-2.6.25-2-686/postinst/bootloader-test-error-2.6.25-2-686:
  linux-image-2.6.25-2-686/prerm/removing-running-kernel-2.6.25-2-686: true
  linux-image-2.6.25-2-686/postinst/old-initrd-link-2.6.25-2-686: true
  linux-image-2.6.25-2-686/preinst/initrd-2.6.25-2-686:
  linux-image-2.6.25-2-686/postinst/kimage-is-a-directory:
  linux-image-2.6.25-2-686/postinst/depmod-error-2.6.25-2-686: false
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.25-2-686/preinst/overwriting-modules-2.6.25-2-686: true
  linux-image-2.6.25-2-686/prerm/would-invalidate-boot-loader-2.6.25-2-686: true
  linux-image-2.6.25-2-686/preinst/elilo-initrd-2.6.25-2-686: true
  linux-image-2.6.25-2-686/postinst/depmod-error-initrd-2.6.25-2-686: false
  linux-image-2.6.25-2-686/preinst/bootloader-initrd-2.6.25-2-686: true
  linux-image-2.6.25-2-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.25-2-686/postinst/bootloader-error-2.6.25-2-686:
  linux-image-2.6.25-2-686/preinst/lilo-initrd-2.6.25-2-686: true
  linux-image-2.6.25-2-686/postinst/old-system-map-link-2.6.25-2-686: true
  linux-image-2.6.25-2-686/postinst/create-kimage-link-2.6.25-2-686: true
  linux-image-2.6.25-2-686/postinst/old-dir-initrd-link-2.6.25-2-686: true
  linux-image-2.6.25-2-686/preinst/abort-overwrite-2.6.25-2-686:
  linux-image-2.6.25-2-686/preinst/failed-to-move-modules-2.6.25-2-686:



-- Package-specific info:
** Version:
Linux version 2.6.25-2-686 (Debian 2.6.25-4) ([EMAIL PROTECTED]) (gcc version 
4.1.3 20080420 (prerelease) (Debian 4.1.2-22)) #1 SMP Tue May 27 
15:38:35 UTC 2
008

** Command line:
root=/dev/sda1 ro

** Tainted: P (1)

** Kernel log:
[1.352098] firewire_ohci: Added fw-ohci device :07:03.0, OHCI version 
1.10
[1.496103] ahci :00:1f.2: version 3.0
[1.496103] ACPI: PCI Interrupt :00:1f.2[A] - GSI 19 (level, low) - 
IRQ 19
[1.552178] firewire_core: created device fw0: GUID 0090270001c9c70a, S400
[1.512135] ahci :00:1f.2: AHCI 0001.0100 32 slots 6 ports 3 Gbps 0x3f 
impl RAID mode
[1.512196] ahci :00:1f.2: flags: 64bit ncq sntf led clo pio slum part
[1.512247] PCI: Setting latency timer of device :00:1f.2 to 64
[1.512502] scsi2 : ahci
[1.512626] scsi3 : ahci
[1.516156] scsi4 : ahci
[1.516272] scsi5 : ahci
[1.516374] scsi6 : ahci
[1.516483] scsi7 : ahci
[1.516600] ata3: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0x93225100 
irq 217
[1.516656] ata4: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0x93225180 
irq 217
[1.516712] ata5: SATA max UDMA/133 abar [EMAIL PROTECTED] 

Bug#484239: linux-image-2.6.25-2-686: kadahat in zalahat

2008-06-03 Thread maximilian attems
On Tue, Jun 03, 2008 at 12:46:32PM +0300, Shai Berger wrote:
 On Tuesday 03 June 2008 11:13:20 you wrote:
  On Tue, Jun 03, 2008 at 10:19:05AM +0300, Shai Berger wrote:
   Subject: linux-image-2.6.25-2-686: sound breaks on second login to main X
   session (vt7) Package: linux-image-2.6.25-2-686
   Version: 2.6.25-4
   Severity: normal
  
  
   This report corrects my misdiagnosis of the problem as
   reported in bug #483664.
  
   I use a desktop machine with multiple X sessions in virtual terminals.
   with kernel 2.6.25, I have this scenario, reproducibly:
  
   - After boot, first user logs into X session on vt7
   - First user logs out
   - Again, a user logs in on vt7 (I used same user, but I don't think that
   matters) - Sound dies
 
  again missing vital info, like dmesg output when that happen.
 
 There's nothing in dmesg when that happens. I only see messages in dmesg when 
 I run alsaconf to fix; I will paste them here when I am back at the machine 
 tonight. I've also looked at syslog and found nothing there.

hmm
still not buying the kernel error yet.

 
  we need more info then Sound dies
 
 
 I just don't know where to look. Any suggestions beyond dmesg 
 and /var/log/syslog?
 
  what sound application are you using?
 
 I'm not sure what you mean by sound application -- I use artsd as part of 
 KDE 3.5.9, and it reports no errors, but plays no sounds (system sounds). 
 Other applications rely on it, If I'm not mistaken.

which applications?
anyway it seems we are in userland trouble here.

post output of that script has relevant sound output
http://hg.alsa-project.org/alsa/raw-file/tip/alsa-info.sh



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]