Re: [OpenIndiana-discuss] Kernel panic after pkg update

[Tony Brian Albers]

Hi Espen,

Are you using the xorg-video-intel driver? The T530 also comes with
nvidia GPU's

/tony


On Thu, 2020-08-20 at 15:10 +0200, Espen Martinsen wrote:
> For what it's worth, it works for me on a Lenovo T530 with Intel(R)
> Core(TM) i7-3630QM CPU @ 2.40GHz CPU Socket - U3E1
> 
> 
> SunOS esmpc 5.11 illumos-b018085dfc i86pc i386 i86pc illumos
> 
> pfexec svcadm disable lightdm
> 
> pfexec pkg update --be-name OIhipster-20200820
> 
> pfexec reboot
> 
> SunOS esmpc 5.11 illumos-76f19f5fdc i86pc i386 i86pc illumos
> 
> 
> pfexec svcadm enable -t lightdm
> 
> works!
> pfexec svcadm enable lightdm
> 
> pfexec reboot
> 
> works!
> 
> # pkg list |grep xorg
> developer/build/autoconf/xorg-macros 
> 1.19.2-2020.0.1.0  i--
> system/font/xorg/iso8859-1   
> 7.7-2020.0.1.0 i--
> system/font/xorg/xorg-core   
> 7.7-2020.0.1.0 i--
> x11/compatibility/links-xorg 
> 7.7-2020.0.1.1 i--
> x11/documentation/xorg-docs  
> 1.7.1-2020.0.1.0   i--
> x11/server/xorg  
> 1.19.7-2020.0.1.6  i--
> x11/server/xorg/driver/xorg-input-hotkey 
> 0.5.11-2020.0.1.3  i--
> x11/server/xorg/driver/xorg-input-keyboard   
> 1.9.0-2020.0.1.3   i--
> x11/server/xorg/driver/xorg-input-mouse  
> 1.9.3-2020.0.1.2   i--
> x11/server/xorg/driver/xorg-input-synaptics  
> 1.9.1-2020.0.1.2   i--
> x11/server/xorg/driver/xorg-input-vmmouse
> 13.1.0-2020.0.1.3  i--
> x11/server/xorg/driver/xorg-video
> 0.5.11-2020.0.1.1  i--
> x11/server/xorg/driver/xorg-video-ast
> 1.1.5-2020.0.1.3   i--
> x11/server/xorg/driver/xorg-video-ati
> 6.14.6-2020.0.1.4  i--
> x11/server/xorg/driver/xorg-video-cirrus 
> 1.5.3-2020.0.1.3   i--
> x11/server/xorg/driver/xorg-video-intel  
> 2.99.917-2020.0.1.10   i--
> x11/server/xorg/driver/xorg-video-mach64 
> 6.9.6-2020.0.1.2   i--
> x11/server/xorg/driver/xorg-video-mga
> 1.6.5-2020.0.1.3   i--
> x11/server/xorg/driver/xorg-video-nv 
> 2.1.21-2020.0.1.3  i--
> x11/server/xorg/driver/xorg-video-openchrome 
> 0.6.0-2020.0.1.4   i--
> x11/server/xorg/driver/xorg-video-r128   
> 6.10.2-2020.0.1.3  i--
> x11/server/xorg/driver/xorg-video-savage 
> 2.3.9-2020.0.1.3   i--
> x11/server/xorg/driver/xorg-video-trident
> 1.3.8-2020.0.1.3   i--
> x11/server/xorg/driver/xorg-video-vboxvideo  
> 1.0.1-2020.0.1.4   i--
> x11/server/xorg/driver/xorg-video-vesa   
> 2.4.0-2020.0.1.2   i--
> x11/server/xorg/driver/xorg-video-vmware 
> 13.3.0-2020.0.1.2  i--
> 
> 
>   
> 
> 
> 
> On 8/20/20 1:57 PM, Tony Brian Albers wrote:
> > I'm not sure whether I was meant to do something, am I?
> > 
> > Thanks
> > 
> > /tony
> > 
> > 
> > On Tue, 2020-08-18 at 10:45 +, Alexander Pyhalov via
> > openindiana-
> > discuss wrote:
> > > Can it be some ABI breakage? Can you confirm that issue
> > > exist  with
> > > latest osnet-incorporation and gfx-drm?
> > > 
> > > С уважением,
> > > Александр Пыхалов,
> > > программист отдела телекоммуникационной инфраструктуры
> > > управления информационно-коммуникационной инфраструктуры ЮФУ
> > > 
> > > 
> > > 
> > > От: Aurélien Larcher 
> > > Отправлено: 18 августа 2020 г. 11:29
> > > Кому: Discussion list for OpenIndiana
> > > Тема: Re: [OpenIndiana-discuss] Kernel panic after pkg update
> > > 
> > > The only outstanding things since May were switching gfx-drm to
> > > gcc-
> > > 7 
> > > and
> > > cherry-picking gcc-10 patches from upstream.
> > > 
> > > 
> > > On Tue, Aug 18, 2020 at 9:43 AM Tony Brian Albers 
> > > wrote:
> > > 
> > > > Here you go:
> > > > 
> > > > https://magpie.fubar.farm/index.php/s/zpgyaLBmyDqrqxk
> > > > 
> > > > /tony
> > > > 
> > > > 
> > > > On Tue, 2020-08-18 at 07:18 +, Alexander Pyhalov via
> > > > openindiana-
> > > > discuss wrote:
> > > > > Hi. Can you share stack trace or dump file?
> > > > > 
> > > > > С уважением,
> > > >

Re: [OpenIndiana-discuss] Kernel panic after pkg update

[Tony Brian Albers]

I'm not sure whether I was meant to do something, am I?

Thanks

/tony


On Tue, 2020-08-18 at 10:45 +, Alexander Pyhalov via openindiana-
discuss wrote:
> Can it be some ABI breakage? Can you confirm that issue exist  with
> latest osnet-incorporation and gfx-drm?
> 
> С уважением,
> Александр Пыхалов,
> программист отдела телекоммуникационной инфраструктуры
> управления информационно-коммуникационной инфраструктуры ЮФУ
> 
> 
> 
> От: Aurélien Larcher 
> Отправлено: 18 августа 2020 г. 11:29
> Кому: Discussion list for OpenIndiana
> Тема: Re: [OpenIndiana-discuss] Kernel panic after pkg update
> 
> The only outstanding things since May were switching gfx-drm to gcc-
> 7 
> and
> cherry-picking gcc-10 patches from upstream.
> 
> 
> On Tue, Aug 18, 2020 at 9:43 AM Tony Brian Albers  wrote:
> 
> > Here you go:
> > 
> > https://magpie.fubar.farm/index.php/s/zpgyaLBmyDqrqxk
> > 
> > /tony
> > 
> > 
> > On Tue, 2020-08-18 at 07:18 +, Alexander Pyhalov via
> > openindiana-
> > discuss wrote:
> > > Hi. Can you share stack trace or dump file?
> > > 
> > > С уважением,
> > > Александр Пыхалов,
> > > программист отдела телекоммуникационной инфраструктуры
> > > управления информационно-коммуникационной инфраструктуры ЮФУ
> > > 
> > > 
> > > ____
> > > От: Tony Brian Albers 
> > > Отправлено: 18 августа 2020 г. 10:14
> > > Кому: openindiana-discuss@openindiana.org
> > > Тема: Re: [OpenIndiana-discuss] Kernel panic after pkg update
> > > 
> > > FYI
> > > 
> > > I removed and reinstalled all xorg-related pkgs. I also ran pkg
> > > update
> > > again.
> > > 
> > > Now Xorg loads more driver modules and there are no errors in
> > > Xorg.log,
> > > but the system still panics.
> > > 
> > > Kernel illumos-0d54f452f4
> > > 
> > > The panic message in /var/adm/messages seems to be exactly the
> > > same.
> > > 
> > > /tony
> > > 
> > > 
> > > 
> > > 
> > > On Tue, 2020-08-18 at 06:50 +, Tony Brian Albers wrote:
> > > > Hi guys,
> > > > 
> > > > I'm trying to get my workstation to run the latest OI.
> > > > Installation
> > > > of
> > > > the desktop-image went fine, and after reboot everything is
> > > > still
> > > > ok.
> > > > 
> > > > Then I did a pkg update. Now running kernel illumos-06260e34c2
> > > > 
> > > > Now, everytime I try to start X, it panics and reboots. I've
> > > > disabled
> > > > the displaymanager(tried both gdm and xdm) and now I get to a
> > > > normal
> > > > login. But if I login and run startx it panics again.
> > > > 
> > > > 
> > > > The interesting thing I've discovered is that Xorg fails with:
> > > > 
> > > > snip---
> > > > [61.472] List of video drivers:
> > > > [61.512]nvidia
> > > > [61.513] (II) LoadModule: "nvidia"
> > > > [61.517] (II) Loading
> > > > /usr/X11/lib/modules/drivers/amd64/nvidia_drv.so
> > > > [61.531] (II) Module nvidia: vendor="NVIDIA Corporation"
> > > > [61.531]compiled for 4.0.2, module version = 1.0.0
> > > > [61.531]Module class: X.Org Video Driver
> > > > [61.584] No devices to configure.  Configuration failed.
> > > > [61.585] (EE) Server terminated with error (2). Closing log
> > > > file.
> > > > snip---
> > > > 
> > > > But I don't have a Nvidia card :( I'm using the Intel GPU on
> > > > the
> > > > CPU
> > > > itself. And it worked fine before the pkg update.
> > > > 
> > > > 
> > > > Pkgs installed relating to video drivers:
> > > > 
> > > > root@emu:~# pkg list |grep video
> > > > x11/server/xorg/driver/xorg-video 0.5.11-
> > > > 2020.0.1.1  i--
> > > > x11/server/xorg/driver/xorg-video-ast 1.1.5-
> > > > 2020.0.1.3   i--
> > > > x11/server/xorg/driver/xorg-video-ati 6.14.6-
> > > > 2020.0.1.4  i--
> > > > x11/server/xorg/driver/xorg-video-cirrus 

Re: [OpenIndiana-discuss] Kernel panic after pkg update

[Espen Martinsen]

For what it's worth, it works for me on a Lenovo T530 with Intel(R)
Core(TM) i7-3630QM CPU @ 2.40GHz CPU Socket - U3E1


SunOS esmpc 5.11 illumos-b018085dfc i86pc i386 i86pc illumos

pfexec svcadm disable lightdm

pfexec pkg update --be-name OIhipster-20200820

pfexec reboot

SunOS esmpc 5.11 illumos-76f19f5fdc i86pc i386 i86pc illumos


pfexec svcadm enable -t lightdm

works!
pfexec svcadm enable lightdm

pfexec reboot

works!

# pkg list |grep xorg
developer/build/autoconf/xorg-macros 
1.19.2-2020.0.1.0  i--
system/font/xorg/iso8859-1   
7.7-2020.0.1.0 i--
system/font/xorg/xorg-core   
7.7-2020.0.1.0 i--
x11/compatibility/links-xorg 
7.7-2020.0.1.1 i--
x11/documentation/xorg-docs  
1.7.1-2020.0.1.0   i--
x11/server/xorg  
1.19.7-2020.0.1.6  i--
x11/server/xorg/driver/xorg-input-hotkey 
0.5.11-2020.0.1.3  i--
x11/server/xorg/driver/xorg-input-keyboard   
1.9.0-2020.0.1.3   i--
x11/server/xorg/driver/xorg-input-mouse  
1.9.3-2020.0.1.2   i--
x11/server/xorg/driver/xorg-input-synaptics  
1.9.1-2020.0.1.2   i--
x11/server/xorg/driver/xorg-input-vmmouse
13.1.0-2020.0.1.3  i--
x11/server/xorg/driver/xorg-video
0.5.11-2020.0.1.1  i--
x11/server/xorg/driver/xorg-video-ast
1.1.5-2020.0.1.3   i--
x11/server/xorg/driver/xorg-video-ati
6.14.6-2020.0.1.4  i--
x11/server/xorg/driver/xorg-video-cirrus 
1.5.3-2020.0.1.3   i--
x11/server/xorg/driver/xorg-video-intel  
2.99.917-2020.0.1.10   i--
x11/server/xorg/driver/xorg-video-mach64 
6.9.6-2020.0.1.2   i--
x11/server/xorg/driver/xorg-video-mga
1.6.5-2020.0.1.3   i--
x11/server/xorg/driver/xorg-video-nv 
2.1.21-2020.0.1.3  i--
x11/server/xorg/driver/xorg-video-openchrome 
0.6.0-2020.0.1.4   i--
x11/server/xorg/driver/xorg-video-r128   
6.10.2-2020.0.1.3  i--
x11/server/xorg/driver/xorg-video-savage 
2.3.9-2020.0.1.3   i--
x11/server/xorg/driver/xorg-video-trident
1.3.8-2020.0.1.3   i--
x11/server/xorg/driver/xorg-video-vboxvideo  
1.0.1-2020.0.1.4   i--
x11/server/xorg/driver/xorg-video-vesa   
2.4.0-2020.0.1.2   i--
x11/server/xorg/driver/xorg-video-vmware 
13.3.0-2020.0.1.2  i--


  



On 8/20/20 1:57 PM, Tony Brian Albers wrote:
> I'm not sure whether I was meant to do something, am I?
>
> Thanks
>
> /tony
>
>
> On Tue, 2020-08-18 at 10:45 +, Alexander Pyhalov via openindiana-
> discuss wrote:
>> Can it be some ABI breakage? Can you confirm that issue exist  with
>> latest osnet-incorporation and gfx-drm?
>>
>> С уважением,
>> Александр Пыхалов,
>> программист отдела телекоммуникационной инфраструктуры
>> управления информационно-коммуникационной инфраструктуры ЮФУ
>>
>>
>> 
>> От: Aurélien Larcher 
>> Отправлено: 18 августа 2020 г. 11:29
>> Кому: Discussion list for OpenIndiana
>> Тема: Re: [OpenIndiana-discuss] Kernel panic after pkg update
>>
>> The only outstanding things since May were switching gfx-drm to gcc-
>> 7 
>> and
>> cherry-picking gcc-10 patches from upstream.
>>
>>
>> On Tue, Aug 18, 2020 at 9:43 AM Tony Brian Albers  wrote:
>>
>>> Here you go:
>>>
>>> https://magpie.fubar.farm/index.php/s/zpgyaLBmyDqrqxk
>>>
>>> /tony
>>>
>>>
>>> On Tue, 2020-08-18 at 07:18 +, Alexander Pyhalov via
>>> openindiana-
>>> discuss wrote:
>>>> Hi. Can you share stack trace or dump file?
>>>>
>>>> С уважением,
>>>> Александр Пыхалов,
>>>> программист отдела телекоммуникационной инфраструктуры
>>>> управления информационно-коммуникационной инфраструктуры ЮФУ
>>>>
>>>>
>>>> 
>>>> От: Tony Brian Albers 
>>>> Отправлено: 18 августа 2020 г. 10:14
>>>> Кому: openindiana-discuss@openindiana.org
>>>> Тема: Re: [OpenIndiana-discuss] Kernel panic after pkg update
>>>>
>>>> FYI
>>>>
>>>> I removed and reinstalled all xorg-related pkgs. I also ran pkg
>>>> update
>>>> again.
>>>>
>>>> Now Xorg loads more driver modules and there are no errors in
>>>> Xorg.log,
>>>> but the system still panics.
>>>>
>>>> Kernel illumos-0d54f452f4
>>>>
>

Re: [OpenIndiana-discuss] Kernel panic after pkg update

[Tony Brian Albers]

I'm not sure whether I was meant to do something, am I?

Thanks

/tony


On Tue, 2020-08-18 at 10:45 +, Alexander Pyhalov via openindiana-
discuss wrote:
> Can it be some ABI breakage? Can you confirm that issue exist  with
> latest osnet-incorporation and gfx-drm?
> 
> С уважением,
> Александр Пыхалов,
> программист отдела телекоммуникационной инфраструктуры
> управления информационно-коммуникационной инфраструктуры ЮФУ
> 
> 
> 
> От: Aurélien Larcher 
> Отправлено: 18 августа 2020 г. 11:29
> Кому: Discussion list for OpenIndiana
> Тема: Re: [OpenIndiana-discuss] Kernel panic after pkg update
> 
> The only outstanding things since May were switching gfx-drm to gcc-
> 7 
> and
> cherry-picking gcc-10 patches from upstream.
> 
> 
> On Tue, Aug 18, 2020 at 9:43 AM Tony Brian Albers  wrote:
> 
> > Here you go:
> > 
> > https://magpie.fubar.farm/index.php/s/zpgyaLBmyDqrqxk
> > 
> > /tony
> > 
> > 
> > On Tue, 2020-08-18 at 07:18 +, Alexander Pyhalov via
> > openindiana-
> > discuss wrote:
> > > Hi. Can you share stack trace or dump file?
> > > 
> > > С уважением,
> > > Александр Пыхалов,
> > > программист отдела телекоммуникационной инфраструктуры
> > > управления информационно-коммуникационной инфраструктуры ЮФУ
> > > 
> > > 
> > > ____
> > > От: Tony Brian Albers 
> > > Отправлено: 18 августа 2020 г. 10:14
> > > Кому: openindiana-discuss@openindiana.org
> > > Тема: Re: [OpenIndiana-discuss] Kernel panic after pkg update
> > > 
> > > FYI
> > > 
> > > I removed and reinstalled all xorg-related pkgs. I also ran pkg
> > > update
> > > again.
> > > 
> > > Now Xorg loads more driver modules and there are no errors in
> > > Xorg.log,
> > > but the system still panics.
> > > 
> > > Kernel illumos-0d54f452f4
> > > 
> > > The panic message in /var/adm/messages seems to be exactly the
> > > same.
> > > 
> > > /tony
> > > 
> > > 
> > > 
> > > 
> > > On Tue, 2020-08-18 at 06:50 +, Tony Brian Albers wrote:
> > > > Hi guys,
> > > > 
> > > > I'm trying to get my workstation to run the latest OI.
> > > > Installation
> > > > of
> > > > the desktop-image went fine, and after reboot everything is
> > > > still
> > > > ok.
> > > > 
> > > > Then I did a pkg update. Now running kernel illumos-06260e34c2
> > > > 
> > > > Now, everytime I try to start X, it panics and reboots. I've
> > > > disabled
> > > > the displaymanager(tried both gdm and xdm) and now I get to a
> > > > normal
> > > > login. But if I login and run startx it panics again.
> > > > 
> > > > 
> > > > The interesting thing I've discovered is that Xorg fails with:
> > > > 
> > > > snip---
> > > > [61.472] List of video drivers:
> > > > [61.512]nvidia
> > > > [61.513] (II) LoadModule: "nvidia"
> > > > [61.517] (II) Loading
> > > > /usr/X11/lib/modules/drivers/amd64/nvidia_drv.so
> > > > [61.531] (II) Module nvidia: vendor="NVIDIA Corporation"
> > > > [61.531]compiled for 4.0.2, module version = 1.0.0
> > > > [61.531]Module class: X.Org Video Driver
> > > > [61.584] No devices to configure.  Configuration failed.
> > > > [61.585] (EE) Server terminated with error (2). Closing log
> > > > file.
> > > > snip---
> > > > 
> > > > But I don't have a Nvidia card :( I'm using the Intel GPU on
> > > > the
> > > > CPU
> > > > itself. And it worked fine before the pkg update.
> > > > 
> > > > 
> > > > Pkgs installed relating to video drivers:
> > > > 
> > > > root@emu:~# pkg list |grep video
> > > > x11/server/xorg/driver/xorg-video 0.5.11-
> > > > 2020.0.1.1  i--
> > > > x11/server/xorg/driver/xorg-video-ast 1.1.5-
> > > > 2020.0.1.3   i--
> > > > x11/server/xorg/driver/xorg-video-ati 6.14.6-
> > > > 2020.0.1.4  i--
> > > > x11/server/xorg/driver/xorg-video-cirrus 

Re: [OpenIndiana-discuss] Kernel panic after pkg update

[Judah Richardson]

Same problem here. Ran a # pkg update -v -r on Sunday and PC (Core i5 2nd
Gen, iGPU) has been bootlooping since.

On Tue, Aug 18, 2020 at 5:45 AM Alexander Pyhalov via openindiana-discuss <
openindiana-discuss@openindiana.org> wrote:

> Can it be some ABI breakage? Can you confirm that issue exist  with latest
> osnet-incorporation and gfx-drm?
>
> С уважением,
> Александр Пыхалов,
> программист отдела телекоммуникационной инфраструктуры
> управления информационно-коммуникационной инфраструктуры ЮФУ
>
>
> 
> От: Aurélien Larcher 
> Отправлено: 18 августа 2020 г. 11:29
> Кому: Discussion list for OpenIndiana
> Тема: Re: [OpenIndiana-discuss] Kernel panic after pkg update
>
> The only outstanding things since May were switching gfx-drm to gcc-7 and
> cherry-picking gcc-10 patches from upstream.
>
>
> On Tue, Aug 18, 2020 at 9:43 AM Tony Brian Albers  wrote:
>
> > Here you go:
> >
> > https://magpie.fubar.farm/index.php/s/zpgyaLBmyDqrqxk
> >
> > /tony
> >
> >
> > On Tue, 2020-08-18 at 07:18 +, Alexander Pyhalov via openindiana-
> > discuss wrote:
> > > Hi. Can you share stack trace or dump file?
> > >
> > > С уважением,
> > > Александр Пыхалов,
> > > программист отдела телекоммуникационной инфраструктуры
> > > управления информационно-коммуникационной инфраструктуры ЮФУ
> > >
> > >
> > > ____
> > > От: Tony Brian Albers 
> > > Отправлено: 18 августа 2020 г. 10:14
> > > Кому: openindiana-discuss@openindiana.org
> > > Тема: Re: [OpenIndiana-discuss] Kernel panic after pkg update
> > >
> > > FYI
> > >
> > > I removed and reinstalled all xorg-related pkgs. I also ran pkg
> > > update
> > > again.
> > >
> > > Now Xorg loads more driver modules and there are no errors in
> > > Xorg.log,
> > > but the system still panics.
> > >
> > > Kernel illumos-0d54f452f4
> > >
> > > The panic message in /var/adm/messages seems to be exactly the same.
> > >
> > > /tony
> > >
> > >
> > >
> > >
> > > On Tue, 2020-08-18 at 06:50 +, Tony Brian Albers wrote:
> > > > Hi guys,
> > > >
> > > > I'm trying to get my workstation to run the latest OI. Installation
> > > > of
> > > > the desktop-image went fine, and after reboot everything is still
> > > > ok.
> > > >
> > > > Then I did a pkg update. Now running kernel illumos-06260e34c2
> > > >
> > > > Now, everytime I try to start X, it panics and reboots. I've
> > > > disabled
> > > > the displaymanager(tried both gdm and xdm) and now I get to a
> > > > normal
> > > > login. But if I login and run startx it panics again.
> > > >
> > > >
> > > > The interesting thing I've discovered is that Xorg fails with:
> > > >
> > > > snip---
> > > > [61.472] List of video drivers:
> > > > [61.512]nvidia
> > > > [61.513] (II) LoadModule: "nvidia"
> > > > [61.517] (II) Loading
> > > > /usr/X11/lib/modules/drivers/amd64/nvidia_drv.so
> > > > [61.531] (II) Module nvidia: vendor="NVIDIA Corporation"
> > > > [61.531]compiled for 4.0.2, module version = 1.0.0
> > > > [61.531]Module class: X.Org Video Driver
> > > > [61.584] No devices to configure.  Configuration failed.
> > > > [61.585] (EE) Server terminated with error (2). Closing log
> > > > file.
> > > > snip---
> > > >
> > > > But I don't have a Nvidia card :( I'm using the Intel GPU on the
> > > > CPU
> > > > itself. And it worked fine before the pkg update.
> > > >
> > > >
> > > > Pkgs installed relating to video drivers:
> > > >
> > > > root@emu:~# pkg list |grep video
> > > > x11/server/xorg/driver/xorg-video 0.5.11-
> > > > 2020.0.1.1  i--
> > > > x11/server/xorg/driver/xorg-video-ast 1.1.5-
> > > > 2020.0.1.3   i--
> > > > x11/server/xorg/driver/xorg-video-ati 6.14.6-
> > > > 2020.0.1.4  i--
> > > > x11/server/xorg/driver/xorg-video-cirrus  1.5.3-
> > > > 2020.0.1.3

Re: [OpenIndiana-discuss] Kernel panic after pkg update

[Alexander Pyhalov via openindiana-discuss]

Can it be some ABI breakage? Can you confirm that issue exist  with latest 
osnet-incorporation and gfx-drm?

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Aurélien Larcher 
Отправлено: 18 августа 2020 г. 11:29
Кому: Discussion list for OpenIndiana
Тема: Re: [OpenIndiana-discuss] Kernel panic after pkg update

The only outstanding things since May were switching gfx-drm to gcc-7 and
cherry-picking gcc-10 patches from upstream.


On Tue, Aug 18, 2020 at 9:43 AM Tony Brian Albers  wrote:

> Here you go:
>
> https://magpie.fubar.farm/index.php/s/zpgyaLBmyDqrqxk
>
> /tony
>
>
> On Tue, 2020-08-18 at 07:18 +, Alexander Pyhalov via openindiana-
> discuss wrote:
> > Hi. Can you share stack trace or dump file?
> >
> > С уважением,
> > Александр Пыхалов,
> > программист отдела телекоммуникационной инфраструктуры
> > управления информационно-коммуникационной инфраструктуры ЮФУ
> >
> >
> > 
> > От: Tony Brian Albers 
> > Отправлено: 18 августа 2020 г. 10:14
> > Кому: openindiana-discuss@openindiana.org
> > Тема: Re: [OpenIndiana-discuss] Kernel panic after pkg update
> >
> > FYI
> >
> > I removed and reinstalled all xorg-related pkgs. I also ran pkg
> > update
> > again.
> >
> > Now Xorg loads more driver modules and there are no errors in
> > Xorg.log,
> > but the system still panics.
> >
> > Kernel illumos-0d54f452f4
> >
> > The panic message in /var/adm/messages seems to be exactly the same.
> >
> > /tony
> >
> >
> >
> >
> > On Tue, 2020-08-18 at 06:50 +, Tony Brian Albers wrote:
> > > Hi guys,
> > >
> > > I'm trying to get my workstation to run the latest OI. Installation
> > > of
> > > the desktop-image went fine, and after reboot everything is still
> > > ok.
> > >
> > > Then I did a pkg update. Now running kernel illumos-06260e34c2
> > >
> > > Now, everytime I try to start X, it panics and reboots. I've
> > > disabled
> > > the displaymanager(tried both gdm and xdm) and now I get to a
> > > normal
> > > login. But if I login and run startx it panics again.
> > >
> > >
> > > The interesting thing I've discovered is that Xorg fails with:
> > >
> > > snip---
> > > [61.472] List of video drivers:
> > > [61.512]nvidia
> > > [61.513] (II) LoadModule: "nvidia"
> > > [61.517] (II) Loading
> > > /usr/X11/lib/modules/drivers/amd64/nvidia_drv.so
> > > [61.531] (II) Module nvidia: vendor="NVIDIA Corporation"
> > > [61.531]compiled for 4.0.2, module version = 1.0.0
> > > [61.531]Module class: X.Org Video Driver
> > > [61.584] No devices to configure.  Configuration failed.
> > > [61.585] (EE) Server terminated with error (2). Closing log
> > > file.
> > > snip---
> > >
> > > But I don't have a Nvidia card :( I'm using the Intel GPU on the
> > > CPU
> > > itself. And it worked fine before the pkg update.
> > >
> > >
> > > Pkgs installed relating to video drivers:
> > >
> > > root@emu:~# pkg list |grep video
> > > x11/server/xorg/driver/xorg-video 0.5.11-
> > > 2020.0.1.1  i--
> > > x11/server/xorg/driver/xorg-video-ast 1.1.5-
> > > 2020.0.1.3   i--
> > > x11/server/xorg/driver/xorg-video-ati 6.14.6-
> > > 2020.0.1.4  i--
> > > x11/server/xorg/driver/xorg-video-cirrus  1.5.3-
> > > 2020.0.1.3   i--
> > > x11/server/xorg/driver/xorg-video-intel   2.99.917-
> > > 2020.0.1.10   i--
> > > x11/server/xorg/driver/xorg-video-mach64  6.9.6-
> > > 2020.0.1.2   i--
> > > x11/server/xorg/driver/xorg-video-mga 1.6.5-
> > > 2020.0.1.3   i--
> > > x11/server/xorg/driver/xorg-video-nv  2.1.21-
> > > 2020.0.1.3  i--
> > > x11/server/xorg/driver/xorg-video-openchrome  0.6.0-
> > > 2020.0.1.4   i--
> > > x11/server/xorg/driver/xorg-video-r1286.10.2-
> > > 2020.0.1.3  i--
> > > x11/server/xorg/driver/xorg-video-savage  2.3.9-
> > > 2020.0.1.3 

Re: [OpenIndiana-discuss] Kernel panic after pkg update

[Aurélien Larcher]

The only outstanding things since May were switching gfx-drm to gcc-7 and
cherry-picking gcc-10 patches from upstream.


On Tue, Aug 18, 2020 at 9:43 AM Tony Brian Albers  wrote:

> Here you go:
>
> https://magpie.fubar.farm/index.php/s/zpgyaLBmyDqrqxk
>
> /tony
>
>
> On Tue, 2020-08-18 at 07:18 +, Alexander Pyhalov via openindiana-
> discuss wrote:
> > Hi. Can you share stack trace or dump file?
> >
> > С уважением,
> > Александр Пыхалов,
> > программист отдела телекоммуникационной инфраструктуры
> > управления информационно-коммуникационной инфраструктуры ЮФУ
> >
> >
> > 
> > От: Tony Brian Albers 
> > Отправлено: 18 августа 2020 г. 10:14
> > Кому: openindiana-discuss@openindiana.org
> > Тема: Re: [OpenIndiana-discuss] Kernel panic after pkg update
> >
> > FYI
> >
> > I removed and reinstalled all xorg-related pkgs. I also ran pkg
> > update
> > again.
> >
> > Now Xorg loads more driver modules and there are no errors in
> > Xorg.log,
> > but the system still panics.
> >
> > Kernel illumos-0d54f452f4
> >
> > The panic message in /var/adm/messages seems to be exactly the same.
> >
> > /tony
> >
> >
> >
> >
> > On Tue, 2020-08-18 at 06:50 +, Tony Brian Albers wrote:
> > > Hi guys,
> > >
> > > I'm trying to get my workstation to run the latest OI. Installation
> > > of
> > > the desktop-image went fine, and after reboot everything is still
> > > ok.
> > >
> > > Then I did a pkg update. Now running kernel illumos-06260e34c2
> > >
> > > Now, everytime I try to start X, it panics and reboots. I've
> > > disabled
> > > the displaymanager(tried both gdm and xdm) and now I get to a
> > > normal
> > > login. But if I login and run startx it panics again.
> > >
> > >
> > > The interesting thing I've discovered is that Xorg fails with:
> > >
> > > snip---
> > > [61.472] List of video drivers:
> > > [61.512]nvidia
> > > [61.513] (II) LoadModule: "nvidia"
> > > [61.517] (II) Loading
> > > /usr/X11/lib/modules/drivers/amd64/nvidia_drv.so
> > > [61.531] (II) Module nvidia: vendor="NVIDIA Corporation"
> > > [61.531]compiled for 4.0.2, module version = 1.0.0
> > > [61.531]Module class: X.Org Video Driver
> > > [61.584] No devices to configure.  Configuration failed.
> > > [61.585] (EE) Server terminated with error (2). Closing log
> > > file.
> > > snip---
> > >
> > > But I don't have a Nvidia card :( I'm using the Intel GPU on the
> > > CPU
> > > itself. And it worked fine before the pkg update.
> > >
> > >
> > > Pkgs installed relating to video drivers:
> > >
> > > root@emu:~# pkg list |grep video
> > > x11/server/xorg/driver/xorg-video 0.5.11-
> > > 2020.0.1.1  i--
> > > x11/server/xorg/driver/xorg-video-ast 1.1.5-
> > > 2020.0.1.3   i--
> > > x11/server/xorg/driver/xorg-video-ati 6.14.6-
> > > 2020.0.1.4  i--
> > > x11/server/xorg/driver/xorg-video-cirrus  1.5.3-
> > > 2020.0.1.3   i--
> > > x11/server/xorg/driver/xorg-video-intel   2.99.917-
> > > 2020.0.1.10   i--
> > > x11/server/xorg/driver/xorg-video-mach64  6.9.6-
> > > 2020.0.1.2   i--
> > > x11/server/xorg/driver/xorg-video-mga 1.6.5-
> > > 2020.0.1.3   i--
> > > x11/server/xorg/driver/xorg-video-nv  2.1.21-
> > > 2020.0.1.3  i--
> > > x11/server/xorg/driver/xorg-video-openchrome  0.6.0-
> > > 2020.0.1.4   i--
> > > x11/server/xorg/driver/xorg-video-r1286.10.2-
> > > 2020.0.1.3  i--
> > > x11/server/xorg/driver/xorg-video-savage  2.3.9-
> > > 2020.0.1.3   i--
> > > x11/server/xorg/driver/xorg-video-trident 1.3.8-
> > > 2020.0.1.3   i--
> > > x11/server/xorg/driver/xorg-video-vboxvideo   1.0.1-
> > > 2020.0.1.4   i--
> > > x11/server/xorg/driver/xorg-video-vesa2.4.0-
> > > 2020.0.1.2   i--
> > > x11/server/xorg/driver/xorg-video-vmware  13.3.0-
> > > 2020.0.1.2  i--
> > 

Re: [OpenIndiana-discuss] Kernel panic after pkg update

[Tony Brian Albers]

Here you go:

https://magpie.fubar.farm/index.php/s/zpgyaLBmyDqrqxk

/tony


