bug

bug

[Nikita N.]

is any programmer listening here?

-- 
http://www.fastmail.com - A no graphics, no pop-ups email service

Re: bug

[Clemens Ladisch]

Nikita N. wrote:
> is any programmer listening here?

No.

But several are reading here.


Regards,
Clemens

Re: bug

[Nikita N.]

is anybody here aware that latest alsamixergui has a bug capable of
produce irreversible damage to internal laptop speakers?
-- 
  Nikita N.
  nikitan@operamail.com


On Mon, Mar 30, 2015, at 12:19 AM, Clemens Ladisch wrote:
> Nikita N. wrote:
> > is any programmer listening here?
> 
> No.
> 
> But several are reading here.
> 
> 
> Regards,
> Clemens

-- 
http://www.fastmail.com - Or how I learned to stop worrying and
                          love email again

Re: bug

[Clemens Ladisch]

Nikita N. wrote:
> is anybody here aware that latest alsamixergui

Despite its name, this program was not written by the ALSA project.

> has a bug capable of
> produce irreversible damage to internal laptop speakers?

What is the bug?


Regards,
Clemens

Re: bug

[Nikita N.]

We are the devs involved in dCore porting, and that is one of our users
report:
http://forum.tinycorelinux.net/index.php/topic,18225

We verified that in few of our legacy laptops.
It didn't reproduce for every laptop, but indeed in a couple of them,
the temperature of the speakers reached extremes levels in few seconds,
only unplugging the AC/DC cable saved them.
This is a serious problem in our opinion, and we would hate to see our
dCore reputation spoiled.
We hate to admit, but it is *NOT* our bug, and would hate to see this
bug reverse engineered into a virus/malware (on Linux, or other OS) and
see ourselves blamed for it.
So we would like to keep the incident quiet, and we are going to remove
that thread from our forum.
On the other side, we would expect any action from ALSA project in
removing that tool and/or exposing the real individual/s guilty of
writing that tool.

Thank you for your attentions and looking forward your feedback.
-- 
  Nikita N.
  nikitan@operamail.com


On Mon, Mar 30, 2015, at 04:13 AM, Clemens Ladisch wrote:
> Nikita N. wrote:
> > is anybody here aware that latest alsamixergui
> 
> Despite its name, this program was not written by the ALSA project.
> 
> > has a bug capable of
> > produce irreversible damage to internal laptop speakers?
> 
> What is the bug?
> 
> 
> Regards,
> Clemens

-- 
http://www.fastmail.com - IMAP accessible web-mail

Re: bug

[Eliot Blennerhassett]

On 31/03/15 03:37, Nikita N. wrote:
> We are the devs involved in dCore porting, and that is one of our users
> report:
> http://forum.tinycorelinux.net/index.php/topic,18225
> 
> We verified that in few of our legacy laptops.
> It didn't reproduce for every laptop, but indeed in a couple of them,
> the temperature of the speakers reached extremes levels in few seconds,
> only unplugging the AC/DC cable saved them.

This is a hardware problem, quite likely reproducible in any OS that
gives control of the

> This is a serious problem in our opinion, and we would hate to see our
> dCore reputation spoiled.
> We hate to admit, but it is *NOT* our bug, and would hate to see this
> bug reverse engineered into a virus/malware (on Linux, or other OS) and
> see ourselves blamed for it.
> So we would like to keep the incident quiet, and we are going to remove
> that thread from our forum.
> On the other side, we would expect any action from ALSA project in
> removing that tool and/or exposing the real individual/s guilty of
> writing that tool.

As Clemens has pointed out, "the ALSA project" cannot remove the tool,
as it is not part of the ALSA project.
However, probably any software that can control all the volumes is
capable of reproducing the same effect.

And in my opinion, you are blaming the wrong party here. As various
posters on your forum thread point out, blame the hardware manufacturer
or the particular user who has done something crazy and now wants to
find some other "guilty" party.

1: User setting ALL volumes to maximum (?) probably causes feedback from
microphone to speakers.   (Yes I can confirm that happens on my laptop
with mic gain set to 20dB below maximum). You can do the same on your
home stereo and blow your speakers, nobody will have any sympathy.

2: The laptop manufacturer has apparently not designed the hardware
robustly, i.e. the speakers are too puny for the maximum output of the
audio amplifier.

3: There is no way for the soundcard driver to know what the limits are,
it just exposes the controls for the user to set.

regards

Eliot

Re: bug

[Nikita N.]

> And in my opinion, you are blaming the wrong party here.
we are not blaming anybody.
We simply want to avoid any more of Our users to damage their speakers.
Most of users are not omniscient, if they are given a tool capable of
creating damage, at least they deserve a warning from the tool/provider.
If ALSA can't fix/remove that tool, we kindly ask you to point us to the
individual who programmed it, and we will contact him/her directly.
Unless that is not a secret.
If that is a secret and/or we will not receive feedback, then we will
expose clearly to the public that tool as a virus/malware, and inform
the antivirus authorities about it.

> (Yes I can confirm that happens on my laptop with mic gain set to 20dB below maximum).
Thank you very much for your confirmation, so in the meantime we start
as blacklisting that tool from our repos.

-- 
  Nikita N.
  nikitan@operamail.com


On Tue, Mar 31, 2015, at 12:18 AM, Eliot Blennerhassett wrote:
> On 31/03/15 03:37, Nikita N. wrote:
> > We are the devs involved in dCore porting, and that is one of our users
> > report:
> > http://forum.tinycorelinux.net/index.php/topic,18225
> > 
> > We verified that in few of our legacy laptops.
> > It didn't reproduce for every laptop, but indeed in a couple of them,
> > the temperature of the speakers reached extremes levels in few seconds,
> > only unplugging the AC/DC cable saved them.
> 
> This is a hardware problem, quite likely reproducible in any OS that
> gives control of the
> 
> > This is a serious problem in our opinion, and we would hate to see our
> > dCore reputation spoiled.
> > We hate to admit, but it is *NOT* our bug, and would hate to see this
> > bug reverse engineered into a virus/malware (on Linux, or other OS) and
> > see ourselves blamed for it.
> > So we would like to keep the incident quiet, and we are going to remove
> > that thread from our forum.
> > On the other side, we would expect any action from ALSA project in
> > removing that tool and/or exposing the real individual/s guilty of
> > writing that tool.
> 
> As Clemens has pointed out, "the ALSA project" cannot remove the tool,
> as it is not part of the ALSA project.
> However, probably any software that can control all the volumes is
> capable of reproducing the same effect.
> 
> And in my opinion, you are blaming the wrong party here. As various
> posters on your forum thread point out, blame the hardware manufacturer
> or the particular user who has done something crazy and now wants to
> find some other "guilty" party.
> 
> 1: User setting ALL volumes to maximum (?) probably causes feedback from
> microphone to speakers.   (Yes I can confirm that happens on my laptop
> with mic gain set to 20dB below maximum). You can do the same on your
> home stereo and blow your speakers, nobody will have any sympathy.
> 
> 2: The laptop manufacturer has apparently not designed the hardware
> robustly, i.e. the speakers are too puny for the maximum output of the
> audio amplifier.
> 
> 3: There is no way for the soundcard driver to know what the limits are,
> it just exposes the controls for the user to set.
> 
> regards
> 
> Eliot

-- 
http://www.fastmail.com - Or how I learned to stop worrying and
                          love email again

Re: bug

[Ricard Wanderlof]

On Mon, 30 Mar 2015, Nikita N. wrote:

> We are the devs involved in dCore porting, and that is one of our users
> report:
> http://forum.tinycorelinux.net/index.php/topic,18225
> 
> We verified that in few of our legacy laptops.
> It didn't reproduce for every laptop, but indeed in a couple of them,
> the temperature of the speakers reached extremes levels in few seconds,
> only unplugging the AC/DC cable saved them.
> This is a serious problem in our opinion, and we would hate to see our
> dCore reputation spoiled.
> We hate to admit, but it is *NOT* our bug, and would hate to see this
> bug reverse engineered into a virus/malware (on Linux, or other OS) and
> see ourselves blamed for it.
> So we would like to keep the incident quiet, and we are going to remove
> that thread from our forum.
> On the other side, we would expect any action from ALSA project in
> removing that tool and/or exposing the real individual/s guilty of
> writing that tool.

First of all, I can't say I'm representing the ALSA project or anyone else 
in this matter, so the following is just my personal opinion. Furthermore 
I have no real experience with the mixer application under discussion 
(alsamixergui), but on the face of it it just looks like any mixer 
application.

>From the thread linked above, it seems that if someone maxes out all 
controls in the mixer, this results in a high-pitched whine in the 
speakers, which on certain laptops seem to cause the destruction of 
something in the machine (likely the speakers themselves). It is further 
speculated in the thread that what might be happening is acoustic feedback 
from the speakers to the microphone, which would make sense given the 
results, but would seem strange from a system design point of view.

First of all, it would seem that this wouldn't be dependent on a 
particular mixer application such as alsamixergui, but should be able to 
happen with any mixer application, given the appropriate settings.

Secondly, if you believe that alsamixergui specifically is missbehaving, 
why don't you just take it out of your distribution (dCore)?

Thirdly, and perhaps most importantly, this seems to be a hardware 
problem. If the drive capability of the laptops's output stage is too much 
for the speakers, then there is a serious design flaw in the hardware. 
Given the proliferation of cheap PC hardware this is not surprising, but 
it is hardly a software problem.

And finally, as Clemens said, alsamixergui is not created by the ALSA 
project, so this mailing list is the wrong place to look if none other 
than for that particular reason.

/Ricard
-- 
Ricard Wolf Wanderlöf                           ricardw(at)axis.com
Axis Communications AB, Lund, Sweden            www.axis.com
Phone +46 46 272 2016                           Fax +46 46 13 61 30

Re: bug

[Clemens Ladisch]

Nikita N. wrote:
> If ALSA can't fix/remove that tool, we kindly ask you to point us to the
> individual who programmed it, and we will contact him/her directly.

http://www.iua.upf.es/~mdeboer/projects/alsamixergui/

> If that is a secret and/or we will not receive feedback, then we will
> expose clearly to the public that tool as a virus/malware, and inform
> the antivirus authorities about it.

Please note that _every_ mixer application on _every_ OS might be able
to set the controls to those dangerous values.


Regards,
Clemens

Re: potential speaker burnout

[Eliot Blennerhassett]

On 31/03/15 21:19, Nikita N. wrote:
>> And in my opinion, you are blaming the wrong party here.
> we are not blaming anybody.

You talk about finding the person who is "guilty"

>> (Yes I can confirm that happens on my laptop with mic gain set to 20dB below maximum).

> Thank you very much for your confirmation, so in the meantime we start
> as blacklisting that tool from our repos.

I agree it would be upsetting to have your laptop speakers go up in smoke.

But I reiterate, it is not the alsamixergui tool. ANY tool that is
capable of adjusting the underlying controls of the soundcard is capable
of reproducing the effect.  I.e. commandline "amixer", terminal
"alsamixer', possibly others...

You would be better to blacklist the problematic laptop hardware, not
these control apps.

The one thing maybe worth thinking about is whether there is any useful
purpose for the control that enables direct feed from microphone to
speakers?  This is something that is provided by the underlying sound
driver, and would need to be "fixed" there.
I.e. your distro would have to patch drivers before building the kernel.

Re: bug

[Eliot Blennerhassett]

(Note - this email now off-list)

On 31/03/15 03:37, Nikita N. wrote:
> This is a serious problem in our opinion, and we would hate to see our
> dCore reputation spoiled.

This problem probably exists in all distros, and probably other OSes as
well.  Apparently it hasn't spoiled their reputation yet.

Given that you're building a lightweight distro, I'd suggest you drop
alsamixergui anyway; A terminal with alsamixer will do the same job,
just not as pretty.

Re: bug

[Nikita N.]

> First of all, I can't say I'm representing the ALSA project or anyone else 
> in this matter, so the following is just my personal opinion.
As we already wrote, we are not blaming you or ALSA.

> particular mixer application such as alsamixergui, but should be able to 
> happen with any mixer application, given the appropriate settings.
That is indeed what we are afraid, if anybody will have the brilliant
idea to reverse engineer that tool to a more damaging level in a
virus/malware , and make its effect unstoppable. 

> Secondly, if you believe that alsamixergui specifically is missbehaving, 
> why don't you just take it out of your distribution (dCore)?
as we wrote, we are going to do this.

> Given the proliferation of cheap PC hardware this is not surprising
as you say, given the proliferation of cheap PC hardware, a
proliferation of such virus/malware could upset not only our users.

> it is hardly a software problem.
I personally don't agree with that.
As we wrote, not everybody is omniscient, I personally was not aware of
this issue, before was pointed out.
Without warnings, even a Teddy Bear can be dangerous.

> alsamixergui is not created by the ALSA 
> project, so this mailing list is the wrong place to look if none other 
> than for that particular reason.
Sure, we would be very grateful if you could point that out, so we can
contact the individual who programmed this tool
Unless it's not a secret or there is smtng to hide.
 
-- 
  Nikita N.
  nikitan@operamail.com


On Tue, Mar 31, 2015, at 01:24 AM, Ricard Wanderlof wrote:
> 
> On Mon, 30 Mar 2015, Nikita N. wrote:
> 
> > We are the devs involved in dCore porting, and that is one of our users
> > report:
> > http://forum.tinycorelinux.net/index.php/topic,18225
> > 
> > We verified that in few of our legacy laptops.
> > It didn't reproduce for every laptop, but indeed in a couple of them,
> > the temperature of the speakers reached extremes levels in few seconds,
> > only unplugging the AC/DC cable saved them.
> > This is a serious problem in our opinion, and we would hate to see our
> > dCore reputation spoiled.
> > We hate to admit, but it is *NOT* our bug, and would hate to see this
> > bug reverse engineered into a virus/malware (on Linux, or other OS) and
> > see ourselves blamed for it.
> > So we would like to keep the incident quiet, and we are going to remove
> > that thread from our forum.
> > On the other side, we would expect any action from ALSA project in
> > removing that tool and/or exposing the real individual/s guilty of
> > writing that tool.
> 
> First of all, I can't say I'm representing the ALSA project or anyone
> else 
> in this matter, so the following is just my personal opinion. Furthermore 
> I have no real experience with the mixer application under discussion 
> (alsamixergui), but on the face of it it just looks like any mixer 
> application.
> 
> From the thread linked above, it seems that if someone maxes out all 
> controls in the mixer, this results in a high-pitched whine in the 
> speakers, which on certain laptops seem to cause the destruction of 
> something in the machine (likely the speakers themselves). It is further 
> speculated in the thread that what might be happening is acoustic
> feedback 
> from the speakers to the microphone, which would make sense given the 
> results, but would seem strange from a system design point of view.
> 
> First of all, it would seem that this wouldn't be dependent on a 
> particular mixer application such as alsamixergui, but should be able to 
> happen with any mixer application, given the appropriate settings.
> 
> Secondly, if you believe that alsamixergui specifically is missbehaving, 
> why don't you just take it out of your distribution (dCore)?
> 
> Thirdly, and perhaps most importantly, this seems to be a hardware 
> problem. If the drive capability of the laptops's output stage is too
> much 
> for the speakers, then there is a serious design flaw in the hardware. 
> Given the proliferation of cheap PC hardware this is not surprising, but 
> it is hardly a software problem.
> 
> And finally, as Clemens said, alsamixergui is not created by the ALSA 
> project, so this mailing list is the wrong place to look if none other 
> than for that particular reason.
> 
> /Ricard
> -- 
> Ricard Wolf Wanderlöf                           ricardw(at)axis.com
> Axis Communications AB, Lund, Sweden            www.axis.com
> Phone +46 46 272 2016                           Fax +46 46 13 61 30

-- 
http://www.fastmail.com - Or how I learned to stop worrying and
                          love email again

Re: bug

[Nikita N.]

> http://www.iua.upf.es/~mdeboer/projects/alsamixergui/
this link is broken, please provide a correct one, thanks.

> Please note that _every_ mixer application on _every_ OS might be able
> to set the controls to those dangerous values.
is it "might" or it is? Is also your alsamixer textual version tool,
capable of speakers burnout?
Thanks

-- 
  Nikita N.
  nikitan@operamail.com


On Tue, Mar 31, 2015, at 01:38 AM, Clemens Ladisch wrote:
> Nikita N. wrote:
> > If ALSA can't fix/remove that tool, we kindly ask you to point us to the
> > individual who programmed it, and we will contact him/her directly.
> 
> http://www.iua.upf.es/~mdeboer/projects/alsamixergui/
> 
> > If that is a secret and/or we will not receive feedback, then we will
> > expose clearly to the public that tool as a virus/malware, and inform
> > the antivirus authorities about it.
> 
> Please note that _every_ mixer application on _every_ OS might be able
> to set the controls to those dangerous values.
> 
> 
> Regards,
> Clemens

-- 
http://www.fastmail.com - Does exactly what it says on the tin

Re: bug

[Ricard Wanderlof]

On Tue, 31 Mar 2015, Nikita N. wrote:

> > alsamixergui is not created by the ALSA 
> > project, so this mailing list is the wrong place to look if none other 
> > than for that particular reason.
> Sure, we would be very grateful if you could point that out, so we can
> contact the individual who programmed this tool
> Unless it's not a secret or there is smtng to hide.

I have no idea who wrote it, Clemens posted a link but at to me it seems 
dead, there should be something in the source code (perhaps that's where 
he got it frome?). Could very well be that it was written by someone who 
has since moved on to other things so that any links or email adresses are 
outdated. It's not necessarily a secret, it could just be unknown at this 
point, and if the person who wrote it is not actively maintaining it any 
more there's probably little to be gained from contacting him.

/Ricard
-- 
Ricard Wolf Wanderlöf                           ricardw(at)axis.com
Axis Communications AB, Lund, Sweden            www.axis.com
Phone +46 46 272 2016                           Fax +46 46 13 61 30

Re: Speaker burnout

[David Henningsson]

On 2015-03-30 16:37, Nikita N. wrote:
> We are the devs involved in dCore porting, and that is one of our users
> report:
> http://forum.tinycorelinux.net/index.php/topic,18225
>
> We verified that in few of our legacy laptops.
> It didn't reproduce for every laptop, but indeed in a couple of them,
> the temperature of the speakers reached extremes levels in few seconds,
> only unplugging the AC/DC cable saved them.
> This is a serious problem in our opinion, and we would hate to see our
> dCore reputation spoiled.
> We hate to admit, but it is *NOT* our bug, and would hate to see this
> bug reverse engineered into a virus/malware (on Linux, or other OS) and
> see ourselves blamed for it.
> So we would like to keep the incident quiet, and we are going to remove
> that thread from our forum.
> On the other side, we would expect any action from ALSA project in
> removing that tool and/or exposing the real individual/s guilty of
> writing that tool.
>
> Thank you for your attentions and looking forward your feedback.

My opinion is that; it would have been better if the laptop had hardware 
protection against these kinds of failures, but now that it apparently 
has not, it should be fixed at the second best level, i e, kernel drivers.

Preferrably by not exposing (at least not by default) the highest levels 
of speaker output.

If you have any concrete examples (alsa-info please!) of speakers that 
can be burned out, and you know a maximum speaker volume where this 
never happens, I think we should artifically lower the max volume to 
this level so that no mixer application can set the speaker volume 
higher than that.

-- 
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic

Re: Speaker burnout

[Nikita N.]

> If you have any concrete examples (alsa-info please!) of speakers that 
> can be burned out, and you know a maximum speaker volume where this 
As we said, that is not our bug, we are not audio experts, nor any of us
is interested in audio matters.
Nevertheless, we all embrace the Debian/Ubuntu philosophy and Manifesto,
to help in creating a better world, in our small.
For this reason, we feel like we can't just ignore this issue, so
something has to be done to fix it - by who has the proper expertise.
"Ubuntu" is an ancient African word, meaning "humanity to others". The
Ubuntu distribution brings the spirit of Ubuntu to the software world.
We don't bring "humanity to others", programming or distributing any
software which can damage the hardware.


On Tue, Mar 31, 2015, at 02:34 AM, David Henningsson wrote:
> 
> 
> On 2015-03-30 16:37, Nikita N. wrote:
> > We are the devs involved in dCore porting, and that is one of our users
> > report:
> > http://forum.tinycorelinux.net/index.php/topic,18225
> >
> > We verified that in few of our legacy laptops.
> > It didn't reproduce for every laptop, but indeed in a couple of them,
> > the temperature of the speakers reached extremes levels in few seconds,
> > only unplugging the AC/DC cable saved them.
> > This is a serious problem in our opinion, and we would hate to see our
> > dCore reputation spoiled.
> > We hate to admit, but it is *NOT* our bug, and would hate to see this
> > bug reverse engineered into a virus/malware (on Linux, or other OS) and
> > see ourselves blamed for it.
> > So we would like to keep the incident quiet, and we are going to remove
> > that thread from our forum.
> > On the other side, we would expect any action from ALSA project in
> > removing that tool and/or exposing the real individual/s guilty of
> > writing that tool.
> >
> > Thank you for your attentions and looking forward your feedback.
> 
> My opinion is that; it would have been better if the laptop had hardware 
> protection against these kinds of failures, but now that it apparently 
> has not, it should be fixed at the second best level, i e, kernel
> drivers.
> 
> Preferrably by not exposing (at least not by default) the highest levels 
> of speaker output.
> 
> If you have any concrete examples (alsa-info please!) of speakers that 
> can be burned out, and you know a maximum speaker volume where this 
> never happens, I think we should artifically lower the max volume to 
> this level so that no mixer application can set the speaker volume 
> higher than that.
> 
> -- 
> David Henningsson, Canonical Ltd.
> https://launchpad.net/~diwic

-- 
http://www.fastmail.com - The professional email service

Re: bug

[Maarten de Boer]

Hello,

I am the author of alsamixergui. I am not actively maintaining alsamixergui anymore (and haven’t been for years). It is pretty much coincidence that I saw this mail thread; a slightly more informative subject would have helped.

There is not much that I can add to this thread (thanks everyone for your replies), but in short:

- alsamixergui is just a graphical frontend, and exposes the mixer capabilities of the sound card in the same way alsamixer, amixer or any other alsa mixer does, so this is not alsamixergui specific. (strongly based on the alsamixer code (verbatim) with fltk gui code added to it.).

- this is not a software problem, this is a hardware problem. The user adjusts the mixer to cause a feedback between speaker and internal microphone, and leaves this running for >30 seconds, and his hardware can’t deal with it. It is probably not even operating system specific.

Finally, I really don’t like the tone you use, Nikita, particularly your talk of “exposing the individuals guilty” and your accusations of secrecy. And "expose clearly to the public that tool as a virus/malware, and inform the antivirus authorities about it.”, really? Good luck with that.

If you want to blacklist alsamixergui from your distro, please go ahead, but don’t forget to blacklist alsamixer and amixer too, as well as any other alsa mixer front ends.

Maarten


On 31 Mar 2015, at 11:14, Ricard Wanderlof <ricard.wanderlof@axis.com> wrote:

> 
> On Tue, 31 Mar 2015, Nikita N. wrote:
> 
>>> alsamixergui is not created by the ALSA 
>>> project, so this mailing list is the wrong place to look if none other 
>>> than for that particular reason.
>> Sure, we would be very grateful if you could point that out, so we can
>> contact the individual who programmed this tool
>> Unless it's not a secret or there is smtng to hide.
> 
> I have no idea who wrote it, Clemens posted a link but at to me it seems 
> dead, there should be something in the source code (perhaps that's where 
> he got it frome?). Could very well be that it was written by someone who 
> has since moved on to other things so that any links or email adresses are 
> outdated. It's not necessarily a secret, it could just be unknown at this 
> point, and if the person who wrote it is not actively maintaining it any 
> more there's probably little to be gained from contacting him.
> 
> /Ricard
> -- 
> Ricard Wolf Wanderlöf                           ricardw(at)axis.com
> Axis Communications AB, Lund, Sweden            www.axis.com
> Phone +46 46 272 2016                           Fax +46 46 13 61 30
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Re: Speaker burnout

[David Henningsson]

On 2015-03-31 12:06, Nikita N. wrote:
>> If you have any concrete examples (alsa-info please!) of speakers that
>> can be burned out, and you know a maximum speaker volume where this
> As we said, that is not our bug, we are not audio experts, nor any of us
> is interested in audio matters.

Here's my suggestion how to move forward on this:

  1) Gather consensus that limit the maximum volume on internal speakers 
is the right way forward. Takashi, Clemens, anyone against that strategy?

  2) From the person with the hardware, we will need alsa-info ( 
https://wiki.ubuntu.com/Audio/AlsaInfo ), and also the max volume where 
this does not happen. Is -6 dB good enough? -12 dB? I don't know - this 
is something someone with the hardware must tell us, it cannot simply be 
guessed.

  3) I or someone else can write a kernel patch that limits the maximum 
volume of the speakers to the amount deducted from point 2). Considering 
that we're actually dealing with hardware breakage, this should be sent 
to stable as well. Then no userspace application can set the volume 
higher than our limit.

-- 
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic

Re: bug

[Nikita N.]

Dear Maarten de Boer,
as you read from many voices here, your software is verified can damage
the speakers, if not used somehow correctly.
The definition of correctly is still to us unknown, nor you are giving
us any hope in that.
We were hoping in some form of amend from yourself, about the dangerous
software you produced and distributed to public.
We were hoping in some form of bug fix or any professional approach to
solving that issue.
We were hoping at least in a simple warning popping up from your tool,
when user sets any "hazardous" levels.
We were hoping at least-least in a warning popping up from your tool at
runtime, something like "Warning: improper settings for this level, this
level and this might result in damages to your audio devices".
But, we only see a nice turnaround "There is not much that I can add".
Your program does not respect the minimum requirement for a software to
be published, such as being "reasonably" bug free.
As for "bug" is intended a software which is limited in creating
software problems.
While instead, your tool expands to a whole new, and more dangerous
level - hardware damage.
Hence your software, as is, doesn't respect our Debian/Ubuntu
philosophy.
So, at this point "There is not much that" we can add.
We also wish you "Good luck with that."

On Tue, Mar 31, 2015, at 03:26 AM, Maarten de Boer wrote:
> Hello,
> 
> I am the author of alsamixergui. I am not actively maintaining
> alsamixergui anymore (and haven’t been for years). It is pretty much
> coincidence that I saw this mail thread; a slightly more informative
> subject would have helped.
> 
> There is not much that I can add to this thread (thanks everyone for your
> replies), but in short:
> 
> - alsamixergui is just a graphical frontend, and exposes the mixer
> capabilities of the sound card in the same way alsamixer, amixer or any
> other alsa mixer does, so this is not alsamixergui specific. (strongly
> based on the alsamixer code (verbatim) with fltk gui code added to it.).
> 
> - this is not a software problem, this is a hardware problem. The user
> adjusts the mixer to cause a feedback between speaker and internal
> microphone, and leaves this running for >30 seconds, and his hardware
> can’t deal with it. It is probably not even operating system specific.
> 
> Finally, I really don’t like the tone you use, Nikita, particularly your
> talk of “exposing the individuals guilty” and your accusations of
> secrecy. And "expose clearly to the public that tool as a virus/malware,
> and inform the antivirus authorities about it.”, really? Good luck with
> that.
> 
> If you want to blacklist alsamixergui from your distro, please go ahead,
> but don’t forget to blacklist alsamixer and amixer too, as well as any
> other alsa mixer front ends.
> 
> Maarten
> 
> 
> On 31 Mar 2015, at 11:14, Ricard Wanderlof <ricard.wanderlof@axis.com>
> wrote:
> 
> > 
> > On Tue, 31 Mar 2015, Nikita N. wrote:
> > 
> >>> alsamixergui is not created by the ALSA 
> >>> project, so this mailing list is the wrong place to look if none other 
> >>> than for that particular reason.
> >> Sure, we would be very grateful if you could point that out, so we can
> >> contact the individual who programmed this tool
> >> Unless it's not a secret or there is smtng to hide.
> > 
> > I have no idea who wrote it, Clemens posted a link but at to me it seems 
> > dead, there should be something in the source code (perhaps that's where 
> > he got it frome?). Could very well be that it was written by someone who 
> > has since moved on to other things so that any links or email adresses are 
> > outdated. It's not necessarily a secret, it could just be unknown at this 
> > point, and if the person who wrote it is not actively maintaining it any 
> > more there's probably little to be gained from contacting him.
> > 
> > /Ricard
> > -- 
> > Ricard Wolf Wanderlöf                           ricardw(at)axis.com
> > Axis Communications AB, Lund, Sweden            www.axis.com
> > Phone +46 46 272 2016                           Fax +46 46 13 61 30
> > _______________________________________________
> > Alsa-devel mailing list
> > Alsa-devel@alsa-project.org
> > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> 

-- 
http://www.fastmail.com - Access all of your messages and folders
                          wherever you are

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Re: Speaker burnout

[Alexander E. Patrakov]

