Bug#546642: [Pkg-alsa-devel] Bug#546642: alsa-utils: alsactl segfaults
On Sun, 30 May 2010, Elimar Riesebieter wrote: * Cristian Ionescu-Idbohrn [091017 13:30 +0200] On Sat, 17 Oct 2009, Elimar Riesebieter wrote: [...] That looks like /var is full. REISERFS + encryptet + softraid - maybe a filesystem is corruptet. No. Not that I can see: md3 : active raid1 sda6[0] sdb6[1] 3903680 blocks [2/2] [UU] Filesystem 1K-blocks Used Available Use% Mounted on /dev/md3 3903556 1299712 2603844 34% /var /dev/md3 on /var type reiserfs (rw) And /var/log _is_ on var, isn't it? The problem might be /var isn't mounted at that point in time. Do you have an idea _where_ alsactl is run from, at that point in time? Is this bug still valid for you? No. I can't find any good or bad (segfaults) alsactl messages in my logs, at all. Is alsactl still in use? Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546642: [Pkg-alsa-devel] Bug#546642: alsa-utils: alsactl segfaults
* Cristian Ionescu-Idbohrn [091017 13:30 +0200] On Sat, 17 Oct 2009, Elimar Riesebieter wrote: [...] That looks like /var is full. REISERFS + encryptet + softraid - maybe a filesystem is corruptet. No. Not that I can see: md3 : active raid1 sda6[0] sdb6[1] 3903680 blocks [2/2] [UU] Filesystem 1K-blocks Used Available Use% Mounted on /dev/md3 3903556 1299712 2603844 34% /var /dev/md3 on /var type reiserfs (rw) And /var/log _is_ on var, isn't it? The problem might be /var isn't mounted at that point in time. Do you have an idea _where_ alsactl is run from, at that point in time? Is this bug still valid for you? Elimar -- Experience is something you don't get until just after you need it! signature.asc Description: Digital signature
Bug#546642: [Pkg-alsa-devel] Bug#546642: alsa-utils: alsactl segfaults
I just found out by accident about this: http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=7;bug=546642 That message never reached my inbox :( Picked up the mbox; trying to provide 'moreinfo', as I'm still seeing those messages: /var/log/dmesg:[ 24.038697] alsactl[1342]: segfault at 0 ip 080580db sp bf947f00 error 4 in alsactl[8048000+13000] /var/log/dmesg:[ 24.086102] alsactl[1341]: segfault at 0 ip 080580db sp bf850a90 error 4 in alsactl[8048000+13000] /var/log/dmesg:[ 24.228787] alsactl[1343]: segfault at 0 ip 080580db sp bfb3ce30 error 4 in alsactl[8048000+13000] /var/log/dmesg:[ 24.232614] alsactl[1344]: segfault at 0 ip 080580db sp bfd8b950 error 4 in alsactl[8048000+13000] /var/log/dmesg:[ 24.498297] alsactl[1454]: segfault at 0 ip 080580db sp bfa17c80 error 4 in alsactl[8048000+13000] /var/log/dmesg:[ 24.503374] alsactl[1455]: segfault at 0 ip 080580db sp bff0c3d0 error 4 in alsactl[8048000+13000] On Mon, 14 Sep 2009, Elimar Riesebieter wrote: tags 546642 moreinfo thanks * Cristian Ionescu-Idbohrn [090914 21:20 +0200] Package: alsa-utils Version: 1.0.20-3 Severity: normal Keep seeing these in my logs: # zegrep alsa /var/log/dmesg* /var/log/dmesg:[ 22.996542] alsactl[2310]: segfault at 0 ip 080580db sp bfa67800 error 4 in alsactl[8048000+13000] Could you please run 'alsactl init' and look for a core file in the dir where you startet alsactl? No segfault and no core file here. Just: , | Unknown hardware: Audigy2 SigmaTel STAC9750,51 AC97a:83847650 0x1102 0x1021 | Hardware is initialized using a guess method ` Another idea: What tells df ? Hm... Don't follow you. What kind of useful info would df provide? Another: delete /var/lib/alsa/asound.state and run alsactl store. No dice :( No segfault. Well, at the moment I can only ask my oracle. That guy stopped speaking to me a long time ago :) Can your hear sound at all and control it via 'alsamixer'? Yes and yes. Maybe the attached dmesg fragments may provide a broader picture of what's going on att boot? Cheers, -- Cristian[8.253275] usbcore: registered new interface driver usbhid [8.292041] usbhid: v2.6:USB HID core driver [8.410955] REISERFS (device md0): found reiserfs format 3.6 with standard journal [8.450375] REISERFS (device md0): using ordered data mode [8.495890] REISERFS (device md0): journal params: device md0, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 [8.577175] REISERFS (device md0): checking transaction log (md0) [8.700175] REISERFS (device md0): Using r5 hash to sort names [ 12.373102] udev: starting version 146 [ 12.480580] processor ACPI_CPU:00: registered as cooling_device0 [ 12.524920] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1 [ 12.569489] ACPI: Power Button [PWRF] [ 12.569615] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input2 [ 12.569625] ACPI: Sleep Button [SLPB] [ 12.625120] i801_smbus :00:1f.3: PCI INT B - GSI 19 (level, low) - IRQ 19 [ 12.629642] intel_rng: Firmware space is locked read-only. If you can't or [ 12.629645] intel_rng: don't want to disable this in firmware setup, and if [ 12.629647] intel_rng: you are certain that your system has a functional [ 12.629649] intel_rng: RNG, try using the 'no_fwh_detect' option. [ 12.913208] processor ACPI_CPU:01: registered as cooling_device1 [ 13.099680] input: PC Speaker as /devices/platform/pcspkr/input/input3 [ 13.214015] EMU10K1_Audigy :05:03.0: PCI INT A - GSI 19 (level, low) - IRQ 19 [ 13.217967] Audigy2 value: Special config. [ 13.862854] input: ImExPS/2 Logitech MX Mouse as /devices/platform/i8042/serio1/input/input4 ...snip... [ 17.301791] md: md9 stopped. [ 17.333753] md: bindsdb12 [ 17.381230] md: bindsda12 [ 17.412031] raid1: raid set md9 active with 2 out of 2 mirrors [ 17.444592] md9: unknown partition table [ 18.722133] Adding 1951800k swap on /dev/md1. Priority:-1 extents:1 across:1951800k [ 19.673525] i2c /dev entries driver [ 21.761694] REISERFS (device md2): found reiserfs format 3.6 with standard journal [ 21.804129] REISERFS (device md2): using ordered data mode [ 21.853763] REISERFS (device md2): journal params: device md2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 [ 21.941312] REISERFS (device md2): checking transaction log (md2) [ 22.043203] REISERFS (device md2): Using r5 hash to sort names ...snip... [ 23.318884] REISERFS (device md5): Using r5 hash to sort names [ 23.491624] REISERFS (device md6): found reiserfs format 3.6 with standard journal [ 23.536607] REISERFS (device md6): using ordered data mode [ 23.594350] REISERFS (device md6): journal params: device md6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age
Bug#546642: [Pkg-alsa-devel] Bug#546642: alsa-utils: alsactl segfaults
* Cristian Ionescu-Idbohrn [091017 11:32 +0200] I just found out by accident about this: http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=7;bug=546642 That message never reached my inbox :( Picked up the mbox; trying to provide 'moreinfo', as I'm still seeing those messages: /var/log/dmesg:[ 24.038697] alsactl[1342]: segfault at 0 ip 080580db sp bf947f00 error 4 in alsactl[8048000+13000] /var/log/dmesg:[ 24.086102] alsactl[1341]: segfault at 0 ip 080580db sp bf850a90 error 4 in alsactl[8048000+13000] /var/log/dmesg:[ 24.228787] alsactl[1343]: segfault at 0 ip 080580db sp bfb3ce30 error 4 in alsactl[8048000+13000] /var/log/dmesg:[ 24.232614] alsactl[1344]: segfault at 0 ip 080580db sp bfd8b950 error 4 in alsactl[8048000+13000] /var/log/dmesg:[ 24.498297] alsactl[1454]: segfault at 0 ip 080580db sp bfa17c80 error 4 in alsactl[8048000+13000] /var/log/dmesg:[ 24.503374] alsactl[1455]: segfault at 0 ip 080580db sp bff0c3d0 error 4 in alsactl[8048000+13000] On Mon, 14 Sep 2009, Elimar Riesebieter wrote: tags 546642 moreinfo thanks * Cristian Ionescu-Idbohrn [090914 21:20 +0200] Package: alsa-utils Version: 1.0.20-3 Severity: normal Keep seeing these in my logs: # zegrep alsa /var/log/dmesg* /var/log/dmesg:[ 22.996542] alsactl[2310]: segfault at 0 ip 080580db sp bfa67800 error 4 in alsactl[8048000+13000] Could you please run 'alsactl init' and look for a core file in the dir where you startet alsactl? No segfault and no core file here. Just: , | Unknown hardware: Audigy2 SigmaTel STAC9750,51 AC97a:83847650 0x1102 0x1021 | Hardware is initialized using a guess method ` This is probably fixed in 1.0.21 Another idea: What tells df ? Hm... Don't follow you. What kind of useful info would df provide? Sometimes a full partition (i.e. /var) confuses applications like alsactl Another: delete /var/lib/alsa/asound.state and run alsactl store. No dice :( No segfault. Well, at the moment I can only ask my oracle. That guy stopped speaking to me a long time ago :) Has gone here as well ;) Can your hear sound at all and control it via 'alsamixer'? Yes and yes. Maybe the attached dmesg fragments may provide a broader picture of what's going on att boot? Cheers, -- Cristian [...] [ 13.214015] EMU10K1_Audigy :05:03.0: PCI INT A - GSI 19 (level, low) - IRQ 19 [ 13.217967] Audigy2 value: Special config. Hmm, I can't verify this. Audigy2 is very new in alsa and I don't have such a device handy. [ 13.862854] input: ImExPS/2 Logitech MX Mouse as /devices/platform/i8042/serio1/input/input4 ...snip... [...] [ 23.893585] REISERFS (device md6): Using r5 hash to sort names [ 24.038697] alsactl[1342]: segfault at 0 ip 080580db sp bf947f00 error 4 in alsactl[8048000+13000] [ 24.086102] alsactl[1341]: segfault at 0 ip 080580db sp bf850a90 error 4 in alsactl[8048000+13000] [ 24.135645] REISERFS (device md7): found reiserfs format 3.6 with standard journal [ 24.182111] REISERFS (device md7): using ordered data mode [ 24.228787] alsactl[1343]: segfault at 0 ip 080580db sp bfb3ce30 error 4 in alsactl[8048000+13000] [ 24.232614] alsactl[1344]: segfault at 0 ip 080580db sp bfd8b950 error 4 in alsactl[8048000+13000] That looks like /var is full. REISERFS + encryptet + softraid - maybe a filesystem is corruptet. [...] Please check your filesystems, try 1.0.21 and report again. Elimar -- Excellent day for drinking heavily. Spike the office water cooler;-) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546642: [Pkg-alsa-devel] Bug#546642: alsa-utils: alsactl segfaults
On Sat, 17 Oct 2009, Elimar Riesebieter wrote: Could you please run 'alsactl init' and look for a core file in the dir where you startet alsactl? No segfault and no core file here. Just: , | Unknown hardware: Audigy2 SigmaTel STAC9750,51 AC97a:83847650 0x1102 0x1021 | Hardware is initialized using a guess method ` This is probably fixed in 1.0.21 Or not, as this is what I'm using now: # apt-cache policy alsa-utils alsa-utils: Installed: 1.0.21-1 Candidate: 1.0.21-1 Another idea: What tells df ? Hm... Don't follow you. What kind of useful info would df provide? Sometimes a full partition (i.e. /var) confuses applications like alsactl I see. That's not the case on this box. [ 23.893585] REISERFS (device md6): Using r5 hash to sort names /dev/md6 on /usr/local type reiserfs (rw) [ 24.038697] alsactl[1342]: segfault at 0 ip 080580db sp bf947f00 error 4 in alsactl[8048000+13000] [ 24.086102] alsactl[1341]: segfault at 0 ip 080580db sp bf850a90 error 4 in alsactl[8048000+13000] [ 24.135645] REISERFS (device md7): found reiserfs format 3.6 with standard journal [ 24.182111] REISERFS (device md7): using ordered data mode /dev/md7 on /opt type reiserfs (rw) [ 24.228787] alsactl[1343]: segfault at 0 ip 080580db sp bfb3ce30 error 4 in alsactl[8048000+13000] [ 24.232614] alsactl[1344]: segfault at 0 ip 080580db sp bfd8b950 error 4 in alsactl[8048000+13000] That looks like /var is full. REISERFS + encryptet + softraid - maybe a filesystem is corruptet. No. Not that I can see: md3 : active raid1 sda6[0] sdb6[1] 3903680 blocks [2/2] [UU] Filesystem 1K-blocks Used Available Use% Mounted on /dev/md3 3903556 1299712 2603844 34% /var /dev/md3 on /var type reiserfs (rw) And /var/log _is_ on var, isn't it? The problem might be /var isn't mounted at that point in time. Do you have an idea _where_ alsactl is run from, at that point in time? Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