On Tue, 2020-08-18 at 07:18 +, Alexander Pyhalov via openindiana-
discuss wrote:
> Hi. Can you share stack trace or dump file?
> 
> С уважением,
> Александр Пыхалов,
> программист отдела телекоммуникационной инфраструктуры
> управления информационно-коммуникационной инфраструктуры ЮФУ
> 
> 
> 
> От: Tony Brian Albers 
> Отправлено: 18 августа 2020 г. 10:14
> Кому: openindiana-discuss@openindiana.org
> Тема: Re: [OpenIndiana-discuss] Kernel panic after pkg update
> 
> FYI
> 
> I removed and reinstalled all xorg-related pkgs. I also ran pkg
> update
> again.
> 
> Now Xorg loads more driver modules and there are no errors in
> Xorg.log,
> but the system still panics.
> 
> Kernel illumos-0d54f452f4
> 
> The panic message in /var/adm/messages seems to be exactly the same.
> 
> /tony
> 
> 
> 
> 
> On Tue, 2020-08-18 at 06:50 +, Tony Brian Albers wrote:
> > Hi guys,
> > 
> > I'm trying to get my workstation to run the latest OI. Installation
> > of
> > the desktop-image went fine, and after reboot everything is still
> > ok.
> > 
> > Then I did a pkg update. Now running kernel illumos-06260e34c2
> > 
> > Now, everytime I try to start X, it panics and reboots. I've
> > disabled
> > the displaymanager(tried both gdm and xdm) and now I get to a
> > normal
> > login. But if I login and run startx it panics again.
> > 
> > 
> > The interesting thing I've discovered is that Xorg fails with:
> > 
> > snip---
> > [61.472] List of video drivers:
> > [61.512]nvidia
> > [61.513] (II) LoadModule: "nvidia"
> > [61.517] (II) Loading
> > /usr/X11/lib/modules/drivers/amd64/nvidia_drv.so
> > [61.531] (II) Module nvidia: vendor="NVIDIA Corporation"
> > [61.531]compiled for 4.0.2, module version = 1.0.0
> > [61.531]Module class: X.Org Video Driver
> > [61.584] No devices to configure.  Configuration failed.
> > [61.585] (EE) Server terminated with error (2). Closing log
> > file.
> > snip---
> > 
> > But I don't have a Nvidia card :( I'm using the Intel GPU on the
> > CPU
> > itself. And it worked fine before the pkg update.
> > 
> > 
> > Pkgs installed relating to video drivers:
> > 
> > root@emu:~# pkg list |grep video
> > x11/server/xorg/driver/xorg-video 0.5.11-
> > 2020.0.1.1  i--
> > x11/server/xorg/driver/xorg-video-ast 1.1.5-
> > 2020.0.1.3   i--
> > x11/server/xorg/driver/xorg-video-ati 6.14.6-
> > 2020.0.1.4  i--
> > x11/server/xorg/driver/xorg-video-cirrus  1.5.3-
> > 2020.0.1.3   i--
> > x11/server/xorg/driver/xorg-video-intel   2.99.917-
> > 2020.0.1.10   i--
> > x11/server/xorg/driver/xorg-video-mach64  6.9.6-
> > 2020.0.1.2   i--
> > x11/server/xorg/driver/xorg-video-mga 1.6.5-
> > 2020.0.1.3   i--
> > x11/server/xorg/driver/xorg-video-nv  2.1.21-
> > 2020.0.1.3  i--
> > x11/server/xorg/driver/xorg-video-openchrome  0.6.0-
> > 2020.0.1.4   i--
> > x11/server/xorg/driver/xorg-video-r1286.10.2-
> > 2020.0.1.3  i--
> > x11/server/xorg/driver/xorg-video-savage  2.3.9-
> > 2020.0.1.3   i--
> > x11/server/xorg/driver/xorg-video-trident 1.3.8-
> > 2020.0.1.3   i--
> > x11/server/xorg/driver/xorg-video-vboxvideo   1.0.1-
> > 2020.0.1.4   i--
> > x11/server/xorg/driver/xorg-video-vesa2.4.0-
> > 2020.0.1.2   i--
> > x11/server/xorg/driver/xorg-video-vmware  13.3.0-
> > 2020.0.1.2  i--
> > root@emu:~#
> > 
> > 
> > Here's what it says in /var/adm/messages:
> > 
> > snip---
> > Aug 17 21:15:43 emu unix: [ID 836849 kern.notice]
> > Aug 17 21:15:43 emu ^Mpanic[cpu1]/thread=fe2cedcf1080:
> > Aug 17 21:15:43 emu genunix: [ID 335743 kern.notice] BAD TRAP:
> > type=e
> > (#pf Page fault) rp=fe003e3d5710 addr=0 occurred in
> >  module "unix" due to a NULL pointer dereference
> > Aug 17 21:15:43 emu unix: [ID 10 kern.notice]
> > Aug 17 21:15:43 emu unix: [ID 839527 kern.notice] Xorg:
> > Aug 17 21:15:43 emu unix: [ID 753105 kern.notice] #pf Page fault
> 

Re: [OpenIndiana-discuss] Kernel panic after pkg update

[Tony Brian Albers]

Aye, let me get one and figure out where to put it for you.

/tony

On Tue, 2020-08-18 at 07:18 +, Alexander Pyhalov via openindiana-
discuss wrote:
> Hi. Can you share stack trace or dump file?
> 
> С уважением,
> Александр Пыхалов,
> программист отдела телекоммуникационной инфраструктуры
> управления информационно-коммуникационной инфраструктуры ЮФУ
> 
> 
> 
> От: Tony Brian Albers 
> Отправлено: 18 августа 2020 г. 10:14
> Кому: openindiana-discuss@openindiana.org
> Тема: Re: [OpenIndiana-discuss] Kernel panic after pkg update
> 
> FYI
> 
> I removed and reinstalled all xorg-related pkgs. I also ran pkg
> update
> again.
> 
> Now Xorg loads more driver modules and there are no errors in
> Xorg.log,
> but the system still panics.
> 
> Kernel illumos-0d54f452f4
> 
> The panic message in /var/adm/messages seems to be exactly the same.
> 
> /tony
> 
> 
> 
> 
> On Tue, 2020-08-18 at 06:50 +, Tony Brian Albers wrote:
> > Hi guys,
> > 
> > I'm trying to get my workstation to run the latest OI. Installation
> > of
> > the desktop-image went fine, and after reboot everything is still
> > ok.
> > 
> > Then I did a pkg update. Now running kernel illumos-06260e34c2
> > 
> > Now, everytime I try to start X, it panics and reboots. I've
> > disabled
> > the displaymanager(tried both gdm and xdm) and now I get to a
> > normal
> > login. But if I login and run startx it panics again.
> > 
> > 
> > The interesting thing I've discovered is that Xorg fails with:
> > 
> > snip---
> > [61.472] List of video drivers:
> > [61.512]nvidia
> > [61.513] (II) LoadModule: "nvidia"
> > [61.517] (II) Loading
> > /usr/X11/lib/modules/drivers/amd64/nvidia_drv.so
> > [61.531] (II) Module nvidia: vendor="NVIDIA Corporation"
> > [61.531]compiled for 4.0.2, module version = 1.0.0
> > [61.531]Module class: X.Org Video Driver
> > [61.584] No devices to configure.  Configuration failed.
> > [61.585] (EE) Server terminated with error (2). Closing log
> > file.
> > snip---
> > 
> > But I don't have a Nvidia card :( I'm using the Intel GPU on the
> > CPU
> > itself. And it worked fine before the pkg update.
> > 
> > 
> > Pkgs installed relating to video drivers:
> > 
> > root@emu:~# pkg list |grep video
> > x11/server/xorg/driver/xorg-video 0.5.11-
> > 2020.0.1.1  i--
> > x11/server/xorg/driver/xorg-video-ast 1.1.5-
> > 2020.0.1.3   i--
> > x11/server/xorg/driver/xorg-video-ati 6.14.6-
> > 2020.0.1.4  i--
> > x11/server/xorg/driver/xorg-video-cirrus  1.5.3-
> > 2020.0.1.3   i--
> > x11/server/xorg/driver/xorg-video-intel   2.99.917-
> > 2020.0.1.10   i--
> > x11/server/xorg/driver/xorg-video-mach64  6.9.6-
> > 2020.0.1.2   i--
> > x11/server/xorg/driver/xorg-video-mga 1.6.5-
> > 2020.0.1.3   i--
> > x11/server/xorg/driver/xorg-video-nv  2.1.21-
> > 2020.0.1.3  i--
> > x11/server/xorg/driver/xorg-video-openchrome  0.6.0-
> > 2020.0.1.4   i--
> > x11/server/xorg/driver/xorg-video-r1286.10.2-
> > 2020.0.1.3  i--
> > x11/server/xorg/driver/xorg-video-savage  2.3.9-
> > 2020.0.1.3   i--
> > x11/server/xorg/driver/xorg-video-trident 1.3.8-
> > 2020.0.1.3   i--
> > x11/server/xorg/driver/xorg-video-vboxvideo   1.0.1-
> > 2020.0.1.4   i--
> > x11/server/xorg/driver/xorg-video-vesa2.4.0-
> > 2020.0.1.2   i--
> > x11/server/xorg/driver/xorg-video-vmware  13.3.0-
> > 2020.0.1.2  i--
> > root@emu:~#
> > 
> > 
> > Here's what it says in /var/adm/messages:
> > 
> > snip---
> > Aug 17 21:15:43 emu unix: [ID 836849 kern.notice]
> > Aug 17 21:15:43 emu ^Mpanic[cpu1]/thread=fe2cedcf1080:
> > Aug 17 21:15:43 emu genunix: [ID 335743 kern.notice] BAD TRAP:
> > type=e
> > (#pf Page fault) rp=fe003e3d5710 addr=0 occurred in
> >  module "unix" due to a NULL pointer dereference
> > Aug 17 21:15:43 emu unix: [ID 10 kern.notice]
> > Aug 17 21:15:43 emu unix: [ID 839527 kern.notice] Xorg:
> > Aug 17 21:15:43 emu unix: [ID 753105 kern.notice] #pf Page fault
> 

Re: [OpenIndiana-discuss] Kernel panic after pkg update

[Alexander Pyhalov via openindiana-discuss]

Hi. Can you share stack trace or dump file?

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ



От: Tony Brian Albers 
Отправлено: 18 августа 2020 г. 10:14
Кому: openindiana-discuss@openindiana.org
Тема: Re: [OpenIndiana-discuss] Kernel panic after pkg update

FYI

I removed and reinstalled all xorg-related pkgs. I also ran pkg update
again.

Now Xorg loads more driver modules and there are no errors in Xorg.log,
but the system still panics.

Kernel illumos-0d54f452f4

The panic message in /var/adm/messages seems to be exactly the same.

/tony




On Tue, 2020-08-18 at 06:50 +, Tony Brian Albers wrote:
> Hi guys,
>
> I'm trying to get my workstation to run the latest OI. Installation
> of
> the desktop-image went fine, and after reboot everything is still ok.
>
> Then I did a pkg update. Now running kernel illumos-06260e34c2
>
> Now, everytime I try to start X, it panics and reboots. I've disabled
> the displaymanager(tried both gdm and xdm) and now I get to a normal
> login. But if I login and run startx it panics again.
>
>
> The interesting thing I've discovered is that Xorg fails with:
>
> snip---
> [61.472] List of video drivers:
> [61.512]nvidia
> [61.513] (II) LoadModule: "nvidia"
> [61.517] (II) Loading
> /usr/X11/lib/modules/drivers/amd64/nvidia_drv.so
> [61.531] (II) Module nvidia: vendor="NVIDIA Corporation"
> [61.531]compiled for 4.0.2, module version = 1.0.0
> [61.531]Module class: X.Org Video Driver
> [61.584] No devices to configure.  Configuration failed.
> [61.585] (EE) Server terminated with error (2). Closing log file.
> snip---
>
> But I don't have a Nvidia card :( I'm using the Intel GPU on the CPU
> itself. And it worked fine before the pkg update.
>
>
> Pkgs installed relating to video drivers:
>
> root@emu:~# pkg list |grep video
> x11/server/xorg/driver/xorg-video 0.5.11-
> 2020.0.1.1  i--
> x11/server/xorg/driver/xorg-video-ast 1.1.5-
> 2020.0.1.3   i--
> x11/server/xorg/driver/xorg-video-ati 6.14.6-
> 2020.0.1.4  i--
> x11/server/xorg/driver/xorg-video-cirrus  1.5.3-
> 2020.0.1.3   i--
> x11/server/xorg/driver/xorg-video-intel   2.99.917-
> 2020.0.1.10   i--
> x11/server/xorg/driver/xorg-video-mach64  6.9.6-
> 2020.0.1.2   i--
> x11/server/xorg/driver/xorg-video-mga 1.6.5-
> 2020.0.1.3   i--
> x11/server/xorg/driver/xorg-video-nv  2.1.21-
> 2020.0.1.3  i--
> x11/server/xorg/driver/xorg-video-openchrome  0.6.0-
> 2020.0.1.4   i--
> x11/server/xorg/driver/xorg-video-r1286.10.2-
> 2020.0.1.3  i--
> x11/server/xorg/driver/xorg-video-savage  2.3.9-
> 2020.0.1.3   i--
> x11/server/xorg/driver/xorg-video-trident 1.3.8-
> 2020.0.1.3   i--
> x11/server/xorg/driver/xorg-video-vboxvideo   1.0.1-
> 2020.0.1.4   i--
> x11/server/xorg/driver/xorg-video-vesa2.4.0-
> 2020.0.1.2   i--
> x11/server/xorg/driver/xorg-video-vmware  13.3.0-
> 2020.0.1.2  i--
> root@emu:~#
>
>
> Here's what it says in /var/adm/messages:
>
> snip---
> Aug 17 21:15:43 emu unix: [ID 836849 kern.notice]
> Aug 17 21:15:43 emu ^Mpanic[cpu1]/thread=fe2cedcf1080:
> Aug 17 21:15:43 emu genunix: [ID 335743 kern.notice] BAD TRAP: type=e
> (#pf Page fault) rp=fe003e3d5710 addr=0 occurred in
>  module "unix" due to a NULL pointer dereference
> Aug 17 21:15:43 emu unix: [ID 10 kern.notice]
> Aug 17 21:15:43 emu unix: [ID 839527 kern.notice] Xorg:
> Aug 17 21:15:43 emu unix: [ID 753105 kern.notice] #pf Page fault
> Aug 17 21:15:43 emu unix: [ID 532287 kern.notice] Bad kernel fault at
> addr=0x0
> Aug 17 21:15:43 emu unix: [ID 243837 kern.notice] pid=4770,
> pc=0xfb88151b, sp=0xfe003e3d5808, eflags=0x10246
> Aug 17 21:15:43 emu unix: [ID 619397 kern.notice] cr0:
> 80050033  cr4:
> 1626f8 xsr,pge,mce,pae,pse,de>
> Aug 17 21:15:43 emu unix: [ID 152204 kern.notice] cr2: 0
> Aug 17 21:15:43 emu unix: [ID 634440 kern.notice] cr3: 80aaa1000
> Aug 17 21:15:43 emu unix: [ID 625715 kern.notice] cr8: 0
> Aug 17 21:15:43 emu unix: [ID 10 kern.notice]
> Aug 17 21:15:43 emu unix: [ID 592667
> kern.notice]   rdi:0 rsi:0 rdx:
> fe2cedcf1080
> Aug 17 21:15:43 emu unix: [ID 592667
> kern.notice]   rcx:1c00

Re: [OpenIndiana-discuss] Kernel panic after pkg update

[Tony Brian Albers]

FYI 

I removed and reinstalled all xorg-related pkgs. I also ran pkg update
again.

Now Xorg loads more driver modules and there are no errors in Xorg.log,
but the system still panics.

Kernel illumos-0d54f452f4

The panic message in /var/adm/messages seems to be exactly the same.

/tony




On Tue, 2020-08-18 at 06:50 +, Tony Brian Albers wrote:
> Hi guys,
> 
> I'm trying to get my workstation to run the latest OI. Installation
> of
> the desktop-image went fine, and after reboot everything is still ok.
> 
> Then I did a pkg update. Now running kernel illumos-06260e34c2
> 
> Now, everytime I try to start X, it panics and reboots. I've disabled
> the displaymanager(tried both gdm and xdm) and now I get to a normal
> login. But if I login and run startx it panics again.
> 
> 
> The interesting thing I've discovered is that Xorg fails with:
> 
> snip---
> [61.472] List of video drivers:
> [61.512]nvidia
> [61.513] (II) LoadModule: "nvidia"
> [61.517] (II) Loading
> /usr/X11/lib/modules/drivers/amd64/nvidia_drv.so
> [61.531] (II) Module nvidia: vendor="NVIDIA Corporation"
> [61.531]compiled for 4.0.2, module version = 1.0.0
> [61.531]Module class: X.Org Video Driver
> [61.584] No devices to configure.  Configuration failed.
> [61.585] (EE) Server terminated with error (2). Closing log file.
> snip---
> 
> But I don't have a Nvidia card :( I'm using the Intel GPU on the CPU
> itself. And it worked fine before the pkg update.
> 
> 
> Pkgs installed relating to video drivers:
> 
> root@emu:~# pkg list |grep video
> x11/server/xorg/driver/xorg-video 0.5.11-
> 2020.0.1.1  i--
> x11/server/xorg/driver/xorg-video-ast 1.1.5-
> 2020.0.1.3   i--
> x11/server/xorg/driver/xorg-video-ati 6.14.6-
> 2020.0.1.4  i--
> x11/server/xorg/driver/xorg-video-cirrus  1.5.3-
> 2020.0.1.3   i--
> x11/server/xorg/driver/xorg-video-intel   2.99.917-
> 2020.0.1.10   i--
> x11/server/xorg/driver/xorg-video-mach64  6.9.6-
> 2020.0.1.2   i--
> x11/server/xorg/driver/xorg-video-mga 1.6.5-
> 2020.0.1.3   i--
> x11/server/xorg/driver/xorg-video-nv  2.1.21-
> 2020.0.1.3  i--
> x11/server/xorg/driver/xorg-video-openchrome  0.6.0-
> 2020.0.1.4   i--
> x11/server/xorg/driver/xorg-video-r1286.10.2-
> 2020.0.1.3  i--
> x11/server/xorg/driver/xorg-video-savage  2.3.9-
> 2020.0.1.3   i--
> x11/server/xorg/driver/xorg-video-trident 1.3.8-
> 2020.0.1.3   i--
> x11/server/xorg/driver/xorg-video-vboxvideo   1.0.1-
> 2020.0.1.4   i--
> x11/server/xorg/driver/xorg-video-vesa2.4.0-
> 2020.0.1.2   i--
> x11/server/xorg/driver/xorg-video-vmware  13.3.0-
> 2020.0.1.2  i--
> root@emu:~#
> 
> 
> Here's what it says in /var/adm/messages:
> 
> snip---
> Aug 17 21:15:43 emu unix: [ID 836849 kern.notice] 
> Aug 17 21:15:43 emu ^Mpanic[cpu1]/thread=fe2cedcf1080: 
> Aug 17 21:15:43 emu genunix: [ID 335743 kern.notice] BAD TRAP: type=e
> (#pf Page fault) rp=fe003e3d5710 addr=0 occurred in
>  module "unix" due to a NULL pointer dereference
> Aug 17 21:15:43 emu unix: [ID 10 kern.notice] 
> Aug 17 21:15:43 emu unix: [ID 839527 kern.notice] Xorg: 
> Aug 17 21:15:43 emu unix: [ID 753105 kern.notice] #pf Page fault
> Aug 17 21:15:43 emu unix: [ID 532287 kern.notice] Bad kernel fault at
> addr=0x0
> Aug 17 21:15:43 emu unix: [ID 243837 kern.notice] pid=4770,
> pc=0xfb88151b, sp=0xfe003e3d5808, eflags=0x10246
> Aug 17 21:15:43 emu unix: [ID 619397 kern.notice] cr0:
> 80050033  cr4:
> 1626f8 xsr,pge,mce,pae,pse,de>
> Aug 17 21:15:43 emu unix: [ID 152204 kern.notice] cr2: 0  
> Aug 17 21:15:43 emu unix: [ID 634440 kern.notice] cr3: 80aaa1000  
> Aug 17 21:15:43 emu unix: [ID 625715 kern.notice] cr8: 0
> Aug 17 21:15:43 emu unix: [ID 10 kern.notice] 
> Aug 17 21:15:43 emu unix: [ID 592667
> kern.notice]   rdi:0 rsi:0 rdx:
> fe2cedcf1080
> Aug 17 21:15:43 emu unix: [ID 592667
> kern.notice]   rcx:1c000  r8: 1000  r9:  
>   
> 1
> Aug 17 21:15:43 emu unix: [ID 592667
> kern.notice]   rax:0 rbx:0 rbp:
> fe003e3d5830
> Aug 17 21:15:43 emu unix: [ID 592667 kern.notice]   r10:
> fb875f78 r11:2 r12: fe003e3d5a78
> Aug 17 21:15:43 emu unix: [ID 592667
> kern.notice]   r13: 1000 r14:1 r15:
> fe2d0a39c020
> Aug 17 21:15:43 emu unix: [ID 592667 kern.notice]   fsb:
> fc7fef0833c0 gsb: fe2ce94cc000  ds:0
> Aug 17 21:15:43 emu unix: [ID 592667
> kern.notice]es:0  fs:0  gs:  
>   
> 0
> Aug 

Re: [OpenIndiana-discuss] Kernel panic

[Adam Števko]

Can you post the core dump somewhere?

Cheers,
Adam

> On 4 Oct 2016, at 14:33, Apostolos Syropoulos via openindiana-discuss 
>  wrote:
> 
> Today I saw the following:
> 
> 
> 
> Oct  4 15:26:18 adalind savecore: [ID 570001 auth.error] reboot after panic: 
> 
> assertion failed: (vp->v_count > 0) && (vp->v_count_dnlc > 0), file: 
> ../../common/fs/vnode.c, line: 852
> 
> 
> Does anybody have any idea what this is about?
> 
> A.S.
> --
> Apostolos Syropoulos
> Xanthi, Greece
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel panic on hung zpool accessed via lofi

[Jason Matthews]

Sent from my iPhone

> On Sep 16, 2015, at 11:49 AM, Watson, Dan  wrote:
> 
> I've noticed that drives with a labeled WWN tend to be less error prone, and 
> only when a driv

This a distinction that only exists in your head.  :)

I have only 768 HGST 600gb sas drives in spinning in production at a time in a 
Hadoop environment. They have no labeled WWN and they may be the best spinning 
rust I have ever used in terms for failures. Also when the drives fail, they 
have so far done so in a graceful manner. 

J. 
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel panic on hung zpool accessed via lofi

[Nikola M]

On 09/16/15 10:42 PM, Andrew Gabriel wrote:
Also what OI/illumos is that, because I was reading long ago there 
were some bugs solved in illumos for mpt_sas.


Somewhere around 18 months ago IIRC, Nexenta pushed a load of fixes 
for this into their git repo. I don't think I've seen these picked up 
yet by Illumos, although maybe I missed it? The fixes were in mpt_sas 
and FMA, to more accurately determine when disks are going bad by 
pushing the timing of the SCSI commands right down to the bottom of 
the stack (so delays in the software stack are not mistaken for bad 
drives), and to have FMA better analyse and handle errors when they do 
happen. 


It is strange how companies in illumos ecosystem do not push their 
changes (or do push veeery slow and late) to illumos upstream, but keep 
them by themselves i their codebase.
And if other distros want to have them, they need to port them 
themselves in possibly different ways.


Maybe illumos have big barrier on code quality of what enters in illumos 
or not,
regarding "always stable" mantra without stable/supportable/older 
illumos releases and developing branches.


___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel panic on hung zpool accessed via lofi

[Rich Murphey]

I'm also seeing panics in 'deadman' caused by failing drives, for SATA
drives, but also for SAS and SATA NAS drives as well.

In my limited experience, I've found Smart stats very effective in
resolving drive issues, using five specific metrics recommended by
Backblaze (below).
By eliminating drives that have non-zero values for any of these specific
metrics, the panics (for me) were eliminated.

I mention this also because drives that are gradually failing can cause
intermittent hangs, and cause one to suspect SAS cables, expanders, etc.
I don't want to discourage you from swapping other parts to try to resolve
issues, but rather look at Smart metrics as well.

Best regards,
Rich


   - SMART 5 – Reallocated_Sector_Count.
   - SMART 187 – Reported_Uncorrectable_Errors.
   - SMART 188 – Command_Timeout.
   - SMART 197 – Current_Pending_Sector_Count.
   - SMART 198 – Offline_Uncorrectable.

https://www.backblaze.com/blog/hard-drive-smart-stats/




On Wed, Sep 16, 2015 at 1:50 PM Watson, Dan <dan.wat...@bcferries.com>
wrote:

> I know it's not the best route to go but for personal use and budget SATA
> drives on SAS expanders is much easier to achieve.  Used 3Gbit SAS trays
> with expander can be had for $12/drive bay, while for retail there is still
> a significant price jump going from SATA interface to SAS. And even drives
> like the new Seagate 8TB "Cloud backup" drive don't have a SAS option,
> although now that I think about it they are probably marketed more towards
> "personal cloud" devices than actual datacenter based cloud services.
>
> Also the newer SATA drives are much less disruptive in a SAS tray than the
> early capacity drives. I've noticed that drives with a labeled WWN tend to
> be less error prone, and only when a drive completely dies do you get the
> cascading bus reset that kills all IO. Just don't daisy chain the SAS
> expanders/trays because that seems to introduce significant errors.
>
> This is an updated fresh install of OI. I'm not using any special
> publisher so I imagine it's somewhat out of date.
>
> I've managed to get the zpool working using the read-only  import option
> mentioned previously and it seems to be working fine. I'm betting I just
> did not have enough RAM available to do dedupe.
>
> Thanks!
> Dan
>
> -Original Message-
> From: Nikola M [mailto:minik...@gmail.com]
> Sent: September 16, 2015 11:25 AM
> To: Discussion list for OpenIndiana
> Subject: Re: [OpenIndiana-discuss] Kernel panic on hung zpool accessed via
> lofi
>
> On 09/11/15 08:57 PM, Watson, Dan wrote:
> > I'm using mpt_sas with SATA drives, and I_DO_  have error counters
> climbing for some of those drives, is it probably that?
> > Any other ideas?
>
> It is generally strongly advised to use SATA disks on SATA controllers
> and SAS disks on SAS controllers. And to use controller that can do JBOD.
>
> Also, using SAS to SATA multipliers or using port multipliers at all is
> strongly disadvised too,
> because it is usually cheap logic in it, that can go crazy and disk is
> not under direct control of the controller..
>
> Also what OI/illumos is that, because I was reading long ago there were
> some bugs solved in illumos for mpt_sas.
>
> First two issues could be hardware problems, and such config is usually
> unsupportable (I know it is not on Smartos), third issue could be seen
> further.
>
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel panic on hung zpool accessed via lofi

[Watson, Dan]

I know it's not the best route to go but for personal use and budget SATA 
drives on SAS expanders is much easier to achieve.  Used 3Gbit SAS trays with 
expander can be had for $12/drive bay, while for retail there is still a 
significant price jump going from SATA interface to SAS. And even drives like 
the new Seagate 8TB "Cloud backup" drive don't have a SAS option, although now 
that I think about it they are probably marketed more towards "personal cloud" 
devices than actual datacenter based cloud services.
 
Also the newer SATA drives are much less disruptive in a SAS tray than the 
early capacity drives. I've noticed that drives with a labeled WWN tend to be 
less error prone, and only when a drive completely dies do you get the 
cascading bus reset that kills all IO. Just don't daisy chain the SAS 
expanders/trays because that seems to introduce significant errors.

This is an updated fresh install of OI. I'm not using any special publisher so 
I imagine it's somewhat out of date.

I've managed to get the zpool working using the read-only  import option 
mentioned previously and it seems to be working fine. I'm betting I just did 
not have enough RAM available to do dedupe.

Thanks!
Dan

-Original Message-
From: Nikola M [mailto:minik...@gmail.com] 
Sent: September 16, 2015 11:25 AM
To: Discussion list for OpenIndiana
Subject: Re: [OpenIndiana-discuss] Kernel panic on hung zpool accessed via lofi

On 09/11/15 08:57 PM, Watson, Dan wrote:
> I'm using mpt_sas with SATA drives, and I_DO_  have error counters climbing 
> for some of those drives, is it probably that?
> Any other ideas?

It is generally strongly advised to use SATA disks on SATA controllers 
and SAS disks on SAS controllers. And to use controller that can do JBOD.

Also, using SAS to SATA multipliers or using port multipliers at all is 
strongly disadvised too,
because it is usually cheap logic in it, that can go crazy and disk is 
not under direct control of the controller..

Also what OI/illumos is that, because I was reading long ago there were 
some bugs solved in illumos for mpt_sas.

First two issues could be hardware problems, and such config is usually 
unsupportable (I know it is not on Smartos), third issue could be seen 
further.


___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel panic on hung zpool accessed via lofi

[Watson, Dan]

>-Original Message-
>From: Jim Klimov [mailto:jimkli...@cos.ru] 
>Sent: September 12, 2015 10:31 AM
>To: Discussion list for OpenIndiana; Watson, Dan; 
>openindiana-discuss@openindiana.org
>Subject: Re: [OpenIndiana-discuss] Kernel panic on hung zpool accessed via lofi
>
>11 сентября 2015 г. 20:57:46 CEST, "Watson, Dan" <dan.wat...@bcferries.com> 
>пишет:
>>Hi all,
>>
>>I've been enjoying OI for quite a while butI'm running into a problem
>>with accessing zpool on disk image files sitting on zfs accessed via
>>lofi that I hope someone can give me a hint on.

>>I have been able to reproduce this problem several times, although it
>>has managed to complete enough to rename the original zpool.
>>
>>Has anyone else encountered this issue with lofi mounted zpools?
>>I'm using mpt_sas with SATA drives, and I _DO_ have error counters
>>climbing for some of those drives, is it probably that?
>>Any other ideas?
>>
>>I'd greatly appreciate any suggestions.
>>
>>Thanks!
>>Dan
>>
>>___
>>openindiana-discuss mailing list
>>openindiana-discuss@openindiana.org
>>http://openindiana.org/mailman/listinfo/openindiana-discuss
>
>From the zpool status I see it also refers to cache disks. Are those device 
>names actually available (present and not used by another pool)? Can you 
>remove them from the pool after you've imported it?
>
>Consider importing with '-N' to not automount (and autoshare) filesystems from 
>this pool, and '-R /a' or some other empty/absent altroot path to ensure lack 
>of conflicts when you do mount (and also does not add the poll into >zfs.cache 
>file for later autoimports). At least, mounting and sharing as a (partially) 
>kernel-side operation is something that might time out...
>
>Also, you might want to tune or disable the deadman timer and increase other 
>acceptable latencies (see OI wiki or other resources).
>
>How much RAM does the box have (you pay twice the ARC cache for oldtank and 
>for pool which hosts the dd files), maybe tune down primary/secondary caching 
>for the files store.
>
>How did you get into this recovery situation? Maybe oldtank is corrupted and 
>so is trying to recover during import? E.g. I had a history with a deduped 
>pool where I deleted lots of data and the kernel wanted more RAM to process 
>>the delete-queue of blocks than I had, and it took dozens of panic-reboots to 
>complete (progress can be tracked with zdb).
>
>Alternately you can import the pool read-only to maybe avoid these recoveries 
>altogether if you only want to retrieve the data.
>
>Jim
>
>--
>Typos courtesy of K-9 Mail on my Samsung Android

I can't remove the cache drives from the zpool as all zpool commands seem to 
hang waiting for something but they are not available on the host (anymore). 
I'm hoping they show up as absent/degraded.

I'll try -N and/or -R /a

I'll read up on how to tune the deadman timer, I've been looking at 
https://smartos.org/bugview/OS-2415 and that has lots of useful things to tune.

I ended up doing this because the original host of the zpool stopped being able 
to make it to multi-user while attached to the disk. With SATA disk in a SAS 
tray that usually means (to me) that one of the disks is faulty and sending 
resets to the controller causing the whole disk tray to reset. I tried 
identifying the faulty disk but tested individually all the disks worked fine. 
I decided to try copying the disk images to the alternate host to try to 
recover the data. Further oddities have cropped up on the original host so I'm 
going to try connecting the original disk tray to an alternate host.

I'll try read-only first. I was unaware there was a way to do this. I obviously 
need a ZFS refresher.

Thanks Jim!

Dan
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel panic on hung zpool accessed via lofi

[Jim Klimov]

14 сентября 2015 г. 20:23:18 CEST, "Watson, Dan" <dan.wat...@bcferries.com> 
пишет:
>>-Original Message-
>>From: Jim Klimov [mailto:jimkli...@cos.ru] 
>>Sent: September 12, 2015 10:31 AM
>>To: Discussion list for OpenIndiana; Watson, Dan;
>openindiana-discuss@openindiana.org
>>Subject: Re: [OpenIndiana-discuss] Kernel panic on hung zpool accessed
>via lofi
>>
>>11 сентября 2015 г. 20:57:46 CEST, "Watson, Dan"
><dan.wat...@bcferries.com> пишет:
>>>Hi all,
>>>
>>>I've been enjoying OI for quite a while butI'm running into a problem
>>>with accessing zpool on disk image files sitting on zfs accessed via
>>>lofi that I hope someone can give me a hint on.
>
>>>I have been able to reproduce this problem several times, although it
>>>has managed to complete enough to rename the original zpool.
>>>
>>>Has anyone else encountered this issue with lofi mounted zpools?
>>>I'm using mpt_sas with SATA drives, and I _DO_ have error counters
>>>climbing for some of those drives, is it probably that?
>>>Any other ideas?
>>>
>>>I'd greatly appreciate any suggestions.
>>>
>>>Thanks!
>>>Dan
>>>
>>>___
>>>openindiana-discuss mailing list
>>>openindiana-discuss@openindiana.org
>>>http://openindiana.org/mailman/listinfo/openindiana-discuss
>>
>>From the zpool status I see it also refers to cache disks. Are those
>device names actually available (present and not used by another pool)?
>Can you remove them from the pool after you've imported it?
>>
>>Consider importing with '-N' to not automount (and autoshare)
>filesystems from this pool, and '-R /a' or some other empty/absent
>altroot path to ensure lack of conflicts when you do mount (and also
>does not add the poll into >zfs.cache file for later autoimports). At
>least, mounting and sharing as a (partially) kernel-side operation is
>something that might time out...
>>
>>Also, you might want to tune or disable the deadman timer and increase
>other acceptable latencies (see OI wiki or other resources).
>>
>>How much RAM does the box have (you pay twice the ARC cache for
>oldtank and for pool which hosts the dd files), maybe tune down
>primary/secondary caching for the files store.
>>
>>How did you get into this recovery situation? Maybe oldtank is
>corrupted and so is trying to recover during import? E.g. I had a
>history with a deduped pool where I deleted lots of data and the kernel
>wanted more RAM to process >the delete-queue of blocks than I had, and
>it took dozens of panic-reboots to complete (progress can be tracked
>with zdb).
>>
>>Alternately you can import the pool read-only to maybe avoid these
>recoveries altogether if you only want to retrieve the data.
>>
>>Jim
>>
>>--
>>Typos courtesy of K-9 Mail on my Samsung Android
>
>I can't remove the cache drives from the zpool as all zpool commands
>seem to hang waiting for something but they are not available on the
>host (anymore). I'm hoping they show up as absent/degraded.
>
>I'll try -N and/or -R /a
>
>I'll read up on how to tune the deadman timer, I've been looking at
>https://smartos.org/bugview/OS-2415 and that has lots of useful things
>to tune.
>
>I ended up doing this because the original host of the zpool stopped
>being able to make it to multi-user while attached to the disk. With
>SATA disk in a SAS tray that usually means (to me) that one of the
>disks is faulty and sending resets to the controller causing the whole
>disk tray to reset. I tried identifying the faulty disk but tested
>individually all the disks worked fine. I decided to try copying the
>disk images to the alternate host to try to recover the data. Further
>oddities have cropped up on the original host so I'm going to try
>connecting the original disk tray to an alternate host.
>
>I'll try read-only first. I was unaware there was a way to do this. I
>obviously need a ZFS refresher.
>
>Thanks Jim!
>
>Dan
>___
>openindiana-discuss mailing list
>openindiana-discuss@openindiana.org
>http://openindiana.org/mailman/listinfo/openindiana-discuss

BTW regarding '-N' to not-mount filesystems from the imported pool - you can 
follow up with 'zfs mount -a' if/when the pool gets imported. It may be that 
some one specific dataset fails to mount and/or share due to some fatal errors, 
while others work ok. If that does bite, on the next reboot you can script a 
oneliner to mount fs'es one by one to determine the troublemaker. ;)
--
Typos courtesy of K-9 Mail on my Samsung Android

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel panic on hung zpool accessed via lofi

[Jim Klimov]

11 сентября 2015 г. 20:57:46 CEST, "Watson, Dan"  
пишет:
>Hi all,
>
>I've been enjoying OI for quite a while butI'm running into a problem
>with accessing zpool on disk image files sitting on zfs accessed via
>lofi that I hope someone can give me a hint on.
>
>To recover data from a zpool I've copied slice 0 off of all the disks
>to a different host under /alt (zfs file system)
>root@represent:/alt# ls
>c1t50014EE0037B0FF3d0s0.dd  c1t50014EE0AE25CF55d0s0.dd 
>c1t50014EE2081874CAd0s0.dd  c1t50014EE25D6CDE92d0s0.dd 
>c1t50014EE25D6DDBC7d0s0.dd  c1t50014EE2B2C380C3d0s0.dd
>c1t50014EE0037B105Fd0s0.dd  c1t50014EE0AE25EFD1d0s0.dd 
>c1t50014EE20818C0ECd0s0.dd  c1t50014EE25D6DCF0Ed0s0.dd 
>c1t50014EE2B2C27AE2d0s0.dd  c1t50014EE6033DD776d0s0.dd
>
>I use lofiadm to access the disk images as devices because for some
>reason zfs can't access a "device" formatted vdev as a file
>root@represent:/alt# lofiadm
>Block Device File   Options
>/dev/lofi/1  /alt/c1t50014EE0037B0FF3d0s0.dd-
>/dev/lofi/2  /alt/c1t50014EE0037B105Fd0s0.dd-
>/dev/lofi/3  /alt/c1t50014EE0AE25CF55d0s0.dd-
>/dev/lofi/4  /alt/c1t50014EE0AE25EFD1d0s0.dd-
>/dev/lofi/5  /alt/c1t50014EE2081874CAd0s0.dd-
>/dev/lofi/6  /alt/c1t50014EE20818C0ECd0s0.dd-
>/dev/lofi/7  /alt/c1t50014EE25D6CDE92d0s0.dd-
>/dev/lofi/8  /alt/c1t50014EE25D6DCF0Ed0s0.dd-
>/dev/lofi/9  /alt/c1t50014EE25D6DDBC7d0s0.dd-
>/dev/lofi/10 /alt/c1t50014EE2B2C27AE2d0s0.dd-
>/dev/lofi/11 /alt/c1t50014EE2B2C380C3d0s0.dd-
>/dev/lofi/12 /alt/c1t50014EE6033DD776d0s0.dd-
>
>The zpool is identifiable
>root@represent:/alt# zpool import -d /dev/lofi
>   pool: oldtank
> id: 1346358639852818
>  state: ONLINE
> status: One or more devices are missing from the system.
> action: The pool can be imported using its name or numeric identifier.
>   see: http://illumos.org/msg/ZFS-8000-2Q
> config:
>oldtank  ONLINE
>  raidz2-0   ONLINE
>/dev/lofi/4  ONLINE
>/dev/lofi/2  ONLINE
>/dev/lofi/1  ONLINE
>/dev/lofi/3  ONLINE
>/dev/lofi/8  ONLINE
>/dev/lofi/10 ONLINE
>/dev/lofi/11 ONLINE
>/dev/lofi/7  ONLINE
>/dev/lofi/6  ONLINE
>/dev/lofi/9  ONLINE
>/dev/lofi/5  ONLINE
>/dev/lofi/12 ONLINE
>cache
>  c1t50015178F36728A3d0
>  c1t50015178F3672944d0
>
>And I import the zpool (this command never exits)
>root@represent:/alt# zpool import -d /dev/lofi oldtank
>
>In another window it is evident that the system has managed to add the
>zpool
>   extended device statistics    errors ---
>r/sw/s   Mr/s   Mw/s wait actv wsvc_t asvc_t  %w  %b s/w h/w trn
>tot device
>101.10.01.70.0  0.3  2.82.9   27.5  28 100   0   0   0 
> 0 lofi1
>118.60.01.30.0  0.3  2.92.4   24.3  28 100   0   0   0 
> 0 lofi2
>123.80.01.00.0  0.3  2.92.7   23.3  31  94   0   0   0 
> 0 lofi3
>133.10.01.10.0  0.4  2.82.7   20.7  34  92   0   0   0 
> 0 lofi4
>144.80.01.60.0  0.2  2.71.3   18.7  17  97   0   0   0 
> 0 lofi5
>132.30.01.20.0  0.2  2.51.4   18.7  17  95   0   0   0 
> 0 lofi6
>100.30.01.00.0  0.2  2.71.9   26.6  18 100   0   0   0 
> 0 lofi7
>117.30.01.20.0  0.2  2.71.9   23.3  21  99   0   0   0 
> 0 lofi8
>142.10.01.00.0  0.3  2.51.9   17.3  26  85   0   0   0 
> 0 lofi9
>142.80.01.00.0  0.2  2.51.5   17.4  20  83   0   0   0 
> 0 lofi10
>144.10.00.90.0  0.3  2.72.0   19.0  28  96   0   0   0 
> 0 lofi11
>101.80.00.80.0  0.2  2.72.2   26.1  21  96   0   0   0 
> 0 lofi12
>1502.10.0   13.70.0 3229.1 35.3 2149.7   23.5 100 100   0   0  
>0   0 oldtank
>...
>195.60.05.80.0  0.0  6.10.0   31.4   0  95   0   0   0 
> 0 c0t50014EE25F8307D2d0
>200.90.05.80.0  0.0  7.50.0   37.2   0  97   0   0   0 
> 0 c0t50014EE2B4CAA6D3d0
>200.10.05.80.0  0.0  7.00.0   35.1   0  97   0   0   0 
> 0 c0t50014EE25F74EC15d0
>197.90.05.90.0  0.0  7.20.0   36.2   0  96   0   0   0 
> 0 c0t50014EE25F74DD46d0
>198.10.05.50.0  0.0  6.70.0   34.0   0  95   0   0   0 
> 0 c0t50014EE2B4D7C1C9d0
>202.40.05.90.0  0.0  6.90.0   34.1   0  97   0   0   0 
> 0 c0t50014EE2B4CA8F9Bd0
>223.90.06.90.0  0.0  8.80.0   39.1   0 100   0   0   0 
> 0 c0t50014EE20A2DAE1Ed0
>201.60.05.90.0  0.0  6.60.0   32.9   0  96   0   0   0 
> 0 

Re: [OpenIndiana-discuss] kernel panic in nsmb module

[Gordon Ross]

You need this fix:
https://github.com/Nexenta/illumos-nexenta/commit/9a60a9d168313d9c350f813abccc6320879ad9b5



On Thu, Apr 17, 2014 at 5:05 PM, Geoff Nordli geo...@gnaa.net wrote:
 On 14-04-17 01:20 PM, Geoff Nordli wrote:

 I am running OI 151a8.

 I had a kernel panic today.   I have the dump file so I can provide more
 detail if needed.

 Should I send this over to the illumos list or can someone help me here?

 thanks,

 Geoff



 TIME   UUID SUNW-MSG-ID
 Apr 17 2014 12:19:26.324813000 dabd95a4-28d1-6cb4-e42e-fc1cc9b9ac26
 SUNOS-8000-KL

   TIME CLASS ENA
   Apr 17 12:19:25.6166 ireport.os.sunos.panic.dump_pending_on_device
 0x

 nvlist version: 0
 version = 0x0
 class = list.suspect
 uuid = dabd95a4-28d1-6cb4-e42e-fc1cc9b9ac26
 code = SUNOS-8000-KL
 diag-time = 1397762366 320950
 de = fmd:///module/software-diagnosis
 fault-list-sz = 0x1
 fault-list = (array of embedded nvlists)
 (start fault-list[0])
 nvlist version: 0
 version = 0x0
 class = defect.sunos.kernel.panic
 certainty = 0x64
 asru =
 sw:///:path=/var/crash/ma-stor1/.dabd95a4-28d1-6cb4-e42e-fc1cc9b9ac26
 resource =
 sw:///:path=/var/crash/ma-stor1/.dabd95a4-28d1-6cb4-e42e-fc1cc9b9ac26
 savecore-succcess = 0
 os-instance-uuid = dabd95a4-28d1-6cb4-e42e-fc1cc9b9ac26
 panicstr = BAD TRAP: type=e (#pf Page fault)
 rp=ff007aae0960 addr=18 occurred in module nsmb due to a NULL pointer
 dereference
 panicstack = unix:die+dd () | unix:trap+17db () |
 unix:cmntrap+e6 () | nsmb:nbssn_recv+e8 () | nsmb:smb_nbst_recv+62 () |
 nsmb:smb_iod_recv1+3b () | nsmb:smb_iod_recvall+65 () |
 nsmb:smb_iod_vc_work+a0 () | nsmb:smb_usr_iod_work+f4 () |
 nsmb:nsmb_ioctl+d5 () | genunix:cdev_ioctl+45 () | specfs:spec_ioctl+5a () |
 genunix:fop_ioctl+7b () | genunix:ioctl+18e () | unix:brand_sys_sysenter+1c9
 () |
 crashtime = 1397760419
 panic-time = Thu Apr 17 11:46:59 2014 PDT
 (end fault-list[0])

 fault-status = 0x1
 severity = Major
 __ttl = 0x1
 __tod = 0x5350293e 0x135c40c8


 some more info:

 ::msgbuf

 ..
 pseudo-device: rdc0
 rdc0 is /pseudo/rdc@0
 WARNING: export[root(/tank/homes/root)]: failed obtaining vnode (2)
 NOTICE: smb_smb_treeconnect: (\\ma-dc1\IPC$) failed, status=0x0
 NOTICE: smb_smb_treeconnect: (\\ma-dc1\IPC$) failed, status=0x0

 ^Mpanic[cpu1]/thread=ff11636efb80:

 BAD TRAP: type=e (#pf Page fault) rp=ff007aae0960 addr=18 occurred in
 module
  nsmb due to a NULL pointer dereference


 smbiod:
 #pf Page fault
 Bad kernel fault at addr=0x18
 pid=11108, pc=0xf7e2cc98, sp=0xff007aae0a50, eflags=0x10246
 cr0: 8005003bpg,wp,ne,et,ts,mp,pe cr4:
 426f8osxsav,vmxe,xmme,fxsr,pge,mce,pae
 ,pse,de
 cr2: 18
 cr3: 869c74000
 cr8: 0

 rdi:0 rsi: ff12090f11b0 rdx:   34
 rcx:0  r8:   34 r9:   1b
 rax:0 rbx: ff007aae0ac8 rbp: ff007aae0ab0
 r10:   1a r11: ff007aae0820 r12:0
 r13: ff12090f11a0 r14: ff007aae0acf r15: ff007aae0b18
 fsb: fd7fff13aa40 gsb: ff11574f4580 ds:   4b
  es:   4b  fs:0 gs:0
 trp:e err:2 rip: f7e2cc98
  cs:   30 rfl:10246 rsp: ff007aae0a50
  ss:   38

 ff007aae0830 unix:die+dd ()
 ff007aae0950 unix:trap+17db ()
 ff007aae0960 unix:cmntrap+e6 ()
 ff007aae0ab0 nsmb:nbssn_recv+e8 ()
 ff007aae0b00 nsmb:smb_nbst_recv+62 ()
 ff007aae0b50 nsmb:smb_iod_recv1+3b ()
 ff007aae0bb0 nsmb:smb_iod_recvall+65 ()
 ff007aae0bf0 nsmb:smb_iod_vc_work+a0 ()
 ff007aae0c50 nsmb:smb_usr_iod_work+f4 ()
 ff007aae0cc0 nsmb:nsmb_ioctl+d5 ()
 ff007aae0d00 genunix:cdev_ioctl+45 ()
 ff007aae0d40 specfs:spec_ioctl+5a ()
 ff007aae0dc0 genunix:fop_ioctl+7b ()
 ff007aae0ec0 genunix:ioctl+18e ()
 ff007aae0f10 unix:brand_sys_sysenter+1c9 ()

 syncing file systems...
  done
 dumping to /dev/zvol/dsk/rpool1/dump, offset 65536, content: kernel
 NOTICE: ahci0: ahci_tran_reset_dport port 0 reset port
 NOTICE: ahci0: ahci_tran_reset_dport port 1 reset port



 ::stack
 nbssn_recv+0xe8(ff12090f11a0, ff007aae0b18, ff007aae0ac8,
 ff007aae0acf)
 smb_nbst_recv+0x62(ff121911, ff007aae0b18)
 smb_iod_recv1+0x3b(ff121911, ff007aae0b78)
 smb_iod_recvall+0x65(ff121911)
 smb_iod_vc_work+0xa0(ff121911, ff11633c20d8)
 smb_usr_iod_work+0xf4(ff12097218b0, 80ec4f0, 13, ff11633c20d8)
 

Re: [OpenIndiana-discuss] kernel panic in nsmb module

[Geoff Nordli]

Thanks Gordon.

Any idea if that has been merged into illumos gate yet?


On 14-04-21 06:04 PM, Gordon Ross wrote:

You need this fix:
https://github.com/Nexenta/illumos-nexenta/commit/9a60a9d168313d9c350f813abccc6320879ad9b5



On Thu, Apr 17, 2014 at 5:05 PM, Geoff Nordli geo...@gnaa.net wrote:

On 14-04-17 01:20 PM, Geoff Nordli wrote:

I am running OI 151a8.

I had a kernel panic today.   I have the dump file so I can provide more
detail if needed.

Should I send this over to the illumos list or can someone help me here?

thanks,

Geoff



TIME   UUID SUNW-MSG-ID
Apr 17 2014 12:19:26.324813000 dabd95a4-28d1-6cb4-e42e-fc1cc9b9ac26
SUNOS-8000-KL

   TIME CLASS ENA
   Apr 17 12:19:25.6166 ireport.os.sunos.panic.dump_pending_on_device
0x

nvlist version: 0
 version = 0x0
 class = list.suspect
 uuid = dabd95a4-28d1-6cb4-e42e-fc1cc9b9ac26
 code = SUNOS-8000-KL
 diag-time = 1397762366 320950
 de = fmd:///module/software-diagnosis
 fault-list-sz = 0x1
 fault-list = (array of embedded nvlists)
 (start fault-list[0])
 nvlist version: 0
 version = 0x0
 class = defect.sunos.kernel.panic
 certainty = 0x64
 asru =
sw:///:path=/var/crash/ma-stor1/.dabd95a4-28d1-6cb4-e42e-fc1cc9b9ac26
 resource =
sw:///:path=/var/crash/ma-stor1/.dabd95a4-28d1-6cb4-e42e-fc1cc9b9ac26
 savecore-succcess = 0
 os-instance-uuid = dabd95a4-28d1-6cb4-e42e-fc1cc9b9ac26
 panicstr = BAD TRAP: type=e (#pf Page fault)
rp=ff007aae0960 addr=18 occurred in module nsmb due to a NULL pointer
dereference
 panicstack = unix:die+dd () | unix:trap+17db () |
unix:cmntrap+e6 () | nsmb:nbssn_recv+e8 () | nsmb:smb_nbst_recv+62 () |
nsmb:smb_iod_recv1+3b () | nsmb:smb_iod_recvall+65 () |
nsmb:smb_iod_vc_work+a0 () | nsmb:smb_usr_iod_work+f4 () |
nsmb:nsmb_ioctl+d5 () | genunix:cdev_ioctl+45 () | specfs:spec_ioctl+5a () |
genunix:fop_ioctl+7b () | genunix:ioctl+18e () | unix:brand_sys_sysenter+1c9
() |
 crashtime = 1397760419
 panic-time = Thu Apr 17 11:46:59 2014 PDT
 (end fault-list[0])

 fault-status = 0x1
 severity = Major
 __ttl = 0x1
 __tod = 0x5350293e 0x135c40c8


some more info:

::msgbuf

..
pseudo-device: rdc0
rdc0 is /pseudo/rdc@0
WARNING: export[root(/tank/homes/root)]: failed obtaining vnode (2)
NOTICE: smb_smb_treeconnect: (\\ma-dc1\IPC$) failed, status=0x0
NOTICE: smb_smb_treeconnect: (\\ma-dc1\IPC$) failed, status=0x0

^Mpanic[cpu1]/thread=ff11636efb80:

BAD TRAP: type=e (#pf Page fault) rp=ff007aae0960 addr=18 occurred in
module
  nsmb due to a NULL pointer dereference


smbiod:
#pf Page fault
Bad kernel fault at addr=0x18
pid=11108, pc=0xf7e2cc98, sp=0xff007aae0a50, eflags=0x10246
cr0: 8005003bpg,wp,ne,et,ts,mp,pe cr4:
426f8osxsav,vmxe,xmme,fxsr,pge,mce,pae
,pse,de
cr2: 18
cr3: 869c74000
cr8: 0

 rdi:0 rsi: ff12090f11b0 rdx:   34
 rcx:0  r8:   34 r9:   1b
 rax:0 rbx: ff007aae0ac8 rbp: ff007aae0ab0
 r10:   1a r11: ff007aae0820 r12:0
 r13: ff12090f11a0 r14: ff007aae0acf r15: ff007aae0b18
 fsb: fd7fff13aa40 gsb: ff11574f4580 ds:   4b
  es:   4b  fs:0 gs:0
 trp:e err:2 rip: f7e2cc98
  cs:   30 rfl:10246 rsp: ff007aae0a50
  ss:   38

ff007aae0830 unix:die+dd ()
ff007aae0950 unix:trap+17db ()
ff007aae0960 unix:cmntrap+e6 ()
ff007aae0ab0 nsmb:nbssn_recv+e8 ()
ff007aae0b00 nsmb:smb_nbst_recv+62 ()
ff007aae0b50 nsmb:smb_iod_recv1+3b ()
ff007aae0bb0 nsmb:smb_iod_recvall+65 ()
ff007aae0bf0 nsmb:smb_iod_vc_work+a0 ()
ff007aae0c50 nsmb:smb_usr_iod_work+f4 ()
ff007aae0cc0 nsmb:nsmb_ioctl+d5 ()
ff007aae0d00 genunix:cdev_ioctl+45 ()
ff007aae0d40 specfs:spec_ioctl+5a ()
ff007aae0dc0 genunix:fop_ioctl+7b ()
ff007aae0ec0 genunix:ioctl+18e ()
ff007aae0f10 unix:brand_sys_sysenter+1c9 ()

syncing file systems...
  done
dumping to /dev/zvol/dsk/rpool1/dump, offset 65536, content: kernel
NOTICE: ahci0: ahci_tran_reset_dport port 0 reset port
NOTICE: ahci0: ahci_tran_reset_dport port 1 reset port




::stack

nbssn_recv+0xe8(ff12090f11a0, ff007aae0b18, ff007aae0ac8,
ff007aae0acf)
smb_nbst_recv+0x62(ff121911, ff007aae0b18)
smb_iod_recv1+0x3b(ff121911, ff007aae0b78)
smb_iod_recvall+0x65(ff121911)
smb_iod_vc_work+0xa0(ff121911, ff11633c20d8)
smb_usr_iod_work+0xf4(ff12097218b0, 80ec4f0, 

Re: [OpenIndiana-discuss] kernel panic in nsmb module

[Geoff Nordli]

On 14-04-17 01:20 PM, Geoff Nordli wrote:

I am running OI 151a8.

I had a kernel panic today.   I have the dump file so I can provide 
more detail if needed.


Should I send this over to the illumos list or can someone help me here?

thanks,

Geoff



TIME   UUID SUNW-MSG-ID
Apr 17 2014 12:19:26.324813000 dabd95a4-28d1-6cb4-e42e-fc1cc9b9ac26 
SUNOS-8000-KL


  TIME CLASS ENA
  Apr 17 12:19:25.6166 ireport.os.sunos.panic.dump_pending_on_device 
0x


nvlist version: 0
version = 0x0
class = list.suspect
uuid = dabd95a4-28d1-6cb4-e42e-fc1cc9b9ac26
code = SUNOS-8000-KL
diag-time = 1397762366 320950
de = fmd:///module/software-diagnosis
fault-list-sz = 0x1
fault-list = (array of embedded nvlists)
(start fault-list[0])
nvlist version: 0
version = 0x0
class = defect.sunos.kernel.panic
certainty = 0x64
asru = 
sw:///:path=/var/crash/ma-stor1/.dabd95a4-28d1-6cb4-e42e-fc1cc9b9ac26
resource = 
sw:///:path=/var/crash/ma-stor1/.dabd95a4-28d1-6cb4-e42e-fc1cc9b9ac26

savecore-succcess = 0
os-instance-uuid = dabd95a4-28d1-6cb4-e42e-fc1cc9b9ac26
panicstr = BAD TRAP: type=e (#pf Page fault) 
rp=ff007aae0960 addr=18 occurred in module nsmb due to a NULL 
pointer dereference
panicstack = unix:die+dd () | unix:trap+17db () | 
unix:cmntrap+e6 () | nsmb:nbssn_recv+e8 () | nsmb:smb_nbst_recv+62 () 
| nsmb:smb_iod_recv1+3b () | nsmb:smb_iod_recvall+65 () | 
nsmb:smb_iod_vc_work+a0 () | nsmb:smb_usr_iod_work+f4 () | 
nsmb:nsmb_ioctl+d5 () | genunix:cdev_ioctl+45 () | 
specfs:spec_ioctl+5a () | genunix:fop_ioctl+7b () | genunix:ioctl+18e 
() | unix:brand_sys_sysenter+1c9 () |

crashtime = 1397760419
panic-time = Thu Apr 17 11:46:59 2014 PDT
(end fault-list[0])

fault-status = 0x1
severity = Major
__ttl = 0x1
__tod = 0x5350293e 0x135c40c8



some more info:

::msgbuf

..
pseudo-device: rdc0
rdc0 is /pseudo/rdc@0
WARNING: export[root(/tank/homes/root)]: failed obtaining vnode (2)
NOTICE: smb_smb_treeconnect: (\\ma-dc1\IPC$) failed, status=0x0
NOTICE: smb_smb_treeconnect: (\\ma-dc1\IPC$) failed, status=0x0

^Mpanic[cpu1]/thread=ff11636efb80:
BAD TRAP: type=e (#pf Page fault) rp=ff007aae0960 addr=18 occurred 
in module

 nsmb due to a NULL pointer dereference


smbiod:
#pf Page fault
Bad kernel fault at addr=0x18
pid=11108, pc=0xf7e2cc98, sp=0xff007aae0a50, eflags=0x10246
cr0: 8005003bpg,wp,ne,et,ts,mp,pe cr4: 
426f8osxsav,vmxe,xmme,fxsr,pge,mce,pae

,pse,de
cr2: 18
cr3: 869c74000
cr8: 0

rdi:0 rsi: ff12090f11b0 rdx:   34
rcx:0  r8:   34 r9:   1b
rax:0 rbx: ff007aae0ac8 rbp: ff007aae0ab0
r10:   1a r11: ff007aae0820 r12:0
r13: ff12090f11a0 r14: ff007aae0acf r15: ff007aae0b18
fsb: fd7fff13aa40 gsb: ff11574f4580 ds:   4b
 es:   4b  fs:0 gs:0
trp:e err:2 rip: f7e2cc98
 cs:   30 rfl:10246 rsp: ff007aae0a50
 ss:   38

ff007aae0830 unix:die+dd ()
ff007aae0950 unix:trap+17db ()
ff007aae0960 unix:cmntrap+e6 ()
ff007aae0ab0 nsmb:nbssn_recv+e8 ()
ff007aae0b00 nsmb:smb_nbst_recv+62 ()
ff007aae0b50 nsmb:smb_iod_recv1+3b ()
ff007aae0bb0 nsmb:smb_iod_recvall+65 ()
ff007aae0bf0 nsmb:smb_iod_vc_work+a0 ()
ff007aae0c50 nsmb:smb_usr_iod_work+f4 ()
ff007aae0cc0 nsmb:nsmb_ioctl+d5 ()
ff007aae0d00 genunix:cdev_ioctl+45 ()
ff007aae0d40 specfs:spec_ioctl+5a ()
ff007aae0dc0 genunix:fop_ioctl+7b ()
ff007aae0ec0 genunix:ioctl+18e ()
ff007aae0f10 unix:brand_sys_sysenter+1c9 ()

syncing file systems...
 done
dumping to /dev/zvol/dsk/rpool1/dump, offset 65536, content: kernel
NOTICE: ahci0: ahci_tran_reset_dport port 0 reset port
NOTICE: ahci0: ahci_tran_reset_dport port 1 reset port



 ::stack
nbssn_recv+0xe8(ff12090f11a0, ff007aae0b18, ff007aae0ac8, 
ff007aae0acf)

smb_nbst_recv+0x62(ff121911, ff007aae0b18)
smb_iod_recv1+0x3b(ff121911, ff007aae0b78)
smb_iod_recvall+0x65(ff121911)
smb_iod_vc_work+0xa0(ff121911, ff11633c20d8)
smb_usr_iod_work+0xf4(ff12097218b0, 80ec4f0, 13, ff11633c20d8)
nsmb_ioctl+0xd5(330002f673, 6e7313, 80ec4f0, 13, ff11633c20d8, 
ff007aae0de4)
cdev_ioctl+0x45(330002f673, 6e7313, 80ec4f0, 13, ff11633c20d8, 
ff007aae0de4)
spec_ioctl+0x5a(ff1165ab7d00, 6e7313, 80ec4f0, 13, 
ff11633c20d8, ff007aae0de4)

Re: [OpenIndiana-discuss] kernel panic

[Marcel Telka]

On Thu, Dec 12, 2013 at 02:48:21PM -0800, Reginald Beardsley wrote:
 I didn't find anything in the wiki about reporting kernel panics.  Is there a
 documented procedure? The dump is ~285 MB.

http://wiki.illumos.org/display/illumos/How+To+Report+Problems

-- 
+---+
| Marcel Telka   e-mail:   mar...@telka.sk  |
|homepage: http://telka.sk/ |
|jabber:   mar...@jabber.sk |
+---+

___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel panic with Intel i7-2670QM CPU (HP EliteBook 8560w)

[Geoff Simmons]

 From: Geoff Simmons ge...@uplex.de 
 
 A colleague attempted to boot oi_151a from CD on an HP EliteBook 8560w 
 laptop: 
 
 http://h10010.www1.hp.com/wwpc/us/en/sm/WF06a/321957-321957-64295-3740645-4307559-5071171.html
  
 
 ... the variant with Intel i7-2670QM. He got an immediate kernel panic

I've now booted (from an oi151a CD) with the kernel debugger switched on
and was able to get a stack trace  -- the crash apparently happens in a
call to wrmsr() within speedstep_pstate_transition(), caused by an event
related to power management (cpupm).

Since I have no way of saving the stack trace, I had to take a picture
of it. In the hopes that attaching photos is not a netiquette violation
on this list, I'll try to send it along with this message (it's a B/W
PNG with about 23KB, so it shouldn't eat too much bandwidth -- my
apologies if this was a no-no).

As it happens, it appears to be exactly the same stack trace that I see
when trying to boot Solaris 11 on the same machine (using the kernel
debugger).

So it would appear that the problem has something to do with power
management, and might be related to some known bugs concerning cpupm:

https://www.illumos.org/issues/423
https://www.illumos.org/issues/1333

But the solutions/workarounds involve editing /etc/power.conf. I'm
trying to get OI to boot up in the first place, and I couldn't edit a
file on CD anyway. What I want to do is install OI, so I'll need to be
able to boot an installer before I can get to fixing up the installed
configuration.

Any ideas? Does this warrant filing a new issue at illumos.org?


Thanks,
Geoff
-- 
** * * UPLEX - Nils Goroll Systemoptimierung

Schwanenwik 24
22087 Hamburg

Tel +49 40 2880 5731
Mob +49 176 636 90917
Fax +49 40 42949753

http://uplex.de
attachment: oi151a_crash.png

signature.asc
Description: OpenPGP digital signature
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel panic with Intel i7-2670QM CPU (HP EliteBook 8560w)

[Bryan N Iotti]

Maybe you could try disabling ACPI in BIOS if possible, or otherwise use 
the acpi-user-options=0x2 at boot.


Read here for more info on disabling ACPI on boot:

https://blogs.oracle.com/danasblog/entry/configuring_solaris_acpi_at_boot

BTW and OT, I hadn't even thought that attaching an image to message 
here might have been bad etiquette/netiquette, so I apologize for that.


Bryan


On 02/13/12 06:39 PM, Geoff Simmons wrote:

From: Geoff Simmonsge...@uplex.de

A colleague attempted to boot oi_151a from CD on an HP EliteBook 8560w
laptop:

http://h10010.www1.hp.com/wwpc/us/en/sm/WF06a/321957-321957-64295-3740645-4307559-5071171.html

... the variant with Intel i7-2670QM. He got an immediate kernel panic

I've now booted (from an oi151a CD) with the kernel debugger switched on
and was able to get a stack trace  -- the crash apparently happens in a
call to wrmsr() within speedstep_pstate_transition(), caused by an event
related to power management (cpupm).

Since I have no way of saving the stack trace, I had to take a picture
of it. In the hopes that attaching photos is not a netiquette violation
on this list, I'll try to send it along with this message (it's a B/W
PNG with about 23KB, so it shouldn't eat too much bandwidth -- my
apologies if this was a no-no).

As it happens, it appears to be exactly the same stack trace that I see
when trying to boot Solaris 11 on the same machine (using the kernel
debugger).

So it would appear that the problem has something to do with power
management, and might be related to some known bugs concerning cpupm:

https://www.illumos.org/issues/423
https://www.illumos.org/issues/1333

But the solutions/workarounds involve editing /etc/power.conf. I'm
trying to get OI to boot up in the first place, and I couldn't edit a
file on CD anyway. What I want to do is install OI, so I'll need to be
able to boot an installer before I can get to fixing up the installed
configuration.

Any ideas? Does this warrant filing a new issue at illumos.org?


Thanks,
Geoff


___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss


___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel panic with Intel i7-2670QM CPU (HP EliteBook 8560w)

[Jason Matthews]

i would start even more conservatively and disable speed step in the bios first 
and then more on to the other suggestions.  i am not a fan of speedstep in 
general. 

j. 


Sent from Jasons' hand held

On Feb 13, 2012, at 9:44 AM, Bryan N Iotti ironsides.med...@gmail.com wrote:

 Maybe you could try disabling ACPI in BIOS if possible, or otherwise use the 
 acpi-user-options=0x2 at boot.
 
 Read here for more info on disabling ACPI on boot:
 
 https://blogs.oracle.com/danasblog/entry/configuring_solaris_acpi_at_boot
 
 BTW and OT, I hadn't even thought that attaching an image to message here 
 might have been bad etiquette/netiquette, so I apologize for that.
 
 Bryan
 
 
 On 02/13/12 06:39 PM, Geoff Simmons wrote:
 From: Geoff Simmonsge...@uplex.de
 A colleague attempted to boot oi_151a from CD on an HP EliteBook 8560w
 laptop:
 
 http://h10010.www1.hp.com/wwpc/us/en/sm/WF06a/321957-321957-64295-3740645-4307559-5071171.html
 
 ... the variant with Intel i7-2670QM. He got an immediate kernel panic
 I've now booted (from an oi151a CD) with the kernel debugger switched on
 and was able to get a stack trace  -- the crash apparently happens in a
 call to wrmsr() within speedstep_pstate_transition(), caused by an event
 related to power management (cpupm).
 
 Since I have no way of saving the stack trace, I had to take a picture
 of it. In the hopes that attaching photos is not a netiquette violation
 on this list, I'll try to send it along with this message (it's a B/W
 PNG with about 23KB, so it shouldn't eat too much bandwidth -- my
 apologies if this was a no-no).
 
 As it happens, it appears to be exactly the same stack trace that I see
 when trying to boot Solaris 11 on the same machine (using the kernel
 debugger).
 
 So it would appear that the problem has something to do with power
 management, and might be related to some known bugs concerning cpupm:
 
 https://www.illumos.org/issues/423
 https://www.illumos.org/issues/1333
 
 But the solutions/workarounds involve editing /etc/power.conf. I'm
 trying to get OI to boot up in the first place, and I couldn't edit a
 file on CD anyway. What I want to do is install OI, so I'll need to be
 able to boot an installer before I can get to fixing up the installed
 configuration.
 
 Any ideas? Does this warrant filing a new issue at illumos.org?
 
 
 Thanks,
 Geoff
 
 
 ___
 OpenIndiana-discuss mailing list
 OpenIndiana-discuss@openindiana.org
 http://openindiana.org/mailman/listinfo/openindiana-discuss
 
 ___
 OpenIndiana-discuss mailing list
 OpenIndiana-discuss@openindiana.org
 http://openindiana.org/mailman/listinfo/openindiana-discuss

___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel panic with Intel i7-2670QM CPU (HP EliteBook 8560w)

[Geoff Simmons]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 02/13/12 06:51 PM, Jason Matthews wrote:
 i would start even more conservatively and disable speed step in the
 bios first and then more on to the other suggestions. i am not a fan of
 speedstep in general.

 On Feb 13, 2012, at 9:44 AM, Bryan N Iotti ironsides.med...@gmail.com wrote:
 
 Maybe you could try disabling ACPI in BIOS if possible, or otherwise use the 
 acpi-user-options=0x2 at boot.

 Read here for more info on disabling ACPI on boot:

 https://blogs.oracle.com/danasblog/entry/configuring_solaris_acpi_at_boot

The beautifully user-friendly BIOS GUI unfortunately has nothing to say
about anything as geeky as ACPI or speedstep. I have the option of
switching off Power Control, but that does not prevent the crash.

I'll investigate the acpi-user-options.


Thanks,
Geoff
- -- 
** * * UPLEX - Nils Goroll Systemoptimierung

Schwanenwik 24
22087 Hamburg

Tel +49 40 2880 5731
Mob +49 176 636 90917
Fax +49 40 42949753

http://uplex.de
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (SunOS)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJPOVGmAAoJEOUwvh9pJNURwgEP/jMIwjkrU829RJXK1pxmZVhm
CVlGr/LXoYobiWiHBoPJ8awJnJW5ugfGfUSGT6X6FTfwVh73ywuxWTPXLTsl32f4
LpOc8+l22zvOFXHEenJfnb12bBe4TIxkpXYXc69gQUVfLlFEnNi86A7ncZ7XkJIT
XK8YXxFi7TfN4uG0DE7oPHH6JZGa5hR6aU+yN2KuS/m4FJtsHcqf7eVyxizKmEg/
KVQ5WK1YGUEemfwmLX5MEEwk+piGnPGxXgIG0SqfjyzfD2yde+I7mW4FgFmTYSiM
ydfebBc/uOSrdoCuMCAaysjbj2RwuXQlcrN1ciSboHoiD2aBmb9AQoZflgsgQtrI
lfV37xkOLS/n0/HQmRduYlR+c+1SMTtqlKoPFRROleyw7cMYrW+NQRtuc99rL8Kj
9scqtkzrwQzbHBeVHALH5+C74hZYqzI8oyo9v/saxp91IcpDsbWb7UZWiaKdDhhe
B1V2VgsFZ+QVjzp/QMA2AsLuSWkDETnQh/ywE+c2cyMozWu+0K3L+Z9TmWYdGqI2
bJXf6mY4BYZJcRRn0YyGnufXpt4nbEx7jGdDYP1xtohYhAUEZvIpmmk9qSXQ8cz+
u/bMZ8Pa0RiJ3Y4UcTmJD03Q03BvftRK4crvq4u0lHdqiMsvK9O4DQqzGV5H3yfq
FgXoMFgS2QNKgC6gQKSX
=aAAq
-END PGP SIGNATURE-

___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel panic with Intel i7-2670QM CPU (HP EliteBook 8560w)

[Geoff Simmons]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 02/13/12 06:44 PM, Bryan N Iotti wrote:
 Maybe you could try disabling ACPI in BIOS if possible, or otherwise use
 the acpi-user-options=0x2 at boot.
 
 Read here for more info on disabling ACPI on boot:
 
 https://blogs.oracle.com/danasblog/entry/configuring_solaris_acpi_at_boot

*Thank you* Bryan, acpi-user-options=0x2 got me past the crash and into
the installer.

As the blog entry says, the value 0x2 disables ACPI, and there are other
choices that allow a kind of partial use of ACPI. I'm going ahead with
the installation now, and will investigate the other choices afterward
(and will share the results with the list).

So, given these facts -- crash with the stack trace attached to my
previous mail, workaround by disabling ACPI -- I'm inclined to think
that this warrants a new bug report for Illumos, since I haven't found
anything similar at illumos.org. (Unless someone can point me to a known
issue.)


Thanks again,
Geoff
- -- 
** * * UPLEX - Nils Goroll Systemoptimierung

Schwanenwik 24
22087 Hamburg

Tel +49 40 2880 5731
Mob +49 176 636 90917
Fax +49 40 42949753

http://uplex.de
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (SunOS)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJPOVjoAAoJEOUwvh9pJNURfQwP/2GBgSiyfzrAR0mUkVnc4RVk
18VOPkeOB7dVQIelULb29EcLQYyR8nrru+NeBZVw2PTq3R51rNfvKFqrJaDxyHOy
GlOCNXxfWyt1piT2QaUP6VuPNpvRuAox6j/o6pEwe5nm0bxXs3bGwDZUTKU1sQaI
Ml96mLFb79t8iTNd0QjK/aSy8mOuUbwy6S8QHRgNys6t/xCklIJ+4IepRyxJmBqo
E2c0dCoRy+EO1ZCztAZayWH2bOxNELCIJs+EKPS3jqDkude3GipROUtJTpcA09q9
JuRQavqaLlCqMU6MDgQPJWE9gp+u7vaEuTVtWJv+gfk6hM9TayY3ZFx7pAlSDy5h
W1B5VIa35EmDF+n0laH0ADBf+9DexZEtEdLQIcWBev18b/3BMv8+M8jkZtardJwC
AcePQFAwZJUyqoHc801ctrEQq6PERhzm+8Ts+K3hYbxxAjSQp0X7A64mbQ2qvrZ1
+hFdwd2zlBSkFgxo79PO5dLp684bOQ/luXs6mw6Bdjdmeev3IjzuQjLVWdcLYdeq
6qWCKWv05TZlm7yVlkP8Xgte6nsmus6f0WWHyJ/N/aaMnSx4nSjlVbsuAr1bZ5GM
/9VB+6mTtMGJ8XYyX+yQgva58z3H7iLi8gsRenea5e5xlXetsNmzg6xMIv7KFQqF
CoM0Tt8lNRePjy26D74+
=pzXd
-END PGP SIGNATURE-

___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel panic with Intel i7-2670QM CPU (HP EliteBook 8560w)

[Milan Jurik]

Hi Geoff,

Geoff Simmons píše v po 13. 02. 2012 v 19:39 +0100:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA256
 
 On 02/13/12 06:44 PM, Bryan N Iotti wrote:
  Maybe you could try disabling ACPI in BIOS if possible, or otherwise use
  the acpi-user-options=0x2 at boot.
  
  Read here for more info on disabling ACPI on boot:
  
  https://blogs.oracle.com/danasblog/entry/configuring_solaris_acpi_at_boot
 
 *Thank you* Bryan, acpi-user-options=0x2 got me past the crash and into
 the installer.
 
 As the blog entry says, the value 0x2 disables ACPI, and there are other
 choices that allow a kind of partial use of ACPI. I'm going ahead with
 the installation now, and will investigate the other choices afterward
 (and will share the results with the list).
 
 So, given these facts -- crash with the stack trace attached to my
 previous mail, workaround by disabling ACPI -- I'm inclined to think
 that this warrants a new bug report for Illumos, since I haven't found
 anything similar at illumos.org. (Unless someone can point me to a known
 issue.)
 

the latest development bits (not integrated in OpenIndiana) contains
updated ACPI support. It would be good to test it after successful
installation.

 
 Thanks again,
 Geoff

Best regards,

Milan


___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel panic with Intel i7-2670QM CPU (HP EliteBook 8560w)

[Matt Connolly]

I've experienced the interrupt storm (at that's what I think it is - ever 
increasing kernel cpu usage and slowing down machine) on a new sandy bridge 
Xeon E3.

As far as I'm aware there is a fix for this in the prestable package repo. I 
just updated my publisher to that on my Xeon machine about 2 days ago, and it's 
looking good so far.

Might be worth giving that a try.

-Matt


On 08/02/2012, at 5:00 AM, Lou Picciano wrote:

 Geoff, 
 
 On the face of it, this looks remarkably like the power management and 
 interrupt issues many (including Yours Truly!) are seeing on SandyBridge CPUs 
 (our is an i7-2600K). These problems often manifest as an 'Interrupt Storm'. 
 Check the bug lists for reports - and some suggested workarounds. 
 
 Trying to work through what I think is the next iteration of this problem; 
 that I can reliably crash our build machine with the -j(n) option to gcc. 
 
 More to follow... 
 
 Lou Picciano 
 
 - Original Message -
 From: Geoff Simmons ge...@uplex.de 
 To: openindiana-discuss@openindiana.org 
 Cc: Nils Goroll nils.gor...@uplex.de 
 Sent: Tuesday, February 7, 2012 7:55:22 AM 
 Subject: [OpenIndiana-discuss] Kernel panic with Intel i7-2670QM CPU (HP 
 EliteBook 8560w) 
 
 -BEGIN PGP SIGNED MESSAGE- 
 Hash: SHA256 
 
 Hello all, 
 
 A colleague attempted to boot oi_151a from CD on an HP EliteBook 8560w 
 laptop: 
 
 http://h10010.www1.hp.com/wwpc/us/en/sm/WF06a/321957-321957-64295-3740645-4307559-5071171.html
  
 
 ... the variant with Intel i7-2670QM. He got an immediate kernel panic, 
 and thinks that he saw a message about the CPU before the screen went 
 blank; which leads us to believe that 2670QM may be too new for oi_151a. 
 
 Has anyone else tried booting OpenIndiana with this CPU, or confirm 
 whether or not it can be used? Or are we looking at the wrong 
 explanation for the kernel panic? 
 
 He also tried some other variations of Solaris: 
 
 - - OpenSolaris snv_134 booted from an SSD also led to immediate kernel 
 panic. 
 
 - - Solaris 11 11/11 also got a kernel panic. 
 
 - - Oddly, OpenSolaris snv_111 could be booted, after issuing warnings 
 about a parser error in the cpudrv or cpupm module. But neither ethernet 
 nor wireless were recognized, and the old nvidia driver didn't work 
 (that could be updated). 
 
 
 Thanks, 
 Geoff 
 - -- 
 ** * * UPLEX - Nils Goroll Systemoptimierung 
 
 Schwanenwik 24 
 22087 Hamburg 
 
 Tel +49 40 2880 5731 
 Mob +49 176 636 90917 
 Fax +49 40 42949753 
 
 http://uplex.de 
 -BEGIN PGP SIGNATURE- 
 Version: GnuPG v1.4.10 (SunOS) 
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ 
 
 iQIcBAEBCAAGBQJPMR86AAoJEOUwvh9pJNURxRUP/RfxscL2wmySc4SlE5T2ucju 
 vDRK/NHvkghW3/tTJ48nY2550NNxMxKELS2CZE02xV+Ivqh9w+zIuy/Olob5YkX/ 
 a0+5n/WQoWor9IcZj0baoxcQhMMTgIdohH2I2PPwpQNSeF2uNy1kX9+hh9/+dMBL 
 zXHYXqdWch6WA16YKHX3+SemEzlXkP3B68WqXLfXvh0BDyPGfrgNZJcRoGUg6JJC 
 p6916iBwuHynq1oCziH1o6ywIwOIIWo6vDiszllH3gdlJsP+Q3YcbkLxn4a7y7Q4 
 CBIvvcxpWUeTgPfwgjkOZs0b2V/hm5BAHyUaKqCDSFNG9weNC8xoOiHo35TmQ9NM 
 rdPAmqQbQicAnIOn98b3w1be4ZLppeONPa59sI3+w+Mz+6iMrSkJR0tUwTxT1UMO 
 4PW6BfZD4ffLsszGoRnqWMMGi/9D3EVnmXTvVFI6durXCY+ZMb2LPMl53HIX5tw9 
 EAaHZSUUb3Wj0nf2DcfO2xZZDD08ykLA0mJaebFnKSObY0BukF4Uq47FVnJDDcyP 
 6QrYu1hKv7n4Bf6qjh2mH+8Wu+v0NWWUa8FfjN4FduvYDbQwZLVC1f+CUXFyAm6g 
 i+r0kxyNNhpeAFpZA5j8cKZgPsP2tzVC/QLsmJhIwyw78FJLSoVvPfFTsVEvDIDu 
 6BHl2di/YMYlIsIqInXE 
 =pIlf 
 -END PGP SIGNATURE- 
 
 ___ 
 OpenIndiana-discuss mailing list 
 OpenIndiana-discuss@openindiana.org 
 http://openindiana.org/mailman/listinfo/openindiana-discuss 
 ___
 OpenIndiana-discuss mailing list
 OpenIndiana-discuss@openindiana.org
 http://openindiana.org/mailman/listinfo/openindiana-discuss


___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel panic with Intel i7-2670QM CPU (HP EliteBook 8560w)

[Geoff Simmons]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 02/ 7/12 05:15 PM, Jerry Kemp wrote:
 I have the same issue/problem with my MacBook Pro 17 i7 and also with a 2010
 Mac Mini server.
 
 Solaris runs fine though from my 2007 Mac Mini.
 
 Jerry
 
 
 On 02/ 7/12 07:37 AM, Bryan N Iotti wrote:
 I had a MacBook Pro 17 i7 that would not boot OI, either through rEFIt or 
 MBR emulation.

I doubt that i7 chips in general are the problem, since I find various
reports on Google of OI/Solaris/Illumos running on some kind of i7
processor.

But there are many different kinds. This is the one on the machine that
got us the kernel panic:

http://ark.intel.com/products/53469/Intel-Core-i7-2670QM-Processor-%286M-Cache-2_20-GHz%29

Very new (launched in Q4 2011), and we're guessing that there's
something there that OI and/or Illumos are not ready for, but I don't
know how to investigate it further.


Best,
Geoff
- -- 
** * * UPLEX - Nils Goroll Systemoptimierung

Schwanenwik 24
22087 Hamburg

Tel +49 40 2880 5731
Mob +49 176 636 90917
Fax +49 40 42949753

http://uplex.de
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (SunOS)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJPMV2PAAoJEOUwvh9pJNUR1qkP/RfJzn0YvrLp0ReferdsZXhO
05nTwPICpg/D6XBrrKpbjvNHoxsRlth7Eby9k5BZXKqWBstF/P7LRnRG0PXSeALz
3rcJrCBCJiN56qtkBiXOhFKoYnXwfHdRAxWqSUdJw3bYesiPiFmNCw93ksMOOifq
YnXyx4u+BFdUvk8dd2/IQ6Bm0lpY3GjT1+fIh/1E2gzhFM4aSBPnSlKdlL0AYATK
dqnMKQ2HtojtU4oR11Q+70pfc/OzIUzS9tZ037PkV6MlRum6WANIofS5LDd+z9cN
zUqanBnSPK0zyQgMS/XSzR5xjRfDM320Ja2WlSmunHSn+7Zgwzr7UZhBDs8Di79F
lZ8MZnagUvfrqtQnpPr8b3tnXN6yaKbglOBshFPmqvz/9cv7ti2SCrGMYI3pqSzs
14d4T0VdLiafTWz1IhlNf8coY/l5rtePbWIjyp7fL9a9NcLz1qs81ZtZhgLQNP3D
T4LtZRW1PlVTZoCthteDpRFsgHO6Pc3zRKC7lUTTXUeOfGn5hIuYD4GLAZNJEYrk
DBQTJwGeDnKny7wauMifGSN2otfnhgawTo7MKAe28/IQape2bhqIIkGMePIwrPFY
sUVJi1hc2QQas4a22dzW7dUKbySvs9rAll0oJu5DWsrp2ntfbrW6xn0s0BzYwiS9
oIi2gkFzsjjf0VDf5cAT
=GsOv
-END PGP SIGNATURE-

___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel Panic installing openindiana on a HP BL460c G1

[Johan Guldmyr]

On 06/28/2011 09:32 PM, Gordon Ross wrote:

Here is the ::stack
  http://img220.imageshack.us/i/oi148stack.jpg/

If you look at what the other threads are doing
   ::walk thread | ::findstack -v
I suspect you'll see that ZFS is still trying to import.

I would suggest you dd if=/dev/zero of=/your/disk
with a much larger count.  ZFS tries quite hard to
find a super block, which works against you here:)


Hello!

I tried dd if=/dev/zero of=/dev/rdsk/c1t0d0p0 count=200
but after some two hours I stopped it (ctrl-z).
The 2M I got from going into format, partition p, c1t0d0 - where it says 
that there were 286599600 blocks.


With
::walk thread | ::findstack -v
the console froze after some 25 pages..
This usually happen while I'm in the kernel debugger.
Sometimes it freezes after first 4-5 characters.

--
Johan Guldmyr, Systems Specialist
Storage Platform,
CSC - IT Center for Science,


___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel Panic installing openindiana on a HP BL460c G1

[Michael Schuster]

On Thu, Jun 30, 2011 at 08:01, Johan Guldmyr johan.guld...@csc.fi wrote:
 On 06/28/2011 09:32 PM, Gordon Ross wrote:

 Here is the ::stack
   http://img220.imageshack.us/i/oi148stack.jpg/

 If you look at what the other threads are doing
   ::walk thread | ::findstack -v
 I suspect you'll see that ZFS is still trying to import.

 I would suggest you dd if=/dev/zero of=/your/disk
 with a much larger count.  ZFS tries quite hard to
 find a super block, which works against you here:)

 Hello!

 I tried dd if=/dev/zero of=/dev/rdsk/c1t0d0p0 count=200
 but after some two hours I stopped it (ctrl-z).

with dd, use bs=bignumber to increase the block size dd reads and
writes in one go - as you quote it, dd wrote 512 bytes at a time. A
good value to start with would be 1048576 (1MB).

Also, you may have stopped the command in an unintended way - Ctl-Z
doesn't terminate a command, merely freezes it in its tracks
(technically, pressing Ctrl-Z causes the shell to send SIGSTOP to the
process); you could let it resume at a later time by using either bg
(to have it continue in the background) or fg (... you get the idea
;-).

HTH
Michael

 The 2M I got from going into format, partition p, c1t0d0 - where it says
 that there were 286599600 blocks.

 With
 ::walk thread | ::findstack -v
 the console froze after some 25 pages..
 This usually happen while I'm in the kernel debugger.
 Sometimes it freezes after first 4-5 characters.

 --
 Johan Guldmyr, Systems Specialist
 Storage Platform,
 CSC - IT Center for Science,


 ___
 OpenIndiana-discuss mailing list
 OpenIndiana-discuss@openindiana.org
 http://openindiana.org/mailman/listinfo/openindiana-discuss




-- 
Michael Schuster
http://recursiveramblings.wordpress.com/

___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel Panic installing openindiana on a HP BL460c G1

[Johan Guldmyr]

On 06/30/2011 09:22 AM, Michael Schuster wrote:

with dd, use bs=bignumber to increase the block size dd reads and
writes in one go - as you quote it, dd wrote 512 bytes at a time. A
good value to start with would be 1048576 (1MB).

Also, you may have stopped the command in an unintended way - Ctl-Z
doesn't terminate a command, merely freezes it in its tracks
(technically, pressing Ctrl-Z causes the shell to send SIGSTOP to the
process); you could let it resume at a later time by using either bg
(to have it continue in the background) or fg (... you get the idea
;-).

HTH


Ooh, good to know, thanks Michael.

Did dd again with bs=10478576b count=5
It completed with 250~ records in/out - and it didn't write all the 
blocks it expected to (about half, I didn't save the output).


Still panics though :(

http://img192.imageshack.us/i/oi148stack2.jpg/

::stack is now slightly different.

--
Johan Guldmyr, Systems Specialist
Storage Platform,
CSC - IT Center for Science,


___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel Panic installing openindiana on a HP BL460c G1

[Johan Guldmyr]

On 06/27/2011 04:42 PM, Steve Gonczi wrote:

Hello,

This should be analyzed and root caused.
A ::stack woudl be useful to see the call parameters.

Without disassembling zio_buf_alloc() I can only guess that
the mutex_enter you see crashing is really in kmem_cache_alloc()

If that proves to be the case, I would verify the offset of cc_lock in ccp, to 
see if
ccp was null, or corrupt.

Next step would be a trip to the kmem_cpu _cache related code, to see if
KMEM_CPU_CACHE can return zero or a corrupt value in some cases.

Again, my guess would be this is a NULL pointer dereference,.

Does this system suffer from a severe out of memory condition?

Best Wishes,

Steve



*/ 2486 void * 2487 kmem_cache_alloc ( kmem_cache_t * cp , int kmflag ) 2488 { 2489 
kmem_cpu_cache_t * ccp = KMEM_CPU_CACHE ( cp ); 2490 kmem_magazine_t * fmp ; 2491 void 
* buf ; 2492 2493 mutex_enter (  ccp -  cc_lock );


/sG/

- Original Message -
Now with the pictures, hope this works:

http://imageshack.us/photo/my-images/402/oi151paniccdollarstatus.jpg/
http://img3.imageshack.us/i/oi151panicmsgbuf1.jpg/
http://img5.imageshack.us/i/oi151panicmsgbuf2.jpg/
http://img89.imageshack.us/i/oi151panicmsgbuf3.jpg/
http://img23.imageshack.us/i/oi151panicmsgbuf4.jpg/
http://img16.imageshack.us/i/oi151panicmsgbuf5.jpg/
http://img694.imageshack.us/i/oi151panicmsgbuf6.jpg/


Hi!

If this should be root caused - is there an official page / bug tracker 
where I should file a report?


The blade has 10240MB RAM.
It also has 2x Xeon Quad-Core CPUs, an extra NIC (NC325m) and an extra 
Fibre Channel card (QMH2462).

I ran an HP Quick Diagnostics yesterday which passed.
We could try taking out the FC card (I cannot discern if it's seen in 
the ::msgbuf) but I'd prefer to keep it.
In the shell during install 'fcinfo hba-port -l' gives 'no adapters 
found', but the card is seen in the out of band admin interface.


I have no problem helping out with testing etc (this is a spare blade 
anyway).


Here is the ::stack
http://img220.imageshack.us/i/oi148stack.jpg/

--
Johan Guldmyr, Systems Specialist
Storage Platform,
CSC - IT Center for Science,


___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel Panic installing openindiana on a HP BL460c G1

[Gordon Ross]

On Tue, Jun 28, 2011 at 2:51 AM, Johan Guldmyr johan.guld...@csc.fi wrote:
 On 06/27/2011 04:42 PM, Steve Gonczi wrote:
[...]
 - Original Message -
 Now with the pictures, hope this works:

 http://imageshack.us/photo/my-images/402/oi151paniccdollarstatus.jpg/
 http://img3.imageshack.us/i/oi151panicmsgbuf1.jpg/
 http://img5.imageshack.us/i/oi151panicmsgbuf2.jpg/
 http://img89.imageshack.us/i/oi151panicmsgbuf3.jpg/
 http://img23.imageshack.us/i/oi151panicmsgbuf4.jpg/
 http://img16.imageshack.us/i/oi151panicmsgbuf5.jpg/
 http://img694.imageshack.us/i/oi151panicmsgbuf6.jpg/

 Hi!

 If this should be root caused - is there an official page / bug tracker
 where I should file a report?

 The blade has 10240MB RAM.
 It also has 2x Xeon Quad-Core CPUs, an extra NIC (NC325m) and an extra Fibre
 Channel card (QMH2462).
 I ran an HP Quick Diagnostics yesterday which passed.
 We could try taking out the FC card (I cannot discern if it's seen in the
 ::msgbuf) but I'd prefer to keep it.
 In the shell during install 'fcinfo hba-port -l' gives 'no adapters found',
 but the card is seen in the out of band admin interface.

 I have no problem helping out with testing etc (this is a spare blade
 anyway).

 Here is the ::stack
 http://img220.imageshack.us/i/oi148stack.jpg/

If you look at what the other threads are doing
  ::walk thread | ::findstack -v
I suspect you'll see that ZFS is still trying to import.

I would suggest you dd if=/dev/zero of=/your/disk
with a much larger count.  ZFS tries quite hard to
find a super block, which works against you here:)

Gordon

___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel Panic installing openindiana on a HP BL460c G1

[Mark]

On 27/06/2011 7:11 p.m., Johan Guldmyr wrote:

On 06/27/2011 10:01 AM, Johan Guldmyr wrote:

When I try to install it, it kernel panics at 0%. By adding -k to the
grub line I got the the :msgbuf (attached in .zip file - several .jpg
files), but I don't understand most of it. If anybody could help me shed
some light in this I would appreciate it a lot!


Now with the pictures, hope this works:

http://imageshack.us/photo/my-images/402/oi151paniccdollarstatus.jpg/
http://img3.imageshack.us/i/oi151panicmsgbuf1.jpg/
http://img5.imageshack.us/i/oi151panicmsgbuf2.jpg/
http://img89.imageshack.us/i/oi151panicmsgbuf3.jpg/
http://img23.imageshack.us/i/oi151panicmsgbuf4.jpg/
http://img16.imageshack.us/i/oi151panicmsgbuf5.jpg/
http://img694.imageshack.us/i/oi151panicmsgbuf6.jpg/



Have you tried deleting the solaris partition from the hard disk (via 
format) ?


It can help prevent detection of an existing, broken filesystem.

Mark.

___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel Panic installing openindiana on a HP BL460c G1

[Johan Guldmyr]

On 06/27/2011 10:52 AM, Mark wrote:

Have you tried deleting the solaris partition from the hard disk (via
format) ?

It can help prevent detection of an existing, broken filesystem.

Mark.


Hello Mark,

I deleted the partition via format, created a new one of 50% and then in 
install I chose to install on the 2nd half of the disk. Same panic 
(except that unix:trap+43e changed from value +1799). It however still 
saw the boot menu.
Ran a 'dd if=/dev/zero of=/dev/rdsk/c1t0d0p0 count=1' and same without 
the count (stopped after an hour) and then it stopped instead. Still 
panicked when I tried after that (and then the trap was back to 1799).


Btw, the format option inside 'format' is not supported on this controller.

As seen in the cpqary3 man page: 
http://download.oracle.com/docs/cd/E19253-01/816-5177/6mbbc4g3m/index.html


// Johan

___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel Panic installing openindiana on a HP BL460c G1

[Steve Gonczi]

Hello, 

This should be analyzed and root caused. 
A ::stack woudl be useful to see the call parameters. 

Without disassembling zio_buf_alloc() I can only guess that 
the mutex_enter you see crashing is really in kmem_cache_alloc() 

If that proves to be the case, I would verify the offset of cc_lock in ccp, to 
see if 
ccp was null, or corrupt. 

Next step would be a trip to the kmem_cpu _cache related code, to see if 
KMEM_CPU_CACHE can return zero or a corrupt value in some cases. 

Again, my guess would be this is a NULL pointer dereference,. 

Does this system suffer from a severe out of memory condition? 

Best Wishes, 

Steve 



*/ 2486 void * 2487 kmem_cache_alloc ( kmem_cache_t * cp , int kmflag ) 2488 { 
2489 kmem_cpu_cache_t * ccp = KMEM_CPU_CACHE ( cp ); 2490 kmem_magazine_t * fmp 
; 2491 void * buf ; 2492 2493 mutex_enter ( ccp - cc_lock ); 


/sG/ 

- Original Message -
Now with the pictures, hope this works: 

http://imageshack.us/photo/my-images/402/oi151paniccdollarstatus.jpg/ 
http://img3.imageshack.us/i/oi151panicmsgbuf1.jpg/ 
http://img5.imageshack.us/i/oi151panicmsgbuf2.jpg/ 
http://img89.imageshack.us/i/oi151panicmsgbuf3.jpg/ 
http://img23.imageshack.us/i/oi151panicmsgbuf4.jpg/ 
http://img16.imageshack.us/i/oi151panicmsgbuf5.jpg/ 
http://img694.imageshack.us/i/oi151panicmsgbuf6.jpg/ 
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel panic trying to install OI

[Albert Lee]

On Fri, Oct 22, 2010 at 3:28 AM, russell str...@willows7.myzen.co.uk wrote:
  Hi Thorsten,

 I found that I experienced a similar kernel panic when attempting to perform
 a clean install of OpenIndiana which would occur at around 2% of the
 installation on a consistent basis.

 I eventually worked out that I had to use GParted to delete any partitions
 on the boot disc prior to selecting Install OpenIndiana, the other thing I
 did was not change the hostname until after OpenIndiana has been installed.

 Hope that helps.

 Russell


If one of you can reproduce the panic, can you copy the stack trace in
panic message? I guess it wouldn't have written a crash dump, so you
may have to boot with the '-k' flag appended to the 'kernel' line in
GRUB, and the 'splashimage' line as well as 'console=graphics' removed
(needs both, or the console will still not be visible). That way the
system won't reboot immediately.

This should help us identify the bug.

Thanks,
-Albert

___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel panic after upgrading to OpenIndiana

[Thorsten Heit]

Michael michaelspriv...@gmail.com schrieb am 04.10.2010 12:12:13:

 On Mon, Oct 4, 2010 at 12:05 PM, Thorsten Heit thorsten.h...@vkb.de 
wrote:
  Hi,
 
  It seems very easy to overlook, but it is my understanding that you
  always need to run these steps in a specific order:
  first just run import by itself
 
  pfexec zpool import
  output will list pools available for import
 
  Great, didn't know about that. Thanks :-)
 
 
  Just run import by itself first and all should be well.
 
  Unfortunately not :-(
 
  Booting the OI USB image, the above command gives the following 
output:
 
 
  j...@opensolaris:~$ pfexec zpool import
 
 what happens if you zpool export one of the non-root pools in osol,
 and then run zpool import on OI?

Same result on the exported pool called tank:

j...@opensolaris:~$ pfexec zpool import
  pool: tank
id: 2207250781070144862
 state: UNAVAIL
status: One or more devices contains corrupted data.
action: The pool cannot be imported due to damaged devices or data.
   see: http://www.sun.com/msg/ZFS-8000-5E
config:

tankUNAVAIL  insufficient replicas
  c4t5d0UNAVAIL  corrupted data


etc.



Regards

Thorsten

___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel panic after upgrading to OpenIndiana

[Thorsten Heit]

Hi,

 It seems very easy to overlook, but it is my understanding that you 
 always need to run these steps in a specific order:
 first just run import by itself
 
 pfexec zpool import
 output will list pools available for import

Great, didn't know about that. Thanks :-)


 Just run import by itself first and all should be well.

Unfortunately not :-(

Booting the OI USB image, the above command gives the following output:


j...@opensolaris:~$ pfexec zpool import
  pool: tank
id: 2207250781070144862
 state: UNAVAIL
status: The pool was last accessed by another system.
action: The pool cannot be imported due to damaged devices or data.
   see: http://www.sun.com/msg/ZFS-8000-EY
config:

tankUNAVAIL  insufficient replicas
  c4t5d0UNAVAIL  corrupted data

  pool: daten
id: 15698494553963200979
 state: UNAVAIL
status: The pool was last accessed by another system.
action: The pool cannot be imported due to damaged devices or data.
   see: http://www.sun.com/msg/ZFS-8000-EY
config:

daten   UNAVAIL  insufficient replicas
  raidz1-0  UNAVAIL  corrupted data
c4t1d0  ONLINE
c4t2d0  ONLINE
c4t3d0  ONLINE

  pool: rpool
id: 10396893521170277275
 state: UNAVAIL
status: The pool was last accessed by another system.
action: The pool cannot be imported due to damaged devices or data.
   see: http://www.sun.com/msg/ZFS-8000-EY
config:

rpool UNAVAIL  insufficient replicas
  mirror-0UNAVAIL  corrupted data
c4t0d0s0  ONLINE
c4t4d0s0  ONLINE
j...@opensolaris:~$ pfexec zpool import -f tank
cannot import 'tank': invalid vdev configuration
j...@opensolaris:~$ 


Directly rebooted in OSOLb134 USB image, executed the same command, and as 
expected the output is different and without any errors:

j...@opensolaris:~$ pfexec zpool import
  pool: tank
id: 2207250781070144862
 state: ONLINE
status: The pool was last accessed by another system.
action: The pool can be imported using its name or numeric identifier and
the '-f' flag.
   see: http://www.sun.com/msg/ZFS-8000-EY
config:

tankONLINE
  c4t5d0ONLINE

  pool: daten
id: 15698494553963200979
 state: ONLINE
status: The pool was last accessed by another system.
action: The pool can be imported using its name or numeric identifier and
the '-f' flag.
   see: http://www.sun.com/msg/ZFS-8000-EY
config:

daten   ONLINE
  raidz1-0  ONLINE
c4t1d0  ONLINE
c4t2d0  ONLINE
c4t3d0  ONLINE

  pool: rpool
id: 10396893521170277275
 state: ONLINE
status: The pool was last accessed by another system.
action: The pool can be imported using its name or numeric identifier and
the '-f' flag.
   see: http://www.sun.com/msg/ZFS-8000-EY
config:

rpool ONLINE
  mirror-0ONLINE
c4t0d0s0  ONLINE
c4t4d0s0  ONLINE
j...@opensolaris:~$ 


Why does OI think _all_ of my pools are corrupt whereas OSOL doesn't?


Regards

Thorsten

___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel panic after upgrading to OpenIndiana

[Michael]

On Mon, Oct 4, 2010 at 12:05 PM, Thorsten Heit thorsten.h...@vkb.de wrote:
 Hi,

 It seems very easy to overlook, but it is my understanding that you
 always need to run these steps in a specific order:
 first just run import by itself

 pfexec zpool import
     output will list pools available for import

 Great, didn't know about that. Thanks :-)


 Just run import by itself first and all should be well.

 Unfortunately not :-(

 Booting the OI USB image, the above command gives the following output:


 j...@opensolaris:~$ pfexec zpool import

what happens if you zpool export one of the non-root pools in osol,
and then run zpool import on OI?

Michael
-- 
regards/mfg
Michael Schuster

___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel panic after upgrading to OpenIndiana

[Thorsten Heit]

Hi,

 This appears very similar to another issue with the bootfs
 specification which is normally transparent:
 http://opensolaris.org/jive/thread.jspa?messageID=315743
 
 Also make sure you have the current version of GRUB installed on
 *both* disks in your mirror, as it's responsible for specifying the
 bootfs parameter.

This was already done after attaching the second disc to rpool.

I just booted into the live USB image to check whether my system is at all 
capable of booting into OI. Works as expected, but I'm not able to import 
the zpools:

j...@opensolaris:~$ pfexec zpool import -f rpool
cannot import 'rpool': invalid vdev configuration
j...@opensolaris:~$


Erm, what does this message wants to tell me?
Why does this happen only when booting the USB image of OI and not the one 
of OSOL b134?


Regards

Thorsten

___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel panic after upgrading to OpenIndiana

[Chris Mosetick]

Sorry you are having trouble.  Just a couple probing questions to open up
everyones mind.  Before I forget, make sure you have burned a OS b134 live
cd and a OI b147 live dvd before you do anything.

The first thing I would try is booting into your b134 BE.  Then export all
the pools besides rpool.

zpool export tank
zpool export dataen

Then try the OI b147 boot environment again.  Does it boot now??

If boot = yes, try:

zpool import  (you have to run this first)
zpool import tank
zpool import daten
Do you get a kernel panic upon one of the imports??  there is your problem

Or another kernel panic upon OI b147 boot with data pools exported?  Maybe
the rpool version is too old for OI b147 to work with??

The next thing I would try:

I would leave the data pools exported until you get everything sorted out
with the boot issues.

Boot into your b134 boot environment.  Run:  zpool get version rpool and zfs
get version rpool/ROOT

It's possible that you might need to update your rpool to a certain pool
version in order to boot OI properly.  I imagine that you have been running
this machine for a while, and probably did not start out with b134.  FWIW,
all of the (mostly test) machines that I have upgraded from OS b134 running
zpool version 22 zfs version 4 to OI b147 have all booted up fine the first
time after the operating system upgrade.

If you are running a really old pool version on your rpool, say 14 or
something like that, you might try booting into your b134 boot environment
and upgrading it to the highest pool version b134 can use, pool version 22,
zfs version 4.

zpool upgrade -V 22 rpool
zfs upgrade -V 4 rpool/ROOT
zfs upgrade -V 4 rpool/opensolaris
basically anything in the rpool

Running the commands above will make boot environments before 134 obsolete,
so a warning is in order.  Seeing as that you are trying to move forward,
rather than keep compatibility with older BE's it's worth a shot to make
sure your rpool is running something that OI can see.


-Chris


On Wed, Sep 29, 2010 at 2:40 AM, thorsten.h...@vkb.de wrote:

 Hi,

 by following the instructions on the wiki I just upgraded from OpenSolaris
 b134 to OpenIndiana. Unfortunately booting into the new BE results in a
 kernel panic:

 ...
 NOTICE: zfs_parse_bootfs: error 22
 Cannot mount root on rpool/101 fstype zfs

 panic[cpu0]/thread=fbc2f260: vs_mountroot: cannot mount root

 Warning - stack not written to the dump buffer
 fbc718e0 genunix:vfs_mountroot+33e ()
 fbc71910 genunix:main+136 ()
 fbc71920 unix:_locore_start+90 ()

 panic: entering debugger (no dump device, continue to reboot)

 Welcome to kmdb
 Loaded modules: [ scsi_vhci mac uppc sd unix zfs krtld apix genunix specfs
 pcplusmp cpu.generic ]
 [0]


 My machine is a HP ProLiant ML350 G5 with 2 quad-core Xeons, 32GB RAM and
 a HP SmartArray E200i RAID controller with 3x160 and 3x500GB SATA discs
 connected to it. Two of the 160GB discs build the mirrored root pool
 (rpool), the third serves as a temporary data pool called tank, and the
 three 500G discs form a RAIDZ1 pool called daten.

 What is causing this kernel panic?
 I tried to recreate/upgrade the boot archive for the OpenIndiana BE, but
 that didn't help...


 Regards

 Thorsten

 ___
 OpenIndiana-discuss mailing list
 OpenIndiana-discuss@openindiana.org
 http://openindiana.org/mailman/listinfo/openindiana-discuss

___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel panic after upgrading to OpenIndiana

[Thorsten Heit]

Hi,

 Sorry you are having trouble.  Just a couple probing questions to open 
up
 everyones mind.  Before I forget, make sure you have burned a OS b134 
live
 cd and a OI b147 live dvd before you do anything.
 
 The first thing I would try is booting into your b134 BE.  Then export 
all
 the pools besides rpool.
 
 zpool export tank
 zpool export dataen
 
 Then try the OI b147 boot environment again.  Does it boot now??

Nope.
I actually even reinstalled OI, but that didn't change anything.
There's only a slight difference in the message after the NOTICE: line:

Cannot mount root on rpool/95 fstype zfs

(instead of ...rpool/101...)
(btw: does this make any difference?)

 Or another kernel panic upon OI b147 boot with data pools exported? 
Maybe
 the rpool version is too old for OI b147 to work with??

Again: No.
The whole machine was recently reinstalled with OSOL b134 after I switched 
from hardware RAID support to ZFS-based software RAID on the boot discs, 
i.e. ZFS is version 4 and zpool version 22.

Do you have any other idea?


Greetings

Thorsten

___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel panic after upgrading to OpenIndiana

[Michael]

 I actually even reinstalled OI, but that didn't change anything.
 There's only a slight difference in the message after the NOTICE: line:

 Cannot mount root on rpool/95 fstype zfs

can you show the output of zfs list -tall as run from a different BE
(at least the relevant parts)? Maybe you can show what a bootable BE
thinks is at that mountpoint/in that FS ... if the stuff in there
isn't immediately relevant, perhaps you can set its mountpoint to
none (I think) to avoid automatic mounting at boot ...

HTH
Michael
-- 
regards/mfg
Michael Schuster

___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Kernel panic after upgrading to OpenIndiana

[Albert Lee]

This appears very similar to another issue with the bootfs
specification which is normally transparent:
http://opensolaris.org/jive/thread.jspa?messageID=315743

Also make sure you have the current version of GRUB installed on
*both* disks in your mirror, as it's responsible for specifying the
bootfs parameter.

-Albert

___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss