Netdev List
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Jay Cliburn <jcliburn@gmail.com>,
	Chris Snook <chris.snook@gmail.com>,
	Jie Yang <jie.yang@atheros.com>
Cc: bugme-daemon@bugzilla.kernel.org, netdev@vger.kernel.org,
	willi@goesgens.de
Subject: Re: [Bugme-new] [Bug 41192] New: acer aspire one d522 locks up due to NIC
Date: Tue, 16 Aug 2011 15:00:43 -0700	[thread overview]
Message-ID: <20110816150043.96a91094.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-41192-10286@https.bugzilla.kernel.org/>


(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Mon, 15 Aug 2011 12:03:56 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=41192
> 
>            Summary: acer aspire one d522 locks up due to NIC
>            Product: Drivers
>            Version: 2.5
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: Network
>         AssignedTo: drivers_network@kernel-bugs.osdl.org
>         ReportedBy: willi@goesgens.de
>         Regression: No
> 
> 
> Created an attachment (id=68882)
>  --> (https://bugzilla.kernel.org/attachment.cgi?id=68882)
> dmesg output of whole system run
> 
> This netbook is equipped with:
> 06:00.0 Ethernet controller: Atheros Communications AR8152 v2.0 Fast Ethernet
> (rev c1)
> 07:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network
> Adapter (PCI-Express) (rev 01)
> 
> if there is a network manager probing the cable NIC for the cable status, the
> whole system locks up completely.
> 
> the lockup can be circumvented by: 
>  - not loading the kernel module for the cable NIC
>  - not starting 'network manager' or 'WICD', same problems on both.
>  - turning on the systems netboot agent as pointed out by walterav on
> http://phoronix.com/forums/showthread.php?31961-Notes-on-Acer-Aspire-One-522/page7
> 
> 
> Module                  Size  Used by
> bnep                   17346  2 
> rfcomm                 73852  0 
> bluetooth             252589  10 bnep,rfcomm
> binfmt_misc             7588  1 
> fuse                   70593  1 
> synaptics_i2c_rmi4      7979  0 
> ath9k                  83089  0 
> mac80211              248833  1 ath9k
> ath9k_common            2456  1 ath9k
> ath9k_hw              302986  2 ath9k,ath9k_common
> k10temp                 3378  0 
> uvcvideo               57863  0 
> ath                    15715  2 ath9k,ath9k_hw
> cfg80211              211736  3 ath9k,mac80211,ath
> atl1c                  45270  0 
> rfkill                 19387  3 bluetooth,cfg80211
> sp5100_tco              5392  0 
> i2c_piix4              11482  0 
> mac_hid                 3645  0
> 


           reply	other threads:[~2011-08-16 22:01 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-41192-10286@https.bugzilla.kernel.org/>]

Reply instructions:

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

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

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

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

  git send-email \
    --in-reply-to=20110816150043.96a91094.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=chris.snook@gmail.com \
    --cc=jcliburn@gmail.com \
    --cc=jie.yang@atheros.com \
    --cc=netdev@vger.kernel.org \
    --cc=willi@goesgens.de \
    /path/to/YOUR_REPLY

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

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