Chiwu Yung wrote:
> Hello Sir, i am using cpu i7 7700k kaby lake, i have no overclock the
> CPU but i think i7 7700k come across with Ethernet crash issue. Don't
> know why it will keeping crash.
> I tested the kernel since 4.8 - 4.12 almost 2-3months and i can see
> that the issue is still exis
On Wed, Aug 30, 2017 at 04:16:54PM +0800, Chiwu Yung wrote:
> Hello Sir, i am using cpu i7 7700k kaby lake, i have no overclock the
> CPU but i think i7 7700k come across with Ethernet crash issue. Don't
> know why it will keeping crash.
> I tested the kernel since 4.8 - 4.12 almost 2-3months and
Hello Sir, i am using cpu i7 7700k kaby lake, i have no overclock the
CPU but i think i7 7700k come across with Ethernet crash issue. Don't
know why it will keeping crash.
I tested the kernel since 4.8 - 4.12 almost 2-3months and i can see
that the issue is still exist.
Kernel error then the Ethe
On Fri, 25 Jan 2008 09:25:59 EST, Lennart Sorensen said:
> Personally I just don't bother with memtest anymore. The only thing it
> tells you is that you have errors or that you might have errors but it
> didn't find them. It never tells you that you do not have errors and it
> often does miss t
On Fri, Jan 25, 2008 at 11:17:22AM +0100, Tobias Winter wrote:
> Did so. After quite some time memtest found errors. Switching the
> module in question resolved the issue. Thanks for the great feedback :)
Often removing half the ram, running a kernel compile, see if it
segfaults, then repeat with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Lennart Sorensen wrote:
> On Wed, Jan 23, 2008 at 05:07:48PM -0800, Stephen Hemminger wrote:
>> Sounds like bad memory. Run memtest for at least 24hrs.
>
Did so. After quite some time memtest found errors. Switching the
module in question resolved th
On Wed, Jan 23, 2008 at 05:07:48PM -0800, Stephen Hemminger wrote:
> Sounds like bad memory. Run memtest for at least 24hrs.
Or better yet take out half the ram and see what happens, then try the
other half and see if you have a bad stick.
Also check the power supply in case it is underpowered or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Stephen Hemminger wrote:
>> [2.] Full description of the problem/report:
>> I upgraded my system to fairly new hardware and find myself unable to
>> compile any kernel source and the system panics under high load e.g.
>> resyncing a RAID or building
> drivers/acpi/pci_bind.c: In function 'acpi_pci_unbind'::0:
> internal compiler error: Segmentation fault
> Depending on which kernel i build, it fails on different things.
Seems like a classic symptom of some sort of hardware fault/memory corruption...
> I tried disabling HPET and VT in the
On Thu, 24 Jan 2008 01:14:35 +0100
Tobias Winter <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hi folks, I'm sending the bug report here, since i have no idea where
> else to send it. I hope it is helping.
>
>
> [1.] One line summary of the problem:
> The ke
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi folks, I'm sending the bug report here, since i have no idea where
else to send it. I hope it is helping.
[1.] One line summary of the problem:
The kernel panics under high CPU/IO load, compilers segfault, mdadm
used to do so, too.
[2.] Full de
> > It looks like it panics during a mem_cpy but I know its
> > difficult to tell just by the output.
> >
> > I get a code: f3 a4 c3 66 66 66 90 66 66 66 90 66 66 66 90 66
> >
> > The problem appears very reproducable so I can provide more
> > information upon request.
>
> What does the rest of
Hi,
> It should have been printed right after the output you posted.
>
> Anyway, the first step is to reproduce it with a non tainted kernel.
There was no call trace after what I saw. No big deal.
I am now working to reproduce the error with a non tainted kernel.
--
Lee
[EMAIL PROTECTED]
1
On Fri, 2005-07-15 at 14:24 -0500, Lee wrote:
> Hi,
>
> > > [20975.978911] PREEMPT SMP DEBUG_PAGEALLOC
> > > [20976.029194] Modules linked in: vmnet vmmon nvidia
> > > [20976.090907] CPU:695757158
> > > [20976.090909] EIP:0060:[]Tainted: P VLI
> >
> > Please reproduce the bug with
Hi,
> > [20975.978911] PREEMPT SMP DEBUG_PAGEALLOC
> > [20976.029194] Modules linked in: vmnet vmmon nvidia
> > [20976.090907] CPU:695757158
> > [20976.090909] EIP:0060:[]Tainted: P VLI
>
> Please reproduce the bug without these proprietary modules loaded. And
> make sure to incl
On Fri, 2005-07-15 at 14:04 -0500, Lee wrote:
> [20975.978911] PREEMPT SMP DEBUG_PAGEALLOC
> [20976.029194] Modules linked in: vmnet vmmon nvidia
> [20976.090907] CPU:695757158
> [20976.090909] EIP:0060:[]Tainted: P VLI
Please reproduce the bug without these proprietary modules lo
Hello,
Motherboard: Tyan Tiger 230T
Memory: 1.5GB
CPU: 2 x 1.13GHz P3
kernel config file attached.
[20975.810849] [ cut here ]
[20975.871509] kernel BUG at kernel/sched.c:2579!
[20975.929776] invalid operand: [#1]
[20975.978911] PREEMPT SMP DEBUG_PAGEALLOC
[20976.0
tor 2005-07-14 klockan 10:10 -0700 skrev Paul Vander Griend:
> System:
> Motherboard = Tyan K8WE
> Processor = 2x Opteron 250
> Memory = 8GB ECC Registered
>
> On all of the recent release candidates except for
> 2.6.13-rc2-git2 the kernel panics while booting. These
> versions include 2.6.13-rc2-
System:
Motherboard = Tyan K8WE
Processor = 2x Opteron 250
Memory = 8GB ECC Registered
On all of the recent release candidates except for
2.6.13-rc2-git2 the kernel panics while booting. These
versions include 2.6.13-rc2-git* (* != 2 ) and 2.6.13-rc3.
I also want to mention that I am using gcc 3
Hi
this was a bug in 2.2.15 you could do
while(1) { connect() }
and it would crash the kernel it was fixed by 2.2.16
In local.linux-kernel-list, you wrote:
>I am enclosing a section of code that crashes the 2.2.15 kernel
>repeatedly. My system is a 266 Intel P2 with 128Mb ram. The
>crash is
On Tue, Apr 03, 2001 at 01:53:26AM -0700, Allen Ashley wrote:
> ---
> soval=fcntl(s,F_GETFL,0);
> ioval=fcntl(0,F_GETFL,0);
> fcntl(s,F_SETFL,soval|O_NONBLOCK);
> fcntl(0,F_SETFL,ioval|O_NONBLOCK);
> cwait=WAITCONNECT;
> *chin=0;
> do{
>
I am enclosing a section of code that crashes the 2.2.15 kernel
repeatedly. My system is a 266 Intel P2 with 128Mb ram. The
crash is caused by the connect statement. It does not crash
if the socket is in BLOCKING mode. My distribution is Slack 7.0
if that matters.
22 matches
Mail list logo
