Factory CD boot problem

classic Classic list List threaded Threaded
18 messages Options
Reply | Threaded
Open this post in threaded view
|

Factory CD boot problem

Andreas Färber
Hello,

Since a number of weeks I am unsuccessful in using the ppc64 install
media on my POWER5+ box. Below is output from latest
openSUSE-NET64-ppc64-Build0023-Media.iso. In qemu-system-ppc64 it
proceeds okay, and Factory boots okay (below). The only difference is me
entering SMS menu to select booting from IDE CD. I notice that the
booting system loads an Elf64 kernel while the ppc64 iso loads an Elf32
kernel. Any ideas?

Thanks,
Andreas

CD:

yaboot starting: loaded at 00040000 00065a88 (0/0/02039a68; sp: 02cbffd0)
Config file 'yaboot.cnf' read, 285 bytes


  Welcome to openSuSE Factory!

  Type  "install"  to start the YaST installer on this CD/DVD
  Type  "slp"      to start the YaST install via network
  Type  "rescue"   to start the rescue system on this CD/DVD


Welcome to yaboot version r22.8-r1190.SuSE
booted from
'/pci@800000020000003/pci@2,3/ide@1/disk@0:1,\suseboot\yaboot.ibm'
running with firmware 'IBM,SF240_284' on model 'IBM,9111-285', serial
'IBM,*********', partition '06-C903E'
Enter "help" to get some basic usage information
boot:
  install                    slp                        rescue
boot: install
Please wait, loading kernel...
Allocated 02f00000 bytes for executable @ 03000000
   Elf32 kernel loaded...

SuSE Linux zImage starting: loaded at 03000000-05dc0d30
(4000000/0/02039a68; sp: 02cbfd90)
uncompressing ELF header done. (00000100 bytes)
Allocated 018461cc bytes for kernel @ 05f00000
Leave 027c7fc4 bytes for initrd @ 035ecece
uncompressing kernel done. (01240ef8 bytes)
entering kernel at 05f10000(35ecece/27c7fc4/02039a68)
OF stdout device is: /vdevice/vty@30000000
Preparing to boot Linux version 3.10.1-3.g0cd5432-default
(geeko@buildhost) (gcc version 4.8.1 20130711 [gcc-4_8-branch revision
200903] (SUSE Linux) ) #1 SMP Fri Jul 19 14:39:31 UTC 2013 (0cd5432)
Detected machine type: 0000000000000101
Max number of cores passed to firmware: 512 (NR_CPUS = 1024)
Calling ibm,client-architecture-support... not implemented
command line: quiet sysrq=1 insmod=sym53c8xx insmod=ipr
memory layout at init:
  memory_limit : 0000000000000000 (16 MB aligned)
  alloc_bottom : 0000000007470000
  alloc_top    : 0000000008000000
  alloc_top_hi : 0000000077000000
  rmo_top      : 0000000008000000
  ram_top      : 0000000077000000
found display   : /pci@800000020000002/display@1, opening... done
Could not allocate memory for RTAS
EXIT called ok
0 >


Disk:

yaboot starting: loaded at 00040000 00065a88 (0/0/02039a68; sp: 02cbffd0)
Config file 'yaboot.cnf' read, 611 bytes

Welcome to yaboot version r22.8-r1190.SuSE
booted from
'/pci@800000020000003/pci@2,4/pci1069,b166@1/scsi@0/sd@8,0:1,yaboot'
running with firmware 'IBM,SF240_284' on model 'IBM,9111-285', serial
'IBM,*********', partition '06-C903E'
Enter "help" to get some basic usage information
boot: Linux_4
Using 01401f9c bytes for initrd buffer
Please wait, loading kernel...
Allocated 01700000 bytes for kernel @ 03000000
   Elf64 kernel loaded...
Loading ramdisk...
ramdisk loaded 01401f9c @ 04700000
OF stdout device is: /vdevice/vty@30000000
Preparing to boot Linux version 3.10.1-3.g0cd5432-default
(geeko@buildhost) (gcc version 4.8.1 20130711 [gcc-4_8-branch revision
200903] (SUSE Linux) ) #1 SMP Fri Jul 19 14:39:31 UTC 2013 (0cd5432)
Detected machine type: 0000000000000101
Max number of cores passed to firmware: 512 (NR_CPUS = 1024)
Calling ibm,client-architecture-support... not implemented
command line:
root=/dev/disk/by-uuid/671e0a08-2bb3-4fae-b606-287d887e2060  quiet
sysrq=1 insmod=sym53c8xx insmod=ipr
memory layout at init:
  memory_limit : 0000000000000000 (16 MB aligned)
  alloc_bottom : 0000000005b10000
  alloc_top    : 0000000008000000
  alloc_top_hi : 0000000077000000
  rmo_top      : 0000000008000000
  ram_top      : 0000000077000000
found display   : /pci@800000020000002/display@1, opening... done
instantiating rtas at 0x00000000076a0000... done
Querying for OPAL presence... not there.
boot cpu hw idx 0
copying OF device tree...
Building dt strings...
Building dt structure...
Device tree strings 0x0000000005b20000 -> 0x0000000005b21372
Device tree struct  0x0000000005b30000 -> 0x0000000005b40000
no ibm,pcie-link-speed-stats property
no ibm,pcie-link-speed-stats property
no ibm,pcie-link-speed-stats property
/home/abuild/rpmbuild/BUILD/kernel-default-3.10.1/linux-3.10/drivers/rtc/hctosys.c:
unable to open rtc device (rtc0)
doing fast boot
[...]


--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Factory CD boot problem

Andreas Färber
Hi Dinar,

Thanks for your work on the installation media.

Unfortunately though, openSUSE-13.1-ppc64-NET-ppc64-Build0018-Media.iso
still fails to boot into Linux on my machine. The initrd appears to load
okay but the failure remains when loading RTAS.

The installed system continues to work fine (except it needs some
partition resizing that I was hoping to do via a reinstall), so it
doesn't sound like it's a general problem with the IBM firmware's RTAS
implementation - the firmware did not change since original installation.

Any ideas would be welcome. Maybe reduce initrd size even more?
Or is the presence of the graphics card maybe causing problems due to
OpenFirmware framebuffer size?

Regards,
Andreas


Elapsed time since release of system processors: 5 mins 35 secs

yaboot starting: loaded at 00040000 00065a88 (0/0/02039a68; sp: 02cbffd0)
Config file 'yaboot.cnf' read, 342 bytes


  Welcome to openSuSE 13.1!

  Type  "install"  to start the YaST installer on this CD/DVD
  Type  "slp"      to start the YaST install via network
  Type  "rescue"   to start the rescue system on this CD/DVD


Welcome to yaboot version r22.8-r1190.SuSE
booted from
'/pci@800000020000003/pci@2,3/ide@1/disk@0:1,\suseboot\yaboot.ibm'
running with firmware 'IBM,SF240_284' on model 'IBM,9111-285', serial
'IBM,*********', partition '06-C903E'
Enter "help" to get some basic usage information
boot: help
  Press the tab key for a list of defined images.
  The label marked with a "*" is the default image, press <return> to
boot it.

  To boot any other label simply type its name and press <return>.
  It is also possible to expand a label with the tab key.

  To boot a kernel image which is not defined in the yaboot configuration
  file, enter the kernel image name as [[device:[partno]],]/path, where
  "device:" is the OpenFirmware device path to the disk the image
  resides on, and "partno" is the partition number the image resides on.
  Note that the comma (,) is only required if you specify an OpenFirmware
  device, if you only specify a filename you should not start it with a ","
  The shortcut '&device;' can be used to specify the OpenFirmware device
path
  where yaboot was loaded from.

  To load an initrd, specify its path as initrd=[[device:[partno]],]/path

  If you omit "device:" and "partno" yaboot will use the values of
  "device=" and "partition=" in yaboot.conf, right now those are set to:
  device=/pci@800000020000003/pci@2,3/ide@1/disk@0
  partition=1

boot:
  install                    slp                        rescue
boot: install
Please wait, loading kernel...
Allocated 01700000 bytes for kernel @ 03000000
   Elf64 kernel loaded...
Loading ramdisk...
ramdisk loaded 031c5a55 @ 04700000
OF stdout device is: /vdevice/vty@30000000
Preparing to boot Linux version 3.11.6-3-default (geeko@buildhost) (gcc
version 4.8.1 20130909 [gcc-4_8-branch revision 202388] (SUSE Linux) )
#1 SMP Thu Oct 24 16:23:02 UTC 2013 (0ba01b7)
Detected machine type: 0000000000000101
Max number of cores passed to firmware: 1024 (NR_CPUS = 2048)
Calling ibm,client-architecture-support... not implemented
command line: quiet sysrq=1 insmod=sym53c8xx insmod=ipr
memory layout at init:
  memory_limit : 0000000000000000 (16 MB aligned)
  alloc_bottom : 00000000078d0000
  alloc_top    : 0000000008000000
  alloc_top_hi : 0000000077000000
  rmo_top      : 0000000008000000
  ram_top      : 0000000077000000
found display   : /pci@800000020000002/display@1, opening... done
Could not allocate memory for RTAS
EXIT called ok
0 >


--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Factory CD boot problem

Alexander Graf-4

On 21.11.2013, at 13:37, Andreas Färber <[hidden email]> wrote:

> Hi Dinar,
>
> Thanks for your work on the installation media.
>
> Unfortunately though, openSUSE-13.1-ppc64-NET-ppc64-Build0018-Media.iso
> still fails to boot into Linux on my machine. The initrd appears to load
> okay but the failure remains when loading RTAS.
>
> The installed system continues to work fine (except it needs some
> partition resizing that I was hoping to do via a reinstall), so it
> doesn't sound like it's a general problem with the IBM firmware's RTAS
> implementation - the firmware did not change since original installation.
>
> Any ideas would be welcome. Maybe reduce initrd size even more?
> Or is the presence of the graphics card maybe causing problems due to
> OpenFirmware framebuffer size?
>
> Regards,
> Andreas
>
>
> Elapsed time since release of system processors: 5 mins 35 secs
>
> yaboot starting: loaded at 00040000 00065a88 (0/0/02039a68; sp: 02cbffd0)
> Config file 'yaboot.cnf' read, 342 bytes
>
>
>  Welcome to openSuSE 13.1!
>
>  Type  "install"  to start the YaST installer on this CD/DVD
>  Type  "slp"      to start the YaST install via network
>  Type  "rescue"   to start the rescue system on this CD/DVD
>
>
> Welcome to yaboot version r22.8-r1190.SuSE
> booted from
> '/pci@800000020000003/pci@2,3/ide@1/disk@0:1,\suseboot\yaboot.ibm'
> running with firmware 'IBM,SF240_284' on model 'IBM,9111-285', serial
> 'IBM,*********', partition '06-C903E'
> Enter "help" to get some basic usage information
> boot: help
>  Press the tab key for a list of defined images.
>  The label marked with a "*" is the default image, press <return> to
> boot it.
>
>  To boot any other label simply type its name and press <return>.
>  It is also possible to expand a label with the tab key.
>
>  To boot a kernel image which is not defined in the yaboot configuration
>  file, enter the kernel image name as [[device:[partno]],]/path, where
>  "device:" is the OpenFirmware device path to the disk the image
>  resides on, and "partno" is the partition number the image resides on.
>  Note that the comma (,) is only required if you specify an OpenFirmware
>  device, if you only specify a filename you should not start it with a ","
>  The shortcut '&device;' can be used to specify the OpenFirmware device
> path
>  where yaboot was loaded from.
>
>  To load an initrd, specify its path as initrd=[[device:[partno]],]/path
>
>  If you omit "device:" and "partno" yaboot will use the values of
>  "device=" and "partition=" in yaboot.conf, right now those are set to:
>  device=/pci@800000020000003/pci@2,3/ide@1/disk@0
>  partition=1
>
> boot:
>  install                    slp                        rescue
> boot: install
> Please wait, loading kernel...
> Allocated 01700000 bytes for kernel @ 03000000
>   Elf64 kernel loaded...
> Loading ramdisk...
> ramdisk loaded 031c5a55 @ 04700000
> OF stdout device is: /vdevice/vty@30000000
> Preparing to boot Linux version 3.11.6-3-default (geeko@buildhost) (gcc
> version 4.8.1 20130909 [gcc-4_8-branch revision 202388] (SUSE Linux) )
> #1 SMP Thu Oct 24 16:23:02 UTC 2013 (0ba01b7)
> Detected machine type: 0000000000000101
> Max number of cores passed to firmware: 1024 (NR_CPUS = 2048)
> Calling ibm,client-architecture-support... not implemented
> command line: quiet sysrq=1 insmod=sym53c8xx insmod=ipr
> memory layout at init:
>  memory_limit : 0000000000000000 (16 MB aligned)
>  alloc_bottom : 00000000078d0000
>  alloc_top    : 0000000008000000
>  alloc_top_hi : 0000000077000000
>  rmo_top      : 0000000008000000
>  ram_top      : 0000000077000000
> found display   : /pci@800000020000002/display@1, opening... done
> Could not allocate memory for RTAS

