Re: Kernel panic....

[Van Snyder]

On Mon, 2024-07-08 at 17:46 +, Andrew M.A. Cater wrote:
> On Sun, Jul 07, 2024 at 07:07:26PM -0700, Van Snyder wrote:
> > I recently installed Debian 12.5 with kernel 6.5.0.0 on an antique
> > Dell
> > Vostro 1700. Occasionally it crashes with
> > 
> > "Kernel Panic - not syncing: Can not allocate SWIOTLB buffer
> > earlier
> > and can't now provide you with the DMA bounce buffer"
> > 
> 
> Hi,
> 
> As suggested, use the Debian 6.1 kernel.
> 
> This is a laptop from around 2008 if I'm reading the spec. correctly.
> This is a laptop with an older Nvidia card. How did you install it?
> Did you try to install the Nvidia drivers at any point? I can't 
> find out whether this is one of the machines that has dual chipsets
> (one Intel / one Nvidia). If so, have you used the instructions
> for bumblebee/primus or whatever the appropriate magic now is?

I tried unsuccessfully to install the NVidia 340 driver from the NVidia
drivers page. I found a SourceForge/GitHub page by MeowIce that had the
patched driver, but not for kernel 6.1, so I installed 6.5.0.0 from
backports-bookworm and the patched NVidia 340 driver. That also didn't
work, so I reinstalled bog-standard Debian 12.5 with the 6.1 kernel
using the net-install ISO from the Debian site. It doesn't have dual
graphic chipsets. The video driver is nouveau.

> 
> > I saw some remarks about this from 2013 in the context of release
> > 3.5.
> > 
> > Is this a problem in the kernel, or is the computer broken?
> > 
> > Should I revert to an earlier release?
> > 
> > 
> 
> Ideally, if you're running Debian stable, don't revert to prior
> versions.
> 
> Apt-get update to ensure that you're running the latest point
> release.
> 
> All the very best, as ever,
> 
> Andy
> (amaca...@debian.org) 
> 

Re: Kernel panic....

[Andrew M.A. Cater]

On Sun, Jul 07, 2024 at 07:07:26PM -0700, Van Snyder wrote:
> I recently installed Debian 12.5 with kernel 6.5.0.0 on an antique Dell
> Vostro 1700. Occasionally it crashes with
> 
> "Kernel Panic - not syncing: Can not allocate SWIOTLB buffer earlier
> and can't now provide you with the DMA bounce buffer"
> 

Hi,

As suggested, use the Debian 6.1 kernel.

This is a laptop from around 2008 if I'm reading the spec. correctly.
This is a laptop with an older Nvidia card. How did you install it?
Did you try to install the Nvidia drivers at any point? I can't 
find out whether this is one of the machines that has dual chipsets
(one Intel / one Nvidia). If so, have you used the instructions
for bumblebee/primus or whatever the appropriate magic now is?

> I saw some remarks about this from 2013 in the context of release 3.5.
> 
> Is this a problem in the kernel, or is the computer broken?
> 
> Should I revert to an earlier release?
> 
>

Ideally, if you're running Debian stable, don't revert to prior versions.

Apt-get update to ensure that you're running the latest point release.

All the very best, as ever,

Andy
(amaca...@debian.org) 

Re: Kernel panic....

[Henning Follmann]

On Sun, Jul 07, 2024 at 07:07:26PM -0700, Van Snyder wrote:
> I recently installed Debian 12.5 with kernel 6.5.0.0 on an antique Dell
> Vostro 1700. Occasionally it crashes with
>

So you installed this kernel from where?

Stable (Debian 12/ bookworm) uses linux kernal 6.1.XXX

> "Kernel Panic - not syncing: Can not allocate SWIOTLB buffer earlier
> and can't now provide you with the DMA bounce buffer"
> 
> I saw some remarks about this from 2013 in the context of release 3.5.
> 
> Is this a problem in the kernel, or is the computer broken?
> 
> Should I revert to an earlier release?

Maybe try the official kernel?


-H 

-- 
Henning Follmann   | hfollm...@itcfollmann.com

Kernel panic....

[Van Snyder]

I recently installed Debian 12.5 with kernel 6.5.0.0 on an antique Dell
Vostro 1700. Occasionally it crashes with

"Kernel Panic - not syncing: Can not allocate SWIOTLB buffer earlier
and can't now provide you with the DMA bounce buffer"

I saw some remarks about this from 2013 in the context of release 3.5.

Is this a problem in the kernel, or is the computer broken?

Should I revert to an earlier release?

Re: booting Debian default kernel with lilo results in kernel panic

[Anssi Saari]

Fourhundred Thecat <400the...@gmx.ch> writes:

> How can I boot Debian kernel with lilo?

I have a vague memory you may need to specify root option per image in
lilo.conf. From my ancient lilo.conf:

# Jessie stock kernel
image = /boot/vmlinuz-3.16.0-4-amd64
  label = "Jessie"
  initrd = /boot/initrd.img-3.16.0-4-amd64
  #append="video=uvesafb:1280x1024,mtrr:2 usbcore.autosuspend=1 elevator=noop"
  append="usbcore.autosuspend=1 elevator=noop"
  root=/dev/sda6

booting Debian default kernel with lilo results in kernel panic

[Fourhundred Thecat]

Hello,

On Debian 10, I am using custom kernel, with lilo boot loader.

Now I want to boot the default Debian distribution kernel. I have
installed the debian kernel image:

  apt-get install linux-image-amd64

and added the entry to /etc/lilo.conf. Now my lilo.conf looks like this:

  https://justpaste.it/99qsr

However, when I boot this kernel, I get kernel panic:

  https://paste.pics/53199721ee9a9f7e4e6fea9e2a8fd7dc

What am I doing  wrong?

How can I boot Debian kernel with lilo?

thanks,

Re: Kernel Panic

[deloptes]

deloptes wrote:

> And gcrypt is libcrypt-2.28.so not .so.20

sorry I was wrong about that /lib/x86_64-linux-gnu/libgcrypt.so.20 is linked
to /lib/x86_64-linux-gnu/libgpg-error.so.0

check where the link is pointing to

ldd /lib/x86_64-linux-gnu/libgcrypt.so.20
linux-vdso.so.1 (0x7ffebd761000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0
(0x7f0628e58000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f0628c97000)
/lib64/ld-linux-x86-64.so.2 (0x7f0628fce000)

Re: Kernel Panic

[deloptes]

john doe wrote:

> On 1/27/2020 7:24 AM, William Torrez Corea wrote:
>> I get the following error, when i send this command
>> sudo apt get update
>>
>> sudo: unable to resolve host debian: Temporary failure in name resolution
>> apt: relocation error: /lib/x86_64-linux-gnu/libgcrypt.so.20: symbol
>> gpgrt_get_syscall_clamp version GPG_ERROR_1.0 not defined in file
>> libgpg-error.so.0 with link time reference
>>
>> I'm trying found a solution, but i don't get results.
>>
>> Follow the following steps
>>
https://gutl.jovenclub.cu/chroot-la-salvacion-elegante-ante-un-kernel-panic/
>>
> 
> You can only use 'apt-get' or 'apt' but not both at the same time.
> 
> $ sudo apt-get update
> $sudo apt update
> 
> However, it looks like your GPG installation is broken.
> 
> --
> John Doe

GPG_ERROR_1.0 is fundamental. It is in buster
in /lib/x86_64-linux-gnu/libgpg-error.so.0.26.1, if I am not wrong.

nm -DC /lib/x86_64-linux-gnu/libgpg-error.so.0.26.1| grep
gpgrt_get_syscall_clamp
ef50 T gpgrt_get_syscall_clamp

And gcrypt is libcrypt-2.28.so not .so.20

perhaps something is wrong with the library paths setup on the system

perhaps you have some custom installed software loading libraries before the
system libraries. Could be also libraries are missing and some left over
has appeared or similar.

Re: Kernel Panic

[john doe]

On 1/27/2020 8:20 AM, William Torrez Corea wrote:
> Ready. I configure Ligpg-error and Libgcrypt but i now get the following
> error:
>
> E: List directory /var/lib/apt/lists/partial is missing. - Acquire (2: No
> such file or directory)
> E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or
> directory)
> E: Could not open file  - open (2: No such file or directory)
> E: Problem opening
> E: The package lists or status file could not be parsed or opened.
>
> On Mon, Jan 27, 2020 at 6:59 AM john doe  wrote:
>
>> On 1/27/2020 7:24 AM, William Torrez Corea wrote:
>>> I get the following error, when i send this command
>>> sudo apt get update
>>>
>>> sudo: unable to resolve host debian: Temporary failure in name resolution
>>> apt: relocation error: /lib/x86_64-linux-gnu/libgcrypt.so.20: symbol
>>> gpgrt_get_syscall_clamp version GPG_ERROR_1.0 not defined in file
>>> libgpg-error.so.0 with link time reference
>>>
>>> I'm trying found a solution, but i don't get results.
>>>
>>> Follow the following steps
>>>
>> https://gutl.jovenclub.cu/chroot-la-salvacion-elegante-ante-un-kernel-panic/
>>>
>>
>> You can only use 'apt-get' or 'apt' but not both at the same time.
>>
>> $ sudo apt-get update
>> $sudo apt update
>>
>> However, it looks like your GPG installation is broken.
>>
>> --
>> John Doe
>>
>>
>

Try this:

$ rm -r /var/lib/apt/*
$ apt-get update


Please post through the list.

--
John Doe

Re: Kernel Panic

[john doe]

On 1/27/2020 7:24 AM, William Torrez Corea wrote:
> I get the following error, when i send this command
> sudo apt get update
>
> sudo: unable to resolve host debian: Temporary failure in name resolution
> apt: relocation error: /lib/x86_64-linux-gnu/libgcrypt.so.20: symbol
> gpgrt_get_syscall_clamp version GPG_ERROR_1.0 not defined in file
> libgpg-error.so.0 with link time reference
>
> I'm trying found a solution, but i don't get results.
>
> Follow the following steps
> https://gutl.jovenclub.cu/chroot-la-salvacion-elegante-ante-un-kernel-panic/
>

You can only use 'apt-get' or 'apt' but not both at the same time.

$ sudo apt-get update
$sudo apt update

However, it looks like your GPG installation is broken.

--
John Doe

Re: Kernel Panic

[Keith Bainbridge]

try sudo apt-get update

Keith Bainbridge

keith.bainbridge.3...@gmail.com
0447 667 468

On 27/1/20 5:24 pm, William Torrez Corea wrote:

sudo apt get update

Kernel Panic

[William Torrez Corea]

I get the following error, when i send this command
sudo apt get update

sudo: unable to resolve host debian: Temporary failure in name resolution
apt: relocation error: /lib/x86_64-linux-gnu/libgcrypt.so.20: symbol
gpgrt_get_syscall_clamp version GPG_ERROR_1.0 not defined in file
libgpg-error.so.0 with link time reference

I'm trying found a solution, but i don't get results.

Follow the following steps
https://gutl.jovenclub.cu/chroot-la-salvacion-elegante-ante-un-kernel-panic/

-- 
William Torrez Corea

Linux debian 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20)
x86_64 GNU/Linux
0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20) x86_64 GNU/Linux

Re: disk encryption causing kernel panic

[Pascal Hambourg]

Le 14/10/2018 à 22:32, Bill a écrit :


The problem seems to be that there is a bug in cryptsetup? which causes 
a kernel panic.


AFAIK bugs in userland programs don't cause kernel panics. Kernel bugs 
do. Userland programs may only trigger kernel bugs which cause a kernel 
panic.


In the output below, md2 is (encrypted) swap and md8 is 
/text - an encrypted partition. /text currently has only a few files 
which I could sacrifice, although I'd rather not.


I successfully enter the password for md2 and then don't even see the 
request for md8_crypt (ie a prompt for input)


Please unlock disk md2_crypt:
cryptsetup (md2_crypt): set up successfully
Please enter passphrase for disk md8_crypt on /text!

   ^
What then is this ?


[   51.451083] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.9.0-3-amd64
As Reco wrote, the panic seems to be related with the swap, which was 
unlocked just before the panic. Did you try to :

- not unlock md2_crypt but only md8_crypt
- unlock md2_crypt but not activate the swap within

You can use a live system or the Debian installer in rescue mode to do 
the tests.



What would I do if there were a lot of files?


Restore from backup, as usual.

Re: disk encryption causing kernel panic

[Reco]

Hi.

On Sun, Oct 14, 2018 at 01:32:31PM -0700, Bill wrote:
> I successfully enter the password for md2 and then don't even see the request 
> for md8_crypt (ie a prompt for input) but get the following
> (condensed) output below.

The most interesting part of those kernel BUGs are stack traces.
The only useful things that I can see in your abridged dmesg are:

1) You're using an old kernel. The current one's called 4.9.0-8.

2) The problem seems to be related to the swap - it's swapper/0 that's
triggering the bug.

3) There are multiple CPUs/CPU cores/CPU threads there.

But stack trace is needed to proceed further.

Reco

disk encryption causing kernel panic

[Bill]

Hi folks,

I'm unable to boot my previously stable workstation after attempting to 
install rinetd through systemd. Although rinetd worked fine prior to 
systemd it doesn't work now and caused /var to saturate (10Gb). This may 
or may not be related, but I mention it as prologue. I have access to 
the system via a rescue key.


The problem seems to be that there is a bug in cryptsetup? which causes 
a kernel panic. In the output below, md2 is (encrypted) swap and md8 is 
/text - an encrypted partition. /text currently has only a few files 
which I could sacrifice, although I'd rather not.


I successfully enter the password for md2 and then don't even see the 
request for md8_crypt (ie a prompt for input) but get the following 
(condensed) output below.


I'm hoping someone has seen this before and knows a workaround. I'd 
rather not do a complete reinstall if I don't have to. What would I do 
if there were a lot of files?


Thanks much,

Bill



Please unlock disk md2_crypt:
cryptsetup (md2_crypt): set up successfully
Please enter passphrase for disk md8_crypt on /text!
[   51.450202] BUG: unable to handle kernel NULL pointer dereference
at(null)
[   51,450255] IP: [<(null)>]   (null)
[   51.450285] PGD 0 [   51.450296]
[   51.450311] Oops: 0010 [#1] SMP
[   51.450329] Modules linked in: ..
[   51.451083] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.9.0-3-amd64 
#1 Debian 4.9.0-2+deb9u5

[   51.451123] Hardware name: Supermicro X9SAE/X9SAE, BIOS 2.0b 07/10/2013
[   51.451156] task: 8e40e500 task.stack: 8e40
[   51.451185] RIP: 0010: [<>]  [> (null)>]   (null)
...
...
...
[   51.451524] Stack:
...
...
[   51.451680] Call Trace:
...
...
[   51.452376] Code: Bad RIP value.
[   51.452403] RIP  [<(null)>] (null)
[   51.452432]  RSP  
[   51.452451] CR2: 
[   51.452471] ---[end trace cd08982bd438f7e2 ]---
[   51.452495] Kernel panic - not syncing: Fatal exception in interrupt
[   51.452561] Kernel Offset: 0xc80 from 0x8100 
(relocation range: 0xffff8000-0xbfff)
[   51.452621] ---[ end Kernel panic - not syncing: Fatal exception in 
interrupt


end of output from boot attempt

--
Sent using Icedove on Debian GNU/Linux.

Re: Stretch 9.5 amd64 kernel panic

[Andy Smith]

Hello,

On Sat, Jul 14, 2018 at 08:48:18PM -0400, Chuck Zmudzinski wrote:
> I captured a little bit of what was written to the xen console
> when the kernel panics which is shown below.
> 
> Anyone else seen this?

Seems the new point release kernel broke Xen PV:



Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Stretch 9.5 amd64 kernel panic

[Chuck Zmudzinski]

Hello,

I just updated my Debian stretch system using apt-get dist-upgrade to 
stretch

9.5, which uses the new 4.9.0-7 kernel. On amd64, the kernel comes from the
linux-image-4.9.0-7-amd64_4.9.110-1_amd64.deb binary package. It was just
released about a week ago. The timestamp on the .deb file is July 6, 2018.

I am running stretch on a Haswell Intel 4590S processor and ASROCK B85M Pro4
motherboard as a Dom0 on the up-to-date Xen 4.8 hyervisor for stretch, or as
a DomU on the same machine and hypervisor for stretch. In both cases, with
the new 4.9.0-7 amd64 kernel, the system enters an endless cycle of kernel
panic -> reboot -> kernel panic -> reboot ...

I also have a Debian stretch 32-bit Xen DomU system and the new 4.9.0-7
i686-pae kernel boots the Debian 9.5 DomU normally on the same hardware.
Only the new amd64 kernel has the problem, not the new i686-pae kernel.

So to run the new Debian stretch 9.5 I need to set grub to boot the 
previously

working kernel, the up-to-date 4.9.0-6 version, for amd64. For i686-pae,
I can use the new 4.9.0-7 version of the kernel.

I captured a little bit of what was written to the xen console when the 
kernel

panics which is shown below.

Anyone else seen this?

Thanks,

Chuck

[    0.120071] dmi: Firmware registration failed.
[    1.176611] dmi-sysfs: dmi entry is absent.
[    1.189531] general protection fault:  [#1] SMP
[    1.189538] Modules linked in:
[    1.189543] CPU: 1 PID: 1 Comm: init Not tainted 4.9.0-7-amd64 #1 
Debian 4.9.110-1

[    1.189549] task: 8800bac08040 task.stack: c90040628000
[    1.189553] RIP: e030:[] [] 
ret_from_fork+0x2d/0x70

[    1.189562] RSP: e02b:c9004062bf50  EFLAGS: 00010006
[    1.189565] RAX: 0002dd603000 RBX: 816076d0 RCX: 
ea0002ebafdf
[    1.189570] RDX: 0002 RSI: 0002 RDI: 
c9004062bf58
[    1.189574] RBP:  R08:  R09: 
8800b7a76000
[    1.189579] R10: 8080808080808080 R11: fefefefefefefeff R12: 

[    1.189583] R13:  R14:  R15: 

[    1.189592] FS:  () GS:8800bbf0() 
knlGS:

[    1.189597] CS:  e033 DS:  ES:  CR0: 80050033
[    1.189601] CR2: 7fffb09bdb79 CR3: b5602000 CR4: 
00042660

[    1.189607] Stack:
[    1.189609]     

[    1.189617]     

[    1.189625]     


[    1.189635] Call Trace:
[    1.189640] Code: c7 e8 b8 fe a8 ff 48 85 db 75 2f 48 89 e7 e8 5b ed 
9e ff 50 90 0f 20 d8 65 48 0b 04 25 e0 02 01 00 78 08 65 88 04 25 e7 02 
01 00 <0f> 22 d8 58 66 0f 1f 44 00 00 e9 c1 07 00 00 4c 89 e7 eb 11 e8

[    1.189708] RIP  [] ret_from_fork+0x2d/0x70
[    1.189714]  RSP 
[    1.189719] ---[ end trace ddfc12432c0049a4 ]---
[    1.189798] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b

[    1.189798]
[    1.189811] Kernel Offset: disabled

Re: Kernel Panic in VMXNET3 Driver

[deloptes]

Mini Trader wrote:

> I am on stretch  Debian 4.9.30-2+deb9u2.  Is there a link to submit this
> bug too?
> 
> On Ubuntu's 4.4.0-83-generic this is not reproducible.

usually reportbug is used to do this, however  IMO you are hitting some
other bug, but this is just a guess

regards

Re: Kernel Panic in VMXNET3 Driver

[Mini Trader]

I am on stretch  Debian 4.9.30-2+deb9u2.  Is there a link to submit this
bug too?

On Ubuntu's 4.4.0-83-generic this is not reproducible.


On Mon, Jul 3, 2017 at 6:45 PM, deloptes  wrote:

> Mini Trader wrote:
>
> > More information.  I found a post here:
> >
> > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650635
> >
> > They mention LRO so I disabled it.  I cannot reproduce if LRO is
> disabled.
> >
> > On Mon, Jul 3, 2017 at 5:59 PM, Mini Trader 
> > wrote:
> >
> >> Looks to be the same.
> >>
> >> On Mon, Jul 3, 2017 at 5:48 PM, deloptes  wrote:
> >>
> >>> Mini Trader wrote:
> >>>
> >>> > task_numa_fault+0x6ed/0xd20
> >>>
> >>> what happens if you boot the vm with numa=off
> >>>
> >>>
> >>>
> >>>
> >>
>
> the change mentioned in the article is in the kernel - at least 4.11.2 - I
> don't know about your version. The article is about 4.4.
>
> perhaps solved by chance - you have to report back to kernel maintainer I
> guess
>
> 4.11.2 and 4.10.14
>
> line nr 1395 to 1415
> if (VMXNET3_VERSION_GE_2(adapter) &&
> rcd->type == VMXNET3_CDTYPE_RXCOMP_LRO) {
> struct Vmxnet3_RxCompDescExt *rcdlro;
> rcdlro = (struct Vmxnet3_RxCompDescExt
> *)rcd;
>
> segCnt = rcdlro->segCnt;
> WARN_ON_ONCE(segCnt == 0);
> mss = rcdlro->mss;
> if (unlikely(segCnt <= 1))
> segCnt = 0;
> } else {
> segCnt = 0;
> }
> } else {
> BUG_ON(ctx->skb == NULL && !skip_page_frags);
>
> /* non SOP buffer must be type 1 in most cases */
> BUG_ON(rbi->buf_type != VMXNET3_RX_BUF_PAGE);
> BUG_ON(rxd->btype != VMXNET3_RXD_BTYPE_BODY);
>
>
>
>