31.03.2015 15:43, David Henningsson wrote:
>   2) From the person with the hardware, we will need alsa-info (
> https://wiki.ubuntu.com/Audio/AlsaInfo ), and also the max volume where
> this does not happen. Is -6 dB good enough? -12 dB? I don't know - this
> is something someone with the hardware must tell us, it cannot simply be
> guessed.

Another useful piece of information would be what Windows does here.

Please generate a -36 dB 1000 Hz sine wave in Audacity, save as a wav 
file, play at the maximum volume in Windows, record with a mobile phone 
(you can use software such as Tape Machine which turns AGC off in the 
phone). Ideally, the mobile phone should be placed on the table to avoid 
movements. Play the same wav file in linux (with a known safe 
attenuation), also record the sound without moving the mobile phone. 
Compare the recordings in Audacity to find out the attenuation done by 
Windows.

-- 
Alexander E. Patrakov

Re: bug

[Maarten de Boer]

Hi,

As I tried to explain, this is not specific for alsamixergui, and it is not a bug, as it is a hardware problem. There is no way for the software to know what would be these “hazardous” levels, as this is hardware specific. And again, alsamixergui is just a graphical frontend. The command line alsamixer does the same thing.

Maarten

On 31 Mar 2015, at 12:49, Nikita N. <nikitan@operamail.com> wrote:

> Dear Maarten de Boer,
> as you read from many voices here, your software is verified can damage
> the speakers, if not used somehow correctly.
> The definition of correctly is still to us unknown, nor you are giving
> us any hope in that.
> We were hoping in some form of amend from yourself, about the dangerous
> software you produced and distributed to public.
> We were hoping in some form of bug fix or any professional approach to
> solving that issue.
> We were hoping at least in a simple warning popping up from your tool,
> when user sets any "hazardous" levels.
> We were hoping at least-least in a warning popping up from your tool at
> runtime, something like "Warning: improper settings for this level, this
> level and this might result in damages to your audio devices".
> But, we only see a nice turnaround "There is not much that I can add".
> Your program does not respect the minimum requirement for a software to
> be published, such as being "reasonably" bug free.
> As for "bug" is intended a software which is limited in creating
> software problems.
> While instead, your tool expands to a whole new, and more dangerous
> level - hardware damage.
> Hence your software, as is, doesn't respect our Debian/Ubuntu
> philosophy.
> So, at this point "There is not much that" we can add.
> We also wish you "Good luck with that."
> 
> On Tue, Mar 31, 2015, at 03:26 AM, Maarten de Boer wrote:
>> Hello,
>> 
>> I am the author of alsamixergui. I am not actively maintaining
>> alsamixergui anymore (and haven’t been for years). It is pretty much
>> coincidence that I saw this mail thread; a slightly more informative
>> subject would have helped.
>> 
>> There is not much that I can add to this thread (thanks everyone for your
>> replies), but in short:
>> 
>> - alsamixergui is just a graphical frontend, and exposes the mixer
>> capabilities of the sound card in the same way alsamixer, amixer or any
>> other alsa mixer does, so this is not alsamixergui specific. (strongly
>> based on the alsamixer code (verbatim) with fltk gui code added to it.).
>> 
>> - this is not a software problem, this is a hardware problem. The user
>> adjusts the mixer to cause a feedback between speaker and internal
>> microphone, and leaves this running for >30 seconds, and his hardware
>> can’t deal with it. It is probably not even operating system specific.
>> 
>> Finally, I really don’t like the tone you use, Nikita, particularly your
>> talk of “exposing the individuals guilty” and your accusations of
>> secrecy. And "expose clearly to the public that tool as a virus/malware,
>> and inform the antivirus authorities about it.”, really? Good luck with
>> that.
>> 
>> If you want to blacklist alsamixergui from your distro, please go ahead,
>> but don’t forget to blacklist alsamixer and amixer too, as well as any
>> other alsa mixer front ends.
>> 
>> Maarten
>> 
>> 
>> On 31 Mar 2015, at 11:14, Ricard Wanderlof <ricard.wanderlof@axis.com>
>> wrote:
>> 
>>> 
>>> On Tue, 31 Mar 2015, Nikita N. wrote:
>>> 
>>>>> alsamixergui is not created by the ALSA 
>>>>> project, so this mailing list is the wrong place to look if none other 
>>>>> than for that particular reason.
>>>> Sure, we would be very grateful if you could point that out, so we can
>>>> contact the individual who programmed this tool
>>>> Unless it's not a secret or there is smtng to hide.
>>> 
>>> I have no idea who wrote it, Clemens posted a link but at to me it seems 
>>> dead, there should be something in the source code (perhaps that's where 
>>> he got it frome?). Could very well be that it was written by someone who 
>>> has since moved on to other things so that any links or email adresses are 
>>> outdated. It's not necessarily a secret, it could just be unknown at this 
>>> point, and if the person who wrote it is not actively maintaining it any 
>>> more there's probably little to be gained from contacting him.
>>> 
>>> /Ricard
>>> -- 
>>> Ricard Wolf Wanderlöf                           ricardw(at)axis.com
>>> Axis Communications AB, Lund, Sweden            www.axis.com
>>> Phone +46 46 272 2016                           Fax +46 46 13 61 30
>>> _______________________________________________
>>> Alsa-devel mailing list
>>> Alsa-devel@alsa-project.org
>>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>> 
> 
> -- 
> http://www.fastmail.com - Access all of your messages and folders
>                          wherever you are
> 

Re: Speaker burnout

[Nikolay Dimitrov]

Hi David,

On 03/31/2015 01:43 PM, David Henningsson wrote:
>
>
> On 2015-03-31 12:06, Nikita N. wrote:
>>> If you have any concrete examples (alsa-info please!) of speakers
>>> that can be burned out, and you know a maximum speaker volume
>>> where this
>> As we said, that is not our bug, we are not audio experts, nor any
>> of us is interested in audio matters.
>
> Here's my suggestion how to move forward on this:
>
> 1) Gather consensus that limit the maximum volume on internal
> speakers is the right way forward. Takashi, Clemens, anyone against
> that strategy?
>
> 2) From the person with the hardware, we will need alsa-info (
> https://wiki.ubuntu.com/Audio/AlsaInfo ), and also the max volume
> where this does not happen. Is -6 dB good enough? -12 dB? I don't
> know - this is something someone with the hardware must tell us, it
> cannot simply be guessed.
>
> 3) I or someone else can write a kernel patch that limits the maximum
>  volume of the speakers to the amount deducted from point 2).
> Considering that we're actually dealing with hardware breakage, this
> should be sent to stable as well. Then no userspace application can
> set the volume higher than our limit.

Probably a kernel patch is not necessary. asound.conf ans asound.state
can do similar job. If the master volume is fixed to a safe value, the
audio can be routed through softvol plugin, which can be used as a
replacement for the master volume control (the exact levels need to be
confirmed with someone who has access to the problematic hardware).

state.Intel {
	control.1 {
		comment.access 'read'  // read-only
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 64'
		comment.dbmin -6400
		comment.dbmax 0
		iface MIXER
		name 'Speaker Playback Volume'
		value.0 42  // safe volume levels
		value.1 42  //
	}
}

Could be even better if the HW master volume control is hidden (I don't
know how to do this), and the softvol control is exposes as master volume:

pcm.!default {
     type            softvol
     slave.pcm       "default"
     control.name    "Master Volume"
     control.card    0
}

...something like this.

Kind regards,
Nikolay

Re: Speaker burnout

[Ricard Wanderlof]

On Tue, 31 Mar 2015, David Henningsson wrote:

> On 2015-03-31 12:06, Nikita N. wrote:
> >> If you have any concrete examples (alsa-info please!) of speakers that
> >> can be burned out, and you know a maximum speaker volume where this
> > As we said, that is not our bug, we are not audio experts, nor any of us
> > is interested in audio matters.
> 
> Here's my suggestion how to move forward on this:
> 
>   1) Gather consensus that limit the maximum volume on internal speakers 
> is the right way forward. Takashi, Clemens, anyone against that strategy?
> 
>   2) From the person with the hardware, we will need alsa-info ( 
> https://wiki.ubuntu.com/Audio/AlsaInfo ), and also the max volume where 
> this does not happen. Is -6 dB good enough? -12 dB? I don't know - this 
> is something someone with the hardware must tell us, it cannot simply be 
> guessed.
> 
>   3) I or someone else can write a kernel patch that limits the maximum 
> volume of the speakers to the amount deducted from point 2). Considering 
> that we're actually dealing with hardware breakage, this should be sent 
> to stable as well. Then no userspace application can set the volume 
> higher than our limit.

While we could technically limit the output level in a driver, the output 
level at which the speakers get damaged must surely depend not only on the 
codec but also on the particular analog output stage driving the speakers 
(assuming it's not built into the codec), the speakers themselves, as well 
as any other hardware on the board, for instance coupling capacitors, or 
potential overload protection circuitry, most of which are components 
which we cannot identify in the driver.

My point is that unless this is a problem with a very specific hardware, 
there's no way the software can actually know what a "dangerous" level 
would be, and hence we cannot limit it in software. What is a "dangerous" 
level in one setup could be an unusably low level in another setup, where 
both setups look identical from a driver point of view.

I'm thinking that any limits must be dependent on a particular hardware 
setup, which means in order to be successful, we would have to extract 
some sort of model name of the system we're actually running on, to be 
compared against some sort of graylist. With the proliferation of model 
names of PC:s, such a list would be sketchy at best.

/Ricard
-- 
Ricard Wolf Wanderlöf                           ricardw(at)axis.com
Axis Communications AB, Lund, Sweden            www.axis.com
Phone +46 46 272 2016                           Fax +46 46 13 61 30

Re: bug

[Ricard Wanderlof]

Sorry, I just can't keep silent on this... though I fear this will go 
nowhere ... :-(

On Tue, 31 Mar 2015, Nikita N. wrote:

> [ ... ] software is verified can damage the speakers, if not used 
> somehow correctly.
> ...
> We were hoping in some form of amend from yourself, about the dangerous
> software you produced and distributed to public.
> ...
> We were hoping at least in a simple warning popping up from your tool,
> when user sets any "hazardous" levels.

There is nothing wrong with the software. As MAarten points out, it does 
the same as any other mixer software. There is a problem with the 
hardware. It is akin to turning up the volume control on your stereo 
system and burning out the speakers in your room. If that happens, you 
have a hardware combination that is incorrectly a designed (i.e. your 
amplifier is too powerful for your speakers), it's not your hand with 
which you turned up the volume that is is 'dangerous'.

I appreciate that users might be upset when that happens, and rightly so, 
however, they should be upset with the hardware design, i.e. in this case 
the PC manufacturer.

In essence, a PC that behaves this way is broken, and if it starts 
emitting smoke when this happens it might even be dangerous and should be 
returned to the manufacturer for replacement. Period.

The same thing would apply if the power supply catches fire while playing 
a CPU- and graphic intensive game, because the large amount of power 
needed. Faulty hardware. Replace it, or buy a reputable brand next time.

That said, with some proper input we might be able to minimize the problem 
in software, given the proper help about which levels are considered 
"dangerous". That is something that must be determined for each specific 
hardware, there is no "dangerous" level from a software point of view.

> We were hoping at least-least in a warning popping up from your tool at
> runtime, something like "Warning: improper settings for this level, this
> level and this might result in damages to your audio devices".

There is no such level that the software can know about. Setting the 
output levels to maximum is not necessarily bad, wrong or dangerous. It 
depends on the hardware, and very likely hardware which the software can 
not know about (such as the exact type of speakers).

/Ricard
-- 
Ricard Wolf Wanderlöf                           ricardw(at)axis.com
Axis Communications AB, Lund, Sweden            www.axis.com
Phone +46 46 272 2016                           Fax +46 46 13 61 30
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Re: Speaker burnout

[David Henningsson]

On 2015-03-31 13:31, Ricard Wanderlof wrote:
>
> On Tue, 31 Mar 2015, David Henningsson wrote:
>
>> On 2015-03-31 12:06, Nikita N. wrote:
>>>> If you have any concrete examples (alsa-info please!) of speakers that
>>>> can be burned out, and you know a maximum speaker volume where this
>>> As we said, that is not our bug, we are not audio experts, nor any of us
>>> is interested in audio matters.
>>
>> Here's my suggestion how to move forward on this:
>>
>>    1) Gather consensus that limit the maximum volume on internal speakers
>> is the right way forward. Takashi, Clemens, anyone against that strategy?
>>
>>    2) From the person with the hardware, we will need alsa-info (
>> https://wiki.ubuntu.com/Audio/AlsaInfo ), and also the max volume where
>> this does not happen. Is -6 dB good enough? -12 dB? I don't know - this
>> is something someone with the hardware must tell us, it cannot simply be
>> guessed.
>>
>>    3) I or someone else can write a kernel patch that limits the maximum
>> volume of the speakers to the amount deducted from point 2). Considering
>> that we're actually dealing with hardware breakage, this should be sent
>> to stable as well. Then no userspace application can set the volume
>> higher than our limit.
>
> While we could technically limit the output level in a driver, the output
> level at which the speakers get damaged must surely depend not only on the
> codec but also on the particular analog output stage driving the speakers
> (assuming it's not built into the codec), the speakers themselves, as well
> as any other hardware on the board, for instance coupling capacitors, or
> potential overload protection circuitry, most of which are components
> which we cannot identify in the driver.
>
> My point is that unless this is a problem with a very specific hardware,
> there's no way the software can actually know what a "dangerous" level
> would be, and hence we cannot limit it in software. What is a "dangerous"
> level in one setup could be an unusably low level in another setup, where
> both setups look identical from a driver point of view.
>
> I'm thinking that any limits must be dependent on a particular hardware
> setup, which means in order to be successful, we would have to extract
> some sort of model name of the system we're actually running on, to be
> compared against some sort of graylist. With the proliferation of model
> names of PC:s, such a list would be sketchy at best.

Yes, this is a problem with very specific hardware, and that's why I 
asked for alsa-info - part of what we get from that is somewhat of a 
unique model-ID (in the form of a PCI SSID).


-- 
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic

Re: bug

[Clemens Ladisch]

Nikita N. wrote:
>> http://www.iua.upf.es/~mdeboer/projects/alsamixergui/
>
> this link is broken, please provide a correct one

This is the last known link.

>> Please note that _every_ mixer application on _every_ OS might be able
>> to set the controls to those dangerous values.
>
> is it "might" or it is?

I was not able to test all of them.  But I would be surprised if there
is any mixer that knows about this broken hardware and somehow restricts
the mixer ranges.

> Is also your alsamixer textual version tool, capable of speakers
> burnout?

As I already wrote above, on that hardware, I estimate that _every_
mixer tool is capable of that.


Regards,
Clemens

Re: Speaker burnout

[Torsten Schenk]

Hi everyone,

I also followed the discussion.
First of all I have to agree to Maarten that I dont' like your,
Nikita's, tone here on the list. First of all, why are you complaining?
As you can see, many people now are trying to figure out what to do to
fix this. But instead you keep blaming, accusing and offending
Maarten. He is right that a mixer application just allows controlling
those parameters the hardware tells to be manipulatable. So the tool
CANNOT be held responsible. Popping up warnings will be annoying for all
the users that NEED to set the volume to a high level and would be
overkill if just very few devices are to be addressed.

Regarding the technical side of this: Since it interested me if this
happened to other people, I found this post:

http://marcin.juszkiewicz.com.pl/2012/12/10/how-to-fry-speakers-in-your-chromebook/

and the previous post on this site.
So it seems that on a Samsung Chromebook you can definitively burn your
speakers. One comment inside these post I found noticeable:

> I’m guessing that a path was set up from MIC1 (wired to DMIC in) to
> the left speaker output. Playing the digital mic input as analog at
> full volume seems like something that might cause speaker failure, and
> wouldn’t necessarily be audible while it is happening.

So this would indicate that not the volume level causes the damage but
a bad audio routing.

Regards,
Torsten

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Re: Speaker burnout

[Nikita N.]

Dear Torsten,

> Nikita's, tone here on the list. First of all, why are you complaining?

as matter of fact, and as already said, we are not blaming anyone.
Also, our complains are now definitely over.
"The Ubuntu community is built on the ideas enshrined in the Ubuntu
Manifesto: that software should be available free of charge, that
software tools should be usable by people in their local language and
despite any disabilities, and that people should have the freedom to
customize and alter their software in whatever way they see fit."
If Mr. Maarten see fit this software as he really wishes, nobody can
complain, as long as the identity of the owner of the software is well
clear and known.
If further issues will rise, the Linux community will know the owner
identity, and contact him directly in the most appropriate way.

> As you can see, many people now are trying to figure out what to do to fix this.
We are very happy about that, and again we apologize if our tones has
been matter of misunderstanding.
We are now sure a proper solution will be found.
By now, waiting for a more stable solutions, we would like to suggest,
if possible, please add a very simple popup, only a single one when
alsamixer-text and/or alsamixergui are run, with such similar message:
"Caution: incorrect settings might cause damage to your audio devices".
That would save us from doing it ourselves, at import time.
Thank you for your attention, and please keep up with your outstanding
achievements.

-- 
  Nikita N.
  nikitan@operamail.com


On Tue, Mar 31, 2015, at 06:47 AM, Torsten Schenk wrote:
> Hi everyone,
> 
> I also followed the discussion.
> First of all I have to agree to Maarten that I dont' like your,
> Nikita's, tone here on the list. First of all, why are you complaining?
> As you can see, many people now are trying to figure out what to do to
> fix this. But instead you keep blaming, accusing and offending
> Maarten. He is right that a mixer application just allows controlling
> those parameters the hardware tells to be manipulatable. So the tool
> CANNOT be held responsible. Popping up warnings will be annoying for all
> the users that NEED to set the volume to a high level and would be
> overkill if just very few devices are to be addressed.
> 
> Regarding the technical side of this: Since it interested me if this
> happened to other people, I found this post:
> 
> http://marcin.juszkiewicz.com.pl/2012/12/10/how-to-fry-speakers-in-your-chromebook/
> 
> and the previous post on this site.
> So it seems that on a Samsung Chromebook you can definitively burn your
> speakers. One comment inside these post I found noticeable:
> 
> > I’m guessing that a path was set up from MIC1 (wired to DMIC in) to
> > the left speaker output. Playing the digital mic input as analog at
> > full volume seems like something that might cause speaker failure, and
> > wouldn’t necessarily be audible while it is happening.
> 
> So this would indicate that not the volume level causes the damage but
> a bad audio routing.
> 
> Regards,
> Torsten
> 

-- 
http://www.fastmail.com - Access all of your messages and folders
                          wherever you are

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Re: Speaker burnout

[Takashi Iwai]

At Tue, 31 Mar 2015 12:43:25 +0200,
David Henningsson wrote:
> 
> 
> 
> On 2015-03-31 12:06, Nikita N. wrote:
> >> If you have any concrete examples (alsa-info please!) of speakers that
> >> can be burned out, and you know a maximum speaker volume where this
> > As we said, that is not our bug, we are not audio experts, nor any of us
> > is interested in audio matters.
> 
> Here's my suggestion how to move forward on this:
> 
>   1) Gather consensus that limit the maximum volume on internal speakers 
> is the right way forward. Takashi, Clemens, anyone against that strategy?

It's the safest (and likely easiest) band aid, yes.


Takashi

Re: Speaker burnout

[Takashi Iwai]

At Tue, 31 Mar 2015 12:14:20 -0700,
Nikita N. wrote:
> 
> Dear Torsten,
> 
> > Nikita's, tone here on the list. First of all, why are you complaining?
> 
> as matter of fact, and as already said, we are not blaming anyone.
> Also, our complains are now definitely over.
> "The Ubuntu community is built on the ideas enshrined in the Ubuntu
> Manifesto: that software should be available free of charge, that
> software tools should be usable by people in their local language and
> despite any disabilities, and that people should have the freedom to
> customize and alter their software in whatever way they see fit."
> If Mr. Maarten see fit this software as he really wishes, nobody can
> complain, as long as the identity of the owner of the software is well
> clear and known.
> If further issues will rise, the Linux community will know the owner
> identity, and contact him directly in the most appropriate way.
> 
> > As you can see, many people now are trying to figure out what to do to fix this.
> We are very happy about that, and again we apologize if our tones has
> been matter of misunderstanding.
> We are now sure a proper solution will be found.
> By now, waiting for a more stable solutions, we would like to suggest,
> if possible, please add a very simple popup, only a single one when
> alsamixer-text and/or alsamixergui are run, with such similar message:
> "Caution: incorrect settings might cause damage to your audio devices".
> That would save us from doing it ourselves, at import time.
> Thank you for your attention, and please keep up with your outstanding
> achievements.

Well, if we were selling a microwave oven and dealing with a customer
who places a poor cat into our product, then we might need to put such
a sticker on it.

However, alsamixer is just a basic tool like a screw driver.  A screw
driver (as far as I know) has no warning sticker showing "this tool
might cause damage to your precious machine."

BTW, Chromebook is essentially a "big" embedded device.  And, the
audio driver for embedded devices usually provides the all possible
buttons and knobs for manual adjustment.  Some of them are known to be
dangerous to play with, and they are usually hidden under some layers
in Android or Chrome OS, only the safe setup are provided via UCM
profile or such.  But once when you play directly with the hardware,
you need to know what you're tweaking.  Something serious like this
can happen.  It's why everywhere a text "at your own risk" is seen.

This is the way we went through over 20 years ago for PC components.
Now it's back as a different form.  Interesting...


Takashi

> 
> -- 
>   Nikita N.
>   nikitan@operamail.com
> 
> 
> On Tue, Mar 31, 2015, at 06:47 AM, Torsten Schenk wrote:
> > Hi everyone,
> > 
> > I also followed the discussion.
> > First of all I have to agree to Maarten that I dont' like your,
> > Nikita's, tone here on the list. First of all, why are you complaining?
> > As you can see, many people now are trying to figure out what to do to
> > fix this. But instead you keep blaming, accusing and offending
> > Maarten. He is right that a mixer application just allows controlling
> > those parameters the hardware tells to be manipulatable. So the tool
> > CANNOT be held responsible. Popping up warnings will be annoying for all
> > the users that NEED to set the volume to a high level and would be
> > overkill if just very few devices are to be addressed.
> > 
> > Regarding the technical side of this: Since it interested me if this
> > happened to other people, I found this post:
> > 
> > http://marcin.juszkiewicz.com.pl/2012/12/10/how-to-fry-speakers-in-your-chromebook/
> > 
> > and the previous post on this site.
> > So it seems that on a Samsung Chromebook you can definitively burn your
> > speakers. One comment inside these post I found noticeable:
> > 
> > > I’m guessing that a path was set up from MIC1 (wired to DMIC in) to
> > > the left speaker output. Playing the digital mic input as analog at
> > > full volume seems like something that might cause speaker failure, and
> > > wouldn’t necessarily be audible while it is happening.
> > 
> > So this would indicate that not the volume level causes the damage but
> > a bad audio routing.
> > 
> > Regards,
> > Torsten
> > 
> 
> -- 
> http://www.fastmail.com - Access all of your messages and folders
>                           wherever you are
> 
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Re: Speaker burnout

[Eliot Blennerhassett]

On 31/03/15 23:43, David Henningsson wrote:
> 
> 
> On 2015-03-31 12:06, Nikita N. wrote:
>>> If you have any concrete examples (alsa-info please!) of speakers that
>>> can be burned out, and you know a maximum speaker volume where this
>> As we said, that is not our bug, we are not audio experts, nor any of us
>> is interested in audio matters.
> 
> Here's my suggestion how to move forward on this:
> 
>  1) Gather consensus that limit the maximum volume on internal speakers
> is the right way forward. Takashi, Clemens, anyone against that strategy?

I'm not sure about this (though in the end it doesn't affect me).  Just
running some experiments on my laptop. (HDA intel PCH sound)

Playing some ordinary music, the level from the internal speakers is
comfortable when master and PCM gains are set to maximum.

At this setting, enabling the internal mic feedthrough with mic boost
set to maximum,  feedback happens when mic playback gain is at -6dB
(max=+12dB).
The signal when recorded is 1325Hz rail to rail square wave.

My point is that in this case for normal usage the maximum output is
fine, I'd even say it is required.  So limiting output would not be a
good idea.
Also when using the mic for speech capture (with headphones for output),
a gain greater than the 'feedback inducing' one is likely to be useful.

So it is (only?) the pathological case of feeding mic direct to speakers
that is problematic.

Given that we can't fix the hardware or wacky user behaviour,
My suggestion would be to either limit, or hide completely the various
"Mic Playback" controls that enable direct feed from input to output.
What is the use case for this anyway? - karaoke?

Given that this goes against the "expose everything in the hardware",
maybe have a module option that can unhide these controls if anybody
actually wants to use them.
--
Eliot

Re: Speaker burnout

[David Henningsson]

On 2015-04-07 07:30, Eliot Blennerhassett wrote:
> On 31/03/15 23:43, David Henningsson wrote:
>>
>>
>> On 2015-03-31 12:06, Nikita N. wrote:
>>>> If you have any concrete examples (alsa-info please!) of speakers that
>>>> can be burned out, and you know a maximum speaker volume where this
>>> As we said, that is not our bug, we are not audio experts, nor any of us
>>> is interested in audio matters.
>>
>> Here's my suggestion how to move forward on this:
>>
>>   1) Gather consensus that limit the maximum volume on internal speakers
>> is the right way forward. Takashi, Clemens, anyone against that strategy?
>
> I'm not sure about this (though in the end it doesn't affect me).  Just
> running some experiments on my laptop. (HDA intel PCH sound)
>
> Playing some ordinary music, the level from the internal speakers is
> comfortable when master and PCM gains are set to maximum.
>
> At this setting, enabling the internal mic feedthrough with mic boost
> set to maximum,  feedback happens when mic playback gain is at -6dB
> (max=+12dB).
> The signal when recorded is 1325Hz rail to rail square wave.
>
> My point is that in this case for normal usage the maximum output is
> fine, I'd even say it is required.  So limiting output would not be a
> good idea.
> Also when using the mic for speech capture (with headphones for output),
> a gain greater than the 'feedback inducing' one is likely to be useful.
>
> So it is (only?) the pathological case of feeding mic direct to speakers
> that is problematic.
>
> Given that we can't fix the hardware or wacky user behaviour,
> My suggestion would be to either limit, or hide completely the various
> "Mic Playback" controls that enable direct feed from input to output.
> What is the use case for this anyway? - karaoke?
>
> Given that this goes against the "expose everything in the hardware",
> maybe have a module option that can unhide these controls if anybody
> actually wants to use them.

On one hand I find your arguments convincing, because limiting internal 
mic playback volume is far less of a limitation (almost no people use 
it), compared to limiting the internal speaker volume.

What bothers me is the following reasoning: If it is possible to burn 
your speakers out by having the speakers outputting some tone caused by 
feedback, would it not be possible to also burn your speakers out by 
simply having a wave file with the same tone and playing it back?

E g, imagine a malicious web page that starts playing this tone back as 
soon as you visit it. Would it be able to cause hardware damage to your 
speakers, if you happened to have the speaker volume at maximum when you 
visited that web page?
Or is there something that causes the feedback tone to be of a larger 
amplitude than could ever be produced by the wave file?

-- 
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic

Re: Speaker burnout

[Clemens Ladisch]

David Henningsson wrote:
> On 2015-04-07 07:30, Eliot Blennerhassett wrote:
>> The signal when recorded is 1325Hz rail to rail square wave.
>> [...]
>
> If it is possible to burn your speakers out by having the speakers
> outputting some tone caused by feedback, would it not be possible to
> also burn your speakers out by simply having a wave file with the same
> tone and playing it back?

Of course.  The problem is the speakers, not the feedback itself.

When connecting some random speaker to some random amp, it is quite
possible to burn it out:
<https://www.google.com/search?q=tweeter+burn-out>
However, this should not happen inside a closed system where amp and
speakers were designed for each other.

> Or is there something that causes the feedback tone to be of a larger
> amplitude than could ever be produced by the wave file?

In theory, it would be possible to do the mixing in the analog domain.
But there is no way to find out what the HDA codec actually does except
trying it out.


Regards,
Clemens

Re: Speaker burnout

[Eliot Blennerhassett]

On 07/04/15 19:26, Clemens Ladisch wrote:

> In theory, it would be possible to do the mixing in the analog domain.
> But there is no way to find out what the HDA codec actually does except
> trying it out.


Dear testers, please perform the following steps:

1. Place laptop on heat-resistant surface in a well-ventilated space.
Have a fire extinguisher handy.  Put on your earmuffs.
2. Start stopwatch
3. Set all alsa volumes to maximum
3.1 If screaming noise not already evident, play this full-scale square wave
4.1 If smoke or flames appear from your laptop, stop stopwatch.
Extinguish any flames.
4.2 If 30 seconds elapsed without smoke, terminate the test.
5. Report back to us the results, if necessary borrow a friend's
computer to do so.

Hmmm, why isn't anyone volunteering to do this testing?

Seriously, How is the safe limit going to be determined?

Re: Speaker burnout

[David Henningsson]

On 2015-04-07 09:49, Eliot Blennerhassett wrote:
> On 07/04/15 19:26, Clemens Ladisch wrote:
>
>> In theory, it would be possible to do the mixing in the analog domain.
>> But there is no way to find out what the HDA codec actually does except
>> trying it out.
>
>
> Dear testers, please perform the following steps:
>
> 1. Place laptop on heat-resistant surface in a well-ventilated space.
> Have a fire extinguisher handy.  Put on your earmuffs.
> 2. Start stopwatch
> 3. Set all alsa volumes to maximum
> 3.1 If screaming noise not already evident, play this full-scale square wave
> 4.1 If smoke or flames appear from your laptop, stop stopwatch.
> Extinguish any flames.
> 4.2 If 30 seconds elapsed without smoke, terminate the test.
> 5. Report back to us the results, if necessary borrow a friend's
> computer to do so.
>
> Hmmm, why isn't anyone volunteering to do this testing?
>
> Seriously, How is the safe limit going to be determined?

I think Alexander had a good idea:

http://mailman.alsa-project.org/pipermail/alsa-devel/2015-March/089815.html

...now if this is chromebook, and I'm not sure whether that's the case 
or not, maybe "Windows" should be replaced with "Chrome OS", but anyhow 
- check what the supported OS is doing, and I believe Alexander 
suggested a safe way to do so.

Nikita - here's your chance to show that you're actually interested in 
getting the bug fixed, and not only to discuss whether alsamixer is a 
screwdriver or a microwave. On the physical hardware that has this 
problem, please perform the tests as Alexander suggested. And also run 
the alsa-info script on that hardware, and submit the result here.

-- 
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic

Re: Speaker burnout

[Ricard Wanderlof]

On Tue, 7 Apr 2015, Eliot Blennerhassett wrote:

> At this setting, enabling the internal mic feedthrough with mic boost
> set to maximum,  feedback happens when mic playback gain is at -6dB
> (max=+12dB).
> The signal when recorded is 1325Hz rail to rail square wave.
> 
> My point is that in this case for normal usage the maximum output is
> fine, I'd even say it is required.  So limiting output would not be a
> good idea.
> Also when using the mic for speech capture (with headphones for output),
> a gain greater than the 'feedback inducing' one is likely to be useful.
> 
> So it is (only?) the pathological case of feeding mic direct to speakers
> that is problematic.
> 
> Given that we can't fix the hardware or wacky user behaviour,
> My suggestion would be to either limit, or hide completely the various
> "Mic Playback" controls that enable direct feed from input to output.
> What is the use case for this anyway? - karaoke?

Can it be used to provide a side tone (telephone system terminology for 
feeding back a portion of the microphone signal to the ear piece in a 
telephone; psychologically it helps avoid the impression that the 
telephone is not connected, so all telephone type equipment have it since 
the birth of telephone technology) in telephone applications?

> Given that this goes against the "expose everything in the hardware",
> maybe have a module option that can unhide these controls if anybody
> actually wants to use them.

This sounds like a useful suggestion to me. Many applications have an 
'advanced' option or button which enables things you normally don't need. 
If the 'mic to playback' function isn't really used normally it would seem 
a reasonable option but I suppose that needs to be researched first 
whether it really is of little use.

/Ricard
-- 
Ricard Wolf Wanderlöf                           ricardw(at)axis.com
Axis Communications AB, Lund, Sweden            www.axis.com
Phone +46 46 272 2016                           Fax +46 46 13 61 30

RE: BUG

[Randall S. Becker]

On November 4, 2020 12:03 PM, I wrote:
> To: 'Alex Marginean' <alexmarginean16@gmail.com>; 'git@vger.kernel.org'
> <git@vger.kernel.org>
> Subject: RE: BUG
> 
> On November 4, 2020 11:10 AM, Alex Marginean wrote:
> > Github has changed the way they name branches, so now instead of the
> > `master` branch there is the `main` branch however, I'm having some
> > trouble with the naming
> >
> > **Steps to replicate my problem**
> >
> > 1. Create a new Github repository and make sure the default branch is
> > `main` 2. Add something to the repo, a `README.md` file should be enough
> 3.
> > Instead of cloning the repo make a new directory with your repo's name
> > `mkdir <repo_name>` and change the directory to it `cd <repo_name>` 4.
> > `git init` 5. Add the remote repo with `git remote add origin
> > <repo_link>` 6. Pull the `main` branch from the remote repo with `git pull
> origin main`.
> 
> Use git init --initial-branch=main

You could also use git branch -m master main after the git init if your version of git is too old.

