linux-kernel - Re: [PATCH -rt DO NOT APPLY] Fix for tg3 networking lockup

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <1154649785.16126.3.camel@dwalker1.mvista.com>
Date:	Thu, 03 Aug 2006 17:03:05 -0700
From:	Daniel Walker <dwalker@...sta.com>
To:	David Miller <davem@...emloft.net>
Cc:	tytso@....edu, mchan@...adcom.com, herbert@...dor.apana.org.au,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH -rt DO NOT APPLY] Fix for tg3 networking lockup

On Thu, 2006-08-03 at 16:56 -0700, David Miller wrote:
> From: Theodore Tso <tytso@....edu>
> Date: Thu, 3 Aug 2006 19:53:26 -0400
> 
> > Any suggestions on how I could figure out what was really going on and
> > what would be a better fix would be greatly appreciated.
> 
> As Michael explained, it's the ASF heartbeat sent by tg3_timer() that
> must be delivered to the chip within certain timing constraints.
> 
> If you had any watchdog devices on this machine, they would likely
> trigger too and reset your machine :)

That's not broken behavior in RT .. That's just plain old task
priorities. Some high priority task (SCHED_FIFO prio 99) is sucking up a
lot of the CPU. But that's 100% legal in SCHED_FIFO.

Daniel

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