Ben, do you know what this means?


Alex

> EXIT called ok
> 0 >
>
>
> --
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Factory CD boot problem

Benjamin Herrenschmidt
On Thu, 2014-01-02 at 21:34 +0100, Alexander Graf wrote:

> > boot:
> >  install                    slp                        rescue
> > boot: install
> > Please wait, loading kernel...
> > Allocated 01700000 bytes for kernel @ 03000000
> >   Elf64 kernel loaded...
> > Loading ramdisk...
> > ramdisk loaded 031c5a55 @ 04700000
> > OF stdout device is: /vdevice/vty@30000000
> > Preparing to boot Linux version 3.11.6-3-default (geeko@buildhost) (gcc
> > version 4.8.1 20130909 [gcc-4_8-branch revision 202388] (SUSE Linux) )
> > #1 SMP Thu Oct 24 16:23:02 UTC 2013 (0ba01b7)
> > Detected machine type: 0000000000000101
> > Max number of cores passed to firmware: 1024 (NR_CPUS = 2048)
> > Calling ibm,client-architecture-support... not implemented
> > command line: quiet sysrq=1 insmod=sym53c8xx insmod=ipr
> > memory layout at init:
> >  memory_limit : 0000000000000000 (16 MB aligned)
> >  alloc_bottom : 00000000078d0000
> >  alloc_top    : 0000000008000000
> >  alloc_top_hi : 0000000077000000
> >  rmo_top      : 0000000008000000
> >  ram_top      : 0000000077000000
> > found display   : /pci@800000020000002/display@1, opening... done
> > Could not allocate memory for RTAS
>
> Ben, do you know what this means?

Yes, it means what the message says ... prom_init.c couldn't find a big
enough free spot of RAM in the RMA to put RTAS in.

Usually that means a too big ramdisk...

Remember pHyp hands out really tiny RMAs, in this case, 128M, that's it
and that's all OFW can use. Look at RTAS size in the device-tree,
so based on where the kernel is loaded, where the ramdisk is
loaded, the reserved area to keep for the kernel etc... you may not
have enough room left for RTAS.

It could also be that yaboot put things in less than optimal spots

Cheers,
Ben.

>
> Alex
>
> > EXIT called ok
> > 0 >
> >
> >
> > --
> > SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> > GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg


--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Factory CD boot problem

Alexander Graf-4

On 02.01.2014, at 21:51, Benjamin Herrenschmidt <[hidden email]> wrote:

> On Thu, 2014-01-02 at 21:34 +0100, Alexander Graf wrote:
>
>>> boot:
>>> install                    slp                        rescue
>>> boot: install
>>> Please wait, loading kernel...
>>> Allocated 01700000 bytes for kernel @ 03000000
>>>  Elf64 kernel loaded...
>>> Loading ramdisk...
>>> ramdisk loaded 031c5a55 @ 04700000
>>> OF stdout device is: /vdevice/vty@30000000
>>> Preparing to boot Linux version 3.11.6-3-default (geeko@buildhost) (gcc
>>> version 4.8.1 20130909 [gcc-4_8-branch revision 202388] (SUSE Linux) )
>>> #1 SMP Thu Oct 24 16:23:02 UTC 2013 (0ba01b7)
>>> Detected machine type: 0000000000000101
>>> Max number of cores passed to firmware: 1024 (NR_CPUS = 2048)
>>> Calling ibm,client-architecture-support... not implemented
>>> command line: quiet sysrq=1 insmod=sym53c8xx insmod=ipr
>>> memory layout at init:
>>> memory_limit : 0000000000000000 (16 MB aligned)
>>> alloc_bottom : 00000000078d0000
>>> alloc_top    : 0000000008000000
>>> alloc_top_hi : 0000000077000000
>>> rmo_top      : 0000000008000000
>>> ram_top      : 0000000077000000
>>> found display   : /pci@800000020000002/display@1, opening... done
>>> Could not allocate memory for RTAS
>>
>> Ben, do you know what this means?
>
> Yes, it means what the message says ... prom_init.c couldn't find a big
> enough free spot of RAM in the RMA to put RTAS in.
>
> Usually that means a too big ramdisk...
>
> Remember pHyp hands out really tiny RMAs, in this case, 128M, that's it
> and that's all OFW can use. Look at RTAS size in the device-tree,
> so based on where the kernel is loaded, where the ramdisk is
> loaded, the reserved area to keep for the kernel etc... you may not
> have enough room left for RTAS.

Andreas, could you please dump /proc/device-tree from a working Linux instance and upload it somewhere or at least tell us how big the RTAS payload is? :)

So we have

48MB - ~71MB kernel
71MB - 120MB initrd

So yeah, I can see how there might be too little space left to put the RTAS blob somewhere. But why is yaboot only allocating as of 48MB?

Either way, I guess in your case the easiest solution would be to trim a few firmware blobs from the initrd. I don't think you have qlogic hbas in your system, right? :)

> It could also be that yaboot put things in less than optimal spots

Well, the only curious thing is that it starts allocation at 48MB. But I suppose that's for a good reason - OFW and yaboot have to all fit into the same tiny 128MB address space after all.


Alex

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Factory CD boot problem

Benjamin Herrenschmidt-2
On Thu, 2014-01-02 at 22:01 +0100, Alexander Graf wrote:
> Well, the only curious thing is that it starts allocation at 48MB. But
> I suppose that's for a good reason - OFW and yaboot have to all fit
> into the same tiny 128MB address space after all.

Check where OFW is ... (real-base)

Cheers,
Ben.


--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Factory CD boot problem

Andreas Färber
In reply to this post by Alexander Graf-4
Am 02.01.2014 22:01, schrieb Alexander Graf:

>
> On 02.01.2014, at 21:51, Benjamin Herrenschmidt <[hidden email]> wrote:
>
>> On Thu, 2014-01-02 at 21:34 +0100, Alexander Graf wrote:
>>
>>>> boot:
>>>> install                    slp                        rescue
>>>> boot: install
>>>> Please wait, loading kernel...
>>>> Allocated 01700000 bytes for kernel @ 03000000
>>>>  Elf64 kernel loaded...
>>>> Loading ramdisk...
>>>> ramdisk loaded 031c5a55 @ 04700000
>>>> OF stdout device is: /vdevice/vty@30000000
>>>> Preparing to boot Linux version 3.11.6-3-default (geeko@buildhost) (gcc
>>>> version 4.8.1 20130909 [gcc-4_8-branch revision 202388] (SUSE Linux) )
>>>> #1 SMP Thu Oct 24 16:23:02 UTC 2013 (0ba01b7)
>>>> Detected machine type: 0000000000000101
>>>> Max number of cores passed to firmware: 1024 (NR_CPUS = 2048)
>>>> Calling ibm,client-architecture-support... not implemented
>>>> command line: quiet sysrq=1 insmod=sym53c8xx insmod=ipr
>>>> memory layout at init:
>>>> memory_limit : 0000000000000000 (16 MB aligned)
>>>> alloc_bottom : 00000000078d0000
>>>> alloc_top    : 0000000008000000
>>>> alloc_top_hi : 0000000077000000
>>>> rmo_top      : 0000000008000000
>>>> ram_top      : 0000000077000000
>>>> found display   : /pci@800000020000002/display@1, opening... done
>>>> Could not allocate memory for RTAS
>>>
>>> Ben, do you know what this means?
>>
>> Yes, it means what the message says ... prom_init.c couldn't find a big
>> enough free spot of RAM in the RMA to put RTAS in.
>>
>> Usually that means a too big ramdisk...
>>
>> Remember pHyp hands out really tiny RMAs, in this case, 128M, that's it
>> and that's all OFW can use. Look at RTAS size in the device-tree,
>> so based on where the kernel is loaded, where the ramdisk is
>> loaded, the reserved area to keep for the kernel etc... you may not
>> have enough room left for RTAS.
>
> Andreas, could you please dump /proc/device-tree from a working Linux instance and upload it somewhere

Transferred a tarball to my notebook.

> or at least tell us how big the RTAS payload is? :)

# cd /proc/device-tree
# hexdump rtas/rtas-size
0000000 0095 c000
0000004

=> RTAS is 9.814.016 bytes if I'm reading that correctly.

> So we have
>
> 48MB - ~71MB kernel
> 71MB - 120MB initrd
>
> So yeah, I can see how there might be too little space left to put the RTAS blob somewhere. But why is yaboot only allocating as of 48MB?
>
> Either way, I guess in your case the easiest solution would be to trim a few firmware blobs from the initrd. I don't think you have qlogic hbas in your system, right? :)

0001:d0:01.0 SCSI storage controller: Mylex Corporation AcceleRAID
600/500/400/Sapphire support Device (rev 04)

>> It could also be that yaboot put things in less than optimal spots
>
> Well, the only curious thing is that it starts allocation at 48MB. But I suppose that's for a good reason - OFW and yaboot have to all fit into the same tiny 128MB address space after all.

Assuming it's trying to stick it on top of initrd, there's indeed not
enough space for > 9 MiB.

Regards,
Andreas

--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Factory CD boot problem

Andreas Färber
In reply to this post by Benjamin Herrenschmidt-2
Am 02.01.2014 22:26, schrieb Benjamin Herrenschmidt:
> On Thu, 2014-01-02 at 22:01 +0100, Alexander Graf wrote:
>> Well, the only curious thing is that it starts allocation at 48MB. But
>> I suppose that's for a good reason - OFW and yaboot have to all fit
>> into the same tiny 128MB address space after all.
>
> Check where OFW is ... (real-base)

# hexdump -C options/real-base
00000000  33 33 35 35 34 34 33 32  00                       |33554432.|
00000009
# hexdump -C options/real-size
00000000  31 36 37 37 37 32 31 36  00                       |16777216.|
00000009

Looks slightly odd to me...

power5:/proc/device-tree # hexdump -C options/virt-base
00000000  34 32 39 34 39 36 37 32  39 35 00                |4294967295.|
0000000b
power5:/proc/device-tree # hexdump -C options/virt-size
00000000  34 32 39 34 39 36 37 32  39 35 00                |4294967295.|
0000000b

# hexdump -C options/load-base
00000000  31 36 33 38 34 00                                 |16384.|
00000006

Cheers,
Andreas

--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Factory CD boot problem

Alexander Graf-4

On 07.01.2014, at 14:40, Andreas Färber <[hidden email]> wrote:

> Am 02.01.2014 22:26, schrieb Benjamin Herrenschmidt:
>> On Thu, 2014-01-02 at 22:01 +0100, Alexander Graf wrote:
>>> Well, the only curious thing is that it starts allocation at 48MB. But
>>> I suppose that's for a good reason - OFW and yaboot have to all fit
>>> into the same tiny 128MB address space after all.
>>
>> Check where OFW is ... (real-base)
>
> # hexdump -C options/real-base
> 00000000  33 33 35 35 34 34 33 32  00                       |33554432.|
> 00000009

>>> 33554432 / 1024. / 1024.
32.0

> # hexdump -C options/real-size
> 00000000  31 36 37 37 37 32 31 36  00                       |16777216.|
> 00000009

>>> 16777216 / 1024. / 1024.
16.0

>
> Looks slightly odd to me...
>
> power5:/proc/device-tree # hexdump -C options/virt-base
> 00000000  34 32 39 34 39 36 37 32  39 35 00                |4294967295.|

>>> hex(4294967295)
'0xffffffff'

> 0000000b
> power5:/proc/device-tree # hexdump -C options/virt-size
> 00000000  34 32 39 34 39 36 37 32  39 35 00                |4294967295.|

>>> hex(4294967295)
'0xffffffff'

> 0000000b
>
> # hexdump -C options/load-base
> 00000000  31 36 33 38 34 00                                 |16384.|

>>> hex(16384)
'0x4000'


Alex

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Factory CD boot problem

Andreas Färber
In reply to this post by Andreas Färber
Hi,

I've finally re-tried to reinstall Factory on my POWER5 box. The
installation started now, but towards the end of the installation I got:

 ┌────────────────────────────────────────────────────────────────────┐
 │ Error                                                              │
 │ Internal error. Please report a bug report with logs.              │
 │ Details: Cannot find in storage mbr disk                           │
 │ Caller:  /usr/share/YaST2/lib/bootloader/mbr_update.rb:64:in
`mbr_is_gpt?' │
 │                                                                    │
 │                                    [OK]                            │
 └────────────────────────────────────────────────────────────────────┘

It then rebooted into the new grub. Selecting the default entry then
resulted in:

Loading Linux 3.19.0-2-default ...
Loading initial ramdisk ...
OF stdout device is: /vdevice/vty@30000000
Preparing to boot Linux version 3.19.0-2-default (geeko@buildhost) (gcc
version 4.8.3 20141208 [gcc-4_8-branch revision 218481] (SUSE Linux) )
#1 SMP Tue Feb 17 20:11:30 UTC 2015 (1133f88)
Detected machine type: 0000000000000101
Max number of cores passed to firmware: 1024 (NR_CPUS = 2048)
Calling ibm,client-architecture-support... not implemented
command line: BOOT_IMAGE=/boot/vmlinux-3.19.0-2-default
root=UUID=4b63b0ad-ccbb-4372-b76c-d4537a8d40b1 quiet splash=silent
memory layout at init:
  memory_limit : 0000000000000000 (16 MB aligned)
  alloc_bottom : 0000000005230000
  alloc_top    : 0000000008000000
  alloc_top_hi : 0000000077000000
  rmo_top      : 0000000008000000
  ram_top      : 0000000077000000
found display   : /pci@800000020000002/display@1, opening... done
instantiating rtas at 0x00000000076a0000... done
prom_hold_cpus: skipped
copying OF device tree...
Building dt strings...
Building dt structure...
Device tree strings 0x0000000005240000 -> 0x000000000524135e
Device tree struct  0x0000000005250000 -> 0x0000000005260000
 -> smp_release_cpus()
spinning_secondaries = 1
 <- smp_release_cpus()
 <- setup_system()
../drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
pstore: decompression failed;returned -5
BTRFS: has skinny extents
NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd-udevd:412]

Is that the consequence of the above error message, or is this "just" a
kernel regression? Any suggestion how to fix?

Regards,
Andreas

--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton; HRB 21284 (AG Nürnberg)
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Factory CD boot problem

Dinar Valeev-2
Hi,
The yast issue has been fixed, it just needs to find its way to
Factory tree.. (btw we're Tumbleweed now)

Kernel issue, seems not related to bootloader issue.

On Sun, Feb 22, 2015 at 10:46 PM, Andreas Färber <[hidden email]> wrote:

> Hi,
>
> I've finally re-tried to reinstall Factory on my POWER5 box. The
> installation started now, but towards the end of the installation I got:
>
>  ┌────────────────────────────────────────────────────────────────────┐
>  │ Error                                                              │
>  │ Internal error. Please report a bug report with logs.              │
>  │ Details: Cannot find in storage mbr disk                           │
>  │ Caller:  /usr/share/YaST2/lib/bootloader/mbr_update.rb:64:in
> `mbr_is_gpt?' │
>  │                                                                    │
>  │                                    [OK]                            │
>  └────────────────────────────────────────────────────────────────────┘
>
> It then rebooted into the new grub. Selecting the default entry then
> resulted in:
>
> Loading Linux 3.19.0-2-default ...
> Loading initial ramdisk ...
> OF stdout device is: /vdevice/vty@30000000
> Preparing to boot Linux version 3.19.0-2-default (geeko@buildhost) (gcc
> version 4.8.3 20141208 [gcc-4_8-branch revision 218481] (SUSE Linux) )
> #1 SMP Tue Feb 17 20:11:30 UTC 2015 (1133f88)
> Detected machine type: 0000000000000101
> Max number of cores passed to firmware: 1024 (NR_CPUS = 2048)
> Calling ibm,client-architecture-support... not implemented
> command line: BOOT_IMAGE=/boot/vmlinux-3.19.0-2-default
> root=UUID=4b63b0ad-ccbb-4372-b76c-d4537a8d40b1 quiet splash=silent
> memory layout at init:
>   memory_limit : 0000000000000000 (16 MB aligned)
>   alloc_bottom : 0000000005230000
>   alloc_top    : 0000000008000000
>   alloc_top_hi : 0000000077000000
>   rmo_top      : 0000000008000000
>   ram_top      : 0000000077000000
> found display   : /pci@800000020000002/display@1, opening... done
> instantiating rtas at 0x00000000076a0000... done
> prom_hold_cpus: skipped
> copying OF device tree...
> Building dt strings...
> Building dt structure...
> Device tree strings 0x0000000005240000 -> 0x000000000524135e
> Device tree struct  0x0000000005250000 -> 0x0000000005260000
>  -> smp_release_cpus()
> spinning_secondaries = 1
>  <- smp_release_cpus()
>  <- setup_system()
> ../drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
> pstore: decompression failed;returned -5
> BTRFS: has skinny extents
> NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd-udevd:412]
>
> Is that the consequence of the above error message, or is this "just" a
> kernel regression? Any suggestion how to fix?
>
> Regards,
> Andreas
>
> --
> SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
> Graham Norton; HRB 21284 (AG Nürnberg)
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Factory CD boot problem

Andreas Färber
Hi,

Am 22.02.2015 um 22:49 schrieb Dinar Valeev:
> The yast issue has been fixed, it just needs to find its way to
> Factory tree..

So what exactly is it about?

> Kernel issue, seems not related to bootloader issue.

Selecting the recovery mode grub entry provides some more output:

Loading Linux 3.19.0-2-default ...
Loading initial ramdisk ...
OF stdout device is: /vdevice/vty@30000000
Preparing to boot Linux version 3.19.0-2-default (geeko@buildhost) (gcc
version 4.8.3 20141208 [gcc-4_8-branch revision 218481] (SUSE Linux) )
#1 SMP Tue Feb 17 20:11:30 UTC 2015 (1133f88)
Detected machine type: 0000000000000101
Max number of cores passed to firmware: 1024 (NR_CPUS = 2048)
Calling ibm,client-architecture-support... not implemented
command line: BOOT_IMAGE=/boot/vmlinux-3.19.0-2-default
root=UUID=4b63b0ad-ccbb-4372-b76c-d4537a8d40b1 x11failsafe
memory layout at init:
  memory_limit : 0000000000000000 (16 MB aligned)
  alloc_bottom : 0000000005230000
  alloc_top    : 0000000008000000
  alloc_top_hi : 0000000077000000
  rmo_top      : 0000000008000000
  ram_top      : 0000000077000000
found display   : /pci@800000020000002/display@1, opening... done
instantiating rtas at 0x00000000076a0000... done
prom_hold_cpus: skipped
copying OF device tree...
Building dt strings...
Building dt structure...
Device tree strings 0x0000000005240000 -> 0x000000000524135e
Device tree struct  0x0000000005250000 -> 0x0000000005260000
Using pSeries machine description
Page sizes from device-tree:
base_shift=12: shift=12, sllp=0x0000, avpnm=0x00000000, tlbiel=1, penc=0
base_shift=16: shift=16, sllp=0x0110, avpnm=0x00000000, tlbiel=1, penc=1
base_shift=24: shift=24, sllp=0x0100, avpnm=0x00000001, tlbiel=0, penc=0
base_shift=34: shift=34, sllp=0x0120, avpnm=0x000007ff, tlbiel=0, penc=3
Using 1TB segments
Found initrd at 0xc000000004a00000:0xc0000000052285cc
bootconsole [udbg0] enabled
Partition configured for 2 cpus.
CPU maps initialized for 2 threads per core
 -> smp_release_cpus()
spinning_secondaries = 1
 <- smp_release_cpus()
Starting Linux PPC64 #1 SMP Tue Feb 17 20:11:30 UTC 2015 (1133f88)
-----------------------------------------------------
ppc64_pft_size    = 0x19
phys_mem_size     = 0x77000000
cpu_features      = 0x080c02e018500041
  possible        = 0x1fffffef18500649
  always          = 0x0000000018100040
cpu_user_features = 0xcc026005 0x00000000
mmu_features      = 0x5c000003
firmware_features = 0x00000000005ffd5f
htab_hash_mask    = 0x3ffff
-----------------------------------------------------
 <- setup_system()
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Initializing cgroup subsys cpuacct
Linux version 3.19.0-2-default (geeko@buildhost) (gcc version 4.8.3
20141208 [gcc-4_8-branch revision 218481] (SUSE Linux) ) #1 SMP Tue Feb
17 20:11:30 UTC 2015 (1133f88)
numa: Initmem setup node 0 [mem 0x00000000-0x76ffffff]
numa:   NODE_DATA [mem 0x76fa9000-0x76fb3fff]
PCI host bridge /pci@800000020000002  ranges:
  IO 0x000003fe00200000..0x000003fe002fffff -> 0x0000000000000000
 MEM 0x0000040040000000..0x000004007fffffff -> 0x00000000c0000000
PCI host bridge /pci@800000020000003  ranges:
  IO 0x000003fe00300000..0x000003fe003fffff -> 0x0000000000000000
 MEM 0x0000040080000000..0x00000400bfffffff -> 0x00000000c0000000
PCI host bridge /pci@800000020000004  ranges:
  IO 0x000003fe00400000..0x000003fe004fffff -> 0x0000000000000000
 MEM 0x00000400c0000000..0x00000400ffffffff -> 0x00000000c0000000
PPC64 nvram contains 7168 bytes
Zone ranges:
  DMA      [mem 0x00000000-0x76ffffff]
  DMA32    empty
  Normal   empty
Movable zone start for each node
Early memory node ranges
  node   0: [mem 0x00000000-0x76ffffff]
Initmem setup node 0 [mem 0x00000000-0x76ffffff]
PERCPU: Embedded 3 pages/cpu @c000000076e00000 s114432 r0 d82176 u524288
Built 1 zonelists in Node order, mobility grouping on.  Total pages: 30430
Policy zone: DMA
Kernel command line: BOOT_IMAGE=/boot/vmlinux-3.19.0-2-default
root=UUID=4b63b0ad-ccbb-4372-b76c-d4537a8d40b1 x11failsafe
PID hash table entries: 4096 (order: -1, 32768 bytes)
Sorting __ex_table...
Memory: 1897920K/1949696K available (8512K kernel code, 2048K rwdata,
3376K rodata, 7168K init, 3274K bss, 51776K reserved, 0K cma-reserved)
Hierarchical RCU implementation.
        CONFIG_RCU_FANOUT set to non-default value of 32
        RCU dyntick-idle grace-period acceleration is enabled.
        RCU restricting CPUs from NR_CPUS=2048 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
NR_IRQS:512 nr_irqs:512 16
        Offload RCU callbacks from all CPUs
        Offload RCU callbacks from CPUs: 0-1.
