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 06-04-2008, 11:23 AM
LÉVAI Dániel
 
Default Bug#484467: (no subject)

> > Package: linux-image-2.6.25-2-amd64
> > Version: 2.6.25-4
> > Severity: serious
>
> overflated severity.

not being able to boot the OS is pretty serious

>
> > --- Please enter the report below this line. ---
> > I have a Lenovo Thinkpad R61i laptop. When using this kernel
> > (2.6.25-2-amd64) then right after the last daemon started from
> > init.d during the boot process, I get the message: init: entering
> > runlevel 0, and the system is getting halted. Why?
>
> doesn't happen here on a x61s.
> post your grub or grub2 config ?
I'm using LILO.

>
> also learn to use reportbug instead of reportbug-ng.
Alright.

Thanks

Daniel

--
LEVAI Daniel
PGP key ID = 0x4AC0A4B1
Key fingerprint = D037 03B9 C12D D338 4412 2D83 1373 917A 4AC0 A4B1



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 06-04-2008, 12:20 PM
maximilian attems
 
Default Bug#484467: (no subject)

On Wed, Jun 04, 2008 at 01:23:12PM +0200, LÉVAI Dániel wrote:
> > > Package: linux-image-2.6.25-2-amd64
> > > Version: 2.6.25-4
> > > Severity: serious
> >
> > overflated severity.
>
> not being able to boot the OS is pretty serious

not really if it only affects *one* box.

> >
> > > --- Please enter the report below this line. ---
> > > I have a Lenovo Thinkpad R61i laptop. When using this kernel
> > > (2.6.25-2-amd64) then right after the last daemon started from
> > > init.d during the boot process, I get the message: init: entering
> > > runlevel 0, and the system is getting halted. Why?
> >
> > doesn't happen here on a x61s.
> > post your grub or grub2 config ?
> I'm using LILO.

how about posting lilo.conf ?
ls -l /boot

> > also learn to use reportbug instead of reportbug-ng.
> Alright.

is the error reprudcible?

--
maks



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 06-04-2008, 05:07 PM
LÉVAI Dániel
 
Default Bug#484467: (no subject)

The problem is with cpufreqd.
After:
# update-rc.d -f cpufreqd remove
the system is up and runnning, but when executing:
# invoke-rc.d cpufreqd start
INIT: Switching to runlevel 0

How about that :

With a self-compiled 2.6.25.4, everything is fine. The freq. governors
are compiled in for me, in contrast with the debian kernel, which has
them in modules. I don't know if this is related, cpufreqd suppose to
load every module it needs.

Guess we could close this, or is this still relevant?

Daniel

--
LEVAI Daniel
PGP key ID = 0x4AC0A4B1
Key fingerprint = D037 03B9 C12D D338 4412 2D83 1373 917A 4AC0 A4B1



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 06-04-2008, 10:56 PM
maximilian attems
 
Default Bug#484467: (no subject)

On Wed, 04 Jun 2008, LÉVAI Dániel wrote:

> The problem is with cpufreqd.
> After:
> # update-rc.d -f cpufreqd remove
> the system is up and runnning, but when executing:
> # invoke-rc.d cpufreqd start
> INIT: Switching to runlevel 0

better use cpufrequtils

> How about that :
>
> With a self-compiled 2.6.25.4, everything is fine. The freq. governors
> are compiled in for me, in contrast with the debian kernel, which has
> them in modules. I don't know if this is related, cpufreqd suppose to
> load every module it needs.
>
> Guess we could close this, or is this still relevant?

hmm kernel should not reboot that easily.
but on a quick guess aboves beast is running as root and thus..
bug needs to be reassigned.

--
maks



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 06-06-2008, 06:11 AM
LÉVAI Dániel
 
Default Bug#484467: (no subject)

On 2008. June 5. 00:56:32 you wrote:
> On Wed, 04 Jun 2008, LÉVAI Dániel wrote:
> > The problem is with cpufreqd.
> > After:
> > # update-rc.d -f cpufreqd remove
> > the system is up and runnning, but when executing:
> > # invoke-rc.d cpufreqd start
> > INIT: Switching to runlevel 0
>
> better use cpufrequtils
I like cpufreqd because it can run arbitrary command when rules apply,
and that command could be
"echo 5 > /sys/class/backlight/acpi_video1/brightness". Is there a way
to do this with cpufrequtils?

>
> > How about that :
> >
> > With a self-compiled 2.6.25.4, everything is fine. The freq.
> > governors are compiled in for me, in contrast with the debian
> > kernel, which has them in modules. I don't know if this is related,
> > cpufreqd suppose to load every module it needs.
> >
> > Guess we could close this, or is this still relevant?
>
> hmm kernel should not reboot that easily.
> but on a quick guess aboves beast is running as root and thus..
> bug needs to be reassigned.
It reboots because there is a rule in /etc/cpufreqd.conf which halts the
system when it detects a 0-1% battery charge. cpufreqd uses the
legacy /proc way to gather battery status information, thus with the
new kernel it doesn't work, and instantly halts because it thinks that
no juice left.

--
LEVAI Daniel
PGP key ID = 0x4AC0A4B1
Key fingerprint = D037 03B9 C12D D338 4412 2D83 1373 917A 4AC0 A4B1



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 06-06-2008, 08:56 AM
maximilian attems
 
Default Bug#484467: (no subject)

reassign 484467 cpufreqd
severity 484467 serious
retitle 484467 query power status in /sys not in /proc
stop


On Fri, Jun 06, 2008 at 08:11:16AM +0200, LÉVAI Dániel wrote:
> It reboots because there is a rule in /etc/cpufreqd.conf which halts the
> system when it detects a 0-1% battery charge. cpufreqd uses the
> legacy /proc way to gather battery status information, thus with the
> new kernel it doesn't work, and instantly halts because it thinks that
> no juice left.

ok thanks a lot for the info, reassigning properly.
up to the cpufreqd maintainer to react.

best regards

--
maks



--
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 12:41 PM.

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