it
Tested it - yes, it fixes the boot.
--
Meelis Roos
-hang-1.jpg and
http://kodu.ut.ee/~mroos/powerpc-boot-hang-1.jpg .
--
Meelis Roos
.
--
Meelis Roos
an actual bug, the size of the copy is bounded by
the count parameter, which *doesn't* come from user space, it's hard
coded.
I suspect the logic is just to convoluted for GCC.
We should fix it somehow, but I haven't worked out what's the best option.
cheers
--
Meelis Roos
/ptrace.o] Error 1
make: *** [Makefile:1052: arch/powerpc/kernel] Error 2
--
Meelis Roos
avoid including headers from
> 'include/linux/' while still achieving the cleanup of the magic number.
>
> Fixes: faa16bc404d72a5 ("lib: Use existing define with polynomial")
> Reported-by: Meelis Roos
> Reported-by: kbuild test robot
> Suggested-by: Christophe LEROY
> Signed-off-by: Joel Stanley
Tested-by: Meelis Roos
--
Meelis Roos (mr...@linux.ee)
: No such file or directory
#include
^~~
--
Meelis Roos (mr...@linux.ee)
/kernel/ptrace.o] Error 1
--
Meelis Roos (mr...@linux.ee)
Mbps, full-duplex
[ 36.007833] gem 0002:20:0f.0 eth0: Pause is enabled (rxfifo: 10240 off: 7168
on: 5632)
[ 36.013215] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 43.522088] aty128fb 0000:00:10.0: Invalid PCI ROM header signature:
expecting 0xaa55, got 0x
--
Meelis Roos (mr...@linux.ee)
] [c0016230] do_page_fault+0x1bc/0x7e8
[ 140.519037] [d05a5f40] [c0012300] handle_page_fault+0x14/0x40
[ 140.519048] --- interrupt: 301 at 0xb78b6864
LR = 0xb78b6c54
--
Meelis Roos (mr...@linux.ee)
hdata.dma_mask;
> dev->ofdev.dev.parent = parent;
> dev->ofdev.dev.bus = _bus_type;
> dev->ofdev.dev.release = macio_release_dev;
Yes, it does - thank you!
Tested-by: Meelis Roos <mr...@linux.ee>
--
Meelis Roos (mr...@linux.ee)
412829] Instruction dump:
[1.418409] 939d 4bff6329 80010024 7fe3fb78 8361000c 83810010 7c0803a6
83a10014
[1.424201] 83c10018 83e1001c 38210020 4e800020 <0fe0> 4b84 7fa3eb78
3be0
[1.430020] ---[ end trace 89c0f4a91a110769 ]---
--
Meelis Roos (mr...@linux.ee)
Use alternate map
> for patch_instruction()")
> Reported-by: Meelis Roos <mr...@linux.ee>
> Cc: Balbir Singh <bsinghar...@gmail.com>
> Signed-off-by: Christophe Leroy <christophe.le...@c-s.fr>
> ---
> v2: Added missing asm/setup.h
It works - thank you! Tested on
of macro ‘PUT_64’
PUT_64(ph + PH_FILESZ, nnote2);
^~
arch/powerpc/boot/addnote.c:85:73: warning: right shift count >= width
of type [-Wshift-count-overflow]
#define PUT_64LE(off, v) (PUT_32LE((off), (v)), PUT_32LE((off) + 4, (v)
>> 32L))
^
arch/powerpc/boot/addnote.c:83:25: note: in definition of macro
‘PUT_16LE’
buf[(off) + 1] = ((v) >> 8) & 0xff)
^
arch/powerpc/boot/addnote.c:85:49: note: in expansion of macro
‘PUT_32LE’
#define PUT_64LE(off, v) (PUT_32LE((off), (v)), PUT_32LE((off) + 4, (v)
>> 32L))
^~~~
arch/powerpc/boot/addnote.c:95:5: note: in expansion of macro ‘PUT_64LE’
PUT_64LE(off, v))
^~~~
arch/powerpc/boot/addnote.c:211:3: note: in expansion of macro ‘PUT_64’
PUT_64(ph + PH_FILESZ, nnote2);
^~
--
Meelis Roos (mr...@linux.ee)
> Meelis Roos <mr...@linux.ee> a écrit :
>
> > > > For me, 4.13 worked and 4.14 hangs early during boot. Bisecting led to
> > > > the following commit. I had STRICT_KERNEL_RWX enabled when I met the
> > > > option. When I disabled STRICT_KERNEL_RW
> > For me, 4.13 worked and 4.14 hangs early during boot. Bisecting led to
> > the following commit. I had STRICT_KERNEL_RWX enabled when I met the
> > option. When I disabled STRICT_KERNEL_RWX, the same kernel booted fine.
>
> Can you please check that 4.13 boots properly with 'nobats' kernel
For me, 4.13 worked and 4.14 hangs early during boot. Bisecting led to
the following commit. I had STRICT_KERNEL_RWX enabled when I met the
option. When I disabled STRICT_KERNEL_RWX, the same kernel booted fine.
95902e6c8864d39b09134dcaa3c99d8161d1deea is the first bad commit
commit
> > I think these messages are harmless and expected. This device has no
> > x86 option ROM but a OpenFirmware one. This is likely unrelated to the
> > sddm crash.
>
> Yes, but after these crashes have happened for a while, vmalloc
> problems appear.
>
> sddm crash might be related to X
bout the same ROM
signature, or why the ROM signature is sometimes 0x and sometimes
0x1110 instead of x86 ROM signature (that clearly is not there,
but this is expected).
--
Meelis Roos (mr...@linux.ee)
> Meelis Roos <mr...@linux.ee> writes:
>
> > I was trying 4.13.0-rc5-00075-gac9a40905a61 on my PowerMac G4 with 1G
> > RAM and after some time of sddm respawning and X trying to restart,
> > dmesg is full of messages about vmap allocation failures.
>
> Did
as the first one I tried after 4.12 and it already had the
problem. Not sure about 4.12 to be honest, will soee some day.
--
Meelis Roos (mr...@linux.ee)
kB
VmallocChunk: 0 kB
--
Meelis Roos (mr...@linux.ee)
ic_key_true cpu_feature_keys[NUM_CPU_FTR_KEYS];
>
>
--
Meelis Roos (mr...@linux.ee)
] start_here+0x38/0x78
[0.00]
--
Meelis Roos (mr...@linux.ee)
.
--
Meelis Roos (mr...@linux.ee)
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
(CC'ing Dave and Meelis who from the git history *might* have HW access
to test a possible patch).
I do have the hardware and can test patches, but it usually takes
several days until I happen to go where it is and connect the machine.
--
Meelis Roos (mr...@linux.ee
'qla4_8xxx_pci_mem_write_direct':
drivers/scsi/qla4xxx/ql4_nx.c:788: error: implicit declaration of function
'writeq'
readq and writeq are defined in io.h but only when compiling for 64-bit
kernel. Adding manual #include linux/io.h does not help here.
--
Meelis Roos (mr...@linux.ee
ERROR: copy_page [fs/fuse/fuse.ko] undefined!
ERROR: empty_zero_page [fs/ext4/ext4dev.ko] undefined!
Try that patch at: http://patchwork.ozlabs.org/linuxppc/patch?id=18710
Fixes it for me.
Yes, this fixes it, thanks! Hopefully it is merged before 2.6.26.
--
Meelis Roos ([EMAIL
While compiling the current kernel on prep ppc:
MODPOST 703 modules
ERROR: copy_page [fs/fuse/fuse.ko] undefined!
ERROR: empty_zero_page [fs/ext4/ext4dev.ko] undefined!
--
Meelis Roos ([EMAIL PROTECTED])
___
Linuxppc-dev mailing list
Linuxppc-dev
' in declaration
of 'flush_dcache_page'
make[1]: *** [arch/ppc/kernel/ppc_ksyms.o] Error 1
--
Meelis Roos ([EMAIL PROTECTED])
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
it.
Any general guidelines or specific hints about that? I have looked
around in the code and some pieces are clearly PReP specific (setup,
pci, boot) but others seem wuite a bit mixed up with other subarches.
--
Meelis Roos ([EMAIL PROTECTED
0200 shift_map
008086d0 g O .data 0300 accent_table
00808ab0 g O .data 0300 TextCLUT
00807000 g O .data 002f cmd_preset
00808e98 g O .data 0004 lines
The only differences are __image_end, __ramdisk_begin and __ramdisk_end.
What more to look at?
--
Meelis
32 matches
Mail list logo
