Tilman Schmidt wrote:
> Apparently not, given that the generated init script is mistaking
> a native environment for a domU instead of a dom0.
>
> In fact, when running 2.6.23-rc1 natively, no matter if compiled
> with or without Xen support, the directory /proc/xen doesn't even
> exist:
>
No,
Am 24.07.2007 21:12 schrieb Andi Kleen:
> On Tue, Jul 24, 2007 at 12:02:45PM -0700, Jeremy Fitzhardinge wrote:
>> Phew, I was getting worried there for a minute. Does the install script
>> check for CONFIG_XEN in the kernel config or something?
>
> Yes 10.2 mkinitrd does. But it still should
Andi Kleen wrote:
> Yes 10.2 mkinitrd does. But it still should work because a dom0
> kernel would obviously need all the drivers. A paravirt ops
> kernel native is like a dom0 variant.
>
> http://firstfloor.org/~andi/mkinitrd
Well, it appears to be assuming that a dom0 Xen kernel will have stuff
On Tue, Jul 24, 2007 at 12:02:45PM -0700, Jeremy Fitzhardinge wrote:
> Tilman Schmidt wrote:
> > Alright, I know what's going on now, and it looks like a problem with
> > the Opensuse init script. In fact, the initrd for the Xen enabled
> > kernel got a *different* init script than the one for the
Tilman Schmidt wrote:
> Alright, I know what's going on now, and it looks like a problem with
> the Opensuse init script. In fact, the initrd for the Xen enabled
> kernel got a *different* init script than the one for the non-Xen one.
> The difference being:
>
Phew, I was getting worried there
Alright, I know what's going on now, and it looks like a problem with
the Opensuse init script. In fact, the initrd for the Xen enabled
kernel got a *different* init script than the one for the non-Xen one.
The difference being:
--- /tmp/testing/init 2007-07-24 15:53:58.0 +0200
+++
Olaf Hering wrote:
> It seems the modules are not loaded at all in initrd, I dont see the
> 'SCSI subsystem initialized' message for example.
Yes. It's not clear to me whether that's because module loading is
failing for some reason, or pci bus probing. And completely unclear to
me why
On Tue, Jul 24, 2007 at 08:45:09AM -0700, Jeremy Fitzhardinge wrote:
> Olaf Hering wrote:
> > It seems the modules are not loaded at all in initrd, I dont see the
> > 'SCSI subsystem initialized' message for example.
>
> Yes. It's not clear to me whether that's because module loading is
>
On Tue, Jul 24, Tilman Schmidt wrote:
> Netconsole logs with initcall_debug=1 of a successful and a
> failing startup and corresponding .config-s are available at
> http://www.phnxsoft.com/~ts/linux/
It seems the modules are not loaded at all in initrd, I dont see the
'SCSI subsystem
Olaf Hering schrieb:
> On Tue, Jul 24, Andi Kleen wrote:
>
>> > Andi, any thoughts about how to debug the suse boot sequence?
>
> The SuSE boot sequence is rather long. Which part (and which version) are we
> talking about?
Quick summary of the problem:
Opensuse 10.2 32-bit install on a
On Tue, Jul 24, Andi Kleen wrote:
> > Andi, any thoughts about how to debug the suse boot sequence?
The SuSE boot sequence is rather long. Which part (and which version) are we
talking about?
As Andi said, putting a 'set -x' into /init script generated by /sbin/mkinitrd
is one thing. You can
On Mon, Jul 23, 2007 at 05:14:05PM -0700, Jeremy Fitzhardinge wrote:
> Well, it looks to me like it all falls over once it hits usermode;
> everything up till then is identical (except for the Xen-related
> initcalls which naturally don't exist in the non-Xen case).
>
> I'm at a loss. I don't
Tilman Schmidt wrote:
> Jeremy Fitzhardinge schrieb:
>
>> Well, it looks to me like it all falls over once it hits usermode;
>> everything up till then is identical (except for the Xen-related
>> initcalls which naturally don't exist in the non-Xen case).
>>
>
> Just a wild thought: could
Jeremy Fitzhardinge schrieb:
> Well, it looks to me like it all falls over once it hits usermode;
> everything up till then is identical (except for the Xen-related
> initcalls which naturally don't exist in the non-Xen case).
Just a wild thought: could the actual problem be with accessing the
Jeremy Fitzhardinge schrieb:
Well, it looks to me like it all falls over once it hits usermode;
everything up till then is identical (except for the Xen-related
initcalls which naturally don't exist in the non-Xen case).
Just a wild thought: could the actual problem be with accessing the
Tilman Schmidt wrote:
Jeremy Fitzhardinge schrieb:
Well, it looks to me like it all falls over once it hits usermode;
everything up till then is identical (except for the Xen-related
initcalls which naturally don't exist in the non-Xen case).
Just a wild thought: could the actual
On Mon, Jul 23, 2007 at 05:14:05PM -0700, Jeremy Fitzhardinge wrote:
Well, it looks to me like it all falls over once it hits usermode;
everything up till then is identical (except for the Xen-related
initcalls which naturally don't exist in the non-Xen case).
I'm at a loss. I don't know
On Tue, Jul 24, Andi Kleen wrote:
Andi, any thoughts about how to debug the suse boot sequence?
The SuSE boot sequence is rather long. Which part (and which version) are we
talking about?
As Andi said, putting a 'set -x' into /init script generated by /sbin/mkinitrd
is one thing. You can
Olaf Hering schrieb:
On Tue, Jul 24, Andi Kleen wrote:
Andi, any thoughts about how to debug the suse boot sequence?
The SuSE boot sequence is rather long. Which part (and which version) are we
talking about?
Quick summary of the problem:
Opensuse 10.2 32-bit install on a Pentium D 940
On Tue, Jul 24, Tilman Schmidt wrote:
Netconsole logs with initcall_debug=1 of a successful and a
failing startup and corresponding .config-s are available at
http://www.phnxsoft.com/~ts/linux/
It seems the modules are not loaded at all in initrd, I dont see the
'SCSI subsystem initialized'
Olaf Hering wrote:
It seems the modules are not loaded at all in initrd, I dont see the
'SCSI subsystem initialized' message for example.
Yes. It's not clear to me whether that's because module loading is
failing for some reason, or pci bus probing. And completely unclear to
me why CONFIG_XEN
On Tue, Jul 24, 2007 at 08:45:09AM -0700, Jeremy Fitzhardinge wrote:
Olaf Hering wrote:
It seems the modules are not loaded at all in initrd, I dont see the
'SCSI subsystem initialized' message for example.
Yes. It's not clear to me whether that's because module loading is
failing for
Alright, I know what's going on now, and it looks like a problem with
the Opensuse init script. In fact, the initrd for the Xen enabled
kernel got a *different* init script than the one for the non-Xen one.
The difference being:
--- /tmp/testing/init 2007-07-24 15:53:58.0 +0200
+++
Tilman Schmidt wrote:
Alright, I know what's going on now, and it looks like a problem with
the Opensuse init script. In fact, the initrd for the Xen enabled
kernel got a *different* init script than the one for the non-Xen one.
The difference being:
Phew, I was getting worried there for
On Tue, Jul 24, 2007 at 12:02:45PM -0700, Jeremy Fitzhardinge wrote:
Tilman Schmidt wrote:
Alright, I know what's going on now, and it looks like a problem with
the Opensuse init script. In fact, the initrd for the Xen enabled
kernel got a *different* init script than the one for the
Andi Kleen wrote:
Yes 10.2 mkinitrd does. But it still should work because a dom0
kernel would obviously need all the drivers. A paravirt ops
kernel native is like a dom0 variant.
http://firstfloor.org/~andi/mkinitrd
Well, it appears to be assuming that a dom0 Xen kernel will have stuff
in
Am 24.07.2007 21:12 schrieb Andi Kleen:
On Tue, Jul 24, 2007 at 12:02:45PM -0700, Jeremy Fitzhardinge wrote:
Phew, I was getting worried there for a minute. Does the install script
check for CONFIG_XEN in the kernel config or something?
Yes 10.2 mkinitrd does. But it still should work
Tilman Schmidt wrote:
Apparently not, given that the generated init script is mistaking
a native environment for a domU instead of a dom0.
In fact, when running 2.6.23-rc1 natively, no matter if compiled
with or without Xen support, the directory /proc/xen doesn't even
exist:
No, the
Tilman Schmidt wrote:
> So yes, all of ahci, pata_marvell, aic7xxx, jbd, dm_mod, ext3 are in
> fact modules in initrd. Would it help to try a kernel with some or all
> of these built in?
>
Yes, that would be useful. It would help tell whether its a module
loading problem or a basic pci
Tilman Schmidt wrote:
> Am 23.07.2007 22:32 schrieb Jeremy Fitzhardinge:
>
>> How much of this is modules? Is the initrd probing for scsi/sata?
>> Maybe the the vdso change is having an effect.
>>
>
> Pretty much all of it is modules. The base system is openSUSE 10.2, and
> SuSE has a
Am 23.07.2007 22:32 schrieb Jeremy Fitzhardinge:
> How much of this is modules? Is the initrd probing for scsi/sata?
> Maybe the the vdso change is having an effect.
Pretty much all of it is modules. The base system is openSUSE 10.2, and
SuSE has a long habit of building everything as modules
Tilman Schmidt wrote:
> To answer that, I have reproduced the effect with kernel 2.6.23-rc1 with
> netconsole compiled in. I'm attaching both captures, for CONFIG_XEN=y
> (unsuccessful) as well CONFIG_XEN=n (successful).
>
> The first noticeable difference is that the nonzero timestamps starting
>
Tilman Schmidt wrote:
> Attached are .config and dmesg (as captured in SuSE's /var/log/boot.msg)
> of a CONFIG_XEN=n git-current build.
That's dmesg from a successful boot? What does it look like when its
unsuccessful? Where do they start to differ?
J
-
To unsubscribe from this list: send
Tilman Schmidt wrote:
> on Mon, 23 Jul 2007 01:47:30 +0200, /me wrote:
>
>> On my test machine with a Pentium D 940 processor, Intel DQ965GF
>> mainboard and SATA disks, kernel 2.6.22-git17 (32 bit build) fails
>> to come up because it cannot find the disk drives. Same issue
>> with a clone of
Tilman Schmidt <[EMAIL PROTECTED]> writes:
> on Mon, 23 Jul 2007 01:47:30 +0200, /me wrote:
> > On my test machine with a Pentium D 940 processor, Intel DQ965GF
> > mainboard and SATA disks, kernel 2.6.22-git17 (32 bit build) fails
> > to come up because it cannot find the disk drives. Same issue
Tilman Schmidt [EMAIL PROTECTED] writes:
on Mon, 23 Jul 2007 01:47:30 +0200, /me wrote:
On my test machine with a Pentium D 940 processor, Intel DQ965GF
mainboard and SATA disks, kernel 2.6.22-git17 (32 bit build) fails
to come up because it cannot find the disk drives. Same issue
with a
Tilman Schmidt wrote:
on Mon, 23 Jul 2007 01:47:30 +0200, /me wrote:
On my test machine with a Pentium D 940 processor, Intel DQ965GF
mainboard and SATA disks, kernel 2.6.22-git17 (32 bit build) fails
to come up because it cannot find the disk drives. Same issue
with a clone of the
Tilman Schmidt wrote:
Attached are .config and dmesg (as captured in SuSE's /var/log/boot.msg)
of a CONFIG_XEN=n git-current build.
That's dmesg from a successful boot? What does it look like when its
unsuccessful? Where do they start to differ?
J
-
To unsubscribe from this list: send
Tilman Schmidt wrote:
To answer that, I have reproduced the effect with kernel 2.6.23-rc1 with
netconsole compiled in. I'm attaching both captures, for CONFIG_XEN=y
(unsuccessful) as well CONFIG_XEN=n (successful).
The first noticeable difference is that the nonzero timestamps starting
after
Am 23.07.2007 22:32 schrieb Jeremy Fitzhardinge:
How much of this is modules? Is the initrd probing for scsi/sata?
Maybe the the vdso change is having an effect.
Pretty much all of it is modules. The base system is openSUSE 10.2, and
SuSE has a long habit of building everything as modules and
Tilman Schmidt wrote:
Am 23.07.2007 22:32 schrieb Jeremy Fitzhardinge:
How much of this is modules? Is the initrd probing for scsi/sata?
Maybe the the vdso change is having an effect.
Pretty much all of it is modules. The base system is openSUSE 10.2, and
SuSE has a long habit of
Tilman Schmidt wrote:
So yes, all of ahci, pata_marvell, aic7xxx, jbd, dm_mod, ext3 are in
fact modules in initrd. Would it help to try a kernel with some or all
of these built in?
Yes, that would be useful. It would help tell whether its a module
loading problem or a basic pci probing
on Mon, 23 Jul 2007 01:47:30 +0200, /me wrote:
> On my test machine with a Pentium D 940 processor, Intel DQ965GF
> mainboard and SATA disks, kernel 2.6.22-git17 (32 bit build) fails
> to come up because it cannot find the disk drives. Same issue
> with a clone of the 'linus' git tree. Anything
Tilman Schmidt wrote:
> On my test machine with a Pentium D 940 processor, Intel DQ965GF
> mainboard and SATA disks, kernel 2.6.22-git17 (32 bit build) fails
> to come up because it cannot find the disk drives. Same issue
> with a clone of the 'linus' git tree. Anything known?
>
Could you post
Tilman Schmidt: wrote
> On my test machine with a Pentium D 940 processor, Intel DQ965GF
> mainboard and SATA disks, kernel 2.6.22-git17 (32 bit build) fails
> to come up because it cannot find the disk drives. Same issue
> with a clone of the 'linus' git tree. Anything known?
I don't know if
On my test machine with a Pentium D 940 processor, Intel DQ965GF
mainboard and SATA disks, kernel 2.6.22-git17 (32 bit build) fails
to come up because it cannot find the disk drives. Same issue
with a clone of the 'linus' git tree. Anything known?
--
Tilman Schmidt
On my test machine with a Pentium D 940 processor, Intel DQ965GF
mainboard and SATA disks, kernel 2.6.22-git17 (32 bit build) fails
to come up because it cannot find the disk drives. Same issue
with a clone of the 'linus' git tree. Anything known?
--
Tilman Schmidt
Tilman Schmidt: wrote
On my test machine with a Pentium D 940 processor, Intel DQ965GF
mainboard and SATA disks, kernel 2.6.22-git17 (32 bit build) fails
to come up because it cannot find the disk drives. Same issue
with a clone of the 'linus' git tree. Anything known?
I don't know if this is
Tilman Schmidt wrote:
On my test machine with a Pentium D 940 processor, Intel DQ965GF
mainboard and SATA disks, kernel 2.6.22-git17 (32 bit build) fails
to come up because it cannot find the disk drives. Same issue
with a clone of the 'linus' git tree. Anything known?
Could you post the
on Mon, 23 Jul 2007 01:47:30 +0200, /me wrote:
On my test machine with a Pentium D 940 processor, Intel DQ965GF
mainboard and SATA disks, kernel 2.6.22-git17 (32 bit build) fails
to come up because it cannot find the disk drives. Same issue
with a clone of the 'linus' git tree. Anything known?
50 matches
Mail list logo