clocksource: timebase mult[21b5431] shift[23] registereconsole [hvc0]
enabled
console [hvc0] enabled
bootconsole [udbg0] disabled
bootconsole [udbg0] disabled
mempolicy: Enabling automatic NUMA balancing. Configure with
numa_balancing= or the kernel.numa_balancing sysctl
pid_max: default: 32768 minimum: 301
Security Framework initialized
AppArmor: AppArmor initialized
Dentry cache hash table entries: 262144 (order: 5, 2097152 bytes)
Inode-cache hash table entries: 131072 (order: 4, 1048576 bytes)
Mount-cache hash table entries: 8192 (order: 0, 65536 bytes)
Mountpoint-cache hash table entries: 8192 (order: 0, 65536 bytes)
Initializing cgroup subsys memory
Initializing cgroup subsys devices
Initializing cgroup subsys freezer
Initializing cgroup subsys net_cls
Initializing cgroup subsys blkio
Initializing cgroup subsys perf_event
Initializing cgroup subsys net_prio
Initializing cgroup subsys hugetlb
ftrace: allocating 22958 entries in 9 pages
EEH: pSeries platform initialized
POWER5+/++ performance monitor hardware support registered
Brought up 2 CPUs
devtmpfs: initialized
EEH: devices created
NET: Registered protocol family 16
EEH: PCI Enhanced I/O Error Handling Enabled
IBM eBus Device Driver
cpuidle: using governor ladder
cpuidle: using governor menu
pstore: Registered nvram as persistent store backend
PCI: Probing PCI hardware
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io  0x10000-0x10ffff] (bus address
[0x0000-0xfffff])
pci_bus 0000:00: root bus resource [mem 0x40040000000-0x4007fffffff]
(bus address [0xc0000000-0xffffffff])
pci_bus 0000:00: root bus resource [bus 00-ff]
IOMMU table initialized, virtual merging enabled
PCI host bridge to bus 0001:00
pci_bus 0001:00: root bus resource [io  0x120000-0x21ffff] (bus address
[0x0000-0xfffff])
pci_bus 0001:00: root bus resource [mem 0x40080000000-0x400bfffffff]
(bus address [0xc0000000-0xffffffff])
pci_bus 0001:00: root bus resource [bus 00-ff]
PCI host bridge to bus 0002:00
pci_bus 0002:00: root bus resource [io  0x230000-0x32ffff] (bus address
[0x0000-0xfffff])
pci_bus 0002:00: root bus resource [mem 0x400c0000000-0x400ffffffff]
(bus address [0xc0000000-0xffffffff])
pci_bus 0002:00: root bus resource [bus 00-ff]
vgaarb: device added: PCI:0000:00:01.0,decodes=io+mem,owns=mem,locks=none
vgaarb: loaded
vgaarb: bridge control possible 0000:00:01.0
EDAC MC: Ver: 3.0.0
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
Switched to clocksource timebase
AppArmor: AppArmor Filesystem Enabled
NET: Registered protocol family 2
TCP established hash table entries: 16384 (order: 1, 131072 bytes)
TCP bind hash table entries: 16384 (order: 2, 262144 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP: reno registered
UDP hash table entries: 2048 (order: 0, 65536 bytes)
UDP-Lite hash table entries: 2048 (order: 0, 65536 bytes)
NET: Registered protocol family 1
Unpacking initramfs...
Freeing initrd memory: 8320K (c000000004a00000 - c000000005220000)
futex hash table entries: 512 (order: 0, 65536 bytes)
Initialise system trusted keyring
audit: initializing netlink subsys (disabled)
audit: type=2000 audit(1424645067.460:1): initialized
HugeTLB registered 16 MB page size, pre-allocated 0 pages
HugeTLB registered 16 GB page size, pre-allocated 0 pages
zpool: loaded
zbud: loaded
VFS: Disk quotas dquot_6.5.2
VFS: Dquot-cache hash table entries: 8192 (order 0, 65536 bytes)
Key type big_key registered
Key type asymmetric registered
Asymmetric key parser 'x509' registered
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.4
rpaphp: RPA HOT Plug PCI Controller Driver version: 0.1
rpaphp: Slot [U787F.001.DPM2D0H-P1-C4] registered
rpaphp: Slot [U787F.001.DPM2D0H-P1-C3] registered
rpaphp: Slot [U787F.001.DPM2D0H-P1-C5] registered
rpaphp: Slot [U787F.001.DPM2D0H-P1-C6] registered
rpaphp: Slot [U787F.001.DPM2D0H-P1-C1] registered
rpaphp: Slot [U787F.001.DPM2D0H-P1-C2] registered
Console: switching to colour frame buffer device 160x64
fb0: IBM GXT6500P frame buffer device
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
pmac_zilog: 0.6 (Benjamin Herrenschmidt <[hidden email]>)
pseries_rng: Registering IBM pSeries RNG driver
Uniform Multi-Platform E-IDE driver
mousedev: PS/2 mouse device common for all mice
ledtrig-cpu: registered to indicate activity on CPUs
hidraw: raw HID events driver (C) Jiri Kosina
TCP: cubic registered
NET: Registered protocol family 10
NET: Registered protocol family 15
Loading compiled-in X.509 certificates
Loaded X.509 cert 'openSUSE Secure Boot Signkey:
0332fa9cbf0d88bf21924b0de82a09a54d5defc8'
registered taskstats version 1
AppArmor: AppArmor sha1 policy hashing enabled
../drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Freeing unused kernel memory: 7168K (c000000000bb0000 - c0000000012b0000)
pstore: decompression failed;returned -5
random: systemd urandom read with 10 bits of entropy available
systemd[1]: systemd 210 running in system mode. (+PAM -LIBWRAP +AUDIT
+SELINUX -IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP +APPARMOR)
systemd[1]: Detected architecture 'ppc64'.
systemd[1]: Running in initial RAM disk.

Welcome to openSUSE 20150129 (Harlequin) (ppc64) dracut-037-30.1
(Initramfs)!

systemd[1]: Set hostname to <linux-3e20>.
systemd[1]: Expecting device
dev-disk-by\x2duuid-4b63b0ad\x2dccbb\x2d4372\x2db76c\x2dd4537a8d40b1.device...
         Expecting device
dev-disk-by\x2duuid-4b63b0ad\x2dccb...d40b1.device...
systemd[1]: Starting Timers.
[  OK  ] Reached target Timers.
systemd[1]: Reached target Timers.
systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
systemd[1]: Starting Paths.
[  OK  ] Reached target Paths.
systemd[1]: Reached target Paths.
systemd[1]: Starting -.slice.
[  OK  ] Created slice -.slice.
systemd[1]: Created slice -.slice.
systemd[1]: Starting udev Kernel Socket.
[  OK  ] Listening on udev Kernel Socket.
systemd[1]: Listening on udev Kernel Socket.
systemd[1]: Starting udev Control Socket.
[  OK  ] Listening on udev Control Socket.
systemd[1]: Listening on udev Control Socket.
systemd[1]: Starting Journal Socket.
[  OK  ] Listening on Journal Socket.
systemd[1]: Listening on Journal Socket.
systemd[1]: Starting Sockets.
[  OK  ] Reached target Sockets.
systemd[1]: Reached target Sockets.
systemd[1]: Starting System Slice.
[  OK  ] Created slice System Slice.
systemd[1]: Created slice System Slice.
systemd[1]: Starting system-systemd\x2dfsck.slice.
[  OK  ] Created slice system-systemd\x2dfsck.slice.
systemd[1]: Created slice system-systemd\x2dfsck.slice.
systemd[1]: Starting dracut cmdline hook...
         Starting dracut cmdline hook...
systemd[1]: Starting Create list of required static device nodes for the
current kernel...
         Starting Create list of required static device nodes...rrent
kernel...
systemd[1]: Starting Load Kernel Modules...
         Starting Load Kernel Modules...
systemd[1]: Starting Journal Service...
SCSI subsystem initialized
         Starting Journal Service...
systemd[1]: Starting Slices.
[  OK  ] Reached target Slices.
systemd[1]: Reached target Slices.
systemd[1]: Starting Swap.
[  OK  ] Reached target Swap.
systemd[1]: Reached target Swap.
systemd[1]: Starting Local File Systems.
[  OK  ] Reached target Local File Systems.
systemd[1]: Reached target Local File Systems.
[  OK  ] Started Journal Service.
systemd[1]: Started Journal Service.
[  OK  ] Started dracut cmdline hook.
[  OK  ] Started Create list of required static device nodes ...current
kernel.
[  OK  ] Started Load Kernel Modules.
         Starting Apply Kernel Variables...
         Starting Create static device nodes in /dev...
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Started Create static device nodes in /dev.
         Starting udev Kernel Device Manager...
[  OK  ] Started udev Kernel Device Manager.
         Starting dracut pre-trigger hook...
[  OK  ] Started dracut pre-trigger hook.
         Starting udev Coldplug all Devices...
[  OK  ] Started udev Coldplug all Devices.
         Starting dracut initqueue hook...
[  OK  ] Reached target System Initialization.
[  OK  ] Reached target Basic System.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
ipr: IBM Power RAID SCSI Device Driver version: 2.6.0 (November 16, 2012)
ipr 0001:d0:01.0: Found IOA with IRQ: 325
ipr 0001:d0:01.0: Cannot enable MSI.
ipr 0001:d0:01.0: Starting IOA initialization sequence.
scsi host0: IBM 0 Storage Adapter
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ehci-pci: EHCI PCI platform driver
ipr 0001:d0:01.0: Adapter firmware version: 0510006D
ehci-pci 0002:cc:01.2: EHCI Host Controller
ehci-pci 0002:cc:01.2: new USB bus registered, assigned bus number 1
ehci-pci 0002:cc:01.2: irq 276, io mem 0x400f8002000
pata_pdc2027x 0001:cc:01.0: enabling device (0002 -> 0003)
ipr 0001:d0:01.0: IOA initialized.
ehci-pci 0002:cc:01.2: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 3.19.0-2-default ehci_hcd
usb usb1: SerialNumber: 0002:cc:01.2
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 5 ports detected
ohci-pci: OHCI PCI platform driver
ohci-pci 0002:cc:01.0: OHCI PCI host controller
ohci-pci 0002:cc:01.0: new USB bus registered, assigned bus number 2
ohci-pci 0002:cc:01.0: irq 276, io mem 0x400f8001000
pata_pdc2027x 0001:cc:01.0: PLL input clock 32754 kHz
scsi host1: pata_pdc2027x
scsi host2: pata_pdc2027x
ata1: PATA max UDMA/133 mmio m16384@0x400b8000000 cmd 0x400b80017c0 irq 324
ata2: PATA max UDMA/133 mmio m16384@0x400b8000000 cmd 0x400b80015c0 irq 324
scsi 0:255:255:255: No Device         IBM      573E001          0150 PQ:
0 ANSI: 0
scsi 0:255:255:255: Attached scsi generic sg0 type 31
scsi 0:0:15:0: Enclosure         IBM      VSBPD4E1  U4SCSI 1203 PQ: 0
ANSI: 2
scsi 0:0:15:0: Attached scsi generic sg1 type 13
scsi 0:0:8:0: Direct-Access     IBM   H0 HUS103073FL3800  RPQR PQ: 0 ANSI: 4
scsi 0:0:8:0: Attached scsi generic sg2 type 0
usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: OHCI PCI host controller
usb usb2: Manufacturer: Linux 3.19.0-2-default ohci_hcd
usb usb2: SerialNumber: 0002:cc:01.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 3 ports detected
sd 0:0:8:0: [sda] 143374000 512-byte logical blocks: (73.4 GB/68.3 GiB)
ohci-pci 0002:cc:01.1: OHCI PCI host controller
ohci-pci 0002:cc:01.1: new USB bus registered, assigned bus number 3
ohci-pci 0002:cc:01.1: irq 276, io mem 0x400f8000000
sd 0:0:8:0: [sda] Write Protect is off
sd 0:0:8:0: [sda] Write cache: disabled, read cache: enabled, supports
DPO and FUA
usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb3: Product: OHCI PCI host controller
usb usb3: Manufacturer: Linux 3.19.0-2-default ohci_hcd
usb usb3: SerialNumber: 0002:cc:01.1
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
 sda: sda1 sda2 < sda5 sda6 sda7 >
ata1.00: ATAPI: IBM     DROM0020541, P633, max UDMA/66
sd 0:0:8:0: [sda] Attached SCSI disk
ata1.00: configured for UDMA/66
scsi 1:0:0:0: CD-ROM            IBM      DROM0020541      P633 PQ: 0 ANSI: 2
scsi 1:0:0:0: Attached scsi generic sg3 type 5
sr 1:0:0:0: [sr0] scsi3-mmc drive: 24x/24x cd/rw xa/form2 cdda tray
cdrom: Uniform CD-ROM driver Revision: 3.20
raid6: int64x1   2057 MB/s
raid6: int64x2   2881 MB/s
raid6: int64x4   3324 MB/s
raid6: int64x8   1538 MB/s
raid6: using algorithm int64x4 (3324 MB/s)
raid6: using intx1 recovery algorithm
xor: measuring software checksum speed
   8regs     :  5766.400 MB/sec
   8regs_prefetch:  5568.000 MB/sec
   32regs    :  6048.000 MB/sec
   32regs_prefetch:  5920.000 MB/sec
xor: using function: 32regs (6048.000 MB/sec)
Btrfs loaded, assert=on
BTRFS: device fsid b7055861-eae1-4406-b13b-63bc6d7c27b2 devid 1 transid
1987 /dev/sda7
BTRFS: device fsid 4b63b0ad-ccbb-4372-b76c-d4537a8d40b1 devid 1 transid
52 /dev/sda6
[  OK  ] Found device HUS103073FL3800.
[  OK  ] Started dracut initqueue hook.
         Starting dracut pre-mount hook...
PM: Starting manual resume from disk
[  OK  ] Reached target Remote File Systems (Pre).
[  OK  ] Reached target Remote File Systems.
[  OK  ] Started dracut pre-mount hook.
         Starting File System Check on
/dev/disk/by-uuid/4b63...d4537a8d40b1...
[  OK  ] Started File System Check on
/dev/disk/by-uuid/4b63b...c-d4537a8d40b1.
         Mounting /sysroot...
BTRFS info (device sda6): disk space caching is enabled
BTRFS: has skinny extents
[  OK  ] Mounted /sysroot.
[  OK  ] Reached target Initrd Root File System.
         Starting Reload Configuration from the Real Root...
[  OK  ] Started Reload Configuration from the Real Root.
[  OK  ] Reached target Initrd File Systems.
[  OK  ] Reached target Initrd Default Target.
systemd-journald[148]: Received SIGTERM from PID 1 (systemd).

Welcome to openSUSE 20150129 (Harlequin) (ppc64)!

[  OK  ] Stopped Switch Root.
[  OK  ] Stopped target Switch Root.
[  OK  ] Stopped target Initrd File Systems.
         Stopping File System Check on
/dev/disk/by-uuid/4b63...d4537a8d40b1...
[  OK  ] Stopped File System Check on
/dev/disk/by-uuid/4b63b...c-d4537a8d40b1.
[  OK  ] Removed slice system-systemd\x2dfsck.slice.
[  OK  ] Stopped target Initrd Root File System.
[  OK  ] Created slice User and Session Slice.
[  OK  ] Created slice system-serial\x2dgetty.slice.
         Expecting device dev-hvc0.device...
[  OK  ] Created slice system-getty.slice.
[  OK  ] Reached target Remote File Systems (Pre).
         Starting Collect Read-Ahead Data...
[  OK  ] Reached target Slices.
[  OK  ] Listening on Delayed Shutdown Socket.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
         Starting Rule generator for /dev/root symlink...
[  OK  ] Stopped Trigger Flushing of Journal to Persistent Storage.
         Stopping Journal Service...
[  OK  ] Stopped Journal Service.
[  OK  ] Reached target Paths.
         Mounting Debug File System...
[  OK  ] Set up automount Arbitrary Executable File Formats F...utomount
Point.
         Starting Create list of required static device nodes...rrent
kernel...
         Mounting POSIX Message Queue File System...
         Mounting Huge Pages File System...
[  OK  ] Listening on LVM2 metadata daemon socket.
[  OK  ] Listening on Device-mapper event daemon FIFOs.
         Starting Device-mapper event daemon...
[  OK  ] Started Device-mapper event daemon.
         Expecting device
dev-disk-by\x2duuid-7421a83d\x2ddf9...2781d.device...
[  OK  ] Listening on udev Kernel Socket.
[  OK  ] Listening on udev Control Socket.
         Expecting device
dev-disk-by\x2duuid-4b63b0ad\x2dccb...d40b1.device...
[  OK  ] Mounted Debug File System.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Mounted Huge Pages File System.
[  OK  ] Started Collect Read-Ahead Data.
[  OK  ] Started Rule generator for /dev/root symlink.
[  OK  ] Started Create list of required static device nodes ...current
kernel.
         Starting Create static device nodes in /dev...
         Starting Load Kernel Modules...
         Starting Setup Virtual Console...
         Starting Remount Root and Kernel File Systems...
BTRFS info (device sda6): disk space caching is enabled
[  OK  ] Started Create static device nodes in /dev.
[  OK  ] Started Load Kernel Modules.
[  OK  ] Started Remount Root and Kernel File Systems.
         Starting Load/Save Random Seed...
         Starting Apply Kernel Variables...
         Starting udev Kernel Device Manager...
[  OK  ] Reached target Local File Systems (Pre).
[  OK  ] Started Setup Virtual Console.
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Started udev Kernel Device Manager.
         Starting Entropy Daemon based on the HAVEGE algorithm...
[  OK  ] Started Entropy Daemon based on the HAVEGE algorithm.
         Starting Journal Service...
         Starting udev Coldplug all Devices...
[  OK  ] Started Journal Service.
[  OK  ] Started udev Coldplug all Devices.
         Starting udev Wait for Complete Device Initialization...
rtc-generic rtc-generic: rtc core: registered rtc-generic as rtc0
[  OK  ] Found device /dev/hvc0.
e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
e1000: Copyright (c) 1999-2006 Intel Corporation.
e1000 0002:d0:01.0: enabling device (0000 -> 0002)
NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd-udevd:423]
Modules linked in: ses(+) windfarm_rm31(-) e1000(+) enclosure
rtc_generic btrfs xor raid6_pq sr_mod cdrom sd_mod ohci_pci
pata_pdc2027x ehci_pci ohci_hcd ehci_hcd ipr usbcore libata usb_common
sg scsi_mod
CPU: 0 PID: 423 Comm: systemd-udevd Not tainted 3.19.0-2-default #1
task: c0000000046f4b10 ti: c00000006f10c000 task.ti: c00000006f10c000
NIP: c00000000083a474 LR: c00000000083a4b8 CTR: c00000000083a3d0
REGS: c00000006f10e880 TRAP: 0901   Not tainted  (3.19.0-2-default)
MSR: 8000000000009032 <SF,EE,ME,IR,DR,RI>  CR: 24044424  XER: 00000000
SOFTE: 1
GPR00: d000000000ef7004 c00000006f10eb00 c00000000143e9b8 0000000000000001
GPR04: c00000000419c470 0000000000000000 c00000007517bb60 000000000000000a
GPR08: 0000000000000010 0000000080000001 0000000000000000 d000000000f06610
GPR12: 0000000024042422 c000000007220000
NIP [c00000000083a474] ._raw_spin_lock_irqsave+0xa4/0x110
LR [c00000000083a4b8] ._raw_spin_lock_irqsave+0xe8/0x110
Call Trace:
[c00000006f10eb00] [c00000006f10eb90] 0xc00000006f10eb90 (unreliable)
[c00000006f10eb90] [d000000000ef7004] .ipr_queuecommand+0x84/0x760 [ipr]
[c00000006f10ec50] [d00000000081d9f0] .scsi_dispatch_cmd+0xe0/0x360
[scsi_mod]
[c00000006f10ece0] [d00000000081f61c] .scsi_queue_rq+0x77c/0x8e0 [scsi_mod]
[c00000006f10edc0] [c000000000498370] .__blk_mq_run_hw_queue+0x2b0/0x4b0
[c00000006f10eed0] [c0000000004993a8] .blk_mq_run_hw_queue+0xd8/0x100
[c00000006f10ef50] [c00000000049a864] .blk_sq_make_request+0x2e4/0x410
[c00000006f10f020] [c00000000048956c] .generic_make_request+0xcc/0x190
[c00000006f10f0b0] [c0000000004896f8] .submit_bio+0xc8/0x1d0
[c00000006f10f170] [d000000001b4a33c] .submit_stripe_bio+0x9c/0x110 [btrfs]
[c00000006f10f220] [d000000001b50944] .btrfs_map_bio+0x2f4/0x590 [btrfs]
[c00000006f10f360] [d000000001b1bdf4] .btrfs_submit_bio_hook+0xb4/0x290
[btrfs]
[c00000006f10f420] [d000000001b3b504] .submit_one_bio+0xc4/0x140 [btrfs]
[c00000006f10f4c0] [d000000001b43d7c] .extent_readpages+0x16c/0x210 [btrfs]
[c00000006f10f630] [d000000001b1c740] .btrfs_readpages+0x40/0x60 [btrfs]
[c00000006f10f6c0] [c00000000023e60c] .__do_page_cache_readahead+0x1ac/0x2f0
[c00000006f10f7e0] [c00000000023e8c4] .ondemand_readahead+0x174/0x2d0
[c00000006f10f890] [c00000000022f418] .generic_file_read_iter+0x488/0x670
[c00000006f10f9c0] [c0000000002c7378] .new_sync_read+0xa8/0x120
[c00000006f10fae0] [c0000000002c8a58] .__vfs_read+0x68/0x120
[c00000006f10fb70] [c0000000002c8bac] .vfs_read+0x9c/0x1b0
[c00000006f10fc10] [c0000000002d070c] .kernel_read+0x5c/0x90
[c00000006f10fcc0] [c0000000002d2824]
.do_execveat_common.isra.20+0x544/0x7f0
[c00000006f10fda0] [c0000000002d2e98] .SyS_execve+0x38/0x50
[c00000006f10fe30] [c0000000000092fc] syscall_exit+0x0/0x7c
Instruction dump:
81810008 eba1ffe8 ebc1fff0 7c0803a6 ebe1fff8 7d908120 4e800020 8bad02ba
4092004c 38600000 4b7d5cf5 60000000 <7c210b78> e92d0000 89290009 792affe3

Regards,
Andreas

--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton; HRB 21284 (AG Nürnberg)
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Factory CD boot problem

Dinar Valeev-2
On Mon, Feb 23, 2015 at 12:01 AM, Andreas Färber <[hidden email]> wrote:
> Hi,
>
> Am 22.02.2015 um 22:49 schrieb Dinar Valeev:
>> The yast issue has been fixed, it just needs to find its way to
>> Factory tree..
>
> So what exactly is it about?
http://bugzilla.opensuse.org/show_bug.cgi?id=917833

>
>> Kernel issue, seems not related to bootloader issue.
>
> Selecting the recovery mode grub entry provides some more output:
>
> Loading Linux 3.19.0-2-default ...
> Loading initial ramdisk ...
> OF stdout device is: /vdevice/vty@30000000
> Preparing to boot Linux version 3.19.0-2-default (geeko@buildhost) (gcc
> version 4.8.3 20141208 [gcc-4_8-branch revision 218481] (SUSE Linux) )
> #1 SMP Tue Feb 17 20:11:30 UTC 2015 (1133f88)
> Detected machine type: 0000000000000101
> Max number of cores passed to firmware: 1024 (NR_CPUS = 2048)
> Calling ibm,client-architecture-support... not implemented
> command line: BOOT_IMAGE=/boot/vmlinux-3.19.0-2-default
> root=UUID=4b63b0ad-ccbb-4372-b76c-d4537a8d40b1 x11failsafe
> memory layout at init:
>   memory_limit : 0000000000000000 (16 MB aligned)
>   alloc_bottom : 0000000005230000
>   alloc_top    : 0000000008000000
>   alloc_top_hi : 0000000077000000
>   rmo_top      : 0000000008000000
>   ram_top      : 0000000077000000
> found display   : /pci@800000020000002/display@1, opening... done
> instantiating rtas at 0x00000000076a0000... done
> prom_hold_cpus: skipped
> copying OF device tree...
> Building dt strings...
> Building dt structure...
> Device tree strings 0x0000000005240000 -> 0x000000000524135e
> Device tree struct  0x0000000005250000 -> 0x0000000005260000
> Using pSeries machine description
> Page sizes from device-tree:
> base_shift=12: shift=12, sllp=0x0000, avpnm=0x00000000, tlbiel=1, penc=0
> base_shift=16: shift=16, sllp=0x0110, avpnm=0x00000000, tlbiel=1, penc=1
> base_shift=24: shift=24, sllp=0x0100, avpnm=0x00000001, tlbiel=0, penc=0
> base_shift=34: shift=34, sllp=0x0120, avpnm=0x000007ff, tlbiel=0, penc=3
> Using 1TB segments
> Found initrd at 0xc000000004a00000:0xc0000000052285cc
> bootconsole [udbg0] enabled
> Partition configured for 2 cpus.
> CPU maps initialized for 2 threads per core
>  -> smp_release_cpus()
> spinning_secondaries = 1
>  <- smp_release_cpus()
> Starting Linux PPC64 #1 SMP Tue Feb 17 20:11:30 UTC 2015 (1133f88)
> -----------------------------------------------------
> ppc64_pft_size    = 0x19
> phys_mem_size     = 0x77000000
> cpu_features      = 0x080c02e018500041
>   possible        = 0x1fffffef18500649
>   always          = 0x0000000018100040
> cpu_user_features = 0xcc026005 0x00000000
> mmu_features      = 0x5c000003
> firmware_features = 0x00000000005ffd5f
> htab_hash_mask    = 0x3ffff
> -----------------------------------------------------
>  <- setup_system()
> Initializing cgroup subsys cpuset
> Initializing cgroup subsys cpu
> Initializing cgroup subsys cpuacct
> Linux version 3.19.0-2-default (geeko@buildhost) (gcc version 4.8.3
> 20141208 [gcc-4_8-branch revision 218481] (SUSE Linux) ) #1 SMP Tue Feb
> 17 20:11:30 UTC 2015 (1133f88)
> numa: Initmem setup node 0 [mem 0x00000000-0x76ffffff]
> numa:   NODE_DATA [mem 0x76fa9000-0x76fb3fff]
> PCI host bridge /pci@800000020000002  ranges:
>   IO 0x000003fe00200000..0x000003fe002fffff -> 0x0000000000000000
>  MEM 0x0000040040000000..0x000004007fffffff -> 0x00000000c0000000
> PCI host bridge /pci@800000020000003  ranges:
>   IO 0x000003fe00300000..0x000003fe003fffff -> 0x0000000000000000
>  MEM 0x0000040080000000..0x00000400bfffffff -> 0x00000000c0000000
> PCI host bridge /pci@800000020000004  ranges:
>   IO 0x000003fe00400000..0x000003fe004fffff -> 0x0000000000000000
>  MEM 0x00000400c0000000..0x00000400ffffffff -> 0x00000000c0000000
> PPC64 nvram contains 7168 bytes
> Zone ranges:
>   DMA      [mem 0x00000000-0x76ffffff]
>   DMA32    empty
>   Normal   empty
> Movable zone start for each node
> Early memory node ranges
>   node   0: [mem 0x00000000-0x76ffffff]
> Initmem setup node 0 [mem 0x00000000-0x76ffffff]
> PERCPU: Embedded 3 pages/cpu @c000000076e00000 s114432 r0 d82176 u524288
> Built 1 zonelists in Node order, mobility grouping on.  Total pages: 30430
> Policy zone: DMA
> Kernel command line: BOOT_IMAGE=/boot/vmlinux-3.19.0-2-default
> root=UUID=4b63b0ad-ccbb-4372-b76c-d4537a8d40b1 x11failsafe
> PID hash table entries: 4096 (order: -1, 32768 bytes)
> Sorting __ex_table...
> Memory: 1897920K/1949696K available (8512K kernel code, 2048K rwdata,
> 3376K rodata, 7168K init, 3274K bss, 51776K reserved, 0K cma-reserved)
> Hierarchical RCU implementation.
>         CONFIG_RCU_FANOUT set to non-default value of 32
>         RCU dyntick-idle grace-period acceleration is enabled.
>         RCU restricting CPUs from NR_CPUS=2048 to nr_cpu_ids=2.
> RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
> NR_IRQS:512 nr_irqs:512 16
>         Offload RCU callbacks from all CPUs
>         Offload RCU callbacks from CPUs: 0-1.
> clocksource: timebase mult[21b5431] shift[23] registereconsole [hvc0]
> enabled
> console [hvc0] enabled
> bootconsole [udbg0] disabled
> bootconsole [udbg0] disabled
> mempolicy: Enabling automatic NUMA balancing. Configure with
> numa_balancing= or the kernel.numa_balancing sysctl
> pid_max: default: 32768 minimum: 301
> Security Framework initialized
> AppArmor: AppArmor initialized
> Dentry cache hash table entries: 262144 (order: 5, 2097152 bytes)
> Inode-cache hash table entries: 131072 (order: 4, 1048576 bytes)
> Mount-cache hash table entries: 8192 (order: 0, 65536 bytes)
> Mountpoint-cache hash table entries: 8192 (order: 0, 65536 bytes)
> Initializing cgroup subsys memory
> Initializing cgroup subsys devices
> Initializing cgroup subsys freezer
> Initializing cgroup subsys net_cls
> Initializing cgroup subsys blkio
> Initializing cgroup subsys perf_event
> Initializing cgroup subsys net_prio
> Initializing cgroup subsys hugetlb
> ftrace: allocating 22958 entries in 9 pages
> EEH: pSeries platform initialized
> POWER5+/++ performance monitor hardware support registered
> Brought up 2 CPUs
> devtmpfs: initialized
> EEH: devices created
> NET: Registered protocol family 16
> EEH: PCI Enhanced I/O Error Handling Enabled
> IBM eBus Device Driver
> cpuidle: using governor ladder
> cpuidle: using governor menu
> pstore: Registered nvram as persistent store backend
> PCI: Probing PCI hardware
> PCI host bridge to bus 0000:00
> pci_bus 0000:00: root bus resource [io  0x10000-0x10ffff] (bus address
> [0x0000-0xfffff])
> pci_bus 0000:00: root bus resource [mem 0x40040000000-0x4007fffffff]
> (bus address [0xc0000000-0xffffffff])
> pci_bus 0000:00: root bus resource [bus 00-ff]
> IOMMU table initialized, virtual merging enabled
> PCI host bridge to bus 0001:00
> pci_bus 0001:00: root bus resource [io  0x120000-0x21ffff] (bus address
> [0x0000-0xfffff])
> pci_bus 0001:00: root bus resource [mem 0x40080000000-0x400bfffffff]
> (bus address [0xc0000000-0xffffffff])
> pci_bus 0001:00: root bus resource [bus 00-ff]
> PCI host bridge to bus 0002:00
> pci_bus 0002:00: root bus resource [io  0x230000-0x32ffff] (bus address
> [0x0000-0xfffff])
> pci_bus 0002:00: root bus resource [mem 0x400c0000000-0x400ffffffff]
> (bus address [0xc0000000-0xffffffff])
> pci_bus 0002:00: root bus resource [bus 00-ff]
> vgaarb: device added: PCI:0000:00:01.0,decodes=io+mem,owns=mem,locks=none
> vgaarb: loaded
> vgaarb: bridge control possible 0000:00:01.0
> EDAC MC: Ver: 3.0.0
> NetLabel: Initializing
> NetLabel:  domain hash size = 128
> NetLabel:  protocols = UNLABELED CIPSOv4
> NetLabel:  unlabeled traffic allowed by default
> Switched to clocksource timebase
> AppArmor: AppArmor Filesystem Enabled
> NET: Registered protocol family 2
> TCP established hash table entries: 16384 (order: 1, 131072 bytes)
> TCP bind hash table entries: 16384 (order: 2, 262144 bytes)
> TCP: Hash tables configured (established 16384 bind 16384)
> TCP: reno registered
> UDP hash table entries: 2048 (order: 0, 65536 bytes)
> UDP-Lite hash table entries: 2048 (order: 0, 65536 bytes)
> NET: Registered protocol family 1
> Unpacking initramfs...
> Freeing initrd memory: 8320K (c000000004a00000 - c000000005220000)
> futex hash table entries: 512 (order: 0, 65536 bytes)
> Initialise system trusted keyring
> audit: initializing netlink subsys (disabled)
> audit: type=2000 audit(1424645067.460:1): initialized
> HugeTLB registered 16 MB page size, pre-allocated 0 pages
> HugeTLB registered 16 GB page size, pre-allocated 0 pages
> zpool: loaded
> zbud: loaded
> VFS: Disk quotas dquot_6.5.2
> VFS: Dquot-cache hash table entries: 8192 (order 0, 65536 bytes)
> Key type big_key registered
> Key type asymmetric registered
> Asymmetric key parser 'x509' registered
> Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
> io scheduler noop registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> pci_hotplug: PCI Hot Plug PCI Core version: 0.5
> pciehp: PCI Express Hot Plug Controller Driver version: 0.4
> rpaphp: RPA HOT Plug PCI Controller Driver version: 0.1
> rpaphp: Slot [U787F.001.DPM2D0H-P1-C4] registered
> rpaphp: Slot [U787F.001.DPM2D0H-P1-C3] registered
> rpaphp: Slot [U787F.001.DPM2D0H-P1-C5] registered
> rpaphp: Slot [U787F.001.DPM2D0H-P1-C6] registered
> rpaphp: Slot [U787F.001.DPM2D0H-P1-C1] registered
> rpaphp: Slot [U787F.001.DPM2D0H-P1-C2] registered
> Console: switching to colour frame buffer device 160x64
> fb0: IBM GXT6500P frame buffer device
> Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
> pmac_zilog: 0.6 (Benjamin Herrenschmidt <[hidden email]>)
> pseries_rng: Registering IBM pSeries RNG driver
> Uniform Multi-Platform E-IDE driver
> mousedev: PS/2 mouse device common for all mice
> ledtrig-cpu: registered to indicate activity on CPUs
> hidraw: raw HID events driver (C) Jiri Kosina
> TCP: cubic registered
> NET: Registered protocol family 10
> NET: Registered protocol family 15
> Loading compiled-in X.509 certificates
> Loaded X.509 cert 'openSUSE Secure Boot Signkey:
> 0332fa9cbf0d88bf21924b0de82a09a54d5defc8'
> registered taskstats version 1
> AppArmor: AppArmor sha1 policy hashing enabled
> ../drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
> Freeing unused kernel memory: 7168K (c000000000bb0000 - c0000000012b0000)
> pstore: decompression failed;returned -5
> random: systemd urandom read with 10 bits of entropy available
> systemd[1]: systemd 210 running in system mode. (+PAM -LIBWRAP +AUDIT
> +SELINUX -IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP +APPARMOR)
> systemd[1]: Detected architecture 'ppc64'.
> systemd[1]: Running in initial RAM disk.
>
> Welcome to openSUSE 20150129 (Harlequin) (ppc64) dracut-037-30.1
> (Initramfs)!
>
> systemd[1]: Set hostname to <linux-3e20>.
> systemd[1]: Expecting device
> dev-disk-by\x2duuid-4b63b0ad\x2dccbb\x2d4372\x2db76c\x2dd4537a8d40b1.device...
>          Expecting device
> dev-disk-by\x2duuid-4b63b0ad\x2dccb...d40b1.device...
> systemd[1]: Starting Timers.
> [  OK  ] Reached target Timers.
> systemd[1]: Reached target Timers.
> systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
> systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
> systemd[1]: Starting Paths.
> [  OK  ] Reached target Paths.
> systemd[1]: Reached target Paths.
> systemd[1]: Starting -.slice.
> [  OK  ] Created slice -.slice.
> systemd[1]: Created slice -.slice.
> systemd[1]: Starting udev Kernel Socket.
> [  OK  ] Listening on udev Kernel Socket.
> systemd[1]: Listening on udev Kernel Socket.
> systemd[1]: Starting udev Control Socket.
> [  OK  ] Listening on udev Control Socket.
> systemd[1]: Listening on udev Control Socket.
> systemd[1]: Starting Journal Socket.
> [  OK  ] Listening on Journal Socket.
> systemd[1]: Listening on Journal Socket.
> systemd[1]: Starting Sockets.
> [  OK  ] Reached target Sockets.
> systemd[1]: Reached target Sockets.
> systemd[1]: Starting System Slice.
> [  OK  ] Created slice System Slice.
> systemd[1]: Created slice System Slice.
> systemd[1]: Starting system-systemd\x2dfsck.slice.
> [  OK  ] Created slice system-systemd\x2dfsck.slice.
> systemd[1]: Created slice system-systemd\x2dfsck.slice.
> systemd[1]: Starting dracut cmdline hook...
>          Starting dracut cmdline hook...
> systemd[1]: Starting Create list of required static device nodes for the
> current kernel...
>          Starting Create list of required static device nodes...rrent
> kernel...
> systemd[1]: Starting Load Kernel Modules...
>          Starting Load Kernel Modules...
> systemd[1]: Starting Journal Service...
> SCSI subsystem initialized
>          Starting Journal Service...
> systemd[1]: Starting Slices.
> [  OK  ] Reached target Slices.
> systemd[1]: Reached target Slices.
> systemd[1]: Starting Swap.
> [  OK  ] Reached target Swap.
> systemd[1]: Reached target Swap.
> systemd[1]: Starting Local File Systems.
> [  OK  ] Reached target Local File Systems.
> systemd[1]: Reached target Local File Systems.
> [  OK  ] Started Journal Service.
> systemd[1]: Started Journal Service.
> [  OK  ] Started dracut cmdline hook.
> [  OK  ] Started Create list of required static device nodes ...current
> kernel.
> [  OK  ] Started Load Kernel Modules.
>          Starting Apply Kernel Variables...
>          Starting Create static device nodes in /dev...
> [  OK  ] Started Apply Kernel Variables.
> [  OK  ] Started Create static device nodes in /dev.
>          Starting udev Kernel Device Manager...
> [  OK  ] Started udev Kernel Device Manager.
>          Starting dracut pre-trigger hook...
> [  OK  ] Started dracut pre-trigger hook.
>          Starting udev Coldplug all Devices...
> [  OK  ] Started udev Coldplug all Devices.
>          Starting dracut initqueue hook...
> [  OK  ] Reached target System Initialization.
> [  OK  ] Reached target Basic System.
> usbcore: registered new interface driver usbfs
> usbcore: registered new interface driver hub
> usbcore: registered new device driver usb
> ipr: IBM Power RAID SCSI Device Driver version: 2.6.0 (November 16, 2012)
> ipr 0001:d0:01.0: Found IOA with IRQ: 325
> ipr 0001:d0:01.0: Cannot enable MSI.
> ipr 0001:d0:01.0: Starting IOA initialization sequence.
> scsi host0: IBM 0 Storage Adapter
> ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
> ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
> ehci-pci: EHCI PCI platform driver
> ipr 0001:d0:01.0: Adapter firmware version: 0510006D
> ehci-pci 0002:cc:01.2: EHCI Host Controller
> ehci-pci 0002:cc:01.2: new USB bus registered, assigned bus number 1
> ehci-pci 0002:cc:01.2: irq 276, io mem 0x400f8002000
> pata_pdc2027x 0001:cc:01.0: enabling device (0002 -> 0003)
> ipr 0001:d0:01.0: IOA initialized.
> ehci-pci 0002:cc:01.2: USB 2.0 started, EHCI 1.00
> usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
> usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> usb usb1: Product: EHCI Host Controller
> usb usb1: Manufacturer: Linux 3.19.0-2-default ehci_hcd
> usb usb1: SerialNumber: 0002:cc:01.2
> hub 1-0:1.0: USB hub found
> hub 1-0:1.0: 5 ports detected
> ohci-pci: OHCI PCI platform driver
> ohci-pci 0002:cc:01.0: OHCI PCI host controller
> ohci-pci 0002:cc:01.0: new USB bus registered, assigned bus number 2
> ohci-pci 0002:cc:01.0: irq 276, io mem 0x400f8001000
> pata_pdc2027x 0001:cc:01.0: PLL input clock 32754 kHz
> scsi host1: pata_pdc2027x
> scsi host2: pata_pdc2027x
> ata1: PATA max UDMA/133 mmio m16384@0x400b8000000 cmd 0x400b80017c0 irq 324
> ata2: PATA max UDMA/133 mmio m16384@0x400b8000000 cmd 0x400b80015c0 irq 324
> scsi 0:255:255:255: No Device         IBM      573E001          0150 PQ:
> 0 ANSI: 0
> scsi 0:255:255:255: Attached scsi generic sg0 type 31
> scsi 0:0:15:0: Enclosure         IBM      VSBPD4E1  U4SCSI 1203 PQ: 0
> ANSI: 2
> scsi 0:0:15:0: Attached scsi generic sg1 type 13
> scsi 0:0:8:0: Direct-Access     IBM   H0 HUS103073FL3800  RPQR PQ: 0 ANSI: 4
> scsi 0:0:8:0: Attached scsi generic sg2 type 0
> usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
> usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> usb usb2: Product: OHCI PCI host controller
> usb usb2: Manufacturer: Linux 3.19.0-2-default ohci_hcd
> usb usb2: SerialNumber: 0002:cc:01.0
> hub 2-0:1.0: USB hub found
> hub 2-0:1.0: 3 ports detected
> sd 0:0:8:0: [sda] 143374000 512-byte logical blocks: (73.4 GB/68.3 GiB)
> ohci-pci 0002:cc:01.1: OHCI PCI host controller
> ohci-pci 0002:cc:01.1: new USB bus registered, assigned bus number 3
> ohci-pci 0002:cc:01.1: irq 276, io mem 0x400f8000000
> sd 0:0:8:0: [sda] Write Protect is off
> sd 0:0:8:0: [sda] Write cache: disabled, read cache: enabled, supports
> DPO and FUA
> usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
> usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> usb usb3: Product: OHCI PCI host controller
> usb usb3: Manufacturer: Linux 3.19.0-2-default ohci_hcd
> usb usb3: SerialNumber: 0002:cc:01.1
> hub 3-0:1.0: USB hub found
> hub 3-0:1.0: 2 ports detected
>  sda: sda1 sda2 < sda5 sda6 sda7 >
> ata1.00: ATAPI: IBM     DROM0020541, P633, max UDMA/66
> sd 0:0:8:0: [sda] Attached SCSI disk
> ata1.00: configured for UDMA/66
> scsi 1:0:0:0: CD-ROM            IBM      DROM0020541      P633 PQ: 0 ANSI: 2
> scsi 1:0:0:0: Attached scsi generic sg3 type 5
> sr 1:0:0:0: [sr0] scsi3-mmc drive: 24x/24x cd/rw xa/form2 cdda tray
> cdrom: Uniform CD-ROM driver Revision: 3.20
> raid6: int64x1   2057 MB/s
> raid6: int64x2   2881 MB/s
> raid6: int64x4   3324 MB/s
> raid6: int64x8   1538 MB/s
> raid6: using algorithm int64x4 (3324 MB/s)
> raid6: using intx1 recovery algorithm
> xor: measuring software checksum speed
>    8regs     :  5766.400 MB/sec
>    8regs_prefetch:  5568.000 MB/sec
>    32regs    :  6048.000 MB/sec
>    32regs_prefetch:  5920.000 MB/sec
> xor: using function: 32regs (6048.000 MB/sec)
> Btrfs loaded, assert=on
> BTRFS: device fsid b7055861-eae1-4406-b13b-63bc6d7c27b2 devid 1 transid
> 1987 /dev/sda7
> BTRFS: device fsid 4b63b0ad-ccbb-4372-b76c-d4537a8d40b1 devid 1 transid
> 52 /dev/sda6
> [  OK  ] Found device HUS103073FL3800.
> [  OK  ] Started dracut initqueue hook.
>          Starting dracut pre-mount hook...
> PM: Starting manual resume from disk
> [  OK  ] Reached target Remote File Systems (Pre).
> [  OK  ] Reached target Remote File Systems.
> [  OK  ] Started dracut pre-mount hook.
>          Starting File System Check on
> /dev/disk/by-uuid/4b63...d4537a8d40b1...
> [  OK  ] Started File System Check on
> /dev/disk/by-uuid/4b63b...c-d4537a8d40b1.
>          Mounting /sysroot...
> BTRFS info (device sda6): disk space caching is enabled
> BTRFS: has skinny extents
> [  OK  ] Mounted /sysroot.
> [  OK  ] Reached target Initrd Root File System.
>          Starting Reload Configuration from the Real Root...
> [  OK  ] Started Reload Configuration from the Real Root.
> [  OK  ] Reached target Initrd File Systems.
> [  OK  ] Reached target Initrd Default Target.
> systemd-journald[148]: Received SIGTERM from PID 1 (systemd).
>
> Welcome to openSUSE 20150129 (Harlequin) (ppc64)!
>
> [  OK  ] Stopped Switch Root.
> [  OK  ] Stopped target Switch Root.
> [  OK  ] Stopped target Initrd File Systems.
>          Stopping File System Check on
> /dev/disk/by-uuid/4b63...d4537a8d40b1...
> [  OK  ] Stopped File System Check on
> /dev/disk/by-uuid/4b63b...c-d4537a8d40b1.
> [  OK  ] Removed slice system-systemd\x2dfsck.slice.
> [  OK  ] Stopped target Initrd Root File System.
> [  OK  ] Created slice User and Session Slice.
> [  OK  ] Created slice system-serial\x2dgetty.slice.
>          Expecting device dev-hvc0.device...
> [  OK  ] Created slice system-getty.slice.
> [  OK  ] Reached target Remote File Systems (Pre).
>          Starting Collect Read-Ahead Data...
> [  OK  ] Reached target Slices.
> [  OK  ] Listening on Delayed Shutdown Socket.
> [  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
>          Starting Rule generator for /dev/root symlink...
> [  OK  ] Stopped Trigger Flushing of Journal to Persistent Storage.
>          Stopping Journal Service...
> [  OK  ] Stopped Journal Service.
> [  OK  ] Reached target Paths.
>          Mounting Debug File System...
> [  OK  ] Set up automount Arbitrary Executable File Formats F...utomount
> Point.
>          Starting Create list of required static device nodes...rrent
> kernel...
>          Mounting POSIX Message Queue File System...
>          Mounting Huge Pages File System...
> [  OK  ] Listening on LVM2 metadata daemon socket.
> [  OK  ] Listening on Device-mapper event daemon FIFOs.
>          Starting Device-mapper event daemon...
> [  OK  ] Started Device-mapper event daemon.
>          Expecting device
> dev-disk-by\x2duuid-7421a83d\x2ddf9...2781d.device...
> [  OK  ] Listening on udev Kernel Socket.
> [  OK  ] Listening on udev Control Socket.
>          Expecting device
> dev-disk-by\x2duuid-4b63b0ad\x2dccb...d40b1.device...
> [  OK  ] Mounted Debug File System.
> [  OK  ] Mounted POSIX Message Queue File System.
> [  OK  ] Mounted Huge Pages File System.
> [  OK  ] Started Collect Read-Ahead Data.
> [  OK  ] Started Rule generator for /dev/root symlink.
> [  OK  ] Started Create list of required static device nodes ...current
> kernel.
>          Starting Create static device nodes in /dev...
>          Starting Load Kernel Modules...
>          Starting Setup Virtual Console...
>          Starting Remount Root and Kernel File Systems...
> BTRFS info (device sda6): disk space caching is enabled
> [  OK  ] Started Create static device nodes in /dev.
> [  OK  ] Started Load Kernel Modules.
> [  OK  ] Started Remount Root and Kernel File Systems.
>          Starting Load/Save Random Seed...
>          Starting Apply Kernel Variables...
>          Starting udev Kernel Device Manager...
> [  OK  ] Reached target Local File Systems (Pre).
> [  OK  ] Started Setup Virtual Console.
> [  OK  ] Started Load/Save Random Seed.
> [  OK  ] Started Apply Kernel Variables.
> [  OK  ] Started udev Kernel Device Manager.
>          Starting Entropy Daemon based on the HAVEGE algorithm...
> [  OK  ] Started Entropy Daemon based on the HAVEGE algorithm.
>          Starting Journal Service...
>          Starting udev Coldplug all Devices...
> [  OK  ] Started Journal Service.
> [  OK  ] Started udev Coldplug all Devices.
>          Starting udev Wait for Complete Device Initialization...
> rtc-generic rtc-generic: rtc core: registered rtc-generic as rtc0
> [  OK  ] Found device /dev/hvc0.
> e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
> e1000: Copyright (c) 1999-2006 Intel Corporation.
> e1000 0002:d0:01.0: enabling device (0000 -> 0002)
> NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd-udevd:423]
> Modules linked in: ses(+) windfarm_rm31(-) e1000(+) enclosure
> rtc_generic btrfs xor raid6_pq sr_mod cdrom sd_mod ohci_pci
> pata_pdc2027x ehci_pci ohci_hcd ehci_hcd ipr usbcore libata usb_common
> sg scsi_mod
> CPU: 0 PID: 423 Comm: systemd-udevd Not tainted 3.19.0-2-default #1
> task: c0000000046f4b10 ti: c00000006f10c000 task.ti: c00000006f10c000
> NIP: c00000000083a474 LR: c00000000083a4b8 CTR: c00000000083a3d0
> REGS: c00000006f10e880 TRAP: 0901   Not tainted  (3.19.0-2-default)
> MSR: 8000000000009032 <SF,EE,ME,IR,DR,RI>  CR: 24044424  XER: 00000000
> SOFTE: 1
> GPR00: d000000000ef7004 c00000006f10eb00 c00000000143e9b8 0000000000000001
> GPR04: c00000000419c470 0000000000000000 c00000007517bb60 000000000000000a
> GPR08: 0000000000000010 0000000080000001 0000000000000000 d000000000f06610
> GPR12: 0000000024042422 c000000007220000
> NIP [c00000000083a474] ._raw_spin_lock_irqsave+0xa4/0x110
> LR [c00000000083a4b8] ._raw_spin_lock_irqsave+0xe8/0x110
> Call Trace:
> [c00000006f10eb00] [c00000006f10eb90] 0xc00000006f10eb90 (unreliable)
> [c00000006f10eb90] [d000000000ef7004] .ipr_queuecommand+0x84/0x760 [ipr]
> [c00000006f10ec50] [d00000000081d9f0] .scsi_dispatch_cmd+0xe0/0x360
> [scsi_mod]
> [c00000006f10ece0] [d00000000081f61c] .scsi_queue_rq+0x77c/0x8e0 [scsi_mod]
> [c00000006f10edc0] [c000000000498370] .__blk_mq_run_hw_queue+0x2b0/0x4b0
> [c00000006f10eed0] [c0000000004993a8] .blk_mq_run_hw_queue+0xd8/0x100
> [c00000006f10ef50] [c00000000049a864] .blk_sq_make_request+0x2e4/0x410
> [c00000006f10f020] [c00000000048956c] .generic_make_request+0xcc/0x190
> [c00000006f10f0b0] [c0000000004896f8] .submit_bio+0xc8/0x1d0
> [c00000006f10f170] [d000000001b4a33c] .submit_stripe_bio+0x9c/0x110 [btrfs]
> [c00000006f10f220] [d000000001b50944] .btrfs_map_bio+0x2f4/0x590 [btrfs]
> [c00000006f10f360] [d000000001b1bdf4] .btrfs_submit_bio_hook+0xb4/0x290
> [btrfs]
> [c00000006f10f420] [d000000001b3b504] .submit_one_bio+0xc4/0x140 [btrfs]
> [c00000006f10f4c0] [d000000001b43d7c] .extent_readpages+0x16c/0x210 [btrfs]
> [c00000006f10f630] [d000000001b1c740] .btrfs_readpages+0x40/0x60 [btrfs]
> [c00000006f10f6c0] [c00000000023e60c] .__do_page_cache_readahead+0x1ac/0x2f0
> [c00000006f10f7e0] [c00000000023e8c4] .ondemand_readahead+0x174/0x2d0
> [c00000006f10f890] [c00000000022f418] .generic_file_read_iter+0x488/0x670
> [c00000006f10f9c0] [c0000000002c7378] .new_sync_read+0xa8/0x120
> [c00000006f10fae0] [c0000000002c8a58] .__vfs_read+0x68/0x120
> [c00000006f10fb70] [c0000000002c8bac] .vfs_read+0x9c/0x1b0
> [c00000006f10fc10] [c0000000002d070c] .kernel_read+0x5c/0x90
> [c00000006f10fcc0] [c0000000002d2824]
> .do_execveat_common.isra.20+0x544/0x7f0
> [c00000006f10fda0] [c0000000002d2e98] .SyS_execve+0x38/0x50
> [c00000006f10fe30] [c0000000000092fc] syscall_exit+0x0/0x7c
> Instruction dump:
> 81810008 eba1ffe8 ebc1fff0 7c0803a6 ebe1fff8 7d908120 4e800020 8bad02ba
> 4092004c 38600000 4b7d5cf5 60000000 <7c210b78> e92d0000 89290009 792affe3
>
> Regards,
> Andreas
>
> --
> SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
> Graham Norton; HRB 21284 (AG Nürnberg)
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Factory CD boot problem

Andreas Färber
Am 23.02.2015 um 00:22 schrieb Dinar Valeev:
> On Mon, Feb 23, 2015 at 12:01 AM, Andreas Färber <[hidden email]> wrote:
>> Am 22.02.2015 um 22:49 schrieb Dinar Valeev:
>>> The yast issue has been fixed, it just needs to find its way to
>>> Factory tree..
>>
>> So what exactly is it about?
> http://bugzilla.opensuse.org/show_bug.cgi?id=917833

OK. Neither that nor https://github.com/yast/yast-bootloader/pull/222
really says what effect exactly this error has though? grub2 bootloader
seemed installed okay.

What I notice is that my disk partitioning is wrong. I had two old btrfs
partitions; I overrode the default suggestion to take the whole disk and
then edited the proposal to not create a separate xfs home partition
(unchecked the option). What it did is it left the old home partition
sda7 alone and installed the root into sda6. Is that related or a
separate issue with yast2-partitioner?

When I chroot into my sda6 via the installer rescue system option and
run "yast bootloader", manually patched as in
https://github.com/yast/yast-bootloader/commit/cbbe4229bd12c78f94efe058a3f6d67cb1b6bd91,
then I get:

Error
Internal error. Please report a bug report with logs.
Details: undefined method `first' for nil:NilClass
Caller:  /usr/share/YaST2/modules/BootStorage.rb:422:in `detect_disks'

I assume that is because Factory is still at 3.1.120? That particular
file didn't change since then though:
https://github.com/yast/yast-bootloader/commits/master/src/modules/BootStorage.rb

Regards,
Andreas

--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton; HRB 21284 (AG Nürnberg)
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Factory CD boot problem

Dinar Valeev-2
On Mon, Feb 23, 2015 at 2:10 AM, Andreas Färber <[hidden email]> wrote:

> Am 23.02.2015 um 00:22 schrieb Dinar Valeev:
>> On Mon, Feb 23, 2015 at 12:01 AM, Andreas Färber <[hidden email]> wrote:
>>> Am 22.02.2015 um 22:49 schrieb Dinar Valeev:
>>>> The yast issue has been fixed, it just needs to find its way to
>>>> Factory tree..
>>>
>>> So what exactly is it about?
>> http://bugzilla.opensuse.org/show_bug.cgi?id=917833
>
> OK. Neither that nor https://github.com/yast/yast-bootloader/pull/222
> really says what effect exactly this error has though? grub2 bootloader
> seemed installed okay.
This error can be workarounded by grub2-install /dev/sda1

Assuming your PReP partition is the first one.

>
> What I notice is that my disk partitioning is wrong. I had two old btrfs
> partitions; I overrode the default suggestion to take the whole disk and
> then edited the proposal to not create a separate xfs home partition
> (unchecked the option). What it did is it left the old home partition
> sda7 alone and installed the root into sda6. Is that related or a
> separate issue with yast2-partitioner?
>
> When I chroot into my sda6 via the installer rescue system option and
> run "yast bootloader", manually patched as in
> https://github.com/yast/yast-bootloader/commit/cbbe4229bd12c78f94efe058a3f6d67cb1b6bd91,
> then I get:
>
> Error
> Internal error. Please report a bug report with logs.
> Details: undefined method `first' for nil:NilClass
> Caller:  /usr/share/YaST2/modules/BootStorage.rb:422:in `detect_disks'
>
> I assume that is because Factory is still at 3.1.120? That particular
> file didn't change since then though:
> https://github.com/yast/yast-bootloader/commits/master/src/modules/BootStorage.rb
I wouldn't trust yast here :)
>
> Regards,
> Andreas
>
> --
> SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
> Graham Norton; HRB 21284 (AG Nürnberg)
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Factory CD boot problem

