From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on sa.local.altlinux.org X-Spam-Level: * X-Spam-Status: No, score=1.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM, FUZZY_XPILL autolearn=no autolearn_force=no version=3.4.1 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru; s=mail2; h=In-Reply-To:Content-Transfer-Encoding:Content-Type:Mime-Version:References:Message-ID:Subject:To:From:Date; bh=iVxYrh7fKg51BokCoKTFMqTnBbdTKRjw/84a/mdy4Qo=; b=q9A3FRANst2lRB8+eETR8g1zvl9xQdAqGWUhU73HmSVeyKXQz40rxLkcFCIyAwmZrYPXf5M82b3BOxa1SBOk0fWKsvOoPbl8cee4GHzTEHkvxuTYvzk4sghXbZh+oj+1Ir24rwkC1mgqqk6L14Tmdelutlq0CntkOuct8SmeI7c=; Date: Sat, 21 Jan 2017 12:26:59 +0300 From: "Vasiliy D. Sevostyanov" To: ALT Linux Community general discussions Message-ID: <20170121092659.GA6590@a1bd44.localdomain> Mail-Followup-To: ALT Linux Community general discussions References: <40cd2640-6163-dee9-18b0-db3b44886e79@myttk.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <81c14087-b18b-050d-d4be-10198111c831@myttk.ru> User-Agent: Mutt/1.4.2.3i X-Operating-System: ALTLinux 3.8.13.2-std-def-alt1.M70P.1 Authentication-Results: smtp27.mail.ru; auth=pass smtp.auth=dil8016@mail.ru smtp.mailfrom=dil8016@mail.ru X-E1FCDC63: 6B6AB7C0BD95A7B0FAA0C5B6AECF397C660823B2EEFD31DC X-E1FCDC64: ADC11E4640AA080A7187C708B392301C0B7DB3AF74893E47B1E3DA7F00A0DCE2 X-Mailru-Sender: DF683AD934B96842537DB3AA6335FB9832FED18ED8DBA51D33CE68E7638666A0066BA8855130448651CE0648C9E8651D X-Mras: OK Subject: Re: [Comm] =?koi8-r?b?NC40LjM5LXN0ZC1kZWYsINfZ28UgzsUg0sHCz9TBxdQ=?= X-BeenThere: community@lists.altlinux.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: ALT Linux Community general discussions List-Id: ALT Linux Community general discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jan 2017 09:27:38 -0000 Archived-At: List-Archive: List-Post: Hi, you wrote 10:39 Sat 21 Jan : На мой дилетантский взгляд, ничего криминального нет, если не считать того, что сам лог длительностью всего пара секунд и это явно не всё, остальное не сбросилось на диск и не сохранилось. Загрузитесь с предложенными выше параметрами, а именно сделайте: - в меню загрузки на выбранном пункте нажмите E; - найдите строку linux /boot/vmlinuz-4.4.43-std-def-alt0.M80P.2 root=UUID=130b49cf-59d6-4492-bd15-e71e153d2671 ro quiet resume=/dev/disk/by-uuid/a5ea076d-5658-452f-b65f-9382c03dd409 panic=30 splash - сотрите `quiet resume=/dev/disk/by-uuid/a5ea076d-5658-452f-b65f-9382c03dd409 panic=30 splash` - добавьте `panic=120 noapic acpi=off nomodeset` (без кавычек, естественно ;-) ) - после редактирования, не выходя оттуда, загрузите выбранное клавишей F10 или Ctrl+X. Спорные моменты (отметил для специалистов, не могу сказать, где норма/критика): --- line 188 kernel: PCI: MMCONFIG for 0000 [bus00-3f] at [mem 0xf0000000-0xf3ffffff] (base 0xf0000000) (size reduced!) --- line 190 kernel: mtrr: your CPUs had inconsistent variable MTRR settings kernel: mtrr: probably your BIOS does not setup all CPUs. kernel: mtrr: corrected configuration. --- line 242 kernel: pci 0000:00:1f.0: [8086:27b8] type 00 class 0x060100 kernel: pci 0000:00:1f.0: Force enabled HPET at 0xfed00000 kernel: pci 0000:00:1f.0: can't claim BAR 13 [io 0x0400-0x047f]: address conflict with ACPI CPU throttle [io 0x0410-0x0415] --- line 270 and 280 kernel: pci 0000:01:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force' --- line 112 kernel: Calgary: detecting Calgary via BIOS EBDA area kernel: Calgary: Unable to locate Rio Grande table in EBDA - bailing! --- line 203 kernel: acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM kernel: acpi PNP0A03:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge --- line 345 kernel: system 00:08: [mem 0x000f0000-0x000f7fff] could not be reserved kernel: system 00:08: [mem 0x000f8000-0x000fbfff] could not be reserved kernel: system 00:08: [mem 0x000fc000-0x000fffff] could not be reserved kernel: system 00:08: [mem 0x9fff0000-0x9fffffff] could not be reserved kernel: system 00:08: [mem 0x00000000-0x0009ffff] could not be reserved kernel: system 00:08: [mem 0x00100000-0x9ffeffff] could not be reserved kernel: system 00:08: [mem 0xfec00000-0xfec00fff] could not be reserved --- AppArmor отключен; статус SeLinux неясен (строка 176); присутствуют vbox*-драйвера. -- С уважением, Василий Д. Севостьянов.