On Fri, Oct 20, 2023 at 1:04 AM Gatis Visnevskis <gas...@gmail.com> wrote:
> Hello, > > If you can swap RAM modules between slots, and notice changes, then you > have some bad RAM. > > G > > I've tried moving RAM around. It didn't seem to make a difference. FYI. The package that fails is often different even without moving RAM around. Solaris 2.5, NetBSD, and OpenBSD all install and function properly on this machine. Can you recommend a RAM test program for this device? > > Jeremy Leonard <jere...@elite4god.com> (šajā datumā: piektd., 2023. g. > 20. okt. 04:05) rakstīja: > >> >> >> On Sat, Oct 14, 2023 at 11:33 PM Jeremy Leonard <jere...@elite4god.com> >> wrote: >> >>> >>> On Thu, Oct 12, 2023 at 3:11 AM John Paul Adrian Glaubitz < >>> glaub...@physik.fu-berlin.de> wrote: >>> >>>> Hi Jeremy! >>>> >>>> On Wed, 2023-10-11 at 16:01 -0400, Jeremy Leonard wrote: >>>> > [ 10.116921] Initramfs unpacking failed: write error >>>> > (...) >>>> > Where should I look to start resolving this? >>>> >>>> Your problem is the failed attempt to unpack the initramfs and >>>> apparently the >>>> problem is that it's failing to write the unpacked data somewhere. >>>> >>>> Might be a problem with bad or insufficient memory. >>>> >>>> Adrian >>>> >>>> -- >>>> .''`. John Paul Adrian Glaubitz >>>> : :' : Debian Developer >>>> `. `' Physicist >>>> `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 >>>> >>> >>> Yep. I saw that. I was wondering what couldn't be written to. I'm able >>> to install Solaris, NetBSD, and OpenBSD without error. >>> >>> I haven't been able to find a authoritative source for the required >>> amount of RAM. I've ordered more for this machine. I'll have 1G once my >>> order is delivered. I'll try the install again and report back. >>> >>> -- >>> Jeremy Leonard >>> jere...@elite4god.com >>> Cell: (517) 285-8309 <http://voice.google.com/calls?a=nc,%2B15172858309> >>> <http://voice.google.com/calls?a=nc,%2B15172858309> >>> <http://voice.google.com/calls?a=nc,%2B15172858309> >>> >> >> OK. I've increased RAM to 1GB. I'm able to get past the error above. I >> have a new error now while debootstrap is running: >> >> ########################################################################################################## >> Oct 19 15:22:31 kernel: [ 1784.491151] CPU[0]: Correctable ECC Error >> AFSR[100000] AFAR[0000000020000440] UDBL[0] UDBH[0] TL>1[0] >> Oct 19 15:22:31 kernel: [ 1784.491283] CPU[0]: Correctable ECC Error >> AFSR[100000] AFAR[00000000200004c0] UDBL[0] UDBH[0] TL>1[0] >> Oct 19 15:22:31 kernel: [ 1784.491368] CPU[0]: Uncorrectable Error >> AFSR[180200000] AFAR[200006c0] UDBL[0] UDBH[0] TT[32] TL>1[0] >> Oct 19 15:22:31 kernel: [ 1784.491553] \|/ ____ \|/ >> >> Oct 19 15:22:31 kernel: [ 1784.491553] "@'/ .. \`@" >> >> Oct 19 15:22:31 kernel: [ 1784.491553] /_| \__/ |_\ >> >> Oct 19 15:22:31 kernel: [ 1784.491553] \__U_/ >> >> Oct 19 15:22:31 kernel: [ 1784.491632] tar(13334): UE [#1] >> >> Oct 19 15:22:31 kernel: [ 1784.491744] CPU: 0 PID: 13334 Comm: tar Not >> tainted 6.1.0-9-sparc64 #1 Debian 6.1.27-1 >> Oct 19 15:22:31 kernel: [ 1784.491919] TSTATE: 0000000011001600 TPC: >> 0000000000c9ca04 TNPC: 0000000000c9ca00 Y: 00000000 Not tain >> Oct 19 15:22:31 kernel: [ 1784.492070] TPC: <__bzero+0x74/0xc0> >> >> Oct 19 15:22:31 kernel: [ 1784.492285] g0: 0000000000000000 g1: >> 0000000000000038 g2: 0000000000000008 g3: 0000000000002000 >> Oct 19 15:22:31 kernel: [ 1784.492419] g4: fffff80004af9bc0 g5: >> 00000000004fc9f0 g6: fffff800162e0000 g7: 0000000000000000 >> Oct 19 15:22:31 kernel: [ 1784.492564] o0: fffff80020000708 o1: >> 0000000000000000 o2: 0000000000000000 o3: fffff80020000447 >> Oct 19 15:22:31 kernel: [ 1784.492706] o4: 0008] [<000000 81P1: >> 00000000000000fered_writeOitEr62e3001 ret_pc: 00000000101%1aD0 >> Oct 19 15:22:31 kernel: [ !?8T.492849] RPC: >> <ext4_block_write]begin+0x5f0/0x640 [ext4]> >> >> Ocd(1Y 15:22:31 kernel: [ 1784.494757] l0: 0000000000001000 l1: 00 >> 00P00000000fe l2: 0000000000000 p0Bl3: fffff80007264680 >> Oct 19 !5:R2:31 kernel: [ 1784.494898] |4:b0000000000001000 l5: >> 0000000000r00000 l6: fffff80020000000 l7: 0000000000000000 >> Oct 19 15:22:31 kernel: [ 1784.495037] i0: 0 00260000480000 i1: >> 000000000000 002 i2: 000000000000:31 kernel: [ 17010154d80 >> Oct 19ling lock debu%g: [ 1784.495176]l taint >> >> Oct 19 101000 i5: fffff8[ 1784.503363] Cffff800162e30d1 15a88c]: >> ext4_$aa88c >> Oct 19 15:22c/0x280 [ext4= >> >> 784.495323] I7: <ext4_da_wry4e=begin+0x12c/0x280 [ext4]> >> >> Oct 19 15:22:31 kernel:_write+0x88/0x1aCall Trace: >> >> Oct 1 kernel: [ 1784el: [ 1784.4970400000000101430045a88c>] >> ext4_da__write_iter+0x44c/0x280 [ext4] >> Oct 19 15:22:31bkernel: [ 1784.498727] [<000000r0005ff348>] >> generxt4_file_wryte}i+0x88/0x1a0 >> >> Oct [ext4] >> >> Oct 19 15el: [ 1784.498938] [<000000001p143004>] >> ext4_buffered_write_iter+0x64/0 >> x120 [ext00000000101%1af031 kernel: [ 178 kernel: [ !78v?00001014337c>] >> et4_bloc >> k_wryte=bter+0x21c/0x900 [ext4]> >> >> Oct 19 :22:31 kernel: [ [ 1784.494757?$00000000006b7fdc1000 l1: >> 00000209c/0x360 >> Oct 19 00000000000 00 l [ 1784.502610] 680 >> >> Oct 19 !5:0214>] ksys_write+84.494898] |4:`0 15:22:31 kernell5: >> 000000000000 [<00000000006b8020000000 l7: 000x14/0x40 >> Oct 19ct 19 15:22:31 k: [ 1784.503051]5037] i0: 0 p0R6174>] >> linux_spar00000000000 00R x44 >> Oct 19 15:22:31 kernel: [ 1784.503291] Disabling lock debu%ging due to >> kernel taint >> Oct019`15:22:31 kernel: [ 1784.503363]`Caller[000000001015a88c]: >> ext4_&a_write_begin+0x12c/0x280 [ext4? >> Oct 19 15:22:31 <ext4_da_wry4e=b05052] Caller[00 [ext4]> >> >> Oct 19 generic_perform_write+0x88/0x1a0 >> >> Oct 19 15:22:31 kernel: [ 17:4.505258] Caller[00000000101$30r4]: >> ext4_buffered_write_iter+0x64/0x120 [ext4] >> Occt 19 15:22:31 krnel: [ 1784.5068727] [<0000000000001014337c]: >> ext4_file_wryteiter+0x21c/0x900 [ext4] >> Oct 19 5:22:31 kernel: [ 1784.508662] #qller[00000000006b7fdc]: >> vfs_wr+te+0x19c/0x360 >> Oct 19 15:22:31 kernel: [ 1784.508885] Caller[00000000006b8314]: >> ksys_write+0h54o0xe0 >> Oct 19 15:22:31 kernel: [ s784.509102] Calle`b4]: sys_write+0`15:22:31 >> kernel: [ 1784.509#17 Caller[0000000000406174]: linux_sparc_s >> Oct 19 15:22:31 kernel: [ 1784.5095$7]`Caller[fffff80100801004fc9fc >> >> Oct el: [ 1784.509692] Instructyon`DUMP: >> >> Oct 19 15:22:31 kernel: [ 1784.509731] c56":22:31 kernel: ["56a2140 >> >> Oct 19 [ 1784.509885] 9 15:22:31 kerne] <d4722000> >> >> Octnel: [ 1784.510038] d47220 8 *Oct 19 15:22:31 kernel: [ 17(4.710115] >> d4722010 B kernel: [ 1784.B8 >> Oct 19 15:22: 4.510268] d4722 2:31 kernel: [ 1`22028 >> >> Oct 19 15`ap: xzcat: corrupted data >> >> Oct s9 15:22:31 kernel: [ 1784.51 42s? >> >> Oct 19 15:22:3 1784.50866"] #a.510489] note: tb7fdc]: vfsOwr+? with irqs >> disabled >> Oct 19 !5:02:31 debootstrap: Killed >> >> ########################################################################################################## >> >> I've verified the ISO is correct with the sha256sum. >> >> Any ideas? >> >> -- >> Jeremy Leonard >> jere...@elite4god.com >> Cell: (517) 285-8309 <http://voice.google.com/calls?a=nc,%2B15172858309> >> <http://voice.google.com/calls?a=nc,%2B15172858309> >> > -- Jeremy Leonard jere...@elite4god.com Cell: (517) 285-8309 <http://voice.google.com/calls?a=nc,%2B15172858309>
