Package: linux-image-2.6.30-1-amd64
Version: 2.6.30-6
Severity: normal
I have also made a video recording of the console log while the kernel boots.
Don't know if that can be useful to you. It does provide more information than
the below kernel log, though the format of said information isn't op
Processing commands for cont...@bugs.debian.org:
> merge 545231 545232
Bug#545231: linux-image-2.6.30-1-amd64: 18 minutes wait until X is ready to
launch, instead of normal ~45 sec
Bug#545232: linux-image-2.6.30-1-amd64: 18 minutes wait until X is ready to
launch, instead of normal ~45 sec
Merge
On Sat, 2009-09-05 at 22:57 +0200, Martin Millnert wrote:
> Package: linux-image-2.6.30-1-amd64
> Version: 2.6.30-6
> Severity: important
>
>
> When booting linux-image-2.6.30-1-amd64 my system takes some 18 minutes to
> boot
> through up until X is ready to launch.
> Normal for my system, for
If the issue is really that your system is so much slow that it is
unable to load the firmware before the 60 seconds timeout expires, and I
highly doubt it, then just set /sys/class/firmware/timeout to a much
higher value (just do it at the top of /lib/udev/firmware.agent and
then rebuild the initr
Processing commands for cont...@bugs.debian.org:
> tags 544194 unreproducible
Bug #544194 [linux-2.6] linux-source-2.6: compiles kernel but fails to make
.deb package
Added tag(s) unreproducible.
> severity 544194 normal
Bug #544194 [linux-2.6] linux-source-2.6: compiles kernel but fails to make
Hi,
sincere apologies for this duplicated report of #545231. Unfortunate
user error.
Please handle as appropriate.
Regards,
--
Martin Millnert
signature.asc
Description: This is a digitally signed message part
Package: linux-image-2.6.30-1-amd64
Version: 2.6.30-6
Severity: important
When booting linux-image-2.6.30-1-amd64 my system takes some 18 minutes to boot
through up until X is ready to launch.
Normal for my system, for example on my current kernel
linux-image-2.6.26-2-amd64,
is some ~45 sec.
I
Processing commands for cont...@bugs.debian.org:
> severity 545229 important
Bug #545229 [linux-image-2.6.30-1-parisc] linux-image-2.6.30-1-parisc: panic on
boot
Severity set to 'important' from 'critical'
>
End of message, stopping processing here.
Please contact me if you need assistance.
De
Package: linux-image-2.6.30-1-amd64
Version: 2.6.30-6
Severity: important
When booting linux-image-2.6.30-1-amd64 my system takes some 18 minutes to boot
through up until X is ready to launch.
Normal for my system, for example on my current kernel
linux-image-2.6.26-2-amd64,
is some ~45 sec.
I
Package: linux-image-2.6.30-1-parisc
Version: 2.6.30-6
Severity: critical
Tags: patch
Justification: breaks the whole system
-- Package-specific info:
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (650, 'testing'), (500, 'stable')
Architecture: hppa (par
Ben Hutchings escreveu:
> It works for me, though I have to run "umask 022" first due to a
> separate bug in the deb-pkg rule.
Even after typing "umask 022", "make deb-pkg" still refuses to work in the
fakeroot environment.
Things has changed however, now under root ownership (using either su or
Your message dated Sat, 05 Sep 2009 20:38:24 +0100
with message-id <1252179504.3494.9.ca...@localhost>
and subject line Re: Bug#544592: linux-image-2.6.30-1-686: sometimes failed to
boot
has caused the Debian Bug report #544592,
regarding linux-image-2.6.30-1-686: sometimes failed to boot
to be ma
Processing commands for cont...@bugs.debian.org:
> notfound 544592 2.6.30-6
Bug #544592 [linux-image-2.6.30-1-686] linux-image-2.6.30-1-686: sometimes
failed to boot
Bug No longer marked as found in versions linux-2.6/2.6.30-6.
>
End of message, stopping processing here.
Please contact me if you
Ben Hutchings wrote:
On Thu, 2009-09-03 at 22:17 +0200, Davide Prina wrote:
Ben Hutchings wrote:
On Tue, 2009-09-01 at 20:44 +0200, Davide Prina wrote:
sometimes the boot fail: after grub I see: "Loading, please wait ...",
but the hard disk is not used.
After a while busybox appear; here I c
Your message dated Sat, 05 Sep 2009 15:58:45 +
with message-id
and subject line Bug#510695: fixed in redhat-cluster 3.0.2-2
has caused the Debian Bug report #510695,
regarding type in included config file for cman initscript
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 05 Sep 2009 15:58:45 +
with message-id
and subject line Bug#528258: fixed in redhat-cluster 3.0.2-2
has caused the Debian Bug report #528258,
regarding please package 3.0.0.rc2
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Your message dated Sat, 05 Sep 2009 15:58:45 +
with message-id
and subject line Bug#471398: fixed in redhat-cluster 3.0.2-2
has caused the Debian Bug report #471398,
regarding ccs: /etc/cluster/cluster.conf: file not found (broken on clean
install)
to be marked as done.
This means that you c
Your message dated Sat, 05 Sep 2009 15:58:45 +
with message-id
and subject line Bug#471398: fixed in redhat-cluster 3.0.2-2
has caused the Debian Bug report #471398,
regarding fails to install
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Sat, 05 Sep 2009 15:58:45 +
with message-id
and subject line Bug#528419: fixed in redhat-cluster 3.0.2-2
has caused the Debian Bug report #528419,
regarding should recommend or at least suggest python-openssl
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 05 Sep 2009 15:58:45 +
with message-id
and subject line Bug#528420: fixed in redhat-cluster 3.0.2-2
has caused the Debian Bug report #528420,
regarding /usr/share/fence/telnet_ssl not executable
to be marked as done.
This means that you claim that the problem has been
On Fri, Sep 04, 2009 at 08:11:10PM +0200, Christoph Franzen wrote:
>
> Whenever a new RAM disk is created (for instance with "update-initramfs -u -k
> all"), the above mentioned "libc" files are missing in the image. If I use
> the package
> "busybox", the kernel will panic because "libm.so" is n
On Sat, Sep 05, 2009 at 05:05:21AM +0100, Ben Hutchings wrote:
> Package: linux-image-2.6.30-1-amd64
> Version: 2.6.30-6
> Severity: important
>
> I've been trying to capture some DV from tape using this kernel
> version, and failing to get more than a few seconds. dvgrab keeps
> running but stop
Processing commands for cont...@bugs.debian.org:
> # at most
> severity 545064 important
Bug #545064 [initramfs-tools] initramfs-tools: "update-initramfs" fails to
include "/lib/libc.so.6" and "/lib/libm.so"
Ignoring request to change severity of Bug 545064 to the same value.
>
End of message, st
> "JT" == Josh Triplett writes:
Indeed, after doing
# modprobe snd-pcsp #enables beep(1)
# alsamixer -c 2 #first time I ever tried -c
And changing
Simple mixer control 'PC Speaker',0
Mono: Playback [on]
to [off], beep stopped beeping. So I apparently have the organs, but I would
rather reta
Hello,
Moritz Muehlenhoff a écrit :
> On Wed, Aug 12, 2009 at 06:27:19AM +0200, Pierre Meurisse wrote:
>>
>> My Ethernet device is unusable with amd64 kernels (2.6.26 ... 2.6.30).
>> When connected to a dhcp server, the system gets a IP address, but
>> no connection is possible
>
> You might hav
On Sat, Sep 05, 2009 at 05:13:42AM +0800, jida...@jidanni.org wrote:
> | jidanni, a few questions about your lack of a console beep:
> Yes must insert modules to get beep(1) to work.
> diff(1) shows amixer output is not affected by module insertion.
> Left most control in alsamixer affects mplayer,
26 matches
Mail list logo
