Hello,
On Thu, Oct 19, 2006 at 07:22:23AM -0400, Carl Fink wrote:
> Is there, perhaps, a debugging kernel I could test that logs everything? If
> there isn't a prebuilt one, I might just compile one this weekend.
you should give an amd64 kernel a try. Install it with
dpkg --force-architecture.
Package: linux-2.6
Version: 2.6.17-3
Severity: important
See also: #391955 (same machine)
My X40 laptop hangs itself up with both 2.6.17-2-686 and
2.6.18-1-686 kernels *without sending a kernel panic via netconsole*
during the rc2.d startup sequence.
lapse:~# ls /etc/rc2.d
K00nstxcd@
Processing commands for [EMAIL PROTECTED]:
> tags 391955 - moreinfo
Bug#391955: random freezes/panics related to network traffic
Tags were: moreinfo
Tags removed: moreinfo
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(admi
tags 391955 - moreinfo
thanks
After two motherboard swaps (onboard e1000), I am still seeing this
bug, which makes me think it's not hardware-related. Thanks to
netconsole, I managed to capture a panic. See below for more
information about the system.
Also see the other (new) bug report I am writ
Package: initramfs-tools
Version: 0.83
Severity: important
Tags: patch
Booting via disk-labels when your root-label is on a md device, results
in the system hanging at "Waiting for root file system..." untill it times
out.
At this point there are no /dev/disk/by-label enteries for the md devices
also sprach martin f krafft <[EMAIL PROTECTED]> [2006.10.10.1801 +0200]:
> I am now seeing problems with 2.6.17 as well.
I think the problem I was seeing on 2.6.17 was a different one (see
the "other bug" which the BTS forwarded to this bug report). At the
time I filed this bug and posted the upda
Hello,
On Sun, Oct 15, 2006 at 08:54:15PM -0400, [EMAIL PROTECTED] wrote:
> Package: kernel-image-2.6.8-12-amd64-k8
> Version: 2.6.8-16sarge4
>
> Install System:
> Compaq Persario v5000.
> Chip: Turion 64
linux 2.6.8 is presumably much older than this box, and support is
expected to be broken.
Package: usplash
Version: 0.3e
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I tried to use usplash, but all it does is give me weird "chdir(): File
or directory not found" messages. Shutdown sequence is accompanied with
the non-standard "[ ok ]" string at the very right, so I
Processing commands for [EMAIL PROTECTED]:
> reassign 394193 mdadm
Bug#394193: initramfs-tools: root file system fails to mount when mounting by a
label, on top of an md device.
Bug reassigned from package `initramfs-tools' to `mdadm'.
> stop
Stopping processing here.
Please contact me if you n
also sprach martin f krafft <[EMAIL PROTECTED]> [2006.10.19.2044 +0200]:
> The problem does *not* occur with 2.6.16-1-686, and I have always
> started xdm at S19.
Believe it or not, I managed to make it freeze with 2.6.16
yesterday, after filing this bug. Argh!
Anyway, I am focusing on acpid now.
reassign 394193 mdadm
stop
On Fri, 20 Oct 2006, Chris Andrews wrote:
>
> Booting via disk-labels when your root-label is on a md device, results
> in the system hanging at "Waiting for root file system..." untill it times
> out.
>
> At this point there are no /dev/disk/by-label enteries for the
Package: linux-image-2.6.17-2-amd64
Version: 2.6.17-9
I occasionally experience a network freeze while transferring a large
amount of data. The console error message is:
NETDEV WATCHDOG : eth0: transmit timed out
sky2 eth0: tx timeout
sky2 hardware hung? flushing
According to lspci my network de
Package: linux-image-2.6.18-1-686
Version: 2.6.18-2
Severity: normal
Resuming from a suspend to RAM has not worked since 2.6.16-1 for my
laptop with an i915 display controller.
It comes up again ok in all respects (I think), except the screen
remains off. It worked perfectly from either X or con
From: Nathanael Nerode:
...
>Here you go, Steve.
>drivers/media/video/dabfirmware.h
>drivers/net/acenic_firmware.h
>drivers/net/dgrs_firmware.c
>drivers/net/tokenring/smctr_firmware.h
>drivers/usb/misc/emi62_fw_m.h
>drivers/usb/misc/emi62_fw_s.h
>The above are all undistributable: smctr_firmware.
On Fri, Oct 20, 2006 at 10:38:23PM +0930, Adrian Johnson wrote:
> Package: linux-image-2.6.17-2-amd64
> Version: 2.6.17-9
>
> I occasionally experience a network freeze while transferring a large
> amount of data.
Adrian,
Can you test a pre-release of the 2.6.18-3 build to confirm that
this is
On Fri, Oct 20, 2006 at 01:32:58PM +0200, ales drtik wrote:
> From: Nathanael Nerode:
> ...
> >Here you go, Steve.
>
> >drivers/media/video/dabfirmware.h
> >drivers/net/acenic_firmware.h
> >drivers/net/dgrs_firmware.c
> >drivers/net/tokenring/smctr_firmware.h
> >drivers/usb/misc/emi62_fw_m.h
> >dr
Joshua Kugler <[EMAIL PROTECTED]> writes:
> Sep 2 06:25:13 kernel: rtc: lost some interrupts at 512Hz.
That's an understatement. My tests revealed that the kernel does not
generate any periodic RTC interrupts (btw. Documentation/rtc.txt
contains a short test program).
Reason: The i386 kernels h
On 2006-10-20 20:54:45 +0200, Norbert Warmuth wrote:
> Workarounds (both tested successfully):
> 1. boot with hpet=disable
> 2. build the kernel with CONFIG_RTC=y
But is it normal that even when the rtc module is loaded (according
to lsmod), I get the following error?
# hwclock --systohc
select
Package: linux-headers-2.6.18-1-amd64
Version: 2.6.18-2
Severity: normal
/lib/modules/2.6.18-1-amd64/build is shipped as an empty directory in
linux-headers-2.6.18-1-amd64. It should be a symbolic link to
/usr/src/linux-headers-2.6.18-1-amd64/ (I needed that to build ivtv 0.8.0
from source)
Ap
Package: linux-image-2.6.17-2-686
Version: 2.6.17-9
Severity: important
>From a recent run of the LSB 3.1 tests:
10|852 /tset/LSB.os/mfiles/msync_P/T.msync_P 22:58:49|TC Start, scenario ref
858-0
15|852 3.6-lite 9|TCM Start
400|852 7 1 22:59:13|IC Start
200|852 7 22:59:13|TP Start
520|852 7
With the conclusion of GR 2006-007[1], we now have a clear statement from the
Debian developers that it is acceptable to release etch with firmware that
does not meet our usual requirements for inclusion in main, subject to three
principal conditions:
1. the freedom of the kernel for etch will n
Hello,
I second the following proposal:
On Sun, Oct 15, 2006 at 10:07:02AM +0200, Sven Luther wrote:
> === START OF PROPOSAL ===
> Definition: For the purpose of this resolution, the "firmware" mentioned below
> designates binary data included in some of the linux kernel drivers, usually
> as
>
[Manoj Srivastava]
> Given this official statement, I also suggest that the GR
> proposal is moot, since the proposer himself believes that the kernel
> modules in question can not be distributed by Debian legally.
There are a few firmware files which are sourceless but explicitly
_not_
Greetings! This exact same problem also afflicts the current hppa
autobuilders and paer.
Take care,
--
Camm Maguire[EMAIL PROTECTED]
==
"The earth is but one country, and mankind i
I was just using acpi events and a script that did this:
echo mem > /sys/power/state
I removed this and installed gnome-power-manager and it now correctly
resumes under 2.6.18. Haven't tested 2.6.17.
This solves my problem. Maybe the script way is not supported anymore? Or
is there still a bug
Steve Langasek <[EMAIL PROTECTED]> writes:
> As mentioned above, it was discovered late in the process that three firmware
> images included in the upstream kernel that are relevant to the installer are
> not distributed under clearly DFSG-compliant licenses: tg3, typhoon, and
> acenic. Of these,
On Fri, Oct 20, 2006 at 03:46:57PM -0500, Peter Samuelson wrote:
>
> [Manoj Srivastava]
> > Given this official statement, I also suggest that the GR
> > proposal is moot, since the proposer himself believes that the kernel
> > modules in question can not be distributed by Debian legally
On Fri, Oct 20, 2006 at 04:35:07PM -0700, Steve Langasek wrote:
> With the conclusion of GR 2006-007[1], we now have a clear statement from the
> Debian developers that it is acceptable to release etch with firmware that
> does not meet our usual requirements for inclusion in main, subject to three
On Fri, Oct 20, 2006 at 08:46:29PM -0700, Thomas Bushnell BSG wrote:
> Steve Langasek <[EMAIL PROTECTED]> writes:
>
> > As mentioned above, it was discovered late in the process that three
> > firmware
> > images included in the upstream kernel that are relevant to the installer
> > are
> > not
I have more news on the LSB test regressions I reported on earlier.
On Sun, 2006-10-15 at 18:22 -0400, Jeff Licquia wrote:
> The two tests are:
>
> /tset/LSB.os/mfiles/msync_P/T.msync_P 7 FAIL
As far as I can tell, the test is correct. The test does an mmap() of
three pages from a large read-wr
30 matches
Mail list logo
