home  bbs  files  messages ]

      ZZLI4424             linux.debian.kernel             1332 messages      

[ previous | next | reply ]

[ list messages | list forums ]

  Msg # 182 of 1332 on ZZLI4424, Monday 9-14-25, 1:08  
  From: DEBIAN BUG TRACKING SYSTE  
  To: SALVATORE BONACCORSO  
  Subj: Bug#1100895: marked as done (nouveau pro  
 From: owner@bugs.debian.org 
  
 This is a multi-part message in MIME format... 
  
 Your message dated Sat, 13 Sep 2025 22:53:00 +0200 
 with message-id  
 and subject line Re: Bug#1100895: Boot logs from versions 6.1.0-27-amd64 
 (booting), 6.1.0-28-amd64 (failing) and 6.1.0-32-amd64 (failing) 
 has caused the Debian Bug report #1100895, 
 regarding nouveau probe of GeForce 840M crashes since 6.1.119-1 
 to be marked as done. 
  
 This means that you claim that the problem has been dealt with. 
 If this is not the case it is now your responsibility to reopen the 
 Bug report if necessary, and/or fix the problem forthwith. 
  
 (NB: If you are a system administrator and have no idea what this 
 message is talking about, this may indicate a serious mail system 
 misconfiguration somewhere. Please contact owner@bugs.debian.org 
 immediately.) 
  
  
 -- 
 1100895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100895 
 Debian Bug Tracking System 
 Contact owner@bugs.debian.org with problems 
  
 Received: (at submit) by bugs.debian.org; 20 Mar 2025 08:35:33 +0000 
 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02 
  (2021-04-09) on buxtehude.debian.org 
 X-Spam-Level: 
 X-Spam-Status: No, score=-17.4 required=4.0 tests=BAYES_00, 
  BODY_INCLUDES_PACKAGE,FOURLA,HAS_PACKAGE,RDNS_NONE,SPF_SOFTFAIL, 
  XMAILER_REPORTBUG autolearn=ham autolearn_force=no 
  version=3.4.6-bugs.debian.org_2005_01_02 
 X-Spam-Bayes: score:0.0000 Tokens: new, 72; hammy, 150; neutral, 575; 
 spammy, 
  0. spammytokens: hammytokens:0.000-+--XDebbugsCc, 
  0.000-+--X-Debbugs-Cc, 0.000-+--H*x:12.0.0, 0.000-+--H*UA:12.0.0, 
  0.000-+--stablesecurity 
 Return-path:  
 Received: from [2001:a61:115f:e501:d0a9:a6a4:4a7d:d17e] (port=54906 
 helo=[127.0.1.1]) 
  by buxtehude.debian.org with esmtp (Exim 4.94.2) 
  (envelope-from ) 
  id 1tvBNE-00D2Yh-6P 
  for submit@bugs.debian.org; Thu, 20 Mar 2025 08:35:33 +0000 
 Content-Type: text/plain; charset="us-ascii" 
 MIME-Version: 1.0 
 Content-Transfer-Encoding: 7bit 
 From: zebonaut  
 To: Debian Bug Tracking System  
 Subject: linux-image-6.1.0-32-amd64: Failed to start systemd-jou 
 nald.service/start, timeout, repeatedly killed, no boot possible 
 Message-ID: <174245973002.7080.9559106582987145640.reportbug@aspire> 
 X-Mailer: reportbug 12.0.0 
 Date: Thu, 20 Mar 2025 09:35:30 +0100 
 Delivered-To: submit@bugs.debian.org 
  
 Package: src:linux 
 Version: 6.1.129-1 
 Severity: normal 
 X-Debbugs-Cc: zb-public@mnet-online.de 
  
 Dear Maintainer, 
  
 after a fresh installation from a netinst usb flash drive, version 
 debian-12.5.0-amd64-netinst.iso, 
 the system did not boot because it went into a loop that repeatedly failed 
 to 
 start job 
 systemd-journald.service. 
  
 I managed to eventually boot the system by telling grub not to boot using 
 linux-image-6.1.0-32-amd64 (default) but 
 linux-image-6.1.0-18-amd64 (chosen manually), 
 which was the second choice still available in grub's start-up menu. 
  
 I am aware that the kernel may not be the package that is the actual root 
 cause. However, I chose 
 linux-image-6.1.0-32-amd64 as the affected package because choosing an older 
 version made the 
 problem disappear. 
  
 I believe this "fix" was available because my netinst iso was already a bit 
 older and during the 
 installation, a newer kernel version was installed and used as a default by 
 grub. 
  
 When re-installing from a new netinst image (debian-12.10.0-amd64-netinst. 
 iso), 
 linux-image-6.1.0-32-amd64 was the only option available to grub, and I 
 could 
 not use 
 an alternative version to start the system. 
  
 This was displayed during the boot process: 
  
 [  *** ] Job systemd-journald.service/start running (1min 19s / 1min 19s) 
 [  *** ] Job systemd-journald.service/start running (2min 49s / 2min 49s) 
 [  189.455547] systemd [1]: systemd-journald.service: State 'stop-sigterm' 
 timed out. Killing. 
  
 This continued in a loop-like fashion until it repeatedly [FAILED]: 
  
 [FAILED] Failed to start systemd-journald.service/start - Journal Service. 
  
 -- Package-specific info: 
 Other than the messages above, I was not able to find any output that 
 appeared 
 to be relevant. 
  
  
 ** Model information 
 sys_vendor: Acer 
 product_name: Aspire E5-771G 
 product_version: TBD by OEM 
 chassis_vendor: Chassis Manufacturer 
 chassis_version: Chassis Version 
 bios_vendor: Insyde Corp. 
 bios_version: V1.09 
 board_vendor: Acer 
 board_name: EA70_HB 
 board_version: Type2 - A01 Board Version 
  
 ** PCI devices: 
 00:00.0 Host bridge [0600]: Intel Corporation Haswell-ULT DRAM Controller 
 [8086:0a04] (rev 0b) 
  Subsystem: Acer Incorporated [ALI] Haswell-ULT DRAM Controller [1025:0882] 
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
 Stepping- 
 SERR- FastB2B- DisINTx- 
  Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  
  Kernel driver in use: hsw_uncore 
  
 00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT 
 Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA 
 controller]) 
  Subsystem: Acer Incorporated [ALI] Haswell-ULT Integrated Graphics 
 Controller 
 [1025:0882] 
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
 Stepping- 
 SERR- FastB2B- DisINTx+ 
  Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

[ list messages | list forums | previous | next | reply ]

search for:

328,089 visits
(c) 1994,  bbs@darkrealms.ca