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 [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
