Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mattia Bertoni <mattia.b89@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: bug
Date: Thu, 08 Aug 2013 11:55:50 +0200	[thread overview]
Message-ID: <52036B26.10906@gmail.com> (raw)
In-Reply-To: <s5hk3jwa75k.wl%tiwai@suse.de>

fortunately I have had this problem only once and more than one month 
ago (15 Jun)
but unfortunately I can't reproduce it because it appeared casually

I'm not a newbie and I knowthis is not the right way to report an issue, 
but these are the all and only information that I have;
anyway other important info are (with the hope you can fix this issue):

Asus A8N-E with nForce4 ultra - CK804 AC'97 Audio Controller (rev a2)
Realtek ALC850 rev 0 at irq 20
snd_intel8x0


archlinux x86_64
kernel3.9.5-1
alsa 1.0.27.1-2
pulseaudio 4.0-2
jack2 1.9.9.5-3

finally I uploaded the output of alsa-info.sh
BUT because I can't reproduce the bug I don't know if this is useful, 
also because it's the output of today in which software is newer:

http://pastebin.com/5SsiVh2u





On 08/08/13 11:00, Takashi Iwai wrote:
> At Wed, 07 Aug 2013 19:14:40 +0200,
> Mattia Bertoni wrote:
>> finally I can report a bug which I encountered some time ago; I send you
>> the important part of the entire log, which is to much big to be posted:
> You didn't write what's your problem at all, so no one understands
> what to do with it.
>
> In addition, the fundamental information is missing: which machine,
> which distro, which kernel and sound systems, and how to reproduce the
> problem.  The first few items can be covered by providing the
> alsa-info.sh output taken from your machine (at best take it after the
> problem appears).
>
>
> thanks,
>
> Takashi

  reply	other threads:[~2013-08-08  9:55 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <520268D8.3000807@gmail.com>
2013-08-07 17:14 ` bug Mattia Bertoni
2013-08-08  8:44   ` bug Mattia Bertoni
2013-08-08  9:00   ` bug Takashi Iwai
2013-08-08  9:55     ` Mattia Bertoni [this message]
2013-08-08 10:12       ` bug Takashi Iwai
2013-08-08 10:44         ` bug Mattia Bertoni
2013-08-08 10:49           ` bug Takashi Iwai
2015-03-28 14:03 bug Nikita N.
2015-03-30  7:19 ` bug Clemens Ladisch
2015-03-30 10:27   ` bug Nikita N.
2015-03-30 11:13     ` bug Clemens Ladisch
2015-03-30 14:37       ` bug Nikita N.
2015-03-31  7:18         ` bug Eliot Blennerhassett
2015-03-31  8:19           ` bug Nikita N.
2015-03-31  8:38             ` bug Clemens Ladisch
2015-03-31  9:05               ` bug Nikita N.
2015-03-31 12:42                 ` bug Clemens Ladisch
2015-03-31  8:24         ` bug Ricard Wanderlof
2015-03-31  8:56           ` bug Nikita N.
2015-03-31  9:14             ` bug Ricard Wanderlof
2015-03-31 10:26               ` bug Maarten de Boer
2015-03-31 10:49                 ` bug Nikita N.
2015-03-31 11:05                   ` bug Maarten de Boer
2015-03-31 11:44                   ` bug Ricard Wanderlof
2015-03-31  8:54         ` bug Eliot Blennerhassett
  -- strict thread matches above, loose matches on Subject: below --
2019-09-02  3:52 bug liebrecht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52036B26.10906@gmail.com \
    --to=mattia.b89@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox