FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 05-19-2008, 07:33 PM
Hugo Vanwoerkom
 
Default freezes in 2.6.25

Hi,

Just FYI, I went back to 2.6.24-1-686.
I had 2.6.25-1-686 + 2.6.25-2-686 running for 9 days and had 3 hard
freezes: nothing moved, no kbd, no mouse.

The logs showed nothing up to the moment.
That hasn't happened since I bought this mobo 3 years ago.

It could be my hardware setup:
2 ATA disks, 2 USB external drives, one ATA, one SATA.

Hugo


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 05-19-2008, 11:16 PM
"thveillon.debian"
 
Default freezes in 2.6.25

Hugo Vanwoerkom a écrit :

Hi,

Just FYI, I went back to 2.6.24-1-686.
I had 2.6.25-1-686 + 2.6.25-2-686 running for 9 days and had 3 hard
freezes: nothing moved, no kbd, no mouse.

The logs showed nothing up to the moment.
That hasn't happened since I bought this mobo 3 years ago.

It could be my hardware setup:
2 ATA disks, 2 USB external drives, one ATA, one SATA.

Hugo

I had the same problem using "bigmem" on an Asus P5K-E mobo, c2duo and
4gb ram. On the same box the -amd64 is running fine. I tried many
compilation options, and I even got the freezes with a vanilla kernel.
It's still the same for 2.6.25-3.
I filled a bug report but it didn't catch a lot of interest so far... I
thought I was the only one to get that.


The only output I got was :

=======================
BUG: soft lockup - cpu#0 stuck for 61s! [cc:6671]

Pid:6671, comm: cc Not tainted (2.6.25-1-686-bigmem #1)
EIP: 0060:[<c010f82d>] EFLAGS: 00000202 CPU: 0
EIP is at native_flush_tlb_others+0x73/0x94
EAX: 00000202 EBX: f6824900 ECX: ffffb300 EDX: 000008fd
ESI: ffffffff EDI: f6df2804 EBP: f64ea000 ESP: f64ebf40
DS: 007b ES: 007b FS: 00g8 GS: 0000 SS: 0068
CR0: 8005003b CR2: 400cfeb4 CR3: 0035e000 CR4: 000006f0
DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
DR6: ffff0ff0 DR7: 00000400
[<c010f7b5>] ? flush_tlb_mm+0x5b/0x60
[<c0167657>] ? exit_mmap+0x98/0xce
[<c0120d1e>] ? mmput+0x20/0x75
[<c01256c5>] ? do_exit+0x1e5/0x5c9
[<c0125b14>] ? do_group_exit+0x6b/0x82
[<c01047e4>] ? sysenter_past_esp+0x6d/0xa5
=======================

It's happening even with no xserver started on non tainted kernel.

What's your hardware precisely ?


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 05-20-2008, 01:54 PM
Hugo Vanwoerkom
 
Default freezes in 2.6.25

thveillon.debian wrote:

Hugo Vanwoerkom a écrit :

Hi,

Just FYI, I went back to 2.6.24-1-686.
I had 2.6.25-1-686 + 2.6.25-2-686 running for 9 days and had 3 hard
freezes: nothing moved, no kbd, no mouse.

The logs showed nothing up to the moment.
That hasn't happened since I bought this mobo 3 years ago.

It could be my hardware setup:
2 ATA disks, 2 USB external drives, one ATA, one SATA.

Hugo

I had the same problem using "bigmem" on an Asus P5K-E mobo, c2duo and
4gb ram. On the same box the -amd64 is running fine. I tried many
compilation options, and I even got the freezes with a vanilla kernel.
It's still the same for 2.6.25-3.
I filled a bug report but it didn't catch a lot of interest so far... I
thought I was the only one to get that.


The only output I got was :



<snip>



It's happening even with no xserver started on non tainted kernel.

What's your hardware precisely ?




I have an EP-8VTAI mobo with an Athlon XP +2700 at 2GHz and 1GB of memory.

What is the number of the bug?

At least you got output, I got nothing.

Hugo


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 05-20-2008, 07:54 PM
"thveillon.debian"
 
Default freezes in 2.6.25

Hugo Vanwoerkom a écrit :

thveillon.debian wrote:

Hugo Vanwoerkom a écrit :

Hi,

Just FYI, I went back to 2.6.24-1-686.
I had 2.6.25-1-686 + 2.6.25-2-686 running for 9 days and had 3 hard
freezes: nothing moved, no kbd, no mouse.

The logs showed nothing up to the moment.
That hasn't happened since I bought this mobo 3 years ago.

It could be my hardware setup:
2 ATA disks, 2 USB external drives, one ATA, one SATA.

Hugo

I had the same problem using "bigmem" on an Asus P5K-E mobo, c2duo
and 4gb ram. On the same box the -amd64 is running fine. I tried many
compilation options, and I even got the freezes with a vanilla
kernel. It's still the same for 2.6.25-3.
I filled a bug report but it didn't catch a lot of interest so far...
I thought I was the only one to get that.


The only output I got was :



<snip>



It's happening even with no xserver started on non tainted kernel.

What's your hardware precisely ?




I have an EP-8VTAI mobo with an Athlon XP +2700 at 2GHz and 1GB of
memory.


What is the number of the bug?

At least you got output, I got nothing.

Hugo



I have filled a new one for the latest 2.6.25-3, bug number *482100*.
Since I had problem with the vanilla kernel (did you try compiling from
vanilla kernel.org sources ?) I'm thinking of filling a bug there. I'll
wait for some Debian feedback first, maybe it's just a problem with a
specific system setting.


Tom
**


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 05-20-2008, 08:17 PM
Hugo Vanwoerkom
 
Default freezes in 2.6.25

thveillon.debian wrote:

Hugo Vanwoerkom a écrit :

thveillon.debian wrote:

Hugo Vanwoerkom a écrit :

Hi,

Just FYI, I went back to 2.6.24-1-686.
I had 2.6.25-1-686 + 2.6.25-2-686 running for 9 days and had 3 hard
freezes: nothing moved, no kbd, no mouse.

The logs showed nothing up to the moment.
That hasn't happened since I bought this mobo 3 years ago.

It could be my hardware setup:
2 ATA disks, 2 USB external drives, one ATA, one SATA.

Hugo

I had the same problem using "bigmem" on an Asus P5K-E mobo, c2duo
and 4gb ram. On the same box the -amd64 is running fine. I tried many
compilation options, and I even got the freezes with a vanilla
kernel. It's still the same for 2.6.25-3.
I filled a bug report but it didn't catch a lot of interest so far...
I thought I was the only one to get that.


The only output I got was :



<snip>



It's happening even with no xserver started on non tainted kernel.

What's your hardware precisely ?




I have an EP-8VTAI mobo with an Athlon XP +2700 at 2GHz and 1GB of
memory.


What is the number of the bug?

At least you got output, I got nothing.

Hugo



I have filled a new one for the latest 2.6.25-3, bug number *482100*.
Since I had problem with the vanilla kernel (did you try compiling from
vanilla kernel.org sources ?) I'm thinking of filling a bug there. I'll
wait for some Debian feedback first, maybe it's just a problem with a
specific system setting.




I did compile from 2.6.25.3 - I see that the current stable is 2.6.25.4
- and I ran that for two days but never got a freeze. I changed my
strategy slightly: I was going to go back to that version after the 3
freezes in the Debian kernel, but instead I went back to 2.6.24-1-686.
Got scared I guess... :-)
I submitted *482074* describing the freeze, but other than looking for
other people who report a freeze I don't hold out much hope.


Hugo





--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 05-20-2008, 08:20 PM
Hugo Vanwoerkom
 
Default freezes in 2.6.25

thveillon.debian wrote:

Hugo Vanwoerkom a écrit :

thveillon.debian wrote:

Hugo Vanwoerkom a écrit :

Hi,

Just FYI, I went back to 2.6.24-1-686.
I had 2.6.25-1-686 + 2.6.25-2-686 running for 9 days and had 3 hard
freezes: nothing moved, no kbd, no mouse.

The logs showed nothing up to the moment.
That hasn't happened since I bought this mobo 3 years ago.

It could be my hardware setup:
2 ATA disks, 2 USB external drives, one ATA, one SATA.

Hugo

I had the same problem using "bigmem" on an Asus P5K-E mobo, c2duo
and 4gb ram. On the same box the -amd64 is running fine. I tried many
compilation options, and I even got the freezes with a vanilla
kernel. It's still the same for 2.6.25-3.
I filled a bug report but it didn't catch a lot of interest so far...
I thought I was the only one to get that.


The only output I got was :



<snip>



It's happening even with no xserver started on non tainted kernel.

What's your hardware precisely ?




I have an EP-8VTAI mobo with an Athlon XP +2700 at 2GHz and 1GB of
memory.


What is the number of the bug?

At least you got output, I got nothing.

Hugo



I have filled a new one for the latest 2.6.25-3, bug number *482100*.
Since I had problem with the vanilla kernel (did you try compiling from
vanilla kernel.org sources ?) I'm thinking of filling a bug there. I'll
wait for some Debian feedback first, maybe it's just a problem with a
specific system setting.




In reading your bugreport, my symptoms are different: I can't tell
*when* I am getting a freeze. Have to play around, but sooner or later
it *does* happen.


Hugo












--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 05-20-2008, 09:14 PM
"thveillon.debian"
 
