; > system fails with kernel panics
> >
> > By adding init=/bin/bash from within grub works and we can then do
> things
> > like
> >
> > mount - o remount /
> > cd /etc/init.d
> > ./networking start
> > ./ssh start
> > apt install stress
> Our servers were running Debian 10 without any issues
> We have been trying to do a fresh install of debian 11.3 on exactly the
> same hardware. The install works without any errors but on rebooting the
> system fails with kernel panics
>
> By adding init=/bin/bash from wit
Hi
Our servers were running Debian 10 without any issues
We have been trying to do a fresh install of debian 11.3 on exactly the
same hardware. The install works without any errors but on rebooting the
system fails with kernel panics
By adding init=/bin/bash from within grub works and we can
On Ma, 08 iun 21, 12:05:21, Thom Castermans wrote:
>
> - Installed non-free firmware (used the unofficial image [1]) during
> installation and installed the intel-microcode package after installation
> in an attempt to fix the error displayed in [4] ("[Firmware Bug]:
> TSC_DEADLINE d
for that additional pointer!
[Reco wrote:]
> I'd like to suggest a different approach, considering we're dealing with
> kernel panics here. (snip) They've invented kdump (snip) with exact
> purpose of capturing kernel panics and storing kernel crash dumps in a
> persistent w
is problem is by making boot logs
> persistent [1] so they could be searched for clues (kernel module
> name, device hint, etc) after each boot.
I'd like to suggest a different approach, considering we're dealing with
kernel panics here.
journald is merely a userspace program, so i
On Tue, Jun 08, 2021 at 04:44:35PM +0500, Alexander V. Makartsev wrote:
> There was an intention from a systemd developers to make persistent logs the
> default, but I'm unsure if that change made it into Debian already.
Unless something changed that I'm unaware of, new installs of bullseye
should
On Tue, Jun 08, 2021 at 07:43:30AM -0400, The Wanderer wrote:
> On 2021-06-08 at 07:27, Greg Wooledge wrote:
> > The first and most obvious thing you should try is booting the buster
> > kernel, and seeing whether the problem still occurs. This will let
> > you know whether the problem is in the k
On 08.06.2021 15:05, Thom Castermans wrote:
Dear Debian users,
Recently I installed Debian on an ASUS UX501J laptop. Debian stable (Buster)
works flawlessly (I'm using that now), but when I tried to upgrade to testing,
things started going wrong. I would get random kernel panics and
On 2021-06-08 at 07:27, Greg Wooledge wrote:
> On Tue, Jun 08, 2021 at 12:05:21PM +0200, Thom Castermans wrote:
>
>> How can I debug this problem? My suspicion is that this has to do with the
>> kernel upgrade between stable and testing (4.19 to 5.10), but I'm not sure.
>>
>> Things I have tried
On Tue, Jun 08, 2021 at 12:05:21PM +0200, Thom Castermans wrote:
> How can I debug this problem? My suspicion is that this has to do with the
> kernel upgrade between stable and testing (4.19 to 5.10), but I'm not sure.
>
> Things I have tried so far:
> - Ran smartctl test on the SSD: no issues
Dear Debian users,
Recently I installed Debian on an ASUS UX501J laptop. Debian stable (Buster)
works flawlessly (I'm using that now), but when I tried to upgrade to testing,
things started going wrong. I would get random kernel panics and other errors
on boot. Thinking I may have done some
On 06/23/2017 08:00 AM, Ron Benincasa wrote:
Colleagues,
I can't figure out what I've done wrong. I did a fresh install of
Stretch, with backports enabled, and Gnome desktop, using the
default kernel as highlighted. When I reboot, I get a kernel panic.
I can SOMETIMES boot in by entering reco
Colleagues,
I can't figure out what I've done wrong. I did a fresh install of
Stretch, with backports enabled, and Gnome desktop, using the
default kernel as highlighted. When I reboot, I get a kernel panic.
I can SOMETIMES boot in by entering recovery mode. I also have
Jessie and Wheezy instal
On Sun, Feb 02, 2014 at 02:23:38PM -0700, Rick Macdonald wrote:
> read-only without rebooting. I was seeing journal errors (ext3
> filesystem). Then I saw a BIOS message saying a hard drive failure
> was imminent.
>
Had a hard drive with many bad blocks on it, and run debian(Woody IIRC)
on it as
I finally updated my 32bit PC to wheezy in October. Shortly after, I
started getting kernel panics (blinking CapsLock/Scroll Lock for about
10 seconds, then it would re-boot itself).
I ran memtest for 14 hours; no errors.
It often happened while watching videos in iceweasel, especially when
On 16/09/2013 13:15, Dr. Jennifer Nussbaum wrote:
> Of course the computer hasnt crashed for the last four days now. I
> did run some of the tests suggested, and everything checks out OK.
>
> Theres no new hardware in the system, no new accessories. ... I dont
> think that I installed any new s
on this; it
isnt a super powerful box anyway.
Jen
>
> From: Erick Ocrospoma
>To: Marko Randjelovic
>Cc: debian-user@lists.debian.org
>Sent: Thursday, September 12, 2013 5:07 PM
>Subject: Re: Frequent kernel panics
>
>
>Hi,
>
&
On Thursday 12 September 2013 10:23:15 Dr. Jennifer Nussbaum wrote:
> I did look in both places and did not see the crash report there. Also
> looked at /var/log/messages--same thing, no crashes shown there.
>
> Jen
http://www.av8n.com/computer/htm/kernel-lockup.htm
especially point 3:
"3[1].
Im running an up-to-date Wheezy on a newish desktop box. In the past the
machine would crash with apparent kernel panics on occasion, but in the last
week or 2 the machine is crashing almost every day. Ill step back to it and
there will be a crash screen with a timestamp log beginning "cut
Hi all,
Normally you could find it in
/var/log/syslog and in /var/log/kern.log
Regards,
Le 12/09/2013 13:49, Dr. Jennifer Nussbaum a écrit :
Im running an up-to-date Wheezy on a newish desktop box. In the past
the machine would crash with apparent kernel panics on occasion, but
in the last week
Hi,
I would suggest at first doing a fsck on your HDD, then testing RAM
(with memtest maybe or using another RAM), as almost everybody said,
this is due to hardware problems.
~ Happy install !
Cellphone : +51 950307809
Blog : http://piobox.blogspot.com/
LUG : http://www.utpinux.o
Eike Lantzsch wrote:
> If it is always the same error (there you need to have a look into
> the log) it might be a recently installed driver or firmware. The
> log may give you an idea which one.
> Do you use binary blobs like video drivers?
> Has there been a recent update?
> Any new hardware in
On Thursday 12 September 2013 09:49:07 Dr. Jennifer Nussbaum wrote:
> Im running an up-to-date Wheezy on a newish desktop box. In the past the
> machine would crash with apparent kernel panics on occasion, but in the
> last week or 2 the machine is crashing almost every day. Ill step bac
12, 2013 12:55 PM
>Subject: Re: Frequent kernel panics
>
>
>
>Hi all,
>Normally you could find it in
>/var/log/syslog and in /var/log/kern.log
>Regards,
>Le 12/09/2013 13:49, Dr. Jennifer Nussbaum a écrit :
>
>Im running an up-to-date Wheezy on a newish desktop bo
On Mon, Apr 30, 2007 at 06:41:55PM +0100, steve downes wrote:
> On Mon, 30 Apr 2007 19:21:46 +0200
> David Jardine <[EMAIL PROTECTED]> wrote:
>
> > > > > kernel /vmlinux root=dev/hda2 ro
> > ^
> > Oops, missed that one! Another typo? Should be vmlinuz.
> >
>
On Mon, 30 Apr 2007 19:21:46 +0200
David Jardine <[EMAIL PROTECTED]> wrote:
> > > > kernel/vmlinux root=dev/hda2 ro
> ^
> Oops, missed that one! Another typo? Should be vmlinuz.
>
I refer you to the answer I gave earlier (UK parlimentary joke)
Steve
(off for a
On Mon, Apr 30, 2007 at 05:25:33PM +0100, steve downes wrote:
> On Mon, 30 Apr 2007 18:10:02 +0200
> David Jardine <[EMAIL PROTECTED]> wrote:
>
> Sorry, yes menu.lst is correct, the typo was in the email
>
> Steve
>
> > >
> > > root(hd0,0)
> > > kernel /vmlinux root=dev/hda2 ro
On Mon, 30 Apr 2007 15:38:28 +0100
Wackojacko <[EMAIL PROTECTED]> wrote:
> >
> > Can anybody suggest anything else - PLEASE
> >
> > Steve
> >
> >
>
> Have you compiled the driver for your motherboard IDE/SATA controller
> into the kernel. If its a module and no initrd then grub will not be
On Mon, 30 Apr 2007 18:10:02 +0200
David Jardine <[EMAIL PROTECTED]> wrote:
Sorry, yes menu.lst is correct, the typo was in the email
Steve
> >
> > root (hd0,0)
> > kernel/vmlinux root=dev/hda2 ro
>
> That should be root=/dev/hda2
> ^
> > [...]
>
--
On Mon, Apr 30, 2007 at 12:36:40PM +0100, steve downes wrote:
> Just compiled my 1st kernel.
>
> Using sources from 2.6.18-4 (same as present kernel to keep it
> simple)
>
> Compiled ext3 & ext2 into the kernel (not as modules)
>
> installed kernel & modules
>
> installed into grub
>
>
steve downes wrote:
Just compiled my 1st kernel.
Using sources from 2.6.18-4 (same as present kernel to keep it
simple)
Compiled ext3 & ext2 into the kernel (not as modules)
installed kernel & modules
installed into grub
root (hd0,0)
kernel /vmlinux root=dev/hda2 ro
noinitrd
steve downes wrote:
Just compiled my 1st kernel.
Using sources from 2.6.18-4 (same as present kernel to keep it
simple)
Compiled ext3 & ext2 into the kernel (not as modules)
installed kernel & modules
installed into grub
root (hd0,0)
kernel /vmlinux root=dev/hda2 ro
noinitrd
Just compiled my 1st kernel.
Using sources from 2.6.18-4 (same as present kernel to keep it
simple)
Compiled ext3 & ext2 into the kernel (not as modules)
installed kernel & modules
installed into grub
root (hd0,0)
kernel/vmlinux root=dev/hda2 ro
noinitrd
save default
The sto
Hello,
I'm running debian unstable with the 2.4.27-2-k7 kernel image. I'm
trying to upgrade to 2.6.12-3-multimedia-k7, which is a kernel image
from an AGNULA/DeMuDi apt source. After apt-getting and rebooting, it
fails att bootup. I get the following message:
ide0 at 0x1f0-0x1f7,0x3f6 on irq
On 21:56 Sun 06 Nov , Hendrik Sattler wrote:
> David Baron wrote:
>
> > On Sunday 06 November 2005 19:32,
> > [EMAIL PROTECTED] wrote:
> >> Thats because devfs is creating the nodes in kernels < 2.6.14.
> >> With 2.6.14 DEVFS is no longer supported in the kernel, so you have
> >> to use anothe
David Baron wrote:
> On Sunday 06 November 2005 19:32,
> [EMAIL PROTECTED] wrote:
>> Thats because devfs is creating the nodes in kernels < 2.6.14.
>> With 2.6.14 DEVFS is no longer supported in the kernel, so you have
>> to use another method to create device nodes like udev (the new way)
>> or M
On Sunday 06 November 2005 19:32, [EMAIL PROTECTED]
wrote:
> Thats because devfs is creating the nodes in kernels < 2.6.14.
> With 2.6.14 DEVFS is no longer supported in the kernel, so you have
> to use another method to create device nodes like udev (the new way)
> or MAKEDEV( the old way, before
On 15:41 Sun 06 Nov , Alex Teclo wrote:
> >> Here is the entry in /boot/grub/menu.lst on machine A:
> >> title Debian GNU/Linux, kernel 2.6.14
> >> root (hd0,4)
> >> kernel/vmlinuz-2.6.14 root=/dev/ataraid/d0p7 ro
> >> initrd /initrd.img-2.6.14
> >> savedefa
>> Here is the entry in /boot/grub/menu.lst on machine A:
>> title Debian GNU/Linux, kernel 2.6.14
>> root (hd0,4)
>> kernel/vmlinuz-2.6.14 root=/dev/ataraid/d0p7 ro
>> initrd /initrd.img-2.6.14
>> savedefault
>> boot
>>
>> But, when I boot machine A with this 2
On Sat, Nov 05, 2005 at 11:43:06PM +0100, Alex Teclo wrote:
> I am having problems with a 2.6.14 kernel.
[snip]
Probably not relevant, but is the typo only in the mail or in the actual
menu.lst file as well?
> Here is the entry in /boot/grub/menu.lst on machine A:
> title Debian GNU/Li
On 23:43 Sat 05 Nov , Alex Teclo wrote:
> I am having problems with a 2.6.14 kernel.
>
><><><><><><><><>
> Here is the entry in /boot/grub/menu.lst on machine A:
> title Debian GNU/Linux, kernel 2.6.14
> root (hd0,4)
> kernel/vmlinuz- 2.6.14 root=/dev/ataraid/d0p7
I am having problems with a 2.6.14 kernel.
I have two x86 machines, A and B. They do not have identical hardware.
Machine A is running Debian woody with a 2.4.28 kernel. There is
nothing on machine B at this point.
I did a tar -zcvf of everything on machine A, then I did tar -zxvf of
that tar fil
Marty wrote:
> It's a udev quirl. You need the device file console in /dev. I usually
copy
> the device manually after cloning a disk.
=BEGIN SNIPPET=
# ls -l /dev/console
crw--- 1 root tty 5, 1 Aug 18 09:32 /dev/console
# echo 'testing write' >/dev/console
testing write
# cat -
Joel Barker wrote:
I have been using two hard drives, an old IDE mounted at / and a brand new
SCSI mounted on /home. A few days ago the IDE drive died. Fortunately, I had
just copied all the data over to the SCSI drive (/dev/sda1). But when I try
to boot off the SCSI drive, I get the following
I have been using two hard drives, an old IDE mounted at / and a brand new
SCSI mounted on /home. A few days ago the IDE drive died. Fortunately, I had
just copied all the data over to the SCSI drive (/dev/sda1). But when I try
to boot off the SCSI drive, I get the following messags:
Freeing un
RIVER,
Rev 6.2.36
aic7899: Ultra160 Wide Channel B, SCSI Id=7,
32/253 SCBs
scsi2 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER,
Rev 6.2.36
aic7892: Ultra160 Wide Channel A, SCSI Id=7,
32/253 SCBs
other people have reported random lockups/kernel
panics. anyway,
On Thu, Feb 26, 2004 at 12:19:52PM +1100, Campbell McLeay wrote:
>
> I am not really sure who to mail regarding this error.
You might want to report a bug, including the kernel panic exact text,
to the kernel package you are running. Probably kernel-image-Something.
--
"If you have an apple
Hi,
We have an unusual problem whereby machines will lockup
with a kernel panic when reading/writing to scsi a hard
drive. This doesn't happen very often, but as the servers
are production machines which need close to 100% uptime,
it is of significant concern. So far, it has happened on
three sep
hi all,
as i said in a previous message, one of my machines continuously
kernel panics. i am thinking this has to do with swapping, but the
swap partition is 100% bad-block free, so i am at a loss.
nevertheless, i would like to detect such a kernel panic.
is it somehow possible to save the
hey all,
my local network is attached to the internet via a 486DX-2/66
(currently only 8Mb of RAM but i am looking for more). only recently
does this machine crash a whole lot, and it's always pid 0, the
"process swapper" which appears in the kernel panic message.
my initial thoughts were bad bloc
A long time ago, in a galaxy far, far way, someone said...
> On Wed, Jan 26, 2000 at 10:55:22PM -0600, Phil Brutsche wrote:
> > 1) Upgrade from hamm to potato (you might need to go to slink first). The
> >bug fixes along are worth it.
>
> Could I use apt to do this? Is there somewhere a howt
I had some odd behavior after installing a 2.2.x kernel on my slink machine.
I investigated installing the potato packages that were recommended for the
new kernel version, but decided that a the benefits of the 2.2.x kernels over
2.0.x kernels were not worth the trouble. As to upgrading that
On Thu, 27 Jan 2000, Werner Reisberger wrote:
> [...]
>
> I tried to compile 2.2.14 but it failed with many error messages in
> console.c. Isn't it possible to run hamm with newer kernels. Last time
> I read on this list Debian is kernel independent (someone asked why his
> potato uses a 2.0.39 k
On Wed, Jan 26, 2000 at 10:55:22PM -0600, Phil Brutsche wrote:
> 1) Upgrade from hamm to potato (you might need to go to slink first). The
>bug fixes along are worth it.
Could I use apt to do this? Is there somewhere a howto for doing this?
> 2) Use a newer kernel. 2.2.9 is about 6 months o
A long time ago, in a galaxy far, far way, someone said...
> My system crashes from time to time but I cannot reproduce the crashes.
> It may run 2 month without any problems and suddenly a daily cronjob or a
> simple shell command seems to cause the crash. Here is what I could write
> today from
My system crashes from time to time but I cannot reproduce the crashes.
It may run 2 month without any problems and suddenly a daily cronjob or a
simple shell command seems to cause the crash. Here is what I could write
today from the system console:
Code: 39 73 70 75 22 c7 43 4c 11 00 a1 3
Peter Ludwig wrote:
> I myself have an Adaptec 1542CF and I have started to receive
> problematic errors with the card. After seeing this message, I'm
> tempted to get another card from somewhere and try that out.
>
> I have looked at adaptec's website in regards to this card (about a
year
> ago
talling a Granite Digital active terminator on the end of the SCSI
> chain
> - verifying that there are no interrupt or IO port confilicts both in the
> device jumper configurations and from the /proc filesystem
>
> I am completely at my wits end with this. I have searched Dej
On Thu, 23 Dec 1999, aphro wrote:
> Does it always happen when you run iptraf? it could be a network driver
> problem or a network card hardware problem.
Nope... The machine can just be sitting there lying "idle" (as idle as a
linux box should get that is...)
> a good way to test the board/cpu/
IIRC there have been changes to the
aha1542 driver since 2.2.11 - current is 2.2.13.
> I am completely at my wits end with this. I have searched DejaNews
> repeatedly for any discussions of kernel panics and crashes with
> Adaptec cards, Linux, SCSI in general, etc., and all I can find is one
completely at my wits end with this. I have searched DejaNews
repeatedly for any discussions of kernel panics and crashes with Adaptec
cards, Linux, SCSI in general, etc., and all I can find is one thread
from about a year ago mentioning the same sorts of problems but no
solution.
Is this a problem that
Does it always happen when you run iptraf? it could be a network driver
problem or a network card hardware problem.
a good way to test the board/cpu/hdd and i/o subsystems that i have found
is running 10x copies of [EMAIL PROTECTED] at the same time for 24-48 hours, if
the machine lasts 24 hours
Just a quick note, I'm starting to wonder about my hardware. For the last
few months (since I reloaded the system back to running slink in fact), I
have been receiving errors similar to the following message :-
Dec 24 00:09:31 midnight kernel: Oops:
Dec 24 00:09:31 midnight kernel: CPU:0
Dear all,
On one of the machines here, which is more or less a clone of other
linux machines, I keep getting kernel panics at times of low activity
(e.g. 6 in the morning). The /var/log/messages file contains lines
like:
Apr 24 08:23:00 bobbin kernel: general protection:
Apr 24 08:23:00
> Saturday night, while I was testing my tape backup procedure, I did a full
> restore into an unused partition. I tried an rm -r on that partition, and
> got a kernel panic, locking my system. Happened again later that night.
>
> Earlier today, while demonstrating the slowness and cpu usage of
Hello all.
Saturday night, while I was testing my tape backup procedure, I did a full
restore into an unused partition. I tried an rm -r on that partition, and
got a kernel panic, locking my system. Happened again later that night.
Earlier today, while demonstrating the slowness and cpu usage
67 matches
Mail list logo