Josef Reidinger-3
In reply to this post by Andreas Färber
On Mon, 23 Feb 2015 02:10:57 +0100
Andreas Färber <[hidden email]> wrote:

> Am 23.02.2015 um 00:22 schrieb Dinar Valeev:
> > On Mon, Feb 23, 2015 at 12:01 AM, Andreas Färber <[hidden email]>
> > wrote:
> >> Am 22.02.2015 um 22:49 schrieb Dinar Valeev:
> >>> The yast issue has been fixed, it just needs to find its way to
> >>> Factory tree..
> >>
> >> So what exactly is it about?
> > http://bugzilla.opensuse.org/show_bug.cgi?id=917833
>
> OK. Neither that nor https://github.com/yast/yast-bootloader/pull/222
> really says what effect exactly this error has though? grub2
> bootloader seemed installed okay.
>
> What I notice is that my disk partitioning is wrong. I had two old
> btrfs partitions; I overrode the default suggestion to take the whole
> disk and then edited the proposal to not create a separate xfs home
> partition (unchecked the option). What it did is it left the old home
> partition sda7 alone and installed the root into sda6. Is that
> related or a separate issue with yast2-partitioner?
>
> When I chroot into my sda6 via the installer rescue system option and
> run "yast bootloader", manually patched as in
>   ,
> then I get:
>
> Error
> Internal error. Please report a bug report with logs.
> Details: undefined method `first' for nil:NilClass
> Caller:  /usr/share/YaST2/modules/BootStorage.rb:422:in `detect_disks'
>
> I assume that is because Factory is still at 3.1.120? That particular
> file didn't change since then though:
> https://github.com/yast/yast-bootloader/commits/master/src/modules/BootStorage.rb
>

This looks like mount data is not properly populated in storage. It
returns empty mount point for "/". Maybe related that you start it from
rescue shell and storage is maybe not properly filled.
Do you try using installation with startshell=1 and placing patched
file in y2update?

josef

> Regards,
> Andreas
>

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Factory CD boot problem

Andreas Färber
Am 23.02.2015 um 19:48 schrieb Josef Reidinger:

> On Mon, 23 Feb 2015 02:10:57 +0100
> Andreas Färber <[hidden email]> wrote:
>
>> When I chroot into my sda6 via the installer rescue system option and
>> run "yast bootloader", manually patched as in
>>   ,
>> then I get:
>>
>> Error
>> Internal error. Please report a bug report with logs.
>> Details: undefined method `first' for nil:NilClass
>> Caller:  /usr/share/YaST2/modules/BootStorage.rb:422:in `detect_disks'
>>
>> I assume that is because Factory is still at 3.1.120? That particular
>> file didn't change since then though:
>> https://github.com/yast/yast-bootloader/commits/master/src/modules/BootStorage.rb
>
> This looks like mount data is not properly populated in storage. It
> returns empty mount point for "/". Maybe related that you start it from
> rescue shell and storage is maybe not properly filled.
> Do you try using installation with startshell=1 and placing patched
> file in y2update?

My fault. I use the NET installation CD and select "Rescue System" from
the grub menu and then go back, select "Start Installation" and from
there "Rescue System". I ran "yast bootloader" from an sda6 chroot but
forgot to bind /dev!

With /proc, /sys and /dev mounted and the file patched, it does work:
hvc0:Rescue:~ # mount /dev/sda6 /mnt
hvc0:Rescue:~ # mount /dev --bind /mnt/dev
hvc0:Rescue:~ # mount /sys --bind /mnt/sys
hvc0:Rescue:~ # mount /proc --bind /mnt/proc
hvc0:Rescue:~ # chroot /mnt/
Rescue:/ # yast bootloader

Not unexpected, my kernel boot problem remains, so I'll try downgrading.
Updating Tumbleweed did not help. With repartitioning I'll rather wait
for the yast-bootloader fixes to hit Factory.

Regards,
Andreas

--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton; HRB 21284 (AG Nürnberg)
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Factory CD boot problem

Andreas Färber
In reply to this post by Andreas Färber
Am 22.02.2015 um 22:46 schrieb Andreas Färber:

> Loading Linux 3.19.0-2-default ...
> Loading initial ramdisk ...
> OF stdout device is: /vdevice/vty@30000000
> Preparing to boot Linux version 3.19.0-2-default (geeko@buildhost) (gcc
> version 4.8.3 20141208 [gcc-4_8-branch revision 218481] (SUSE Linux) )
> #1 SMP Tue Feb 17 20:11:30 UTC 2015 (1133f88)
> Detected machine type: 0000000000000101
> Max number of cores passed to firmware: 1024 (NR_CPUS = 2048)
> Calling ibm,client-architecture-support... not implemented
> command line: BOOT_IMAGE=/boot/vmlinux-3.19.0-2-default
> root=UUID=4b63b0ad-ccbb-4372-b76c-d4537a8d40b1 quiet splash=silent
> memory layout at init:
>   memory_limit : 0000000000000000 (16 MB aligned)
>   alloc_bottom : 0000000005230000
>   alloc_top    : 0000000008000000
>   alloc_top_hi : 0000000077000000
>   rmo_top      : 0000000008000000
>   ram_top      : 0000000077000000
> found display   : /pci@800000020000002/display@1, opening... done
> instantiating rtas at 0x00000000076a0000... done
> prom_hold_cpus: skipped
> copying OF device tree...
> Building dt strings...
> Building dt structure...
> Device tree strings 0x0000000005240000 -> 0x000000000524135e
> Device tree struct  0x0000000005250000 -> 0x0000000005260000
>  -> smp_release_cpus()
> spinning_secondaries = 1
>  <- smp_release_cpus()
>  <- setup_system()
> ../drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
> pstore: decompression failed;returned -5
> BTRFS: has skinny extents
> NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd-udevd:412]
>
> Is that the consequence of the above error message, or is this "just" a
> kernel regression?

3.16.7-48.g267ab8f-default from Kernel:openSUSE-13.2 works fine.

Regards,
Andreas

--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton; HRB 21284 (AG Nürnberg)
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]