Geoffrey Kransdorf
2007-Oct-25 04:50 UTC
snv_b75a crash on starting X - intel driver issue?
I installed snv_b75a this week. It works great in regular mode but when I boot to Xvm from GRUB it panics while starting up the X login screen (CDM, not the new gdm one). X seems to start up ok (I get as far as the hourglass), but never gets to the login screen. /var/adm/messages reports: ^Mpanic[cpu0]/thread=d5af3600 I''m not sure which other logs or info would be useful. The system is an Intel P4 (F41 family 15 model 4 step 1 clock 3Ghz) with an Intel 915G video card. In regular mode X is accelerated and I can run Compiz and GL applications with no problems. Any suggestions? This message posted from opensolaris.org
michael schuster
2007-Oct-25 05:02 UTC
Re: snv_b75a crash on starting X - intel driver issue?
Geoffrey Kransdorf wrote:> I installed snv_b75a this week. It works great in regular mode butwhat you call "regular mode", we normally refer to as "(running) on metal" or "bare metal" :-)> when I boot to Xvm from GRUB it panics while starting up the X login > screen (CDM, not the new gdm one). X seems to start up ok (I get as > far as the hourglass), but never gets to the login screen. > > /var/adm/messages reports:> ^Mpanic[cpu0]/thread=d5af3600 we''d need what comes after that, probably until the next occurrence of the boot message: ^MSunOS Release 5.11 Version ... next, run dumpadm (as root) and look for "Savecore directory:" - the directory you''ll most likely find there is "/var/crash/<hostname>", and in that directory, you should find unix.N and vmcore.N (N: 0, 1, ...). gzip vmcore.N and put it up somewhere ftp''able. HTH Michael -- Michael Schuster Sun Microsystems, Inc. recursion, n: see ''recursion''
James Cornell
2007-Oct-25 05:30 UTC
Re: snv_b75a crash on starting X - intel driver issue?
Geoffrey Kransdorf wrote:> I installed snv_b75a this week. It works great in regular mode but when I boot to Xvm from GRUB it panics while starting up the X login screen (CDM, not the new gdm one). X seems to start up ok (I get as far as the hourglass), but never gets to the login screen. > > /var/adm/messages reports: > ^Mpanic[cpu0]/thread=d5af3600 > > I''m not sure which other logs or info would be useful. The system is an Intel P4 (F41 family 15 model 4 step 1 clock 3Ghz) with an Intel 915G video card. In regular mode X is accelerated and I can run Compiz and GL applications with no problems. > > Any suggestions? > > > This message posted from opensolaris.org > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org >Compiz on OpenSolaris. No wai. Does the CPU have HT? If it does, disable it temporarily, and see if it stops crashing. (I suspect APIC bugs) James
Hi, I have the same issue with a macbook, which also has an intel video controller with shared memory, probably this is the same issue. michael schuster wrote:> Geoffrey Kransdorf wrote: >> I installed snv_b75a this week. It works great in regular mode but > > what you call "regular mode", we normally refer to as "(running) on > metal" or "bare metal" :-) > >> when I boot to Xvm from GRUB it panics while starting up the X login >> screen (CDM, not the new gdm one). X seems to start up ok (I get as >> far as the hourglass), but never gets to the login screen. >> >> /var/adm/messages reports: > > ^Mpanic[cpu0]/thread=d5af3600 > > we''d need what comes after that, probably until the next occurrence of > the boot message: > > ^MSunOS Release 5.11 Version ... > > next, run dumpadm (as root) and look for "Savecore directory:" - the > directory you''ll most likely find there is "/var/crash/<hostname>", and > in that directory, you should find unix.N and vmcore.N (N: 0, 1, ...). > > gzip vmcore.N and put it up somewhere ftp''able. > > HTH > Michael-- /\ \\ \ \ \\ / Peter Boros / \/ / / Technical Specialist / / \//\ \//\ / / Sun Microsystems, Inc. / / /\ / Hungary / \\ \ Phone +36 1 4898910 \ \\ Mobile +36 70 5296200 \/
James Cornell
2007-Oct-25 06:48 UTC
Re: snv_b75a crash on starting X - intel driver issue?
Peter Boros wrote:> Hi, > > I have the same issue with a macbook, which also has an intel video > controller with shared memory, probably this is the same issue. > > michael schuster wrote: > >> Geoffrey Kransdorf wrote: >> >>> I installed snv_b75a this week. It works great in regular mode but >>> >> what you call "regular mode", we normally refer to as "(running) on >> metal" or "bare metal" :-) >> >> >>> when I boot to Xvm from GRUB it panics while starting up the X login >>> screen (CDM, not the new gdm one). X seems to start up ok (I get as >>> far as the hourglass), but never gets to the login screen. >>> >>> /var/adm/messages reports: >>> >> > ^Mpanic[cpu0]/thread=d5af3600 >> >> we''d need what comes after that, probably until the next occurrence of >> the boot message: >> >> ^MSunOS Release 5.11 Version ... >> >> next, run dumpadm (as root) and look for "Savecore directory:" - the >> directory you''ll most likely find there is "/var/crash/<hostname>", and >> in that directory, you should find unix.N and vmcore.N (N: 0, 1, ...). >> >> gzip vmcore.N and put it up somewhere ftp''able. >> >> HTH >> Michael >> > >Peter, how did you go about getting OpenSolaris on your MacBook? Did you use this from Paul Mitchell? http://blogs.sun.com/paulm/entry/dual_partitioning_a_macbook_pro I have a MacBook Pro (rev 3) with NVIDIA Geforce 8600 GT. If it works on mine, I''m positive it''s the GPU on yours. They use the same CPU, same disks, same OS, same memory depending on slight configuration changes. (Fast disks, etc) Is your chipset the Intel 965? James
Geoffrey Kransdorf
2007-Oct-25 07:01 UTC
Re: snv_b75a crash on starting X - intel driver issue?
Thanks very much for the reply. I uploaded the vmcore and complete messages file to http://rapidshare.com/files/65015405/vmcore.tar.html Sorry for Rapidshare, but my companies network is heavily firewalled and I can''t ftp it out directly. Hope this helps. Thanks again! Geoff This message posted from opensolaris.org
Hi, No, the macbook uses an other chipset (this was used in the previous generation of macbook pros intel 945 I think, the video controller is Intel GMA 950), so the 2 chipsets are not the same. I didn''t used refit or anything, it is not OS X - Solaris dual boot, now only Solaris is installed (of course, later I will set up the dual-boot environment, but I think the problem is not with that right now). James Cornell wrote:> Peter Boros wrote: >> Hi, >> >> I have the same issue with a macbook, which also has an intel video >> controller with shared memory, probably this is the same issue. >> >> michael schuster wrote: >> >>> Geoffrey Kransdorf wrote: >>> >>>> I installed snv_b75a this week. It works great in regular mode but >>>> >>> what you call "regular mode", we normally refer to as "(running) on >>> metal" or "bare metal" :-) >>> >>> >>>> when I boot to Xvm from GRUB it panics while starting up the X login >>>> screen (CDM, not the new gdm one). X seems to start up ok (I get as >>>> far as the hourglass), but never gets to the login screen. >>>> >>>> /var/adm/messages reports: >>>> >>> > ^Mpanic[cpu0]/thread=d5af3600 >>> >>> we''d need what comes after that, probably until the next occurrence of >>> the boot message: >>> >>> ^MSunOS Release 5.11 Version ... >>> >>> next, run dumpadm (as root) and look for "Savecore directory:" - the >>> directory you''ll most likely find there is "/var/crash/<hostname>", and >>> in that directory, you should find unix.N and vmcore.N (N: 0, 1, ...). >>> >>> gzip vmcore.N and put it up somewhere ftp''able. >>> >>> HTH >>> Michael >>> >> > Peter, how did you go about getting OpenSolaris on your MacBook? > > Did you use this from Paul Mitchell? > http://blogs.sun.com/paulm/entry/dual_partitioning_a_macbook_pro > > I have a MacBook Pro (rev 3) with NVIDIA Geforce 8600 GT. If it works > on mine, I''m positive it''s the GPU on yours. They use the same CPU, > same disks, same OS, same memory depending on slight configuration > changes. (Fast disks, etc) Is your chipset the Intel 965? > > James-- /\ \\ \ \ \\ / Peter Boros / \/ / / Technical Specialist / / \//\ \//\ / / Sun Microsystems, Inc. / / /\ / Hungary / \\ \ Phone +36 1 4898910 \ \\ Mobile +36 70 5296200 \/
James Cornell
2007-Oct-25 07:40 UTC
Re: snv_b75a crash on starting X - intel driver issue?
Peter Boros wrote:> Hi, > > No, the macbook uses an other chipset (this was used in the previous > generation of macbook pros intel 945 I think, the video controller is > Intel GMA 950), so the 2 chipsets are not the same. I didn''t used > refit or anything, it is not OS X - Solaris dual boot, now only > Solaris is installed (of course, later I will set up the dual-boot > environment, but I think the problem is not with that right now). > > James Cornell wrote: >> Peter Boros wrote: >>> Hi, >>> >>> I have the same issue with a macbook, which also has an intel video >>> controller with shared memory, probably this is the same issue. >>> >>> michael schuster wrote: >>> >>>> Geoffrey Kransdorf wrote: >>>> >>>>> I installed snv_b75a this week. It works great in regular mode but >>>>> >>>> what you call "regular mode", we normally refer to as "(running) on >>>> metal" or "bare metal" :-) >>>> >>>> >>>>> when I boot to Xvm from GRUB it panics while starting up the X login >>>>> screen (CDM, not the new gdm one). X seems to start up ok (I get as >>>>> far as the hourglass), but never gets to the login screen. >>>>> >>>>> /var/adm/messages reports: >>>>> >>>> > ^Mpanic[cpu0]/thread=d5af3600 >>>> >>>> we''d need what comes after that, probably until the next occurrence >>>> of the boot message: >>>> >>>> ^MSunOS Release 5.11 Version ... >>>> >>>> next, run dumpadm (as root) and look for "Savecore directory:" - >>>> the directory you''ll most likely find there is >>>> "/var/crash/<hostname>", and in that directory, you should find >>>> unix.N and vmcore.N (N: 0, 1, ...). >>>> >>>> gzip vmcore.N and put it up somewhere ftp''able. >>>> >>>> HTH >>>> Michael >>>> >>> >> Peter, how did you go about getting OpenSolaris on your MacBook? >> >> Did you use this from Paul Mitchell? >> http://blogs.sun.com/paulm/entry/dual_partitioning_a_macbook_pro >> >> I have a MacBook Pro (rev 3) with NVIDIA Geforce 8600 GT. If it works >> on mine, I''m positive it''s the GPU on yours. They use the same CPU, >> same disks, same OS, same memory depending on slight configuration >> changes. (Fast disks, etc) Is your chipset the Intel 965? >> >> James >Okay. I upgraded from a first gen MacBook Pro to a rev 3 because of the NVIDIA graphics, pre-N out of the box, and Santa Rosa. You''re right, 945 was it. James
Peter Boros wrote:> Hi, > > No, the macbook uses an other chipset (this was used in the previous > generation of macbook pros intel 945 I think, the video controller is > Intel GMA 950), so the 2 chipsets are not the same. I didn''t used refit > or anything, it is not OS X - Solaris dual boot, now only Solaris is > installed (of course, later I will set up the dual-boot environment, but > I think the problem is not with that right now).It sounds like we have a bug with the graphics driver for the Intel GMA 950 on xVM.. Can you file a bug? MRJ> James Cornell wrote: >> Peter Boros wrote: >>> Hi, >>> >>> I have the same issue with a macbook, which also has an intel video >>> controller with shared memory, probably this is the same issue. >>> >>> michael schuster wrote: >>> >>>> Geoffrey Kransdorf wrote: >>>> >>>>> I installed snv_b75a this week. It works great in regular mode but >>>>> >>>> what you call "regular mode", we normally refer to as "(running) on >>>> metal" or "bare metal" :-) >>>> >>>> >>>>> when I boot to Xvm from GRUB it panics while starting up the X login >>>>> screen (CDM, not the new gdm one). X seems to start up ok (I get as >>>>> far as the hourglass), but never gets to the login screen. >>>>> >>>>> /var/adm/messages reports: >>>>> >>>> > ^Mpanic[cpu0]/thread=d5af3600 >>>> >>>> we''d need what comes after that, probably until the next occurrence of >>>> the boot message: >>>> >>>> ^MSunOS Release 5.11 Version ... >>>> >>>> next, run dumpadm (as root) and look for "Savecore directory:" - the >>>> directory you''ll most likely find there is "/var/crash/<hostname>", and >>>> in that directory, you should find unix.N and vmcore.N (N: 0, 1, ...). >>>> >>>> gzip vmcore.N and put it up somewhere ftp''able. >>>> >>>> HTH >>>> Michael >>>> >>> >> Peter, how did you go about getting OpenSolaris on your MacBook? >> >> Did you use this from Paul Mitchell? >> http://blogs.sun.com/paulm/entry/dual_partitioning_a_macbook_pro >> >> I have a MacBook Pro (rev 3) with NVIDIA Geforce 8600 GT. If it works >> on mine, I''m positive it''s the GPU on yours. They use the same CPU, >> same disks, same OS, same memory depending on slight configuration >> changes. (Fast disks, etc) Is your chipset the Intel 965? >> >> James >-- Mark Johnson <mark.johnson@sun.com> Sun Microsystems, Inc. (781) 442-0869
Would another core be of any use? I seem to be experiencing the same problem I''m on build 76. I could boot successfully with graphical login disabled but as soon as I did: root@frank / $ svcadm enable cde-login:default the system would panic I''ve just put an ancient pci card in and I seem to be able to renable cde-login without a panic what I think might be relevant: /var/adm/messages Nov 13 15:45:48 frank ^Mpanic[cpu1]/thread=ffffff018e446ea0: Nov 13 15:45:48 frank genunix: [ID 335743 kern.notice] BAD TRAP: type=e (#pf Page fault) rp=fffffffffbc7aa10 addr=a8 occurred in module "genunix" due to a NULL po inter dereference Nov 13 15:45:48 frank unix: [ID 100000 kern.notice] Nov 13 15:45:48 frank genunix: [ID 111219 kern.notice] dumping to /dev/dsk/c0d1s1 , offset 431030272, content: kernel Nov 13 15:45:53 frank genunix: [ID 409368 kern.notice] ^M100% done: 75706 pages d umped, compression ratio 3.88, Nov 13 15:45:53 frank genunix: [ID 851671 kern.notice] dump succeeded Nov 13 15:46:30 frank genunix: [ID 540533 kern.notice] ^MSunOS Release 5.11 Versi on snv_76 64-bit This message posted from opensolaris.org
James Legg wrote:> Would another core be of any use? I seem to be experiencing the same problem I''m on build 76. > > I could boot successfully with graphical login disabled but as soon as I did: > > root@frank / $ svcadm enable cde-login:default > > the system would panic > > I''ve just put an ancient pci card in and I seem to be able to renable cde-login without a panicWhat kind of graphics controller do you have? What does the panic stack look like? Thanks, MRJ> what I think might be relevant: > /var/adm/messages > > Nov 13 15:45:48 frank ^Mpanic[cpu1]/thread=ffffff018e446ea0: > Nov 13 15:45:48 frank genunix: [ID 335743 kern.notice] BAD TRAP: type=e (#pf Page > fault) rp=fffffffffbc7aa10 addr=a8 occurred in module "genunix" due to a NULL po > inter dereference > Nov 13 15:45:48 frank unix: [ID 100000 kern.notice] > Nov 13 15:45:48 frank genunix: [ID 111219 kern.notice] dumping to /dev/dsk/c0d1s1 > , offset 431030272, content: kernel > Nov 13 15:45:53 frank genunix: [ID 409368 kern.notice] ^M100% done: 75706 pages d > umped, compression ratio 3.88, > Nov 13 15:45:53 frank genunix: [ID 851671 kern.notice] dump succeeded > Nov 13 15:46:30 frank genunix: [ID 540533 kern.notice] ^MSunOS Release 5.11 Versi > on snv_76 64-bit > > > This message posted from opensolaris.org > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
Duncan Groenewald
2007-Nov-14 08:49 UTC
Re: snv_b75a crash on starting X - intel driver issue?
I installed snv_76 on my MacBook (intel graphics) and have the same problem. System crashes and reboots when graphical login starts up when booting using xVM. Otherwise its fine. I just installed snv_76 directly from DVD to the internal harddrive (had to seperately install network drivers though). No OS X or Boot Manager or anything else. This message posted from opensolaris.org
James Cornell
2007-Nov-14 09:40 UTC
Re: snv_b75a crash on starting X - intel driver issue?
Well obviously there''s no Boot Manager. You can keep OS X by using an
external hard drive, formatting it as GUID and installing Mac OS X
directly to it, using diskutil to recopy it from the installation
DVD. You''d need to temporarily hose the EFI partition by changing the
id to something like HFS+ without formatting or using it, then change
it back from the installation DVD to type EE. You''d be using Boot
Camp assistant to create a Windows partition, which becomes the
Solaris root slice.
You''d notice that even just changing the id of the EFI partition,
would hose the partition, which is needed for EFI updates, a sort of
buffer zone. I suspect it''s a matter of fdisk and EFI gpt not
synchronizing back once it''s changed, and the GUID value changes, so
it can''t find it, which means maybe even dd wouldn''t work.
Using
parted you''ll have more success in restoring it since it does
synchronize both and theoretically with the correct options the GUID
also.
To switch between, you''d use rEFIt or manually load the installation
DVD and Startup Disk. Solaris'' partition will not boot if
it''s not
using MS-DOS type created with diskutil or if you''re not using rEFIt,
because Solaris will retain the Windows label even as Solaris2 type as
EFI holds that extra information and it doesn''t affect Solaris. All
Solaris really needs is to be located about 128MB after the Mac OS X
partition so the hardware EFI loader can boot strap legacy mode.
There''s full coverage at:
http://blogs.sun.com/paulm/entry/dual_partitioning_a_macbook_pro
http://blogs.sun.com/alanp/entry/setting_up_a_mac_mini
Stock Leopard, using whole disk -
/dev/disk0
#: TYPE NAME SIZE
IDENTIFIER
0: GUID_partition_scheme *149.1 Gi
disk0
1: EFI 200.0 Mi
disk0s1
2: Apple_HFS Xray 148.7 Gi
disk0s2
Disk: /dev/disk0 geometry: 19457/255/63 [312581808 sectors]
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: EE 1023 254 63 - 1023 254 63 [ 1 - 312581807] <Unknown
ID>
2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
Stock boot camp, split in two -
/dev/disk0
#: TYPE NAME SIZE
IDENTIFIER
0: GUID_partition_scheme *149.1 Gi
disk0
1: EFI 200.0 Mi
disk0s1
2: Apple_HFS Xray 73.9 Gi
disk0s2
3: Microsoft Basic Data BOOTCAMP 74.8 Gi
disk0s3
Disk: /dev/disk0 geometry: 19457/255/63 [312581808 sectors]
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: EE 1023 254 63 - 1023 254 63 [ 1 - 409639] <Unknown
ID>
2: AF 1023 254 63 - 1023 254 63 [ 409640 - 154927104] HFS+
3: 0B 1023 254 63 - 1023 254 63 [ 155598888 - 156982880] Win95
FAT-32
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
I''m using a MacBook Pro so I don''t have those cruddy Intel
graphics or
glitches, although the chipsets and hardware is very similar, just
higher grade. I don''t have any problems dual booting with
Paul''s
guide. I suspect that in xwin_78 or xwin_79 your Intel GMA950
glitches may be fixed.
James
On Nov 14, 2007, at 12:49 AM, Duncan Groenewald wrote:
> I installed snv_76 on my MacBook (intel graphics) and have the same
> problem. System crashes and reboots when graphical login starts up
> when booting using xVM. Otherwise its fine.
>
> I just installed snv_76 directly from DVD to the internal harddrive
> (had to seperately install network drivers though). No OS X or Boot
> Manager or anything else.
>
>
> This message posted from opensolaris.org
> _______________________________________________
> xen-discuss mailing list
> xen-discuss@opensolaris.org
Burt wrote:> GPU is Intel Graphics Media Accelerator 950 > > This is what I get on the serial console is this what your after? >Yes, thanks.. This is 6624364 xVM Hypervisor panic on systems with intel embedded graphics http://bugs.opensolaris.org/view_bug.do?bug_id=6624364 I haven''t gotten a hold of a system with an intel graphics chip and a serial port yet, so I can debug it. MRJ> root@frank / $ svcadm enable > svc:/application/graphical-login/cde-login:default > root@frank / $ > > ***************************************************************************** > > * > * Starting Desktop Login on display :0... > * > * Wait for the Desktop Login screen before logging in. > * > ***************************************************************************** > > Nov 13 17:46:34 frank unix: NOTICE: IRQ18 is shared > Nov 13 17:46:37 frank unix: NOTICE: IRQ16 is shared > > panic[cpu1]/thread=ffffff018f1bf400: BAD TRAP: type=e (#pf Page fault) > rp=ffffff00065d4c10 addr=ffffff018f973fbc > > syslogd: #pf Page fault > Bad kernel fault at addr=0xffffff018f973fbc > pid=478, pc=0xfffffffff7838966, sp=0xffffff00065d4d00, eflags=0x10282 > cr0: 8005003b<pg,wp,ne,et,ts,mp,pe> cr4: 2620<vmxe,xmme,fxsr,pae> > cr2: ffffff018f973fbc > rdi: ffffff01873dfdf0 rsi: ffffff00065d4d98 rdx: ffffff018f1bf400 > rcx: 0 r8: ffffff018f54d690 r9: ffffff018e2e4078 > rax: 0 rbx: ffffff018f973fa8 rbp: ffffff00065d4d50 > r10: ffffff018f54d780 r11: ffffff018f1bf400 r12: ffffff01873dfd00 > r13: ffffff01873dfdf0 r14: ffffff00065d4d98 r15: ffffff018f54d8c0 > fsb: 0 gsb: ffffff0187885b00 ds: 4b > es: 4b fs: 0 gs: 1c3 > trp: e err: 0 rip: fffffffff7838966 > cs: e030 rfl: 10282 rsp: ffffff00065d4d00 > ss: e02b > > ffffff00065d4af0 unix:die+ea () > ffffff00065d4c00 unix:trap+13b3 () > ffffff00065d4c10 unix:_cmntrap+12f () > ffffff00065d4d50 ufs:logmap_free_cancel+156 () > ffffff00065d4dd0 ufs:top_end_sync+15d () > ffffff00065d4e40 ufs:ufs_fsync+1cb () > ffffff00065d4e90 genunix:fop_fsync+51 () > ffffff00065d4ec0 genunix:fdsync+35 () > ffffff00065d4f10 unix:brand_sys_syscall32+1d0 () > > syncing file systems... > panic[cpu1]/thread=ffffff018f1bf400: BAD TRAP: type=e (#pf Page fault) > rp=fffffffffbc7aa70 addr=0 occurred in module "unix" due to a NULL > pointer dereference > dumping to /dev/dsk/c0d1s1, offset 431030272, content: kernel > > panic[cpu1]/thread=ffffff018f1bf400: BAD TRAP: type=e (#pf Page fault) > rp=fffffffffbc79f40 addr=ffffff018f81754b > dump aborted: please record the above information! > rebooting... > (XEN) Domain 0 shutdown: rebooting machine. > > > > > > > On 13 Nov 2007, at 17:26, Mark Johnson wrote: > >> >> >> James Legg wrote: >>> Would another core be of any use? I seem to be experiencing the same >>> problem I''m on build 76. >>> >>> I could boot successfully with graphical login disabled but as soon >>> as I did: >>> root@frank / $ svcadm enable cde-login:default >>> the system would panic >>> I''ve just put an ancient pci card in and I seem to be able to renable >>> cde-login without a panic >> >> What kind of graphics controller do you have? What does >> the panic stack look like? >> >> >> >> Thanks, >> >> >> MRJ >> >>> what I think might be relevant: >>> /var/adm/messages Nov 13 15:45:48 frank >>> ^Mpanic[cpu1]/thread=ffffff018e446ea0: Nov 13 15:45:48 frank genunix: >>> [ID 335743 kern.notice] BAD TRAP: type=e (#pf Page >>> fault) rp=fffffffffbc7aa10 addr=a8 occurred in module "genunix" due >>> to a NULL po >>> inter dereference >>> Nov 13 15:45:48 frank unix: [ID 100000 kern.notice] Nov 13 15:45:48 >>> frank genunix: [ID 111219 kern.notice] dumping to /dev/dsk/c0d1s1 >>> , offset 431030272, content: kernel >>> Nov 13 15:45:53 frank genunix: [ID 409368 kern.notice] ^M100% done: >>> 75706 pages d >>> umped, compression ratio 3.88, Nov 13 15:45:53 frank genunix: [ID >>> 851671 kern.notice] dump succeeded >>> Nov 13 15:46:30 frank genunix: [ID 540533 kern.notice] ^MSunOS >>> Release 5.11 Versi >>> on snv_76 64-bit >>> This message posted from opensolaris.org >>> _______________________________________________ >>> xen-discuss mailing list >>> xen-discuss@opensolaris.org >
Andrew Watkins
2007-Dec-20 16:38 UTC
Re: snv_b75a crash on starting X - intel driver issue?
Add another Intel driver to the crash list:
Intel Corporation 82Q963/Q965 Integrated Graphics Controller rev 2
Downloaded B78 and Normal (bare metal) mode works fine no problems with Gnome.
But, as soon as I boot into Xvm mode and I start cde-login the hour glass
appears for a second and the system crashes.
I will see if I can find another graphics card.
# uname -a
SunOS ares 5.11 snv_78 i86pc i386 i86xpv
# psrinfo -vp
The physical processor has 2 virtual processors (0 1)
x86 (GenuineIntel 6F6 family 6 model 15 step 6 clock 2400 MHz)
Intel(r) Core(tm)2 CPU 6600 @ 2.40GHz
/var/adm/messages:
Dec 20 13:15:37 ares panic[cpu0]/thread=ffffff0131468800:
Dec 20 13:15:37 ares genunix: [ID 103648 kern.notice] mutex_enter: bad mutex,
lp=ffffff0136dc0d40 owner=35556b00355568 thread=ffffff0131468800
Dec 20 13:15:37 ares unix: [ID 100000 kern.notice]
Dec 20 13:15:37 ares genunix: [ID 655072 kern.notice] ffffff00040995f0
unix:mutex_panic+73 ()
Dec 20 13:15:37 ares genunix: [ID 655072 kern.notice] ffffff0004099660
unix:mutex_vector_enter+4df ()
....
Dec 20 13:15:37 ares genunix: [ID 672855 kern.notice] syncing file systems...
Dec 20 13:15:37 ares unix: [ID 836849 kern.notice]
Dec 20 13:15:37 ares panic[cpu0]/thread=ffffff0131468800:
Dec 20 13:15:37 ares genunix: [ID 683410 kern.notice] BAD TRAP: type=d (#gp
General protection) rp=fffffffffbc79bc0 addr=0
Dec 20 13:15:37 ares unix: [ID 100000 kern.notice]
This message posted from opensolaris.org
michael schuster
2007-Dec-20 16:52 UTC
Re: snv_b75a crash on starting X - intel driver issue?
Andrew, could you post the whole panic stack so we can make certain you''re not encountering something else? thx Michael Andrew Watkins wrote:> /var/adm/messages: > Dec 20 13:15:37 ares panic[cpu0]/thread=ffffff0131468800: > Dec 20 13:15:37 ares genunix: [ID 103648 kern.notice] mutex_enter: bad mutex, lp=ffffff0136dc0d40 owner=35556b00355568 thread=ffffff0131468800 > Dec 20 13:15:37 ares unix: [ID 100000 kern.notice] > Dec 20 13:15:37 ares genunix: [ID 655072 kern.notice] ffffff00040995f0 unix:mutex_panic+73 () > Dec 20 13:15:37 ares genunix: [ID 655072 kern.notice] ffffff0004099660 unix:mutex_vector_enter+4df () > .... > Dec 20 13:15:37 ares genunix: [ID 672855 kern.notice] syncing file systems...-- Michael Schuster Sun Microsystems, Inc. recursion, n: see ''recursion''
Andrew Watkins
2007-Dec-20 17:07 UTC
Re: snv_b75a crash on starting X - intel driver issue?
He is the full contents of /var/adm/messages. If you want any thing from crash dump let me know (please give the relevant commands since my mdb is very poor) Dec 20 16:12:46 ares rootnex: [ID 349649 kern.info] xsvc0 at root: space 0 offset 0 Dec 20 16:12:46 ares genunix: [ID 936769 kern.info] xsvc0 is /xsvc@0,0 Dec 20 16:12:48 ares unix: [ID 954099 kern.info] NOTICE: IRQ16 is being shared by drivers with different interrupt levels. Dec 20 16:12:48 ares This may result in reduced system performance. Dec 20 16:12:48 ares unix: [ID 881207 kern.notice] NOTICE: IRQ16 is shared Dec 20 16:12:50 ares last message repeated 1 time Dec 20 16:14:24 ares unix: [ID 954099 kern.info] NOTICE: IRQ16 is being shared by drivers with different interrupt levels. Dec 20 16:14:24 ares This may result in reduced system performance. Dec 20 16:14:24 ares unix: [ID 881207 kern.notice] NOTICE: IRQ16 is shared Dec 20 16:14:56 ares unix: [ID 836849 kern.notice] Dec 20 16:14:56 ares ^Mpanic[cpu0]/thread=ffffff0130ae7460: Dec 20 16:14:56 ares genunix: [ID 103648 kern.notice] mutex_enter: bad mutex, lp=ffffff0136c13bc0 owner=37586f00375868 thread=ffffff0130ae7460 Dec 20 16:14:56 ares unix: [ID 100000 kern.notice] Dec 20 16:14:56 ares genunix: [ID 655072 kern.notice] ffffff0003bb1c50 unix:mutex_panic+73 () Dec 20 16:14:56 ares genunix: [ID 655072 kern.notice] ffffff0003bb1cc0 unix:mutex_vector_enter+4df () Dec 20 16:14:56 ares genunix: [ID 655072 kern.notice] ffffff0003bb1d50 ufs:ufs_scan_inodes+b6 () Dec 20 16:14:56 ares genunix: [ID 655072 kern.notice] ffffff0003bb1dd0 ufs:ufs_update+21b () Dec 20 16:14:56 ares genunix: [ID 655072 kern.notice] ffffff0003bb1e30 ufs:ufs_sync+239 () Dec 20 16:14:56 ares genunix: [ID 655072 kern.notice] ffffff0003bb1e60 genunix:fsop_sync_by_kind+49 () Dec 20 16:14:56 ares genunix: [ID 655072 kern.notice] ffffff0003bb1ef0 genunix:fsflush+471 () Dec 20 16:14:56 ares genunix: [ID 655072 kern.notice] ffffff0003bb1f00 unix:thread_start+8 () Dec 20 16:14:56 ares unix: [ID 100000 kern.notice] Dec 20 16:14:56 ares genunix: [ID 672855 kern.notice] syncing file systems... Dec 20 16:14:56 ares genunix: [ID 733762 kern.notice] 8 Dec 20 16:14:57 ares genunix: [ID 733762 kern.notice] 2 Dec 20 16:15:17 ares last message repeated 20 times Dec 20 16:15:18 ares genunix: [ID 622722 kern.notice] done (not all i/o completed) Dec 20 16:15:19 ares genunix: [ID 111219 kern.notice] dumping to /dev/dsk/c1d0s1, offset 431030272, content: kernel Dec 20 16:15:22 ares genunix: [ID 409368 kern.notice] ^M100% done: 59158 pages dumped, compression ratio 4.16, Dec 20 16:15:22 ares genunix: [ID 851671 kern.notice] dump succeeded Dec 20 16:15:56 ares genunix: [ID 540533 kern.notice] ^MSunOS Release 5.11 Version snv_78 64-bit Dec 20 16:15:56 ares genunix: [ID 943907 kern.notice] Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved. Dec 20 16:15:56 ares Use is subject to license terms. Dec 20 16:15:56 ares unix: [ID 126719 kern.info] features: 31e66c6<ssse3,cpuid,cmp,cx16,sse3,nx,sse2,sse,cx8,pae,mmx,cmov,msr,tsc> Dec 20 16:15:56 ares unix: [ID 168242 kern.info] mem = 1903136K (0x74288000) Dec 20 16:15:56 ares unix: [ID 508459 kern.warning] WARNING: Cannot load psm pcplusmp Dec 20 16:15:56 ares rootnex: [ID 466748 kern.info] root nexus = i86xpv Dec 20 16:15:56 ares rootnex: [ID 349649 kern.info] pseudo0 at root Dec 20 16:15:56 ares genunix: [ID 936769 kern.info] pseudo0 is /pseudo Dec 20 16:15:56 ares rootnex: [ID 349649 kern.info] scsi_vhci0 at root Dec 20 16:15:56 ares genunix: [ID 936769 kern.info] scsi_vhci0 is /scsi_vhci Dec 20 16:15:56 ares rootnex: [ID 349649 kern.info] isa0 at root Dec 20 16:15:56 ares xpv_psm: [ID 658230 kern.info] NOTICE: apic: local nmi: 1 0 0 1 Dec 20 16:15:56 ares xpv_psm: [ID 658230 kern.info] NOTICE: apic: local nmi: 2 0 0 1 Dec 20 16:15:56 ares xpv_psm: [ID 177709 kern.info] xen_psm: vector 0x9 ioapic 0x2 intin 0x9 is bound to cpu 1 Dec 20 16:15:56 ares genunix: [ID 636498 kern.warning] WARNING: cannot load platform pm driver acpippm Dec 20 16:15:56 ares genunix: [ID 636498 kern.warning] WARNING: cannot load platform pm driver ppm Dec 20 16:15:56 ares rootnex: [ID 349649 kern.info] npe0 at root: space 0 offset 0 Dec 20 16:15:56 ares genunix: [ID 936769 kern.info] npe0 is /pci@0,0 Dec 20 16:15:56 ares xpv_psm: [ID 803547 kern.info] xen_psm: pci-ide (pci-ide) instance 0 vector 0x13 ioapic 0x2 intin 0x13 is bound to cpu 0 Dec 20 16:15:56 ares genunix: [ID 640982 kern.info] IDE device at targ 0, lun 0 lastlun 0x0 Dec 20 16:15:56 ares genunix: [ID 846691 kern.info] model Hitachi HDT725032VLA360 Dec 20 16:15:56 ares genunix: [ID 479077 kern.info] ATA/ATAPI-7 supported, majver 0xfc minver 0x1a Dec 20 16:15:57 ares npe: [ID 236367 kern.info] PCI Express-device: ide@0, ata0 Dec 20 16:15:57 ares genunix: [ID 936769 kern.info] ata0 is /pci@0,0/pci-ide@1f,2/ide@0 Dec 20 16:15:57 ares genunix: [ID 773945 kern.info] UltraDMA mode 5 selected Dec 20 16:15:57 ares gda: [ID 243001 kern.info] Disk0: <Vendor ''Gen-ATA '' Product ''Hitachi HDT72503''> Dec 20 16:15:59 ares ata: [ID 496167 kern.info] cmdk0 at ata0 target 0 lun 0 Dec 20 16:15:59 ares genunix: [ID 936769 kern.info] cmdk0 is /pci@0,0/pci-ide@1f,2/ide@0/cmdk@0,0 Dec 20 16:16:01 ares unix: [ID 190185 kern.info] SMBIOS v2.4 loaded (1500 bytes) Dec 20 16:16:01 ares genunix: [ID 408114 kern.info] /cpus (cpunex0) online Dec 20 16:16:01 ares pseudo: [ID 129642 kern.info] pseudo-device: dld0 Dec 20 16:16:01 ares genunix: [ID 936769 kern.info] dld0 is /pseudo/dld@0 Dec 20 16:16:01 ares genunix: [ID 830136 kern.info] NOTICE: drm: Initialized i915 1.4.0 20060929 Dec 20 16:16:02 ares xpv_psm: [ID 803547 kern.info] xen_psm: pciclass,0c0320 (ehci) instance 0 vector 0x12 ioapic 0x2 intin 0x12 is bound to cpu 1 Dec 20 16:16:03 ares npe: [ID 236367 kern.info] PCI Express-device: pci8086,4f43@1a,7, ehci0 Dec 20 16:16:03 ares genunix: [ID 936769 kern.info] ehci0 is /pci@0,0/pci8086,4f43@1a,7 Dec 20 16:16:03 ares xpv_psm: [ID 444295 kern.info] xen_psm: pciclass,0c0320 (ehci) instance #1 vector 0x17 ioapic 0x2 intin 0x17 is bound to cpu 0 Dec 20 16:16:04 ares npe: [ID 236367 kern.info] PCI Express-device: pci8086,4f43@1d,7, ehci1 Dec 20 16:16:04 ares genunix: [ID 936769 kern.info] ehci1 is /pci@0,0/pci8086,4f43@1d,7 Dec 20 16:16:04 ares xpv_psm: [ID 803547 kern.info] xen_psm: pciclass,0c0300 (uhci) instance 0 vector 0x10 ioapic 0x2 intin 0x10 is bound to cpu 0 Dec 20 16:16:04 ares npe: [ID 236367 kern.info] PCI Express-device: pci8086,4f43@1a, uhci0 Dec 20 16:16:04 ares genunix: [ID 936769 kern.info] uhci0 is /pci@0,0/pci8086,4f43@1a Dec 20 16:16:04 ares xpv_psm: [ID 444295 kern.info] xen_psm: pciclass,0c0300 (uhci) instance #1 vector 0x15 ioapic 0x2 intin 0x15 is bound to cpu 0 Dec 20 16:16:04 ares npe: [ID 236367 kern.info] PCI Express-device: pci8086,4f43@1a,1, uhci1 Dec 20 16:16:04 ares genunix: [ID 936769 kern.info] uhci1 is /pci@0,0/pci8086,4f43@1a,1 Dec 20 16:16:04 ares unix: [ID 881207 kern.notice] NOTICE: IRQ23 is shared Dec 20 16:16:05 ares npe: [ID 236367 kern.info] PCI Express-device: pci8086,4f43@1d, uhci2 Dec 20 16:16:05 ares genunix: [ID 936769 kern.info] uhci2 is /pci@0,0/pci8086,4f43@1d Dec 20 16:16:05 ares unix: [ID 954099 kern.info] NOTICE: IRQ19 is being shared by drivers with different interrupt levels. Dec 20 16:16:05 ares This may result in reduced system performance. Dec 20 16:16:05 ares npe: [ID 236367 kern.info] PCI Express-device: pci8086,4f43@1d,1, uhci3 Dec 20 16:16:05 ares genunix: [ID 936769 kern.info] uhci3 is /pci@0,0/pci8086,4f43@1d,1 Dec 20 16:16:05 ares unix: [ID 881207 kern.notice] NOTICE: IRQ18 is shared Dec 20 16:16:05 ares npe: [ID 236367 kern.info] PCI Express-device: pci8086,4f43@1d,2, uhci4 Dec 20 16:16:05 ares genunix: [ID 936769 kern.info] uhci4 is /pci@0,0/pci8086,4f43@1d,2 Dec 20 16:16:05 ares unix: [ID 950921 kern.info] cpu0: x86 (chipid 0x0 GenuineIntel 6F6 family 6 model 15 step 6 clock 2400 MHz) Dec 20 16:16:05 ares unix: [ID 950921 kern.info] cpu0: Intel(r) Core(tm)2 CPU 6600 @ 2.40GHz Dec 20 16:16:05 ares unix: [ID 950921 kern.info] cpu1: x86 (chipid 0x0 GenuineIntel 6F6 family 6 model 15 step 6 clock 2400 MHz) Dec 20 16:16:05 ares unix: [ID 950921 kern.info] cpu1: Intel(r) Core(tm)2 CPU 6600 @ 2.40GHz Dec 20 16:16:05 ares unix: [ID 557827 kern.info] cpu1 initialization complete - online Dec 20 16:16:05 ares unix: [ID 469452 kern.info] NOTICE: cpqhpc: 64-bit driver module not found Dec 20 16:16:05 ares usba: [ID 912658 kern.info] USB 1.10 device (usb4f2,116) operating at low speed (USB 1.x) on USB 1.10 root hub: keyboard@1, hid0 at bus address 2 Dec 20 16:16:05 ares usba: [ID 349649 kern.info] CHICONY USB Keyboard Dec 20 16:16:05 ares genunix: [ID 936769 kern.info] hid0 is /pci@0,0/pci8086,4f43@1d,2/keyboard@1 Dec 20 16:16:05 ares genunix: [ID 408114 kern.info] /pci@0,0/pci8086,4f43@1d,2/keyboard@1 (hid0) online Dec 20 16:16:05 ares usba: [ID 912658 kern.info] USB 1.10 device (usb45e,83) operating at low speed (USB 1.x) on USB 1.10 root hub: mouse@2, hid1 at bus address 3 Dec 20 16:16:05 ares usba: [ID 349649 kern.info] Microsoft Basic Optical Mouse Dec 20 16:16:05 ares genunix: [ID 936769 kern.info] hid1 is /pci@0,0/pci8086,4f43@1d,2/mouse@2 Dec 20 16:16:05 ares genunix: [ID 408114 kern.info] /pci@0,0/pci8086,4f43@1d,2/mouse@2 (hid1) online Dec 20 16:16:05 ares pcie_pci: [ID 975022 kern.info] Failed to initialize inband hotplug controller Dec 20 16:16:05 ares npe: [ID 236367 kern.info] PCI Express-device: pci8086,283f@1c, pcie_pci0 Dec 20 16:16:05 ares genunix: [ID 936769 kern.info] pcie_pci0 is /pci@0,0/pci8086,283f@1c Dec 20 16:16:05 ares pcie_pci: [ID 975022 kern.info] Failed to initialize inband hotplug controller Dec 20 16:16:05 ares npe: [ID 236367 kern.info] PCI Express-device: pci8086,2841@1c,1, pcie_pci1 Dec 20 16:16:05 ares genunix: [ID 936769 kern.info] pcie_pci1 is /pci@0,0/pci8086,2841@1c,1 Dec 20 16:16:05 ares pcie_pci: [ID 975022 kern.info] Failed to initialize inband hotplug controller Dec 20 16:16:05 ares npe: [ID 236367 kern.info] PCI Express-device: pci8086,2843@1c,2, pcie_pci2 Dec 20 16:16:05 ares genunix: [ID 936769 kern.info] pcie_pci2 is /pci@0,0/pci8086,2843@1c,2 Dec 20 16:16:05 ares pcie_pci: [ID 975022 kern.info] Failed to initialize inband hotplug controller Dec 20 16:16:05 ares npe: [ID 236367 kern.info] PCI Express-device: pci8086,2845@1c,3, pcie_pci3 Dec 20 16:16:05 ares genunix: [ID 936769 kern.info] pcie_pci3 is /pci@0,0/pci8086,2845@1c,3 Dec 20 16:16:05 ares pcie_pci: [ID 975022 kern.info] Failed to initialize inband hotplug controller Dec 20 16:16:05 ares npe: [ID 236367 kern.info] PCI Express-device: pci8086,2847@1c,4, pcie_pci4 Dec 20 16:16:05 ares genunix: [ID 936769 kern.info] pcie_pci4 is /pci@0,0/pci8086,2847@1c,4 Dec 20 16:16:08 ares unix: [ID 469452 kern.info] NOTICE: cpqhpc: 64-bit driver module not found Dec 20 16:16:09 ares genunix: [ID 773945 kern.info] UltraDMA mode 5 selected Dec 20 16:16:10 ares genunix: [ID 454863 kern.info] dump on /dev/dsk/c1d0s1 size 2055 MB Dec 20 16:16:15 ares mac: [ID 469746 kern.info] NOTICE: e1000g0 registered Dec 20 16:16:15 ares xpv_psm: [ID 803547 kern.info] xen_psm: pci8086,104a (e1000g) instance 0 vector 0x14 ioapic 0x2 intin 0x14 is bound to cpu 1 Dec 20 16:16:15 ares e1000g: [ID 766679 kern.info] Intel(R) PRO/1000 Network Connection, Driver Ver. 5.2.3 Dec 20 16:16:15 ares audiosup: [ID 553120 kern.warning] WARNING: audiohd0: unsupported HD codec: vid=0x83847618, rev=0x00100201 Dec 20 16:16:15 ares audiosup: [ID 493330 kern.warning] WARNING: audiohd0: audiohd_attach() couldn''t create codec Dec 20 16:16:15 ares npe: [ID 236367 kern.info] PCI Express-device: pci8086,244e@1e, pci_pci0 Dec 20 16:16:15 ares genunix: [ID 936769 kern.info] pci_pci0 is /pci@0,0/pci8086,244e@1e Dec 20 16:16:16 ares pseudo: [ID 129642 kern.info] pseudo-device: zfs0 Dec 20 16:16:16 ares genunix: [ID 936769 kern.info] zfs0 is /pseudo/zfs@0 Dec 20 16:16:17 ares pseudo: [ID 129642 kern.info] pseudo-device: devinfo0 Dec 20 16:16:17 ares genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0 Dec 20 16:16:18 ares pseudo: [ID 129642 kern.info] pseudo-device: pm0 Dec 20 16:16:18 ares genunix: [ID 936769 kern.info] pm0 is /pseudo/pm@0 Dec 20 16:16:18 ares rootnex: [ID 349649 kern.info] xsvc0 at root: space 0 offset 0 Dec 20 16:16:18 ares genunix: [ID 936769 kern.info] xsvc0 is /xsvc@0,0 Dec 20 16:16:18 ares pseudo: [ID 129642 kern.info] pseudo-device: power0 Dec 20 16:16:18 ares genunix: [ID 936769 kern.info] power0 is /pseudo/power@0 Dec 20 16:16:18 ares pseudo: [ID 129642 kern.info] pseudo-device: srn0 Dec 20 16:16:18 ares genunix: [ID 936769 kern.info] srn0 is /pseudo/srn@0 Dec 20 16:16:18 ares /usr/lib/power/powerd: [ID 387247 daemon.error] Able to open /dev/srn Dec 20 16:16:19 ares mac: [ID 435574 kern.info] NOTICE: e1000g0 link up, 100 Mbps, full duplex Dec 20 16:16:32 ares rootnex: [ID 349649 kern.info] xpvd0 at root Dec 20 16:16:32 ares xpvd: [ID 395608 kern.info] xenbus@0, xenbus0 Dec 20 16:16:32 ares genunix: [ID 936769 kern.info] xenbus0 is /xpvd/xenbus@0 Dec 20 16:16:32 ares xpvd: [ID 395608 kern.info] privcmd@0, privcmd0 Dec 20 16:16:32 ares genunix: [ID 936769 kern.info] privcmd0 is /xpvd/privcmd@0 Dec 20 16:16:33 ares in.routed[406]: [ID 749644 daemon.notice] e1000g0 has a bad address 0.0.0.0 Dec 20 16:16:33 ares xenstored: [ID 702911 daemon.error] Checking store ... Dec 20 16:16:33 ares xenstored: [ID 702911 daemon.error] Checking store complete. Dec 20 16:16:33 ares xpvd: [ID 395608 kern.info] evtchn@0, evtchn0 Dec 20 16:16:33 ares genunix: [ID 936769 kern.info] evtchn0 is /xpvd/evtchn@0 Dec 20 16:16:35 ares xpv_psm: [ID 803547 kern.info] xen_psm: asy (asy) instance 0 vector 0x4 ioapic 0x2 intin 0x4 is bound to cpu 0 Dec 20 16:16:35 ares isa: [ID 202937 kern.info] ISA-device: asy0 Dec 20 16:16:35 ares genunix: [ID 936769 kern.info] asy0 is /isa/asy@1,3f8 Dec 20 16:16:35 ares pseudo: [ID 129642 kern.info] pseudo-device: dtrace0 Dec 20 16:16:35 ares genunix: [ID 936769 kern.info] dtrace0 is /pseudo/dtrace@0 Dec 20 16:16:35 ares xpv_psm: [ID 444295 kern.info] xen_psm: pci-ide (pci-ide) instance #2 vector 0x11 ioapic 0x2 intin 0x11 is bound to cpu 0 Dec 20 16:16:35 ares genunix: [ID 640982 kern.info] ATAPI device at targ 0, lun 0 lastlun 0x0 Dec 20 16:16:35 ares genunix: [ID 846691 kern.info] model SONY CD-RW CRX320EE Dec 20 16:16:35 ares genunix: [ID 479077 kern.info] ATA/ATAPI-5 supported, majver 0x20 minver 0x0 Dec 20 16:16:36 ares savecore: [ID 570001 auth.error] reboot after panic: mutex_enter: bad mutex, lp=ffffff0136c13bc0 owner=37586f00375868 thread=ffffff0130ae7460 Dec 20 16:16:36 ares savecore: [ID 748169 auth.error] saving system crash dump in /var/crash/ares/*.0 Dec 20 16:16:37 ares pcie_pci: [ID 586369 kern.info] PCIE-device: ide@0, ata4 Dec 20 16:16:37 ares genunix: [ID 936769 kern.info] ata4 is /pci@0,0/pci8086,2841@1c,1/pci-ide@0/ide@0 Dec 20 16:16:37 ares genunix: [ID 773945 kern.info] UltraDMA mode 2 selected Dec 20 16:16:37 ares last message repeated 2 times Dec 20 16:16:37 ares scsi: [ID 193665 kern.info] sd0 at ata4: target 0 lun 0 Dec 20 16:16:37 ares genunix: [ID 936769 kern.info] sd0 is /pci@0,0/pci8086,2841@1c,1/pci-ide@0/ide@0/sd@0,0 Dec 20 16:16:37 ares genunix: [ID 314293 kern.info] device pci8086,2992@2(display#0) keeps up device sd@0,0(sd#0), but the latter is not power managed Dec 20 16:16:39 ares sendmail[517]: [ID 702911 mail.crit] My unqualified host name (ares) unknown; sleeping for retry Dec 20 16:16:39 ares sendmail[516]: [ID 702911 mail.crit] My unqualified host name (ares) unknown; sleeping for retry Dec 20 16:16:41 ares xpv_psm: [ID 803547 kern.info] xen_psm: lp (ecpp) instance 0 vector 0x7 ioapic 0x2 intin 0x7 is bound to cpu 1 Dec 20 16:16:41 ares isa: [ID 202937 kern.info] ISA-device: ecpp0 Dec 20 16:16:41 ares genunix: [ID 936769 kern.info] ecpp0 is /isa/lp@1,378 Dec 20 16:16:48 ares unix: [ID 517869 kern.info] cpu0: externally initiated on-line Dec 20 16:16:49 ares unix: [ID 517869 kern.info] cpu1: externally initiated on-line Dec 20 16:16:55 ares rootnex: [ID 349649 kern.info] xsvc0 at root: space 0 offset 0 Dec 20 16:16:55 ares genunix: [ID 936769 kern.info] xsvc0 is /xsvc@0,0 Dec 20 16:16:55 ares pseudo: [ID 129642 kern.info] pseudo-device: devinfo0 Dec 20 16:16:55 ares genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0 Dec 20 16:17:22 ares /sbin/dhcpagent[184]: [ID 981413 daemon.warning] configure_v4_lease: incorrect broadcast address 255.255.255.0 specified for e1000g0; ignoring Dec 20 16:17:32 ares pseudo: [ID 129642 kern.info] pseudo-device: pool0 Dec 20 16:17:32 ares genunix: [ID 936769 kern.info] pool0 is /pseudo/pool@0 Dec 20 16:17:39 ares sendmail[517]: [ID 702911 mail.alert] unable to qualify my own domain name (ares) -- using short name Dec 20 16:17:39 ares sendmail[516]: [ID 702911 mail.alert] unable to qualify my own domain name (ares) -- using short name Dec 20 16:41:15 ares inetd[469]: [ID 702911 daemon.warning] inetd_offline method for instance svc:/network/rpc/cde-calendar-manager:default is unspecified. Taking default action: kill. Dec 20 16:41:15 ares inetd[469]: [ID 702911 daemon.warning] inetd_offline method for instance svc:/network/rpc/cde-ttdbserver:tcp is unspecified. Taking default action: kill. Dec 20 16:41:24 ares pseudo: [ID 129642 kern.info] pseudo-device: pm0 Dec 20 16:41:24 ares genunix: [ID 936769 kern.info] pm0 is /pseudo/pm@0 Dec 20 16:41:24 ares syslogd: going down on signal 15 Dec 20 16:41:29 ares rpcbind: [ID 564983 daemon.error] rpcbind terminating on signal. Dec 20 16:41:35 ares nwamd[30]: [ID 665447 daemon.notice] Terminated received, shutting down Dec 20 16:41:56 ares genunix: [ID 672855 kern.notice] syncing file systems... Dec 20 16:41:56 ares genunix: [ID 904073 kern.notice] done Thanks Andrew Watkins This message posted from opensolaris.org
Andrew Watkins wrote:> Add another Intel driver to the crash list: > > Intel Corporation 82Q963/Q965 Integrated Graphics Controller rev 2 > > Downloaded B78 and Normal (bare metal) mode works fine no problems with Gnome.This bug was fix in b79. http://bugs.opensolaris.org/view_bug.do?bug_id=6624364 MRJ> But, as soon as I boot into Xvm mode and I start cde-login the hour glass appears for a second and the system crashes. > I will see if I can find another graphics card. > > # uname -a > SunOS ares 5.11 snv_78 i86pc i386 i86xpv > > # psrinfo -vp > The physical processor has 2 virtual processors (0 1) > x86 (GenuineIntel 6F6 family 6 model 15 step 6 clock 2400 MHz) > Intel(r) Core(tm)2 CPU 6600 @ 2.40GHz > > /var/adm/messages: > Dec 20 13:15:37 ares panic[cpu0]/thread=ffffff0131468800: > Dec 20 13:15:37 ares genunix: [ID 103648 kern.notice] mutex_enter: bad mutex, lp=ffffff0136dc0d40 owner=35556b00355568 thread=ffffff0131468800 > Dec 20 13:15:37 ares unix: [ID 100000 kern.notice] > Dec 20 13:15:37 ares genunix: [ID 655072 kern.notice] ffffff00040995f0 unix:mutex_panic+73 () > Dec 20 13:15:37 ares genunix: [ID 655072 kern.notice] ffffff0004099660 unix:mutex_vector_enter+4df () > .... > Dec 20 13:15:37 ares genunix: [ID 672855 kern.notice] syncing file systems... > Dec 20 13:15:37 ares unix: [ID 836849 kern.notice] > Dec 20 13:15:37 ares panic[cpu0]/thread=ffffff0131468800: > Dec 20 13:15:37 ares genunix: [ID 683410 kern.notice] BAD TRAP: type=d (#gp General protection) rp=fffffffffbc79bc0 addr=0 > Dec 20 13:15:37 ares unix: [ID 100000 kern.notice] > > > This message posted from opensolaris.org > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
michael schuster
2007-Dec-20 17:27 UTC
Re: snv_b75a crash on starting X - intel driver issue?
Andrew Watkins wrote:> He is the full contents of /var/adm/messages.ahem ... I did say "stack", didn''t I? :-)> If you want any thing from crash dump let me know (please give the relevant commands since my mdb is very poor)> Dec 20 16:14:56 ares genunix: [ID 103648 kern.notice] mutex_enter: bad mutex, lp=ffffff0136c13bc0 owner=37586f00375868 thread=ffffff0130ae7460 > Dec 20 16:14:56 ares unix: [ID 100000 kern.notice] > Dec 20 16:14:56 ares genunix: [ID 655072 kern.notice] ffffff0003bb1c50 unix:mutex_panic+73 () > Dec 20 16:14:56 ares genunix: [ID 655072 kern.notice] ffffff0003bb1cc0 unix:mutex_vector_enter+4df () > Dec 20 16:14:56 ares genunix: [ID 655072 kern.notice] ffffff0003bb1d50 ufs:ufs_scan_inodes+b6 () > Dec 20 16:14:56 ares genunix: [ID 655072 kern.notice] ffffff0003bb1dd0 ufs:ufs_update+21b () > Dec 20 16:14:56 ares genunix: [ID 655072 kern.notice] ffffff0003bb1e30 ufs:ufs_sync+239 () > Dec 20 16:14:56 ares genunix: [ID 655072 kern.notice] ffffff0003bb1e60 genunix:fsop_sync_by_kind+49 () > Dec 20 16:14:56 ares genunix: [ID 655072 kern.notice] ffffff0003bb1ef0 genunix:fsflush+471 () > Dec 20 16:14:56 ares genunix: [ID 655072 kern.notice] ffffff0003bb1f00 unix:thread_start+8 () > Dec 20 16:14:56 ares unix: [ID 100000 kern.notice] > Dec 20 16:14:56 ares genunix: [ID 672855 kern.notice] syncing file systems...this definitely doesn''t look like a graphics problem ... UFS is panicking because it''s trying to access a mutex whose owner thread is a bad value (37586f00375868 - this is not a valid thread pointer, AFAIK). Do other panics which you attribute to bad graphics have a similar stack? Michael -- Michael Schuster Sun Microsystems, Inc. recursion, n: see ''recursion''
michael schuster
2007-Dec-20 17:37 UTC
Re: snv_b75a crash on starting X - intel driver issue?
> this definitely doesn''t look like a graphics problem ... UFS is panicking > because it''s trying to access a mutex whose owner thread is a bad value > (37586f00375868 - this is not a valid thread pointer, AFAIK). > > Do other panics which you attribute to bad graphics have a similar stack?andrew, Mark just informed me that he thinks it''s very likely the graphics bug ... so don''t bother sending further (older) stacks. Michael -- Michael Schuster Sun Microsystems, Inc. recursion, n: see ''recursion''
Andrew Watkins
2007-Dec-20 18:16 UTC
Re: snv_b75a crash on starting X - intel driver issue?
Thanks and it looks like it was the graphics bug 6624364 I did the workround and it worked like a dream: =====Force Xorg to use the vesa driver: Boot into single-user and run /usr/X11/bin/Xorg -configure Copy /xorg.conf.new to /etc/X11/xorg.conf Edit /etc/X11/xorg.conf and scroll to the "Device" section. Replace Driver "intel" with Driver "vesa" ===== Thanks Andrew This message posted from opensolaris.org