> 
> This assumes a recent version of git.
> 
> >
> > After the step number 6. instead of my branch changing to `main` my
> > current branch is changed to `master` which has every file and change
> > of the branch `main`. This is a real problem because if I try to push
> > changes to `main` although my current branch shows up as `master` it
> > creates another branch called `master` on Github and the `main`
> > remains unchanged. Yeah sure I can `git checkout main` after that and
> > make my changes there but I'm not sure why it defaults to `master` and
> > copies `main` from Github into local branch `master`.
> >
> > P.S. If you were to use `git fetch origin` instead of `git pull origin
> > <branch_name> and then manually change branch to `main` with `git
> > checkout main` it would work. Also, if you were to clone the Github
> > repo using `git clone <link>` you will get the correct current branch that is
> `main`.
> 
> Regards,
> Randall
> -- Brief whoami:
>  NonStop developer since approximately 211288444200000000  UNIX
> developer since approximately 421664400
> -- In my real life, I talk too much.

RE: BUG

[Randall S. Becker]

On November 4, 2020 11:10 AM, Alex Marginean wrote:
> Github has changed the way they name branches, so now instead of the
> `master` branch there is the `main` branch however, I'm having some trouble
> with the naming
> 
> **Steps to replicate my problem**
> 
> 1. Create a new Github repository and make sure the default branch is `main`
> 2. Add something to the repo, a `README.md` file should be enough 3.
> Instead of cloning the repo make a new directory with your repo's name
> `mkdir <repo_name>` and change the directory to it `cd <repo_name>` 4. `git
> init` 5. Add the remote repo with `git remote add origin <repo_link>` 6. Pull
> the `main` branch from the remote repo with `git pull origin main`.

Use git init --initial-branch=main

This assumes a recent version of git.

> 
> After the step number 6. instead of my branch changing to `main` my current
> branch is changed to `master` which has every file and change of the branch
> `main`. This is a real problem because if I try to push changes to `main`
> although my current branch shows up as `master` it creates another branch
> called `master` on Github and the `main` remains unchanged. Yeah sure I can
> `git checkout main` after that and make my changes there but I'm not sure
> why it defaults to `master` and copies `main` from Github into local branch
> `master`.
> 
> P.S. If you were to use `git fetch origin` instead of `git pull origin
> <branch_name> and then manually change branch to `main` with `git
> checkout main` it would work. Also, if you were to clone the Github repo
> using `git clone <link>` you will get the correct current branch that is `main`.

Regards,
Randall
-- Brief whoami:
 NonStop developer since approximately 211288444200000000
 UNIX developer since approximately 421664400
-- In my real life, I talk too much.

BUG

[Alex Marginean]

[-- Attachment #1: Type: text/plain, Size: 1488 bytes --]

Hey,

Github has changed the way they name branches, so now instead of the
`master` branch there is the `main` branch however, I'm having some
trouble with the naming

**Steps to replicate my problem**

1. Create a new Github repository and make sure the default branch is `main`
2. Add something to the repo, a `README.md` file should be enough
3. Instead of cloning the repo make a new directory with your repo's
name `mkdir <repo_name>` and change the directory to it `cd
<repo_name>`
4. `git init`
5. Add the remote repo with `git remote add origin <repo_link>`
6. Pull the `main` branch from the remote repo with `git pull origin main`.

After the step number 6. instead of my branch changing to `main` my
current branch is changed to `master` which has every file and change
of the branch `main`. This is a real problem because if I try to push
changes to `main` although my current branch shows up as `master` it
creates another branch called `master` on Github and the `main`
remains unchanged. Yeah sure I can `git checkout main` after that and
make my changes there but I'm not sure why it defaults to `master` and
copies `main` from Github into local branch `master`.

P.S. If you were to use `git fetch origin` instead of `git pull origin
<branch_name> and then manually change branch to `main` with `git
checkout main` it would work. Also, if you were to clone the Github
repo using `git clone <link>` you will get the correct current branch
that is `main`.

Sincerely,
Alex

[-- Attachment #2: git-bugreport-2020-11-04-1731.txt --]
[-- Type: text/plain, Size: 2639 bytes --]

Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.

What did you do before the bug happened? (Steps to reproduce your issue)

Github has changed the way they name branches, so now instead of the `master` branch there is the `main` branch however, I'm having some trouble with the naming

1. Create a new Github repository and make sure the default branch is `main`
2. Add something to the repo, a `README.md` file should be enough
3. Instead of cloning the repo make a new directory with your repo's name `mkdir <repo_name>` and change the directory to it `cd <repo_name>`
4. `git init`
5. Add the remote repo with `git remote add origin <repo_link>`
6. Pull the `main` branch from the remote repo with `git pull origin main`.

What did you expect to happen? (Expected behavior)

After step 6. I expected to be switched to a branch called `main` that would include every file and change from the `main` branch on the origin. 

What happened instead? (Actual behavior)

After the step number 6. instead of my branch changing to `main` my current branch is changed to `master` which has every file and change of the branch `main`. This is a real problem because if I try to push changes to `main` although my current branch shows up as `master` it creates another branch called `master` on Github and the `main` remains unchanged. Yeah sure I can `git checkout main` after that and make my changes there but I'm not sure why it defaults to `master` and copies `main` from Github into local branch `master`.

What's different between what you expected and what actually happened?

The name of the branch and the duplication of the `main` branch to a branch called `master`.

Anything else you want to add:

P.S. If you were to use `git fetch origin` instead of `git pull origin <branch_name> and then manually change branch to `main` with `git checkout main` it would work. Also, if you were to clone the Github repo using `git clone <link>` you will get the correct current branch that is `main`.

Please review the rest of the bug report below.
You can delete any lines you don't wish to share.


[System Info]
git version:
git version 2.29.2
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Darwin 19.6.0 Darwin Kernel Version 19.6.0: Mon Aug 31 22:12:52 PDT 2020; root:xnu-6153.141.2~1/RELEASE_X86_64 x86_64
compiler info: clang: 12.0.0 (clang-1200.0.32.21)
libc info: no libc information available
$SHELL (typically, interactive shell): /bin/zsh


[Enabled Hooks]
not run from a git repository - no hooks to show

bug

[Luke Knoble]

Howdy,

I've found an issue in which I'm using this command:

git clone --recurse-submodules ssh://git@someurl:9999/someproject/repoX.git

git clones the repo successfully if I dont pass “git clone” any flags,
but gives me this error when I use “--recurse-submodules” and git
attempts to clone a single submodule:

git@someurl: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
fatal: clone of
'ssh://git@someurl:9999/someproject/submodule_repo.git' into submodule
path 'C:/someproject/submodule_repo' failed

The obvious answer is that my permissions are bad, but I can clone the
submodule repo directly without issue.. This command succeeds:

git clone --recurse-submodules
ssh://git@someurl:9999/someproject/submodule_repo.git

what gives git?

bug

[liebrecht]

Clearly a problem with Alsa.
Alsa reports  "Most likely this is a bug in the ALSA driver 
'snd_usb_audio'."

Alsa used to work great.
howevere recently it takes 1/2-1hour for pulseaudio to convince alsa to 
make the 1818VSL available.
Jack is not involved at all.
Pulseaudio connects straight to alsa.
Pulseaudio is my saving grace roight now as it perpetually tries to 
initialize and get alsa to present the audio interface, which it 
eventually after an hour does "waking up"

Also sorts of decides to "wake up" and then suddenly the 1818vsl is 
found.

How do I "wake up" alsa so that I can use soundcards.
I cannot wait an hour after reboot or logout to get alsa to work again.


See below


What  happens after starting pulseaudio is that it cycles the 1818 for 
about 1/2 hour to get a link to the 181vsl soundcard. That is the first 
paragraph (1) below which is perpetually cycled by pulseaudio.
Eventually it succeeds which gives the BUG comment as below in paragraph 
(2)
-------------------------------------------------------
1)
E: [pulseaudio] udev-util.c: Failed to get card object.
E: [pulseaudio] module-alsa-card.c: Failed to find a working profile.
E: [pulseaudio] module.c: Failed to load module "module-alsa-card" 
(argument: "device_id="3" name="usb-PreSonus_AudioBox_1818_VSL_2209-00" 
card_name="alsa_card.usb-PreSonus_Audio.Box_1818_VSL_2209-00" 
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no 
deferred_volume=yes use_ucm=yes 
card_properties="module-udev-detect.discovered=1""): initialization 
failed.
(**Note this message is cycled for an hour**)

2)
(**Then miraculously....Alsa wakes up and pulseaudio can connect to 
1818vsl **)
E: [alsa-sink-USB Audio] alsa-sink.c: ALSA woke us up to write new data 
to the device, but there was actually nothing to write.
E: [alsa-sink-USB Audio] alsa-sink.c: Most likely this is a bug in the 
ALSA driver 'snd_usb_audio'. Please report this issue to the ALSA 
developers.
E: [alsa-sink-USB Audio] alsa-sink.c: We were woken up with POLLOUT set 
-- however a subsequent snd_pcm_avail() returned 0 or another value < 
min_avail.

------------------------------------------------------


Dont know what happened top Also to behave this way.
Maybe someone has an idea ?





upload=true&script=true&cardinfo=
!!################################
!!ALSA Information Script v 0.4.64
!!################################

!!Script ran on: Mon Sep  2 03:27:26 UTC 2019


!!Linux Distribution
!!------------------

^[[1;36mWelcome to ^[[1;33mMX Linux^[[1;36m! Powered by 
^[[1;33mDebian^[[1;36m.^[[0m PRETTY_NAME="Debian GNU/Linux 9 (stretch)" 
NAME="Debian GNU/Linux" ID=debian HOME_URL="https://www.debian.org/" 
SUPPORT_URL="https://www.debian.org/support" 
BUG_REPORT_URL="https://bugs.debian.org/" MX-18.3_x64 Continuum Dec 20, 
2018 MX-18.3_x64 Continuum Dec 20, 2018


!!DMI Information
!!---------------

Manufacturer:      Supermicro
Product Name:      H8DGU
Product Version:   1234567890
Firmware Version:  3.5c
Board Vendor:      Supermicro
Board Name:        H8DGU


!!ACPI Device Status Information
!!---------------

/sys/bus/acpi/devices/PNP0103:00/status 	 15
/sys/bus/acpi/devices/PNP0501:00/status 	 15
/sys/bus/acpi/devices/PNP0501:01/status 	 15
/sys/bus/acpi/devices/PNP0C0C:00/status 	 11
/sys/bus/acpi/devices/PNP0C0F:00/status 	 9
/sys/bus/acpi/devices/PNP0C0F:01/status 	 9
/sys/bus/acpi/devices/PNP0C0F:02/status 	 9
/sys/bus/acpi/devices/PNP0C0F:03/status 	 9
/sys/bus/acpi/devices/PNP0C0F:04/status 	 9
/sys/bus/acpi/devices/PNP0C0F:05/status 	 9
/sys/bus/acpi/devices/PNP0C0F:06/status 	 9
/sys/bus/acpi/devices/PNP0C0F:07/status 	 9
/sys/bus/acpi/devices/device:1e/status 	 15
/sys/bus/acpi/devices/device:1f/status 	 15
/sys/bus/acpi/devices/device:21/status 	 15
/sys/bus/acpi/devices/device:22/status 	 15


!!Kernel Information
!!------------------

Kernel release:    4.19.0-5-amd64
Operating System:  GNU/Linux
Architecture:      x86_64
Processor:         unknown
SMP Enabled:       Yes


!!ALSA Version
!!------------

Driver version:     k4.19.0-5-amd64
Library version:    1.1.9
Utilities version:  1.1.3


!!Loaded ALSA modules
!!-------------------

snd_hda_intel
snd_usb_audio
snd_usb_audio


!!Sound Servers on this system
!!----------------------------

Pulseaudio:
       Installed - Yes (/usr/bin/pulseaudio)
       Running - Yes

Jack:
       Installed - Yes (/usr/bin/jackd)
       Running - No


!!Soundcards recognised by ALSA
!!-----------------------------

  0 [HDMI           ]: HDA-Intel - HDA ATI HDMI
                       HDA ATI HDMI at 0xfebfc000 irq 46
  1 [Interface      ]: USB-Audio - USB Uno MIDI Interface
                       M-Audio USB Uno MIDI Interface at 
usb-0000:00:12.2-1.2.3, full speed
  2 [M1x1           ]: USB-Audio - MidiSport 1x1
                       M-Audio MidiSport 1x1 at usb-0000:00:12.2-1.2.2, 
full speed


!!PCI Soundcards installed in the system
!!--------------------------------------

03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aae0


!!Advanced information - PCI Vendor/Device/Subsystem ID's
!!-------------------------------------------------------

03:00.1 0403: 1002:aae0
	Subsystem: 1462:aae0


!!Modprobe options (Sound related)
!!--------------------------------

snd_pcsp: index=-2
snd_usb_audio: index=-2
snd_atiixp_modem: index=-2
snd_intel8x0m: index=-2
snd_via82xx_modem: index=-2


!!Loaded sound module options
!!---------------------------

!!Module: snd_hda_intel
	align_buffer_size : -1
	bdl_pos_adj : 
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
	beep_mode : 
Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y
	enable : 
Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y
	enable_msi : -1
	id : 
(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
	index : 
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
	jackpoll_ms : 
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
	model : 
(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
	patch : 
(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
	pm_blacklist : Y
	position_fix : 
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
	power_save : 0
	power_save_controller : N
	probe_mask : 
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
	probe_only : 
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
	single_cmd : -1
	snoop : -1

!!Module: snd_usb_audio
	autoclock : Y
	device_setup : 
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
	enable : 
Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y
	id : 
(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
	ignore_ctl_error : N
	index : 
-2,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
	pid : 
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
	quirk_alias : 
(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
	use_vmalloc : Y
	vid : 
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1

!!Module: snd_usb_audio
	autoclock : Y
	device_setup : 
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
	enable : 
Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y
	id : 
(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
	ignore_ctl_error : N
	index : 
-2,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
	pid : 
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
	quirk_alias : 
(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
	use_vmalloc : Y
	vid : 
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1


!!HDA-Intel Codec information
!!---------------------------
--startcollapse--

Codec: ATI R6xx HDMI
Address: 0
AFG Function Id: 0x1 (unsol 0)
Vendor Id: 0x1002aa01
Subsystem Id: 0x00aa0100
Revision Id: 0x100700
No Modem Function Group found
Default PCM:
     rates [0x70]: 32000 44100 48000
     bits [0x2]: 16
     formats [0x1]: PCM
Default Amp-In caps: N/A
Default Amp-Out caps: N/A
State of AFG node 0x01:
   Power states:  D0 D3 CLKSTOP EPSS
   Power: setting=D0, actual=D0, Clock-stop-OK
GPIO: io=0, o=0, i=0, unsolicited=0, wake=0
Node 0x02 [Audio Output] wcaps 0x221: Stereo Digital Stripe
   Converter: stream=0, channel=0
   Digital: Enabled
   Digital category: 0x0
   IEC Coding Type: 0x0
Node 0x03 [Pin Complex] wcaps 0x400381: Stereo Digital
   Control: name="IEC958 Playback Con Mask", index=0, device=0
   Control: name="IEC958 Playback Pro Mask", index=0, device=0
   Control: name="IEC958 Playback Default", index=0, device=0
   Control: name="IEC958 Playback Switch", index=0, device=0
   Pincap 0x00000094: OUT Detect HDMI
   Pin Default 0x185600f0: [Jack] Digital Out at Int HDMI
     Conn = Digital, Color = Unknown
     DefAssociation = 0xf, Sequence = 0x0
   Pin-ctls: 0x40: OUT
   Unsolicited: tag=01, enabled=1
   Connection: 1
      0x02
Node 0x04 [Audio Output] wcaps 0x221: Stereo Digital Stripe
   Converter: stream=0, channel=0
   Digital: Enabled
   Digital category: 0x0
   IEC Coding Type: 0x0
Node 0x05 [Pin Complex] wcaps 0x400381: Stereo Digital
   Control: name="IEC958 Playback Con Mask", index=1, device=0
   Control: name="IEC958 Playback Pro Mask", index=1, device=0
   Control: name="IEC958 Playback Default", index=1, device=0
   Control: name="IEC958 Playback Switch", index=1, device=0
   Pincap 0x00000094: OUT Detect HDMI
   Pin Default 0x185600f0: [Jack] Digital Out at Int HDMI
     Conn = Digital, Color = Unknown
     DefAssociation = 0xf, Sequence = 0x0
   Pin-ctls: 0x40: OUT
   Unsolicited: tag=02, enabled=1
   Connection: 1
      0x04
Node 0x06 [Audio Output] wcaps 0x221: Stereo Digital Stripe
   Converter: stream=0, channel=0
   Digital: Enabled
   Digital category: 0x0
   IEC Coding Type: 0x0
Node 0x07 [Pin Complex] wcaps 0x400381: Stereo Digital
   Control: name="IEC958 Playback Con Mask", index=2, device=0
   Control: name="IEC958 Playback Pro Mask", index=2, device=0
   Control: name="IEC958 Playback Default", index=2, device=0
   Control: name="IEC958 Playback Switch", index=2, device=0
   Pincap 0x00000094: OUT Detect HDMI
   Pin Default 0x185600f0: [Jack] Digital Out at Int HDMI
     Conn = Digital, Color = Unknown
     DefAssociation = 0xf, Sequence = 0x0
   Pin-ctls: 0x40: OUT
   Unsolicited: tag=03, enabled=1
   Connection: 1
      0x06
Node 0x08 [Audio Output] wcaps 0x221: Stereo Digital Stripe
   Converter: stream=0, channel=0
   Digital: Enabled
   Digital category: 0x0
   IEC Coding Type: 0x0
Node 0x09 [Pin Complex] wcaps 0x400381: Stereo Digital
   Control: name="IEC958 Playback Con Mask", index=3, device=0
   Control: name="IEC958 Playback Pro Mask", index=3, device=0
   Control: name="IEC958 Playback Default", index=3, device=0
   Control: name="IEC958 Playback Switch", index=3, device=0
   Pincap 0x00000094: OUT Detect HDMI
   Pin Default 0x185600f0: [Jack] Digital Out at Int HDMI
     Conn = Digital, Color = Unknown
     DefAssociation = 0xf, Sequence = 0x0
   Pin-ctls: 0x40: OUT
   Unsolicited: tag=04, enabled=1
   Connection: 1
      0x08
Node 0x0a [Audio Output] wcaps 0x221: Stereo Digital Stripe
   Converter: stream=1, channel=0
   Digital: Enabled
   Digital category: 0x0
   IEC Coding Type: 0x0
Node 0x0b [Pin Complex] wcaps 0x400381: Stereo Digital
   Control: name="IEC958 Playback Con Mask", index=4, device=0
   Control: name="IEC958 Playback Pro Mask", index=4, device=0
   Control: name="IEC958 Playback Default", index=4, device=0
   Control: name="IEC958 Playback Switch", index=4, device=0
   Pincap 0x00000094: OUT Detect HDMI
   Pin Default 0x185600f0: [Jack] Digital Out at Int HDMI
     Conn = Digital, Color = Unknown
     DefAssociation = 0xf, Sequence = 0x0
   Pin-ctls: 0x40: OUT
   Unsolicited: tag=05, enabled=1
   Connection: 1
      0x0a
Node 0x0c [Audio Output] wcaps 0x221: Stereo Digital Stripe
   Converter: stream=0, channel=0
   Digital:
   Digital category: 0x0
   IEC Coding Type: 0x0
Node 0x0d [Pin Complex] wcaps 0x400381: Stereo Digital
   Pincap 0x00000094: OUT Detect HDMI
   Pin Default 0x585600f0: [N/A] Digital Out at Int HDMI
     Conn = Digital, Color = Unknown
     DefAssociation = 0xf, Sequence = 0x0
   Pin-ctls: 0x40: OUT
   Unsolicited: tag=00, enabled=0
   Connection: 1
      0x0c
--endcollapse--


!!USB Mixer information
!!---------------------
--startcollapse--

USB Mixer: usb_id=0x07630150, ctrlif=0, ctlerr=0
Card: M-Audio USB Uno MIDI Interface at usb-0000:00:12.2-1.2.3, full 
speed
--endcollapse--


!!ALSA Device nodes
!!-----------------

crw-rw---- 1 root audio 116,  8 Sep  1 04:44 /dev/snd/controlC0
crw-rw---- 1 root audio 116, 10 Sep  1 06:36 /dev/snd/controlC1
crw-rw---- 1 root audio 116, 12 Sep  1 06:36 /dev/snd/controlC2
crw-rw---- 1 root audio 116,  7 Sep  1 04:44 /dev/snd/hwC0D0
crw-rw---- 1 root audio 116,  9 Sep  1 06:36 /dev/snd/midiC1D0
crw-rw---- 1 root audio 116, 11 Sep  1 06:36 /dev/snd/midiC2D0
crw-rw---- 1 root audio 116,  6 Sep  1 23:17 /dev/snd/pcmC0D10p
crw-rw---- 1 root audio 116,  2 Sep  1 23:17 /dev/snd/pcmC0D3p
crw-rw---- 1 root audio 116,  3 Sep  1 23:17 /dev/snd/pcmC0D7p
crw-rw---- 1 root audio 116,  4 Sep  1 23:17 /dev/snd/pcmC0D8p
crw-rw---- 1 root audio 116,  5 Sep  1 23:17 /dev/snd/pcmC0D9p
crw-rw---- 1 root audio 116,  1 Sep  1 05:13 /dev/snd/seq
crw-rw---- 1 root audio 116, 33 Sep  1 04:44 /dev/snd/timer

/dev/snd/by-id:
total 0
drwxr-xr-x 2 root root  80 Sep  1 22:40 .
drwxr-xr-x 4 root root 340 Sep  1 22:40 ..
lrwxrwxrwx 1 root root  12 Sep  1 06:36 usb-0763_1011-00 -> ../controlC2
lrwxrwxrwx 1 root root  12 Sep  1 06:36 
usb-M-Audio_USB_Uno_MIDI_Interface-00 -> ../controlC1

/dev/snd/by-path:
total 0
drwxr-xr-x 2 root root 100 Sep  1 22:40 .
drwxr-xr-x 4 root root 340 Sep  1 22:40 ..
lrwxrwxrwx 1 root root  12 Sep  1 06:36 pci-0000:00:12.2-usb-0:1.2.2:1.0 
-> ../controlC2
lrwxrwxrwx 1 root root  12 Sep  1 06:36 pci-0000:00:12.2-usb-0:1.2.3:1.0 
-> ../controlC1
lrwxrwxrwx 1 root root  12 Sep  1 04:44 pci-0000:03:00.1 -> ../controlC0


!!ALSA configuration files
!!------------------------

!!System wide config file (/etc/asound.conf)

# v4.0
# Requires alsa-utils libasound2-plugin-equal



# ***** Defaults *******************************************************

# Audio card/chip and device to use and control
# In most cases these settings should remain commented (#)
# When commented, card and device 0 are usually automatically selected
# When uncommented, the item corresponding to the number is selected
#defaults.pcm.card 0
#defaults.pcm.device 0
#defaults.ctl.card 0



# ***** Reset **********************************************************

# override the existing definition of the default device
pcm.!default
{
    type plug

    # point output to the equalizer device
    slave.pcm plugequal
}



# ***** Equalizer ******************************************************

# set up the control interface of the equalizer device
ctl.equalizer
{
    type equal
}


# set up the equalizer device
pcm.plugequal
{
    type equal

    # point output to device named preamp
    slave.pcm  "plug:preamp"
}



# ***** Pre-Amp ********************************************************

# set up the preamp device
pcm.preamp
{
    type softvol

    # name of slider control to display in alsamixer interface
    control.name Pre-Amp

    # minimum dB when slider is at 0%
    min_dB -5.0

    # maximum dB when slider is at 100%
    max_dB 40.0

    # point output to device named duplex
    slave.pcm "duplex"
}



# ***** Playback and Capture *******************************************

# set up the playback/capture device
pcm.duplex
{
    type asym

    # point playback output to use dmix
    playback.pcm "dmix"

    # point capture input record to use dsnoop
    capture.pcm "dsnoop"
}


!!Aplay/Arecord output
!!--------------------

APLAY

**** List of PLAYBACK Hardware Devices ****
card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
card 0: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
card 0: HDMI [HDA ATI HDMI], device 8: HDMI 2 [HDMI 2]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
card 0: HDMI [HDA ATI HDMI], device 9: HDMI 3 [HDMI 3]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
card 0: HDMI [HDA ATI HDMI], device 10: HDMI 4 [HDMI 4]
   Subdevices: 1/1
   Subdevice #0: subdevice #0

ARECORD

**** List of CAPTURE Hardware Devices ****

!!Amixer output
!!-------------

!!-------Mixer controls for card 0 [HDMI]

Card hw:0 'HDMI'/'HDA ATI HDMI at 0xfebfc000 irq 46'
   Mixer name	: 'ATI R6xx HDMI'
   Components	: 'HDA:1002aa01,00aa0100,00100700'
   Controls      : 35
   Simple ctrls  : 5
Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined
   Playback channels: Mono
   Mono: Playback [on]
Simple mixer control 'IEC958',1
   Capabilities: pswitch pswitch-joined
   Playback channels: Mono
   Mono: Playback [on]
Simple mixer control 'IEC958',2
   Capabilities: pswitch pswitch-joined
   Playback channels: Mono
   Mono: Playback [on]
Simple mixer control 'IEC958',3
   Capabilities: pswitch pswitch-joined
   Playback channels: Mono
   Mono: Playback [on]
Simple mixer control 'IEC958',4
   Capabilities: pswitch pswitch-joined
   Playback channels: Mono
   Mono: Playback [on]

!!-------Mixer controls for card 1 [Interface]

Card hw:1 'Interface'/'M-Audio USB Uno MIDI Interface at 
usb-0000:00:12.2-1.2.3, full speed'
   Mixer name	: 'USB Mixer'
   Components	: 'USB0763:0150'
   Controls      : 1
   Simple ctrls  : 0

!!-------Mixer controls for card 2 [M1x1]

Card hw:2 'M1x1'/'M-Audio MidiSport 1x1 at usb-0000:00:12.2-1.2.2, full 
speed'
   Mixer name	: ''
   Components	: 'USB0763:1011'
   Controls      : 0
   Simple ctrls  : 0


!!Alsactl output
!!--------------

--startcollapse--
state.HDMI {
	control.1 {
		iface CARD
		name 'HDMI/DP,pcm=3 Jack'
		value false
		comment {
			access read
			type BOOLEAN
			count 1
		}
	}
	control.2 {
		iface MIXER
		name 'IEC958 Playback Con Mask'
		value 
'0fff000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
		comment {
			access read
			type IEC958
			count 1
		}
	}
	control.3 {
		iface MIXER
		name 'IEC958 Playback Pro Mask'
		value 
'0f00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
		comment {
			access read
			type IEC958
			count 1
		}
	}
	control.4 {
		iface MIXER
		name 'IEC958 Playback Default'
		value 
'0400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
		comment {
			access 'read write'
			type IEC958
			count 1
		}
	}
	control.5 {
		iface MIXER
		name 'IEC958 Playback Switch'
		value true
		comment {
			access 'read write'
			type BOOLEAN
			count 1
		}
	}
	control.6 {
		iface PCM
		device 3
		name ELD
		value ''
		comment {
			access 'read volatile'
			type BYTES
			count 0
		}
	}
	control.7 {
		iface CARD
		name 'HDMI/DP,pcm=7 Jack'
		value false
		comment {
			access read
			type BOOLEAN
			count 1
		}
	}
	control.8 {
		iface MIXER
		name 'IEC958 Playback Con Mask'
		index 1
		value 
'0fff000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
		comment {
			access read
			type IEC958
			count 1
		}
	}
	control.9 {
		iface MIXER
		name 'IEC958 Playback Pro Mask'
		index 1
		value 
'0f00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
		comment {
			access read
			type IEC958
			count 1
		}
	}
	control.10 {
		iface MIXER
		name 'IEC958 Playback Default'
		index 1
		value 
'0400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
		comment {
			access 'read write'
			type IEC958
			count 1
		}
	}
	control.11 {
		iface MIXER
		name 'IEC958 Playback Switch'
		index 1
		value true
		comment {
			access 'read write'
			type BOOLEAN
			count 1
		}
	}
	control.12 {
		iface PCM
		device 7
		name ELD
		value ''
		comment {
			access 'read volatile'
			type BYTES
			count 0
		}
	}
	control.13 {
		iface CARD
		name 'HDMI/DP,pcm=8 Jack'
		value false
		comment {
			access read
			type BOOLEAN
			count 1
		}
	}
	control.14 {
		iface MIXER
		name 'IEC958 Playback Con Mask'
		index 2
		value 
'0fff000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
		comment {
			access read
			type IEC958
			count 1
		}
	}
	control.15 {
		iface MIXER
		name 'IEC958 Playback Pro Mask'
		index 2
		value 
'0f00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
		comment {
			access read
			type IEC958
			count 1
		}
	}
	control.16 {
		iface MIXER
		name 'IEC958 Playback Default'
		index 2
		value 
'0400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
		comment {
			access 'read write'
			type IEC958
			count 1
		}
	}
	control.17 {
		iface MIXER
		name 'IEC958 Playback Switch'
		index 2
		value true
		comment {
			access 'read write'
			type BOOLEAN
			count 1
		}
	}
	control.18 {
		iface PCM
		device 8
		name ELD
		value ''
		comment {
			access 'read volatile'
			type BYTES
			count 0
		}
	}
	control.19 {
		iface CARD
		name 'HDMI/DP,pcm=9 Jack'
		value false
		comment {
			access read
			type BOOLEAN
			count 1
		}
	}
	control.20 {
		iface MIXER
		name 'IEC958 Playback Con Mask'
		index 3
		value 
'0fff000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
		comment {
			access read
			type IEC958
			count 1
		}
	}
	control.21 {
		iface MIXER
		name 'IEC958 Playback Pro Mask'
		index 3
		value 
'0f00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
		comment {
			access read
			type IEC958
			count 1
		}
	}
	control.22 {
		iface MIXER
		name 'IEC958 Playback Default'
		index 3
		value 
'0400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
		comment {
			access 'read write'
			type IEC958
			count 1
		}
	}
	control.23 {
		iface MIXER
		name 'IEC958 Playback Switch'
		index 3
		value true
		comment {
			access 'read write'
			type BOOLEAN
			count 1
		}
	}
	control.24 {
		iface PCM
		device 9
		name ELD
		value ''
		comment {
			access 'read volatile'
			type BYTES
			count 0
		}
	}
	control.25 {
		iface CARD
		name 'HDMI/DP,pcm=10 Jack'
		value false
		comment {
			access read
			type BOOLEAN
			count 1
		}
	}
	control.26 {
		iface MIXER
		name 'IEC958 Playback Con Mask'
		index 4
		value 
'0fff000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
		comment {
			access read
			type IEC958
			count 1
		}
	}
	control.27 {
		iface MIXER
		name 'IEC958 Playback Pro Mask'
		index 4
		value 
'0f00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
		comment {
			access read
			type IEC958
			count 1
		}
	}
	control.28 {
		iface MIXER
		name 'IEC958 Playback Default'
		index 4
		value 
'0400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
		comment {
			access 'read write'
			type IEC958
			count 1
		}
	}
	control.29 {
		iface MIXER
		name 'IEC958 Playback Switch'
		index 4
		value true
		comment {
			access 'read write'
			type BOOLEAN
			count 1
		}
	}
	control.30 {
		iface PCM
		device 10
		name ELD
		value ''
		comment {
			access 'read volatile'
			type BYTES
			count 0
		}
	}
	control.31 {
		iface PCM
		device 3
		name 'Playback Channel Map'
		value.0 0
		value.1 0
		value.2 0
		value.3 0
		value.4 0
		value.5 0
		value.6 0
		value.7 0
		comment {
			access 'read write'
			type INTEGER
			count 8
			range '0 - 36'
		}
	}
	control.32 {
		iface PCM
		device 7
		name 'Playback Channel Map'
		value.0 0
		value.1 0
		value.2 0
		value.3 0
		value.4 0
		value.5 0
		value.6 0
		value.7 0
		comment {
			access 'read write'
			type INTEGER
			count 8
			range '0 - 36'
		}
	}
	control.33 {
		iface PCM
		device 8
		name 'Playback Channel Map'
		value.0 0
		value.1 0
		value.2 0
		value.3 0
		value.4 0
		value.5 0
		value.6 0
		value.7 0
		comment {
			access 'read write'
			type INTEGER
			count 8
			range '0 - 36'
		}
	}
	control.34 {
		iface PCM
		device 9
		name 'Playback Channel Map'
		value.0 0
		value.1 0
		value.2 0
		value.3 0
		value.4 0
		value.5 0
		value.6 0
		value.7 0
		comment {
			access 'read write'
			type INTEGER
			count 8
			range '0 - 36'
		}
	}
	control.35 {
		iface PCM
		device 10
		name 'Playback Channel Map'
		value.0 0
		value.1 0
		value.2 0
		value.3 0
		value.4 0
		value.5 0
		value.6 0
		value.7 0
		comment {
			access 'read write'
			type INTEGER
			count 8
			range '0 - 36'
		}
	}
}
state.Interface {
	control.1 {
		iface CARD
		name 'Keep Interface'
		value false
		comment {
			access 'read write'
			type BOOLEAN
			count 1
		}
	}
}
state.M1x1 {
	control {
	}
}
--endcollapse--


!!All Loaded Modules
!!------------------

Module
snd_seq_dummy
snd_seq_midi
snd_seq_midi_event
snd_seq
bnep
rpcsec_gss_krb5
nfsv4
dns_resolver
nfs
fscache
cpufreq_userspace
cpufreq_conservative
cpufreq_powersave
bluetooth
pci_stub
vboxpci
drbg
ansi_cprng
vboxnetadp
ecdh_generic
rfkill
vboxnetflt
vboxdrv
ftdi_sio
usbserial
binfmt_misc
snd_usb_audio
snd_usbmidi_lib
snd_rawmidi
snd_seq_device
joydev
snd_hda_codec_hdmi
snd_hda_intel
snd_hda_codec
amd64_edac_mod
edac_mce_amd
amdgpu
snd_hda_core
snd_hwdep
snd_pcm_oss
kvm_amd
ccp
mgag200
rng_core
snd_mixer_oss
kvm
irqbypass
chash
snd_pcm
gpu_sched
ipmi_si
crct10dif_pclmul
evdev
crc32_pclmul
serio_raw
ghash_clmulni_intel
ipmi_devintf
snd_timer
ttm
ipmi_msghandler
drm_kms_helper
k10temp
sg
snd
fam15h_power
sp5100_tco
drm
soundcore
button
nfsd
auth_rpcgss
nfs_acl
lockd
grace
sunrpc
loop
vhba
ecryptfs
parport_pc
ppdev
lp
parport
ip_tables
x_tables
autofs4
sr_mod
cdrom
ext4
crc16
mbcache
jbd2
fscrypto
ecb
uas
usb_storage
hid_generic
usbhid
hid
btrfs
xor
zstd_decompress
zstd_compress
xxhash
sd_mod
raid6_pq
libcrc32c
crc32c_generic
vmd
crc32c_intel
ohci_pci
ata_generic
aesni_intel
aes_x86_64
ahci
crypto_simd
ehci_pci
ohci_hcd
pata_atiixp
libahci
cryptd
glue_helper
ehci_hcd
psmouse
libata
igb
usbcore
i2c_piix4
i2c_algo_bit
scsi_mod
usb_common
dca


!!Sysfs Files
!!-----------

/sys/class/sound/hwC0D0/init_pin_configs:
0x03 0x185600f0
0x05 0x185600f0
0x07 0x185600f0
0x09 0x185600f0
0x0b 0x185600f0
0x0d 0x585600f0

/sys/class/sound/hwC0D0/driver_pin_configs:

/sys/class/sound/hwC0D0/user_pin_configs:

/sys/class/sound/hwC0D0/init_verbs:

/sys/class/sound/hwC0D0/hints:


!!ALSA/HDA dmesg
!!--------------

Bug

[H-P.Teufel]

Sehr geehrte Damen und Herren, 
anbei die Meldung meines Rechners


hpt@saturn:/home/hpt$ less /var/lof/mes
/var/lof/mes: Datei oder Verzeichnis nicht gefunden
hpt@saturn:/home/hpt$ su -
Passwort: 
root@saturn:~# less /var/log/messages
root@saturn:~# cat /tmp/kernel-bug.txt 
Nov  2 15:09:11 saturn kernel: [  148.391127] ------------[ cut here ]------------
Nov  2 15:09:11 saturn kernel: [  148.392049] WARNING: at /build/linux-5VIh7j/linux-3.2.78/lib/kref.c:34 kref_get+0x1b/0x21()
Nov  2 15:09:11 saturn kernel: [  148.392049] Hardware name: To Be Filled By O.E.M.
Nov  2 15:09:11 saturn kernel: [  148.392049] Modules linked in: fuse cpufreq_powersave parport_pc cpufreq_stats ppdev cpufreq_conservative lp cpufreq_userspace parport w83627ehf hwmon_vid loop dm_crypt snd_hda_codec_realtek arc4 rtl8187 eeprom_93cx6 mac80211 nouveau cfg80211 rfkill snd_hda_intel ttm snd_hda_codec snd_hwdep snd_pcm drm_kms_helper drm snd_page_alloc edac_mce_amd snd_seq snd_seq_device snd_timer mxm_wmi video snd powernow_k8 edac_core mperf k10temp wmi power_supply i2c_algo_bit processor soundcore button i2c_nforce2 thermal_sys i2c_core pcspkr evdev ext3 mbcache jbd dm_mod md_mod usbhid hid sr_mod cdrom sg sd_mod crc_t10dif ata_generic usb_storage ohci_hcd ahci libahci pata_amd ehci_hcd libata forcedeth scsi_mod usbcore usb_common [last unloaded: scsi_wait_scan]
Nov  2 15:09:11 saturn kernel: [  148.427473] Pid: 11, comm: kworker/0:1 Not tainted 3.2.0-4-amd64 #1 Debian 3.2.78-1
Nov  2 15:09:11 saturn kernel: [  148.427473] Call Trace:
Nov  2 15:09:11 saturn kernel: [  148.427473]  [<ffffffff81046e31>] ? warn_slowpath_common+0x78/0x8c
Nov  2 15:09:11 saturn kernel: [  148.427473]  [<ffffffff811aebd2>] ? kref_get+0x1b/0x21
Nov  2 15:09:11 saturn kernel: [  148.427473]  [<ffffffff811ada85>] ? kobject_get+0x12/0x17
Nov  2 15:09:11 saturn kernel: [  148.427473]  [<ffffffff81250913>] ? get_device+0x11/0x17
Nov  2 15:09:11 saturn kernel: [  148.427473]  [<ffffffffa00409d4>] ? scsi_request_fn+0x2c/0x51e [scsi_mod]
Nov  2 15:09:11 saturn kernel: [  148.427473]  [<ffffffff81039b54>] ? finish_task_switch+0x51/0xbc
Nov  2 15:09:11 saturn kernel: [  148.427473]  [<ffffffff811a6fbe>] ? cfq_kick_queue+0x25/0x34
Nov  2 15:09:11 saturn kernel: [  148.427473]  [<ffffffff8105b7d7>] ? process_one_work+0x161/0x269
Nov  2 15:09:11 saturn kernel: [  148.427473]  [<ffffffff8105c7a0>] ? worker_thread+0xc2/0x145
Nov  2 15:09:11 saturn kernel: [  148.427473]  [<ffffffff8105c6de>] ? manage_workers.isra.25+0x15b/0x15b
Nov  2 15:09:11 saturn kernel: [  148.427473]  [<ffffffff8105f8ed>] ? kthread+0x76/0x7e
Nov  2 15:09:11 saturn kernel: [  148.427473]  [<ffffffff813593f4>] ? kernel_thread_helper+0x4/0x10
Nov  2 15:09:11 saturn kernel: [  148.427473]  [<ffffffff8105f877>] ? kthread_worker_fn+0x139/0x139
Nov  2 15:09:11 saturn kernel: [  148.427473]  [<ffffffff813593f0>] ? gs_change+0x13/0x13
Nov  2 15:09:11 saturn kernel: [  148.427473] ---[ end trace 505b6a2dee3a96dc ]---
Nov  2 15:09:11 saturn kernel: [  148.577647] CPU 0 
Nov  2 15:09:11 saturn kernel: [  148.579499] Modules linked in: fuse cpufreq_powersave parport_pc cpufreq_stats ppdev cpufreq_conservative lp cpufreq_userspace parport w83627ehf hwmon_vid loop dm_crypt snd_hda_codec_realtek arc4 rtl8187 eeprom_93cx6 mac80211 nouveau cfg80211 rfkill snd_hda_intel ttm snd_hda_codec snd_hwdep snd_pcm drm_kms_helper drm snd_page_alloc edac_mce_amd snd_seq snd_seq_device snd_timer mxm_wmi video snd powernow_k8 edac_core mperf k10temp wmi power_supply i2c_algo_bit processor soundcore button i2c_nforce2 thermal_sys i2c_core pcspkr evdev ext3 mbcache jbd dm_mod md_mod usbhid hid sr_mod cdrom sg sd_mod crc_t10dif ata_generic usb_storage ohci_hcd ahci libahci pata_amd ehci_hcd
Nov  2 15:09:11 saturn kernel: [  148.640033] usb 1-2: new high-speed USB device number 79 using ehci_hcd
Nov  2 15:09:11 saturn kernel: [  148.647612]  libata forcedeth scsi_mod usbcore usb_common [last unloaded: scsi_wait_scan]
Nov  2 15:09:11 saturn kernel: [  148.655985] 
Nov  2 15:09:11 saturn kernel: [  148.657503] Pid: 11, comm: kworker/0:1 Tainted: G        W    3.2.0-4-amd64 #1 Debian 3.2.78-1 To Be Filled By O.E.M. To Be Filled By O.E.M./K10N780SLIX3-WiFi
Nov  2 15:09:11 saturn kernel: [  148.671772] RIP: 0010:[<ffffffffa004468b>]  [<ffffffffa004468b>] scsi_device_dev_release_usercontext+0x66/0x187 [scsi_mod]
Nov  2 15:09:11 saturn kernel: [  148.682901] RSP: 0018:ffff88012aeedd50  EFLAGS: 00010046
Nov  2 15:09:11 saturn kernel: [  148.688236] RAX: 0000000000000246 RBX: ffff8800cf82be38 RCX: dead000000100100
Nov  2 15:09:11 saturn kernel: [  148.695399] RDX: dead000000200200 RSI: dead000000100100 RDI: dead000000200200
Nov  2 15:09:11 saturn kernel: [  148.702571] RBP: ffff8800cf82b800 R08: dead000000100100 R09: dead000000200200


Mit freundlichen Grüßen
Hans-Peter Teufel

Re: Bug

[Dennis Kaarsemaker]

On Tue, 2016-09-13 at 13:18 -0400, Mike Hawes wrote:
> To whom this may concern,
>
> I found a bug in git while trying to push my website.
> I redid the process and it happened again.
> I also tried it on another computer and it happened again.
> I was wondering how to claim a bug?

Hi Mike,

When you think git does not behave as you expect, please do not stop
your bug report with just "git does not work".  "I used git in this
way, but it did not work" is not much better, neither is "I used git
in this way, and X happend, which is broken".  It often is that git is
correct to cause X happen in such a case, and it is your expectation
that is broken. People would not know what other result Y you expected
to see instead of X, if you left it unsaid.

Please remember to always state

 - what you wanted to achieve;

 - what you did (the version of git and the command sequence to reproduce
   the behavior);

 - what you saw happen (X above);

 - what you expected to see (Y above); and

 - how the last two are different.

See http://www.chiark.greenend.org.uk/~sgtatham/bugs.html for further
hints.

(The above was shamelessly copied from the "A note from the maintainer" mails)

D.

Re: Bug

[Santiago Torres]

Hi, Michael.

It would be helpful to get more context on what triggered this bug. I'm
not a 'core' dev, so there may be a better way to send this. In general,
you want to state the following:

0) Information about your git installation, host system, etc.
1) Information about your repo (was it GitHub? local? self-hosted?)
2) What did you do? (git push origin master? git push?)
3) What happened instead of working? (the error message would be
   helpful.

Hope this helps.

Cheers!
-Santiago.

On Tue, Sep 13, 2016 at 01:18:52PM -0400, Mike Hawes wrote:
> To whom this may concern,
> 
> I found a bug in git while trying to push my website.
> 
> I redid the process and it happened again.
> 
> I also tried it on another computer and it happened again.
> 
> I was wondering how to claim a bug?
> 
> Thank you,
> 
> 
> Michael Hawes

Bug

[Mike Hawes]

To whom this may concern,

I found a bug in git while trying to push my website.

I redid the process and it happened again.

I also tried it on another computer and it happened again.

I was wondering how to claim a bug?

Thank you,


Michael Hawes

Re: Bug

[Leonard Bocock]

Hi Luiz

I haven=E2=80=99t been able to track it through logs. It may be iOS 9.4 =
related or hardware related.=20

I=E2=80=99ve decided to move the product under development to IP =
wireless zero config.=20

Bluez is too unstable, too difficult to work with in it=E2=80=99s =
current form (no code comments, no documentation).=20

I=E2=80=99ve invested too much time in it already.=20

Thanks, Leonard

> On 23/08/2016, at 8:41 PM, Luiz Augusto von Dentz =
<luiz.dentz@gmail.com> wrote:
>=20
> Hi Leonard,
>=20
> On Fri, Aug 19, 2016 at 11:44 PM, Leonard Bocock
> <leonard.bocock@gmail.com> wrote:
>> The tools/gatt-service.c no longer works under 5.41. It worked under =
5.3x.
>>=20
>> An iPhone will connect to it; however timeout while reading =
characteristics.
>=20
> Logs? Have you tried running upstream version?
>=20
> --=20
> Luiz Augusto von Dentz

Leonard Bocock
leonard.bocock@gmail.com
Mobile: 	+64 (0)211 498 052

Re: Bug

[Luiz Augusto von Dentz]

Hi Leonard,

On Fri, Aug 19, 2016 at 11:44 PM, Leonard Bocock
<leonard.bocock@gmail.com> wrote:
> The tools/gatt-service.c no longer works under 5.41. It worked under 5.3x.
>
> An iPhone will connect to it; however timeout while reading characteristics.

Logs? Have you tried running upstream version?

-- 
Luiz Augusto von Dentz

Bug

[Leonard Bocock]

The tools/gatt-service.c no longer works under 5.41. It worked under 5.3x.

An iPhone will connect to it; however timeout while reading characteristics.

Thanks,
Leonard 

Re: Bug

[Gleb Natapov]

On Fri, Nov 29, 2013 at 12:28:06PM +0100, Otártics András wrote:
> Hi,
>    I think I found a bug that I do not want to post on any public
> bugtrackers of KVM.
>   Please let me know a mail to write to.
> 
Look up KVM maintainers in MAINTAINERS file in the root of the Linux source
tree and email to them.

--
			Gleb.

Bug

[Otártics András]

Hi,
    I think I found a bug that I do not want to post on any public 
bugtrackers of KVM.
   Please let me know a mail to write to.

Thank you in advance!
Bests,
András

bug

[squadrato]

Hello i own a Fujitsu ah512 laptop. As described in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1159690
I cannot switch the wireless with fn + f5, even in the last ubuntu version, 
released yesterday.
grretings

Re: bug

[David Sterba]

On Thu, Aug 29, 2013 at 10:34:00AM +0800, lilofile wrote:
>  I made a btrfs on five disks using RAID5 (-d raid5 for mount option).
>  When a power failure occurs, I can not remount btrfs after my system
>  reboots. Dmesg for remount is presented as following:

Please note that current implementation of raid5/6 is not completely
crash-safe, as was mentioned in the announcement (eg. here
http://lwn.net/Articles/536038/). The mount could fail if the parity of
metadata blocks is corrupted due to crash.

david

Re: bug

[Liu Bo]

On Thu, Aug 29, 2013 at 10:34:00AM +0800, lilofile wrote:
>  I made a btrfs on five disks using RAID5 (-d raid5 for mount option). When a power failure occurs, I can not remount btrfs after my system reboots. Dmesg for remount is presented as following:
>  
> [  192.713953] bio: create slab <bio-1> at 1
> [  192.716230] Btrfs loaded
> [  192.717177] device fsid a0dff7ea-9354-43fd-8516-0e17f370991d devid 1 transid 6 /dev/sdb
> [  192.717712] btrfs: disk space caching is enabled
> [  192.720572] btrfs: failed to read the system array on sdb
> [  192.723398] btrfs: open_ctree failed
>  
> linux md raid5 have resync , the test seems btrfs raid5 have not resync,how fix the bug?

Have you tried 'btrfs device scan' before mounting it?

-liubo

bug

[lilofile]

 I made a btrfs on five disks using RAID5 (-d raid5 for mount option). When a power failure occurs, I can not remount btrfs after my system reboots. Dmesg for remount is presented as following:
 
[  192.713953] bio: create slab <bio-1> at 1
[  192.716230] Btrfs loaded
[  192.717177] device fsid a0dff7ea-9354-43fd-8516-0e17f370991d devid 1 transid 6 /dev/sdb
[  192.717712] btrfs: disk space caching is enabled
[  192.720572] btrfs: failed to read the system array on sdb
[  192.723398] btrfs: open_ctree failed
 
linux md raid5 have resync , the test seems btrfs raid5 have not resync,how fix the bug?

Re: bug

[Takashi Iwai]

At Thu, 08 Aug 2013 12:44:24 +0200,
Mattia Bertoni wrote:
> 
> user-side there is no problem
> 
> because alsa logs this issue I report it....

Ah, so you took the chatty words in the pulseaudio log seriously.
Now I got it.  It's been mostly harmless as long as you don't see any
obvious problems, especially on the old hardware :)


Takashi

> On 08/08/13 12:12, Takashi Iwai wrote:
> > At Thu, 08 Aug 2013 11:55:50 +0200,
> > Mattia Bertoni wrote:
> >> 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 have no idea *what* problem you're talking about.  (And your mail
> > subject says only "bug".  Yes, there must be lots of bugs in the
> > world, virtually and really...)
> >
> > Please begin with describing what's the problem at first.
> >
> >
> > Takashi
> 
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> 

Re: bug

[Mattia Bertoni]

user-side there is no problem

because alsa logs this issue I report it....




On 08/08/13 12:12, Takashi Iwai wrote:
> At Thu, 08 Aug 2013 11:55:50 +0200,
> Mattia Bertoni wrote:
>> 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 have no idea *what* problem you're talking about.  (And your mail
> subject says only "bug".  Yes, there must be lots of bugs in the
> world, virtually and really...)
>
> Please begin with describing what's the problem at first.
>
>
> Takashi

Re: bug

[Takashi Iwai]

At Thu, 08 Aug 2013 11:55:50 +0200,
Mattia Bertoni wrote:
> 
> 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 have no idea *what* problem you're talking about.  (And your mail
subject says only "bug".  Yes, there must be lots of bugs in the
world, virtually and really...)

Please begin with describing what's the problem at first.


Takashi

Re: bug

[Mattia Bertoni]

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

Re: bug

[Takashi Iwai]

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

Re: bug

[Mattia Bertoni]

I uploaded the full log on pastebin:           http://pastebin.com/4whbdz79

I hope this help you!




On 08/07/13 19:14, 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:
>
> Jun 15 18:18:00 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c: snd_pcm_avail() returned a value that is exceptionally 
> large: 420736 bytes (2191 ms).
> Jun 15 18:18:00 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c: Most likely this is a bug in the ALSA driver 
> 'snd_intel8x0'. Please report this issue to the ALSA developers.
> Jun 15 18:18:00 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c: snd_pcm_dump():
> Jun 15 18:18:00 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c: Hardware PCM card 0 'NVidia CK804' device 0 subdevice 0
> Jun 15 18:18:00 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c: Its setup is:
> Jun 15 18:18:00 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   stream       : PLAYBACK
> Jun 15 18:18:00 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   access       : MMAP_INTERLEAVED
> Jun 15 18:18:00 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   format       : S16_LE
> Jun 15 18:18:00 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   subformat    : STD
> Jun 15 18:18:00 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   channels     : 2
> Jun 15 18:18:00 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   rate         : 48000
> Jun 15 18:18:00 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   exact rate   : 48000 (48000/1)
> Jun 15 18:18:03 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   msbits       : 16
> Jun 15 18:18:03 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   buffer_size  : 16384
> Jun 15 18:18:03 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   period_size  : 16384
> Jun 15 18:18:03 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   period_time  : 341333
> Jun 15 18:18:03 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   tstamp_mode  : ENABLE
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   period_step  : 1
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   avail_min    : 16384
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   period_event : 0
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   start_threshold  : -1
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   stop_threshold   : 4611686018427387904
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   silence_threshold: 0
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   silence_size : 0
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   boundary     : 4611686018427387904
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   appl_ptr     : 26406104
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   hw_ptr       : 26494904
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c: snd_pcm_delay() returned a value that is exceptionally 
> large: -465056 bytes (-2422 ms).
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c: Most likely this is a bug in the ALSA driver 
> 'snd_intel8x0'. Please report this issue to the ALSA developers.
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c: snd_pcm_dump():
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c: Hardware PCM card 0 'NVidia CK804' device 0 subdevice 0
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c: Its setup is:
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   stream       : PLAYBACK
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   access       : MMAP_INTERLEAVED
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   format       : S16_LE
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   subformat    : STD
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   channels     : 2
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   rate         : 48000
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   exact rate   : 48000 (48000/1)
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   msbits       : 16
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   buffer_size  : 16384
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   period_size  : 16384
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   period_time  : 341333
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   tstamp_mode  : ENABLE
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   period_step  : 1
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   avail_min    : 16384
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   period_event : 0
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   start_threshold  : -1
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   stop_threshold   : 4611686018427387904
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   silence_threshold: 0
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   silence_size : 0
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   boundary     : 4611686018427387904
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   appl_ptr     : 26569944
> Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
> alsa-util.c:   hw_ptr       : 26686208

bug

[Mattia Bertoni]

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:

Jun 15 18:18:00 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c: snd_pcm_avail() returned a value that is exceptionally 
large: 420736 bytes (2191 ms).
Jun 15 18:18:00 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c: Most likely this is a bug in the ALSA driver 
'snd_intel8x0'. Please report this issue to the ALSA developers.
Jun 15 18:18:00 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c: snd_pcm_dump():
Jun 15 18:18:00 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c: Hardware PCM card 0 'NVidia CK804' device 0 subdevice 0
Jun 15 18:18:00 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c: Its setup is:
Jun 15 18:18:00 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   stream       : PLAYBACK
Jun 15 18:18:00 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   access       : MMAP_INTERLEAVED
Jun 15 18:18:00 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   format       : S16_LE
Jun 15 18:18:00 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   subformat    : STD
Jun 15 18:18:00 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   channels     : 2
Jun 15 18:18:00 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   rate         : 48000
Jun 15 18:18:00 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   exact rate   : 48000 (48000/1)
Jun 15 18:18:03 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   msbits       : 16
Jun 15 18:18:03 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   buffer_size  : 16384
Jun 15 18:18:03 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   period_size  : 16384
Jun 15 18:18:03 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   period_time  : 341333
Jun 15 18:18:03 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   tstamp_mode  : ENABLE
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   period_step  : 1
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   avail_min    : 16384
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   period_event : 0
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   start_threshold  : -1
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   stop_threshold   : 4611686018427387904
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   silence_threshold: 0
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   silence_size : 0
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   boundary     : 4611686018427387904
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   appl_ptr     : 26406104
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   hw_ptr       : 26494904
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c: snd_pcm_delay() returned a value that is exceptionally 
large: -465056 bytes (-2422 ms).
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c: Most likely this is a bug in the ALSA driver 
'snd_intel8x0'. Please report this issue to the ALSA developers.
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c: snd_pcm_dump():
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c: Hardware PCM card 0 'NVidia CK804' device 0 subdevice 0
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c: Its setup is:
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   stream       : PLAYBACK
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   access       : MMAP_INTERLEAVED
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   format       : S16_LE
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   subformat    : STD
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   channels     : 2
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   rate         : 48000
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   exact rate   : 48000 (48000/1)
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   msbits       : 16
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   buffer_size  : 16384
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   period_size  : 16384
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   period_time  : 341333
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   tstamp_mode  : ENABLE
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   period_step  : 1
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   avail_min    : 16384
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   period_event : 0
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   start_threshold  : -1
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   stop_threshold   : 4611686018427387904
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   silence_threshold: 0
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   silence_size : 0
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   boundary     : 4611686018427387904
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   appl_ptr     : 26569944
Jun 15 18:18:04 arch-dekstop pulseaudio[776]: [alsa-sink-Intel ICH] 
alsa-util.c:   hw_ptr       : 26686208

Re: BUG

[Duncan]

Mark Murawski posted on Tue, 11 Jun 2013 11:11:25 -0400 as excerpted:

> Jun 10 05:24:57 localhost kernel: BUG: unable to handle kernel NULL
> pointer dereference at 0000000000000090

I'll let someone else handle the real technical stuff, but I distinctly 
recall reading that a number of null-pointer bugs had been fixed for 
3.10, and you're running 3.9, so I could suggest trying the latest Linus-
tree rc (3.10.0-rc5 just came out a couple days ago) or live-git HEAD.

I've been running 3.10-pre here with a (new) dual-SSD raid-1 data/
metadata both set of btrfs filesystems (I partition mine down, less eggs 
in one filesystem basket), without issue so far.

Might nor might not be the same bug; as I said I don't get that deep into 
the technical stuff, but it's worth a try.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

BUG

[Mark Murawski]

With this array I have to mount -o degraded, even though all devices are 
present.

Linux cartman 3.9.0 #1 SMP PREEMPT Fri May 3 22:02:21 EDT 2013 x86_64 
GNU/Linux
btrfs-tools 
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git * 
master 7854c8b


When I try and mount without degraded, I get this:
btrfs: failed to read chunk tree on sdh
btrfs: open_ctree failed


Mounting -o degraded, I get this:

cartman {~} root# btrfs filesystem show
Label: none  uuid: d71404d4-468e-47d5-8f06-3b65fa7776aa
         Total devices 2 FS bytes used 7.01GB
         devid    1 size 9.31GB used 8.35GB path /dev/sdg6
         devid    3 size 9.31GB used 8.34GB path /dev/sdc6

Label: none  uuid: b142f575-df1c-4a57-8846-a43b979e2e09
         Total devices 8 FS bytes used 1.79TB
         devid    4 size 149.05GB used 7.00GB path /dev/sdh
         devid    6 size 920.34GB used 495.00GB path /dev/sdg7
         devid    8 size 1.36TB used 1.21TB path /dev/sdf
         devid    2 size 465.76GB used 303.00GB path /dev/sde
         devid    3 size 149.05GB used 6.00GB path /dev/sdd
         devid    5 size 920.34GB used 745.03GB path /dev/sdc7
         devid    9 size 465.76GB used 303.00GB path /dev/sdb
         devid    7 size 1.36TB used 1.21TB path /dev/sda

Btrfs v0.20-rc1-253-g7854c8b

Tried to fix up /dev/sdh...

cartman {~} root# btrfs device delete /dev/sdh /storage

btrfs: bdev /dev/sda errs: wr 0, rd 0, flush 0, corrupt 4733368, gen 0
btrfs: relocating block group 4787944816640 flags 17
btrfs: free space inode generation (0) did not match free space cache 
generation (19517)
btrfs: free space inode generation (0) did not match free space cache 
generation (19519)
btrfs: free space inode generation (0) did not match free space cache 
generation (19519)
btrfs: free space inode generation (0) did not match free space cache 
generation (8540)
btrfs: free space inode generation (0) did not match free space cache 
generation (9080)
btrfs: free space inode generation (0) did not match free space cache 
generation (9143)
btrfs: free space inode generation (0) did not match free space cache 
generation (28604)
btrfs: free space inode generation (0) did not match free space cache 
generation (28604)
btrfs: free space inode generation (0) did not match free space cache 
generation (30096)
btrfs: free space inode generation (0) did not match free space cache 
generation (28551)
btrfs: free space inode generation (0) did not match free space cache 
generation (30191)
btrfs: free space inode generation (0) did not match free space cache 
generation (28613)
btrfs: free space inode generation (0) did not match free space cache 
generation (30191)
btrfs: free space inode generation (0) did not match free space cache 
generation (30191)
btrfs: free space inode generation (0) did not match free space cache 
generation (19382)
btrfs: free space inode generation (0) did not match free space cache 
generation (28867)
btrfs: free space inode generation (0) did not match free space cache 
generation (28623)
btrfs: free space inode generation (0) did not match free space cache 
generation (28623)
btrfs: free space inode generation (0) did not match free space cache 
generation (19382)
btrfs: free space inode generation (0) did not match free space cache 
generation (19387)
btrfs: free space inode generation (0) did not match free space cache 
generation (19387)
btrfs: free space inode generation (0) did not match free space cache 
generation (19387)
btrfs: free space inode generation (0) did not match free space cache 
generation (19387)
btrfs: free space inode generation (0) did not match free space cache 
generation (19387)
Jun 10 05:20:21 localhost kernel: btrfs: found 31 extents
Jun 10 05:20:30 localhost kernel: btrfs: found 31 extents
Jun 10 05:20:30 localhost kernel: btrfs: relocating block group 
4784723591168 flags 17
Jun 10 05:21:00 localhost kernel: btrfs: found 33 extents
Jun 10 05:21:11 localhost kernel: btrfs: found 33 extents
Jun 10 05:21:11 localhost kernel: btrfs: relocating block group 
4781502365696 flags 17
Jun 10 05:21:40 localhost kernel: btrfs: found 29 extents
Jun 10 05:21:49 localhost kernel: btrfs: found 29 extents
Jun 10 05:21:49 localhost kernel: btrfs: relocating block group 
4778281140224 flags 17
Jun 10 05:22:19 localhost kernel: btrfs: found 65 extents
Jun 10 05:22:32 localhost kernel: btrfs: found 65 extents
Jun 10 05:22:33 localhost kernel: btrfs: relocating block group 
4775059914752 flags 17
Jun 10 05:23:04 localhost kernel: btrfs: found 20 extents
Jun 10 05:23:11 localhost kernel: btrfs: found 20 extents
Jun 10 05:23:13 localhost kernel: btrfs: relocating block group 
4771838689280 flags 17
Jun 10 05:23:41 localhost kernel: btrfs: found 27 extents
Jun 10 05:23:48 localhost kernel: btrfs: found 27 extents
Jun 10 05:23:49 localhost kernel: btrfs: relocating block group 
4768617463808 flags 17
Jun 10 05:24:17 localhost kernel: btrfs: found 14 extents
Jun 10 05:24:24 localhost kernel: btrfs: found 14 extents
Jun 10 05:24:57 localhost kernel: BUG: unable to handle kernel NULL 
pointer dereference at 0000000000000090
Jun 10 05:24:57 localhost kernel: IP: [<ffffffff81131ef0>] 
bio_phys_segments+0x20/0x20
Jun 10 05:24:57 localhost kernel: PGD 74285067 PUD 73ca5067 PMD 0
Jun 10 05:24:57 localhost kernel: Oops: 0000 [#1] PREEMPT SMP
Jun 10 05:24:57 localhost kernel: Modules linked in:
Jun 10 05:24:57 localhost kernel: CPU 0
Jun 10 05:24:57 localhost kernel: Pid: 16027, comm: btrfs-transacti Not 
tainted 3.9.0 #1 Gigabyte Technology Co., Ltd. GA-MA74GM-S2/GA-MA74GM-S2
Jun 10 05:24:57 localhost kernel: RIP: 0010:[<ffffffff81131ef0>] 
[<ffffffff81131ef0>] bio_phys_segments+0x20/0x20
Jun 10 05:24:57 localhost kernel: RSP: 0018:ffff8800546c3820  EFLAGS: 
00010246
Jun 10 05:24:57 localhost kernel: RAX: 0000000000000000 RBX: 
ffff8800546c3ab0 RCX: 000000011a262f30
Jun 10 05:24:57 localhost kernel: RDX: 0000000000000100 RSI: 
ffff88004f5b6660 RDI: 0000000000000000
Jun 10 05:24:57 localhost kernel: RBP: 0000000000001000 R08: 
0000000000001000 R09: 0000000000000000
Jun 10 05:24:57 localhost kernel: R10: 0000000000000000 R11: 
0000000000000014 R12: 0000000000000000
Jun 10 05:24:57 localhost kernel: R13: ffff88004f5b6660 R14: 
0000000000000000 R15: 000000011a262f30
Jun 10 05:24:57 localhost kernel: FS:  00007fa95eb7e7a0(0000) 
GS:ffff880077a00000(0000) knlGS:0000000000000000
Jun 10 05:24:57 localhost kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 
000000008005003b
Jun 10 05:24:57 localhost kernel: CR2: 0000000000000090 CR3: 
00000000745c5000 CR4: 00000000000007f0
Jun 10 05:24:57 localhost kernel: DR0: 0000000000000000 DR1: 
0000000000000000 DR2: 0000000000000000
Jun 10 05:24:57 localhost kernel: DR3: 0000000000000000 DR6: 
00000000ffff0ff0 DR7: 0000000000000400
Jun 10 05:24:57 localhost kernel: Process btrfs-transacti (pid: 16027, 
threadinfo ffff8800546c2000, task ffff8800752dbf20)
Jun 10 05:24:57 localhost kernel: Stack:
Jun 10 05:24:57 localhost kernel: ffffffff8129f64c 0000000000000000 
ffffea000122fcc0 0000000000000000
Jun 10 05:24:57 localhost kernel: 0000000000000000 ffffffff8129f360 
0000000000000411 ffffffff8125efe7
Jun 10 05:24:57 localhost kernel: ffff88004f5b6660 0000000000001000 
0000000000000000 000002344c5e6000
Jun 10 05:24:57 localhost kernel: Call Trace:
Jun 10 05:24:57 localhost kernel: [<ffffffff8129f64c>] ? 
submit_extent_page.isra.47+0x1cc/0x250
Jun 10 05:24:57 localhost kernel: [<ffffffff8129f360>] ? 
end_extent_writepage+0x70/0x70
Jun 10 05:24:57 localhost kernel: [<ffffffff8125efe7>] ? comp_keys+0x27/0x30
Jun 10 05:24:57 localhost kernel: [<ffffffff812a0385>] ? 
__extent_writepage+0x585/0x720
Jun 10 05:24:57 localhost kernel: [<ffffffff8129f360>] ? 
end_extent_writepage+0x70/0x70
Jun 10 05:24:57 localhost kernel: [<ffffffff812a0728>] ? 
extent_write_cache_pages.isra.39.constprop.52+0x208/0x370
Jun 10 05:24:57 localhost kernel: [<ffffffff812a0acb>] ? 
extent_writepages+0x4b/0x70
Jun 10 05:24:57 localhost kernel: [<ffffffff81287b10>] ? 
btrfs_fiemap+0x80/0x80
Jun 10 05:24:57 localhost kernel: [<ffffffff810c8a69>] ? 
__filemap_fdatawrite_range+0x49/0x50
Jun 10 05:24:57 localhost kernel: [<ffffffff8129b47f>] ? 
btrfs_wait_ordered_range+0x3f/0x100
Jun 10 05:24:57 localhost kernel: [<ffffffff812c0592>] ? 
__btrfs_write_out_cache+0x7b2/0x9d0
Jun 10 05:24:57 localhost kernel: [<ffffffff8127d90d>] ? 
btrfs_buffer_uptodate+0x6d/0x80
Jun 10 05:24:57 localhost kernel: [<ffffffff812c0847>] ? 
btrfs_write_out_cache+0x97/0xf0
Jun 10 05:24:57 localhost kernel: [<ffffffff812a1f20>] ? 
set_extent_buffer_dirty+0x60/0xa0
Jun 10 05:24:57 localhost kernel: [<ffffffff812730ca>] ? 
btrfs_write_dirty_block_groups+0x54a/0x640
Jun 10 05:24:57 localhost kernel: [<ffffffff812e5ffe>] ? 
btrfs_run_dev_replace+0x5e/0x350
Jun 10 05:24:57 localhost kernel: [<ffffffff8128108a>] ? 
commit_cowonly_roots+0x18a/0x280
Jun 10 05:24:57 localhost kernel: [<ffffffff81282dbd>] ? 
btrfs_commit_transaction+0x49d/0x9d0
Jun 10 05:24:57 localhost kernel: [<ffffffff8107dd70>] ? 
abort_exclusive_wait+0xb0/0xb0
Jun 10 05:24:57 localhost kernel: [<ffffffff8128397b>] ? 
start_transaction+0x9b/0x430
Jun 10 05:24:57 localhost kernel: [<ffffffff8127aac5>] ? 
transaction_kthread+0x195/0x210
Jun 10 05:24:57 localhost kernel: [<ffffffff8127a930>] ? 
btrfs_alloc_root+0x30/0x30
Jun 10 05:24:57 localhost kernel: [<ffffffff8107d423>] ? kthread+0xb3/0xc0
Jun 10 05:24:57 localhost kernel: [<ffffffff81080000>] ? 
hrtimer_forward+0xa0/0xc0
Jun 10 05:24:57 localhost kernel: [<ffffffff8107d370>] ? 
kthread_freezable_should_stop+0x60/0x60
Jun 10 05:24:57 localhost kernel: [<ffffffff81769cac>] ? 
ret_from_fork+0x7c/0xb0
Jun 10 05:24:57 localhost kernel: [<ffffffff8107d370>] ? 
kthread_freezable_should_stop+0x60/0x60
Jun 10 05:24:57 localhost kernel: Code: 31 c0 e8 f5 ea 62 00 eb ae 90 90 
f6 46 18 08 53 48 89 f3 74 05 8b 43 2c 5b c3 e8 1c f2 1d 00 eb f4 66 2e 
0f 1f 84 00 00                    00 00 00 <48> 8b 87 90 00 00 00 b9 00 
01 00 00 48 8b 90 60 02 00 00 0f b7
Jun 10 05:24:57 localhost kernel: RIP  [<ffffffff81131ef0>] 
bio_phys_segments+0x20/0x20
Jun 10 05:24:57 localhost kernel: RSP <ffff8800546c3820>
Jun 10 05:24:57 localhost kernel: CR2: 0000000000000090
Jun 10 05:24:57 localhost kernel: ---[ end trace 22bc28adecc95827 ]---

Bug

[Володимир Остап]

Hi,

[1. ] copy data from USB flash drive hungs-up the PC or router

[2.] If user copy data from USB flash drive CPU load is going to 100% by kernel.

Test CPU usage, 1 core, router with USB
-------------------------------------
CPU idle: 98.0% user: 0.0% kernel: 2.0% [sys: 1.0% hardirq: 0.0%
softirq: 1.0%] iowait : 0.0% steal: 0.0% Period: 1.0
CPU idle: 99.0% user: 1.0% kernel: 0.0% [sys: 0.0% hardirq: 0.0%
softirq: 0.0%] iowait : 0.0% steal: 0.0% Period: 1.0
cat dev/sda > dev/null
CPU idle: 70.3% user: 1.0% kernel: 16.8% [sys: 13.9% hardirq: 0.0%
softirq: 3.0%] iowait : 11.9% steal: 0.0% Period: 1.0
CPU idle: 0.0% user: 2.0% kernel: 53.0% [sys: 45.0% hardirq: 1.0%
softirq: 7.0%] iowait : 45.0% steal: 0.0% Period: 1.0
CPU idle: 0.0% user: 1.0% kernel: 55.0% [sys: 47.0% hardirq: 1.0%
softirq: 7.0%] iowait : 44.0% steal: 0.0% Period: 1.0

It is OK if you don't like to work with this router.

But, If you try to work with some software in user space you will be
disappointed. Kernel doesn't free CPU for user space at all.

CPU is fully occupied by URB kernel mechanism.


Test CPU usage, 2 core, PC
-------------------------------------

06:57:10 PM     CPU     %user     %nice   %system   %iowait    %steal     %idle
06:57:11 PM     all      0.99      0.00      0.50      0.00      0.00     98.51
06:57:11 PM       0      1.01      0.00      0.00      0.00      0.00     98.99
06:57:11 PM       1      0.97      0.00      0.97      0.00      0.00     98.06

06:57:11 PM     CPU     %user     %nice   %system   %iowait    %steal     %idle
06:57:12 PM     all      2.96      0.00      2.96     10.84      0.00     83.25
06:57:12 PM       0      1.98      0.00      4.95     10.89      0.00     82.18
06:57:12 PM       1      3.92      0.00      0.98     11.76      0.00     83.33

cat dev/sda > dev/null

06:57:12 PM     CPU     %user     %nice   %system   %iowait    %steal     %idle
06:57:13 PM     all      1.96      0.00      4.41     45.10      0.00     48.53
06:57:13 PM       0      0.00      0.00      5.00     47.00      0.00     48.00
06:57:13 PM       1      3.85      0.00      4.81     42.31      0.00     49.04

06:57:13 PM     CPU     %user     %nice   %system   %iowait    %steal     %idle
06:57:14 PM     all      1.97      0.00      2.96     48.28      0.00     46.80
06:57:14 PM       0      2.00      0.00      2.00     22.00      0.00     74.00
06:57:14 PM       1      1.90      0.00      3.81     73.33      0.00     20.95

06:57:14 PM     CPU     %user     %nice   %system   %iowait    %steal     %idle
06:57:15 PM     all      7.32      0.00      6.34     42.44      0.00     43.90
06:57:15 PM       0     10.89      0.00      2.97     35.64      0.00     50.50
06:57:15 PM       1      3.88      0.00      9.71     49.51      0.00     36.89

06:57:15 PM     CPU     %user     %nice   %system   %iowait    %steal     %idle
06:57:16 PM     all      1.47      0.00      2.94     46.57      0.00     49.02
06:57:16 PM       0      2.02      0.00      2.02     60.61      0.00     35.35
06:57:16 PM       1      1.87      0.00      3.74     32.71      0.00     61.68

It seems like power of 1 core is occupied by URB mechanism.

[3. ] Keywords: URB, USB, kernel, driver:

[4.] Kernel version (from /proc/version):

1 core router:

Linux version 2.6.21.5 #1 Fri Dec 16 20:04:52 EET 2011

For 2 core router:

Linux version 2.6.32-5-686 (Debian 2.6.32-28) (ben@decadent.org.uk)
(gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Thu Nov 25 18:43:34 UTC
2010


[6.] A small shell script or example program which triggers the

- sar -P 1 100 in another console

- execute cat /dev/sda > /dev/null in one terminal

[7.] Environment

[7.1.] Software (add the output of the ver_linux script here)

1 Core CPU board: script cannot be executed.

2 Core CPU PC:

If some fields are empty or look unusual you may have an old version.

Compare to the current minimal requirements in Documentation/Changes.

Linux volodymyro 2.6.32-5-686 #1 SMP Thu Nov 25 18:43:34 UTC 2010 i686 GNU/Linux

Gnu C                  4.4.6-11)
Gnu make               3.81
binutils               Binutils
util-linux             2.17.2
mount                  support
module-init-tools      3.12
e2fsprogs              1.41.12
reiserfsprogs          3.6.21
xfsprogs               3.1.4
Linux C Library        > libc.2.13
Dynamic linker (ldd)   2.13
Procps                 3.2.8
Net-tools              1.60
Kbd                    1.15.2
Sh-utils               8.5
wireless-tools         30
Modules Loaded         usb_storage vboxnetadp vboxnetflt vboxdrv
parport_pc ppdev lp parport sco bnep rfcomm l2cap crc16 bluetooth
rfkill nfs lockd fscache nfs_acl auth_rpcgss sunrpc uinput fuse ext3
jbd mbcache loop snd_hda_codec_intelhdmi snd_hda_codec_realtek
snd_hda_intel snd_hda_codec uvcvideo snd_usb_audio videodev
snd_pcm_oss snd_mixer_oss snd_usb_lib v4l1_compat snd_pcm snd_hwdep
snd_seq_midi pl2303 snd_rawmidi usbserial snd_seq_midi_event i915
snd_seq drm_kms_helper drm snd_timer i2c_algo_bit snd_seq_device
i2c_core snd wmi button soundcore snd_page_alloc evdev psmouse pcspkr
serio_raw processor video output reiserfs usbhid hid sd_mod crc_t10dif
ehci_hcd ahci libata r8169 mii scsi_mod thermal thermal_sys usbcore
nls_base e1000e

[7.2.] Processor information (from /proc/cpuinfo):

1 Core router:

system type             : 96362ADVNgr
processor               : 0
cpu model               : Broadcom4350 V7.0
BogoMIPS                : 398.33
wait instruction        : yes
microsecond timers      : yes
tlb_entries             : 32
extra interrupt vector  : no
hardware watchpoint     : no
ASEs implemented        :
VCED exceptions         : not available
VCEI exceptions         : not available

2 Core PC:

processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 37
model name      : Intel(R) Core(TM) i5 CPU         650  @ 3.20GHz
stepping        : 2
cpu MHz         : 3199.968
cache size      : 4096 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2
apicid          : 0
initial apicid  : 0
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 11
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx
rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3
cx16 xtpr pdcm sse4_1 sse4_2 popcnt aes lahf_lm ida arat tpr_shadow
vnmi flexpriority ept vpid
bogomips        : 6399.93
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 37
model name      : Intel(R) Core(TM) i5 CPU         650  @ 3.20GHz
stepping        : 2
cpu MHz         : 3199.968
cache size      : 4096 KB
physical id     : 0
siblings        : 2
core id         : 2
cpu cores       : 2
apicid          : 4
initial apicid  : 4
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 11
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx
rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3
cx16 xtpr pdcm sse4_1 sse4_2 popcnt aes lahf_lm ida arat tpr_shadow
vnmi flexpriority ept vpid
bogomips        : 6399.78
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

[7.3.] Module information (from /proc/modules):

2 Core PC

usb_storage 30541 0 - Live 0xfbfca000
vboxnetadp 5591 0 - Live 0xf7fa5000
vboxnetflt 15404 0 - Live 0xf7f7c000
vboxdrv 151314 2 vboxnetadp,vboxnetflt, Live 0xf7f2e000
parport_pc 15799 0 - Live 0xf7eb7000
ppdev 4058 0 - Live 0xf7ea6000
lp 5570 0 - Live 0xf7e9a000
parport 22554 3 parport_pc,ppdev,lp, Live 0xf7e87000
sco 5857 2 - Live 0xf7e72000
bnep 7444 2 - Live 0xf7e63000
rfcomm 25171 0 - Live 0xf7e4e000
l2cap 21705 6 bnep,rfcomm, Live 0xf7e29000
crc16 1027 1 l2cap, Live 0xf7e15000
bluetooth 36319 6 sco,bnep,rfcomm,l2cap, Live 0xf7dec000
rfkill 10264 2 bluetooth, Live 0xf7dc5000
nfs 206978 1 - Live 0xf7d78000
lockd 49437 1 nfs, Live 0xf7d13000
fscache 24662 1 nfs, Live 0xf7ced000
nfs_acl 1695 1 nfs, Live 0xf7cd7000
auth_rpcgss 25268 1 nfs, Live 0xf7cc5000
sunrpc 134748 8 nfs,lockd,nfs_acl,auth_rpcgss, Live 0xf7c49000
uinput 4796 1 - Live 0xf9a90000
fuse 43829 1 - Live 0xf9a77000
ext3 94204 1 - Live 0xf9a39000
jbd 32169 1 ext3, Live 0xf9a03000
mbcache 3762 1 ext3, Live 0xf99ec000
loop 9765 0 - Live 0xf99cd000
snd_hda_codec_intelhdmi 9027 1 - Live 0xf979c000
snd_hda_codec_realtek 163194 1 - Live 0xf9767000
snd_hda_intel 16787 2 - Live 0xf970d000
snd_hda_codec 46002 3
snd_hda_codec_intelhdmi,snd_hda_codec_realtek,snd_hda_intel, Live
0xf96ea000
uvcvideo 45342 0 - Live 0xf96c0000
snd_usb_audio 50670 0 - Live 0xf9695000
videodev 25545 1 uvcvideo, Live 0xf966c000
snd_pcm_oss 28671 0 - Live 0xf9652000
snd_mixer_oss 10461 1 snd_pcm_oss, Live 0xf963d000
snd_usb_lib 11156 1 snd_usb_audio, Live 0xf8f71000
v4l1_compat 10250 2 uvcvideo,videodev, Live 0xf8f5b000
snd_pcm 47226 4 snd_hda_intel,snd_hda_codec,snd_usb_audio,snd_pcm_oss,
Live 0xf8f3b000
snd_hwdep 4054 2 snd_hda_codec,snd_usb_audio, Live 0xf8f1e000
snd_seq_midi 3576 0 - Live 0xf8afd000
pl2303 11624 1 - Live 0xf8f0b000
snd_rawmidi 12513 2 snd_usb_lib,snd_seq_midi, Live 0xf8af2000
usbserial 21847 3 pl2303, Live 0xf8ab5000
snd_seq_midi_event 3684 1 snd_seq_midi, Live 0xf8aa1000
i915 222064 2 - Live 0xf884c000
snd_seq 35463 2 snd_seq_midi,snd_seq_midi_event, Live 0xf87eb000
drm_kms_helper 18301 1 i915, Live 0xf87ce000
drm 112088 3 i915,drm_kms_helper, Live 0xf8796000
snd_timer 12258 2 snd_pcm,snd_seq, Live 0xf875c000
i2c_algo_bit 3497 1 i915, Live 0xf874d000
snd_seq_device 3673 3 snd_seq_midi,snd_rawmidi,snd_seq, Live 0xf8743000
i2c_core 12696 5 videodev,i915,drm_kms_helper,drm,i2c_algo_bit, Live 0xf8733000
snd 34375 17 snd_hda_codec_intelhdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_usb_audio,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_hwdep,snd_rawmidi,snd_seq,snd_timer,snd_seq_device,
Live 0xf8716000
wmi 3575 0 - Live 0xf86fd000
button 3598 1 i915, Live 0xf86ed000
soundcore 3450 1 snd, Live 0xf86e1000
snd_page_alloc 5045 2 snd_hda_intel,snd_pcm, Live 0xf86d5000
evdev 5609 15 - Live 0xf86c8000
psmouse 44657 0 - Live 0xf86b0000
pcspkr 1207 0 - Live 0xf8697000
serio_raw 2916 0 - Live 0xf8688000
processor 26327 2 - Live 0xf85fa000
video 14605 1 i915, Live 0xf85df000
output 1204 1 video, Live 0xf85cf000
reiserfs 176190 1 - Live 0xf84d1000
usbhid 28008 0 - Live 0xf8449000
hid 50845 1 usbhid, Live 0xf8427000
sd_mod 25969 4 - Live 0xf8404000
crc_t10dif 1012 1 sd_mod, Live 0xf83f0000
ehci_hcd 27851 0 - Live 0xf83b8000
ahci 27270 3 - Live 0xf8391000
libata 115745 1 ahci, Live 0xf8352000
r8169 24860 0 - Live 0xf830f000
mii 2714 1 r8169, Live 0xf7ffe000
scsi_mod 101421 3 usb_storage,sd_mod,libata, Live 0xf824c000
thermal 9206 0 - Live 0xf8213000
thermal_sys 9378 3 processor,video,thermal, Live 0xf8202000
usbcore 98453 9
usb_storage,uvcvideo,snd_usb_audio,snd_usb_lib,pl2303,usbserial,usbhid,ehci_hcd,
Live 0xf7fc9000
nls_base 4541 1 usbcore, Live 0xf7c79000
e1000e 97725 0 - Live 0xf7f82000

[7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)n

0000-001f : dma1
0020-0021 : pic1
0040-0043 : timer0
0050-0053 : timer1
0060-0060 : keyboard
0064-0064 : keyboard
0070-0071 : rtc0
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu
03c0-03df : vesafb
0400-041f : pnp 00:0b
0420-043f : pnp 00:0b
0440-045f : pnp 00:0b
0460-047f : pnp 00:0b
 0460-0461 : ACPI PM1b_CNT_BLK
0480-048f : pnp 00:0b
04d0-04d1 : pnp 00:0a
0cb0-0cbf : pnp 00:0a
0cf8-0cff : PCI conf1
1000-1fff : PCI Bus 0000:30
 1100-11ff : 0000:30:00.0
   1100-11ff : r8169
2000-2fff : PCI Bus 0000:24
 2100-21ff : 0000:24:00.0
   2100-21ff : r8169
3100-311f : 0000:00:19.0
3120-313f : 0000:00:1f.2
 3120-313f : ahci
3170-3177 : 0000:00:02.0
3188-318f : 0000:00:16.3
 3188-318f : serial
3190-3197 : 0000:00:1f.2
 3190-3197 : ahci
3198-319f : 0000:00:1f.2
 3198-319f : ahci
31a8-31ab : 0000:00:1f.2
 31a8-31ab : ahci
31ac-31af : 0000:00:1f.2
 31ac-31af : ahci
4000-4fff : PCI Bus 0000:18
f800-f81f : pnp 00:0b
 f800-f803 : ACPI PM1a_EVT_BLK
 f804-f805 : ACPI PM1a_CNT_BLK
 f808-f80b : ACPI PM_TMR
 f810-f815 : ACPI CPU throttle
f820-f83f : pnp 00:0b
 f820-f82f : ACPI GPE0_BLK
f840-f85f : pnp 00:0b
f860-f87f : pnp 00:0b
fa00-fa3f : pnp 00:0b
fc00-fc7f : pnp 00:0b
fc80-fcff : pnp 00:0b
fe00-fe7f : pnp 00:0b
fe80-feff : pnp 00:0b

[7.5.] PCI information ('lspci -vvv' as root)
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)
        Subsystem: Hewlett-Packard Company Device 170b
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort+ >SERR- <PERR- INTx-
        Latency: 0
        Capabilities: [e0] Vendor Specific Information: Len=0c <?>
        Kernel driver in use: agpgart-intel

00:02.0 VGA compatible controller: Intel Corporation Core Processor
Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller])
        Subsystem: Hewlett-Packard Company Device 170b
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 36
        Region 0: Memory at f0000000 (64-bit, non-prefetchable) [size=4M]
        Region 2: Memory at e0000000 (64-bit, prefetchable) [size=256M]
        Region 4: I/O ports at 3170 [size=8]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
                Address: fee0300c  Data: 41d9
        Capabilities: [d0] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [a4] PCI Advanced Features
                AFCap: TP+ FLR+
                AFCtrl: FLR-
                AFStatus: TP-
        Kernel driver in use: i915

00:16.0 Communication controller: Intel Corporation 5 Series/3400
Series Chipset HECI Controller (rev 06)
        Subsystem: Hewlett-Packard Company Device 170b
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 5
        Region 0: Memory at f042a000 (64-bit, non-prefetchable) [size=16]
        Capabilities: [50] Power Management version 3
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [8c] MSI: Enable- Count=1/1 Maskable- 64bit+
                Address: 0000000000000000  Data: 0000

00:16.3 Serial controller: Intel Corporation 5 Series/3400 Series
Chipset KT Controller (rev 06) (prog-if 02 [16550])
        Subsystem: Hewlett-Packard Company Device 170b
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin B routed to IRQ 17
        Region 0: I/O ports at 3188 [size=8]
        Region 1: Memory at f0424000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [c8] Power Management version 3
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
                Address: 0000000000000000  Data: 0000
        Kernel driver in use: serial

00:19.0 Ethernet controller: Intel Corporation 82578DM Gigabit Network
Connection (rev 05)
        Subsystem: Hewlett-Packard Company Device 170b
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin B routed to IRQ 35
        Region 0: Memory at f0400000 (32-bit, non-prefetchable) [size=128K]
        Region 1: Memory at f0425000 (32-bit, non-prefetchable) [size=4K]
        Region 2: I/O ports at 3100 [size=32]
        Capabilities: [c8] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
        Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
                Address: 00000000fee0300c  Data: 4142
        Capabilities: [e0] PCI Advanced Features
                AFCap: TP+ FLR+
                AFCtrl: FLR-
                AFStatus: TP-
        Kernel driver in use: e1000e

00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset
USB2 Enhanced Host Controller (rev 05) (prog-if 20 [EHCI])
        Subsystem: Hewlett-Packard Company Device 170b
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 20
        Region 0: Memory at f0427000 (32-bit, non-prefetchable) [size=1K]
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [58] Debug port: BAR=1 offset=00a0
        Capabilities: [98] PCI Advanced Features
                AFCap: TP+ FLR+
                AFCtrl: FLR-
                AFStatus: TP-
        Kernel driver in use: ehci_hcd

00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset
High Definition Audio (rev 05)
        Subsystem: Hewlett-Packard Company Device 170b
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 21
        Region 0: Memory at f0420000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+
                Address: 0000000000000000  Data: 0000
        Capabilities: [70] Express (v1) Root Complex Integrated Endpoint, MSI 00
                DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
<64ns, L1 <1us
                        ExtTag- RBE- FLReset+
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
                        RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
                        MaxPayload 128 bytes, MaxReadReq 128 bytes
                DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq-
AuxPwr+ TransPend-
                LnkCap: Port #0, Speed unknown, Width x0, ASPM
unknown, Latency L0 <64ns, L1 <1us
                        ClockPM- Surprise- LLActRep- BwNot-
                LnkCtl: ASPM Disabled; Disabled- Retrain- CommClk-
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed unknown, Width x0, TrErr- Train-
SlotClk- DLActive- BWMgmt- ABWMgmt-
        Capabilities: [100 v1] Virtual Channel
                Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
                Arb:    Fixed- WRR32- WRR64- WRR128-
                Ctrl:   ArbSelect=Fixed
                Status: InProgress-
                VC0:    Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
                        Arb:    Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
                        Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
                        Status: NegoPending- InProgress-
                VC1:    Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
                        Arb:    Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
                        Ctrl:   Enable- ID=2 ArbSelect=Fixed TC/VC=04
                        Status: NegoPending- InProgress-
        Capabilities: [130 v1] Root Complex Link
                Desc:   PortNumber=0f ComponentID=00 EltType=Config
                Link0:  Desc:   TargetPort=00 TargetComponent=00
AssocRCRB- LinkType=MemMapped LinkValid+
                        Addr:   00000000fed1c000
        Kernel driver in use: HDA Intel

00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 1 (rev 05) (prog-if 00 [Normal decode])
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Bus: primary=00, secondary=18, subordinate=18, sec-latency=0
        I/O behind bridge: 00004000-00004fff
        Memory behind bridge: f0700000-f08fffff
        Prefetchable memory behind bridge: 00000000f0900000-00000000f0afffff
        Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- <SERR- <PERR-
        BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
                PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
        Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
                DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
<64ns, L1 <1us
                        ExtTag- RBE+ FLReset-
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
                        RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
                        MaxPayload 128 bytes, MaxReadReq 128 bytes
                DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq-
AuxPwr+ TransPend-
                LnkCap: Port #1, Speed 2.5GT/s, Width x4, ASPM L0s L1,
Latency L0 <1us, L1 <4us
                        ClockPM- Surprise- LLActRep+ BwNot-
                LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train-
SlotClk+ DLActive- BWMgmt- ABWMgmt-
                SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd-
HotPlug+ Surprise+
                        Slot #0, PowerLimit 25.000W; Interlock- NoCompl+
                SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet-
CmdCplt- HPIrq- LinkChg-
                        Control: AttnInd Unknown, PwrInd Unknown,
Power- Interlock-
                SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt-
PresDet- Interlock-
                        Changed: MRL- PresDet- LinkState-
                RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal-
PMEIntEna- CRSVisible-
                RootCap: CRSVisible-
                RootSta: PME ReqID 0000, PMEStatus- PMEPending-
                DevCap2: Completion Timeout: Range BC, TimeoutDis+ ARIFwd-
                DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- ARIFwd-
                LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance-
SpeedDis-, Selectable De-emphasis: -6dB
                         Transmit Margin: Normal Operating Range,
EnterModifiedCompliance- ComplianceSOS-
                         Compliance De-emphasis: -6dB
                LnkSta2: Current De-emphasis Level: -6dB
        Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
                Address: fee0300c  Data: 4181
        Capabilities: [90] Subsystem: Hewlett-Packard Company Device 170b
        Capabilities: [a0] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Kernel driver in use: pcieport

00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 5 (rev 05) (prog-if 00 [Normal decode])
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Bus: primary=00, secondary=24, subordinate=24, sec-latency=0
        I/O behind bridge: 00002000-00002fff
        Memory behind bridge: f0600000-f06fffff
        Prefetchable memory behind bridge: 00000000f0b00000-00000000f0cfffff
        Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- <SERR- <PERR-
        BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
                PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
        Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
                DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
<64ns, L1 <1us
                        ExtTag- RBE+ FLReset-
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
                        RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
                        MaxPayload 128 bytes, MaxReadReq 128 bytes
                DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq-
AuxPwr+ TransPend-
                LnkCap: Port #5, Speed 2.5GT/s, Width x1, ASPM L0s L1,
Latency L0 <256ns, L1 <4us
                        ClockPM- Surprise- LLActRep+ BwNot-
                LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train-
SlotClk+ DLActive+ BWMgmt- ABWMgmt-
                SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd-
HotPlug+ Surprise+
                        Slot #0, PowerLimit 10.000W; Interlock- NoCompl+
                SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet-
CmdCplt- HPIrq- LinkChg-
                        Control: AttnInd Unknown, PwrInd Unknown,
Power- Interlock-
                SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt-
PresDet+ Interlock-
                        Changed: MRL- PresDet+ LinkState+
                RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal-
PMEIntEna- CRSVisible-
                RootCap: CRSVisible-
                RootSta: PME ReqID 0000, PMEStatus- PMEPending-
                DevCap2: Completion Timeout: Range BC, TimeoutDis+ ARIFwd-
                DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- ARIFwd-
                LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance-
SpeedDis-, Selectable De-emphasis: -6dB
                         Transmit Margin: Normal Operating Range,
EnterModifiedCompliance- ComplianceSOS-
                         Compliance De-emphasis: -6dB
                LnkSta2: Current De-emphasis Level: -6dB
        Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
                Address: fee0300c  Data: 4189
        Capabilities: [90] Subsystem: Hewlett-Packard Company Device 170b
        Capabilities: [a0] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Kernel driver in use: pcieport

00:1c.6 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 7 (rev 05) (prog-if 00 [Normal decode])
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Bus: primary=00, secondary=30, subordinate=30, sec-latency=0
        I/O behind bridge: 00001000-00001fff
        Memory behind bridge: f0500000-f05fffff
        Prefetchable memory behind bridge: 00000000f0d00000-00000000f0efffff
        Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- <SERR- <PERR-
        BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
                PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
        Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
                DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
<64ns, L1 <1us
                        ExtTag- RBE+ FLReset-
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
                        RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
                        MaxPayload 128 bytes, MaxReadReq 128 bytes
                DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq-
AuxPwr+ TransPend-
                LnkCap: Port #7, Speed 2.5GT/s, Width x1, ASPM L0s L1,
Latency L0 <256ns, L1 <4us
                        ClockPM- Surprise- LLActRep+ BwNot-
                LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train-
SlotClk+ DLActive+ BWMgmt- ABWMgmt-
                SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd-
HotPlug+ Surprise+
                        Slot #0, PowerLimit 10.000W; Interlock- NoCompl+
                SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet-
CmdCplt- HPIrq- LinkChg-
                        Control: AttnInd Unknown, PwrInd Unknown,
Power- Interlock-
                SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt-
PresDet+ Interlock-
                        Changed: MRL- PresDet+ LinkState+
                RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal-
PMEIntEna- CRSVisible-
                RootCap: CRSVisible-
                RootSta: PME ReqID 0000, PMEStatus- PMEPending-
                DevCap2: Completion Timeout: Range BC, TimeoutDis+ ARIFwd-
                DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- ARIFwd-
                LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance-
SpeedDis-, Selectable De-emphasis: -6dB
                         Transmit Margin: Normal Operating Range,
EnterModifiedCompliance- ComplianceSOS-
                         Compliance De-emphasis: -6dB
                LnkSta2: Current De-emphasis Level: -6dB
        Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
                Address: fee0300c  Data: 4191
        Capabilities: [90] Subsystem: Hewlett-Packard Company Device 170b
        Capabilities: [a0] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Kernel driver in use: pcieport

00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset
USB2 Enhanced Host Controller (rev 05) (prog-if 20 [EHCI])
        Subsystem: Hewlett-Packard Company Device 170b
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 20
        Region 0: Memory at f0428000 (32-bit, non-prefetchable) [size=1K]
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [58] Debug port: BAR=1 offset=00a0
        Capabilities: [98] PCI Advanced Features
                AFCap: TP+ FLR+
                AFCtrl: FLR-
                AFStatus: TP-
        Kernel driver in use: ehci_hcd

00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a5)
(prog-if 01 [Subtractive decode])
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Bus: primary=00, secondary=10, subordinate=10, sec-latency=32
        I/O behind bridge: 0000f000-00000fff
        Memory behind bridge: fff00000-000fffff
        Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff
        Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort+ <SERR- <PERR-
        BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
                PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
        Capabilities: [50] Subsystem: Hewlett-Packard Company Device 170b

00:1f.0 ISA bridge: Intel Corporation 3400 Series Chipset LPC
Interface Controller (rev 05)
        Subsystem: Hewlett-Packard Company Device 170b
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Capabilities: [e0] Vendor Specific Information: Len=10 <?>

00:1f.2 RAID bus controller: Intel Corporation 82801 SATA RAID
Controller (rev 05)
        Subsystem: Hewlett-Packard Company Device 170b
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin B routed to IRQ 34
        Region 0: I/O ports at 3190 [size=8]
        Region 1: I/O ports at 31a8 [size=4]
        Region 2: I/O ports at 3198 [size=8]
        Region 3: I/O ports at 31ac [size=4]
        Region 4: I/O ports at 3120 [size=32]
        Region 5: Memory at f0426000 (32-bit, non-prefetchable) [size=2K]
        Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
                Address: fee0300c  Data: 41c1
        Capabilities: [70] Power Management version 3
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot+,D3cold-)
                Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [a8] SATA HBA v1.0 BAR4 Offset=00000004
        Capabilities: [b0] PCI Advanced Features
                AFCap: TP+ FLR+
                AFCtrl: FLR-
                AFStatus: TP-
        Kernel driver in use: ahci

24:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
        Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI
Express Gigabit Ethernet controller
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 32
        Region 0: I/O ports at 2100 [size=256]
        Region 2: Memory at f0600000 (64-bit, non-prefetchable) [size=4K]
        [virtual] Expansion ROM at f0b00000 [disabled] [size=128K]
        Capabilities: [40] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
PME(D0-,D1+,D2+,D3hot+,D3cold+)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [48] Vital Product Data
                Unknown small resource type 00, will not decode more.
        Capabilities: [50] MSI: Enable+ Count=1/2 Maskable- 64bit+
                Address: 00000000fee0300c  Data: 41a9
        Capabilities: [60] Express (v1) Endpoint, MSI 00
                DevCap: MaxPayload 1024 bytes, PhantFunc 0, Latency
L0s <1us, L1 unlimited
                        ExtTag+ AttnBtn+ AttnInd+ PwrInd+ RBE- FLReset-
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal+
Unsupported-
                        RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
                        MaxPayload 128 bytes, MaxReadReq 4096 bytes
                DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq-
AuxPwr+ TransPend-
                LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s,
Latency L0 unlimited, L1 unlimited
                        ClockPM- Surprise- LLActRep- BwNot-
                LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train-
SlotClk+ DLActive- BWMgmt- ABWMgmt-
        Capabilities: [84] Vendor Specific Information: Len=4c <?>
        Capabilities: [100 v1] Advanced Error Reporting
                UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt-
UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt-
UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt-
UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
                CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
                CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
                AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
        Capabilities: [12c v1] Virtual Channel
                Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
                Arb:    Fixed- WRR32- WRR64- WRR128-
                Ctrl:   ArbSelect=Fixed
                Status: InProgress-
                VC0:    Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
                        Arb:    Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
                        Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=01
                        Status: NegoPending- InProgress-
        Capabilities: [148 v1] Device Serial Number 6f-21-00-00-10-ec-81-68
        Capabilities: [154 v1] Power Budgeting <?>
        Kernel driver in use: r8169

30:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
        Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI
Express Gigabit Ethernet controller
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 33
        Region 0: I/O ports at 1100 [size=256]
        Region 2: Memory at f0500000 (64-bit, non-prefetchable) [size=4K]
        [virtual] Expansion ROM at f0d00000 [disabled] [size=128K]
        Capabilities: [40] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
PME(D0-,D1+,D2+,D3hot+,D3cold+)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [48] Vital Product Data
                Unknown small resource type 00, will not decode more.
        Capabilities: [50] MSI: Enable+ Count=1/2 Maskable- 64bit+
                Address: 00000000fee0300c  Data: 41b9
        Capabilities: [60] Express (v1) Endpoint, MSI 00
                DevCap: MaxPayload 1024 bytes, PhantFunc 0, Latency
L0s <1us, L1 unlimited
                        ExtTag+ AttnBtn+ AttnInd+ PwrInd+ RBE- FLReset-
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal+
Unsupported-
                        RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
                        MaxPayload 128 bytes, MaxReadReq 4096 bytes
                DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq-
AuxPwr+ TransPend-
                LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s,
Latency L0 unlimited, L1 unlimited
                        ClockPM- Surprise- LLActRep- BwNot-
                LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train-
SlotClk+ DLActive- BWMgmt- ABWMgmt-
        Capabilities: [84] Vendor Specific Information: Len=4c <?>
        Capabilities: [100 v1] Advanced Error Reporting
                UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt-
UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt-
UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt-
UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
                CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
                CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
                AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
        Capabilities: [12c v1] Virtual Channel
                Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
                Arb:    Fixed- WRR32- WRR64- WRR128-
                Ctrl:   ArbSelect=Fixed
                Status: InProgress-
                VC0:    Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
                        Arb:    Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
                        Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=01
                        Status: NegoPending- InProgress-
        Capabilities: [148 v1] Device Serial Number 29-22-00-00-10-ec-81-68
        Capabilities: [154 v1] Power Budgeting <?>
        Kernel driver in use: r8169

[7.6.] SCSI information (from /proc/scsi/scsi)

no such file
[7.7.] Other information that might be relevant to the problem

It seems that kernel URB mechanism took a lot of CPU performance as
iowait and in spin-locks.
As you see above the problem exist for new kernel too. Problem was
found on a router when I tried to copy data from connected USB flash
via Samba.
For testing I used cat /dev/sda > /dev/null to avoid influence from file system.
My suggestion is not decrease CPU Load but free a piece of CPU for user space.
This fix is important for routers and PC which has only one core and
USB handling is not main task.

[X.] Other notes, patches, fixes, workarounds:

Fix which helps to free CPU for user space if it is needed was made:

drivers/usb/core/message.c
void usb_sg_wait (struct usb_sg_request *io)
{
.......
for (i = 0; i < entries && !io->status; i++) {
.....
switch (retval) {
.....
case 0:
cpu_relax();
                yield (); // FIX
break;
....
It helps to decrease USB speed if user space software needs CPU but in
this case USB speed in idle CPU (no user space software is executed)
is decreased only less than 5%.

Copying the file via Samba from USB connected to the router router
(graph from Slurm)
-----------------------------------
Without fix
-----------------------------------
USB speed:
        copy  USB data                   executing a big user space
software       copy USB data
           start                                      start
                                    end
            |                                             |
                                         |
           V             x                             V
                                     V
            xxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx x xxxxxx
       x
            xxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxx
       x
           xxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxx
       x
           xxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
           xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
           xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
           xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
           xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
           xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

CPU is overloaded by 100% kernel usage. User space software is working
as turtle, cannot start properly.
USB speed is not decreased when user space software is executed (graph
above). User is


------------------------------------
With fix
------------------------------------
USB speed:
          executing user space sw                       copy USB data
        start
  end                                        end
     | d                              |                     |
     V                                V                     V
   x
xxxx                                   xxxxxxx xx  xxxxxx                    x
xxxx                                   xxxxxxx xxx xxxxxx                    x
xxxx                                   xxxxxxx xxx xxxxxxx                   x
xxxx                                   xxxxxxx xxx xxxxxxx x
xxxx                                   xxxxxxxxxxxxxxxxxxxxxx
xxxx                                   xxxxxxxxxxxxxxxxxxxxxx
xxxx                  x                xxxxxxxxxxxxxxxxxxxxxx
xxxx                  x          xx   xxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxx x   x  x  xxx xx x x  xxxxx xxxxxxxxxxxxxxxxxxxxxxxxx    xxx     xx

As we see, CPU is freed for user space and USB speed is decreased
(graph above) if it is needed.
So, user space is working as without any USB coping. User is  CPU is
divided between user space and kernel.

Bug

[Guido Telscher]

Bug bei cpufreq-info:

analysiere CPU 0:
   kein oder nicht bestimmbarer cpufreq-Treiber aktiv
   Maximale Dauer eines Taktfrequenzwechsels: 0.00 ms.
analysiere CPU 1:
   kein oder nicht bestimmbarer cpufreq-Treiber aktiv
   Maximale Dauer eines Taktfrequenzwechsels: 0.00 ms.

Wie kann ich auf dem Thinkpad R60e die CPU steuern?

BUG

[Plamen Vasilev]

Hi,
I have D-LINK DWA-547 PCI card on my Gentoo based PC.
I'm using kernel 2.31.r8 with the latest drivers from the linux wireless site.

I have the following error from the kernel :

Nov 30 22:27:04 plamenvasilev kernel: [  493.171844] ------------[ cut here ]------------
Nov 30 22:27:04 plamenvasilev kernel: [  493.171952] WARNING: at /root/compat-wireless-2.6.31-rc7/net/mac80211/tx.c:1251 ieee80211_tx+0x5b/0x1ae [mac80211]()
Nov 30 22:27:04 plamenvasilev kernel: [  493.171960] Hardware name: Deskpro
Nov 30 22:27:04 plamenvasilev kernel: [  493.171965] Modules linked in: xt_state xt_TCPMSS xt_comment iptable_raw pppoe pppox ath9k mac80211 ath cfg80211
Nov 30 22:27:04 plamenvasilev kernel: [  493.171991] Pid: 0, comm: swapper Not tainted 2.6.31-gentoo-r6 #11
Nov 30 22:27:04 plamenvasilev kernel: [  493.171997] Call Trace:
Nov 30 22:27:04 plamenvasilev kernel: [  493.172026]  [<c102f339>] warn_slowpath_common+0x60/0x90
Nov 30 22:27:04 plamenvasilev kernel: [  493.172036]  [<c102f376>] warn_slowpath_null+0xd/0x10
Nov 30 22:27:04 plamenvasilev kernel: [  493.172069]  [<e0840765>] ieee80211_tx+0x5b/0x1ae [mac80211]
Nov 30 22:27:04 plamenvasilev kernel: [  493.172089]  [<c13c815b>] ? skb_release_data+0x8e/0x92
Nov 30 22:27:04 plamenvasilev kernel: [  493.172122]  [<e0840c3c>] ? ieee80211_skb_resize+0x72/0xa6 [mac80211]
Nov 30 22:27:04 plamenvasilev kernel: [  493.172155]  [<e08416a6>] ieee80211_master_start_xmit+0x334/0x362 [mac80211]
Nov 30 22:27:04 plamenvasilev kernel: [  493.172172]  [<c13cf0c2>] dev_hard_start_xmit+0x20e/0x2a1
Nov 30 22:27:04 plamenvasilev kernel: [  493.172196]  [<c13de226>] __qdisc_run+0xbf/0x19d
Nov 30 22:27:04 plamenvasilev kernel: [  493.172205]  [<c13cf496>] dev_queue_xmit+0x25b/0x350
Nov 30 22:27:04 plamenvasilev kernel: [  493.172237]  [<e0841359>] ieee80211_subif_start_xmit+0x6e9/0x702 [mac80211]
Nov 30 22:27:04 plamenvasilev kernel: [  493.172270]  [<e083f402>] ? __ieee80211_tx_prepare+0x2d4/0x311 [mac80211]
Nov 30 22:27:04 plamenvasilev kernel: [  493.172292]  [<c13c0000>] ? pci_fixup_nforce2+0x14/0x6f
Nov 30 22:27:04 plamenvasilev kernel: [  493.172313]  [<c1466dac>] ? packet_rcv_spkt+0xb9/0xc1
Nov 30 22:27:04 plamenvasilev kernel: [  493.172322]  [<c13cf0c2>] dev_hard_start_xmit+0x20e/0x2a1
Nov 30 22:27:04 plamenvasilev kernel: [  493.172331]  [<c13c71be>] ? skb_copy_bits+0x4b/0x18b
Nov 30 22:27:04 plamenvasilev kernel: [  493.172341]  [<c13de226>] __qdisc_run+0xbf/0x19d
Nov 30 22:27:04 plamenvasilev kernel: [  493.172350]  [<c13cf496>] dev_queue_xmit+0x25b/0x350
Nov 30 22:27:04 plamenvasilev kernel: [  493.172382]  [<e083c849>] ieee80211_deliver_skb+0xf9/0x101 [mac80211]
Nov 30 22:27:04 plamenvasilev kernel: [  493.172414]  [<e083dcac>] ieee80211_invoke_rx_handlers+0x145b/0x1b9e [mac80211]
Nov 30 22:27:04 plamenvasilev kernel: [  493.172425]  [<c13de24a>] ? __qdisc_run+0xe3/0x19d
Nov 30 22:27:04 plamenvasilev kernel: [  493.172457]  [<e0841359>] ? ieee80211_subif_start_xmit+0x6e9/0x702 [mac80211]
Nov 30 22:27:04 plamenvasilev kernel: [  493.172492]  [<e083e83c>] __ieee80211_rx_handle_packet+0x44d/0x45f [mac80211]
Nov 30 22:27:04 plamenvasilev kernel: [  493.172526]  [<e083ef83>] __ieee80211_rx+0x4b9/0x50a [mac80211]
Nov 30 22:27:04 plamenvasilev kernel: [  493.172544]  [<c149fdc3>] ? _spin_unlock_bh+0xd/0xf
Nov 30 22:27:04 plamenvasilev kernel: [  493.172613]  [<e08a0b05>] ath_rx_send_to_mac80211+0x6b/0x72 [ath9k]
Nov 30 22:27:04 plamenvasilev kernel: [  493.172640]  [<e08a11b6>] ath_rx_tasklet+0x628/0x670 [ath9k]
Nov 30 22:27:04 plamenvasilev kernel: [  493.172656]  [<c104a6c0>] ? clockevents_program_event+0xd4/0xe3
Nov 30 22:27:04 plamenvasilev kernel: [  493.172668]  [<c104b52e>] ? tick_dev_program_event+0x28/0x95
Nov 30 22:27:04 plamenvasilev kernel: [  493.172677]  [<c1049040>] ? clocksource_get_next+0x3c/0x43
Nov 30 22:27:04 plamenvasilev kernel: [  493.172703]  [<e089f9b8>] ath9k_tasklet+0x44/0x91 [ath9k]
Nov 30 22:27:04 plamenvasilev kernel: [  493.172713]  [<c10331b9>] tasklet_action+0x62/0x9f
Nov 30 22:27:04 plamenvasilev kernel: [  493.172725]  [<c1033f0e>] __do_softirq+0xa7/0x144
Nov 30 22:27:04 plamenvasilev kernel: [  493.172734]  [<c1033fd1>] do_softirq+0x26/0x2b
Nov 30 22:27:04 plamenvasilev kernel: [  493.172742]  [<c10340b6>] irq_exit+0x29/0x5c
Nov 30 22:27:04 plamenvasilev kernel: [  493.172756]  [<c1003f6f>] do_IRQ+0x80/0x96
Nov 30 22:27:04 plamenvasilev kernel: [  493.172766]  [<c10030a9>] common_interrupt+0x29/0x30
Nov 30 22:27:04 plamenvasilev kernel: [  493.172766]  [<c1008065>] ? default_idle+0x42/0x5f
Nov 30 22:27:04 plamenvasilev kernel: [  493.172766]  [<c1001d4c>] cpu_idle+0x44/0x60
Nov 30 22:27:04 plamenvasilev kernel: [  493.172766]  [<c1483f97>] rest_init+0x53/0x55
Nov 30 22:27:04 plamenvasilev kernel: [  493.172766]  [<c17407d7>] start_kernel+0x2b1/0x2b6
Nov 30 22:27:04 plamenvasilev kernel: [  493.172766]  [<c174006a>] i386_start_kernel+0x6a/0x6f
Nov 30 22:27:04 plamenvasilev kernel: [  493.172766] ---[ end trace a8b664535fdf6c28 ]--- 

After some time of using the wireless i get the following :

Nov 30 22:33:47 plamenvasilev hostapd: wlan0: STA 00:1f:df:0e:dd:eb MLME: MLME-AUTHENTICATE.indication(00:1f:df:0e:dd:eb, OPEN_SYSTEM)
Nov 30 22:33:47 plamenvasilev hostapd: wlan0: STA 00:1f:df:0e:dd:eb MLME: MLME-DELETEKEYS.request(00:1f:df:0e:dd:eb)
Nov 30 22:33:47 plamenvasilev hostapd: wlan0: STA 00:1f:df:0e:dd:eb IEEE 802.11: authentication OK (open system)
Nov 30 22:33:47 plamenvasilev hostapd: wlan0: STA 00:1f:df:0e:dd:eb MLME: MLME-AUTHENTICATE.indication(00:1f:df:0e:dd:eb, OPEN_SYSTEM)
Nov 30 22:33:47 plamenvasilev hostapd: wlan0: STA 00:1f:df:0e:dd:eb MLME: MLME-DELETEKEYS.request(00:1f:df:0e:dd:eb)
Nov 30 22:33:47 plamenvasilev hostapd: wlan0: STA 00:1f:df:0e:dd:eb IEEE 802.11: authenticated
Nov 30 22:33:47 plamenvasilev hostapd: wlan0: STA 00:1f:df:0e:dd:eb IEEE 802.11: authenticated
Nov 30 22:36:14 plamenvasilev hostapd: wlan0: WPA rekeying GTK
Nov 30 22:36:14 plamenvasilev hostapd: wlan0: STA 00:1e:52:83:3f:f2 WPA: sending 1/2 msg of Group Key Handshake
Nov 30 22:36:14 plamenvasilev hostapd: wlan0: STA 00:1e:52:83:3f:f2 WPA: received EAPOL-Key frame (2/2 Group)
Nov 30 22:36:14 plamenvasilev hostapd: wlan0: STA 00:1e:52:83:3f:f2 WPA: group key handshake completed (RSN)
Nov 30 22:36:48 plamenvasilev hostapd: wlan0: STA 00:1e:52:83:3f:f2 WPA: event 2 notification
Nov 30 22:36:48 plamenvasilev hostapd: wlan0: STA 00:1e:52:83:3f:f2 IEEE 802.1X: unauthorizing port
Nov 30 22:36:48 plamenvasilev hostapd: wlan0: STA 00:1e:52:83:3f:f2 IEEE 802.11: disassociated
Nov 30 22:36:48 plamenvasilev hostapd: wlan0: STA 00:1e:52:83:3f:f2 MLME: MLME-DISASSOCIATE.indication(00:1e:52:83:3f:f2, 8)
Nov 30 22:36:48 plamenvasilev hostapd: wlan0: STA 00:1e:52:83:3f:f2 MLME: MLME-DELETEKEYS.request(00:1e:52:83:3f:f2)
Nov 30 22:36:49 plamenvasilev hostapd: wlan0: STA 00:1e:52:83:3f:f2 IEEE 802.11: deauthenticated due to inactivity
Nov 30 22:36:49 plamenvasilev hostapd: wlan0: STA 00:1e:52:83:3f:f2 MLME: MLME-DEAUTHENTICATE.indication(00:1e:52:83:3f:f2, 2)
Nov 30 22:36:49 plamenvasilev hostapd: wlan0: STA 00:1e:52:83:3f:f2 MLME: MLME-DELETEKEYS.request(00:1e:52:83:3f:f2)

After that i have to restart hostapd service because i cannot connect any more.
Any ideas ?

Re: Bug

[Chris Mason]

On Fri, Jul 24, 2009 at 03:28:19PM -0500, Steven Pratt wrote:
> Still having issue on the non-raid system. not sure if there is anything  
> new in this that can help debug the problem.

Could you send along the full dmesg please?

-chris

Bug

[Steven Pratt]

Still having issue on the non-raid system. not sure if there is anything 
new in this that can help debug the problem.

Message from syslogd@ at Fri Jul 24 12:34:27 2009 ...
btrfs2 kernel: [ 4543.844556] ------------[ cut here ]------------
Message from syslogd@ at Fri Jul 24 12:34:27 2009 ...
btrfs2 kernel: [ 4543.844635] invalid opcode: 0000 [#1] SMP
Message from syslogd@ at Fri Jul 24 12:34:27 2009 ...
btrfs2 kernel: [ 4543.844635] last sysfs file: 
/sys/devices/pci0000:01/0000:01:01.1/irq
Message from syslogd@ at Fri Jul 24 12:34:28 2009 ...
btrfs2 kernel: [ 4543.844635] Stack:
Message from syslogd@ at Fri Jul 24 12:34:28 2009 ...
btrfs2 kernel: [ 4543.844635]  ffff88013b1c1000 ffff880099cc4760 
000000b221521bd0 ffffffffa036519a
Message from syslogd@ at Fri Jul 24 12:34:28 2009 ...
btrfs2 kernel: [ 4543.844635]  000000353b1c1000 ffff880024ddf440 
ffff8800bf8e3ac0 0000000000000001
Message from syslogd@ at Fri Jul 24 12:34:28 2009 ...
btrfs2 kernel: [ 4543.844635] Call Trace:
Message from syslogd@ at Fri Jul 24 12:34:28 2009 ...
btrfs2 kernel: [ 4543.844635]  [<ffffffffa036519a>] ? 
update_reserved_extents+0xa1/0xb8 [btrfs]
Message from syslogd@ at Fri Jul 24 12:34:28 2009 ...
btrfs2 kernel: [ 4543.844635]  [<ffffffffa036a56e>] 
run_one_delayed_ref+0x385/0x432 [btrfs]
Message from syslogd@ at Fri Jul 24 12:34:28 2009 ...
btrfs2 kernel: [ 4543.844635]  [<ffffffffa036b1f2>] 
run_clustered_refs+0x237/0x2b4 [btrfs]
Message from syslogd@ at Fri Jul 24 12:34:28 2009 ...
btrfs2 kernel: [ 4543.844635]  [<ffffffffa03a011d>] ? 
btrfs_find_ref_cluster+0xdc/0x115 [btrfs]
Message from syslogd@ at Fri Jul 24 12:34:28 2009 ...
btrfs2 kernel: [ 4543.844635]  [<ffffffffa036b31b>] 
btrfs_run_delayed_refs+0xac/0x195 [btrfs]
Message from syslogd@ at Fri Jul 24 12:34:28 2009 ...
btrfs2 kernel: [ 4543.844635]  [<ffffffffa0374b05>] 
__btrfs_end_transaction+0x59/0xfe [btrfs]
Message from syslogd@ at Fri Jul 24 12:34:28 2009 ...
btrfs2 kernel: [ 4543.844635]  [<ffffffffa0374bc5>] 
btrfs_end_transaction+0xb/0xd [btrfs]
Message from syslogd@ at Fri Jul 24 12:34:28 2009 ...
btrfs2 kernel: [ 4543.844635]  [<ffffffffa037a295>] 
btrfs_finish_ordered_io+0x224/0x24d [btrfs]
Message from syslogd@ at Fri Jul 24 12:34:28 2009 ...
btrfs2 kernel: [ 4543.844635]  [<ffffffffa037a2ce>] 
btrfs_writepage_end_io_hook+0x10/0x12 [btrfs]
Message from syslogd@ at Fri Jul 24 12:34:28 2009 ...
btrfs2 kernel: [ 4543.844635]  [<ffffffffa038d6a9>] 
end_bio_extent_writepage+0xa3/0x18f [btrfs]
Message from syslogd@ at Fri Jul 24 12:34:28 2009 ...
btrfs2 kernel: [ 4543.844635]  [<ffffffff80242782>] ? 
del_timer_sync+0x14/0x20
Message from syslogd@ at Fri Jul 24 12:34:28 2009 ...
btrfs2 kernel: [ 4543.844635]  [<ffffffff802cbc6a>] bio_endio+0x26/0x28
Message from syslogd@ at Fri Jul 24 12:34:28 2009 ...
btrfs2 kernel: [ 4543.844635]  [<ffffffffa0371799>] 
end_workqueue_fn+0x111/0x11e [btrfs]
Message from syslogd@ at Fri Jul 24 12:34:28 2009 ...
btrfs2 kernel: [ 4543.844635]  [<ffffffffa0395274>] 
worker_loop+0x67/0x1ef [btrfs]
Message from syslogd@ at Fri Jul 24 12:34:28 2009 ...
btrfs2 kernel: [ 4543.844635]  [<ffffffffa039520d>] ? 
worker_loop+0x0/0x1ef [btrfs]
Message from syslogd@ at Fri Jul 24 12:34:28 2009 ...
btrfs2 kernel: [ 4543.844635]  [<ffffffff8024c33c>] kthread+0x56/0x86
Message from syslogd@ at Fri Jul 24 12:34:28 2009 ...
btrfs2 kernel: [ 4543.844635]  [<ffffffff8020c9fa>] child_rip+0xa/0x20
Message from syslogd@ at Fri Jul 24 12:34:28 2009 ...
btrfs2 kernel: [ 4543.844635]  [<ffffffff8024c2e6>] ? kthread+0x0/0x86
Message from syslogd@ at Fri Jul 24 12:34:28 2009 ...
btrfs2 kernel: [ 4543.844635]  [<ffffffff8020c9f0>] ? child_rip+0x0/0x20
Message from syslogd@ at Fri Jul 24 12:34:28 2009 ...
btrfs2 kernel: [ 4543.844635] Code: 08 4c 8d 45 d4 41 8d 44 24 18 48 8b 
73 20 48 8b 4d 18 41 b9 01 00 00 00 48 8b 7d b8 4c 89 ea 89 45 d4 e8 8a 
e2 ff ff 85 c0 74 04 <0f> 0b eb fe 49 63 75 40 4d 8b 65 00 49 83 cf 01 
4c 89 e7 48 6b


After this, we seem to get stuck with all threads spinning in 
btrfs_endio_write, 100% cpu witn no IO going on.  dmesg full of softlockups:


Jul 24 15:25:18 btrfs2 kernel: [14789.720395] BUG: soft lockup - CPU#1 
stuck for 61s! [btrfs-endio-wri:16195]
Jul 24 15:25:18 btrfs2 kernel: [14789.720395] Modules linked in: btrfs 
zlib_deflate oprofile autofs4 nfs lockd nfs_acl auth_rpcgss sunrpc dm_mu
ltipath video output sbs sbshc battery ac parport_pc lp parport sg 
joydev serio_raw acpi_memhotplug rtc_cmos rtc_core rtc_lib button tg3 libphy
 i2c_piix4 i2c_core pcspkr dm_snapshot dm_zero dm_mirror dm_region_hash 
dm_log dm_mod lpfc scsi_transport_fc aic94xx libsas libata scsi_transpo
rt_sas sd_mod scsi_mod ext3 jbd uhci_hcd ohci_hcd ehci_hcd [last 
unloaded: microcode]
Jul 24 15:25:18 btrfs2 kernel: [14789.720395] CPU 1:
Jul 24 15:25:18 btrfs2 kernel: [14789.720395] Modules linked in: btrfs 
zlib_deflate oprofile autofs4 nfs lockd nfs_acl auth_rpcgss sunrpc dm_mu
ltipath video output sbs sbshc battery ac parport_pc lp parport sg 
joydev serio_raw acpi_memhotplug rtc_cmos rtc_core rtc_lib button tg3 libphy
 i2c_piix4 i2c_core pcspkr dm_snapshot dm_zero dm_mirror dm_region_hash 
dm_log dm_mod lpfc scsi_transport_fc aic94xx libsas libata scsi_transpo
rt_sas sd_mod scsi_mod ext3 jbd uhci_hcd ohci_hcd ehci_hcd [last 
unloaded: microcode]
Jul 24 15:25:18 btrfs2 kernel: [14789.720395] Pid: 16195, comm: 
btrfs-endio-wri Tainted: G      D    2.6.30-autokern1 #1 IBM 
x3950-[88726RU]-
Jul 24 15:25:18 btrfs2 kernel: [14789.720395] RIP: 
0010:[<ffffffff804cdd1d>]  [<ffffffff804cdd1d>] _spin_lock+0x14/0x1a
Jul 24 15:25:18 btrfs2 kernel: [14789.720395] RSP: 
0018:ffff88013ad69a70  EFLAGS: 00000293
Jul 24 15:25:18 btrfs2 kernel: [14789.720395] RAX: 0000000000009d98 RBX: 
ffff88013ad69a70 RCX: 0000000000000000
Jul 24 15:25:18 btrfs2 kernel: [14789.720395] RDX: 0000000000000000 RSI: 
ffff88013b40c000 RDI: ffff8801285fd6b0
Jul 24 15:25:18 btrfs2 kernel: [14789.720395] RBP: ffffffff8020c50e R08: 
000000000000004c R09: 0000000000000001
Jul 24 15:25:18 btrfs2 kernel: [14789.720395] R10: 0000000000000008 R11: 
ffff88013ad69da0 R12: ffff88013ad69a30
Jul 24 15:25:18 btrfs2 kernel: [14789.720395] R13: ffff880100000004 R14: 
ffff88013ad69a50 R15: ffffffffa038ace1
Jul 24 15:25:18 btrfs2 kernel: [14789.720395] FS:  
0000000000000000(0000) GS:ffff88002ba18000(0000) knlGS:0000000000000000
Jul 24 15:25:18 btrfs2 kernel: [14789.720395] CS:  0010 DS: 0018 ES: 
0018 CR0: 000000008005003b
Jul 24 15:25:18 btrfs2 kernel: [14789.720395] CR2: 00007fc84af9f000 CR3: 
000000013e0d4000 CR4: 00000000000006e0
Jul 24 15:25:18 btrfs2 kernel: [14789.720395] DR0: 0000000000000000 DR1: 
0000000000000000 DR2: 0000000000000000
Jul 24 15:25:18 btrfs2 kernel: [14789.720395] DR3: 0000000000000000 DR6: 
00000000ffff0ff0 DR7: 0000000000000400
Jul 24 15:25:18 btrfs2 kernel: [14789.720395] Call Trace:
Jul 24 15:25:18 btrfs2 kernel: [14789.720395]  [<ffffffffa03976b7>] ? 
btrfs_tree_lock+0x54/0x9e [btrfs]
Jul 24 15:25:19 btrfs2 kernel: [14789.720395]  [<ffffffffa039760a>] ? 
btrfs_wake_function+0x0/0x10 [btrfs]
Jul 24 15:25:19 btrfs2 kernel: [14789.720395]  [<ffffffffa035cfa3>] ? 
btrfs_lock_root_node+0x1d/0x4b [btrfs]
Jul 24 15:25:19 btrfs2 kernel: [14789.720395]  [<ffffffffa0362fd6>] ? 
btrfs_search_slot+0xc7/0x76c [btrfs]
Jul 24 15:25:19 btrfs2 kernel: [14789.720395]  [<ffffffffa038ace1>] ? 
map_extent_buffer+0xab/0xbe [btrfs]
Jul 24 15:25:19 btrfs2 kernel: [14789.720395]  [<ffffffffa03643bb>] ? 
btrfs_insert_empty_items+0x5e/0xa9 [btrfs]
Jul 24 15:25:19 btrfs2 kernel: [14789.720395]  [<ffffffffa036a350>] ? 
run_one_delayed_ref+0x167/0x432 [btrfs]
Jul 24 15:25:19 btrfs2 kernel: [14789.720395]  [<ffffffffa036b1f2>] ? 
run_clustered_refs+0x237/0x2b4 [btrfs]
Jul 24 15:25:19 btrfs2 kernel: [14789.720395]  [<ffffffffa03a011d>] ? 
btrfs_find_ref_cluster+0xdc/0x115 [btrfs]
Jul 24 15:25:19 btrfs2 kernel: [14789.720395]  [<ffffffffa036b31b>] ? 
btrfs_run_delayed_refs+0xac/0x195 [btrfs]
Jul 24 15:25:19 btrfs2 kernel: [14789.720395]  [<ffffffffa0374b05>] ? 
__btrfs_end_transaction+0x59/0xfe [btrfs]


Steve

Bug

[Artjom]

Unable to load compat-wireless-2.6.tar.bz2 drivers in fedora 8.
Kernel is 2.6.26.2-3.fc8

                                                  Best Regards.
                                                        Artjom.

Here is the output of dmesg -c:
[root@localhost compat-wireless-2008-08-06]# dmesg -c

mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
rtl8180: Unknown symbol ieee80211_free_hw
rtl8180: Unknown symbol ieee80211_alloc_hw
rtl8180: Unknown symbol ieee80211_register_hw
rtl8180: Unknown symbol ieee80211_wake_queue
rtl8180: Unknown symbol ieee80211_tx_status_irqsafe
rtl8180: Unknown symbol ieee80211_stop_queue
rtl8180: Unknown symbol ieee80211_unregister_hw
rtl8180: Unknown symbol ieee80211_frequency_to_channel
rtl8180: Unknown symbol ieee80211_rx_irqsafe
rtl8180: Unknown symbol ieee80211_rts_duration
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
rtl8187: Unknown symbol ieee80211_free_hw
rtl8187: Unknown symbol ieee80211_alloc_hw
rtl8187: Unknown symbol ieee80211_register_hw
rtl8187: Unknown symbol ieee80211_generic_frame_duration
rtl8187: Unknown symbol ieee80211_tx_status_irqsafe
rtl8187: Unknown symbol ieee80211_unregister_hw
rtl8187: Unknown symbol ieee80211_frequency_to_channel
rtl8187: Unknown symbol ieee80211_rx_irqsafe
rtl8187: Unknown symbol ieee80211_rts_duration
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
rtl8180: Unknown symbol ieee80211_free_hw
rtl8180: Unknown symbol ieee80211_alloc_hw
rtl8180: Unknown symbol ieee80211_register_hw
rtl8180: Unknown symbol ieee80211_wake_queue
rtl8180: Unknown symbol ieee80211_tx_status_irqsafe
rtl8180: Unknown symbol ieee80211_stop_queue
rtl8180: Unknown symbol ieee80211_unregister_hw
rtl8180: Unknown symbol ieee80211_frequency_to_channel
rtl8180: Unknown symbol ieee80211_rx_irqsafe
rtl8180: Unknown symbol ieee80211_rts_duration
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
rtl8187: Unknown symbol ieee80211_free_hw
rtl8187: Unknown symbol ieee80211_alloc_hw
rtl8187: Unknown symbol ieee80211_register_hw
rtl8187: Unknown symbol ieee80211_generic_frame_duration
rtl8187: Unknown symbol ieee80211_tx_status_irqsafe
rtl8187: Unknown symbol ieee80211_unregister_hw
rtl8187: Unknown symbol ieee80211_frequency_to_channel
rtl8187: Unknown symbol ieee80211_rx_irqsafe
rtl8187: Unknown symbol ieee80211_rts_duration
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
rt2x00lib: Unknown symbol ieee80211_register_hw
rt2x00lib: Unknown symbol ieee80211_get_hdrlen_from_skb
rt2x00lib: Unknown symbol ieee80211_wake_queue
rt2x00lib: Unknown symbol ieee80211_tx_status_irqsafe
rt2x00lib: Unknown symbol ieee80211_ctstoself_get
rt2x00lib: Unknown symbol ieee80211_wake_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces
rt2x00lib: Unknown symbol ieee80211_stop_queue
rt2x00lib: Unknown symbol ieee80211_stop_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces_atomic
rt2x00lib: Unknown symbol ieee80211_channel_to_frequency
rt2x00lib: Unknown symbol ieee80211_unregister_hw
rt2x00lib: Unknown symbol ieee80211_rts_get
rt2x00lib: Unknown symbol ieee80211_beacon_get
rt2x00lib: Unknown symbol ieee80211_rx_irqsafe
rt2x00pci: Unknown symbol rt2x00lib_suspend
rt2x00pci: Unknown symbol rt2x00lib_probe_dev
rt2x00pci: Unknown symbol ieee80211_free_hw
rt2x00pci: Unknown symbol ieee80211_alloc_hw
rt2x00pci: Unknown symbol rt2x00lib_rxdone
rt2x00pci: Unknown symbol rt2x00queue_get_entry
rt2x00pci: Unknown symbol rt2x00lib_remove_dev
rt2x00pci: Unknown symbol rt2x00lib_resume
rt2400pci: Unknown symbol rt2x00mac_add_interface
rt2400pci: Unknown symbol rt2x00queue_map_txskb
rt2400pci: Unknown symbol rt2x00mac_get_stats
rt2400pci: Unknown symbol rt2x00pci_initialize
rt2400pci: Unknown symbol rt2x00pci_uninitialize
rt2400pci: Unknown symbol rt2x00queue_get_entry
rt2400pci: Unknown symbol rt2x00pci_suspend
rt2400pci: Unknown symbol rt2x00mac_config_interface
rt2400pci: Unknown symbol rt2x00pci_remove
rt2400pci: Unknown symbol rt2x00mac_remove_interface
rt2400pci: Unknown symbol rt2x00lib_txdone
rt2400pci: Unknown symbol rt2x00mac_config
rt2400pci: Unknown symbol rt2x00queue_get_queue
rt2400pci: Unknown symbol rt2x00mac_conf_tx
rt2400pci: Unknown symbol rt2x00mac_start
rt2400pci: Unknown symbol rt2x00mac_stop
rt2400pci: Unknown symbol rt2x00mac_configure_filter
rt2400pci: Unknown symbol rt2x00mac_tx
rt2400pci: Unknown symbol rt2x00pci_resume
rt2400pci: Unknown symbol rt2x00pci_probe
rt2400pci: Unknown symbol rt2x00mac_get_tx_stats
rt2400pci: Unknown symbol rt2x00pci_rxdone
rt2400pci: Unknown symbol rt2x00lib_beacondone
rt2400pci: Unknown symbol rt2x00mac_bss_info_changed
rt2400pci: Unknown symbol rt2x00pci_write_tx_data
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
rt2x00lib: Unknown symbol ieee80211_register_hw
rt2x00lib: Unknown symbol ieee80211_get_hdrlen_from_skb
rt2x00lib: Unknown symbol ieee80211_wake_queue
rt2x00lib: Unknown symbol ieee80211_tx_status_irqsafe
rt2x00lib: Unknown symbol ieee80211_ctstoself_get
rt2x00lib: Unknown symbol ieee80211_wake_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces
rt2x00lib: Unknown symbol ieee80211_stop_queue
rt2x00lib: Unknown symbol ieee80211_stop_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces_atomic
rt2x00lib: Unknown symbol ieee80211_channel_to_frequency
rt2x00lib: Unknown symbol ieee80211_unregister_hw
rt2x00lib: Unknown symbol ieee80211_rts_get
rt2x00lib: Unknown symbol ieee80211_beacon_get
rt2x00lib: Unknown symbol ieee80211_rx_irqsafe
rt2x00pci: Unknown symbol rt2x00lib_suspend
rt2x00pci: Unknown symbol rt2x00lib_probe_dev
rt2x00pci: Unknown symbol ieee80211_free_hw
rt2x00pci: Unknown symbol ieee80211_alloc_hw
rt2x00pci: Unknown symbol rt2x00lib_rxdone
rt2x00pci: Unknown symbol rt2x00queue_get_entry
rt2x00pci: Unknown symbol rt2x00lib_remove_dev
rt2x00pci: Unknown symbol rt2x00lib_resume
rt2500pci: Unknown symbol rt2x00mac_add_interface
rt2500pci: Unknown symbol rt2x00queue_map_txskb
rt2500pci: Unknown symbol rt2x00mac_get_stats
rt2500pci: Unknown symbol rt2x00pci_initialize
rt2500pci: Unknown symbol rt2x00pci_uninitialize
rt2500pci: Unknown symbol rt2x00queue_get_entry
rt2500pci: Unknown symbol rt2x00pci_suspend
rt2500pci: Unknown symbol rt2x00mac_config_interface
rt2500pci: Unknown symbol rt2x00pci_remove
rt2500pci: Unknown symbol rt2x00mac_remove_interface
rt2500pci: Unknown symbol rt2x00lib_txdone
rt2500pci: Unknown symbol rt2x00mac_config
rt2500pci: Unknown symbol rt2x00queue_get_queue
rt2500pci: Unknown symbol rt2x00mac_conf_tx
rt2500pci: Unknown symbol rt2x00mac_start
rt2500pci: Unknown symbol rt2x00mac_stop
rt2500pci: Unknown symbol rt2x00mac_configure_filter
rt2500pci: Unknown symbol rt2x00mac_tx
rt2500pci: Unknown symbol rt2x00pci_resume
rt2500pci: Unknown symbol rt2x00pci_probe
rt2500pci: Unknown symbol rt2x00mac_get_tx_stats
rt2500pci: Unknown symbol rt2x00pci_rxdone
rt2500pci: Unknown symbol rt2x00lib_beacondone
rt2500pci: Unknown symbol rt2x00mac_bss_info_changed
rt2500pci: Unknown symbol rt2x00pci_write_tx_data
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
rt2x00lib: Unknown symbol ieee80211_register_hw
rt2x00lib: Unknown symbol ieee80211_get_hdrlen_from_skb
rt2x00lib: Unknown symbol ieee80211_wake_queue
rt2x00lib: Unknown symbol ieee80211_tx_status_irqsafe
rt2x00lib: Unknown symbol ieee80211_ctstoself_get
rt2x00lib: Unknown symbol ieee80211_wake_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces
rt2x00lib: Unknown symbol ieee80211_stop_queue
rt2x00lib: Unknown symbol ieee80211_stop_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces_atomic
rt2x00lib: Unknown symbol ieee80211_channel_to_frequency
rt2x00lib: Unknown symbol ieee80211_unregister_hw
rt2x00lib: Unknown symbol ieee80211_rts_get
rt2x00lib: Unknown symbol ieee80211_beacon_get
rt2x00lib: Unknown symbol ieee80211_rx_irqsafe
rt2x00pci: Unknown symbol rt2x00lib_suspend
rt2x00pci: Unknown symbol rt2x00lib_probe_dev
rt2x00pci: Unknown symbol ieee80211_free_hw
rt2x00pci: Unknown symbol ieee80211_alloc_hw
rt2x00pci: Unknown symbol rt2x00lib_rxdone
rt2x00pci: Unknown symbol rt2x00queue_get_entry
rt2x00pci: Unknown symbol rt2x00lib_remove_dev
rt2x00pci: Unknown symbol rt2x00lib_resume
rt61pci: Unknown symbol rt2x00mac_add_interface
rt61pci: Unknown symbol rt2x00mac_get_stats
rt61pci: Unknown symbol rt2x00pci_initialize
rt61pci: Unknown symbol rt2x00pci_uninitialize
rt61pci: Unknown symbol rt2x00queue_get_entry
rt61pci: Unknown symbol rt2x00pci_suspend
rt61pci: Unknown symbol rt2x00mac_config_interface
rt61pci: Unknown symbol rt2x00pci_remove
rt61pci: Unknown symbol rt2x00mac_remove_interface
rt61pci: Unknown symbol rt2x00lib_txdone
rt61pci: Unknown symbol rt2x00mac_config
rt61pci: Unknown symbol rt2x00queue_get_queue
rt61pci: Unknown symbol rt2x00mac_conf_tx
rt61pci: Unknown symbol rt2x00mac_start
rt61pci: Unknown symbol rt2x00mac_stop
rt61pci: Unknown symbol rt2x00mac_configure_filter
rt61pci: Unknown symbol rt2x00mac_tx
rt61pci: Unknown symbol rt2x00pci_resume
rt61pci: Unknown symbol rt2x00pci_probe
rt61pci: Unknown symbol rt2x00mac_get_tx_stats
rt61pci: Unknown symbol rt2x00pci_rxdone
rt61pci: Unknown symbol rt2x00mac_bss_info_changed
rt61pci: Unknown symbol rt2x00pci_write_tx_data
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
rt2x00lib: Unknown symbol ieee80211_register_hw
rt2x00lib: Unknown symbol ieee80211_get_hdrlen_from_skb
rt2x00lib: Unknown symbol ieee80211_wake_queue
rt2x00lib: Unknown symbol ieee80211_tx_status_irqsafe
rt2x00lib: Unknown symbol ieee80211_ctstoself_get
rt2x00lib: Unknown symbol ieee80211_wake_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces
rt2x00lib: Unknown symbol ieee80211_stop_queue
rt2x00lib: Unknown symbol ieee80211_stop_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces_atomic
rt2x00lib: Unknown symbol ieee80211_channel_to_frequency
rt2x00lib: Unknown symbol ieee80211_unregister_hw
rt2x00lib: Unknown symbol ieee80211_rts_get
rt2x00lib: Unknown symbol ieee80211_beacon_get
rt2x00lib: Unknown symbol ieee80211_rx_irqsafe
rt2x00usb: Unknown symbol rt2x00lib_suspend
rt2x00usb: Unknown symbol rt2x00lib_probe_dev
rt2x00usb: Unknown symbol ieee80211_free_hw
rt2x00usb: Unknown symbol ieee80211_alloc_hw
rt2x00usb: Unknown symbol rt2x00lib_rxdone
rt2x00usb: Unknown symbol rt2x00lib_remove_dev
rt2x00usb: Unknown symbol rt2x00lib_txdone
rt2x00usb: Unknown symbol rt2x00queue_get_queue
rt2x00usb: Unknown symbol rt2x00lib_resume
rt2500usb: Unknown symbol rt2x00mac_add_interface
rt2500usb: Unknown symbol rt2x00mac_get_stats
rt2500usb: Unknown symbol rt2x00usb_init_rxentry
rt2500usb: Unknown symbol rt2x00usb_disable_radio
rt2500usb: Unknown symbol rt2x00usb_init_txentry
rt2500usb: Unknown symbol rt2x00usb_vendor_request_buff
rt2500usb: Unknown symbol rt2x00usb_kick_tx_queue
rt2500usb: Unknown symbol rt2x00usb_write_tx_data
rt2500usb: Unknown symbol rt2x00mac_config_interface
rt2500usb: Unknown symbol rt2x00mac_remove_interface
rt2500usb: Unknown symbol rt2x00usb_vendor_request
rt2500usb: Unknown symbol rt2x00usb_probe
rt2500usb: Unknown symbol rt2x00mac_config
rt2500usb: Unknown symbol rt2x00usb_suspend
rt2500usb: Unknown symbol rt2x00mac_conf_tx
rt2500usb: Unknown symbol rt2x00mac_start
rt2500usb: Unknown symbol rt2x00mac_stop
rt2500usb: Unknown symbol rt2x00mac_configure_filter
rt2500usb: Unknown symbol rt2x00usb_disconnect
rt2500usb: Unknown symbol rt2x00mac_tx
rt2500usb: Unknown symbol rt2x00usb_vendor_req_buff_lock
rt2500usb: Unknown symbol rt2x00mac_get_tx_stats
rt2500usb: Unknown symbol rt2x00usb_resume
rt2500usb: Unknown symbol rt2x00usb_uninitialize
rt2500usb: Unknown symbol rt2x00usb_initialize
rt2500usb: Unknown symbol rt2x00mac_bss_info_changed
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
rt2x00lib: Unknown symbol ieee80211_register_hw
rt2x00lib: Unknown symbol ieee80211_get_hdrlen_from_skb
rt2x00lib: Unknown symbol ieee80211_wake_queue
rt2x00lib: Unknown symbol ieee80211_tx_status_irqsafe
rt2x00lib: Unknown symbol ieee80211_ctstoself_get
rt2x00lib: Unknown symbol ieee80211_wake_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces
rt2x00lib: Unknown symbol ieee80211_stop_queue
rt2x00lib: Unknown symbol ieee80211_stop_queues
rt2x00lib: Unknown symbol ieee80211_iterate_active_interfaces_atomic
rt2x00lib: Unknown symbol ieee80211_channel_to_frequency
rt2x00lib: Unknown symbol ieee80211_unregister_hw
rt2x00lib: Unknown symbol ieee80211_rts_get
rt2x00lib: Unknown symbol ieee80211_beacon_get
rt2x00lib: Unknown symbol ieee80211_rx_irqsafe
rt2x00usb: Unknown symbol rt2x00lib_suspend
rt2x00usb: Unknown symbol rt2x00lib_probe_dev
rt2x00usb: Unknown symbol ieee80211_free_hw
rt2x00usb: Unknown symbol ieee80211_alloc_hw
rt2x00usb: Unknown symbol rt2x00lib_rxdone
rt2x00usb: Unknown symbol rt2x00lib_remove_dev
rt2x00usb: Unknown symbol rt2x00lib_txdone
rt2x00usb: Unknown symbol rt2x00queue_get_queue
rt2x00usb: Unknown symbol rt2x00lib_resume
rt73usb: Unknown symbol rt2x00mac_add_interface
rt73usb: Unknown symbol rt2x00mac_get_stats
rt73usb: Unknown symbol rt2x00usb_init_rxentry
rt73usb: Unknown symbol rt2x00usb_disable_radio
rt73usb: Unknown symbol rt2x00usb_init_txentry
rt73usb: Unknown symbol rt2x00usb_vendor_request_buff
rt73usb: Unknown symbol rt2x00usb_kick_tx_queue
rt73usb: Unknown symbol rt2x00usb_write_tx_data
rt73usb: Unknown symbol rt2x00mac_config_interface
rt73usb: Unknown symbol rt2x00mac_remove_interface
rt73usb: Unknown symbol rt2x00usb_vendor_request
rt73usb: Unknown symbol rt2x00usb_probe
rt73usb: Unknown symbol rt2x00mac_config
rt73usb: Unknown symbol rt2x00usb_suspend
rt73usb: Unknown symbol rt2x00mac_conf_tx
rt73usb: Unknown symbol rt2x00mac_start
rt73usb: Unknown symbol rt2x00mac_stop
rt73usb: Unknown symbol rt2x00mac_configure_filter
rt73usb: Unknown symbol rt2x00usb_disconnect
rt73usb: Unknown symbol rt2x00mac_tx
rt73usb: Unknown symbol rt2x00usb_vendor_req_buff_lock
rt73usb: Unknown symbol rt2x00mac_get_tx_stats
rt73usb: Unknown symbol rt2x00usb_resume
rt73usb: Unknown symbol rt2x00usb_uninitialize
rt73usb: Unknown symbol rt2x00usb_initialize
rt73usb: Unknown symbol rt2x00mac_bss_info_changed
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver rndis_host
usbcore: registered new interface driver rndis_wlan
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
at76_usb: Unknown symbol ieee80211_free_hw
at76_usb: Unknown symbol ieee80211_alloc_hw
at76_usb: Unknown symbol ieee80211_register_hw
at76_usb: Unknown symbol ieee80211_tx_status_irqsafe
at76_usb: Unknown symbol ieee80211_wake_queues
at76_usb: Unknown symbol ieee80211_stop_queues
at76_usb: Unknown symbol ieee80211_scan_completed
at76_usb: Unknown symbol ieee80211_unregister_hw
at76_usb: Unknown symbol ieee80211_rx_irqsafe
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
ath5k: Unknown symbol ieee80211_free_hw
ath5k: Unknown symbol ieee80211_alloc_hw
ath5k: Unknown symbol ieee80211_register_hw
ath5k: Unknown symbol ieee80211_get_hdrlen_from_skb
ath5k: Unknown symbol ieee80211_generic_frame_duration
ath5k: Unknown symbol __ieee80211_get_tx_led_name
ath5k: Unknown symbol __ieee80211_get_rx_led_name
ath5k: Unknown symbol ieee80211_wake_queues
ath5k: Unknown symbol __ieee80211_rx
ath5k: Unknown symbol ieee80211_tx_status
ath5k: Unknown symbol ieee80211_stop_queue
ath5k: Unknown symbol ieee80211_stop_queues
ath5k: Unknown symbol ieee80211_unregister_hw
ath5k: Unknown symbol ieee80211_beacon_get
ath5k: Unknown symbol ieee80211_frequency_to_channel
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [LK4E] -> GSI 19 (level,
high) -> IRQ 19
PCI: Setting latency timer of device 0000:03:00.0 to 64
ssb: Sonics Silicon Backplane found on PCI device 0000:03:00.0
b43: Unknown symbol ieee80211_free_hw
b43: Unknown symbol ieee80211_alloc_hw
b43: Unknown symbol ieee80211_register_hw
b43: Unknown symbol ieee80211_generic_frame_duration
b43: Unknown symbol ieee80211_wake_queue
b43: Unknown symbol __ieee80211_get_tx_led_name
b43: Unknown symbol ieee80211_tx_status_irqsafe
b43: Unknown symbol __ieee80211_get_rx_led_name
b43: Unknown symbol ieee80211_ctstoself_get
b43: Unknown symbol ieee80211_stop_queue
b43: Unknown symbol __ieee80211_get_assoc_led_name
b43: Unknown symbol ieee80211_unregister_hw
b43: Unknown symbol ieee80211_hdrlen
b43: Unknown symbol ieee80211_rts_get
b43: Unknown symbol ieee80211_beacon_get
b43: Unknown symbol ieee80211_rx_irqsafe
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
b43legacy: Unknown symbol ieee80211_free_hw
b43legacy: Unknown symbol ieee80211_alloc_hw
b43legacy: Unknown symbol ieee80211_register_hw
b43legacy: Unknown symbol ieee80211_generic_frame_duration
b43legacy: Unknown symbol ieee80211_wake_queue
b43legacy: Unknown symbol __ieee80211_get_tx_led_name
b43legacy: Unknown symbol ieee80211_tx_status_irqsafe
b43legacy: Unknown symbol __ieee80211_get_rx_led_name
b43legacy: Unknown symbol ieee80211_ctstoself_get
b43legacy: Unknown symbol ieee80211_stop_queue
b43legacy: Unknown symbol ieee80211_stop_queues
b43legacy: Unknown symbol ieee80211_get_hdrlen
b43legacy: Unknown symbol __ieee80211_get_assoc_led_name
b43legacy: Unknown symbol ieee80211_unregister_hw
b43legacy: Unknown symbol ieee80211_hdrlen
b43legacy: Unknown symbol ieee80211_rts_get
b43legacy: Unknown symbol ieee80211_beacon_get
b43legacy: Unknown symbol ieee80211_rx_irqsafe
cfg80211: exports duplicate symbol rfkill_force_state (owned by rfkill)
mac80211: Unknown symbol wiphy_register
mac80211: Unknown symbol wiphy_new
mac80211: Unknown symbol wiphy_unregister
mac80211: Unknown symbol ieee80211_radiotap_iterator_init
mac80211: Unknown symbol __ieee80211_get_channel
mac80211: Unknown symbol ieee80211_radiotap_iterator_next
mac80211: Unknown symbol ieee80211_channel_to_frequency
mac80211: Unknown symbol ieee80211_frequency_to_channel
mac80211: Unknown symbol wiphy_free
b43: Unknown symbol ieee80211_free_hw
b43: Unknown symbol ieee80211_alloc_hw
b43: Unknown symbol ieee80211_register_hw
b43: Unknown symbol ieee80211_generic_frame_duration
b43: Unknown symbol ieee80211_wake_queue
b43: Unknown symbol __ieee80211_get_tx_led_name
b43: Unknown symbol ieee80211_tx_status_irqsafe
b43: Unknown symbol __ieee80211_get_rx_led_name
b43: Unknown symbol ieee80211_ctstoself_get
b43: Unknown symbol ieee80211_stop_queue
b43: Unknown symbol __ieee80211_get_assoc_led_name
b43: Unknown symbol ieee80211_unregister_hw
b43: Unknown symbol ieee80211_hdrlen
b43: Unknown symbol ieee80211_rts_get
b43: Unknown symbol ieee80211_beacon_get
b43: Unknown symbol ieee80211_rx_irqsafe

Bug

[ohviey1]

I work with ubutnu the last version.
I have a big problem when a search to load filesystem into an ARM with 
ethernet who works at 10 Mb/s
The problem is thet:


IP-Config: 
Complete:                                                           
      device=eth0, addr=10.193.101.129, mask=255.255.255.0, 
gw=10.193.101.1,   
     host=10.193.101.129, domain=, 
nis-domain=(none),                          
     bootserver=10.193.101.100, rootserver=10.193.101.100, 
rootpath=           
Looking up port of RPC 100003/2 on 
10.193.101.100                              
Looking up port of RPC 100005/1 on 
10.193.101.100                              
w1_master_driver w1_bus_master1: Family 9 for 09.000003f08c27.80 is not 
registe.
VFS: Mounted root (nfs 
filesystem).                                            
Freeing init memory: 
200K                                                      
nfs: server 10.193.101.100 not responding, still 
trying                        
nfs: server 10.193.101.100 not responding, still 
trying                        

Have you same idea how can reslve thet i searched on google possible is 
a bug?

Re: bug

[Adrian Bunk]

On Thu, Jan 12, 2006 at 04:23:55PM +0100, Philippe Delodder wrote:
> ------------[ cut here ]------------
> kernel BUG at lib/radix-tree.c:271!
> invalid operand: 0000 [#1]
> PREEMPT
> Modules linked in: af_packet ipv6 floppy analog parport_pc parport evdev
> pcspkr 8139cp snd_intel8x0m snd_intel8x0 snd_ac97_codec snd_pcm snd_timer
> snd_page_alloc gameport snd_mpu401_uart snd_rawmidi snd_seq_device snd
> hw_random pci_hotplug intel_agp uhci_hcd usbcore i810_audio ac97_codec
> soundcore 8139too mii agpgart quota_v2 ext3 jbd capability commoncap
> psmouse ide_cd cdrom rtc reiserfs ide_generic ide_disk piix ide_core unix
> font vesafb cfbcopyarea cfbimgblt cfbfillrect
> CPU:    0
> EIP:    0060:[<c018d02e>]    Not tainted
> EFLAGS: 00010096   (2.6.8-2-386)
>...

2.6.8 is a very ancient kernel.

Please either try to reproduce it with a vanilla ftp.kernel.org 2.6.15 
or contact your vendor (Debian?) regarding this issue.

> Philippe Delodder

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

bug

[Philippe Delodder]

------------[ cut here ]------------
kernel BUG at lib/radix-tree.c:271!
invalid operand: 0000 [#1]
PREEMPT
Modules linked in: af_packet ipv6 floppy analog parport_pc parport evdev
pcspkr 8139cp snd_intel8x0m snd_intel8x0 snd_ac97_codec snd_pcm snd_timer
snd_page_alloc gameport snd_mpu401_uart snd_rawmidi snd_seq_device snd
hw_random pci_hotplug intel_agp uhci_hcd usbcore i810_audio ac97_codec
soundcore 8139too mii agpgart quota_v2 ext3 jbd capability commoncap
psmouse ide_cd cdrom rtc reiserfs ide_generic ide_disk piix ide_core unix
font vesafb cfbcopyarea cfbimgblt cfbfillrect
CPU:    0
EIP:    0060:[<c018d02e>]    Not tainted
EFLAGS: 00010096   (2.6.8-2-386)
EIP is at radix_tree_insert+0xc7/0xdc
eax: ffffffff   ebx: 00000000   ecx: 00000000   edx: 00000014
esi: c6ae3c90   edi: c6ae3ce4   ebp: fffffffa   esp: c534bb2c
ds: 007b   es: 007b   ss: 0068
Process find (pid: 26989, threadinfo=c534a000 task=c78242b0)
Stack: c534a000 00000000 c10594c0 cfa9c13c c012d1ec cfa9c140 000c82d4
c10594c0
       c10594c0 c10594c0 00000050 000c82d4 c012d24d c10594c0 cfa9c13c
000c82d4
       00000050 c10594c0 00000000 c012d658 c10594c0 cfa9c13c 000c82d4
00000050
Call Trace:
 [<c012d1ec>] add_to_page_cache+0x39/0x82
 [<c012d24d>] add_to_page_cache_lru+0x18/0x2d
 [<c012d658>] find_or_create_page+0x4f/0x91
 [<c01468e6>] grow_dev_page+0x28/0x108
 [<c0146a9f>] __getblk_slow+0xd9/0x124
 [<c0146da2>] __getblk+0x2d/0x35
 [<d08f486f>] search_by_key+0x73/0xe22 [reiserfs]
 [<d08ede10>] init_once+0x21/0x32 [reiserfs]
 [<d08f4541>] pathrelse+0x1e/0x2d [reiserfs]
 [<d08e4b5b>] init_inode+0x2d8/0x381 [reiserfs]
 [<d08e5165>] reiserfs_read_locked_inode+0x61/0xe7 [reiserfs]
 [<d08e5258>] reiserfs_iget+0x4a/0x7f [reiserfs]
 [<d08e0a23>] reiserfs_lookup+0xfa/0x1b8 [reiserfs]
 [<c010b003>] timer_interrupt+0x45/0xff
 [<c01586eb>] d_lookup+0x18/0x35
 [<c014f646>] real_lookup+0x51/0xb5
 [<c014f86b>] do_lookup+0x41/0x72
 [<c015008c>] link_path_walk+0x7f0/0xb86
 [<c0107ee5>] do_IRQ+0xe5/0xf9
 [<c010697c>] common_interrupt+0x18/0x20
 [<c014007b>] shmem_file_setup+0x128/0x190
 [<c01506ea>] path_lookup+0x121/0x129
 [<c015081c>] __user_walk+0x23/0x3a
 [<c014c26c>] vfs_lstat+0x12/0x3e
 [<c014c7e8>] sys_lstat64+0x10/0x27
 [<c0105f97>] syscall_call+0x7/0xb
Code: 0f 0b 0f 01 c5 5b 26 c0 8b 44 24 1c 89 07 31 c0 5b 5e 5f 5d
 <6>note: find[26989] exited with preempt_count 3
bad: scheduling while atomic!
 [<c024d5a0>] schedule+0x3c/0x3e6
 [<c01382ad>] unmap_vmas+0xe0/0x1cf
 [<c013832f>] unmap_vmas+0x162/0x1cf
 [<c013b8a3>] exit_mmap+0x6a/0x12a
 [<c01171db>] mmput+0x5e/0x73
 [<c011ab81>] do_exit+0x162/0x34f
 [<c0106fde>] do_divide_error+0x0/0xa7
 [<c0107262>] do_invalid_op+0x8a/0x93
 [<c018d02e>] radix_tree_insert+0xc7/0xdc
 [<d085a48e>] ide_build_sglist+0x30/0x90 [ide_core]
 [<c011eaf0>] __mod_timer+0xe6/0x13d
 [<c018f12c>] __delay+0xc/0xe
 [<d085590b>] ide_execute_command+0x82/0xa3 [ide_core]
 [<d085ab7d>] __ide_dma_begin+0x27/0x38 [ide_core]
 [<c018d02e>] radix_tree_insert+0xc7/0xdc
 [<c011437a>] do_emu+0x409/0x453
 [<d085a82e>] dma_timer_expiry+0x0/0x64 [ide_core]
 [<d0857e1e>] do_rw_taskfile+0x1c7/0x1e1 [ide_core]
 [<c018d02f>] radix_tree_insert+0xc8/0xdc
 [<c0113f71>] do_emu+0x0/0x453
 [<c0106a19>] error_code+0x2d/0x38
 [<c018d02e>] radix_tree_insert+0xc7/0xdc
 [<c012d1ec>] add_to_page_cache+0x39/0x82
 [<c012d24d>] add_to_page_cache_lru+0x18/0x2d
 [<c012d658>] find_or_create_page+0x4f/0x91
 [<c01468e6>] grow_dev_page+0x28/0x108
 [<c0146a9f>] __getblk_slow+0xd9/0x124
 [<c0146da2>] __getblk+0x2d/0x35
 [<d08f486f>] search_by_key+0x73/0xe22 [reiserfs]
 [<d08ede10>] init_once+0x21/0x32 [reiserfs]
 [<d08f4541>] pathrelse+0x1e/0x2d [reiserfs]
 [<d08e4b5b>] init_inode+0x2d8/0x381 [reiserfs]
 [<d08e5165>] reiserfs_read_locked_inode+0x61/0xe7 [reiserfs]
 [<d08e5258>] reiserfs_iget+0x4a/0x7f [reiserfs]
 [<d08e0a23>] reiserfs_lookup+0xfa/0x1b8 [reiserfs]
 [<c010b003>] timer_interrupt+0x45/0xff
 [<c01586eb>] d_lookup+0x18/0x35
 [<c014f646>] real_lookup+0x51/0xb5
 [<c014f86b>] do_lookup+0x41/0x72
 [<c015008c>] link_path_walk+0x7f0/0xb86
 [<c0107ee5>] do_IRQ+0xe5/0xf9
 [<c010697c>] common_interrupt+0x18/0x20
 [<c014007b>] shmem_file_setup+0x128/0x190
 [<c01506ea>] path_lookup+0x121/0x129
 [<c015081c>] __user_walk+0x23/0x3a
 [<c014c26c>] vfs_lstat+0x12/0x3e
 [<c014c7e8>] sys_lstat64+0x10/0x27
 [<c0105f97>] syscall_call+0x7/0xb



-- 
Philippe Delodder
lodder@delodder.be
http://www.delodder.be

bug

[Victor G. Marimon]

ses/i2c-ali15x3.c -o kernel/busses/i2c-ali15x3.o
gcc  -DMODVERSIONS -include /lib/modules/2.4.21/build/include/linux/modversions.
h -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/includ
e -I/usr/local/include -I/lib/modules/2.4.21/build/include   -O2   -c kernel/bus
ses/i2c-amd756.c -o kernel/busses/i2c-amd756.o
gcc  -DMODVERSIONS -include /lib/modules/2.4.21/build/include/linux/modversions.
h -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/includ
e -I/usr/local/include -I/lib/modules/2.4.21/build/include   -O2   -c kernel/bus
ses/i2c-amd8111.c -o kernel/busses/i2c-amd8111.o
kernel/busses/i2c-amd8111.c:25:2: #error Your i2c is too old - i2c-2.7.0 or grea
ter required!
kernel/busses/i2c-amd8111.c: En la funci?n `amd8111_access':
kernel/busses/i2c-amd8111.c:238: `I2C_CLIENT_PEC' no ha sido declarado aqu? (pri
mero ?selo en esta funci?n)
kernel/busses/i2c-amd8111.c:238: (Cada identificador no declarado solamente se r
eporta una vez
kernel/busses/i2c-amd8111.c:238: para cada funcion en la que aparece.)
kernel/busses/i2c-amd8111.c:298: `I2C_SMBUS_BLOCK_PROC_CALL' no ha sido declarad
o aqu? (primero ?selo en esta funci?n)
kernel/busses/i2c-amd8111.c:309: `I2C_SMBUS_WORD_DATA_PEC' no ha sido declarado
aqu? (primero ?selo en esta funci?n)
kernel/busses/i2c-amd8111.c:310: `I2C_SMBUS_BLOCK_DATA_PEC' no ha sido declarado
 aqu? (primero ?selo en esta funci?n)
kernel/busses/i2c-amd8111.c:311: `I2C_SMBUS_PROC_CALL_PEC' no ha sido declarado
aqu? (primero ?selo en esta funci?n)
kernel/busses/i2c-amd8111.c:312: `I2C_SMBUS_BLOCK_PROC_CALL_PEC' no ha sido decl
arado aqu? (primero ?selo en esta funci?n)
kernel/busses/i2c-amd8111.c: En la funci?n `amd8111_func':
kernel/busses/i2c-amd8111.c:385: `I2C_FUNC_SMBUS_BLOCK_PROC_CALL' no ha sido dec
larado aqu? (primero ?selo en esta funci?n)
kernel/busses/i2c-amd8111.c:386: `I2C_FUNC_SMBUS_HWPEC_CALC' no ha sido declarad
o aqu? (primero ?selo en esta funci?n)
kernel/busses/i2c-amd8111.c: En la funci?n `amd8111_probe':
kernel/busses/i2c-amd8111.c:426: `I2C_HW_SMBUS_AMD8111' no ha sido declarado aqu
? (primero ?selo en esta funci?n)
make: *** [kernel/busses/i2c-amd8111.o] Error 1
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20030630/ec968927/attachment.html

bug

[Jean Delvare]

> ses/i2c-ali15x3.c -o kernel/busses/i2c-ali15x3.o
> gcc  -DMODVERSIONS -include
> /lib/modules/2.4.21/build/include/linux/modversions. h -D__KERNEL__
> -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/includ e
> -I/usr/local/include -I/lib/modules/2.4.21/build/include   -O2   -c
> kernel/bus ses/i2c-amd756.c -o kernel/busses/i2c-amd756.o
> gcc  -DMODVERSIONS -include
> /lib/modules/2.4.21/build/include/linux/modversions. h -D__KERNEL__
> -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/includ e
> -I/usr/local/include -I/lib/modules/2.4.21/build/include   -O2   -c
> kernel/bus ses/i2c-amd8111.c -o kernel/busses/i2c-amd8111.o
> kernel/busses/i2c-amd8111.c:25:2: #error Your i2c is too old -
> i2c-2.7.0 or grea ter required!

Well, I think the error message is explicit. You need to upgrade i2c to
2.7.0.

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

bug

[Victor G. Marimon]

>
> > ses/i2c-ali15x3.c -o kernel/busses/i2c-ali15x3.o
> > gcc  -DMODVERSIONS -include
> > /lib/modules/2.4.21/build/include/linux/modversions. h -D__KERNEL__
> > -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/includ e
> > -I/usr/local/include -I/lib/modules/2.4.21/build/include   -O2   -c
> > kernel/bus ses/i2c-amd756.c -o kernel/busses/i2c-amd756.o
> > gcc  -DMODVERSIONS -include
> > /lib/modules/2.4.21/build/include/linux/modversions. h -D__KERNEL__
> > -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/includ e
> > -I/usr/local/include -I/lib/modules/2.4.21/build/include   -O2   -c
> > kernel/bus ses/i2c-amd8111.c -o kernel/busses/i2c-amd8111.o
> > kernel/busses/i2c-amd8111.c:25:2: #error Your i2c is too old -
> > i2c-2.7.0 or grea ter required!
>
> Well, I think the error message is explicit. You need to upgrade i2c to
> 2.7.0.


        yes, but i'm using kernel 2.4.21 and for now only have i2c patches
for 2.4.20

bug

[Jean Delvare]

> > Well, I think the error message is explicit. You need to upgrade i2c
> > to 2.7.0.
> 
> 
>         yes, but i'm using kernel 2.4.21 and for now only have i2c
>         patches
> for 2.4.20

You can install i2c from our i2c-2.7.0 package. It doesn't require to
patch the kernel. Just make sure you don't have any I2C module built
into the kernel itself, and install all the modules from our package
(make && make install && depmod -ae should just do it).

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

bug

[Victor G. Marimon]

> You can install i2c from our i2c-2.7.0 package. It doesn't require to
> patch the kernel. Just make sure you don't have any I2C module built
> into the kernel itself, and install all the modules from our package
> (make && make install && depmod -ae should just do it).


        i compiled & instaled i2c-2.7.0 and when doing 'make' in lm-sensors
shows the same error:









h -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/in
clud
e -I/usr/local/include -I/lib/modules/2.4.21/build/include   -O2   -c
kernel/bus
ses/i2c-amd8111.c -o kernel/busses/i2c-amd8111.o
kernel/busses/i2c-amd8111.c:25:2: #error Your i2c is too old - i2c-2.7.0 or
grea
ter required!
kernel/busses/i2c-amd8111.c: En la funci?n `amd8111_access':
kernel/busses/i2c-amd8111.c:238: `I2C_CLIENT_PEC' no ha sido declarado aqu?
(pri
mero ?selo en esta funci?n)
kernel/busses/i2c-amd8111.c:238: (Cada identificador no declarado solamente
se r
eporta una vez
kernel/busses/i2c-amd8111.c:238: para cada funcion en la que aparece.)
kernel/busses/i2c-amd8111.c:298: `I2C_SMBUS_BLOCK_PROC_CALL' no ha sido
declarad
o aqu? (primero ?selo en esta funci?n)
kernel/busses/i2c-amd8111.c:309: `I2C_SMBUS_WORD_DATA_PEC' no ha sido
declarado
aqu? (primero ?selo en esta funci?n)
kernel/busses/i2c-amd8111.c:310: `I2C_SMBUS_BLOCK_DATA_PEC' no ha sido
declarado
 aqu? (primero ?selo en esta funci?n)
kernel/busses/i2c-amd8111.c:311: `I2C_SMBUS_PROC_CALL_PEC' no ha sido
declarado
aqu? (primero ?selo en esta funci?n)
kernel/busses/i2c-amd8111.c:312: `I2C_SMBUS_BLOCK_PROC_CALL_PEC' no ha sido
decl
arado aqu? (primero ?selo en esta funci?n)
kernel/busses/i2c-amd8111.c: En la funci?n `amd8111_func':
kernel/busses/i2c-amd8111.c:385: `I2C_FUNC_SMBUS_BLOCK_PROC_CALL' no ha sido
dec
larado aqu? (primero ?selo en esta funci?n)
kernel/busses/i2c-amd8111.c:386: `I2C_FUNC_SMBUS_HWPEC_CALC' no ha sido
declarad
o aqu? (primero ?selo en esta funci?n)
kernel/busses/i2c-amd8111.c: En la funci?n `amd8111_probe':
kernel/busses/i2c-amd8111.c:426: `I2C_HW_SMBUS_AMD8111' no ha sido declarado
aqu
? (primero ?selo en esta funci?n)
make: *** [kernel/busses/i2c-amd8111.o] Error 1

bug

[Jean Delvare]

> > You can install i2c from our i2c-2.7.0 package. It doesn't require
> > to patch the kernel. Just make sure you don't have any I2C module
> > built into the kernel itself, and install all the modules from our
> > package(make && make install && depmod -ae should just do it).
> 
> 
>         i compiled & instaled i2c-2.7.0 and when doing 'make' in
>         lm-sensors
> shows the same error:

Please make sure you don't have an old set of i2c header files in
/usr/include, this is a common mistake. Also, take a look at the news
item of May 31st, 2003 on our news pages:
http://secure.netroedge.com/~lm78/

This seems to describe your problem quite well.

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

Re: bug

[Kay Sievers]

On Wed, 2005-03-23 at 11:41 +0100, Jan Boros wrote:

> I did update my kernel on my gentoo laptop, when I plug my PCMCIA eth
> card I am getting following message:

> Mar 23 11:36:17 rachel wait_for_sysfs[10476]: error: unknown bus, please
> report to <linux-hotplug-devel@lists.sourceforge.net> 'pcmcia'
> Mar 23 11:36:17 rachel wait_for_sysfs[10476]: either wait_for_sysfs
> (udev 045) needs an update to handle the device

You may update your udev version to get rid of these messages.

> Mar 23 11:36:20 rachel irq 11: nobody cared!
> Mar 23 11:36:20 rachel [<c0133c3a>] __report_bad_irq+0x2a/0xa0

Which kernel version is it?
Which network driver do you load?

Kay



-------------------------------------------------------
This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
for the chance to win $25,000 and application distribution. Enter today at
http://ads.osdn.com/?ad_idh82&alloc_id\x15148&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

bug

[Jan Boros]

[-- Attachment #1: Type: text/plain, Size: 3151 bytes --]

HI


I did update my kernel on my gentoo laptop, when I plug my PCMCIA eth
card I am getting following message:

cardmgr[6952]: socket 1: D-Link DMF560TX Ethernet/Modem
Mar 23 11:36:17 rachel cs: memory probe 0xa0000000-0xa0ffffff: clean.
Mar 23 11:36:17 rachel cardmgr[6952]: executing: 'modprobe pcnet_cs'
Mar 23 11:36:17 rachel cardmgr[6952]: executing: 'modprobe serial_cs'
Mar 23 11:36:17 rachel cardmgr[6952]: executing: './network start eth0'
Mar 23 11:36:17 rachel eth0: NE2000 (DL10019 rev 05): io 0x300, irq 11,
hw_addr 00:E0:98:8E:40:6D
Mar 23 11:36:17 rachel ttyS1 at I/O 0x2f8 (irq = 11) is a 16550A
Mar 23 11:36:17 rachel wait_for_sysfs[10476]: error: unknown bus, please
report to <linux-hotplug-devel@lists.sourceforge.net> 'pcmcia'
Mar 23 11:36:17 rachel wait_for_sysfs[10476]: either wait_for_sysfs
(udev 045) needs an update to handle the device
'/devices/pci0000:00/0000:00:1e.0/0000:02:0f.1/1.0' properly (unknown
bus) or the sysfs-support of your device's driver needs to be fixed,
please report to <linux-hotplug-devel@lists.sourceforge.net>
Mar 23 11:36:17 rachel wait_for_sysfs[10483]: error: unknown bus, please
report to <linux-hotplug-devel@lists.sourceforge.net> 'pcmcia'
Mar 23 11:36:17 rachel wait_for_sysfs[10493]: error: unknown bus, please
report to <linux-hotplug-devel@lists.sourceforge.net> 'pcmcia'
Mar 23 11:36:17 rachel wait_for_sysfs[10493]: either wait_for_sysfs
(udev 045) needs an update to handle the device
'/devices/pci0000:00/0000:00:1e.0/0000:02:0f.1/1.1' properly (unknown
bus) or the sysfs-support of your device's driver needs to be fixed,
please report to <linux-hotplug-devel@lists.sourceforge.net>
Mar 23 11:36:20 rachel irq 11: nobody cared!
Mar 23 11:36:20 rachel [<c0133c3a>] __report_bad_irq+0x2a/0xa0
Mar 23 11:36:20 rachel [<c0133560>] handle_IRQ_event+0x30/0x70
Mar 23 11:36:20 rachel [<c0133d40>] note_interrupt+0x70/0xb0
Mar 23 11:36:20 rachel [<c01336e5>] __do_IRQ+0x145/0x160
Mar 23 11:36:20 rachel [<c0104da3>] do_IRQ+0x23/0x40
Mar 23 11:36:20 rachel [<c010331e>] common_interrupt+0x1a/0x20
Mar 23 11:36:20 rachel [<c011c46e>] __do_softirq+0x2e/0x90
Mar 23 11:36:20 rachel [<c011c4f6>] do_softirq+0x26/0x30
Mar 23 11:36:20 rachel [<c011c5c5>] irq_exit+0x35/0x40
Mar 23 11:36:20 rachel [<c0104da8>] do_IRQ+0x28/0x40
Mar 23 11:36:20 rachel [<c010331e>] common_interrupt+0x1a/0x20
Mar 23 11:36:20 rachel handlers:
Mar 23 11:36:20 rachel [<e0c87e00>] (usb_hcd_irq+0x0/0x70 [usbcore])
Mar 23 11:36:20 rachel [<e0eea8a0>] (yenta_interrupt+0x0/0x40
[yenta_socket])
Mar 23 11:36:20 rachel [<e0eea8a0>] (yenta_interrupt+0x0/0x40
[yenta_socket])
Mar 23 11:36:20 rachel [<e10116e0>] (ei_irq_wrapper+0x0/0x40 [pcnet_cs])
Mar 23 11:36:20 rachel Disabling IRQ #11
Mar 23 11:36:20 rachel eth0: found link beat
Mar 23 11:36:20 rachel eth0: autonegotiation complete: 100baseT-FD
selected
Mar 23 11:36:20 rachel cardmgr[6952]: +  * WARNING:  "net.eth0" has
already been started.
Mar 23 11:36:20 rachel rc-scripts: WARNING:  "net.eth0" has already been
started.




so, I am writing to that email, do you want me to send more info ?


j.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: Bug

[Ryan Underwood]

[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]


On Sat, Jan 10, 2004 at 12:54:19PM -0700, Tyler Harmor wrote:
> Went thru the install.  When it told me to type 'xdosemu' that would not
> work, so I followed the instructions at the end of the 'make install'
> which said to run 'dosemu'.  This then asked the startup questions and
> when it asked me to finally hit 'enter' to start it up this is what it
> gave me:
> 
> Linux DOS emulator 1.1.99.1 $Date: 2003/09/17 14:40:53 $
> Last configured at Sat Jan 10 12:40:31 MST 2004 on linux
> This is work in progress.
> Please test against a recent version before reporting bugs and problems.
> Submit Bug Reports, Patches & New Code to linux-msdos@vger.kernel.org or
> via
> the SourceForge tracking system at
> http://www.sourceforge.net/projects/dosemu
> 
> DPMI-Server Version 0.9 installed
> 
> 
> Sorry, there is no operating system.
> Have a nice day!
> 
> Not to sure how I should proceed, but thought you may want to know about
> it.  I am currently running Debian Linux with the linux-2.4.22 kernel.

Have you installed a DOS (such as freedos) somewhere? Try apt-get
install dosemu-freedos.

-- 
Ryan Underwood, <nemesis@icequake.net>

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Bug

[Tyler Harmor]

Went thru the install.  When it told me to type 'xdosemu' that would not
work, so I followed the instructions at the end of the 'make install'
which said to run 'dosemu'.  This then asked the startup questions and
when it asked me to finally hit 'enter' to start it up this is what it
gave me:

Linux DOS emulator 1.1.99.1 $Date: 2003/09/17 14:40:53 $
Last configured at Sat Jan 10 12:40:31 MST 2004 on linux
This is work in progress.
Please test against a recent version before reporting bugs and problems.
Submit Bug Reports, Patches & New Code to linux-msdos@vger.kernel.org or
via
the SourceForge tracking system at
http://www.sourceforge.net/projects/dosemu

DPMI-Server Version 0.9 installed


Sorry, there is no operating system.
Have a nice day!

Not to sure how I should proceed, but thought you may want to know about
it.  I am currently running Debian Linux with the linux-2.4.22 kernel.

ty|er.

"Two roads divirged in the woods, and the driver took the one without
state troopers."

bug

[Виталий]

(i'm not subscribed to linux kernel mail list)
System dying while watching video from cdrom.
When I installed kernel 2.4.18, anytime i was watching video from cdrom
system was dying in 10-15 minits and hdd led was on
(normally hdd led do not light while reading from cdrom).
There is no such problem in 2.4.17.

Chipset VIA Apollo pro 133 (VT82C693A and VT82C686A)
Cdrom Mitsumi FX810T4

/proc/version
Linux version 2.4.18 (agri@agri) (gcc version 3.0.4) #3 Птн Мар 15 22:43:10 
MSK
 2002

ver_linux output:
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.
 
Linux agri 2.4.18 #3 Птн Мар 15 22:43:10 MSK 2002 i686 unknown

Gnu C                  3.0.4
Gnu make               3.79.1
binutils               2.11.2
util-linux             2.10q
mount                  2.10q
modutils               2.4.1
e2fsprogs              1.19
PPP                    2.4.0
Linux C Library        2.2.5
Dynamic linker (ldd)   2.2.5
Linux C++ Library      3.0.4
Procps                 2.0.7
Net-tools              1.57
Kbd                    1.02
Sh-utils               2.0
Modules Loaded         rtc serial isa-pnp isofs cdrom

/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 6
model name	: Celeron (Mendocino)
stepping	: 0
cpu MHz		: 487.515
cache size	: 128 KB
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 2
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 
mmx
 fxsr
bogomips	: 973.20

/proc/modules:
isofs                  16720   0 (unused)
cdrom                  27840   0 (unused)
rtc                     5760   0 (autoclean)
serial                 45680   0 (autoclean) (unused)
isa-pnp                29168   0 (autoclean) [serial]

/proc/ioports:
0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
0213-0213 : isapnp read
0376-0376 : ide1
03c0-03df : vga+
03f6-03f6 : ide0
0a79-0a79 : isapnp write
0cf8-0cff : PCI conf1
5000-500f : PCI device 1106:3057
6000-607f : PCI device 1106:3057
e000-e00f : PCI device 1106:0571
  e000-e007 : ide0
  e008-e00f : ide1
e400-e41f : PCI device 1106:3038
e800-e81f : PCI device 1106:3038
ec00-ec07 : PCI device 12b9:1008
  ec00-ec07 : serial(auto)

/proc/iomem:
00000000-0009fbff : System RAM
0009fc00-0009ffff : reserved
000a0000-000bffff : Video RAM area
000c0000-000c7fff : Video ROM
000f0000-000fffff : System ROM
00100000-07ffffff : System RAM
  00100000-001d4bc4 : Kernel code
  001d4bc5-002038bf : Kernel data
d0000000-d7ffffff : PCI Bus #01
  d0000000-d3ffffff : PCI device 5333:8a13
d8000000-d83fffff : PCI device 1106:0691
ffff0000-ffffffff : reserved

hdparm /dev/hdd (cdrom):

 HDIO_GET_MULTCOUNT failed: Invalid argument
 HDIO_GET_NOWERR failed: Invalid argument
 HDIO_GETGEO failed: Invalid argument

/dev/hdd:
 I/O support  =  1 (32-bit)
 unmaskirq    =  1 (on)
 using_dma    =  1 (on)
 keepsettings =  0 (off)
 readonly     =  1 (on)
 readahead    =  8 (on)


hdparm /dev/hda:

/dev/hda:
 multcount    =  0 (off)
 I/O support  =  1 (32-bit)
 unmaskirq    =  1 (on)
 using_dma    =  1 (on)
 keepsettings =  0 (off)
 nowerr       =  0 (off)
 readonly     =  0 (off)
 readahead    =  8 (on)
 geometry     = 2490/255/63, sectors = 40011300, start = 0

BUG

[Attila A Odry]

Sep  6 23:45:25 Outside kernel: skput:over: c01f12c6:1448 put:1448
dev:<NULL>kernel BUG at skbuff.c:93!
Sep  6 23:45:25 Outside kernel: invalid operand: 0000
Sep  6 23:45:25 Outside kernel: CPU:    0

Kernel version 2.4.9 FINAL,  CPU INFO 667Mhz Coppermine 512MB 133Mhz SDRAM

Re: BUG

[Zdenek Kabelac]

Grzegorz Sojka wrote:
> 
> I am using kernel v2.4.0 on Abit BP6 with two Intel Pentium Celeron
> 366@517Mhz + video based on Riva TNT2 M64 32Mb + network card 3com 3c905b
> + Creative Sound Blaster 64 pnp isa and hercules video card. I'm geting
> all over the time messages like that:
> Jan 31 23:37:16 Zeus kernel: APIC error on CPU0: 02(02)
> Jan 31 23:37:17 Zeus kernel: APIC error on CPU1: 02(08)

Enjoy this wonderful patch :)

--- linux.orig/arch/i386/kernel/apic.c  Tue Jan 23 21:41:23 2001
+++ linux/arch/i386/kernel/apic.c       Tue Jan 23 21:40:41 2001
@@ -765,6 +765,7 @@
        v1 = apic_read(APIC_ESR);
        ack_APIC_irq();
        irq_err_count++;
+       if (1) return;
 
        /* Here is what the APIC error bits mean:
           0: Send CS error


It's not fix - you just don't get this borring message....


-- 
             There are three types of people in the world:
               those who can count, and those who can't.
  Zdenek Kabelac  http://i.am/kabi/ kabi@i.am {debian.org; fi.muni.cz}

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: BUG

[Maciej W. Rozycki]

On Wed, 31 Jan 2001, James Sutherland wrote:

> > Jan 31 23:39:18 Zeus kernel: APIC error on CPU1: 08(02)
> > Jan 31 23:39:46 Zeus kernel: APIC error on CPU0: 04(02)
[...]
> (These are common, but fairly harmless FWIH, on BP6s.)

 Yep, until you get a lockup due to an undetected error...

-- 
+  Maciej W. Rozycki, Technical University of Gdansk, Poland   +
+--------------------------------------------------------------+
+        e-mail: macro@ds2.pg.gda.pl, PGP key available        +

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: BUG

[James Sutherland]

On Wed, 31 Jan 2001, Grzegorz Sojka wrote:

> I am using kernel v2.4.0 on Abit BP6 with two Intel Pentium Celeron
> 366@517Mhz + video based on Riva TNT2 M64 32Mb + network card 3com 3c905b
> + Creative Sound Blaster 64 pnp isa and hercules video card. I'm geting
> all over the time messages like that:
> Jan 31 23:37:16 Zeus kernel: APIC error on CPU0: 02(02)
> Jan 31 23:37:17 Zeus kernel: APIC error on CPU1: 02(08)
> Jan 31 23:37:26 Zeus kernel: APIC error on CPU1: 08(08)
> Jan 31 23:37:26 Zeus kernel: APIC error on CPU1: 08(08)
> Jan 31 23:37:26 Zeus kernel: APIC error on CPU0: 02(04)
> Jan 31 23:37:27 Zeus kernel: APIC error on CPU0: 04(02)
> Jan 31 23:37:30 Zeus kernel: APIC error on CPU1: 08(08)
> Jan 31 23:38:17 Zeus kernel: APIC error on CPU0: 02(08)
> Jan 31 23:38:20 Zeus kernel: APIC error on CPU1: 08(08)
> Jan 31 23:38:22 Zeus kernel: APIC error on CPU0: 08(02)
> Jan 31 23:38:26 Zeus kernel: APIC error on CPU1: 08(08)
> Jan 31 23:38:26 Zeus kernel: APIC error on CPU0: 02(02)
> Jan 31 23:38:29 Zeus kernel: APIC error on CPU1: 08(02)
> Jan 31 23:38:41 Zeus kernel: APIC error on CPU1: 02(08)
> Jan 31 23:38:51 Zeus kernel: APIC error on CPU0: 02(02)
> Jan 31 23:38:58 Zeus kernel: APIC error on CPU1: 08(08)
> Jan 31 23:39:15 Zeus kernel: APIC error on CPU1: 08(02)
> Jan 31 23:39:15 Zeus kernel: APIC error on CPU1: 02(08)
> Jan 31 23:39:15 Zeus kernel: APIC error on CPU0: 02(04)
> Jan 31 23:39:17 Zeus kernel: APIC error on CPU1: 08(08)
> Jan 31 23:39:18 Zeus kernel: APIC error on CPU1: 08(02)
> Jan 31 23:39:46 Zeus kernel: APIC error on CPU0: 04(02)
> And when I was using kernels v2.2.x ther was no such messages. I am
> wandering if it is hardware or software problem?

Hardware problem. You don't SEE these messages on 2.2 because it doesn't
tell you about them :-)

(These are common, but fairly harmless FWIH, on BP6s.)


James.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

BUG

[Grzegorz Sojka]

I am using kernel v2.4.0 on Abit BP6 with two Intel Pentium Celeron
366@517Mhz + video based on Riva TNT2 M64 32Mb + network card 3com 3c905b
+ Creative Sound Blaster 64 pnp isa and hercules video card. I'm geting
all over the time messages like that:
Jan 31 23:37:16 Zeus kernel: APIC error on CPU0: 02(02)
Jan 31 23:37:17 Zeus kernel: APIC error on CPU1: 02(08)
Jan 31 23:37:26 Zeus kernel: APIC error on CPU1: 08(08)
Jan 31 23:37:26 Zeus kernel: APIC error on CPU1: 08(08)
Jan 31 23:37:26 Zeus kernel: APIC error on CPU0: 02(04)
Jan 31 23:37:27 Zeus kernel: APIC error on CPU0: 04(02)
Jan 31 23:37:30 Zeus kernel: APIC error on CPU1: 08(08)
Jan 31 23:38:17 Zeus kernel: APIC error on CPU0: 02(08)
Jan 31 23:38:20 Zeus kernel: APIC error on CPU1: 08(08)
Jan 31 23:38:22 Zeus kernel: APIC error on CPU0: 08(02)
Jan 31 23:38:26 Zeus kernel: APIC error on CPU1: 08(08)
Jan 31 23:38:26 Zeus kernel: APIC error on CPU0: 02(02)
Jan 31 23:38:29 Zeus kernel: APIC error on CPU1: 08(02)
Jan 31 23:38:41 Zeus kernel: APIC error on CPU1: 02(08)
Jan 31 23:38:51 Zeus kernel: APIC error on CPU0: 02(02)
Jan 31 23:38:58 Zeus kernel: APIC error on CPU1: 08(08)
Jan 31 23:39:15 Zeus kernel: APIC error on CPU1: 08(02)
Jan 31 23:39:15 Zeus kernel: APIC error on CPU1: 02(08)
Jan 31 23:39:15 Zeus kernel: APIC error on CPU0: 02(04)
Jan 31 23:39:17 Zeus kernel: APIC error on CPU1: 08(08)
Jan 31 23:39:18 Zeus kernel: APIC error on CPU1: 08(02)
Jan 31 23:39:46 Zeus kernel: APIC error on CPU0: 04(02)
And when I was using kernels v2.2.x ther was no such messages. I am
wandering if it is hardware or software problem?


				Grzes.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Bug

[ralf]

On Fri, Sep 04, 1998 at 08:51:47PM +0200, Ulf Carlsson wrote:

> I think you forgot a break in the middle of a switch statement, setting
> order to 3 is pretty nonsense otherwise.
> I compiled a new kernel with my patch, and I couldn't see any changes. The
> VCED is probably handled correctly by the interrupt anyway.

Thanks, applied.  Note that this bug just resulted in somewhat reduced
performance at cost of 28kb more memory used.  On SC CPUs we use 8
different empty_zero_page pages to avoid VCED errors completly.

  Ralf

Bug

[Ulf Carlsson]

Hi,

I think you forgot a break in the middle of a switch statement, setting
order to 3 is pretty nonsense otherwise.
I compiled a new kernel with my patch, and I couldn't see any changes. The
VCED is probably handled correctly by the interrupt anyway.

patch applies to arch/mips/mm/init.c

--- init.c.org  Fri Sep  4 20:34:11 1998
+++ init.c      Fri Sep  4 20:45:40 1998
@@ -126,6 +126,7 @@
        case CPU_R4400SC:
        case CPU_R4400MC:
                order = 3;
+               break;
        default:
                order = 0;
        }

- Ulf

bug

[Ulf Carlsson]

How's it going with the bug?

- Ulf

Re: bug

[ralf]

On Sat, Apr 04, 1998 at 06:30:15PM +0200, Ulf Carlsson wrote:

> How's it going with the bug?

EGCS is bootstrapping ...

   Ralf