| View previous topic :: View next topic |
| Author |
Message |
jvax
n00b
Joined: 29 Nov 2006
Posts: 18
Location: Japan
|
 Posted: Fri Dec 08, 2006 5:51 am Post subject: System hangs during shutdown |
 |
|
Hi all,
I am running 2.6.17r8 on a Blade 100 with X 7.1.1 and whenever I try to shut it down, it hangs just after tring to go back to OPB and freezes there. I say "trying" because on the same freeze screen I can see gentoo shutdown messages, (get this, in a pink color font!!) like "unmounting filesystems..." AND the OBP OK> prompt.
From there I get no response from keyboard or anything so I always have to power it off by holding down the power button for a few secons.
The strange thing is that this does not happen when rebooting, and it's driving me nuts.
Here are the commands I use:
poweroff system freezes
reboot system reboots with success
shutdown -i 0 now system freezes
shutdown -h now system freezes
shutdown -r now system reboots with success.
I will update this post with a snapshot of the freeze screen later.
UPDATE: Here are some snapshots. snapshot1 snapshot2
Anyone got a similar problem? Everything I came through when searching was a few other experiences of the same problem but no solution.
Any log files I can post, please tell me and I'll post them.
Thanks
_________________
Blade 100 2.6.17r8
a wise man said once:
"Give your sun a sparc with Gentoo"
Last edited by jvax on Fri Dec 08, 2006 3:04 pm; edited 1 time in total |
|
| Back to top |
|
 |
psychomunky
Guru
Joined: 02 Nov 2004
Posts: 337
Location: Canada
|
| Posted: Fri Dec 08, 2006 6:26 am Post subject: |
|
|
| There are numerous buggy BIOSes and motherboards out there that can cause this. As a result there are quite a few options in the kernel to workaround this. The most prominent one I know about is "Processor Type and Features --> Enable X86 board specific fixups for reboot". |
|
| Back to top |
|
|
jvax
n00b
Joined: 29 Nov 2006
Posts: 18
Location: Japan
|
| Posted: Fri Dec 08, 2006 3:10 pm Post subject: |
|
|
| psychomunky wrote: | | There are numerous buggy BIOSes and motherboards out there that can cause this. As a result there are quite a few options in the kernel to workaround this. The most prominent one I know about is "Processor Type and Features --> Enable X86 board specific fixups for reboot". |
BIOS and x86 are PC terms. Blade 100 is a SPARC platform, therefore in stead of BIOS it has OpenBoot Prom and instead of a x86 CPU it's a UltraSPARC IIe CPU.
Thanks for the info though. I'll be sure not to miss it if I use a PC.
_________________
Blade 100 2.6.17r8
a wise man said once:
"Give your sun a sparc with Gentoo" |
|
| Back to top |
|
|
Risk
n00b
Joined: 05 Mar 2004
Posts: 38
Location: Zoo York City
|
| Posted: Fri Dec 08, 2006 5:14 pm Post subject: |
|
|
Give gentoo-sources-2.6.19-r1 a try.
2.6.19 has some salient fixes:
| Quote: | [SPARC64]: Fix PCI memory space root resource on Hummingbird.
For Hummingbird PCI controllers, we should create the root
PCI memory space resource as the full 4GB area, and then
allocate the IOMMU DMA translation window out of there.
The old code just assumed that the IOMMU DMA translation base
to the top of the 4GB area was unusable. This is not true on
many systems such as SB100 and SB150, where the IOMMU DMA
translation window sits at 0xc0000000->0xdfffffff.
So what would happen is that any device mapped by the firmware
at the top section 0xe0000000->0xffffffff would get remapped
by Linux somewhere else leading to all kinds of problems and
boot failures.
While we're here, report more cases of OBP resource assignment
conflicts. The only truly valid ones are ROM resource conflicts.
[PATCH] sparc64 pt_regs fixes
[PATCH] pci: don't try to remove sysfs files before they are setup.
The PCI sysfs attributes are created after the initial PCI bus scan. With
the addition of more return value checking and assertions in the device and
sysfs layers we now can get dumps like this on sparc64:
[ 20.135032] Call Trace:
[ 20.135042] [0000000000537f88] pci_remove_bus_device+0x30/0xc0
[ 20.135076] [000000000078f890] pci_fill_in_pbm_cookies+0x98/0x440
[ 20.135109] [000000000042e828] sabre_scan_bus+0x230/0x400
[ 20.135139] [000000000078c710] pcibios_init+0x58/0xa0
[ 20.135159] [0000000000416f14] init+0x9c/0x2e0
[ 20.135190] [0000000000417a50] kernel_thread+0x38/0x60
[ 20.135211] [0000000000417170] rest_init+0x18/0x40
[ 20.135514] PCI0(PBMB): Bus running at 33MHz
It's triggering because removal of the "config" PCI sysfs file for the
device fails.
On sparc64, after probing the device, we'll delete the PCI device via
pci_remove_bus_device() if we cannot find the firmware device tree node
corresponding to it.
This is fine, but at this point the sysfs files for the PCI device won't be
setup yet.
So we should not try to do anything in pci_remove_sysfs_dev_files() if
pci_sysfs_init() has not run yet. |
|
|
| Back to top |
|
|
jvax
n00b
Joined: 29 Nov 2006
Posts: 18
Location: Japan
|
| Posted: Sat Dec 09, 2006 12:02 am Post subject: |
|
|
| Risk wrote: | Give gentoo-sources-2.6.19-r1 a try.
2.6.19 has some salient fixes:
| Quote: | [SPARC64]: Fix PCI memory space root resource on Hummingbird.
For Hummingbird PCI controllers, we should create the root
PCI memory space resource as the full 4GB area, and then
allocate the IOMMU DMA translation window out of there.
The old code just assumed that the IOMMU DMA translation base
to the top of the 4GB area was unusable. This is not true on
many systems such as SB100 and SB150, where the IOMMU DMA
translation window sits at 0xc0000000->0xdfffffff.
So what would happen is that any device mapped by the firmware
at the top section 0xe0000000->0xffffffff would get remapped
by Linux somewhere else leading to all kinds of problems and
boot failures.
While we're here, report more cases of OBP resource assignment
conflicts. The only truly valid ones are ROM resource conflicts.
[PATCH] sparc64 pt_regs fixes
[PATCH] pci: don't try to remove sysfs files before they are setup.
The PCI sysfs attributes are created after the initial PCI bus scan. With
the addition of more return value checking and assertions in the device and
sysfs layers we now can get dumps like this on sparc64:
[ 20.135032] Call Trace:
[ 20.135042] [0000000000537f88] pci_remove_bus_device+0x30/0xc0
[ 20.135076] [000000000078f890] pci_fill_in_pbm_cookies+0x98/0x440
[ 20.135109] [000000000042e828] sabre_scan_bus+0x230/0x400
[ 20.135139] [000000000078c710] pcibios_init+0x58/0xa0
[ 20.135159] [0000000000416f14] init+0x9c/0x2e0
[ 20.135190] [0000000000417a50] kernel_thread+0x38/0x60
[ 20.135211] [0000000000417170] rest_init+0x18/0x40
[ 20.135514] PCI0(PBMB): Bus running at 33MHz
It's triggering because removal of the "config" PCI sysfs file for the
device fails.
On sparc64, after probing the device, we'll delete the PCI device via
pci_remove_bus_device() if we cannot find the firmware device tree node
corresponding to it.
This is fine, but at this point the sysfs files for the PCI device won't be
setup yet.
So we should not try to do anything in pci_remove_sysfs_dev_files() if
pci_sysfs_init() has not run yet. |
|
I might give it a try when I get time.
Although I can't help it wonder why would 2.6.17r8 be released as stable if this issue were kernel-related...
_________________
Blade 100 2.6.17r8
a wise man said once:
"Give your sun a sparc with Gentoo" |
|
| Back to top |
|
|
Risk
n00b
Joined: 05 Mar 2004
Posts: 38
Location: Zoo York City
|
| Posted: Tue Dec 12, 2006 8:32 pm Post subject: |
|
|
Many things (not just software) are released as "stable" and then cause rather unusual problems.
Think of all software as "works in progress".
Then: s/software/cars/
s/cars/attitudes/
s/attitudes/people/
so on and so forth
This is the way of the world. |
|
| Back to top |
|
|
psychomunky
Guru
Joined: 02 Nov 2004
Posts: 337
Location: Canada
|
| Posted: Wed Dec 13, 2006 12:38 am Post subject: |
|
|
| jvax wrote: | | BIOS and x86 are PC terms. |
No argument there...
| jvax wrote: | | Blade 100 is a SPARC platform, therefore in stead of BIOS it has OpenBoot Prom and instead of a x86 CPU it's a UltraSPARC IIe CPU. |
Ahh, here I did not know...at my work we run Blades as well, but all of ours are x86 or EM64T (Intel anyways) based. Since I am not a hardware guy/server admin (Programmer by trade, DBA by job description), I am not certain what models of Blades we run, nor did I "know" that your Blade 100 was a Sparc machine. Based on my experience with Blade Servers, I naturally assumed that yours was Intel based as well....my bad. BTW, I appreciate the wake-up call, it shows me how used to working in a 98% Intel/Windows shop I have become...which is why I refuse to become a Server Admin at this shop....but I digress...
You think the whole "Gentoo on Sparc" title of this thread would have clued me in.... |
|
| Back to top |
|
|
jvax
n00b
Joined: 29 Nov 2006
Posts: 18
Location: Japan
|
| Posted: Wed Dec 13, 2006 12:59 am Post subject: |
|
|
| Risk wrote: | Many things (not just software) are released as "stable" and then cause rather unusual problems.
Think of all software as "works in progress".
Then: s/software/cars/
s/cars/attitudes/
s/attitudes/people/
so on and so forth
This is the way of the world. |
You're probably right.
Thanks for the wise reminder.
Cheers
_________________
Blade 100 2.6.17r8
a wise man said once:
"Give your sun a sparc with Gentoo" |
|
| Back to top |
|
|
jvax
n00b
Joined: 29 Nov 2006
Posts: 18
Location: Japan
|
| Posted: Wed Dec 13, 2006 1:11 am Post subject: |
|
|
| psychomunky wrote: |
Ahh, here I did not know...at my work we run Blades as well, but all of ours are x86 or EM64T (Intel anyways) based. Since I am not a hardware guy/server admin (Programmer by trade, DBA by job description), I am not certain what models of Blades we run, nor did I "know" that your Blade 100 was a Sparc machine. Based on my experience with Blade Servers, I naturally assumed that yours was Intel based as well....my bad. BTW, I appreciate the wake-up call, it shows me how used to working in a 98% Intel/Windows shop I have become...which is why I refuse to become a Server Admin at this shop....but I digress...
You think the whole "Gentoo on Sparc" title of this thread would have clued me in.... |
I think I led you to confusion by saying Blade. My mistake. I should have said Sun Blade 100 Workstation, which has nothing to do with those pluggable server modules, called "blades", sold today by many vendors, IBM, HP, Hitachi, to name a few... AFAIK, those seem to be generally Intel based.
_________________
Blade 100 2.6.17r8
a wise man said once:
"Give your sun a sparc with Gentoo" |
|
| Back to top |
|
|
Weeve
Retired Dev
Joined: 30 Oct 2002
Posts: 641
|
| Posted: Wed Dec 13, 2006 2:53 pm Post subject: |
|
|
Not to be confused with the server blades Sun sells either  |
|
| Back to top |
|
|
jvax
n00b
Joined: 29 Nov 2006
Posts: 18
Location: Japan
|
| Posted: Wed Dec 13, 2006 3:04 pm Post subject: |
|
|
| Weeve wrote: | | Not to be confused with the server blades Sun sells either |
Right. Sun too does sell those...
Hey Weeve, anything I can do about the above-mentioned shutdown-system-hang issue?
_________________
Blade 100 2.6.17r8
a wise man said once:
"Give your sun a sparc with Gentoo" |
|
| Back to top |
|
|
Weeve
Retired Dev
Joined: 30 Oct 2002
Posts: 641
|
| Posted: Wed Dec 13, 2006 9:01 pm Post subject: |
|
|
Hrm, its been a while since I've had a Blade 100 setup with a monitor and keyboard. Normally I run mine headless and the default behavior then is to dump you back into OBP when it shuts down.
I don't know that it matters, but what version of OBP are you running? |
|
| Back to top |
|
|
jvax
n00b
Joined: 29 Nov 2006
Posts: 18
Location: Japan
|
| Posted: Thu Dec 14, 2006 2:17 am Post subject: |
|
|
OBP 4.5.9
I think the latest is 4.6.x
Should I try an upgrade? Although, I heard somewhere that 4.6 has issues with linux...
_________________
Blade 100 2.6.17r8
a wise man said once:
"Give your sun a sparc with Gentoo" |
|
| Back to top |
|
|
Risk
n00b
Joined: 05 Mar 2004
Posts: 38
Location: Zoo York City
|
| Posted: Thu Dec 14, 2006 2:50 pm Post subject: |
|
|
| Actually, I just experienced this shutdown "hang" on an E4500 running 2.6.18-r3 with the latest PROM version (3.2.30) so your mileage on OBP upgrade may vary. |
|
| Back to top |
|
|
Danhien
n00b
Joined: 19 Jan 2007
Posts: 7
|
| Posted: Thu Feb 01, 2007 9:45 am Post subject: |
|
|
| jvax wrote: | OBP 4.5.9
I think the latest is 4.6.x
Should I try an upgrade? Although, I heard somewhere that 4.6 has issues with linux... |
Did your try the OBP upgrade ? |
|
| Back to top |
|
|
jvax
n00b
Joined: 29 Nov 2006
Posts: 18
Location: Japan
|
| Posted: Thu Feb 01, 2007 4:12 pm Post subject: |
|
|
| Danhien wrote: | | jvax wrote: | OBP 4.5.9
I think the latest is 4.6.x
Should I try an upgrade? Although, I heard somewhere that 4.6 has issues with linux... |
Did your try the OBP upgrade ? |
Nope, havent had the time. I just decided to leave it up.
_________________
Blade 100 2.6.17r8
a wise man said once:
"Give your sun a sparc with Gentoo" |
|
| Back to top |
|
|
flak7
n00b
Joined: 17 Sep 2005
Posts: 44
Location: Poland
|
| Posted: Thu Feb 01, 2007 10:25 pm Post subject: |
|
|
https://forums.gentoo.org/viewtopic-t-517469.html
This thread concerns the same problem.
Anyway I am dealing with this problem (on Blade 100) since November without any luck.
_________________
IA32 - Slackware
SPARC64 - Gentoo |
|
| Back to top |
|
|
|
Gentoo on Sparc
