I have DL385 after upgrade to Solaris 6/6 my server begun hang up after init
6or reboot. Every time after reboot I could se a message at RAID controler
that some “data” is there and it needs to pushed ... Crap!!.. Power off always
clean that cache or Crap. I fixed new BIOS firmware(BIOS
Vlad wrote:
I have DL385 after upgrade to Solaris 6/6 my server begun hang up after init
6or reboot.
This is a known problem, for which I am preparing to integrate a fix into
Solaris Nevada
(and into the next possible S10 update).
The hang is caused when, during PCI enumeration, a PCI-PCI
I'm disappointed,
i'll change sysytem disks and install Windows 2003 x64, if it will work good,
i'll take leave of Solaris :)
maybe it is too early for production
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
Same problems here. DL585 with last firmware.
We have 14 units to upgrade to U2 as we need ZFS.
Now testing linux ... :(
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Dmitry wrote:
today dl585 hang at work,
but it only copied 1 big file from network,
So, the system hangs not only during boot, but sometimes
long after boot?
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
big text, i attach it at first message
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
now i see hp.com
software and drivers
HP ProLiant DL585 Server, Sun Solaris 10 x86 Platform Edition
HP System Management Homepage for Solaris (x86) 10 2.0.0 [b]new 18 Jul 06[/b]
so it should be work
???
This message posted from opensolaris.org
i don't understand it :) (i run it in 32-bit mode )
# ./autovec
...
[9]
acpi_wrapper_isr() pri 0
So, my theory that the hang could be caused by shared interrupts is wrong;
there is exactly one interrupt handler registered for vector 9.
I also had a closer look at the acpica initialization
can i use this method for debug acpica at boot?
http://blogs.sun.com/roller/page/danasblog?entry=solaris_acpi_ca_debug_output
I try it today later
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
As far as I can see, the problem seems to occur during the pci device tree
creation.
Maybe adding:
set pci_autoconfig:pci_boot_debug=1
to your /etc/system will provide more info about when the hang occurs.
Regards,
J-F
This message posted from opensolaris.org
From what I see in the screenshot the hang occurs during the pci bus probing.
I think it hangs in the following function:
http://cvs.opensolaris.org/source/xref/on/usr/src/uts/i86pc/io/pci/pci_boot.c#enumerate_bus_devs
just after the call of:
i try to set
set acpica:acpica_muzzle_debug_output=0
set acpica:AcpiDbgLevel=0x7
set acpica:acpica_console_out=1
please see screenshot 3 in the first message
may be increase AcpiDbgLevel?
I think AcpiDbgLevel=0x3fff is the default that is compiled into the acpica
module, and should print
Jürgen Keil wrote:
[...]
But... You also added set pci_autoconfig:pci_boot_debug=1 ?
The PCI Hot-Plug and the NOTICE messages are not from the acpica code.
So, now it is looking more and more as if acpica isn't responsible for the
hang,
but the pci bus enumeration code.
Quote from
Jean-François Ndi wrote:
From what I see in the screenshot the hang occurs during the pci bus probing.
I haven't seen a screenshot - did Dmitri send one? Could you forward it
to me?
I think it hangs in the following function:
i don't now, i'm muzzy
now i'll try to boot
with difeerent options
reboot -- -B acpi-user-options=
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Dmitry wrote:
i don't now, i'm muzzy
now i'll try to boot
with difeerent options
reboot -- -B acpi-user-options=
I would suggest not changing the default for acpi-user-options; the
evidence indicates that the issue is during PCI enumeration.
When the system *does* boot, would you be so kind
[b]The Solaris is being revamped because of Sun going through new construction
with Scott.[/b]
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Hi,
in -kd hang not present,
i attach full screenshot with set moddebug=0x8000
second file in the first mesaage
Can you add the v option to the kernel line (-kvd)? Maybe the system will show
something after loading acpica but before hanging.
Any better idea?
Regards,
J-F
That is, if you power cycle the machine, it will boot
without hanging,
at least sometimes?
if power off, on - usually it boot (sometime not)
echo ::interrupts | mdb -k
ope the ::interrupts command is supported by S10
6/2006)
[b]# echo ::interrupts | mdb -k
mdb: invalid command
[b]to jfndi[/b]
with -kv few reboot not hang,
without -kv, again hang
I just began to look at the ACPI code and spec. I have no furher idea for now.
If I have another one I will let you know.
Regards,
J-F
This message posted from opensolaris.org
I just began to look at the ACPI code and spec. I
have no furher idea for now. If I have another one I
will let you know.
thanks, i wait impatiently ...
i must to make decision, use Solaris or not
This message posted from opensolaris.org
___
echo ::interrupts | mdb -k
I hope the ::interrupts command is supported by S10 6/2006)
[b]# echo ::interrupts | mdb -k
mdb: invalid command '::interrupts': unknown dcmd
name[/b]
Too bad, the mdb ::interrupts command isn't backported to S10U2.
This is a new feature in OpenSolaris,
Is the hang with oracle reproducable? Does is always
hang when you
run a certain database command? For example when you
have
tablespace allocated to files on a logging ufs
filesystem, and you
drop such a file (= remove a big file from a logging
ufs filesystem) [*] ?
now i try to start
Hi Dmitry,
npe not present
So as I expected 6401605 is not involved here.
Thanks,
back to my ACPI study ;-)
Regards,
J-F
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Hi,
you can try this:
- boot in the debugger (-kd)
- ::bp acpica`_init (note the backtick character)
- :c
When you hit the break point:
- ::step over
this, until you either hang or see another module getting installed. (I know,
not the most elegant but it will help you determine what is
Jean-François Ndi wrote:
Hi,
you can try this:
- boot in the debugger (-kd)
- ::bp acpica`_init (note the backtick character)
- :c
When you hit the break point:
- ::step over
this, until you either hang or see another module getting installed. (I know,
not the most elegant but
26 matches
Mail list logo
