:: Re: [DNG] Who remembers rootkit..
トップ ページ
このメッセージを削除
このメッセージに返信
著者: Jimmy Johnson
日付:  
To: dng
題目: Re: [DNG] Who remembers rootkit..
On 10/23/18 11:27 AM, Bastiaan van den Berg wrote:
> Is there any log of the actual issue?
>
> --
> buZz



I made a post with the log last night, but it's now missing, gone,
caput, not even in my sent folder or my draft folder..

Here's the log:
[ 213.706282] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 213.994776] e1000e: eth0 NIC Link is Down
[ 214.238328] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 215.912089] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow
Control: Rx/Tx
[ 215.912095] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
[ 215.912130] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
GLib-CRITICAL: Source ID 123 was not found when attempting to remove it
------------------------------------------------------------------------

What you see is I have brought eth0 down, when it gets to disabling TSO
is where the kernel has now bound its self to the kernel via the intel
driver e1000e and is trying to get HTTP, my system is using a
controversial driver e1000e and it's been pointed out by both Linus and
lwn.net where they prefer using the older e1000 but your redhat system
will choose the e1000e over the e1000. I see the whole redhat system as
being controversial myself, and people you think are trying to help, are
just seeking info to make things more obscure, they don't want you to
see this kind of stuff or people to talk about this kind of stuff.
--
Jimmy Johnson

Slackware64 Current - KDE 4.14.38 - AMD A8-7600 - EXT4 at sda9
Registered Linux User #380263