From: Andrew Morton <akpm@linux-foundation.org>
To: badibere@gmail.com
Cc: bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, netdev@vger.kernel.org,
linux-acpi@vger.kernel.org,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Jay Cliburn <jcliburn@gmail.com>,
Chris Snook <chris.snook@gmail.com>,
Jie Yang <jie.yang@atheros.com>
Subject: Re: [Bugme-new] [Bug 14336] New: [Pardus] Soft Lockup Problem with Attansic Ethernet Card
Date: Tue, 6 Oct 2009 15:55:02 -0700 [thread overview]
Message-ID: <20091006155502.f3fc86d9.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-14336-10286@http.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Tue, 6 Oct 2009 22:37:13 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=14336
>
> Summary: [Pardus] Soft Lockup Problem with Attansic Ethernet
> Card
> Product: Networking
> Version: 2.5
> Kernel Version: 2.6.30.8
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: high
> Priority: P1
> Component: IPV4
> AssignedTo: shemminger@linux-foundation.org
> ReportedBy: badibere@gmail.com
> Regression: No
>
>
> I have soft lockup problem with attansic ethernet card while activating eth0
> interface.
>
> My ethernet card is 09:00.0 Ethernet controller: Attansic Technology Corp.
> Device 1063 (rev c0)
>
> If I try to activate eth0 interface while network cable is pluged in, then
> everything freezes.
>
> If I try to activate eth0 interface while network cable isn't pluged in, then
> no problem. But, if i plug in, again freezes.
>
> My /var/log/syslog is in attachment.
>
>From the dmesg output it appears that this card is driven by the atl1c
driver:
Oct 7 00:55:57 baDibere kernel: [ 169.943463] atl1c 0000:09:00.0: Unable to allocate MSI interrupt Error: -22
Oct 7 00:55:57 baDibere kernel: [ 169.943576] atl1c 0000:09:00.0: atl1c: eth0 NIC Link is Up<100 Mbps Full Duplex>
Oct 7 00:56:22 baDibere kernel: [ 194.849361] NVRM: Xid (0001:00): 16, Head 00000000 Count 00003651
Oct 7 00:56:31 baDibere kernel: [ 203.849307] NVRM: Xid (0001:00): 16, Head 00000000 Count 00003653
Oct 7 00:56:36 baDibere kernel: [ 208.849339] NVRM: Xid (0001:00): 8, Channel 00000003
Oct 7 00:56:41 baDibere kernel: [ 213.852320] NVRM: Xid (0001:00): 16, Head 00000000 Count 00003655
The "Unable to allocate MSI interrupt" might be the immediate problem.
Who belongs to MSI interrupt allocation? PCI? ACPI?
However the driver does attempt to handle and recover from the MSI
interrupt allocation error so perhaps that's no the cause at all.
next parent reply other threads:[~2009-10-06 22:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14336-10286@http.bugzilla.kernel.org/>
2009-10-06 22:55 ` Andrew Morton [this message]
[not found] ` <3d54862b0910061601iba25b87hfba151f71d6ce4ef@mail.gmail.com>
2009-10-06 23:33 ` [Bugme-new] [Bug 14336] New: [Pardus] Soft Lockup Problem with Attansic Ethernet Card J. K. Cliburn
2009-10-06 23:39 ` J. K. Cliburn
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=20091006155502.f3fc86d9.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=badibere@gmail.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=chris.snook@gmail.com \
--cc=jbarnes@virtuousgeek.org \
--cc=jcliburn@gmail.com \
--cc=jie.yang@atheros.com \
--cc=linux-acpi@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).