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 Kernel

 
 
LinkBack Thread Tools
 
Old 05-07-2008, 07:50 AM
Michael Meskes
 
Default Bug#479709: Same here

I'm experiencing the same problem on my HP nx7400 laptop but do not get
the lost interrupts. The system simply freezes after only a very short
uptime, sometimes even during the boot process. No output given.

I tried both, the amd64 and the 686 flavour and both fail.

Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes@jabber.org
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 05-09-2008, 10:11 PM
maximilian attems
 
Default Bug#479709: Same here

On Wed, 07 May 2008, Michael Meskes wrote:

> I'm experiencing the same problem on my HP nx7400 laptop but do not get
> the lost interrupts. The system simply freezes after only a very short
> uptime, sometimes even during the boot process. No output given.
>
> I tried both, the amd64 and the 686 flavour and both fail.

can you please file the bug upstream in bugzilla.kernel.org and
let us know the bug number. thanks

--
maks



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 06-20-2008, 10:54 AM
Michael Meskes
 
Default Bug#479709: Same here

Hi,

On Sat, May 10, 2008 at 12:11:56AM +0200, maximilian attems wrote:
> > I'm experiencing the same problem on my HP nx7400 laptop but do not get
> > the lost interrupts. The system simply freezes after only a very short
> > uptime, sometimes even during the boot process. No output given.
> >
> > I tried both, the amd64 and the 686 flavour and both fail.
>
> can you please file the bug upstream in bugzilla.kernel.org and
> let us know the bug number. thanks

I spend some time trying to figure out what's going on, using different
boot option, compiling my own kernel, adding debug output, etc. which
took some time because it sometimes took about a day before the system
froze. At the moment I do run 2.6.25 with an uptime of ~ 26 hours
(including suspend time in between) without a problem. It's too early to
tell whether my last change was the reason, but you might want to try
too. All I did was to disable the high precision timer by adding
"hpet=disable" to my command line.

Checking whether the right rtc module is included is probably the next
step, but before I need to keep it running some more time to see whether
the problem is really fixed.

Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes@jabber.org
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 06-20-2008, 12:46 PM
maximilian attems
 
Default Bug#479709: Same here

On Fri, Jun 20, 2008 at 12:54:21PM +0200, Michael Meskes wrote:
> Hi,
>
> On Sat, May 10, 2008 at 12:11:56AM +0200, maximilian attems wrote:
> > > I'm experiencing the same problem on my HP nx7400 laptop but do not get
> > > the lost interrupts. The system simply freezes after only a very short
> > > uptime, sometimes even during the boot process. No output given.
> > >
> > > I tried both, the amd64 and the 686 flavour and both fail.
> >
> > can you please file the bug upstream in bugzilla.kernel.org and
> > let us know the bug number. thanks
>
> I spend some time trying to figure out what's going on, using different
> boot option, compiling my own kernel, adding debug output, etc. which
> took some time because it sometimes took about a day before the system
> froze. At the moment I do run 2.6.25 with an uptime of ~ 26 hours
> (including suspend time in between) without a problem. It's too early to
> tell whether my last change was the reason, but you might want to try
> too. All I did was to disable the high precision timer by adding
> "hpet=disable" to my command line.
>
> Checking whether the right rtc module is included is probably the next
> step, but before I need to keep it running some more time to see whether
> the problem is really fixed.

irc there were fixes for the hpet in 2.6.26, can you please checkout
those too, trunk apt lines -> http://wiki.debian.org/DebianKernel

(beware to blacklist snd-pcsp or you'll here a lot of noise)

--
maks



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 06-20-2008, 02:20 PM
Michael Meskes
 
Default Bug#479709: Same here

On Fri, Jun 20, 2008 at 02:46:03PM +0200, maximilian attems wrote:
> irc there were fixes for the hpet in 2.6.26, can you please checkout
> those too, trunk apt lines -> http://wiki.debian.org/DebianKernel

I tried the Ubuntu 2.6.26 package which was the kernel that ran for
almost a day. Looking at the changes brought me to hpet=disable. :-)

> (beware to blacklist snd-pcsp or you'll here a lot of noise)

Yes, this one's ugly.

Michael

--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes@jabber.org
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 07-14-2008, 10:34 PM
Joergen Bergmann
 
Default Bug#479709: Same here

Package: linux-image-2.6.25-2-amd64
Version: 2.6.25-6

Hi,

with the migration of kernel 2.6.25-6 from unstable to testing this
error is spreading to many machines.


Because this error and it's patch are known since may, this migration to
testing should have been avoided, for my understanding.
(I also run into LILO troubles/kernel panic with initrd #487421,
large-memory in lilo.conf fixed this for me)


Maybe some warnings or hints would be fine, before installing this kernel.

Disabling HPET in Bios fixed the problem for me.

Will this problem be fixed in 2.6.25-7, which is already in unstable
linux-source?


best regards

Jörgen



--
To UNSUBSCRIBE, email to debian-kernel-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 07:18 AM.

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