ALT Linux Community general discussions
 help / color / mirror / Atom feed
From: Andrew Borodin <borodin@zarya-k.ru>
To: community@lists.altlinux.org
Subject: Re: [Comm] p8: 4.9.66-std-def: no network
Date: Thu, 7 Dec 2017 11:30:53 +0300
Message-ID: <20171207083052.GA4181@borodin.zk.lan> (raw)
In-Reply-To: <f2345220-1c0b-552e-f081-1c5f0c12bbe9@gmail.com>

On Thu, Dec 07, 2017 at 11:55:32AM +0500, Stas wrote:
> On 07.12.2017 11:36, Andrew Borodin wrote:
> > Вчера обновился до текущего p8. Пропала сеть.

> > Было ядро 4.9.62-std-def, была сеть. Установил ядро
> > 4.9.66-std-def, сети нет.

> > Я просто гружусь то с одним ядром, то с другим. При всех
> > прочих равных условиях со старым ядром сеть есть, с новым нет.
> > Не стартует dhcp-клиент.

> > В логах ничего криминального не вижу. За исключеним того,
> > что два устройства обменялись прерываниями:

> Покажите вывод `ip addr`,

.62

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 08:60:6e:eb:83:88 brd ff:ff:ff:ff:ff:ff
    inet 172.31.1.22/25 brd 172.31.1.127 scope global eno1
       valid_lft forever preferred_lft forever

.66

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state
UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 08:60:6e:eb:83:88 brd ff:ff:ff:ff:ff:ff

То же самое, только адрес не получили, так как не стартует
dhcp-клиент, как я уже писал.

Вот лог от .62 (вчерашний, но не суть:):

Dec  6 16:01:44 borodin network: Computing interface groups:
Dec  6 16:01:44 borodin network: .
Dec  6 16:01:44 borodin network: .
Dec  6 16:01:44 borodin network:  2 interfaces found
Dec  6 16:01:44 borodin network: Starting group 0/virtual (1 interfaces)
Dec  6 16:01:44 borodin network: ^IStarting lo:
Dec  6 16:01:44 borodin network: .
Dec  6 16:01:44 borodin last message repeated 3 times
Dec  6 16:01:44 borodin network: OK
Dec  6 16:01:44 borodin network: Starting group 1/realphys (1 interfaces)
Dec  6 16:01:44 borodin network: ^IStarting eno1:
Dec  6 16:01:44 borodin network: .
Dec  6 16:01:44 borodin last message repeated 2 times
Dec  6 16:01:44 borodin network: ?
Dec  6 16:01:44 borodin smartd: smartd startup succeeded
Dec  6 16:01:44 borodin network: ?
Dec  6 16:01:44 borodin network: ?
Dec  6 16:01:44 borodin network: .
Dec  6 16:01:44 borodin dhcpcd[1384]: eno1: soliciting a DHCP lease
Dec  6 16:01:44 borodin dhcpcd[1384]: eno1: offered 172.31.1.22 from 172.31.1.1
Dec  6 16:01:44 borodin dhcpcd[1384]: eno1: leased 172.31.1.22 for 86400 seconds
Dec  6 16:01:44 borodin dhcpcd[1384]: eno1: adding route to 172.31.1.0/25
Dec  6 16:01:44 borodin dhcpcd[1384]: eno1: adding default route via 172.31.1.126
Dec  6 16:01:44 borodin dhcpcd[1384]: forked to background, child pid 1571
Dec  6 16:01:44 borodin network: .
Dec  6 16:01:44 borodin network: .
Dec  6 16:01:44 borodin network: OK
Dec  6 16:01:44 borodin network: Processing /etc/net/vlantab:
Dec  6 16:01:44 borodin network: empty.
Dec  6 16:01:44 borodin rc: Starting network: succeeded


А вот от .66:

Dec  6 16:04:16 borodin network: Computing interface groups:
Dec  6 16:04:16 borodin network: .
Dec  6 16:04:16 borodin network: .
Dec  6 16:04:16 borodin network:  2 interfaces found
Dec  6 16:04:16 borodin network: Starting group 0/virtual (1 interfaces)
Dec  6 16:04:16 borodin network: ^IStarting lo:
Dec  6 16:04:16 borodin network: .
Dec  6 16:04:16 borodin last message repeated 3 times
Dec  6 16:04:16 borodin network: OK
Dec  6 16:04:16 borodin network: Starting group 1/realphys (1 interfaces)
Dec  6 16:04:16 borodin network: ^IStarting eno1:
Dec  6 16:04:16 borodin network: .
Dec  6 16:04:16 borodin last message repeated 2 times
Dec  6 16:04:16 borodin network: ?
Dec  6 16:04:16 borodin last message repeated 4 times
Dec  6 16:04:16 borodin network: !
Dec  6 16:04:16 borodin network: .
Dec  6 16:04:16 borodin network: OK
Dec  6 16:04:16 borodin network: Processing /etc/net/vlantab:
Dec  6 16:04:16 borodin network: empty.
Dec  6 16:04:16 borodin rc: Starting network: succeeded


>`iptables-save`

iptables не используется, сервис выключен.

> а если есть мосты - и `brctl> show`

Нету.

--

С уважением
А. Бородин.


  reply	other threads:[~2017-12-07  8:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-07  6:36 Andrew Borodin
2017-12-07  6:55 ` Stas
2017-12-07  8:30   ` Andrew Borodin [this message]
2017-12-07 20:27     ` Mikhail Efremov
2017-12-08  7:56       ` Andrew Borodin
2017-12-09 10:32           ` Andrey Borodin
2017-12-11  9:58             ` Andrew Borodin
2017-12-07  8:32   ` Andrew Borodin
2017-12-07 11:57         ` Вадим Илларионов
2017-12-10 11:31     ` Sergey
2017-12-07 11:00 ` Michael Shigorin
2017-12-08 10:51   ` Andrew Borodin
2017-12-07 11:12 ` Andrew Borodin
2017-12-07 11:50   ` Alexei Takaseev
2017-12-07 13:48     ` Andrew Borodin
2017-12-07 15:32       ` Peter Evdokimov

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=20171207083052.GA4181@borodin.zk.lan \
    --to=borodin@zarya-k.ru \
    --cc=community@lists.altlinux.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

ALT Linux Community general discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/community/0 community/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 community community/ http://lore.altlinux.org/community \
		mandrake-russian@linuxteam.iplabs.ru community@lists.altlinux.org community@lists.altlinux.ru community@lists.altlinux.com
	public-inbox-index community

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.community


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git