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
| ||
|
Date: Sat, 21 Aug 2010 22:03:12 +0200 From: "Rafael J. Wysocki" <rjw@...k.pl> To: Alex <alexbtk@....de> Cc: eric.dumazet@...il.com, romieu@...zoreil.com, davem@...emloft.net, adobriyan@...il.com, jpirko@...hat.com, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: Fwd: Re: Linux r8169 interrupt patch On Saturday, August 21, 2010, Alex wrote: > Hello gyus, > > I am writing to you, on case of the linux r8169 interrupt bug. Sergey > gave me your addresses. I assume you can read all the neccessary > informations below. Please reopen the thread at the bugtracker. > I have several servers running with this chipset and driver. In my case, > the problem is very critical. Network brokes even every day down. I can > provide some testing if you would give me some patches or solution tips. > > Thanks in advance for your reply. https://bugzilla.kernel.org/show_bug.cgi?id=15704 reopened. Thanks, Rafael > -------- Original-Nachricht -------- > Betreff: Re: Linux r8169 interrupt patch > Datum: Sat, 21 Aug 2010 14:14:36 +0300 > Von: Sergey Senozhatsky <sergey.senozhatsky@...il.com> > An: alex <alexbtk@....de> > CC: sergey.senozhatsky@...il.com > > > > On (08/20/10 22:24), alex wrote: > > Date: Fri, 20 Aug 2010 22:24:20 +0200 > > From: alex<alexbtk@....de> > > To: sergey.senozhatsky@...il.com > > Subject: Linux r8169 interrupt patch > > User-Agent: Opera Mail/10.61 (Win32) > > > > Hello Sergey, > > > > Hello Alex, > > > I write to you, because of your conversation in this tracker: > > http://patchwork.ozlabs.org/patch/47889/ > > > > I have the same problem on the 2.6.33.7 kernel. I even upgraded > > yesterday from 2.6.33.6, hoping to solve this bug. My kernel-panic > > occurs even every day. That's very disgustig. > > Here the trace: > > > > Aug 20 02:41:48 het1 kernel: [49652.963863] ------------[ cut here > > ]------------ > > Aug 20 02:41:48 het1 kernel: [49652.964033] WARNING: at > > net/sched/sch_generic.c:259 dev_watchdog+0x14d/0x208() > > Aug 20 02:41:48 het1 kernel: [49652.964346] Hardware name: MS-7522 > > Aug 20 02:41:48 het1 kernel: [49652.964504] NETDEV WATCHDOG: eth0 > > (r8169): transmit queue 0 timed out > > Aug 20 02:41:48 het1 kernel: [49652.964670] Pid: 71, comm: > > sirq-timer/5 Not tainted 2.6.33.7-rt29 #1 > > Aug 20 02:41:48 het1 kernel: [49652.964835] Call Trace: > > Aug 20 02:41:48 het1 kernel: [49652.964997] [<ffffffff812fcf32>] ? > > dev_watchdog+0x14d/0x208 > > Aug 20 02:41:48 het1 kernel: [49652.965001] [<ffffffff8103233c>] ? > > warn_slowpath_common+0x72/0x9e > > Aug 20 02:41:48 het1 kernel: [49652.965004] [<ffffffff810323c4>] ? > > warn_slowpath_fmt+0x51/0x59 > > Aug 20 02:41:48 het1 kernel: [49652.965008] [<ffffffff8102e474>] ? > > try_to_wake_up+0x351/0x37f > > Aug 20 02:41:48 het1 kernel: [49652.965012] [<ffffffff8106dce4>] ? > > cpupri_set+0x10f/0x138 > > Aug 20 02:41:48 het1 kernel: [49652.965016] [<ffffffff812ebb40>] ? > > netdev_drivername+0x3b/0x40 > > Aug 20 02:41:48 het1 kernel: [49652.965019] [<ffffffff812fcf32>] ? > > dev_watchdog+0x14d/0x208 > > Aug 20 02:41:48 het1 kernel: [49652.965022] [<ffffffff81027e68>] ? > > update_curr_rt+0x114/0x18b > > Aug 20 02:41:48 het1 kernel: [49652.965025] [<ffffffff8102c972>] ? > > finish_task_switch+0x4a/0xa3 > > Aug 20 02:41:48 het1 kernel: [49652.965028] [<ffffffff812fcde5>] ? > > dev_watchdog+0x0/0x208 > > Aug 20 02:41:48 het1 kernel: [49652.965031] [<ffffffff8103b688>] ? > > run_timer_softirq+0x20b/0x2a9 > > Aug 20 02:41:48 het1 kernel: [49652.965035] [<ffffffff81036b50>] ? > > run_ksoftirqd+0x182/0x2a6 > > Aug 20 02:41:48 het1 kernel: [49652.965038] [<ffffffff810369ce>] ? > > run_ksoftirqd+0x0/0x2a6 > > Aug 20 02:41:48 het1 kernel: [49652.965041] [<ffffffff81044759>] ? > > kthread+0x79/0x81 > > Aug 20 02:41:48 het1 kernel: [49652.965044] [<ffffffff8102c972>] ? > > finish_task_switch+0x4a/0xa3 > > Aug 20 02:41:48 het1 kernel: [49652.965048] [<ffffffff81003714>] ? > > kernel_thread_helper+0x4/0x10 > > Aug 20 02:41:48 het1 kernel: [49652.965051] [<ffffffff810446e0>] ? > > kthread+0x0/0x81 > > Aug 20 02:41:48 het1 kernel: [49652.965053] [<ffffffff81003710>] ? > > kernel_thread_helper+0x0/0x10 > > Aug 20 02:41:48 het1 kernel: [49652.965055] ---[ end trace > > 1af3434dfa0224f2 ]--- > > > > I read that the patch fix the rx_interrupt(), but as I can see in my > > case, he fails while sending the packets "transmit queue 0 timed > > out". > > My question now: Have you solved the problem? If yes, by applying the > > patch? > > > > No, unfortunately no. The problem is that this laptop (with r8169) is no longer > available. > > We had a later conversation with Eric, and he had proposed several patches > (none of them, however didn't solve the problem). > > So, I'll recommend to contanct Eric Dumazet<eric.dumazet@...il.com> > and "Rafael J. Wysocki"<rjw@...k.pl> to reopen bug entry: > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15704 > > Subject : [r8169] WARNING: at net/sched/sch_generic.c > > Submitter : Sergey Senozhatsky<sergey.senozhatsky@...il.com> > > Date : 2010-03-31 10:21 (124 days old) > > Message-ID :<20100331102142.GA3294@...rdfish.minsk.epam.com> > > References : http://marc.info/?l=linux-kernel&m=127003090406108&w=2 > > > > as now we have hardware to reproduce this. > > Maintainers of r8169 are: > Francois Romieu<romieu@...zoreil.com> > "David S. Miller"<davem@...emloft.net> > Alexey Dobriyan<adobriyan@...il.com> > Jiri Pirko<jpirko@...hat.com> > netdev@...r.kernel.org > linux-kernel@...r.kernel.org > > So, please Cc them too. > > > > Thanks for your answer in advance, I hope to hear from you soon. > > > > Best regards > > Alexey Batyuk > > > > All the best, > > > Sergey > > > -- 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
Powered by blists - more mailing lists