Default freezes in 2.6.25

Hugo Vanwoerkom a écrit :

thveillon.debian wrote:

Hugo Vanwoerkom a écrit :

thveillon.debian wrote:

Hugo Vanwoerkom a écrit :

Hi,

Just FYI, I went back to 2.6.24-1-686.
I had 2.6.25-1-686 + 2.6.25-2-686 running for 9 days and had 3
hard freezes: nothing moved, no kbd, no mouse.

The logs showed nothing up to the moment.
That hasn't happened since I bought this mobo 3 years ago.

It could be my hardware setup:
2 ATA disks, 2 USB external drives, one ATA, one SATA.

Hugo

I had the same problem using "bigmem" on an Asus P5K-E mobo, c2duo
and 4gb ram. On the same box the -amd64 is running fine. I tried
many compilation options, and I even got the freezes with a vanilla
kernel. It's still the same for 2.6.25-3.
I filled a bug report but it didn't catch a lot of interest so
far... I thought I was the only one to get that.


The only output I got was :



<snip>



It's happening even with no xserver started on non tainted kernel.

What's your hardware precisely ?




I have an EP-8VTAI mobo with an Athlon XP +2700 at 2GHz and 1GB of
memory.


What is the number of the bug?

At least you got output, I got nothing.

Hugo



I have filled a new one for the latest 2.6.25-3, bug number *482100*.
Since I had problem with the vanilla kernel (did you try compiling
from vanilla kernel.org sources ?) I'm thinking of filling a bug
there. I'll wait for some Debian feedback first, maybe it's just a
problem with a specific system setting.




I did compile from 2.6.25.3 - I see that the current stable is
2.6.25.4 - and I ran that for two days but never got a freeze. I
changed my strategy slightly: I was going to go back to that version
after the 3 freezes in the Debian kernel, but instead I went back to
2.6.24-1-686. Got scared I guess... :-)
I submitted *482074* describing the freeze, but other than looking for
other people who report a freeze I don't hold out much hope.

Hugo


I didn't try the .4 since the good point about this problem is I
switched my system to x86-64. I'm going to try it out of curiosity.


Regarding the when the "bug" (or not) happens, it's usually soon after
boot time on my system, which is usually heavily loaded (with .1 I could
hardly reach the login screen). The longer I got was with the vanilla
build, about half an hour, for the debian builds it was always less than
that.


Tom


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 05-27-2008, 11:03 PM
Celejar
 
Default freezes in 2.6.25

On Mon, 19 May 2008 14:33:58 -0500
Hugo Vanwoerkom <hvw59601@care2.com> wrote:

> Hi,
>
> Just FYI, I went back to 2.6.24-1-686.
> I had 2.6.25-1-686 + 2.6.25-2-686 running for 9 days and had 3 hard
> freezes: nothing moved, no kbd, no mouse.
> The logs showed nothing up to the moment.
> That hasn't happened since I bought this mobo 3 years ago.
>
> It could be my hardware setup:
> 2 ATA disks, 2 USB external drives, one ATA, one SATA.

2.6.25 freezes for me, too, after various amounts of uptime, but always
within about fifteen minutes. In my case, I'm pretty sure it's this:

http://bugzilla.kernel.org/show_bug.cgi?id=10729

some sort of regression in the RTC code (I, and the reporter there, had
been running 2.6.24 without any problems), since when I followed a
suggestion in the bug thread and disabled chrony, the problem went
away. If you're running an NTP daemon, or anything else that talks to
the RTC, try disabling it and see if the problem persists

> Hugo

Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 05-27-2008, 11:32 PM
John Hasler
 
Default freezes in 2.6.25

Celejar writes:
> some sort of regression in the RTC code (I, and the reporter there, had
> been running 2.6.24 without any problems), since when I followed a
> suggestion in the bug thread and disabled chrony, the problem went away.

Did you have the rtcfile line commented out in /etc/chrony/chrony.conf? If
not did you try commenting it out before turning chrony off?
--
John Hasler


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 05-28-2008, 12:09 AM
Celejar
 
Default freezes in 2.6.25

On Tue, 27 May 2008 18:32:21 -0500
John Hasler <jhasler@debian.org> wrote:

> Celejar writes:
> > some sort of regression in the RTC code (I, and the reporter there, had
> > been running 2.6.24 without any problems), since when I followed a
> > suggestion in the bug thread and disabled chrony, the problem went away.
>
> Did you have the rtcfile line commented out in /etc/chrony/chrony.conf? If

I didn't.

> not did you try commenting it out before turning chrony off?

I'll try it and report back. Thanks for the suggestion; it's been a
while since I configured chrony, and I'd forgotten about that.

> John Hasler

Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 

Thread Tools




All times are GMT. The time now is 02:07 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org