[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Kernel Panic with updating



Hi James,

Thank you for your advice.
I have upgraded the system with an old working kernel.

Cheers,
Louis

2016-12-09 1:41 GMT+08:00 James Clarke <jrtc27@jrtc27.com>:
>> On 8 Dec 2016, at 17:31, Louis Liu <pttdog@gmail.com> wrote:
>>
>> Hi all,
>>
>> My system panics when updating packages.
>>
>> System:
>> Sun Netra T1-105
>> Linux FirstRangers 4.8.0-1-sparc64 #1 Debian 4.8.7-1 (2016-11-13)
>> sparc64 GNU/Linux
>>
>> The system panics every time with the command:
>> root@FirstRangers:~# dpkg --configure -a
>> Setting up systemd (232-7) ...
>> addgroup: The group `systemd-journal' already exists as a system group. Exiting.
>>
>> panic message:
>>
>> [575227.880355] CPU: 0 PID: 1 Comm: systemd Not tainted
>> 4.8.0-1-sparc64 #1 Debian 4.8.7-1
>> [575227.984570] task: fffff800360ac020 task.stack: fffff800360e0000
>> [575228.063583] TSTATE: 0000000011001600 TPC: 00000000007951e4 TNPC:
>> 00000000007951e8 Y: 1cc01dba    Not tainted
>> [575228.194131] TPC: <misc_open+0x64/0x180>
>> [575228.245660] g0: 0000000000000000 g1: 00000000102987e8 g2:
>> 0000000000000000 g3: 000000000000001d
>> [575228.361315] g4: fffff800360ac020 g5: 0000000000b3ac24 g6:
>> fffff800360e0000 g7: 0000000000000001
>> [575228.476949] o0: 0000000000b42cd8 o1: 000000000000000a o2:
>> 00000000000000eb o3: 0000000000000002
>> [575228.592584] o4: 000007feff91f270 o5: 0000000000000000 sp:
>> fffff800360e2f81 ret_pc: 00000000007951a0
>> [575228.712803] RPC: <misc_open+0x20/0x180>
>> [575228.764360] l0: 0000000000b42c00 l1: 000000031fdbe203 l2:
>> fffff80035e1bee0 l3: 0000000000000000
>> [575228.880012] l4: 0000000000010000 l5: 00000100000b4750 l6:
>> fffff800360e0000 l7: 0000000000000000
>> [575228.995645] i0: fffff80034483d50 i1: fffff80033d8f640 i2:
>> 0000000000b42c00 i3: 0000000000b42cf0
>> [575229.111281] i4: 00000000000000eb i5: 00000000102987d0 i6:
>> fffff800360e3031 i7: 00000000005b48b0
>> [575229.226931] I7: <chrdev_open+0x90/0x120>
>> [575229.279609] Call Trace:
>> [575229.312906]  [00000000005b48b0] chrdev_open+0x90/0x120
>> [575229.381658]  [00000000005acd0c] do_dentry_open+0x22c/0x360
>> [575229.454959]  [00000000005adccc] vfs_open+0x4c/0x80
>> [575229.519119]  [00000000005be928] path_openat+0x188/0x11c0
>> [575229.590143]  [00000000005c0ab0] do_filp_open+0x50/0xc0
>> [575229.658880]  [00000000005ae114] do_sys_open+0x134/0x220
>> [575229.728758]  [00000000005ae224] SyS_open+0x24/0x40
>> [575229.792930]  [00000000004060b4] linux_sparc_syscall+0x34/0x44
>
>
> Was there anything else about the type of panic? Does an older kernel
> work? If so, please try booting an older working kernel and update to
> 4.8.11-1, which has some sparc64 fixes.
>
> Regards,
> James
>


Reply to: