netdev - RE: alt1c: ethernet driver bug

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 9 Oct 2009 11:37:11 +0800
From:	Jie Yang <Jie.Yang@...eros.com>
To:	Stephen Hemminger <shemminger@...tta.com>
CC:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: alt1c: ethernet driver bug

 Stephen Hemminger <shemminger@...tta.com> wrote:
> Sent: Wednesday, October 07, 2009 7:11 AM
> To: Jie Yang
> Cc: netdev@...r.kernel.org
> Subject: alt1c: ethernet driver bug
>
> > 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@...ux-foundation.org
> >         ReportedBy: badibere@...il.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.
> >
>
> this is what was in the bug attachment
>
> Oct  7 00:53:33 baDibere kernel: [   16.162099] atl1c
> 0000:09:00.0: enabling device (0000 -> 0002)
> Oct  7 00:53:33 baDibere kernel: [   16.162117] atl1c
> 0000:09:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> Oct  7 00:53:33 baDibere kernel: [   16.162141] atl1c
> 0000:09:00.0: setting latency timer to 64
> Oct  7 00:53:33 baDibere kernel: [   16.162247] atl1c
> 0000:09:00.0: PME# disabled
> Oct  7 00:53:33 baDibere kernel: [   16.162266] atl1c
> 0000:09:00.0: PME# disabled
> Oct  7 00:53:33 baDibere kernel: [   16.230835] atl1c
> 0000:09:00.0: version 1.0.0.1-NAPI
> 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>
>
when "pci_enable_msi" failed, I will also request_irq, so it should not be a problem.
the message "NIC Link is Up<100 Mbps Full Duplex>" demonstrate the atl1c interrupt has worked.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html