Re: Kernel Panic in VMXNET3 Driver

[deloptes]

Mini Trader wrote:

> More information.  I found a post here:
> 
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650635
> 
> They mention LRO so I disabled it.  I cannot reproduce if LRO is disabled.
> 
> On Mon, Jul 3, 2017 at 5:59 PM, Mini Trader 
> wrote:
> 
>> Looks to be the same.
>>
>> On Mon, Jul 3, 2017 at 5:48 PM, deloptes  wrote:
>>
>>> Mini Trader wrote:
>>>
>>> > task_numa_fault+0x6ed/0xd20
>>>
>>> what happens if you boot the vm with numa=off
>>>
>>>
>>>
>>>
>>

the change mentioned in the article is in the kernel - at least 4.11.2 - I
don't know about your version. The article is about 4.4.

perhaps solved by chance - you have to report back to kernel maintainer I
guess

4.11.2 and 4.10.14

line nr 1395 to 1415
if (VMXNET3_VERSION_GE_2(adapter) &&
rcd->type == VMXNET3_CDTYPE_RXCOMP_LRO) {
struct Vmxnet3_RxCompDescExt *rcdlro;
rcdlro = (struct Vmxnet3_RxCompDescExt
*)rcd;

segCnt = rcdlro->segCnt;
WARN_ON_ONCE(segCnt == 0);
mss = rcdlro->mss;
if (unlikely(segCnt <= 1))
segCnt = 0;
} else {
segCnt = 0;
}
} else {
BUG_ON(ctx->skb == NULL && !skip_page_frags);

/* non SOP buffer must be type 1 in most cases */
BUG_ON(rbi->buf_type != VMXNET3_RX_BUF_PAGE);
BUG_ON(rxd->btype != VMXNET3_RXD_BTYPE_BODY);

Re: Kernel Panic in VMXNET3 Driver

[Mini Trader]

More information.  I found a post here:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650635

They mention LRO so I disabled it.  I cannot reproduce if LRO is disabled.

On Mon, Jul 3, 2017 at 5:59 PM, Mini Trader 
wrote:

> Looks to be the same.
>
> On Mon, Jul 3, 2017 at 5:48 PM, deloptes  wrote:
>
>> Mini Trader wrote:
>>
>> > task_numa_fault+0x6ed/0xd20
>>
>> what happens if you boot the vm with numa=off
>>
>>
>>
>>
>

Re: Kernel Panic in VMXNET3 Driver

[Mini Trader]

Looks to be the same.

On Mon, Jul 3, 2017 at 5:48 PM, deloptes  wrote:

> Mini Trader wrote:
>
> > task_numa_fault+0x6ed/0xd20
>
> what happens if you boot the vm with numa=off
>
>
>
>

Re: Kernel Panic in VMXNET3 Driver

[deloptes]

Mini Trader wrote:

> task_numa_fault+0x6ed/0xd20

what happens if you boot the vm with numa=off

Kernel Panic in VMXNET3 Driver

[Mini Trader]

I had posted earlier that I was having issues with a java program but after
doing some quick digging I've been able to identity the error.  I enabled
logging kernel messages over the network and was able to capture this.
Would appreciate some guidance on where to go from here.

[  118.656721] [ cut here ]
[  118.657261] kernel BUG at
/build/linux-9uDFZV/linux-4.9.30/drivers/net/vmxnet3/vmxnet3_drv.c:1413!
[  118.658106] invalid opcode:  [#1] SMP
[  118.658628] Modules linked in: netconsole configfs sb_edac edac_core
coretemp crct10dif_pclmul ppdev crc32_pclmul vmw_balloon
ghash_clmulni_intel intel_rapl_perf joydev serio_raw pcspkr sg shpchp
vmwgfx vmw_vmci ttm drm_kms_helper drm nfit libnvdimm battery evdev
parport_pc parport ac acpi_cpufreq button ip_tables x_tables autofs4 ext4
crc16 jbd2 crc32c_generic fscrypto ecb mbcache dm_mod sr_mod cdrom sd_mod
ata_generic crc32c_intel aesni_intel aes_x86_64 glue_helper lrw gf128mul
ablk_helper cryptd psmouse ata_piix vmxnet3 vmw_pvscsi i2c_piix4 libata
scsi_mod
[  118.661572] CPU: 0 PID: 891 Comm: java Not tainted 4.9.0-3-amd64 #1
Debian 4.9.30-2+deb9u2
[  118.662153] Hardware name: VMware, Inc. VMware Virtual Platform/440BX
Desktop Reference Platform, BIOS 6.00 04/05/2016
[  118.663136] task: 8dd87882a0c0 task.stack: a9998147
[  118.663695] RIP: 0010:[]  []
vmxnet3_rq_rx_complete+0x905/0xf10 [vmxnet3]
[  118.664735] RSP: :8dd87fc03e38  EFLAGS: 00010297
[  118.665279] RAX:  RBX:  RCX:
8dd878ad5a00
[  118.665857] RDX: 0040 RSI: 0001 RDI:
0040
[  118.666426] RBP: 0001 R08:  R09:
0028
[  118.666984] R10:  R11: 8dd8369688c0 R12:
8dd8369690c0
[  118.667613] R13: 8dd835ea8330 R14: 8dd87c192010 R15:
8dd835ed8018
[  118.668172] FS:  7f1b1974e700() GS:8dd87fc0()
knlGS:
[  118.668723] CS:  0010 DS:  ES:  CR0: 80050033
[  118.669310] CR2: 7f1ad63e2fd8 CR3: 7bcac000 CR4:
003406f0
[  118.669892] DR0:  DR1:  DR2:

[  118.670520] DR3:  DR6: fffe0ff0 DR7:
0400
[  118.671099] Stack:
[  118.671677]  8dd836969190 0047 0002
8dd8369690e0
[  118.672313]  b22b002d 8dd8369688c0 
8dd8369688c0
[  118.672950]   8dd8369688c0 8dd8369690e0
0040
[  118.673603] Call Trace:
[  118.674166]   [  118.674180]  [] ?
task_numa_fault+0x6ed/0xd20
[  118.674876]  [] ? vmxnet3_poll_rx_only+0x35/0xa0
[vmxnet3]
[  118.675479]  [] ? net_rx_action+0x240/0x370
[  118.676099]  [] ? __do_softirq+0x105/0x290
[  118.676681]  [] ? irq_exit+0xae/0xb0
[  118.677294]  [] ? do_IRQ+0x4f/0xd0
[  118.677971]  [] ? common_interrupt+0x82/0x82
[  118.678522]   [  118.678532] Code:
89 54 24 28 e8 9d 72 4e f2 0f b6 44 24 30 4c 8b 5c 24 38 4c 8b 54 24 28 49
c7 84 24 48 01 00 00 00 00 00 00 89 c6 e9 59 f8 ff ff <0f> 0b 0f 0b 49 83
84 24 a0 01 00 00 01 49 c7 84 24 48 01 00 00
[  118.680438] RIP  [] vmxnet3_rq_rx_complete+0x905/0xf10
[vmxnet3]
[  118.681063]  RSP 
[  118.681676] ---[ end trace 5927dc1afdb8f3dd ]---
[  118.682244] Kernel panic - not syncing: Fatal exception in interrupt
[  118.682880] Kernel Offset: 0x3120 from 0x8100
(relocation range: 0x8000-0xbfff)
[  118.683993] ---[ end Kernel panic - not syncing: Fatal exception in
interrupt

kernel panic irq flow_dissect pppoe in debian stretch

[HugLeo]

Kernel version: 4.9.0-1-amd64 #1 SMP Debian 4.9.2-2 (2017-01-12) x86_64
GNU/Linux

/

SHORT LOG:

Feb  2 13:51:50 server [17103.669019] BUG: unable to handle kernel
Feb  2 13:51:50 server NULL pointer dereference
Feb  2 13:51:50 server at 0080
Feb  2 13:51:50 server [17103.669065] IP:
Feb  2 13:51:50 server [] __skb_flow_dissect+0xa8a/0xcf0
Feb  2 13:51:50 server [17103.669092] PGD 0
Feb  2 13:51:50 server [17103.669100]
Feb  2 13:51:50 server [17103.669109] Oops:  [#1] SMP
Feb  2 13:51:50 server [17103.669122] Modules linked in:


Feb  2 13:51:50 server [17103.669680] CPU: 2 PID: 0 Comm: swapper/2
Tainted: G   OE   4.9.0-1-amd64 #1 Debian 4.9.2-2
Feb  2 13:51:50 server [17103.669710] Hardware name: IBM IBM System x3650
M4: -[7915AC1]-/00KF656, BIOS -[VVE142DUS-1.73]- 07/31/2014
Feb  2 13:51:50 server [17103.669742] task: 9e1d2d03b040 task.stack:
c0898190c000
Feb  2 13:51:50 server [17103.669762] RIP: 0010:[]
Feb  2 13:51:50 server [] __skb_flow_dissect+0xa8a/0xcf0
Feb  2 13:51:50 server [17103.669794] RSP: 0018:9e1d3fc83cc0  EFLAGS:
00010286
Feb  2 13:51:50 server [17103.669812] RAX: 8130 RBX:
a03176c0 RCX: 9e1cf514b000
Feb  2 13:51:50 server [17103.669836] RDX: 000c RSI:
0008 RDI: 000c
Feb  2 13:51:50 server [17103.669859] RBP: 0b88 R08:
 R09: 002a
Feb  2 13:51:50 server [17103.669883] R10: 0008 R11:
9e1d3fc83d84 R12: 
Feb  2 13:51:50 server [17103.669906] R13: 9e1cf514b000 R14:
9e1d3fc83d84 R15: 002f
Feb  2 13:51:50 server [17103.669930] FS:  ()
GS:9e1d3fc8() knlGS:
Feb  2 13:51:50 server [17103.669957] CS:  0010 DS:  ES:  CR0:
80050033
Feb  2 13:51:50 server [17103.669976] CR2: 0080 CR3:
00045ef91000 CR4: 001406e0
Feb  2 13:51:50 server [17103.67] Stack:
Feb  2 13:51:50 server [17103.670009]  9e1cf514b02a
Feb  2 13:51:50 server 0001
Feb  2 13:51:50 server 9fadbf9f
Feb  2 13:51:50 server 9e1d000c
Feb  2 13:51:50 server
Feb  2 13:51:50 server [17103.670040]  9e1d1eeea078
Feb  2 13:51:50 server c0957220
Feb  2 13:51:50 server 9e1d2760
Feb  2 13:51:50 server 9e1d276000a0
Feb  2 13:51:50 server
Feb  2 13:51:50 server [17103.670072]  9faf3c99
Feb  2 13:51:50 server 9fb39700
Feb  2 13:51:50 server dc6a359a63444ed4
Feb  2 13:51:50 server 0246
Feb  2 13:51:50 server
Feb  2 13:51:50 server [17103.670103] Call Trace:
Feb  2 13:51:50 server [17103.670114]  
Feb  2 13:51:50 server [17103.670125]  [] ?
__sk_receive_skb+0x13f/0x1d0
Feb  2 13:51:50 server [17103.670149]  [] ?
__netif_receive_skb_core+0x4f9/0xa00
Feb  2 13:51:50 server [17103.670173]  [] ?
ip_finish_output2+0x350/0x370
Feb  2 13:51:50 server [17103.670194]  [] ?
ip_forward+0x379/0x470
Feb  2 13:51:50 server [17103.670215]  [] ?
eth_get_headlen+0x80/0xd0
Feb  2 13:51:50 server [17103.670243]  [] ?
ixgbe_clean_rx_irq+0x814/0xa80 [ixgbe]
Feb  2 13:51:50 server [17103.670270]  [] ?
ixgbe_poll+0x3cc/0x780 [ixgbe]
Feb  2 13:51:50 server [17103.670292]  [] ?
net_rx_action+0x240/0x370
Feb  2 13:51:50 server [17103.670314]  [] ?
__do_softirq+0x105/0x290
Feb  2 13:51:50 server [17103.670335]  [] ?
irq_exit+0xae/0xb0
Feb  2 13:51:50 server [17103.670353]  [] ?
do_IRQ+0x4f/0xd0
Feb  2 13:51:50 server [17103.670372]  [] ?
common_interrupt+0x82/0x82
Feb  2 13:51:50 server [17103.670392]  
Feb  2 13:51:50 server [17103.670403]  [] ?
cpuidle_enter_state+0x11a/0x2b0
Feb  2 13:51:50 server [17103.670425]  [] ?
cpuidle_enter_state+0x107/0x2b0
Feb  2 13:51:50 server [17103.671327]  [] ?
cpu_startup_entry+0x154/0x240
Feb  2 13:51:50 server [17103.672226]  [] ?
start_secondary+0x14d/0x190
Feb  2 13:51:50 server [17103.673124] Code:



Do you anybody help?

kernel panic at Jessie shutdown

[Elmer E. Dow]

I installed Debian LXDE 8.2 (Jessie) on an IBM R40 laptop (2897-54U, 1.3 
Centrino processor, 256 meg memory) using the netinst CD. The LAN port 
is broken, so I used a USB to RJ45 adapter. Installation went fine, but 
when I clicked logout, then shutdown, it went into kernel panic, giving 
the following messages:


[   222.710760] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009

[   222.710760]
[   222.713883] Kernel offset: 0x0 from 0xc000  (relocation range: 
0xc000 - 0xd075)
[   222.713883] drm_kms_helper: panic occurred, switching back to text 
console
[   222.713883] ---[end kernel panic - not syncing: Attempted to kill 
init! exitcode:0x0009

[   222.713883]

Then it failed to shutdown, so I had to press the power button to shut 
it down. It continues to do that.


Any suggestion as to what's the cause  and what's the solution? I had 
been running Squeeze before this Jessie installation.


Please cc me as I am not subscribed.

elmer

Kernel panic and shutdown

[Eric Offermann]

I have an i7-3612Qe system that has been giving kernel panics when running a 
custom video streaming application pretty consistently after a couple minutes.  
After the kernel panic, the machine reboots.  When I turn off turbo mode in the 
BIOS, the panics happen less frequently.  Other BIOS settings are all default, 
no overclocking or anything fancy.



-Can be reproduced by running streaming application using ~250% CPU, temps are 
a little high, they float around 68-71 degrees

-sysbench runs fine with 8 threads, throttles CPU up to ~800%, no kernel 
panics, temps remain below 70 degrees

-MemTest did not report any errors

-Intel Processor Diagnotic tool passed

-Tried swapping RAM

-Reproducible on multiple machines, not just a single processor (possibly 
eliminates it being a bad single proc)



-Able to mitigate most of the kernel panics and reboots by disabling Turbo mode 
(this is unacceptable, just including this for debugging purposes)

-Also able to mitigate kernel panics and reboots by changing the cpu frequency 
sacling_governor to conservative, from ondemand.  Conservative should 
"gracefully increase and decreases the CPU speed rather than jumping to max 
speed the moment there is any load on the CPU" 
(https://www.kernel.org/doc/Documentation/cpu-freq/governors.txt)



Here is what I could copy down from the kernel panic on the monitor, sometimes 
the messages vary slightly, bu the TSC and PROCESSOR messages are almost always 
the same.



[Hardware Error]:  TSC 6e496d96062

[Hardware Error]:  PROCESSOR 0:306a9 TIME 1418929330 SOCKET 0 APIC 3 microcode 
12

[Hardware Error]:  Run the above through 'mcelog --ascii'

[Hardware Error]:  CPU 0: Machine Check Exception: 5 Bank 4: b2100402

[Hardware Error]:  RIP !INEXACT! 10: {intel_idle+0xb9/0x119}

[Hardware Error]:  TSC 148c99828a0

[Hardware Error]:  PROCESSOR 0:306a9 TIME 1418929330 SOCKET 0 APIC 3 microcode 
12

[Hardware Error]:  Run the above through 'mcelog --ascii'

[Hardware Error]:  Some CPUs didn't answer in synchronization

[Hardware Error]:  Machine check:  Processor context corrupt

Kernel panic - not synching: Fatal machine check on current CPU

Pid: 0, comm: swapper/3 Tained: P  M   0 3.2.0-4-amd64 #1 Debian 3.2.51-1

Call Trace: ...



Also, here is a post from superuser on some suggestions that I tried: cpu - 
Kernel Panic from overheating? - Super 
User<http://superuser.com/questions/854199/kernel-panic-from-overheating?noredirect=1#comment1130272_854199>



Here is my discussion on intel where someone recommended I post to the debian 
list https://communities.intel.com/thread/58372?sr=stream



I am looking to actually debug and fix this, but not finding a lot out there.  
Any ideas for what to try next?

Re: Kernel panic - 2.6.32, tcp_keepalive_timer

[Karl E. Jorgensen]

Hi

On Wed, Nov 06, 2013 at 12:39:42PM +0200, Vladimir Zagaychuk wrote:
> Good day!
> 
> I am getting kernel panic with the kernel version 2.6.32 - call trace is
> available here:
> http://i.imgur.com/kHfhRy9.jpg
> 
> Is there any ideas how to deal with this?
> Thank you!

Not really - to make sense of it, the whole trace would be needed
(probably about 50-100 lines or so), rather than just the last 24
lines...

If the kernel panic made it to disk, have a look in /var/log/kern.log..

Hope this helps

-- 
Karl E. Jorgensen


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131106122853.GA5700@hawking

Kernel panic - 2.6.32, tcp_keepalive_timer

[Vladimir Zagaychuk]

Good day!

I am getting kernel panic with the kernel version 2.6.32 - call trace is
available here:
http://i.imgur.com/kHfhRy9.jpg

Is there any ideas how to deal with this?
Thank you!

-- 
Vladimir Zagaychuk (VZ485-RIPE)

Re: Diagnosing kernel panic involving fglrx

[Ari Epstein]

One change I made shortly before the problems started that might be
relevant: I enabled i386 architecture support (it's amd64 laptop).


On Tue, Jun 4, 2013 at 7:36 AM, Ari Epstein  wrote:

> Hi all,
>
> Got a new laptop and installed wheezy a few weeks ago.  I noticed the HDMI
> audio was not working, and figured it was a limitation in the fglrx driver
> and it seemed otherwise to run well.  Starting yesterday, however, I have
> frequent but not consistent kernel panics during the boot process that seem
> to involve support for that feature.  Sometimes it boots without any audio
> (there is another integrated audio device), sometimes with, sometimes it
> does not boot at all. Never had to debug something like this before so some
> pointers about how to go about it are appreciated! dmesg logs attached for
> occassions that it booted with audio and without audio.
>



-- 

Ari Epstein

311 W Buffalo St
Ithaca, NY 14850-4123

aepstein...@gmail.com
607.222.5116

Re: BTRFS Kernel Panic

[Alex Robbins]

I was able to copy almost everything from dd images to a new set
of filesystems.  The only thing that was excluded from the transfer
was /var/cache/apt, because something in there was causing the problem.
I performed the transfer by booting to a second system.  Interestingly,
when this problem arose during the transfer, which was being run from this
other system, the problem was not as serious.  The program that triggered
the problem died and a call stack was printed by the kernel, but apparently
everything else continued to work.  I don't know why the problem was less
serious when it occurred on the transfer system, as the filesystem with
a problem was not the / of any system, it was /var (and therefore no more
important to the first system as it was to the system performing the 
transfer).


In any case, all appears to be well; I can run both aptitude update and
updatedb, and it hasn't crashed since.

Thank you for your help.



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/516b5c2b.10...@gmail.com

Re: BTRFS Kernel Panic

[Martin Steigerwald]

On Thursday 11 April 2013 23:23:30 Roger Leigh wrote:
> You could also try upgrading to a newer kernel e.g. 3.8.x.  I've
> done this myself due to btrfs issues with older kernels; you might
> need to hand-build it though since Debian doesn't yet have it.
> See kernel-package.

Debian has it in experimental:

martin@merkaba:~> rmadison linux-image-3.8-trunk-amd64
 linux-image-3.8-trunk-amd64 | 3.8.5-1~experimental.1 | experimental | 
amd64, i386

;)

I also recommend running current kernels with BTRFS.

-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/29696065.TvIoNG5Q5r@merkaba

Re: BTRFS Kernel Panic

[Roger Leigh]

On Thu, Apr 11, 2013 at 03:50:19PM -0500, Alex Robbins wrote:
> So it looks like btrfs really is still experimental.
> 
> I have / and /var on two separate btrfs partitions and I consistently get
> a kernel panic when I run "aptitude update" (see the end).  I also managed
> to get the same results by using find and dd to read every file in /var.
> 
> Although my oops output does have RIP: btrfs_num_copies, I do not think that
> I need to use btrfs-zero-log because (1) I am using a 3.2 series kernel, (2)
> my panic callstack does not have a function that begins with "replay_one_",
> and (3) I am able to mount the partitions (and boot) just fine.  It is only
> when some process such as aptitude or updatedb (indexing for the locate
> command) tries to read something in the filesystem.

I'd suggest that you firstly:

1) take a full image of the raw devices containing these filesystems
   with dd in case of further damage
2) try to backup the filesystems with tar

If you get a backup, you could then reformat the partitions and
restore the backups.

I'd definitely recommend looking at the changelog for newer
versions of the linux kernel to see if this has fixed.  It
also might be worth contacting the brtfs developers' mailing
list to see if they have seen this issue before--the BUG alone
might be useful.

You could also try upgrading to a newer kernel e.g. 3.8.x.  I've
done this myself due to btrfs issues with older kernels; you might
need to hand-build it though since Debian doesn't yet have it.
See kernel-package.

[I've previously lost a large raid-1 btrfs filesystem--both copies
completely trashed after a SATA glitch, including the good copy
which was corrupted entirely by btrfs...  Currently using it on an
SSH for testing purposes as my rootfs, but don't use it for user
data, which is on ext4 on LVM RAID.]


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linuxhttp://people.debian.org/~rleigh/
 `. `'   schroot and sbuild  http://alioth.debian.org/projects/buildd-tools
   `-GPG Public Key  F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130411222330.ga23...@codelibre.net

BTRFS Kernel Panic

[Alex Robbins]

So it looks like btrfs really is still experimental.

I have / and /var on two separate btrfs partitions and I consistently get
a kernel panic when I run "aptitude update" (see the end).  I also managed
to get the same results by using find and dd to read every file in /var.

Although my oops output does have RIP: btrfs_num_copies, I do not think that
I need to use btrfs-zero-log because (1) I am using a 3.2 series kernel, (2)
my panic callstack does not have a function that begins with "replay_one_",
and (3) I am able to mount the partitions (and boot) just fine.  It is only
when some process such as aptitude or updatedb (indexing for the locate
command) tries to read something in the filesystem.

I tried scrubbing the filesystems, but no errors were found (and somehow no
panics occured).  Finally, I can't really see what's going on with an strace
or anything because the panic happens before anything gets written to 
the disk

(even if I do an emergency sync and remount-ro with sysrq before rebooting),
and I *really* don't want to install netconsole because I am worried that
any package management will cause a panic during an installation which could
make my situation much worse.

I have run out of ideas and am looking for suggestions.

The panic from /var/log/kern.log:
Apr  7 17:39:29 alexdell2-wheezy kernel: [ 7290.632188] parent transid 
verify failed on 18446277369678266402 wanted 18446277756225214326 found 0
Apr  7 17:39:29 alexdell2-wheezy kernel: [ 7290.632203] parent transid 
verify failed on 18446277369678266402 wanted 18446277756225214326 found 0
Apr  7 17:39:29 alexdell2-wheezy kernel: [ 7290.632278] [ 
cut here ]
Apr  7 17:39:29 alexdell2-wheezy kernel: [ 7290.632331] kernel BUG at 
/build/buildd-linux_3.2.39-2-amd64-G5_nN0/linux-3.2.39/fs/btrfs/volumes.c:2860!
Apr  7 17:39:29 alexdell2-wheezy kernel: [ 7290.632412] invalid opcode: 
 [#1] SMP

Apr  7 17:39:29 alexdell2-wheezy kernel: [ 7290.632458] CPU 0
Apr  7 17:39:29 alexdell2-wheezy kernel: [ 7290.632478] Modules linked 
in: hidp cryptd aes_x86_64 aes_generic nbd ip6table_filter ip6_tables 
iptable_filter ip_tables ebtable_nat ebtables x_tables parport_pc ppdev 
lp parport rfcomm bnep cpufreq_userspace cpufreq_stats cpufreq_powersave 
cpufreq_conservative pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) 
vboxdrv(O) binfmt_misc uinput fuse nfsd nfs nfs_acl auth_rpcgss fscache 
lockd sunrpc loop dm_crypt sg uvcvideo videodev v4l2_compat_ioctl32 
media btusb bluetooth crc16 joydev ata_generic acpi_cpufreq i915 mperf 
r592 dell_laptop ata_piix coretemp drm_kms_helper dcdbas drm 
i2c_algo_bit memstick snd_hda_codec_idt snd_hda_codec_hdmi pcspkr arc4 
firewire_ohci firewire_core crc_itu_t iwl3945 iwl_legacy snd_hda_intel 
mac80211 snd_hda_codec sky2 snd_hwdep snd_pcm snd_page_alloc psmouse 
serio_raw cfg80211 rfkill r852 sm_common nand nand_ecc nand_ids mtd 
dell_wmi snd_seq snd_seq_device sparse_keymap snd_timer sdhci_pci sdhci 
snd iTCO_wdt iTCO_vendor_support wmi soundcore processor mm
Apr  7 17:39:29 alexdell2-wheezy kernel: c_core i2c_i801 video battery 
ac i2c_core evdev power_supply button btrfs crc32c libcrc32c 
zlib_deflate dm_mod usb_storage usbhid hid sl811_hcd ohci_hcd sr_mod 
cdrom sd_mod crc_t10dif thermal ahci libahci libata thermal_sys uhci_hcd 
scsi_mod ehci_hcd usbcore usb_common

Apr  7 17:39:29 alexdell2-wheezy kernel: [ 7290.633954]
Apr  7 17:39:29 alexdell2-wheezy kernel: [ 7290.633972] Pid: 6448, comm: 
aptitude Tainted: G   O 3.2.0-4-amd64 #1 Debian 3.2.39-2 Dell 
Inc. Inspiron 1525   /0WP007
Apr  7 17:39:29 alexdell2-wheezy kernel: [ 7290.634090] RIP: 
0010:[]  [] 
btrfs_num_copies+0x3f/0x89 [btrfs]
Apr  7 17:39:29 alexdell2-wheezy kernel: [ 7290.634196] RSP: 
0018:88004dd1d9b8  EFLAGS: 00010246
Apr  7 17:39:29 alexdell2-wheezy kernel: [ 7290.634244] RAX: 
 RBX: fffe57890022 RCX: 0001
Apr  7 17:39:29 alexdell2-wheezy kernel: [ 7290.634304] RDX: 
 RSI: fffe57890022 RDI: 880115079110
Apr  7 17:39:29 alexdell2-wheezy kernel: [ 7290.634363] RBP: 
880115079110 R08:  R09: 
Apr  7 17:39:29 alexdell2-wheezy kernel: [ 7290.634424] R10: 
88007972a6d8 R11: 88007972a6d8 R12: 
Apr  7 17:39:29 alexdell2-wheezy kernel: [ 7290.634484] R13: 
 R14: fffe57e2fffe5776 R15: 880116877820
Apr  7 17:39:29 alexdell2-wheezy kernel: [ 7290.634545] FS:  
7f2b8c238760() GS:88011fc0() knlGS:
Apr  7 17:39:29 alexdell2-wheezy kernel: [ 7290.634615] CS:  0010 DS: 
 ES:  CR0: 80050033
Apr  7 17:39:29 alexdell2-wheezy kernel: [ 7290.634664] CR2: 
7f2b8a913f50 CR3: 4dd1a000 CR4: 06f0
Apr  7 17:39:29 alexdell2-wheezy kernel: [ 7290.634724] DR0: 
 DR1:  DR2: 
Apr  7 17:39:29 alexdell2-wheezy kernel: [ 7290

Re: Kernel Panic

[Camaleón]

On Fri, 06 Jul 2012 15:08:18 +0530, Harshad Joshi wrote:

(please, no html posts, thanks...)

> I saw a very strange error while installing debian cd -
> 
> kernel panic - not syncing vfs unable to mount root fs on unknown block
> (254,6)
> 
> What might be the reason for this error? !!!

I've never seen it before :-?

You can:

1/ Check the validity of the original ISO file checksum
2/ Try to install from USB stick instead

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jt70pg$339$1...@dough.gmane.org

Re: Kernel Panic

[Harshad Joshi]

i am testing it on a dell vostro running Ubuntu 10.10 and Oracle
Virtualbox..i havent tested it on real machine as yet..

the same iso runs well on older debian lenny and Virtualbox

On Fri, Jul 6, 2012 at 4:09 PM, Kirill Sotnikov <
kirill.sotni...@maxifier.com> wrote:

> What motherboard do u use?
> Kirill Sotnikov
> Maxifier, Inc.
>
> phone: +79179468634
> skype: wlan1024
>
>
>
>
> On Fri, Jul 6, 2012 at 1:38 PM, Harshad Joshi wrote:
>
>> I saw a very strange error while installing debian cd -
>>
>> kernel panic - not syncing vfs unable to mount root fs on unknown block
>> (254,6)
>>
>> What might be the reason for this error? !!!
>>
>>
>> --
>> Harshad Joshi
>>
>>
>>
>


-- 
Harshad Joshi

Kernel Panic

[Harshad Joshi]

I saw a very strange error while installing debian cd -

kernel panic - not syncing vfs unable to mount root fs on unknown block
(254,6)

What might be the reason for this error? !!!


-- 
Harshad Joshi

Re: 3.2.0-3-686-pae kernel doesn't boot, kernel panic

[Brian]

On Fri 06 Jul 2012 at 03:23:33 -0700, John Magolske wrote:

> I just installed 3.2.0-3-686-pae, but got a kernel panic when trying
> to boot with it. As transcribed from my phone-camera "screenshot"
> (there are 10 more lines of output I can transcribe if that'd help):
> 
> [ 0.987169] Kernel panic - not syncing : VFS: Unable to mount root
> fs on unknown block(0,0)
> 
> Any thoughts on why this kernel isn't working?

Not any more than might come from a search with the error message you
have. Purge and reinstall the new kernel? Generate a new initrd? Have a
look and see what you think.

> Fortunately I was able to re-boot by selecting 3.2.0-2-686-pae from
> the Grub menu. This kernel had been installed explicitly by name:
> 
> # aptitude install linux-image-3.2.0-2-686-pae
> 
> Whereas 3.2.0-3-686-pae was installed using the linux-image-686-pae
> meta-package:
> 
> # aptitude install linux-image-686-pae
> 
> So something else I'm wondering...if I had initially installed
> 3.2.0-2-686-pae using the meta-package instead, would my recent
> upgrade to 3.2.0-3-686-pae using that same meta-package have removed
> 3.2.0-2-686-pae?

No. Which was fortunate for you. :)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120705204002.GG28931@desktop

3.2.0-3-686-pae kernel doesn't boot, kernel panic

[John Magolske]

Hi,

I just installed 3.2.0-3-686-pae, but got a kernel panic when trying
to boot with it. As transcribed from my phone-camera "screenshot"
(there are 10 more lines of output I can transcribe if that'd help):

    [ 0.987169] Kernel panic - not syncing : VFS: Unable to mount root
fs on unknown block(0,0)

Any thoughts on why this kernel isn't working?

Fortunately I was able to re-boot by selecting 3.2.0-2-686-pae from
the Grub menu. This kernel had been installed explicitly by name:

# aptitude install linux-image-3.2.0-2-686-pae

Whereas 3.2.0-3-686-pae was installed using the linux-image-686-pae
meta-package:

# aptitude install linux-image-686-pae

So something else I'm wondering...if I had initially installed
3.2.0-2-686-pae using the meta-package instead, would my recent
upgrade to 3.2.0-3-686-pae using that same meta-package have removed
3.2.0-2-686-pae?

% apt-show-versions linux-image-3.2.0-2-686-pae
linux-image-3.2.0-2-686-pae 3.2.20-1 installed:
No available version in archive

% apt-show-versions linux-image-3.2.0-3-rt-686-pae
linux-image-3.2.0-3-rt-686-pae/sid uptodate 3.2.21-3

% apt-show-versions linux-image-686-pae
linux-image-686-pae/sid uptodate 3.2+45

This is up-to-date Sid on an X200s ThinkPad.

John

-- 
John Magolske
http://B79.net/contact


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120706102333.gb10...@s70206.gridserver.com

Re: How do I debug kernel panic that occurs while running X?

[Brendon Higgins]

Hi,

Jason Heeris wrote (Sun March 4, 2012):
> The most watertight way I know of to capture kernel
> output is a serial port and another computer. If, by any chance, you
> have one on your machine

Not really an option (at least, not an easy one), I'm afraid. I only have two 
machines, and neither of them have serial ports. Rendered obsolete, indeed.

Sven Joachim wrote (Sun March 4, 2012):
> Either log in via ssh if that is still possible,

The computer has gone well beyond the point of responding to anything coming 
in over the network by the time it has frozen.

> or use netconsole to capture kernel messages.

Thanks for the links. This looked promising, but I cannot get it to function. 
I can get the problem machine connected to a netbook successfully (I can talk 
between them over UDP using netcat). However, netconsole refuses to transmit 
any messages. I install the module just as the article you linked to suggests, 
and it appears to be correct when I see it logged in dmesg:
[103337.293616] netconsole: local port 6665
[103337.293626] netconsole: local IP 0.0.0.0
[103337.293632] netconsole: interface 'eth0'
[103337.293637] netconsole: remote port 
[103337.293642] netconsole: remote IP 192.168.0.1
[103337.293646] netconsole: remote ethernet address ff:ff:ff:ff:ff:ff
[103337.293654] netconsole: local IP 192.168.0.2
[103337.293754] console [netcon0] enabled
[103337.293762] netconsole: network logging started
But this doesn't seem to work - there's just nothing transmitted. I can't even 
get it to send messages to a netcat listener on the same machine.

Have you (or anyone) found this approach works? Is there something I'm 
missing?

Thanks for your help so far.

Peace,
Brendon


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201203041717.11587.blhigg...@gmail.com

Re: How do I debug kernel panic that occurs while running X?

[Sven Joachim]

On 2012-03-04 09:16 +0100, Jason Heeris wrote:

> On 4 March 2012 01:28, Brendon Higgins  wrote:
>> Any more ideas? As I said, I tried getting kdump working but have been having
>> trouble getting it to behave.
>
> One more thought, but it's a bit of a long shot as to whether you have
> the equipment. The most watertight way I know of to capture kernel
> output is a serial port and another computer. If, by any chance, you
> have one on your machine, edit /etc/defaults/grub to include
> console=ttyS0,155200n1 (or whatever speed you like) on the kernel boot
> line. You'll also need another machine with either a serial port or a
> USB-serial adapter, making it half as likely that this will help you
> :P
>
> Of course, most computers these days (*ahem*) don't have serial ports.
> *Maybe* a USB-serial adapter will work for the target machine too...
> although this requires an extra level of redirection on the part of
> the kernel, and may not be as foolproof, so I wouldn't spend the money
> if you don't already have one (or, in fact, two).
>
> Other than that, I'm out of ideas. Hopefully someone else on this list
> has an idea that doesn't require technology that was rendered obsolete
> for most people by 1995...

Either log in via ssh if that is still possible, or use netconsole to
capture kernel messages.

Sven


http://www.kernel.org/doc/Documentation/networking/netconsole.txt
http://blog.mraw.org/2010/11/08/Debugging_using_netconsole/


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87eht84p3v@turtle.gmx.de

Re: How do I debug kernel panic that occurs while running X?

[Jason Heeris]

On 4 March 2012 01:28, Brendon Higgins  wrote:
> Any more ideas? As I said, I tried getting kdump working but have been having
> trouble getting it to behave.

One more thought, but it's a bit of a long shot as to whether you have
the equipment. The most watertight way I know of to capture kernel
output is a serial port and another computer. If, by any chance, you
have one on your machine, edit /etc/defaults/grub to include
console=ttyS0,155200n1 (or whatever speed you like) on the kernel boot
line. You'll also need another machine with either a serial port or a
USB-serial adapter, making it half as likely that this will help you
:P

Of course, most computers these days (*ahem*) don't have serial ports.
*Maybe* a USB-serial adapter will work for the target machine too...
although this requires an extra level of redirection on the part of
the kernel, and may not be as foolproof, so I wouldn't spend the money
if you don't already have one (or, in fact, two).

Other than that, I'm out of ideas. Hopefully someone else on this list
has an idea that doesn't require technology that was rendered obsolete
for most people by 1995...

— Jason


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CA+Zd3Fc6Y7SjN_RafobOV4NJ819wR=6kjg0jaf2kxzbysfg...@mail.gmail.com

Re: How do I debug kernel panic that occurs while running X?

[Brendon Higgins]

Hi again,

Charles Krinke wrote (Thu March 1, 2012):
> On the next boot, /var/log/messages shoild contain the last printk's from
> the kernel which would include any panic.

Thanks. I'd already checked there, though, and no dice. The log just skips 
from the last innocuous kernel message to messages about the next boot. 
Nothing about what caused the reboot to be necessary.

Jason Heeris wrote (Fri March 2, 2012):
> I've had problems with write caching causing the last few messages to
> be lost after a panic*, so if you don't see anything suspicious, maybe
> turn off write caching with 'hdparm -W 0 /dev/whatever' for long
> enough to reproduce the crash. Just in case.

Thanks for the tip. I gave that a try using the manual invocation of a kernel 
panic (i.e., echo c > /proc/sysrq-trigger) but I still get nothing in 
/var/log/messages about this event. So, I'm doubtful this'll work when a real 
panic strikes, unfortunately.

FWIW, at the moment I'm running the kernel in testing, but this has been a 
problem since back about 2.6.38 or 39. (I even tried doing a git bisection at 
one point, but being an intermittent problem it's difficult to determine when a 
particular commit doesn't exhibit it - I think I screwed it up at some point.)

Any more ideas? As I said, I tried getting kdump working but have been having 
trouble getting it to behave.

Peace,
Brendon


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201203031228.44898.blhigg...@gmail.com

Re: How do I debug kernel panic that occurs while running X?

[Jason Heeris]

On 2 March 2012 12:50, Charles Krinke  wrote:
> So, one should be able to tail /var/log messages and see what the kernel did
> at the time of the freeze.

I've had problems with write caching causing the last few messages to
be lost after a panic*, so if you don't see anything suspicious, maybe
turn off write caching with 'hdparm -W 0 /dev/whatever' for long
enough to reproduce the crash. Just in case.

* This was really only a problem because I was using a flash-based
drive (not USB, but for an embedded system) with *really* aggressive
caching. I don't know how bad the problem might be on a more ordinary
drive.

— Jason


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/ca+zd3fewattbjkp1km6armnkuhjmqfqce8cj3aaurf2dbjb...@mail.gmail.com

Re: How do I debug kernel panic that occurs while running X?

[Charles Krinke]

On the next boot, /var/log/messages shoild contain the last printk's from
the kernel which would include any panic.

So, one should be able to tail /var/log messages and see what the kernel
did at the time of the freeze.

Remembdr that the fresh boot is appendex to /var/log/messages, so you need
to scroll back a hundred lines or so.

Charles
On Mar 1, 2012 8:41 PM, "Brendon Higgins"  wrote:

> Hi list,
>
> For the better part of a year, now, something has been causing my machine
> to
> freeze. The mouse stops moving on the screen, pressing any key (including
> keys
> that should toggle lights) does nothing. The freezes are intermittent,
> without
> warning, and I've been unable to determine if there is any particular
> cause.
>
> I think the kernel is panicking, but I can't tell for sure. I don't think
> it
> caused by my hardware, either, because a Windows 7 install (Wintendo)
> seems to
> operate fine. The problem has never happened while I've been using the
> console,
> mostly because I'm there very rarely and I do the vast majority of my work
> in
> X. It's a desktop machine, after all.
>
> If it weren't for the fact of X being in the way when this happens, I
> might be
> far closer to finding the root cause of the problem I'm seeing. But the
> fact
> that I am unable to get any information at all from the kernel when the
> freeze
> occurs means I haven't been able to get anywhere with it in all this time.
> And
> yet it happens about once every few days. It's terrifically frustrating.
>
> I tried to get kdump working. I got as far as getting kexec running, and
> kdump
> claims to successfully load its kernel, but when I either manually cause a
> test panic or the bug happens, the kernel fails to start new, and so kdump
> never gets a chance to do its thing. kexec works fine to perform a regular
> restart the machine, though - which is irritating, actually, because it
> gets
> in the way when I wish to reboot into Wintendo.
>
> This issue is actually beginning to cause me some distress. There must be a
> way to extract panic info when X is running - how would the graphics driver
> writers debug things, otherwise?
>
> So does anyone have any suggestions as to how I can make some progress on
> diagnosing this?
>
> I'd appreciate being CC'd on replies, as I'm not sub'd to the list. Thanks!
>
> Peace,
> Brendon
>
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive: http://lists.debian.org/201203012323.50867.blhigg...@gmail.com
>
>

How do I debug kernel panic that occurs while running X?

[Brendon Higgins]

Hi list,

For the better part of a year, now, something has been causing my machine to 
freeze. The mouse stops moving on the screen, pressing any key (including keys 
that should toggle lights) does nothing. The freezes are intermittent, without 
warning, and I've been unable to determine if there is any particular cause.

I think the kernel is panicking, but I can't tell for sure. I don't think it 
caused by my hardware, either, because a Windows 7 install (Wintendo) seems to 
operate fine. The problem has never happened while I've been using the console, 
mostly because I'm there very rarely and I do the vast majority of my work in 
X. It's a desktop machine, after all.

If it weren't for the fact of X being in the way when this happens, I might be 
far closer to finding the root cause of the problem I'm seeing. But the fact 
that I am unable to get any information at all from the kernel when the freeze 
occurs means I haven't been able to get anywhere with it in all this time. And 
yet it happens about once every few days. It's terrifically frustrating.

I tried to get kdump working. I got as far as getting kexec running, and kdump 
claims to successfully load its kernel, but when I either manually cause a 
test panic or the bug happens, the kernel fails to start new, and so kdump 
never gets a chance to do its thing. kexec works fine to perform a regular 
restart the machine, though - which is irritating, actually, because it gets 
in the way when I wish to reboot into Wintendo.

This issue is actually beginning to cause me some distress. There must be a 
way to extract panic info when X is running - how would the graphics driver 
writers debug things, otherwise?

So does anyone have any suggestions as to how I can make some progress on 
diagnosing this?

I'd appreciate being CC'd on replies, as I'm not sub'd to the list. Thanks!

Peace,
Brendon


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201203012323.50867.blhigg...@gmail.com

Re: Recent update of Xen packages causes kernel panic with HVM domU

[Stan Hoeppner]

On 11/9/2011 9:56 PM, David Howland wrote:
> On 11/9/2011 10:17 PM, Stan Hoeppner wrote:
>> On 11/9/2011 7:55 PM, David Howland wrote:
>>> 8<=
>>>   kernel:[ 1919.981706] general protection fault:  [#1] SMP
>>>   kernel:[ 1919.981714] last sysfs file: /sys/devices/vbd-3-832/uevent
>>>   kernel:[ 1919.981870] Stack:
>>>   kernel:[ 1919.981893] Call Trace:
>>>   kernel:[ 1919.982020] Code: ff 14 25 40 eb 47 81 65 8b 04 25 a8 e3 00
>>> 00 48 98 49 8b 94 c4 f0 02 00 00 8b 4a 18 89 4c 24 14 48 8b 1a 48 85 db
>>> 74 0c 8b 42 14<48>  8b 04 c3 48 89 02 eb 19 48 8b 4c 24 08 49 89 d0 44
>>> 89 ee 83
>>
>> Where's the call trace?
>>
> 
> Here's the full syslog dump:



See if you can fix it by backing these 3 out to the previous version you
had installed:

[UPGRADE] xen-hypervisor-4.0-amd64 4.0.1-2 -> 4.0.1-4
[UPGRADE] xen-utils-4.0 4.0.1-2 -> 4.0.1-4
[UPGRADE] xenstore-utils 4.0.1-2 -> 4.0.1-4

Post the circumstances/history and a copy of the error log to LKML and
the Xen list.  In the mean time, check your filesystems to make sure
none of your VM image files (or anyhting else) didn't get corrupted when
the power died, or as a result of the upgrade.  It would probably be a
good idea to check out your hardware as well.  Power outages often
included spikes and surges before it completely goes dark.  Assuming
you're jacked into a good quality known-to-be-working UPS, damage to the
machine, or storage array, is less likely to be a factor here.

-- 
Stan


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ebb50a0.30...@hardwarefreak.com

Re: Recent update of Xen packages causes kernel panic with HVM domU

[David Howland]

On 11/9/2011 10:17 PM, Stan Hoeppner wrote:

On 11/9/2011 7:55 PM, David Howland wrote:

8<=
  kernel:[ 1919.981706] general protection fault:  [#1] SMP
  kernel:[ 1919.981714] last sysfs file: /sys/devices/vbd-3-832/uevent
  kernel:[ 1919.981870] Stack:
  kernel:[ 1919.981893] Call Trace:
  kernel:[ 1919.982020] Code: ff 14 25 40 eb 47 81 65 8b 04 25 a8 e3 00
00 48 98 49 8b 94 c4 f0 02 00 00 8b 4a 18 89 4c 24 14 48 8b 1a 48 85 db
74 0c 8b 42 14<48>  8b 04 c3 48 89 02 eb 19 48 8b 4c 24 08 49 89 d0 44
89 ee 83


Where's the call trace?



Here's the full syslog dump:

Nov  9 16:45:32 rackable kernel: [ 1919.981706] general protection 
fault:  [#1] SMP
Nov  9 16:45:32 rackable kernel: [ 1919.981714] last sysfs file: 
/sys/devices/vbd-3-832/uevent

Nov  9 16:45:32 rackable kernel: [ 1919.981717] CPU 2
Nov  9 16:45:32 rackable kernel: [ 1919.981720] Modules linked in: tun 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack xt_physdev 
ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables 
x_tables cpufreq_powersave cpufreq_stats cpufreq_userspace 
cpufreq_conservative parport_pc ppdev lp parport nfsd lockd nfs_acl 
auth_rpcgss sunrpc exportfs xen_evtchn xenfs binfmt_misc bridge stp fuse 
loop ioatdma radeon ttm drm_kms_helper i2c_i801 drm i2c_algo_bit 
rng_core pcspkr dca evdev i2c_core i5000_edac edac_core i5k_amb psmouse 
serio_raw processor button acpi_processor shpchp pci_hotplug ext3 jbd 
mbcache dm_mod sd_mod crc_t10dif uhci_hcd ata_generic ata_piix ehci_hcd 
libata scsi_mod usbcore nls_base e1000e thermal thermal_sys [last 
unloaded: scsi_wait_scan]
Nov  9 16:45:32 rackable kernel: [ 1919.981816] Pid: 24, comm: xenwatch 
Not tainted 2.6.32-5-xen-amd64 #1 S5000PSL
Nov  9 16:45:32 rackable kernel: [ 1919.981819] RIP: 
e030:[]  [] 
__kmalloc_track_caller+0xcd/0x13c
Nov  9 16:45:32 rackable kernel: [ 1919.981829] RSP: 
e02b:8803ea52bb10  EFLAGS: 00010002
Nov  9 16:45:32 rackable kernel: [ 1919.981832] RAX:  
RBX: 331474c384d0f7d9 RCX: 0008
Nov  9 16:45:32 rackable kernel: [ 1919.981835] RDX: 880013216090 
RSI: 00d0 RDI: 0003
Nov  9 16:45:32 rackable kernel: [ 1919.981838] RBP: 0200 
R08: 80d0 R09: 8803ea52bdd7
Nov  9 16:45:32 rackable kernel: [ 1919.981841] R10:  
R11: 000186a0 R12: 8146bf10
Nov  9 16:45:32 rackable kernel: [ 1919.981843] R13: 00d0 
R14: 00d0 R15: 0008
Nov  9 16:45:32 rackable kernel: [ 1919.981851] FS: 
7fbc8fe9d700() GS:880013204000() knlGS:
Nov  9 16:45:32 rackable kernel: [ 1919.981854] CS:  e033 DS:  ES: 
 CR0: 8005003b
Nov  9 16:45:32 rackable kernel: [ 1919.981857] CR2: 7fbc8f747000 
CR3: 00030f11a000 CR4: 2660
Nov  9 16:45:32 rackable kernel: [ 1919.981861] DR0:  
DR1:  DR2: 
Nov  9 16:45:32 rackable kernel: [ 1919.981864] DR3:  
DR6: 0ff0 DR7: 0400
Nov  9 16:45:32 rackable kernel: [ 1919.981868] Process xenwatch (pid: 
24, threadinfo 8803ea52a000, task 8803ea4f3880)

Nov  9 16:45:32 rackable kernel: [ 1919.981870] Stack:
Nov  9 16:45:32 rackable kernel: [ 1919.981872]  8803ea4f3880 
81141305 000881044ced 0008
Nov  9 16:45:32 rackable kernel: [ 1919.981878] <0> 8803 
8803 0001 8803ea52bc28
Nov  9 16:45:32 rackable kernel: [ 1919.981885] <0> 41ed 
810c846f 0004 

Nov  9 16:45:32 rackable kernel: [ 1919.981893] Call Trace:
Nov  9 16:45:32 rackable kernel: [ 1919.981900]  [] ? 
sysfs_new_dirent+0x2a/0xf7
Nov  9 16:45:32 rackable kernel: [ 1919.981906]  [] ? 
kstrdup+0x2b/0x40
Nov  9 16:45:32 rackable kernel: [ 1919.981910]  [] ? 
sysfs_new_dirent+0x2a/0xf7
Nov  9 16:45:32 rackable kernel: [ 1919.981914]  [] ? 
create_dir+0x2d/0x7c
Nov  9 16:45:32 rackable kernel: [ 1919.981918]  [] ? 
sysfs_create_dir+0x35/0x4a
Nov  9 16:45:32 rackable kernel: [ 1919.981924]  [] ? 
kobject_get+0x12/0x17
Nov  9 16:45:32 rackable kernel: [ 1919.981928]  [] ? 
kobject_add_internal+0xcb/0x181
Nov  9 16:45:32 rackable kernel: [ 1919.981932]  [] ? 
kobject_add+0x74/0x7c
Nov  9 16:45:32 rackable kernel: [ 1919.981943]  [] ? 
xen_force_evtchn_callback+0x9/0xa
Nov  9 16:45:32 rackable kernel: [ 1919.981948]  [] ? 
check_events+0x12/0x20
Nov  9 16:45:32 rackable kernel: [ 1919.981952]  [] ? 
__kmalloc+0x12f/0x141
Nov  9 16:45:32 rackable kernel: [ 1919.981958]  [] ? 
device_private_init+0x13/0x45
Nov  9 16:45:32 rackable kernel: [ 1919.981963]  [] ? 
device_add+0xce/0x537
Nov  9 16:45:32 rackable kernel: [ 1919.981969]  [] ? 
backend_bus_id+0x10f/0x132
Nov  9 16:45:32 rackable kernel: [ 1919.981973]  [] ? 
xenbus_probe_node+0x13b/0x1d4
Nov  9 16:45:32 rackable kernel: [ 1919.981977]  [] ? 
cmp_dev+0x0/0x39
Nov  9 16:45:32 rackabl

Re: Recent update of Xen packages causes kernel panic with HVM domU

[Stan Hoeppner]

On 11/9/2011 7:55 PM, David Howland wrote:
> Recently I lost power (along with much of New England) for eight days.
> When the juice started flowing again, I restarted my Xen server (Debian
> Squeeze, dual Xeon (8 cores), 16GB RAM), which came up fine but had a
> pile of package updates pending...



> 8<=
>  kernel:[ 1919.981706] general protection fault:  [#1] SMP
>  kernel:[ 1919.981714] last sysfs file: /sys/devices/vbd-3-832/uevent
>  kernel:[ 1919.981870] Stack:
>  kernel:[ 1919.981893] Call Trace:
>  kernel:[ 1919.982020] Code: ff 14 25 40 eb 47 81 65 8b 04 25 a8 e3 00
> 00 48 98 49 8b 94 c4 f0 02 00 00 8b 4a 18 89 4c 24 14 48 8b 1a 48 85 db
> 74 0c 8b 42 14 <48> 8b 04 c3 48 89 02 eb 19 48 8b 4c 24 08 49 89 d0 44
> 89 ee 83

Where's the call trace?

-- 
Stan


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ebb4248.9010...@hardwarefreak.com

Recent update of Xen packages causes kernel panic with HVM domU

[David Howland]

Recently I lost power (along with much of New England) for eight days. 
When the juice started flowing again, I restarted my Xen server (Debian 
Squeeze, dual Xeon (8 cores), 16GB RAM), which came up fine but had a 
pile of package updates pending...


===
[UPGRADE] libavcodec52 4:0.5.4-1 -> 4:0.5.5-1
[UPGRADE] libavformat52 4:0.5.4-1 -> 4:0.5.5-1
[UPGRADE] libavutil49 4:0.5.4-1 -> 4:0.5.5-1
[UPGRADE] libnss3-1d 3.12.8-1+squeeze3 -> 3.12.8-1+squeeze4
[UPGRADE] libpostproc51 4:0.5.4-1 -> 4:0.5.5-1
[UPGRADE] libpq5 8.4.8-0squeeze2 -> 8.4.9-0squeeze1+b1
[UPGRADE] libswscale0 4:0.5.4-1 -> 4:0.5.5-1
[UPGRADE] libxenstore3.0 4.0.1-2 -> 4.0.1-4
[UPGRADE] postgresql 8.4.8-0squeeze2 -> 8.4.9-0squeeze1
[UPGRADE] postgresql-8.4 8.4.8-0squeeze2 -> 8.4.9-0squeeze1+b1
[UPGRADE] postgresql-client 8.4.8-0squeeze2 -> 8.4.9-0squeeze1
[UPGRADE] postgresql-client-8.4 8.4.8-0squeeze2 -> 8.4.9-0squeeze1+b1
[UPGRADE] postgresql-contrib 8.4.8-0squeeze2 -> 8.4.9-0squeeze1
[UPGRADE] postgresql-contrib-8.4 8.4.8-0squeeze2 -> 8.4.9-0squeeze1+b1
[UPGRADE] postgresql-doc 8.4.8-0squeeze2 -> 8.4.9-0squeeze1
[UPGRADE] postgresql-doc-8.4 8.4.8-0squeeze2 -> 8.4.9-0squeeze1
[UPGRADE] tzdata 2011m-0squeeze1 -> 2011n-0squeeze1
[UPGRADE] tzdata-java 2011m-0squeeze1 -> 2011n-0squeeze1
[UPGRADE] xen-hypervisor-4.0-amd64 4.0.1-2 -> 4.0.1-4
[UPGRADE] xen-utils-4.0 4.0.1-2 -> 4.0.1-4
[UPGRADE] xenstore-utils 4.0.1-2 -> 4.0.1-4
===

I did an "aptitude safe-upgrade" without even really looking at it.  At 
the time, I had an HVM domU running.  The upgrade crashed the system. 
I'm pretty sure it crashed while configuring the 
xen-hypervisor-4.0-amd64 package.  When I brought it back up, I ran a 
"dpkg --configure -a" to finish the job.


However, now, when I try to use my Windows HVM, I always get a kernel 
panic dealing with the vbd.  For example...


8<=
 kernel:[ 1919.981706] general protection fault:  [#1] SMP
 kernel:[ 1919.981714] last sysfs file: /sys/devices/vbd-3-832/uevent
 kernel:[ 1919.981870] Stack:
 kernel:[ 1919.981893] Call Trace:
 kernel:[ 1919.982020] Code: ff 14 25 40 eb 47 81 65 8b 04 25 a8 e3 00 
00 48 98 49 8b 94 c4 f0 02 00 00 8b 4a 18 89 4c 24 14 48 8b 1a 48 85 db 
74 0c 8b 42 14 <48> 8b 04 c3 48 89 02 eb 19 48 8b 4c 24 08 49 89 d0 44 
89 ee 83


 kernel:[ 1920.014542] general protection fault:  [#2] SMP
 kernel:[ 1920.014550] last sysfs file: /sys/devices/vbd-3-832/uevent
 kernel:[ 1920.014729] Stack:
 kernel:[ 1920.014752] Call Trace:
 kernel:[ 1920.014836] Code: ff 14 25 40 eb 47 81 65 8b 04 25 a8 e3 00 
00 48 98 49 8b 94 c4 f0 02 00 00 8b 4a 18 89 4c 24 14 48 8b 1a 48 85 db 
74 0c 8b 42 14 <48> 8b 04 c3 48 89 02 eb 19 48 8b 4c 24 08 49 89 d0 44 
89 ee 83

8<=
Then the system destabilizes.

I have a pretty common setup.  I can't be the only one!
What the heck happened with those updates?!?  Please help me out!

thanks,
-d


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4ebb2f08.4060...@fastmail.fm

Re: creaing new 3.0.4 kernel in squeeze --kernel panic

[Sian Mountbatten]

poenik...@operamail.com wrote:

> On Oct 30, 8:10 pm, Hugo Vanwoerkom  wrote:

>
> I suspect that my configuration of the kernel is at fault, but where
> should I start looking for problems?
> 
> 
Problem solved by installing wheezy which comes with a 3.0.0 kernel.
Thank you all for your time and patience.
-- 
Sian


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/j91888$c88$3...@speranza.aioe.org

Re: creaing new 3.0.4 kernel in squeeze --kernel panic

[Sian Mountbatten]

Arnt Karlsen wrote:

> On Mon, 31 Oct 2011 13:56:46 -0700 (PDT), poenik...@operamail.com 
wrote
> in message
> <6a9c6581-5fbb-4848-9d92-81bf0dbce...@j36g2000prh.googlegroups.com>:
> 
>> On Oct 31, 7:20 pm, "poenik...@operamail.com"
>>  wrote:
>> > On Oct 31, 12:40 am, Stephen Powell  wrote:
>> > > Also, I recommend that you read
>> >
>> > > http://users.wowway.com/~zlinuxman/Kernel.htm
>> >
>> > > for a fairly comprehensive tutorial on kernel building in Debian
>> > > which documents many common "gotchas" in kernel building.  For
>> > > example, there is a patch to kernel-package which is needed in
>> > > some circumstances when building a version 3 kernel with
>> > > make-kpkg.  The patch is documented on the above web page.  And,
>> > > depending on which boot loader you use, you may need to install
>> > > some hook scripts when using a custom kernel with Squeeze and
>> > > later releases.  This is also documented on the above web page.
>> >
>> > > --
>> > > .''`. Stephen Powell
>> > > : :'  :
>> > > `. `'`
>> >
>> > I followed the instructions given in Kernel.htm and built a kernel
>> > from the source tree I had
>> > downloaded fromwww.kernel.orgafter issuing make-kpkg debian. I 
also
>> > patched kernel-package
>> > using the patch file (linuxv3.diff) mentioned on the web page.
>> >
>> > I also used make localmodconfig to greatly reduce the number of
>> > modules actually compiled.
>> > Compiling the kernel took 34 mins on my 1.6GHz laptop.
>> >
>> > I installed the kernel using dpkg as root, checked that an 
initramfs
>> > image had been created, closed down
>> > and rebooted.
>> >
>> > The kernel loaded, entered runlevel 2, but commands that tried to
>> > write to the fs failed because it was
>> > still readonly. The kernel finally hung with nfsd. ctrl-alt-del
>> > successfully rebooted. I shall recompile
>> > the kernel without NFS support because I don't need it.
>> 
>> I removed NFS stuff and recompiled the kernel. I also removed the
>> packages nfs-kernel-server and
>> nfs-common.
>> 
>> After rebooting with the new kernel, it loaded, hung at points and
>> eventually gave me a tty login
>> prompt. I could login as sian as well as root, but the file system 
was
>> still read-only. I suspect that
>> GNOME has to be able to write to the fs so that is why I only got a
>> tty prompt.
>> 
>> Some messages emitted by the kernel when loading:
>> 
-
>> Can't open or create /var/run/syslogd.pid
>> Unknown hardware ThinkPad EC
>> touch: setting times of /var/lib/sudo: Read-only file system
>> 
--
>> What do I do next?
> 
> ..remount your disk read-write.
> 
>> At least the kernel loads and gives me a prompt. I
>> don't understand why the
>> file system is still read-only.
> 
> ..could be _anything_ from a bad disk to a kernel config bug.
> My reading of your NFS "hang" is you should have patient enough
> to give it time to time out, at least once. (5 or 15 minutes?)
> 
> ..try set up a syslog host on your lan and point your
> 3.0.4 box' syslog there, and post the url to it if you
> find funny errors etc things that warrants further fun.
> 
>> 
> 
> 
Problem solved by installing wheezy.
-- 
Sian


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/j91811$c88$2...@speranza.aioe.org

Re: creaing new 3.0.4 kernel in squeeze --kernel panic

[Sian Mountbatten]

Stephen Powell wrote:

> On Tue, 01 Nov 2011 21:02:56 -0400 (EDT), Sian Mountbatten wrote:
>> 
>> Thank you all for your helpful advice and info.
>> 
>> I am giving up on squeeze because I get so many problems with 
building
>> a series 3 kernel. I tried to download a kernel image from wheezy, 
but
>> got problems when I tried to install the Debian package. I tried
>> downloading and installing the dependencies, but putting a wheezy
>> kernel onto a squeeze system did not work. So I have now downloaded
>> the first DVD iso for wheeze and I shall try to install a series
>> 3 kernel for that release.
>> 
>> Again, thank you all for your help.
> 
> I hope you have better luck with Wheezy.  I am running a custom-built
> 3.0.0 kernel on Wheezy right now, and I am not having any problems.
> There are often dependencies between the kernel releases and some
> other packages closely related to the kernel, such as initramfs-
tools,
> libc*, udev, etc.  I suspect you will do better with Wheezy.
> 
I have now successfully installed wheezy on both my desktop and my
laptop. I am more than satisfied with the KDE desktop and all the
apps which are available.

Thank you all for your time and interest.
-- 
Sian


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/j917ug$c88$1...@speranza.aioe.org

Re: creaing new 3.0.4 kernel in squeeze --kernel panic

[Stephen Powell]

On Tue, 01 Nov 2011 21:02:56 -0400 (EDT), Sian Mountbatten wrote:
> 
> Thank you all for your helpful advice and info.
> 
> I am giving up on squeeze because I get so many problems with building
> a series 3 kernel. I tried to download a kernel image from wheezy, but
> got problems when I tried to install the Debian package. I tried
> downloading and installing the dependencies, but putting a wheezy
> kernel onto a squeeze system did not work. So I have now downloaded
> the first DVD iso for wheeze and I shall try to install a series
> 3 kernel for that release.
> 
> Again, thank you all for your help.

I hope you have better luck with Wheezy.  I am running a custom-built
3.0.0 kernel on Wheezy right now, and I am not having any problems.
There are often dependencies between the kernel releases and some
other packages closely related to the kernel, such as initramfs-tools,
libc*, udev, etc.  I suspect you will do better with Wheezy.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/332873274.481855.1320198967497.javamail.r...@md01.wow.synacor.com

Re: creaing new 3.0.4 kernel in squeeze --kernel panic

[Stephen Powell]

On Tue, 01 Nov 2011 20:43:12 -0400 (EDT), Walter Hurry wrote:
> 
> But my (single internal) hard disk is always /dev/sda, and my two 
> external USB disks are always /dev/sdb and /dev/sdc.  So what difference 
> does it make?

You mean that *so far* your internal hard disk is always /dev/sda
and *so far* your external USB disks are always /dev/sdb and /dev/sdc.
There are no guarantees that it will always be so.

On my system, I've noticed that my single internal hard disk is
usually /dev/sda and my CD-ROM drive is usually /dev/sdb.
But if I boot my system from a rescue CD, the CD-ROM drive
is usually /dev/sda and the hard disk is usually /dev/sdb.
But I cannot guarantee that the hard disk will always be /dev/sda
even if I boot from the hard disk every time.
It's all timing dependent.  Devices are not necessarily discovered
in any particular order anymore.  It is safest to use UUIDs
or LABELs.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1532239075.481697.1320198540616.javamail.r...@md01.wow.synacor.com

Re: creaing new 3.0.4 kernel in squeeze --kernel panic

[Sian Mountbatten]

On Wed, 02 Nov 2011 01:10:02 +0100, Stephen Powell wrote:

> On Tue, 01 Nov 2011 19:46:13 -0400 (EDT), Walter Hurry wrote:
>> On Tue, 01 Nov 2011 19:43:20 -0400, Stephen Powell wrote:
>>> 
>>> It is important that you *not* use traditional device nomenclature,
>>> such as
>>> 
>>>   /dev/hda1
>>>   /dev/sda1
>> 
>> Why?
> 
> Two reasons.  First, whether an IDE hard disk shows up as /dev/hda,
> /dev/hdb, etc. or /dev/sda, /dev/sdb, etc. depends on which drivers are
> being used.  For example, the 2.6.32-3-686 kernel and earlier ones use
> the traditional IDE drivers, with device names /dev/hda, /dev/hdb, etc.
> The 2.6.32-5-686 and later kernels use the libata SCSI emulation
> drivers, with device names /dev/sda, /dev/sdb, etc.
> 
> Second, the devices are not necessarily discovered in the same order
> every time with newer kernels.  Let's say you have a system with one
> hard disk and one CD-ROM drive.  On one boot, your hard disk may be
> assigned device name /dev/sda and the CD-ROM drive may be assigned the
> device name /dev/sdb.  But on the next boot, it is possible that the
> CD-ROM drive may be assigned the device name /dev/sda and the hard disk
> may be assigned the device name /dev/sdb.  You can never be sure. By
> using UUIDs or LABELs, you will always get the same physical partition
> mounted as the root file system every time, regardless of what its
> device name happens to be in the current boot.  The same applies to
> non-root file sytems in /etc/fstab (i.e. /boot, /home, etc.)
> 
> --
>   .''`. Stephen Powell
>  : :'  :
>  `. `'`
>`-

Thank you all for your helpful advice and info.

I am giving up on squeeze because I get so many problems with building
a series 3 kernel. I tried to download a kernel image from wheezy, but
got problems when I tried to install the Debian package. I tried
downloading and installing the dependencies, but putting a wheezy
kernel onto a squeeze system did not work. So I have now downloaded
the first DVD iso for wheeze and I shall try to install a series
3 kernel for that release.

Again, thank you all for your help.
-- 
Sian Mountbatten


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/j8q4s0$m0k$1...@dont-email.me

Re: creaing new 3.0.4 kernel in squeeze --kernel panic

[Walter Hurry]

On Tue, 01 Nov 2011 20:00:54 -0400, Stephen Powell wrote:

> On Tue, 01 Nov 2011 19:46:13 -0400 (EDT), Walter Hurry wrote:
>> On Tue, 01 Nov 2011 19:43:20 -0400, Stephen Powell wrote:
>>> 
>>> It is important that you *not* use traditional device nomenclature,
>>> such as
>>> 
>>>   /dev/hda1 /dev/sda1
>> 
>> Why?
> 
> Two reasons.  First, whether an IDE hard disk shows up as /dev/hda,
> /dev/hdb, etc. or /dev/sda, /dev/sdb, etc. depends on which drivers are
> being used.  For example, the 2.6.32-3-686 kernel and earlier ones use
> the traditional IDE drivers, with device names /dev/hda, /dev/hdb, etc.
> The 2.6.32-5-686 and later kernels use the libata SCSI emulation
> drivers, with device names /dev/sda, /dev/sdb, etc.
> 
> Second, the devices are not necessarily discovered in the same order
> every time with newer kernels.  Let's say you have a system with one
> hard disk and one CD-ROM drive.  On one boot, your hard disk may be
> assigned device name /dev/sda and the CD-ROM drive may be assigned the
> device name /dev/sdb.  But on the next boot, it is possible that the
> CD-ROM drive may be assigned the device name /dev/sda and the hard disk
> may be assigned the device name /dev/sdb.  You can never be sure.
> By using UUIDs or LABELs, you will always get the same physical
> partition mounted as the root file system every time, regardless of what
> its device name happens to be in the current boot.  The same applies to
> non-root file sytems in /etc/fstab (i.e. /boot, /home, etc.)

But my (single internal) hard disk is always /dev/sda, and my two 
external USB disks are always /dev/sdb and /dev/sdc. So what difference 
does it make?



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/j8q3n0$eor$1...@dough.gmane.org

Re: creaing new 3.0.4 kernel in squeeze --kernel panic

[Stephen Powell]

On Tue, 01 Nov 2011 19:46:13 -0400 (EDT), Walter Hurry wrote:
> On Tue, 01 Nov 2011 19:43:20 -0400, Stephen Powell wrote:
>> 
>> It is important that you *not* use traditional device nomenclature, such
>> as
>> 
>>   /dev/hda1
>>   /dev/sda1
> 
> Why?

Two reasons.  First, whether an IDE hard disk shows up as /dev/hda,
/dev/hdb, etc. or /dev/sda, /dev/sdb, etc. depends on which drivers
are being used.  For example, the 2.6.32-3-686 kernel and earlier ones
use the traditional IDE drivers, with device names /dev/hda, /dev/hdb, etc.
The 2.6.32-5-686 and later kernels use the libata SCSI emulation
drivers, with device names /dev/sda, /dev/sdb, etc.

Second, the devices are not necessarily discovered in the same order
every time with newer kernels.  Let's say you have a system with
one hard disk and one CD-ROM drive.  On one boot, your hard disk may
be assigned device name /dev/sda and the CD-ROM drive may be assigned
the device name /dev/sdb.  But on the next boot, it is possible that
the CD-ROM drive may be assigned the device name /dev/sda and the hard
disk may be assigned the device name /dev/sdb.  You can never be sure.
By using UUIDs or LABELs, you will always get the same physical partition
mounted as the root file system every time, regardless of what its
device name happens to be in the current boot.  The same applies to
non-root file sytems in /etc/fstab (i.e. /boot, /home, etc.)

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/544765130.478134.1320192054767.javamail.r...@md01.wow.synacor.com

Re: creaing new 3.0.4 kernel in squeeze --kernel panic

[Walter Hurry]

On Tue, 01 Nov 2011 19:43:20 -0400, Stephen Powell wrote:

> It is important that you *not* use traditional device nomenclature, such
> as
> 
>/dev/hda1 /dev/sda1

Why?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/j8q0c5$noi$1...@dough.gmane.org

Re: creaing new 3.0.4 kernel in squeeze --kernel panic

[Stephen Powell]

On Mon, 31 Oct 2011 14:54:37 -0400 (EDT), poenik...@operamail.com wrote:
> 
> I followed the instructions given in Kernel.htm and built a kernel
> from the source tree I had
> downloaded from www.kernel.org after issuing make-kpkg debian. I also
> patched kernel-package
> using the patch file (linuxv3.diff) mentioned on the web page.
> 
> I also used make localmodconfig to greatly reduce the number of
> modules actually compiled.
> Compiling the kernel took 34 mins on my 1.6GHz laptop.
> 
> I installed the kernel using dpkg as root, checked that an initramfs
> image had been created, closed down
> and rebooted.
> 
> The kernel loaded, entered runlevel 2, but commands that tried to
> write to the fs failed because it was
> still readonly. The kernel finally hung with nfsd. ctrl-alt-del
> successfully rebooted. I shall recompile
> the kernel without NFS support because I don't need it.

In a typical Debian boot, there are three stages for the root
file system.  In stage 1, the initial RAM file system is mounted
as the root (/) file system.  The boot loader loads the (mostly)
compressed kernel image and the compressed initial RAM file system
image into memory, then passes control to the kernel.  The boot
loader tells the kernel where the compressed initial RAM file system
image is by passing it's address to the kernel.
The kernel decompresses itself, decompresses the initial RAM file
system image, frees the memory associated with the compressed version
of the initial RAM file system, then mounts the uncompressed version
of the initial RAM file system as the root (/) file system.
For LILO, the "image" and "initrd" boot loader configuration records
specify the kernel image and initial RAM file system image to be
used, respectively.

In stage 2, once all modules needed to do I/O to the disk have
been loaded, as well as all modules needed to interpret the file system,
the permanent root file system is mounted.  Typically, it is mounted
read-only.  The location of the permanent root file system is passed
to the kernel via the kernel command line from parameters specified
in the boot loader configuration file.  For LILO, the "read-only"
and "root" boot loader configuration records specify this information.
The corresponding options passed on the kernel command line are
"ro" and "root".  Once the permanent root file system has been mounted
read-only, the uncompressed initial RAM file system image is freed from
memory.  Additional kernel modules are loaded at this stage, including
those specified in /etc/modules.  They are loaded from the permanent
root file system, still mounted read-only.

In stage 3, the permanent root file system is mounted read-write.
At this stage, the file system to use is specified by /etc/fstab.
Obviously, you must make sure that your boot loader configuration
file and /etc/fstab specify the same root file system.  It is important
that you *not* use traditional device nomenclature, such as

   /dev/hda1
   /dev/sda1

etc.  Generally, the newer the kernel, the less likely this is to work.
You should specify the root file system, both in the boot loader configuration
file and in /etc/fstab by using "UUID=xxx..." or "LABEL=xxx" specifications.

Since you seem to be having trouble at stage 3, the first thing I would
look at is /etc/fstab.  If you don't find any errors there, please
post your boot loader configuration file, /etc/fstab, and the kernel
boot messages.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1391569326.477490.1320191000468.javamail.r...@md01.wow.synacor.com

Re: creaing new 3.0.4 kernel in squeeze --kernel panic

[Stephen Powell]

On Mon, 31 Oct 2011 10:25:04 -0400 (EDT), Hugo Vanwoerkom wrote:
> Stephen Powell wrote:
>> I would recommend using something like "make localmodconfig" to strip
>> out drivers your hardware doesn't need.  There are many hidden
>> dependencies, such as SCSI support, that are not obvious.
>> ...
> That will definitely give you a bootable kernel but with the stock 
> Debian config, which is huge and gives you way more than you really need.
> IMO to get just the right kernel config is very tricky because it is an 
> trial and error thing. What would be handy is an IDE that records what 
> change you made and for what reason, so that it can be removed when your 
> hardware changes.

Perhaps you're thinking of "make oldconfig" or some other configuration
target.  "make localmodconfig" will definitely strip out modules that
are not in use by the current hardware.  There may be a few things that
are built-in to the kernel that could be eliminated, but most stuff
that is hardware-related is in a module by default, and "make localmodconfig"
will get you 99% of the way (or better) toward the minimal kernel
configuration for the current hardware.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1875441311.476634.1320189198947.javamail.r...@md01.wow.synacor.com

Re: creaing new 3.0.4 kernel in squeeze --kernel panic

[Arnt Karlsen]

On Mon, 31 Oct 2011 13:56:46 -0700 (PDT), poenik...@operamail.com wrote
in message
<6a9c6581-5fbb-4848-9d92-81bf0dbce...@j36g2000prh.googlegroups.com>:

> On Oct 31, 7:20 pm, "poenik...@operamail.com"
>  wrote:
> > On Oct 31, 12:40 am, Stephen Powell  wrote:
> > > Also, I recommend that you read
> >
> > >    http://users.wowway.com/~zlinuxman/Kernel.htm
> >
> > > for a fairly comprehensive tutorial on kernel building in Debian
> > > which documents many common "gotchas" in kernel building.  For
> > > example, there is a patch to kernel-package which is needed in
> > > some circumstances when building a version 3 kernel with
> > > make-kpkg.  The patch is documented on the above web page.  And,
> > > depending on which boot loader you use, you may need to install
> > > some hook scripts when using a custom kernel with Squeeze and
> > > later releases.  This is also documented on the above web page.
> >
> > > --
> > >   .''`.     Stephen Powell    
> > >  : :'  :
> > >  `. `'`
> >
> > I followed the instructions given in Kernel.htm and built a kernel
> > from the source tree I had
> > downloaded fromwww.kernel.orgafter issuing make-kpkg debian. I also
> > patched kernel-package
> > using the patch file (linuxv3.diff) mentioned on the web page.
> >
> > I also used make localmodconfig to greatly reduce the number of
> > modules actually compiled.
> > Compiling the kernel took 34 mins on my 1.6GHz laptop.
> >
> > I installed the kernel using dpkg as root, checked that an initramfs
> > image had been created, closed down
> > and rebooted.
> >
> > The kernel loaded, entered runlevel 2, but commands that tried to
> > write to the fs failed because it was
> > still readonly. The kernel finally hung with nfsd. ctrl-alt-del
> > successfully rebooted. I shall recompile
> > the kernel without NFS support because I don't need it.
> 
> I removed NFS stuff and recompiled the kernel. I also removed the
> packages nfs-kernel-server and
> nfs-common.
> 
> After rebooting with the new kernel, it loaded, hung at points and
> eventually gave me a tty login
> prompt. I could login as sian as well as root, but the file system was
> still read-only. I suspect that
> GNOME has to be able to write to the fs so that is why I only got a
> tty prompt.
> 
> Some messages emitted by the kernel when loading:
> -
> Can't open or create /var/run/syslogd.pid
> Unknown hardware ThinkPad EC
> touch: setting times of /var/lib/sudo: Read-only file system
> --
> What do I do next?

..remount your disk read-write.  

> At least the kernel loads and gives me a prompt. I
> don't understand why the
> file system is still read-only.

..could be _anything_ from a bad disk to a kernel config bug.
My reading of your NFS "hang" is you should have patient enough 
to give it time to time out, at least once. (5 or 15 minutes?) 

..try set up a syslog host on your lan and point your 
3.0.4 box' syslog there, and post the url to it if you 
find funny errors etc things that warrants further fun.

> 


-- 
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/2001151717.1dc35...@nb6.lan

Re: creaing new 3.0.4 kernel in squeeze --kernel panic

[poenik...@operamail.com]

On Oct 31, 7:20 pm, "poenik...@operamail.com"
 wrote:
> On Oct 31, 12:40 am, Stephen Powell  wrote:
> > Also, I recommend that you read
>
> >    http://users.wowway.com/~zlinuxman/Kernel.htm
>
> > for a fairly comprehensive tutorial on kernel building in Debian which
> > documents many common "gotchas" in kernel building.  For example, there
> > is a patch to kernel-package which is needed in some circumstances
> > when building a version 3 kernel with make-kpkg.  The patch is documented
> > on the above web page.  And, depending on which boot loader you use,
> > you may need to install some hook scripts when using a custom kernel
> > with Squeeze and later releases.  This is also documented on the
> > above web page.
>
> > --
> >   .''`.     Stephen Powell    
> >  : :'  :
> >  `. `'`
>
> I followed the instructions given in Kernel.htm and built a kernel
> from the source tree I had
> downloaded fromwww.kernel.orgafter issuing make-kpkg debian. I also
> patched kernel-package
> using the patch file (linuxv3.diff) mentioned on the web page.
>
> I also used make localmodconfig to greatly reduce the number of
> modules actually compiled.
> Compiling the kernel took 34 mins on my 1.6GHz laptop.
>
> I installed the kernel using dpkg as root, checked that an initramfs
> image had been created, closed down
> and rebooted.
>
> The kernel loaded, entered runlevel 2, but commands that tried to
> write to the fs failed because it was
> still readonly. The kernel finally hung with nfsd. ctrl-alt-del
> successfully rebooted. I shall recompile
> the kernel without NFS support because I don't need it.

I removed NFS stuff and recompiled the kernel. I also removed the
packages nfs-kernel-server and
nfs-common.

After rebooting with the new kernel, it loaded, hung at points and
eventually gave me a tty login
prompt. I could login as sian as well as root, but the file system was
still read-only. I suspect that
GNOME has to be able to write to the fs so that is why I only got a
tty prompt.

Some messages emitted by the kernel when loading:
-
Can't open or create /var/run/syslogd.pid
Unknown hardware ThinkPad EC
touch: setting times of /var/lib/sudo: Read-only file system
--
What do I do next? At least the kernel loads and gives me a prompt. I
don't understand why the
file system is still read-only.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/6a9c6581-5fbb-4848-9d92-81bf0dbce...@j36g2000prh.googlegroups.com

Re: creaing new 3.0.4 kernel in squeeze --kernel panic

[poenik...@operamail.com]

On Oct 31, 12:40 am, Stephen Powell  wrote:
> On Sun, 30 Oct 2011 14:24:28 -0400 (EDT), poenik...@operamail.com wrote:
>
> > I downloaded the source for kernel version 3.0.4 fromwww.kernel.org.
> > ...
> > I then ploughed through all the options, removing modules where I was
> > sure I did not have
> > the relevant hardware.
> > ...
> > I closed down squeeze, rebooted and chose the new 3.0.4 kernel. It
> > displayed an
> > error message (kernel panic) to the effect that it could not load the
> > root fs.
>
> > What have I done wrong?
>
> I would recommend using something like "make localmodconfig" to strip
> out drivers your hardware doesn't need.  There are many hidden
> dependencies, such as SCSI support, that are not obvious.
> Also, I recommend that you read
>
>    http://users.wowway.com/~zlinuxman/Kernel.htm
>
> for a fairly comprehensive tutorial on kernel building in Debian which
> documents many common "gotchas" in kernel building.  For example, there
> is a patch to kernel-package which is needed in some circumstances
> when building a version 3 kernel with make-kpkg.  The patch is documented
> on the above web page.  And, depending on which boot loader you use,
> you may need to install some hook scripts when using a custom kernel
> with Squeeze and later releases.  This is also documented on the
> above web page.
>
> --
>   .''`.     Stephen Powell    
>  : :'  :
>  `. `'`
I followed the instructions given in Kernel.htm and built a kernel
from the source tree I had
downloaded from www.kernel.org after issuing make-kpkg debian. I also
patched kernel-package
using the patch file (linuxv3.diff) mentioned on the web page.

I also used make localmodconfig to greatly reduce the number of
modules actually compiled.
Compiling the kernel took 34 mins on my 1.6GHz laptop.

I installed the kernel using dpkg as root, checked that an initramfs
image had been created, closed down
and rebooted.

The kernel loaded, entered runlevel 2, but commands that tried to
write to the fs failed because it was
still readonly. The kernel finally hung with nfsd. ctrl-alt-del
successfully rebooted. I shall recompile
the kernel without NFS support because I don't need it.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20a54e07-8ae8-4781-9d05-05ff49ec6...@q35g2000prh.googlegroups.com

Re: creaing new 3.0.4 kernel in squeeze --kernel panic

[Hugo Vanwoerkom]

Stephen Powell wrote:

On Sun, 30 Oct 2011 14:24:28 -0400 (EDT), poenik...@operamail.com wrote:

I downloaded the source for kernel version 3.0.4 from www.kernel.org.
...
I then ploughed through all the options, removing modules where I was
sure I did not have
the relevant hardware.
...
I closed down squeeze, rebooted and chose the new 3.0.4 kernel. It
displayed an
error message (kernel panic) to the effect that it could not load the
root fs.

What have I done wrong?


I would recommend using something like "make localmodconfig" to strip
out drivers your hardware doesn't need.  There are many hidden
dependencies, such as SCSI support, that are not obvious.
Also, I recommend that you read

   http://users.wowway.com/~zlinuxman/Kernel.htm





That will definitely give you a bootable kernel but with the stock 
Debian config, which is huge and gives you way more than you really need.
IMO to get just the right kernel config is very tricky because it is an 
trial and error thing. What would be handy is an IDE that records what 
change you made and for what reason, so that it can be removed when your 
hardware changes.


Hugo


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/j8mb41$4jj$1...@dough.gmane.org

Re: creaing new 3.0.4 kernel in squeeze --kernel panic

[Ralf Mardorf]

On Mon, 2011-10-31 at 05:16 +0100, Ralf Mardorf wrote:
> On Sun, 2011-10-30 at 12:40 -0700, poenik...@operamail.com wrote:
> > Here is the screen output for the kernel panic:-
> > --------
> > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
> > block(0.0)
> > Pid: 1. comm:swapper Not tainted 3.0.4 #1
> > Call trace:
> > [] ? panic+0x4d/0x137
> > [] ? mount_block_root+0x1e6/0x1fa
> > [] ? parse_early_options+0x18/0x18
> > [] ? mount_root+0x39/0x4d
> > [] ? parse_early_options+0x18/0x18
> > [] ? prepare_namespace+0x105/0x135
> > [] ? kernel_init+0xe9/0xf2
> > [] ? kernel_thread_helper+0x6/0xd
> > -
> > The computer locked and only continually pressing the on/off button
> > worked.
> > 
> > Any help appreciated. I can upload the .config file, but obviously not
> > to this user group
> > because it is 70KB long! :-)
> > 
> > Regards,  Sian
> 
> Perhaps no initrd was build?
> Perhaps you didn't run apt-get build-dep linux when installing the
> requirements to build a kernel?
> 
> I did it in this order
> 
> apt-get update
> apt-get install fakeroot build-essential crash kexec-tools makedumpfile
> kernel-package kernel-wedge
> apt-get build-dep linux
> apt-get install libncurses5 libncurses5-dev libelf-dev asciidoc
> binutils-dev

Sorry, seems to be nonsense, I suspect I was confusing it with an old
issue for Ubuntu:

"Intrepid (8.10), through to Karmic (9.10):

sudo apt-get install fakeroot kernel-wedge build-essential makedumpfile
kernel-package

Note: The linux-kernel-devel package does not exist in Intrepid,
Jaunty, or any newer release. To compile the kernel on Intrepid or
newer, you'll also need to run: 

sudo apt-get build-dep linux

This will install the compiler related packages and kernel packaging
tools. It will also install the git-core package, which is the best way
to interact with the Ubuntu kernel source."

root@debian:/home/spinymouse# apt-get build-dep linux
Reading package lists... Done
Building dependency tree   
Reading state information... Done
E: Unable to find a source package for linux



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1320036384.2802.9.camel@debian

Re: creaing new 3.0.4 kernel in squeeze --kernel panic

[Ralf Mardorf]

On Sun, 2011-10-30 at 13:56 -0600, Hugo Vanwoerkom wrote:
> I use:
> make-kpkg --revision 1 --append-to-version -amd64 --initrd kernel_image

I run
make-kpkg --rootcmd fakeroot --initrd kernel-image kernel-headers


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1320034961.2802.6.camel@debian

Re: creaing new 3.0.4 kernel in squeeze --kernel panic

[Ralf Mardorf]

On Sun, 2011-10-30 at 12:40 -0700, poenik...@operamail.com wrote:
> Here is the screen output for the kernel panic:-
> ----
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
> block(0.0)
> Pid: 1. comm:swapper Not tainted 3.0.4 #1
> Call trace:
> [] ? panic+0x4d/0x137
> [] ? mount_block_root+0x1e6/0x1fa
> [] ? parse_early_options+0x18/0x18
> [] ? mount_root+0x39/0x4d
> [] ? parse_early_options+0x18/0x18
> [] ? prepare_namespace+0x105/0x135
> [] ? kernel_init+0xe9/0xf2
> [] ? kernel_thread_helper+0x6/0xd
> -
> The computer locked and only continually pressing the on/off button
> worked.
> 
> Any help appreciated. I can upload the .config file, but obviously not
> to this user group
> because it is 70KB long! :-)
> 
> Regards,  Sian

Perhaps no initrd was build?
Perhaps you didn't run apt-get build-dep linux when installing the
requirements to build a kernel?

I did it in this order

apt-get update
apt-get install fakeroot build-essential crash kexec-tools makedumpfile
kernel-package kernel-wedge
apt-get build-dep linux
apt-get install libncurses5 libncurses5-dev libelf-dev asciidoc
binutils-dev


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1320034589.2802.5.camel@debian

Re: creaing new 3.0.4 kernel in squeeze --kernel panic

[Stephen Powell]

On Sun, 30 Oct 2011 14:24:28 -0400 (EDT), poenik...@operamail.com wrote:
> 
> I downloaded the source for kernel version 3.0.4 from www.kernel.org.
> ...
> I then ploughed through all the options, removing modules where I was
> sure I did not have
> the relevant hardware.
> ...
> I closed down squeeze, rebooted and chose the new 3.0.4 kernel. It
> displayed an
> error message (kernel panic) to the effect that it could not load the
> root fs.
> 
> What have I done wrong?

I would recommend using something like "make localmodconfig" to strip
out drivers your hardware doesn't need.  There are many hidden
dependencies, such as SCSI support, that are not obvious.
Also, I recommend that you read

   http://users.wowway.com/~zlinuxman/Kernel.htm

for a fairly comprehensive tutorial on kernel building in Debian which
documents many common "gotchas" in kernel building.  For example, there
is a patch to kernel-package which is needed in some circumstances
when building a version 3 kernel with make-kpkg.  The patch is documented
on the above web page.  And, depending on which boot loader you use,
you may need to install some hook scripts when using a custom kernel
with Squeeze and later releases.  This is also documented on the
above web page.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1462473744.43.1320021505717.javamail.r...@md01.wow.synacor.com

Re: creaing new 3.0.4 kernel in squeeze --kernel panic

[poenik...@operamail.com]

On Oct 30, 8:10 pm, Hugo Vanwoerkom  wrote:
> poenik...@operamail.com wrote:
> > I downloaded the source for kernel version 3.0.4 fromwww.kernel.org.
> > I then booted to the
> > Deiban squeeze partition and as superuser, unpacked the kernel source
> > in one of my own
> > directories.
>
> > I ran make targets to get what config commands were available. I
> > installed qt4-dev files from
> > the Debian squeeze DVD and did make xconfig which gave me a
> > configuration screen for
> > the new kernel source.
>
> > I then ploughed through all the options, removing modules where I was
> > sure I did not have
> > the relevant hardware. I eventually did make-kpkg clean, then  make-
> > kpkg debian and then
> > make-kpkg --targets, chose
> > binary and issued
> >             make-kpkg binary
> > The kernel was compiled and after much activity, make-kpkg returned me
> > to the command
> > line. In the directory above the top of the source tree were a number
> > of Debian packages
> > which included linux-image-3.0.4_3.0.4-10.00.Custom_i386.deb which I
> > installed using
> > dpkg. grub was run which found the Linux kernels as well as Ubuntu
> > 11.10.
>
> > I closed down squeeze, rebooted and chose the new 3.0.4 kernel. It
> > displayed an
> > error message (kernel panic) to the effect that it could not load the
> > root fs.
>
> > What have I done wrong?
>
> > I remember not choosing the option for an initramfs. What would be put
> > in it if I had
> > chosen that option?
>
> I use:
> make-kpkg --revision 1 --append-to-version -amd64 --initrd kernel_image
>
> which installs an initrd.img for an initramfs, but it will depend upon
> the config that you ended up with.
>
> Hugo
>

I tried this and got a kernel image which installed ok, but when I
rebooted into it, it gave the
following:
Loading, please wait...
there then followed a definite pause followed by these messages:
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
  - Check rootdelay
  - Check root (did the system wait for the right device?)
  - Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/disk/by-uuid/long number string does not exist.

I suspect that my configuration of the kernel is at fault, but where
should I start looking for problems?


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/9bcfad6f-88bd-4684-a593-32553ddaf...@t8g2000yql.googlegroups.com

Re: creaing new 3.0.4 kernel in squeeze --kernel panic

[Stan Hoeppner]

On 10/30/2011 1:24 PM, poenik...@operamail.com wrote:

> What have I done wrong?
> 
> I remember not choosing the option for an initramfs. What would be put
> in it if I had
> chosen that option?

I'd guess you configured your root filesystem (EXT3/4?) as a module
instead of building it directly into the kernel.  When you then omitted
initramfs the kernel had no way to load the filesystem code, hence the
error:

"Unable to mount root fs on unknown"

"Unknown" in this context means the kernel can't identify the filesystem
on the device where you are telling it the root filesystem resides.  It
can't because the FS driver isn't loaded.

The solution is to build the filesystem driver directly into the kernel
or to enable initramfs.  Personally I always build my filesystem
driver(s) directly into the kernel.  Every machine must have a
filesystem driver for the root filesystem, so there is no advantage to
making it a module--put it in the kernel proper.

-- 
Stan


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4eadd00b.6000...@hardwarefreak.com

Re: creaing new 3.0.4 kernel in squeeze --kernel panic

[poenik...@operamail.com]

On Oct 30, 6:50 pm, "poenik...@operamail.com"
 wrote:
> I downloaded the source for kernel version 3.0.4 fromwww.kernel.org.
> I then booted to the
> Deiban squeeze partition and as superuser, unpacked the kernel source
> in one of my own
> directories.
>
> I ran make targets to get what config commands were available. I
> installed qt4-dev files from
> the Debian squeeze DVD and did make xconfig which gave me a
> configuration screen for
> the new kernel source.
>
> I then ploughed through all the options, removing modules where I was
> sure I did not have
> the relevant hardware. I eventually did make-kpkg clean, then  make-
> kpkg debian and then
> make-kpkg --targets, chose
> binary and issued
>             make-kpkg binary
> The kernel was compiled and after much activity, make-kpkg returned me
> to the command
> line. In the directory above the top of the source tree were a number
> of Debian packages
> which included linux-image-3.0.4_3.0.4-10.00.Custom_i386.deb which I
> installed using
> dpkg. grub was run which found the Linux kernels as well as Ubuntu
> 11.10.
>
> I closed down squeeze, rebooted and chose the new 3.0.4 kernel. It
> displayed an
> error message (kernel panic) to the effect that it could not load the
> root fs.
>
> What have I done wrong?
>
> I remember not choosing the option for an initramfs. What would be put
> in it if I had
> chosen that option?
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: 
> http://lists.debian.org/50833057-0988-4022-9f24-28b06e0e6...@hj4g2000vbb.googlegroups.com

Here is the screen output for the kernel panic:-

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
block(0.0)
Pid: 1. comm:swapper Not tainted 3.0.4 #1
Call trace:
[] ? panic+0x4d/0x137
[] ? mount_block_root+0x1e6/0x1fa
[] ? parse_early_options+0x18/0x18
[] ? mount_root+0x39/0x4d
[] ? parse_early_options+0x18/0x18
[] ? prepare_namespace+0x105/0x135
[] ? kernel_init+0xe9/0xf2
[] ? kernel_thread_helper+0x6/0xd
-
The computer locked and only continually pressing the on/off button
worked.

Any help appreciated. I can upload the .config file, but obviously not
to this user group
because it is 70KB long! :-)

Regards,  Sian


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/86a460a6-05a2-483b-81ac-bd5c946f1...@a7g2000yqd.googlegroups.com

Re: creaing new 3.0.4 kernel in squeeze --kernel panic

[Hugo Vanwoerkom]

poenik...@operamail.com wrote:

I downloaded the source for kernel version 3.0.4 from www.kernel.org.
I then booted to the
Deiban squeeze partition and as superuser, unpacked the kernel source
in one of my own
directories.

I ran make targets to get what config commands were available. I
installed qt4-dev files from
the Debian squeeze DVD and did make xconfig which gave me a
configuration screen for
the new kernel source.

I then ploughed through all the options, removing modules where I was
sure I did not have
the relevant hardware. I eventually did make-kpkg clean, then  make-
kpkg debian and then
make-kpkg --targets, chose
binary and issued
make-kpkg binary
The kernel was compiled and after much activity, make-kpkg returned me
to the command
line. In the directory above the top of the source tree were a number
of Debian packages
which included linux-image-3.0.4_3.0.4-10.00.Custom_i386.deb which I
installed using
dpkg. grub was run which found the Linux kernels as well as Ubuntu
11.10.

I closed down squeeze, rebooted and chose the new 3.0.4 kernel. It
displayed an
error message (kernel panic) to the effect that it could not load the
root fs.

What have I done wrong?

I remember not choosing the option for an initramfs. What would be put
in it if I had
chosen that option?




I use:
make-kpkg --revision 1 --append-to-version -amd64 --initrd kernel_image

which installs an initrd.img for an initramfs, but it will depend upon 
the config that you ended up with.


Hugo










--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/j8ka66$doe$1...@dough.gmane.org

creaing new 3.0.4 kernel in squeeze --kernel panic

[poenik...@operamail.com]

I downloaded the source for kernel version 3.0.4 from www.kernel.org.
I then booted to the
Deiban squeeze partition and as superuser, unpacked the kernel source
in one of my own
directories.

I ran make targets to get what config commands were available. I
installed qt4-dev files from
the Debian squeeze DVD and did make xconfig which gave me a
configuration screen for
the new kernel source.

I then ploughed through all the options, removing modules where I was
sure I did not have
the relevant hardware. I eventually did make-kpkg clean, then  make-
kpkg debian and then
make-kpkg --targets, chose
binary and issued
make-kpkg binary
The kernel was compiled and after much activity, make-kpkg returned me
to the command
line. In the directory above the top of the source tree were a number
of Debian packages
which included linux-image-3.0.4_3.0.4-10.00.Custom_i386.deb which I
installed using
dpkg. grub was run which found the Linux kernels as well as Ubuntu
11.10.

I closed down squeeze, rebooted and chose the new 3.0.4 kernel. It
displayed an
error message (kernel panic) to the effect that it could not load the
root fs.

What have I done wrong?

I remember not choosing the option for an initramfs. What would be put
in it if I had
chosen that option?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/50833057-0988-4022-9f24-28b06e0e6...@hj4g2000vbb.googlegroups.com

Re: Re: debian kernel panic no init found SOLVED

[dirkydirk]

On Mon, 2011-02-28 at 17:13 +, Wolodja Wentland wrote:
> A quick look at the manpage reveals that you have to specify one of the
> supported commands. Let's try "list":
> 
> $ apt-listbugs list apt/0.8.11.5
> serious bugs of apt (0.8.11.5 -> 0.8.11.5) 
>  #558784 - apt: re-adds removed keys
> Summary:
>  apt(1 bug)

Ah, let's try it for the current case:

apt-listbugs list libc-bin/2.11.2-12
Reading package fields... Done
Reading package status... Done
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
serious bugs of libc-bin (2.11.2-13 -> 2.11.2-12) 
 #615839 - Kernel panic - not syncing: No init found (Fixed: eglibc/2.11.2-13)
   Merged with: 615806
Summary:
 libc-bin(1 bug)

Looks good. Hopefully this tool does not slow down a dist-upgrade too
much if it looks up bugs for almost 2.3k packages. I'm looking forward
to the next upgrade to see it in action.



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1298919806.4064.9.camel@Morrigan.annwn.local

Re: Re: debian kernel panic no init found SOLVED

[Wolodja Wentland]

On Mon, Feb 28, 2011 at 16:40 +0100, dirkydirk wrote:
> On Mon, 2011-02-28 at 15:17 +, Wolodja Wentland wrote:
> > On Mon, Feb 28, 2011 at 15:37 +0100, dirkydirk wrote:

> > Which version of libc-bin do you have installed (dpkg -l libc-bin). If you
> > have 2.11.2-12 you might have run into
[...]
> > [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%23615806#10

> That's it! Pulled version 2.11.2-13 of the libc-involved libraries, run
> dpkg-reconfigure linux-image-2.6.37-1-amd64 to generate a new ramdisc
> and it works!

Wonderful :)

> P.S. Heard about apt-listbugs the 1st time, installed it but it seems to
> have an issue itself:
> apt-listbugs apt
> 
> E: apt Pre-Install-Pkgs is not giving me expected 'VERSION 2' string.

I have never attempted to run apt-listbugs manually. It is typically
automatically invoked during the install/upgrade process and queried for
applicable bugs for the packages you are about to install/upgrade.

If there are indeed serious or grave bugs that apply to one of these packags,
you can choose to abort the installation altogether or pin selected packages
to the version you have installed.

While we are at it, another useful tool that is comparable to apt-listbugs is
apt-listchanges, which will bring important changes to your attention.

A quick look at the manpage reveals that you have to specify one of the
supported commands. Let's try "list":

$ apt-listbugs list apt/0.8.11.5
serious bugs of apt (0.8.11.5 -> 0.8.11.5) 
 #558784 - apt: re-adds removed keys
Summary:
 apt(1 bug)

voilà!
-- 
  .''`. Wolodja Wentland
 : :'  :
 `. `'` 4096R/CAF14EFC
   `-   081C B7CD FF04 2BA9 94EA  36B2 8B7F 7D30 CAF1 4EFC


signature.asc
Description: Digital signature

Re: Re: debian kernel panic no init found SOLVED

[dirkydirk]

On Mon, 2011-02-28 at 15:17 +, Wolodja Wentland wrote:
> On Mon, Feb 28, 2011 at 15:37 +0100, dirkydirk wrote:
> 
> > I conclude then, there's an issue with the update script. (I'm running
> > Debian sid, btw.)
> 
> An important piece of information. Which version of libc-bin do you have
> installed (dpkg -l libc-bin). If you have 2.11.2-12 you might have run into
> [0], but you probably would have mentioned the other symptoms that accompany
> that bug as well. As always: It is a good idea to have apt-listbugs installed.
> 
> [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%23615806#10

That's it! Pulled version 2.11.2-13 of the libc-involved libraries, run
dpkg-reconfigure linux-image-2.6.37-1-amd64 to generate a new ramdisc
and it works!
Thanks a lot, Wolodia, and love you guys for your quick and precise
support!

KR, m

P.S. Heard about apt-listbugs the 1st time, installed it but it seems to
have an issue itself:
apt-listbugs apt

E: apt Pre-Install-Pkgs is not giving me expected 'VERSION 2' string.




-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1298907650.4064.4.camel@Morrigan.annwn.local

Re: debian kernel panic no init found

[Hugo Vanwoerkom]

Wolodja Wentland wrote:

On Mon, Feb 28, 2011 at 15:37 +0100, dirkydirk wrote:


I conclude then, there's an issue with the update script. (I'm running
Debian sid, btw.)


An important piece of information. Which version of libc-bin do you have
installed (dpkg -l libc-bin). If you have 2.11.2-12 you might have run into
[0], but you probably would have mentioned the other symptoms that accompany
that bug as well. As always: It is a good idea to have apt-listbugs installed.

[0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%23615806#10


That's true, except for the fact that listbugs sits there for ever 
without giving a clue as to what it is doing... I removed it...


Hugo


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/ikgf6m$sbv$2...@dough.gmane.org

Re: debian kernel panic no init found

[Tom H]

On Mon, Feb 28, 2011 at 9:54 AM, dirkydirk  wrote:
>
> I suspect the script that generates the ramdisc to be faulty. See my
> other reply here:
> http://lists.debian.org/debian-user/2011/02/msg02902.html

Have you tried running update-initramfs one kernel at a time rather
than "update-initramfs -k all" - and anyway can it be run without "-c"
or "-u"?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktikqmagp_xglsrjuddjjdq2zhcvicnlnkcnz0...@mail.gmail.com

Re: debian kernel panic no init found

[dirkydirk]

Hmm, interestingly only swap and tmp were listed with an UUID. But alas,
it did not work out to list the other partitions with their UUID. 
Should I mention that software raid and lvm is used?

KR, m

On Mon, 2011-02-28 at 16:57 +0200, Andrei Popescu wrote:
> On Lu, 28 feb 11, 15:54:38, dirkydirk wrote:
> > It's grub2 and UUIDs are used; and grub finds the kernel and the ramdisc
> > file. (If it would not find them, grub would show a different msg.
> > Already encountered and solved that a while ago when grub had an issue
> > with wanting "/boot" in the path ;)
> 
> And fstab also?
> 
> Regards,
> Andrei



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1298906343.3809.2.camel@Morrigan.annwn.local

Re: Re: debian kernel panic no init found

[Wolodja Wentland]

On Mon, Feb 28, 2011 at 15:37 +0100, dirkydirk wrote:

> I conclude then, there's an issue with the update script. (I'm running
> Debian sid, btw.)

An important piece of information. Which version of libc-bin do you have
installed (dpkg -l libc-bin). If you have 2.11.2-12 you might have run into
[0], but you probably would have mentioned the other symptoms that accompany
that bug as well. As always: It is a good idea to have apt-listbugs installed.

[0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%23615806#10
-- 
  .''`. Wolodja Wentland
 : :'  :
 `. `'` 4096R/CAF14EFC
   `-   081C B7CD FF04 2BA9 94EA  36B2 8B7F 7D30 CAF1 4EFC


signature.asc
Description: Digital signature

Re: debian kernel panic no init found

[Andrei Popescu]

On Lu, 28 feb 11, 15:54:38, dirkydirk wrote:
> It's grub2 and UUIDs are used; and grub finds the kernel and the ramdisc
> file. (If it would not find them, grub would show a different msg.
> Already encountered and solved that a while ago when grub had an issue
> with wanting "/boot" in the path ;)

And fstab also?

Regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Re: debian kernel panic no init found

[dirkydirk]

It's grub2 and UUIDs are used; and grub finds the kernel and the ramdisc
file. (If it would not find them, grub would show a different msg.
Already encountered and solved that a while ago when grub had an issue
with wanting "/boot" in the path ;)

I suspect the script that generates the ramdisc to be faulty. See my
other reply here:
http://lists.debian.org/debian-user/2011/02/msg02902.html

KR, m


On Mon, 2011-02-28 at 16:35 +0200, Andrei Popescu wrote:
> On Lu, 28 feb 11, 13:09:20, dirkyd...@gmx.net wrote:
> > Hi all,
> > 
> > after updating my Debian box, it ceases to boot with above error. I 
> > use kernel 2.6.32. Booting older 2.6.28 seems to run the init process 
> > well (but has other issues).
> > 
> > Somebody has an idea what went wrong?
> 
> I suspect problems mounting the root partition. Make sure your fstab and 
> grub.cfg (or menu.lst, you didn't mention what release you are using) 
> use UUIDs or LABELs everywhere.
> 
> Regards,
> Andrei



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1298904878.4367.14.camel@Morrigan.annwn.local

Re: Re: debian kernel panic no init found

[dirkydirk]

Hi,

yes, there's init in it. But the directory structure of the ramdisc
looks quite different from a 2.6.31 ramdisc on another computer.

Unfortunately I did run update-initramfs -k all, and now even the 2.6.26
kernel refuses to boot. Same error.

>From the recent grml live-distro I copied kernel and modules, so at
least I can boot into my system. Then I installed 2.6.37 via aptitude
and got the same issue. Also, updating the ramdisk the debian-way via
dpkg-reconfigure linux-image-2.6.37-1-amd64 did not help.

I conclude then, there's an issue with the update script. (I'm running
Debian sid, btw.)

KR, m


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1298903845.4367.8.camel@Morrigan.annwn.local

Re: debian kernel panic no init found

[Andrei Popescu]

On Lu, 28 feb 11, 13:09:20, dirkyd...@gmx.net wrote:
> Hi all,
> 
> after updating my Debian box, it ceases to boot with above error. I 
> use kernel 2.6.32. Booting older 2.6.28 seems to run the init process 
> well (but has other issues).
> 
> Somebody has an idea what went wrong?

I suspect problems mounting the root partition. Make sure your fstab and 
grub.cfg (or menu.lst, you didn't mention what release you are using) 
use UUIDs or LABELs everywhere.

Regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Re: debian kernel panic no init found

[kuLa]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 28/02/11 12:09, dirkyd...@gmx.net wrote:
> Hi all,

hi

> after updating my Debian box, it ceases to boot with above error. I use 
> kernel 2.6.32. Booting older 2.6.28 seems to run the init process well (but 
> has other issues).
> 
> Somebody has an idea what went wrong?
> 
> KR, m

1st check if you've got init in your initrd image if not then run
update-initramfs for 2.6.32 kernel to ensure you've got it.

- -- 

|_|0|_|  |
|_|_|0| "Heghlu'Meh QaQ jajVam"  |
|0|0|0|  kuLa -  |

gpg --keyserver pgp.mit.edu --recv-keys 0xC100B4CA
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJNa6ycAAoJEOqHloDBALTK4v8IAJuHWlGqOH0mMWRwuriKEUhT
gtb53dqLQRUDMLyoX2G9gwjpBYAkcxQURCr+ddDkMGk2ZiB43zuEVocKZVw1zOpi
J3GKMIKkT5ml3E7zoFnZ2EKXxNqLZa/36hoYwBd5FdKClic+dCb7wHI+CcmAqV8d
NCB1EHI7vOhArXugp7gmWH4/PobpHoUwbBPEZQM1ZG9qCdWg8eIT07fY/fMwcOVr
aYxWrD/IjsGSt52OVVSLOubInCDuEVKi+chZRcgT2B9ZIel0/SvYp6sUxXxTqJEe
k99aPn4Gjwl1ULtr/4ppQ/QnUHWi3HsqCZbyJpAykA87YCpPiZH+eB7yQR/qhsU=
=op+v
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d6bac9c.4040...@kulisz.net

debian kernel panic no init found

[DirkyDirk]

Hi all,

after updating my Debian box, it ceases to boot with above error. I use kernel 
2.6.32. Booting older 2.6.28 seems to run the init process well (but has other 
issues).

Somebody has an idea what went wrong?

KR, m
-- 
NEU: FreePhone - kostenlos mobil telefonieren und surfen!   
Jetzt informieren: http://www.gmx.net/de/go/freephone


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110228120920.92...@gmx.net

Re: understanding kernel panic message

[Camaleón]

On Sat, 21 Aug 2010 08:24:19 -0400, Miles Fidelman wrote:

> Camaleón wrote:
 
>> Better if you upload to some place the full error log or a snapshot if
>> the "panic" comes at installation time.
>>
>> When does the error occur?
>>
> The Lenny version of the Xen Hypervisor has a known bug that causes
> infrequent crash/reboot events.  It's the final console message before
> the hypervisor reboots.  It's been fixed in later versions.
> 
> But having encountered it more than a few times now, I've become curious
> about what's going on.  Which leads me to wonder if there's a guide
> somewhere to kernel panic messages.  I can't seem to find a cross
> reference to kernel panic messages - but there must be one somewhere.

Kernel panics can come from different sources. Logs will tell you where 
to start... anyway, you can always start from here:

http://www.google.com/webhp?hl=en#hl=en&q=debugging+linux+kernel+panics&fp=7bb5c562e6b4c787

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2010.08.21.13.48...@gmail.com

Re: understanding kernel panic message

[Miles Fidelman]

Camaleón wrote:

On Fri, 20 Aug 2010 17:36:03 -0400, Miles Fidelman wrote:
   

So what does it actually mean when I get the message "kernel panic: not
syncing"?  I can't seem to find a reference, in any of the obvious
places, as to what the various kernel-generated oops and panic messages
actually mean - can someone point me at one?
 

Better if you upload to some place the full error log or a snapshot if
the "panic" comes at installation time.

When does the error occur?
   
The Lenny version of the Xen Hypervisor has a known bug that causes 
infrequent crash/reboot events.  It's the final console message before 
the hypervisor reboots.  It's been fixed in later versions.


But having encountered it more than a few times now, I've become curious 
about what's going on.  Which leads me to wonder if there's a guide 
somewhere to kernel panic messages.  I can't seem to find a cross 
reference to kernel panic messages - but there must be one somewhere.


Miles

--
In theory, there is no difference between theory and practice.
In  practice, there is.    Yogi Berra



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4c6fc573.6070...@meetinghouse.net

Re: understanding kernel panic message

[Camaleón]

On Fri, 20 Aug 2010 17:36:03 -0400, Miles Fidelman wrote:

> So what does it actually mean when I get the message "kernel panic: not
> syncing"?  I can't seem to find a reference, in any of the obvious
> places, as to what the various kernel-generated oops and panic messages
> actually mean - can someone point me at one?

Better if you upload to some place the full error log or a snapshot if 
the "panic" comes at installation time.

When does the error occur?

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2010.08.21.12.09...@gmail.com

understanding kernel panic message

[Miles Fidelman]

Hi Folks,

So what does it actually mean when I get the message "kernel panic: not 
syncing"?  I can't seem to find a reference, in any of the obvious 
places, as to what the various kernel-generated oops and panic messages 
actually mean - can someone point me at one?


Thanks,

Miles Fidelman

--
In theory, there is no difference between theory and practice.
In  practice, there is.    Yogi Berra



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4c6ef543.1060...@meetinghouse.net

Re: kernel panic error

[Anand Sivaram]

On Sun, Jul 18, 2010 at 13:39, Andrei Popescu wrote:

> On Sb, 17 iul 10, 23:10:39, Anand Sivaram wrote:
> > >
> > > Could you please elaborate on that? How can UUID fail if you have
> > > modules compiled in the kernel, since UUID is a property of the
> > > filesystem?
> >
> > Even if every driver is compiled into the kernel, an initrd may be
> required
> > to
> > use root=UUID=format.
> > That is what my experience too, finally I swithed to root=/dev/sda2
> > There are many suggestions that root=/dev/disk/by-uuid/
> > could be used instead without an initrd.
> >
> > See the link,
> > https://bbs.archlinux.org/viewtopic.php?id=61451
>
> The link only talks about /dev/disk/by-uuid/... which is correct. Those
> are actually symlinks created by udev and I'm guessing they are not
> present if you don't have an initrd. But passing root=UUID=... should
> not require an initrd, because it doesn't rely on /dev being present.
>
> Regards,
> Andrei
> --
> Offtopic discussions among Debian users and developers:
> http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iQEcBAEBCAAGBQJMQra/AAoJEHNWs3jeoi3pQLcH/iaFfF7w6oqspQuqlODIk1v6
> lIHoL/bTED1XhsADh+mfIOpEnEbT09UILN5RsoCZhxzwDU6LtBz1XQiR4sJLGqvZ
> IPY4mwxSquJCBPZBs3RO1UxSsGlzyULNLnHFoUXLLYzApUYNMVbIfNGdOj2Db5vb
> aWThBHPXfQczfh/0dITU7kkycH43uGhiZ5mjtrct61ZLRc8yzPQ1C6V89+h0p9bs
> Jze55L5UZAGm2Jsttic0RlrWz0UWP1OYVbyS0dn/jr32OWVswZEuh7SbhuyZij3z
> yuLU2IB08Lkzky0oVAkVWFMFGZyd8S1vn31RMvSgIhIG12+M0WQ8AGKH2eU4kq0=
> =nCgD
> -END PGP SIGNATURE-
>
>
I am using a custom 2.6.34 kernel with every driver built in.  Currently it
is booted with root=/dev/sda2 option.

Just to see how it works, I changed that to
1)  linux /boot/vmlinuz-2.6.34
root=UUID=ddc23ac8-37bf-4e89-a1cd-d77aefc011c8 ro  quiet
and
2) linux /boot/vmlinuz-2.6.34
root=/dev/disk/by-uuid/ddc23ac8-37bf-4e89-a1cd-d77aefc011c8

In both cases the system did not boot up.  The error was unable to mount
root device.
So finally, to use uuid option in either way, it is required to use initrd.

Re: kernel panic error

[Andrei Popescu]

On Sb, 17 iul 10, 23:10:39, Anand Sivaram wrote:
> >
> > Could you please elaborate on that? How can UUID fail if you have
> > modules compiled in the kernel, since UUID is a property of the
> > filesystem?
> 
> Even if every driver is compiled into the kernel, an initrd may be required
> to
> use root=UUID=format.
> That is what my experience too, finally I swithed to root=/dev/sda2
> There are many suggestions that root=/dev/disk/by-uuid/
> could be used instead without an initrd.
> 
> See the link,
> https://bbs.archlinux.org/viewtopic.php?id=61451

The link only talks about /dev/disk/by-uuid/... which is correct. Those 
are actually symlinks created by udev and I'm guessing they are not 
present if you don't have an initrd. But passing root=UUID=... should 
not require an initrd, because it doesn't rely on /dev being present.

Regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Fwd: kernel panic error

[Anand Sivaram]

On Sat, Jul 17, 2010 at 12:23, Andrei Popescu wrote:

> On Sb, 17 iul 10, 09:06:02, Anand Sivaram wrote:
> > >
> > It is necessary to use initrd image while using UUID.  So UUID method may
> > not work with custom kernels where drivers are compiled in.
>
> Could you please elaborate on that? How can UUID fail if you have
> modules compiled in the kernel, since UUID is a property of the
> filesystem?
>
> Regards,
> Andrei
> --
> Offtopic discussions among Debian users and developers:
> http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iQEcBAEBCAAGBQJMQVOBAAoJEHNWs3jeoi3pgJkH/1sIYoAOzgjqvUmQPgmyhEQA
> yHfiV3t9B6vRc5nUKb9Ck/Z4aZaodz0VKMOZSwc8VlZutOitJLgPSqXPKvWnciRk
> gcTJKDCvpn6Z/SB2jAHhk4MNVs2rn5jOvl1Qwpb046ak0vuvPJpmhl+X+SYQXsry
> Qp/ARgVzQDSsvYeVazt2uNF7ZBwXGKESYnZV1eHwgMQHaps/qB88w2HLMJYDYYF4
> xD6qWdkq6AnSH1L3Ywuyf8V+MelxjctbZOGBSNjcFzvzios6g9JMYrLdTJWEy8jX
> 006l0xPTL51UeUjGmOZTLYDOvFyhUV/AaWpuehXSY6GO+/pK2e5pfVmqVjJyjzE=
> =dJRE
> -END PGP SIGNATURE-
>
>
@Andrei,

Even if every driver is compiled into the kernel, an initrd may be required
to
use root=UUID=format.
That is what my experience too, finally I swithed to root=/dev/sda2
There are many suggestions that root=/dev/disk/by-uuid/
could be used instead without an initrd.

See the link,
https://bbs.archlinux.org/viewtopic.php?id=61451

Re: kernel panic error

[Anand Sivaram]

On Sat, Jul 17, 2010 at 12:23, Andrei Popescu wrote:

> On Sb, 17 iul 10, 09:06:02, Anand Sivaram wrote:
> > >
> > It is necessary to use initrd image while using UUID.  So UUID method may
> > not work with custom kernels where drivers are compiled in.
>
> Could you please elaborate on that? How can UUID fail if you have
> modules compiled in the kernel, since UUID is a property of the
> filesystem?
>
> Regards,
> Andrei
> --
> Offtopic discussions among Debian users and developers:
> http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iQEcBAEBCAAGBQJMQVOBAAoJEHNWs3jeoi3pgJkH/1sIYoAOzgjqvUmQPgmyhEQA
> yHfiV3t9B6vRc5nUKb9Ck/Z4aZaodz0VKMOZSwc8VlZutOitJLgPSqXPKvWnciRk
> gcTJKDCvpn6Z/SB2jAHhk4MNVs2rn5jOvl1Qwpb046ak0vuvPJpmhl+X+SYQXsry
> Qp/ARgVzQDSsvYeVazt2uNF7ZBwXGKESYnZV1eHwgMQHaps/qB88w2HLMJYDYYF4
> xD6qWdkq6AnSH1L3Ywuyf8V+MelxjctbZOGBSNjcFzvzios6g9JMYrLdTJWEy8jX
> 006l0xPTL51UeUjGmOZTLYDOvFyhUV/AaWpuehXSY6GO+/pK2e5pfVmqVjJyjzE=
> =dJRE
> -END PGP SIGNATURE-
>
>
@Andrei,

Even if every driver is compiled into the kernel, an initrd may be required
to
use root=UUID=format.
That is what my experience too, finally I swithed to root=/dev/sda2
There are many suggestions that root=/dev/disk/by-uuid/
could be used instead without an initrd.

See the link,
https://bbs.archlinux.org/viewtopic.php?id=61451

Re: kernel panic error

[Andrei Popescu]

On Sb, 17 iul 10, 09:06:02, Anand Sivaram wrote:
> >
> It is necessary to use initrd image while using UUID.  So UUID method may
> not work with custom kernels where drivers are compiled in. 

Could you please elaborate on that? How can UUID fail if you have 
modules compiled in the kernel, since UUID is a property of the 
filesystem?

Regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Re: kernel panic error

[Anand Sivaram]

On Fri, Jul 16, 2010 at 20:54, H.S.  wrote:

> On 10-07-16 10:56 AM, H.S. wrote:
>
>> On 16/07/10 05:59 AM, Sunita Barve wrote:
>>
>>> I have been using debian 5.0.3. I had changed disk and had connected on
>>> two
>>> different machines. Now I am getting the following error
>>>
>>
>> I am in a similar situation.
>>
>>  kinit: trying to resume from /dev/sda5
>>> kinit:No resume image, doing normal boot...
>>> Target filesystem doesnt have /sbin/init.
>>> run-init: /bin/sh: No such file  or directory
>>>
>>> [ 5.449855] Kernel Panic - not syncing : Attempted to kill init!
>>>
>>> can anyone help me to sort out this error.
>>>
>>
>> And I am getting similar errors. Can you post what are the grub lines
>> for the kernel you are trying to boot in? Also, what are the disc
>> partitions like in this machine (which is "/", "/boot")?
>>
>>
>>
> The solution in my case was to fix the grub's boot stanza for the relevant
> kernel. The drives' names may change in different computers. My solution was
> to put the UUIDs of the partitions for "/" and "/boot" (I have these on
> different partitions), instead of their patition names like /dev/sda2, in
> the boot stanza. If you want, I can post the stanza from the /boot the
> machine as an example.
>
>
>
>
>
>
>
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a
> subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/i1ptjm$r3...@dough.gmane.org
>
>
It is necessary to use initrd image while using UUID.  So UUID method may
not work with custom kernels where drivers are compiled in.  To find the
uuids of of a non working system, first boot with a live/boot cd and issue
either "blkid" or "ls -l /dev/disk/by-uuid"
Update grub accordingly.

Re: kernel panic error

[H.S.]

On 10-07-16 10:56 AM, H.S. wrote:

On 16/07/10 05:59 AM, Sunita Barve wrote:

I have been using debian 5.0.3. I had changed disk and had connected on two
different machines. Now I am getting the following error


I am in a similar situation.


kinit: trying to resume from /dev/sda5
kinit:No resume image, doing normal boot...
Target filesystem doesnt have /sbin/init.
run-init: /bin/sh: No such file  or directory

[ 5.449855] Kernel Panic - not syncing : Attempted to kill init!

can anyone help me to sort out this error.


And I am getting similar errors. Can you post what are the grub lines
for the kernel you are trying to boot in? Also, what are the disc
partitions like in this machine (which is "/", "/boot")?




The solution in my case was to fix the grub's boot stanza for the 
relevant kernel. The drives' names may change in different computers. My 
solution was to put the UUIDs of the partitions for "/" and "/boot" (I 
have these on different partitions), instead of their patition names 
like /dev/sda2, in the boot stanza. If you want, I can post the stanza 
from the /boot the machine as an example.








--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/i1ptjm$r3...@dough.gmane.org

Re: kernel panic error

[H.S.]

On 16/07/10 05:59 AM, Sunita Barve wrote:
> I have been using debian 5.0.3. I had changed disk and had connected on two
> different machines. Now I am getting the following error

I am in a similar situation.

> kinit: trying to resume from /dev/sda5
> kinit:No resume image, doing normal boot...
> Target filesystem doesnt have /sbin/init.
> run-init: /bin/sh: No such file  or directory
> 
> [ 5.449855] Kernel Panic - not syncing : Attempted to kill init!
> 
> can anyone help me to sort out this error.

And I am getting similar errors. Can you post what are the grub lines
for the kernel you are trying to boot in? Also, what are the disc
partitions like in this machine (which is "/", "/boot")?





-- 

Please reply to this list only. I read this list on its corresponding
newsgroup on gmane.org. Replies sent to my email address are just
filtered to a folder in my mailbox and get periodically deleted without
ever having been read.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/i1prvj$jp...@dough.gmane.org

kernel panic error

[Sunita Barve]

I have been using debian 5.0.3. I had changed disk and had connected on two
different machines. Now I am getting the following error

kinit: trying to resume from /dev/sda5
kinit:No resume image, doing normal boot...
Target filesystem doesnt have /sbin/init.
run-init: /bin/sh: No such file  or directory

[ 5.449855] Kernel Panic - not syncing : Attempted to kill init!

can anyone help me to sort out this error.

Thanks in advance,

-- 
Sunita Barve, Ph. D.
SIRC-In-Charge
National Centre for Radio Astrophysics
Post Bag No. 3, Pune Univ. Campus
Pune 411 007, INDIA
Phone : Office : 91-20-25719211
Residence : 91-020- 24470022
Mobile: 9922753827
Email : suni...@ncra.tifr.res.in ; sunitaba...@gmail.com