Your message dated Fri, 28 May 2021 23:58:04 -0700 (PDT)
with message-id <60b1e5fc.1c69fb81.4661d.1...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #912085,
regarding linux-image-4.18.0-0.bpo.1-amd64: boot
Package: src:linux
Version: 4.18.6-1~bpo9+1
Severity: normal
Dear Maintainer,
on boot it displays:
[0.004000] do_IRQ: 1.55 No irq handler for vector
I tried several solutions found on the web mainly editing /etc/default/grub but
nothing works.
-- Package-specific info:
** Version:
Linux
faakin 'ell :) woo, ok. setting acpi_os_name="Windows 2009" and also
removing vesafb from /etc/initramfs-tools/modules resulted in a boot
(attaching dmesg boot which contains two ACPI-related kernel-level
warnings).
sorry it's an attachment rather than inline. i don't know if it was
the setting
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Wed, Feb 22, 2017 at 12:06 PM, Ben Hutchings wrote:
> Control: retitle -1 linux-image-4.9.0-1-amd64: Failed to execute /init
> Control: tag -1 moreinfo
>
> On Mon, 20 Feb 2017 04:00:03 +
http://www.linuxquestions.org/questions/linux-from-scratch-13/acpi-errors-when-booting-927408/
ah christ almighty, they're talking about "updating the bios fixes the
problem" *sigh*.
3.16, 4.7 and 4.8 are all fine - so wtf is 4.9 doing not being capable
of running /init when all prior version
Processing control commands:
> retitle -1 linux-image-4.9.0-1-amd64: Failed to execute /init
Bug #88 [src:linux] linux-image-4.9.0-1-amd64: ACPI boot error causes
/sbin/init to segfault (!)
Changed Bug title to 'linux-image-4.9.0-1-amd64: Failed to execute /init' from
'linux-image-4.9.
Control: retitle -1 linux-image-4.9.0-1-amd64: Failed to execute /init
Control: tag -1 moreinfo
On Mon, 20 Feb 2017 04:00:03 + lkcl wrote:
> Package: src:linux
> Version: 4.9.6-3
> Severity: important
> Tags: upstream
>
> this is a very recent (skylake) very expensive laptop
Package: src:linux
Version: 4.9.6-3
Severity: important
Tags: upstream
this is a very recent (skylake) very expensive laptop with an intel core i7
full report is here, with a link (at the bottom of the report) to
hardware info:
http://lkcl.net/reports/aorus_x3_plus_v6.html
it includes some
hi, i was getting to the prompt "NMI handler (perf_event_nmi_handler) took
too long to run" and my system was just freezing. i had a duel pci gpu
configuration with the single or duel gpu pci type of HW-card used as the
switch between each mode. i removed the second gpu and flipped the switch
back
On Thursday 28 March 2013 11:10 PM, Guy Roussin wrote:
Hi,
Thank you Ritesh,
I don't know how to test those packages. I try dpkg -i *deb
but multipath-tools refuse to upgrade because / is
multipathed ...
I can make some tests, my server is not a production server ...
Can you paste the
Hello,
I tried your packages without results :
LM05q:~/tmp# LANG=C dpkg -i *deb
(Reading database ... 31699 files and directories currently installed.)
Preparing to replace kpartx 0.4.9+git0.4dfdaf2b-7 (using
kpartx_0.4.9+git0.4dfdaf2b-7_amd64.deb) ...
Unpacking replacement kpartx ...
On Friday 29 March 2013 01:04 AM, Ritesh Raj Sarraf wrote:
Can you paste the logs when you hit the command?
The init script denies stopping the daemon since root in on multipath.
But I guess, your installation would have completed. Can you also paste
the output of dpkg -l | grep -i
Le 29/03/2013 08:20, Ritesh Raj Sarraf a écrit :
On Friday 29 March 2013 01:04 AM, Ritesh Raj Sarraf wrote:
Can you paste the logs when you hit the command?
The init script denies stopping the daemon since root in on multipath.
But I guess, your installation would have completed. Can you
On Friday 29 March 2013 01:46 PM, Guy Roussin wrote:
multipath-tools_0.4.9+git0.4dfdaf2b-7_amd64.deb) ...
[] Root is on a multipathed device, multipathd can not be
stopped:invoke-rc.d: initscript multipath-tools, action stop failed.
dpkg: warning: subprocess old pre-removal script returned
On Saturday 30 March 2013 01:13 AM, Ritesh Raj Sarraf wrote:
On Friday 29 March 2013 01:46 PM, Guy Roussin wrote:
multipath-tools_0.4.9+git0.4dfdaf2b-7_amd64.deb) ...
[] Root is on a multipathed device, multipathd can not be
stopped:invoke-rc.d: initscript multipath-tools, action stop
reassign 704073 multipath-tools-boot
thanks
* Ritesh Raj Sarraf [Thu Mar 28, 2013 at 10:58:20AM +0530]:
On Wednesday 27 March 2013 10:03 PM, Guy Roussin wrote:
I get this error when upgrading from squeeze to wheezy
on a boot on san (ibm ds4700)
update-initramfs: Generating
On Thursday 28 March 2013 04:08 PM, Michael Prokop wrote:
I can't see a reason why this would fail. I suspect it to be an
initramfs problem.
Looks like /usr/share/initramfs-tools/scripts/init-top/multipath is
missing the PREREQ/prereqs header (see e.g. initramfs-tools(8)), so
set this up (so
On 28/03/2013 16:55, Ritesh Raj Sarraf wrote:
On Thursday 28 March 2013 04:08 PM, Michael Prokop wrote:
I can't see a reason why this would fail. I suspect it to be an
initramfs problem.
Looks like /usr/share/initramfs-tools/scripts/init-top/multipath is
missing the PREREQ/prereqs header (see
On Thursday 28 March 2013 11:10 PM, Guy Roussin wrote:
Hi,
Thank you Ritesh,
I don't know how to test those packages. I try dpkg -i *deb
but multipath-tools refuse to upgrade because / is
multipathed ...
I can make some tests, my server is not a production server ...
Can you paste the
Your message dated Fri, 14 Aug 2009 00:33:09 +0200
with message-id 20090813223309.ga14...@galadriel.inutil.org
and subject line Re: Kernel boot error on a SUN Netra T4 server
has caused the Debian Bug report #438926,
regarding Kernel boot error on a SUN Netra T4 server
to be marked as done
On Mon, Aug 20, 2007 at 07:44:09PM +0100, Mário Santiago Batista wrote:
Package: kernel-image sparc
Version: 2.6.18
I downloaded the lastest net-install SPARC ISO CD (etch) and trying to boot
from CD I get the error Illegal Instruction.
Outputs
Package: kernel-image sparc
Version: 2.6.18
I downloaded the lastest net-install SPARC ISO CD (etch) and trying to boot
from CD I get the error Illegal Instruction.
Outputs
###
{0} ok boot cdrom
Boot device:
Hi,
i've got an error (maybe a warning) during the boot up process, as
written in /var/log/boot:
Cleaning /tmpfind: warning: you have specified the -maxdepth option
after a non-option argument -perm, but options are not positi
onal (-maxdepth affects tests specified before it as well as
23 matches
Mail list logo