do not stumble upon it like I did?
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
).
Bisection between 4.1 and 4.2 is possible but not easy since the
machines are usually actively used when I am near them.
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majo
).
Bisection between 4.1 and 4.2 is possible but not easy since the
machines are usually actively used when I am near them.
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majo
ee/~mroos/dm/dm.v120
http://kodu.ut.ee/~mroos/dm/dm.v210
http://kodu.ut.ee/~mroos/dm/dm.v240
http://kodu.ut.ee/~mroos/dm/dm.sb100
amd64 machine:
http://kodu.ut.ee/~mroos/dm/dm.x2100
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel&
ee/~mroos/dm/dm.v120
http://kodu.ut.ee/~mroos/dm/dm.v210
http://kodu.ut.ee/~mroos/dm/dm.v240
http://kodu.ut.ee/~mroos/dm/dm.sb100
amd64 machine:
http://kodu.ut.ee/~mroos/dm/dm.x2100
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel&
> On Sun, Oct 4, 2015 at 3:33 AM, Meelis Roos wrote:
> >> This is 4.3.0-rc1 on Sun E220R (dual-CPU sparc64). Sometimes it boots,
> >> sometimes it fails to boot with looping errors and finally a watchdog
> >> timeout. This console log from a failure. Config is b
> On Sun, Oct 4, 2015 at 3:33 AM, Meelis Roos <mr...@linux.ee> wrote:
> >> This is 4.3.0-rc1 on Sun E220R (dual-CPU sparc64). Sometimes it boots,
> >> sometimes it fails to boot with looping errors and finally a watchdog
> >> timeout. This console log from a
687015] Caller[004c7ab4]: SyS_finit_module+0x74/0xa0
> [ 110.758889] Caller[004061d4]: linux_sparc_syscall32+0x34/0x60
> [ 110.835949] Caller[70015738]: 0x70015738
> [ 110.891141] Instruction DUMP: 0100 0100 9de3bf50
> 8208600c 0ac04005 11002409 b210200
]: do_init_module+0x48/0x1e4
> [ 110.617242] Caller[004c7654]: load_module+0xf14/0x11e0
> [ 110.687015] Caller[004c7ab4]: SyS_finit_module+0x74/0xa0
> [ 110.758889] Caller[004061d4]: linux_sparc_syscall32+0x34/0x60
> [ 110.835949] Caller[70015738]: 0x70015738
> [
; > ACPICA commit c0b38b4c3982c2336ee92a2a14716107248bd941
>
> Thanks a lot for bisecting this!
>
> It will help if you file a bug entry at bugzilla.kernel.org agaist ACPI for
> this issue (please mark it as a regression) and attach the output of acpidump
> from the affected system to it.
D
> > ACPICA commit c0b38b4c3982c2336ee92a2a14716107248bd941
>
> Thanks a lot for bisecting this!
>
> It will help if you file a bug entry at bugzilla.kernel.org agaist ACPI for
> this issue (please mark it as a regression) and attach the output of acpidump
> fr
ty:-1 extents:1
across:1005564k
[7.113287] EXT4-fs (sda1): re-mounted. Opts: (null)
[7.402468] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[8.360798] loop: module loaded
[8.431688] it87: Found IT8712F chip at 0x290, revision 4
[ 8.431965] it87 it87.656: Detected broken BIOS defa
[8.431688] it87: Found IT8712F chip at 0x290, revision 4
[8.431965] it87 it87.656: Detected broken BIOS defaults, disabling PWM
interface
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
4.2.0 worked fine, 4.3.0-rc3-00042-g3225031 was the next one tested
after that and with this kernel, ACPI enabling fails. This is Pentium
III, 1 GHz, Intel 815 chipset, DMI tells something about "Packard Bell
NEC" as the mainboard type.
Full dmesg and config are below. What additional
4.2.0 worked fine, 4.3.0-rc3-00042-g3225031 was the next one tested
after that and with this kernel, ACPI enabling fails. This is Pentium
III, 1 GHz, Intel 815 chipset, DMI tells something about "Packard Bell
NEC" as the mainboard type.
Full dmesg and config are below. What additional
My trusty K6/430TX machine with ISA SB16 variant has worked fine until
4.2. However, in 4.3.0-rc1 and 4.3.0-rc3-00025-ge3be426 I get a null
pointer dereferencing BUG during SB16 initialization. Full dmesg and
config are below.
[0.00] Linux version 4.3.0-rc3-00025-ge3be426 (mroos@roos)
My trusty K6/430TX machine with ISA SB16 variant has worked fine until
4.2. However, in 4.3.0-rc1 and 4.3.0-rc3-00025-ge3be426 I get a null
pointer dereferencing BUG during SB16 initialization. Full dmesg and
config are below.
[0.00] Linux version 4.3.0-rc3-00025-ge3be426 (mroos@roos)
> > Yes, sorry - I applied the last chunk by hand because it was mangled by
> > the web UI, and added ti to a wrong struct.
> >
> > Now I tested it on top of 4.3.0-rc1. COmpiles, rebooted fine 6 times,
> > but now it hangs again, seems to be the same message:
> >
> > [ 107.143910] kobject
> > Yes, sorry - I applied the last chunk by hand because it was mangled by
> > the web UI, and added ti to a wrong struct.
> >
> > Now I tested it on top of 4.3.0-rc1. COmpiles, rebooted fine 6 times,
> > but now it hangs again, seems to be the same message:
> >
> > [ 107.143910] kobject
86] Caller[004de3c4]: do_init_module+0x48/0x1e4
[ 111.402806] Caller[004c7654]: load_module+0xf14/0x11e0
[ 111.472581] Caller[004c7ab4]: SyS_finit_module+0x74/0xa0
[ 111.544426] Caller[004061d4]: linux_sparc_syscall32+0x34/0x60
[ 111.621508] Caller[7
> On Tue, Sep 15, 2015 at 3:06 AM, Meelis Roos wrote:
> > This is 4.3.0-rc1 on Sun E220R (dual-CPU sparc64). Sometimes it boots,
> > sometimes it fails to boot with looping errors and finally a watchdog
> > timeout. This console log from a failure. Config is below.
> &
> On Tue, Sep 15, 2015 at 3:06 AM, Meelis Roos <mr...@linux.ee> wrote:
> > This is 4.3.0-rc1 on Sun E220R (dual-CPU sparc64). Sometimes it boots,
> > sometimes it fails to boot with looping errors and finally a watchdog
> > timeout. This console log from
44426] Caller[004061d4]: linux_sparc_syscall32+0x34/0x60
[ 111.621508] Caller[70015738]: 0x70015738
[ 111.676682] Instruction DUMP: 0100 0100 9de3bf50
8208600c 0ac04005 11002409 b2102003 1
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: sen
This is 4.3.0-rc1 on Sun E220R (dual-CPU sparc64). Sometimes it boots,
sometimes it fails to boot with looping errors and finally a watchdog
timeout. This console log from a failure. Config is below.
[0.00] PROMLIB: Sun IEEE Boot Prom 'OBP 3.31.0 2001/07/25 20:31'
[0.00]
This is my trusty K6 computer. It ran fine up to 4.2 but in 4.3-rc1, I
get a Warning from sb16 sound initailization, from DMA allocation.
Config is also below.
[0.00] Linux version 4.3.0-rc1 (mroos@roos) (gcc version 5.2.1 20150808
(Debian 5.2.1-15) ) #9 Mon Sep 14 02:10:37 EEST 2015
This is my trusty K6 computer. It ran fine up to 4.2 but in 4.3-rc1, I
get a Warning from sb16 sound initailization, from DMA allocation.
Config is also below.
[0.00] Linux version 4.3.0-rc1 (mroos@roos) (gcc version 5.2.1 20150808
(Debian 5.2.1-15) ) #9 Mon Sep 14 02:10:37 EEST 2015
This is 4.3.0-rc1 on Sun E220R (dual-CPU sparc64). Sometimes it boots,
sometimes it fails to boot with looping errors and finally a watchdog
timeout. This console log from a failure. Config is below.
[0.00] PROMLIB: Sun IEEE Boot Prom 'OBP 3.31.0 2001/07/25 20:31'
[0.00]
The first crash seems to be related to radeon_hotplug_work_func during
> > radeon initialization.
>
> Looks like a race at startup, I've sent a fix to dri-devel that should work.
It works. Applied on top of 4.2.0-rc7-00071-g0bad909 and everything
seems to work fine, no crash.
--
Mee
to radeon_hotplug_work_func during
radeon initialization.
Looks like a race at startup, I've sent a fix to dri-devel that should work.
It works. Applied on top of 4.2.0-rc7-00071-g0bad909 and everything
seems to work fine, no crash.
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send
> On 19 August 2015 at 00:28, Meelis Roos wrote:
> > Hi, I tried 4.2-rc7 and todays 4.2-rc7+git on a P4 PC with Intel 850
> > chipset and old Radeon graphics. The machine crashes during boot and
> > starts spamming dmesg as fast as it scrolls. Netconsole caught the
> &g
On 19 August 2015 at 00:28, Meelis Roos mr...@linux.ee wrote:
Hi, I tried 4.2-rc7 and todays 4.2-rc7+git on a P4 PC with Intel 850
chipset and old Radeon graphics. The machine crashes during boot and
starts spamming dmesg as fast as it scrolls. Netconsole caught the
dmesg. 4.1.0 worked
start and even recompiled known good
version was broken, so I tried make mrproper and it cured the problem.
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More major
Hi, I tried 4.2-rc7 and todays 4.2-rc7+git on a P4 PC with Intel 850
chipset and old Radeon graphics. The machine crashes during boot and
starts spamming dmesg as fast as it scrolls. Netconsole caught the
dmesg. 4.1.0 worked fine.
The first crash seems to be related to radeon_hotplug_work_func
was broken, so I tried make mrproper and it cured the problem.
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read
Hi, I tried 4.2-rc7 and todays 4.2-rc7+git on a P4 PC with Intel 850
chipset and old Radeon graphics. The machine crashes during boot and
starts spamming dmesg as fast as it scrolls. Netconsole caught the
dmesg. 4.1.0 worked fine.
The first crash seems to be related to radeon_hotplug_work_func
in 4.2.0-rc7.
> Screenshot at http://kodu.ut.ee/~mroos/x346-crash.jpg
>
> Config and dmesg from working 4.2.0-rc2-00077-gf760b87 are below. I can
> not bisect until next week.
Will try to bisect, slowly as I have no remote management on that
server.
--
Meelis Roos (mr...@linux.ee) ht
at http://kodu.ut.ee/~mroos/x346-crash.jpg
Config and dmesg from working 4.2.0-rc2-00077-gf760b87 are below. I can
not bisect until next week.
Will try to bisect, slowly as I have no remote management on that
server.
--
Meelis Roos (mr...@linux.ee) http://www.cs.ut.ee/~mroos
IBM Xseries 346, 2x Xeon 3.2 HT 64-bit (4 threads total, P4 era Xeon),
5G RAM. All kernels so far worked fine, last working one was
4.2.0-rc2-00077-gf760b87. First kernel tested after that was
v4.2-rc6-20-g7a834ba and that one crashes on boot.
Screenshot at
IBM Xseries 346, 2x Xeon 3.2 HT 64-bit (4 threads total, P4 era Xeon),
5G RAM. All kernels so far worked fine, last working one was
4.2.0-rc2-00077-gf760b87. First kernel tested after that was
v4.2-rc6-20-g7a834ba and that one crashes on boot.
Screenshot at
t; > cases. Even for pmd that are not attached to the pgd.
> > So 'free_pages' can never be called anymore, leading to a memory leak.
>
> That's really great!!! Thanks for spotting this!
>
> I assume this fixes the leak which killed our debian buildds with OOM
> after an upti
'free_pages' can never be called anymore, leading to a memory leak.
That's really great!!! Thanks for spotting this!
I assume this fixes the leak which killed our debian buildds with OOM
after an uptime of 1-4 days and which only happened since kernel 4.0.
Meelis Roos reported the issue
Tried v4.2-rc2-77-gf760b87 on one of my older machines (K6-2 with custom
config) and got the following link error:
Building modules, stage 2.
MODPOST 385 modules
ERROR: "tick_broadcast_oneshot_control" [drivers/acpi/processor.ko] undefined!
scripts/Makefile.modpost:90: recipe for target
Tried v4.2-rc2-77-gf760b87 on one of my older machines (K6-2 with custom
config) and got the following link error:
Building modules, stage 2.
MODPOST 385 modules
ERROR: tick_broadcast_oneshot_control [drivers/acpi/processor.ko] undefined!
scripts/Makefile.modpost:90: recipe for target
> > [ 31.898697] Running resizable hashtable tests...
> > [ 31.898915] Adding 2048 keys
> > [ 31.952911] Traversal complete: counted=17, nelems=2048, entries=2048
> > [ 31.953004] Test failed: Total count mismatch ^^^
> > [ 32.022676] Traversal complete: counted=17, nelems=2048,
[ 31.898697] Running resizable hashtable tests...
[ 31.898915] Adding 2048 keys
[ 31.952911] Traversal complete: counted=17, nelems=2048, entries=2048
[ 31.953004] Test failed: Total count mismatch ^^^
[ 32.022676] Traversal complete: counted=17, nelems=2048, entries=2048
This is 4.1 on sparc64 - one of my boxes that happens to have most
runtime test left on from some debugging effort. In 4.0 it was fine, 4.1
gives this in dmesg:
[ 31.898697] Running resizable hashtable tests...
[ 31.898915] Adding 2048 keys
[ 31.952911] Traversal complete: counted=17,
This is 4.1 on sparc64 - one of my boxes that happens to have most
runtime test left on from some debugging effort. In 4.0 it was fine, 4.1
gives this in dmesg:
[ 31.898697] Running resizable hashtable tests...
[ 31.898915] Adding 2048 keys
[ 31.952911] Traversal complete: counted=17,
silent on this one, I will send it to you:
Revert change that breaks QLA2XXX on big-endian systems,
__constant_cpu_to_le16() is still needed.
Signed-off-by: Meelis Roos
diff --git a/drivers/scsi/qla2xxx/qla_fw.h b/drivers/scsi/qla2xxx/qla_fw.h
index 42bb357..88d3143 100644
--- a/drivers/scsi/qla2xxx/q
it to you:
Revert change that breaks QLA2XXX on big-endian systems,
__constant_cpu_to_le16() is still needed.
Signed-off-by: Meelis Roos mr...@linux.ee
diff --git a/drivers/scsi/qla2xxx/qla_fw.h b/drivers/scsi/qla2xxx/qla_fw.h
index 42bb357..88d3143 100644
--- a/drivers/scsi/qla2xxx/qla_fw.h
+++ b
I recently activated netconsole on one of my computers to debug boot
crash with big IOMMU size. Left netconsole on and got the BUG about
sleeping function called from invalid context when netconsole is doing
printk during nouveau initialization. Full dmesg and .configare
below.
[
[ 26.446275] [] entSys+0xa4/0xc0
[ 26.446275] ---[ end trace 613e3a954cbbda7f ]---
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.
[ 26.446275] [fc3c7eac] find_vma+0x2c/0xc0
[ 26.446275] [fc31112c] entMM+0x9c/0xc0
[ 26.446275] [fc3ef804] SYSC_stat64+0x34/0x70
[ 26.446275] [fc3114d4] entSys+0xa4/0xc0
[ 26.446275] ---[ end trace 613e3a954cbbda7f ]---
--
Meelis Roos (mr...@linux.ee
I recently activated netconsole on one of my computers to debug boot
crash with big IOMMU size. Left netconsole on and got the BUG about
sleeping function called from invalid context when netconsole is doing
printk during nouveau initialization. Full dmesg and .configare
below.
[
I have a computer where I had noticed that I must not turn on IOMMU in
the BIOS, or Linux would crash on boot. The computer is Sun Ultra 20
workstation with dual-core 1st gen Opteron (175) and Nvidia CK804
chipset and 4G RAM. So IOMMU never worked for me before.
I investigated it more today -
I have a computer where I had noticed that I must not turn on IOMMU in
the BIOS, or Linux would crash on boot. The computer is Sun Ultra 20
workstation with dual-core 1st gen Opteron (175) and Nvidia CK804
chipset and 4G RAM. So IOMMU never worked for me before.
I investigated it more today -
I repaired my Sun Fire V240 after a long downtime and tested the latest
kernels on it.
4.0 shows a warning, 4.1.0-rc2-00117-g3e0283a still has it. The warning
happened last during aptitude run and did not disturb actual working so
far.
Seems to be related to hugetlb_setup.
.config is also
I repaired my Sun Fire V240 after a long downtime and tested the latest
kernels on it.
4.0 shows a warning, 4.1.0-rc2-00117-g3e0283a still has it. The warning
happened last during aptitude run and did not disturb actual working so
far.
Seems to be related to hugetlb_setup.
.config is also
nontrivial emerge compilation loop kills
> > the smaller box).
>
> I've also had problems with 4.0. I had HPMC after a few hours on rp3440.
My rp3440 worked fine for emerge world - maybe an hour or some hours.
Because of 12G RAM, it did not run out of memory.
--
Meelis Roos (mr...@li
the smaller box).
I've also had problems with 4.0. I had HPMC after a few hours on rp3440.
My rp3440 worked fine for emerge world - maybe an hour or some hours.
Because of 12G RAM, it did not run out of memory.
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line
ry linking info.
The results are at
http://kodu.ut.ee/~mroos/slabtop-log
http://kodu.ut.ee/~mroos/meminfo-log
http://kodu.ut.ee/~mroos/vmstat-log
Anything else I can provide to pinpoint it?
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line "unsubscri
info.
The results are at
http://kodu.ut.ee/~mroos/slabtop-log
http://kodu.ut.ee/~mroos/meminfo-log
http://kodu.ut.ee/~mroos/vmstat-log
Anything else I can provide to pinpoint it?
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
: mounted filesystem without journal. Opts: (null)
[ 381.894633] systemd-journald[70]: Received request to flush runtime journal
from PID 1
[ 387.067316] eth0: Link is up using internal transceiver at 100Mb/s, Full
Duplex.
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line &q
] systemd-journald[70]: Received request to flush runtime journal
from PID 1
[ 387.067316] eth0: Link is up using internal transceiver at 100Mb/s, Full
Duplex.
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
> On Mon, Nov 03, 2014 at 11:32:14PM +0200, Meelis Roos wrote:
> > Yes. I took the same 3.18.0-rc1-00422-g2cc9188-dirty kernel that had
> > just this patch reverted, it started the controller fine, detected disk,
> > mounted root, started multiple tasks and then some time af
On Mon, Nov 03, 2014 at 11:32:14PM +0200, Meelis Roos wrote:
Yes. I took the same 3.18.0-rc1-00422-g2cc9188-dirty kernel that had
just this patch reverted, it started the controller fine, detected disk,
mounted root, started multiple tasks and then some time after startin
exim it just
c9188-dirty kernel that had
just this patch reverted, it started the controller fine, detected disk,
mounted root, started multiple tasks and then some time after startin
exim it just hangs. This is consisten with what I saw during bisection.
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from
, started multiple tasks and then some time after startin
exim it just hangs. This is consisten with what I saw during bisection.
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo
This may not be the only problem - when bisecting, I also came to commits
that got past this step but hang after about 165 seconds of uptime while
running userspace startup scripts. But let that be another issue at the
moment.
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list
at the
moment.
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
es, there are no doubt other RCU bugs waiting to be found. ;-)
I reproduced the problem on Thinkpad T400 with Core2Duo and Chromium
startup failing, and your patch fixes that.
Tested-by: Meelis Roos
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line "unsubscribe l
t I an using remote sessions only for now (no desktop).
At least it's not clearly broken :)
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vg
an using remote sessions only for now (no desktop).
At least it's not clearly broken :)
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo
on Thinkpad T400 with Core2Duo and Chromium
startup failing, and your patch fixes that.
Tested-by: Meelis Roos mr...@linux.ee
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo
Config is below.
> > [ 960.346611] INFO: task kworker/u16:0:6 blocked for more than 120 seconds.
> > [ 960.346616] Tainted: GW 3.18.0-rc1-00221-gc3351df #150
> > [ 960.346618] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
> > this message.
> > [ 960.346621]
> > I can reproduce and I know what the problem is, fixed patch coming up
> > shortly.
>
> Ok, please test this patch below.
Thank you, it works fine on my V210, V440 and newly added V245.
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line "u
I can reproduce and I know what the problem is, fixed patch coming up
shortly.
Ok, please test this patch below.
Thank you, it works fine on my V210, V440 and newly added V245.
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line unsubscribe linux-kernel
Config is below.
[ 960.346611] INFO: task kworker/u16:0:6 blocked for more than 120 seconds.
[ 960.346616] Tainted: GW 3.18.0-rc1-00221-gc3351df #150
[ 960.346618] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables
this message.
[ 960.346621] kworker/u16:0
This is first real test on a computer where 3.17 did hang. Fist the hung
task info, then full dmesg.
[ 960.346611] INFO: task kworker/u16:0:6 blocked for more than 120 seconds.
[ 960.346616] Tainted: GW 3.18.0-rc1-00221-gc3351df #150
[ 960.346618] "echo 0 >
; >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> > the body of a message to majord...@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> ---end quoted text---
>
--
Meelis R
linux-scsi in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
---end quoted text---
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord
This is first real test on a computer where 3.17 did hang. Fist the hung
task info, then full dmesg.
[ 960.346611] INFO: task kworker/u16:0:6 blocked for more than 120 seconds.
[ 960.346616] Tainted: GW 3.18.0-rc1-00221-gc3351df #150
[ 960.346618] echo 0
25.288559] clockevent: mult[3126e98] shift[32]
[ 25.342813] Console: colour dummy device 80x25
[ 25.395990] console [tty0] enabled
[ 25.436726] bootconsole [earlyprom0] disabled
ERROR: Last Trap: Memory Address not Aligned
ok
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send
] clockevent: mult[3126e98] shift[32]
[ 25.342813] Console: colour dummy device 80x25
[ 25.395990] console [tty0] enabled
[ 25.436726] bootconsole [earlyprom0] disabled
ERROR: Last Trap: Memory Address not Aligned
ok
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line
0.068000] [] show_stack+0x90/0xc0
[0.068000] sp=a00100b47a00
bsp=a00100b41198
[0.068000] Disabling lock debugging due to kernel taint
[0.184005] Kernel panic - not syncing: Attempted to kill the idle task!
--
Meelis Roos (mr...@linux.ee)
--
To unsubscri
] sp=a00100b47a00
bsp=a00100b41198
[0.068000] Disabling lock debugging due to kernel taint
[0.184005] Kernel panic - not syncing: Attempted to kill the idle task!
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line
>
> Works fine with 3.17.0-09670-g0429fbc + fault patch.
>
> Will try current git next to find any new problems :)
Works on all 3 machines, with latest git (only had to apply the no-ipv6
patch on one of them). Thank you for the good work!
--
Meelis Roos (mr...@linux.ee)
--
To unsubs
0-g0429fbc + fault patch.
Will try current git next to find any new problems :)
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/major
gt; patch fails on 3 machines (all I tried). Will try bisecting later if I
> get time.
Dave Miller identified it as a sparc64-specific problem with
CONFIG_SCHED_STACK_END_CHECK in another thread and his fix is working
for me.
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this l
> From: Meelis Roos
> Date: Fri, 17 Oct 2014 00:38:20 +0300 (EEST)
>
> > arch/sparc/kernel/setup_64.c is the only culprit.
> >
> > Attached are 2 versions of the object file as of v3.17-rc1-22-g480cadc
> > that I tested.
>
> Just to confirm, a gcc-4.9 c
From: Meelis Roos mr...@linux.ee
Date: Fri, 17 Oct 2014 00:38:20 +0300 (EEST)
arch/sparc/kernel/setup_64.c is the only culprit.
Attached are 2 versions of the object file as of v3.17-rc1-22-g480cadc
that I tested.
Just to confirm, a gcc-4.9 compiled kernel works if just setup_64.c
machines (all I tried). Will try bisecting later if I
get time.
Dave Miller identified it as a sparc64-specific problem with
CONFIG_SCHED_STACK_END_CHECK in another thread and his fix is working
for me.
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line unsubscribe
current git next to find any new problems :)
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
.
Will try current git next to find any new problems :)
Works on all 3 machines, with latest git (only had to apply the no-ipv6
patch on one of them). Thank you for the good work!
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
-09670-g0429fbc it explodes with
scheduler BUG - just reported to LKML + sched maintainers.
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://
x_sparc_syscall32+0x34/0x60
Caller[0085f5c0]: schedule+0x60/0x80
Caller[0045d318]: do_exit+0x938/0xa80
Caller[00428be8]: die_if_kernel+0x288/0x2e0
Caller[00428dd0]: bad_trap+0x70/0x100
Caller[004220b0]: tl0_resv104+0x30/0xa0
Caller[0085ec2c]: __schedule+0x
]: SyS_waitpid+0x10/0x20
Caller[004061f4]: linux_sparc_syscall32+0x34/0x60
Caller[00014ef4]: 0x14ef4
Instruction DUMP: 92102a8e 7fef241d 90122250 91d02005 05000800 82284002
80a06001 02680008 0100
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line
reported to LKML + sched maintainers.
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
stood I confused 2 problems with the same subject. You
are talking about SIGBUS problem that is also happening on IIIi, my last
comment is about gcc-4.9 problem so please just ignore it.
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel&quo
> I just reproduced this on my Sun Blade 2500, so it can trigger on
> UltraSPARC-IIIi
> systems too.
I looked it up - V210 and V440 are also IIIi, not plain III. So I do not
have information about real USIII, sorry for confusion.
--
Meelis Roos (mr...@linux.ee)
--
To unsubsc
illed chekroot
during startup, for some shells under some circumstances, for some sshd.
--
Meelis Roos (mr...@linux.ee)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.
501 - 600 of 1001 matches
Mail list logo
