Re: Latest Debian Sparc64 installer

2018-12-17 Thread Tom Dial



On 12/17/18 04:25, John Paul Adrian Glaubitz wrote:
> Hi Thomas!
> 
> On 12/17/18 8:27 AM, Thomas D Dial wrote:
>> I have found debian-10.0-sparc64-NETINST-1.iso (apparent date 5/18/18
>> and debian-9.0-sparc64-NETINST-1.iso (apparent date 4/4/18) at
>> cdimage.debian.org. Is there a later version of either?
> 
> I'm working on a newer release, but I need to fix GRUB2 on sparc64 first
> which currently fails to build there due to a change in binutils.

Thanks to everyone who answered. The result of booting from the
installation CD_ROM of 20180516-10:56 is below. I generated the
diagnostic report because of reported CD-ROM failure on a prior attempt:

 /pci@8,70/scsi@6
Target 6
  Unit 0   Removable Read Only deviceTOSHIBA DVD-ROM SD-M14011007

{0} ok boot cdrom
Boot device: /pci@8,70/scsi@6/disk@6,0:f  File and args:

Can't open boot device

This was not a problem except with a serial console, and did not recur
after I removed a D-Link DGE-530T gigabit ethernet card that had been
/pci@8,70: Device 2.

I apologize for the length, but don't know enough about the hardware or
Linux internals to be confident in excluding anything.


@(#)OBP 4.16.4 2004/12/18 05:18
Power-On Reset
Executing Power On SelfTest
0:0>
0:0>@(#) Sun Fire[TM] V280, Sun Blade[TM] 1000 POST 4.16.3 2004/11/05 20:02

/dat/fw/common-source/firmware_re/post/post-build-4.16.3/Camelot/excal/integrated
 (firmware_re)
0:0>Copyright � 2004 Sun Microsystems, Inc. All rights reserved
  SUN PROPRIETARY/CONFIDENTIAL.
  Use is subject to license terms.
0:0>Jump from OBP->POST.
0:0>diag-switch? configuration variable set TRUE.
0:0>Diag level set to MIN.
0:0>MFG scrpt mode set to NONE
0:0>I/O port set to serial TTYA.
0:0>Done with First Init, reset system.
0:0>Current CPU frequency is 400 MHz.
0:0>Resetting to 900
0:0>Clock Synth Reset.
0:0>
0:0>Start selftest...
0:0>CPUs present in system: 0:0 1:0
0:0>Test CPU(s).
0:0>Init CPU
0:0>UltraSparc_III_base Version 5.11
0:0>DMMU Registers Access
0:0>DMMU TLB DATA RAM Access
0:0>DMMU TLB TAGS Access
0:0>IMMU Registers Access
0:0>IMMU TLB DATA RAM Access
0:0>IMMU TLB TAGS Access
0:0>Probe Ecache
0:0>Size = .0080...
0:0>Ecache Data Bitwalk
0:0>Ecache Address Bitwalk
0:0>Scrub and Setup Ecache
0:0>Setup and Enable DMMU
0:0>Setup DMMU Miss Handler
0:0>Test and Init Temp Mailbox
1:0>Init CPU
1:0>UltraSparc_III_base Version 5.11
1:0>DMMU Registers Access
1:0>DMMU TLB DATA RAM Access
1:0>DMMU TLB TAGS Access
1:0>IMMU Registers Access
1:0>IMMU TLB DATA RAM Access
1:0>IMMU TLB TAGS Access
1:0>Probe Ecache
1:0>Size = .0080...
1:0>Ecache Data Bitwalk
1:0>Ecache Address Bitwalk
1:0>Scrub and Setup Ecache
1:0>Setup and Enable DMMU
1:0>Setup DMMU Miss Handler
1:0>Test and Init Temp Mailbox
0:0>Init Scan/I2C.
0:0>Initializing Scan Database
0:0>BBC:1483203b
0:0>SCSI:   15060045
0:0>ICHIP:  0d1e203b
0:0>RIO:13e5d03b
0:0>IO-Bridge:  307be06d
0:0>CPMS0:  1142903b
0:0>CPMS1:  1142903b
0:0>CPMS2:  1142903b
0:0>CPMS3:  1142903b
0:0>CPMS4:  1142903b
0:0>CPMS5:  1142903b
0:0>Init I2C
0:0>Unquiesce Safari
0:0>Blast Fans
0:0>Set Trip Temp CPU 0 to 110C
0:0>Set Trip Temp CPU 1 to 110C
0:0>TUES DEC  18 3:44:00 GMT 18
0:0>Safari quick check
0:0> to IO-bridge_0
0:0>Safari full  check
0:0> to IO-bridge_0
0:0>Basic Memory Test.
0:0>Probe and Setup Memory
0:0>INFO: 4096MB Bank 0
0:0>INFO: 4096MB Bank 1
0:0>INFO: 4096MB Bank 2
0:0>INFO: 4096MB Bank 3
0:0>
0:0>Data Bitwalk on Master
0:0>Test Bank 0.
0:0>Test Bank 1.
0:0>Test Bank 2.
0:0>Test Bank 3.
0:0>Address Bitwalk on Master
0:0>
0:0>INFO: Addr walk mem test on CPU 0:0 Bank 0: . to
0001..
0:0>
0:0>INFO: Addr walk mem test on CPU 0:0 Bank 1: 0001. to
0002..
0:0>
0:0>INFO: Addr walk mem test on CPU 0:0 Bank 2: 0002. to
0003..
0:0>
0:0>INFO: Addr walk mem test on CPU 0:0 Bank 3: 0003. to
0004..
0:0>Set Mailbox
0:0>Setup Final DMMU Entries
0:0>Post Image Region Scrub
0:0>Run POST from Memory
0:0>Verifying checksum on copied image.
0:0>The Memory's CHECKSUM value is c3b1.
0:0>The Memory's Content Size value is 9b29c.
0:0>Success...  Checksum on Memory Validated.
1:0>Safari quick check
1:0> to IO-bridge_0
1:0>Safari full  check
1:0> to IO-bridge_0
1:0>Probe and Setup Memory
1:0>INFO:   No memory on cpu 1
1:0>Set Mailbox
1:0>Data Bitwalk on mem
1:0>Test Bank 0.
1:0>Test Bank 1.
1:0>Test Bank 2.
1:0>Test Bank 3.
1:0>Setup Final DMMU Entries
1:0>Map Slave POST to master memory
1:0>Print Mem Config
1:0>Caches : Icache is ON, Dcache is ON, Wcache is ON, Pcache is OFF.
0:0>Memory Block.
0:0>Print Mem Config
0:0>Caches : Icache is ON, Dcache is ON, Wcache is ON, Pcache is OFF.
0:0>Memory in non-interleave config:
0:0>Bank 0   4096MB : . 

Re: Sun Blade 1000

2018-05-28 Thread Tom Dial



On 05/20/2018 01:17 PM, Frank Scheiner wrote:
> Hi Rick, hi Tom,
> 
> On 05/17/2018 03:09 PM, Rick Leir wrote:
>> Tom, Frans
>> Yes, perhaps it is fixed. However there are not many eyes on this
>> problem, so maybe it's not fixed.
>>
>> There was a suggestion that this driver would only fail during
>> installation, but would be fine if you had booted from some SCSI disk,
>> and are mounting the FibreChannel disk from a running Linux.
> 
> I tried Debian GNU/Linux Sid on my 280R (in storage) yesterday, though I
> didn't do an installation but netbooted from a ready-made NFS root FS.
> 
> I can confirm that Sid works on the 280R and hence most likely will also
> work on a Blade 1000, but still the qla2xxx driver makes problems as
> soon as it begins working - as Frans already mentioned.
> 
> At first the qla2xxx module didn't work due to missing firmware, but
> after installing the missing firmware (from the `firmware-qlogic`
> package) and rebooting, the currently used kernel 4.16.5 panics soon
> (about 15 seconds) after the qla2xxx module is loaded (see below).
> 
> So when testing a Debian installation on a Blade 1000, one should also
> prepare an internal/external SCSI disk for installation. There might be
> a 68 pin SCSI connector plus power connector available below the disc
> drive. The qla2xxx module can be blacklisted with e.g.
> `modprobe.blacklist=qla2xxx` in the kernel command line if it creates
> problems during installation.

So it appears the QLogic HBA is not supported yet (hopefully to change
sometime).

I have a sizable storage server and a D-Link dge530-T gigabit ethernet
card. That opens the possibility of installing on iSCSI if:

a) the dge530-T is supported; and
b) iSCSI storage is supported.

Are these known to be true (or false)?

On the other hand, I do not think it got as far as the presumably faulty
fiber channel driver. The fail point showed as follows on my system:

"
[ 1.788117] [005ba17c] memblock_reserve+0x3c/0x80
[ 1.802074] [00c9ac0c] memblock_virt_alloc_internal+0xf8/0x19c
[ 1.817504] [00c9af10] memblock_virt_alloc_try_nid+0x58/0xa4
[ 1.832709] [00c8276c] start_kernel+0xa0/0x474
[ 1.846158] [00c85090] start_early_boot+0x284/0x294
[ 1.860172] [00a04d80] tlb_fixup_done+0x4c/0x6c
[ 1.873860] []   (null)
[ 1.886665] Disabling lock debugging due to kernel taint
[ 1.900395] Caller[005b9eb4]: memblock_add_range+0x134/0x300
[ 1.915487] Caller[005ba17c]: memblock_reserve+0x3c/0x80
[ 1.930089] Caller[00c9ac0c]:
memblock_virt_alloc_internal+0xf8/0x19c

[ 1.952322] Ca11er[00c9af10]: memblock_virt_alloc_try_nid+0x58/0xa4
[ 1.968210] Caller[00c8276c]: start_kernel+0xa0/0x474
[ 1.982510] Caller[00c85090]: start_early_boot+0x284/0x294
[ 1.997378] Caller[00a04d80]: tlb_fixup_done+0x4C/0x6c
[ 2.011610] Caller[]:   (null)
[ 2.024924] Instruction DUMP:
[ 2.024928]  921021bf
[ 2.035576]  7ff9bc41
[ 2.045258]  9010
[ 2.055113] <91d02005>
[ 2.064968]  c2022018
[ 2.074655]  80a08001
[ 2.084509]  3244
[ 2.094191]  68072001
[ 2.104046]  c459e010
[ 2.113893]
[ 2.132446] Kernel panic — not syncing: Attempted to kill the idle task!
[ 2.147988] Press Stop—A (L1—A) from sun keyboard or send break
[ 2.147988] twice on console to return to the boot prom
I 2.175042] ———[ end Kernel panic — not syncing: Attempted to kill the
idle task!
"

I would be grateful for any suggestions.

Tom Dial


> 
> ```
> [   45.422523] qla2xxx [:00:00.0]-0005: : QLogic Fibre Channel HBA
> Driver: 10.00.00.05-k.
> [...]
> [   45.698591] qla2xxx [0001:00:04.0]-001d: : Found an ISP2200 irq 17
> iobase 0x82de312a.
> [   45.812219] qla2xxx [0001:00:04.0]-0050:2: No matching ROM signature.
> [...]
> [   46.112936] qla2xxx [0001:00:04.0]-0065:2: Falling back to
> functioning (yet invalid -- WWPN) defaults.
> [   46.234884] qla2xxx [0001:00:04.0]-0069:2: NVRAM configuration failed.
>  St[   46.335599] qla2xxx 0001:00:04.0: firmware: direct-loading
> firmware ql2200_fw.bin
> [...]
> [   61.869433] ERROR(1): Cheetah error trap taken afsr[0800]
> afar[07fd00100040] TL1(0)
> [   61.987605] ERROR(1): TPC[103917c8] TNPC[103917cc] O7[103915f0]
> TSTATE[4411001602]
> [   62.086349] ERROR(1):
> [   62.086700] TPC
> [   62.193646] ERROR(1): M_SYND(0),  E_SYND(0)
> [   62.247720] ERROR(1): Highest priority error (0800) "Bus
> error response from system bus"
> [   62.367084] ERROR(1): D-cache idx[0] tag[]
> utag[] stag[]
> [   62.491042] ERROR(1): D-cache data0[]
> data1[] data2[] data3[
> ]
&g