(new) aufs-modules-2.6-486_2.6.22-1_i386.deb optional admin
Another UnionFS modules for Linux 2.6 on x86
This package depends on the Another UnionFS modules for latest Linux
kernel 2.6 on x86 and compatible machines.
(new) aufs-modules-2.6-686-bigmem_2.6.22-1_i386.deb optional admin
Another
linux-modules-contrib-2.6_2.6.22-2_i386.changes uploaded successfully to
localhost
along with the files:
linux-modules-contrib-2.6_2.6.22-2.dsc
linux-modules-contrib-2.6_2.6.22-2.tar.gz
ipw3945-modules-2.6.22-2-486_2.6.22+1.2.2-2_i386.deb
ipw3945-modules-2.6-486_2.6.22-2_i386.deb
ipw3945-modules-2.6-486_2.6.22-2_i386.deb
to
pool/contrib/l/linux-modules-contrib-2.6/ipw3945-modules-2.6-486_2.6.22-2_i386.deb
ipw3945-modules-2.6-686-bigmem_2.6.22-2_i386.deb
to
pool/contrib/l/linux-modules-contrib-2.6/ipw3945-modules-2.6-686-bigmem_2.6.22-2_i386.deb
On Fri, Jul 06, 2007 at 03:07:40PM +0200, Florian Fainelli wrote:
Package: linux-image-2.6.18-4-sparc64-smp
Version: 2.6.18+6
Description :
The realtek r8169 driver is not included by default in the
linux-image-2.6-sparc64-smp kernel package. Since this driver causes kernel
unaligned
Package: 2.6.21-2-sparc64
Version: 2.6.21-6
Severity: important
Hi,
2.6.21-2-sparc64 fails to boot on a SunFire v880 with the same/similar
error as described on
http://people.debian.org/~terpstra/message/20070307.205218.812de3a7.en.html#debian-sparc
Obviously gentoo works well on the machine,
Processing commands for [EMAIL PROTECTED]:
reassign 431977 linux-2.6
Bug#431977: Realtek r8169 driver is not included by default for sparc64/smp
kernels
Warning: Unknown package 'linux-image-2.6.18-4-sparc64-smp'
Bug reassigned from package `linux-image-2.6.18-4-sparc64-smp' to `linux-2.6'.
Jeffrey B. Green wrote:
(I've delayed a few weeks in reporting this bug and so unsure whether other
work on it has already occurred. However I could not find anything
relevant.)
A very similar behaviour can be reproduced with i386 as well (with the Etch
versions of the Linux kernel and
On Tue, Sep 04, 2007 at 06:16:05AM +0200, Fabio Massimo Di Nitto wrote:
#433187 is the bug that has killed the buildds on lebrun and spontini,
right?
AIUC, yes. at least i can reproduce that on my buildd.
Hi guys,
We (David Miller and I) are already working on this. We finally got
On Tue, Sep 04, 2007 at 12:20:23AM +0100, Chris Andrew wrote:
Hi,
Just for clarity, is the call for help for sparc or sparc 64, or both?
The two mentioned RC bugs are for sparc64:
http://bugs.debian.org/433187
http://bugs.debian.org/440445
I was not able to reproduce either of them locally
Josip Rodin wrote:
On Tue, Sep 04, 2007 at 06:16:05AM +0200, Fabio Massimo Di Nitto wrote:
#433187 is the bug that has killed the buildds on lebrun and spontini,
right?
AIUC, yes. at least i can reproduce that on my buildd.
Hi guys,
We (David Miller and I) are already working on this. We
Josip Rodin wrote:
On Tue, Sep 04, 2007 at 10:17:33AM +0200, Fabio Massimo Di Nitto wrote:
I should mention that lebrun.d.o is still dead since the last attempt
(ssh unresponsive since 2007-08-30 ~21:25), when it was running a 2.6.22.5
with one davem patch applied (one line in
On Tue, Sep 04, 2007 at 10:17:33AM +0200, Fabio Massimo Di Nitto wrote:
I should mention that lebrun.d.o is still dead since the last attempt
(ssh unresponsive since 2007-08-30 ~21:25), when it was running a 2.6.22.5
with one davem patch applied (one line in kernel/futex_compat.c). If you
Hi,
On Tue Sep 04, 2007 at 10:17:33 +0200, Fabio Massimo Di Nitto wrote:
Josip Rodin wrote:
On Tue, Sep 04, 2007 at 06:16:05AM +0200, Fabio Massimo Di Nitto wrote:
#433187 is the bug that has killed the buildds on lebrun and spontini,
right?
AIUC, yes. at least i can reproduce that on
Martin Zobel-Helas wrote:
Hi,
On Tue Sep 04, 2007 at 10:17:33 +0200, Fabio Massimo Di Nitto wrote:
Josip Rodin wrote:
On Tue, Sep 04, 2007 at 06:16:05AM +0200, Fabio Massimo Di Nitto wrote:
#433187 is the bug that has killed the buildds on lebrun and spontini,
right?
AIUC, yes. at least
On Tue, Sep 04, 2007 at 10:17:33AM +0200, Fabio Massimo Di Nitto wrote:
anyway we were able to reproduce the problem by doing some fancy building on
Niagara and that already isolate the problems to a more generic bit of the
code
rather than CPU specific.
I'm able to reproduce it with
On Mon, 03 Sep 2007, [EMAIL PROTECTED] wrote:
so splitting out the networking related code into a separate function
would move towards not having forked code for all of these different
network boot methods. at least, that's my hope.
applied see
Bastian Blank wrote:
On Tue, Sep 04, 2007 at 10:17:33AM +0200, Fabio Massimo Di Nitto wrote:
anyway we were able to reproduce the problem by doing some fancy building on
Niagara and that already isolate the problems to a more generic bit of the
code
rather than CPU specific.
I'm able to
tags 440694 -moreinfo
tags 440694 wontfix
severity 440694 wishlist
retitle 440694 initramfs-tools MODULES=dep support new mdadm naming scheme
+ partioned devices
stop
On Mon, 03 Sep 2007, Mario 'BitKoenig' Holbe wrote:
On Mon, Sep 03, 2007 at 08:44:10PM +0200, maximilian attems wrote:
[
On Mon, 03 Sep 2007, Justin Pryzby wrote:
On Mon, Sep 03, 2007 at 10:36:56PM +0200, maximilian attems wrote:
i'll try to rephrase you have chroot where /proc is mounted,
where the exterior /boot is ro. thus no initramfs is generated
inside of the chroot?
Right. The readonly boot is
On Tue, Sep 04, 2007 at 11:07:32AM +0200, Fabio Massimo Di Nitto wrote:
Bastian Blank wrote:
But with 2.6.23-rc4 this dies with the niagara problem but the futex one.
What Niagara problem?
It dies on a T2000 within 30 minutes, depending on the load. You said
this is a Niagara-only problem. I
Bastian Blank wrote:
On Tue, Sep 04, 2007 at 11:07:32AM +0200, Fabio Massimo Di Nitto wrote:
Bastian Blank wrote:
But with 2.6.23-rc4 this dies with the niagara problem but the futex one.
What Niagara problem?
It dies on a T2000 within 30 minutes, depending on the load. You said
this is a
Hi maximilian,
I made some progresses. I found that some could make it work there.
http://gentoo-wiki.com/HARDWARE_saa7134
http://www.linuxquestions.org/questions/showthread.php?t=260926
Since I am really crap in linux, what would you advice me to do ?
I compiled a freshly 2.6.22.6 kernel.
and I
Hello,
I did not try yet this one. But I tried all kernels in between, and I
realize that no one fixed this bug or issue since years. I am hence
believing that in the future, no one will care much about this device and
kind of bug. I read that some pinnacle users have troubles. So, why 20.1.
Package: linux-image-686
Version: 2.6.22+9
Severity: serious
--- Please enter the report below this line. ---
linux-image 2.6.22+9 has been removed from sid, so the dependency is broken.
--- System information. ---
Architecture: i386
Kernel: Linux 2.6.22-1-686
Debian Release: lenny/sid
990
Package: linux-2.6
Severity: wishlist
Version: 2.6.22-4
Hi,
I run a console server with a serial port replicator, but the number of serial
ports in the kernel is limited to 16 (CONFIG_SERIAL_8250_NR_UARTS), so I have to
rebuild the kernel every time I update it.
It would be good if the limit
David wrote:
Package: linux-image-686
Version: 2.6.22+9
Severity: serious
--- Please enter the report below this line. ---
linux-image 2.6.22+9 has been removed from sid, so the dependency is broken.
I guess you mean linux-image-2.6.22-1-686 has been removed and the
dependency of
Exactly. Maybe this bug should be reasigned to linux-image-2.6-686.
But, still, linux-image-686 should change the version number...
On 04/09/07, Luk Claes [EMAIL PROTECTED] wrote:
David wrote:
Package: linux-image-686
Version: 2.6.22+9
Severity: serious
--- Please enter the report
Actually, the incident is primarily on i386 machines. Sorry about the
report being a bit deceptive by submitting from my standard work machine
which is a powerpc. The powerpc kernel may not exhibit this behavior.
-jeff
Moritz Mühlenhoff wrote:
Jeffrey B. Green wrote:
(I've delayed a few
also sprach Mario 'BitKoenig' Holbe [EMAIL PROTECTED] [2007.09.03.2147 +0200]:
[ please use reportbug in furture it adds important info ]
...and add python to my system... grrr :)
Write yourself a shell replacement then.
See #440712: v1-style naming is currently not supported by Debian's
On Tue, Sep 04, 2007 at 11:44:33AM +0200, maximilian attems wrote:
ok, so i don't care about the old devfs way,
as that is clearly old fashioned.
I understand your decision, especially regarding the current lack of
support for non-'standard' names from Debian mdadm.
However... no offense meant,
On Tue, Sep 04, 2007 at 04:08:49PM +0200, martin f krafft wrote:
also sprach Mario 'BitKoenig' Holbe [EMAIL PROTECTED] [2007.09.03.2147
+0200]:
[ please use reportbug in furture it adds important info ]
...and add python to my system... grrr :)
Write yourself a shell replacement then.
I
On Tue, 04 Sep 2007, Mario 'BitKoenig' Holbe wrote:
However... no offense meant, just as strategic hint: please don't do
the mistake and consider /dev/md/ style names as old way or old
fashioned, since exactly the opposite is the case: Neil (md, mdadm
developer) considers them the new way and
On Tue, Sep 04, 2007 at 06:50:53PM +0200, maximilian attems wrote:
any pointer to a statement on that topic?
man mdadm
look for /dev/md/root, you should end up in the ASSEMBLE MODE section.
The DEVICE NAMES section describes the two standard naming schemes.
Mario
--
If her DNA was off by one
also sprach maximilian attems [EMAIL PROTECTED] [2007.09.04.1850 +0200]:
However... no offense meant, just as strategic hint: please don't do
the mistake and consider /dev/md/ style names as old way or old
fashioned, since exactly the opposite is the case: Neil (md, mdadm
developer)
On Mon, 03 Sep 2007, Paul wrote:
You say you need more info. Like, what? --Paul
your 2.6.16 config please?
i bet your trouble is not reproducible with stock debian
linux-images.
concerning the severity reread the severity descriptions.
--
maks
--
To UNSUBSCRIBE, email to [EMAIL
On Mon, 6 Aug 2007 16:30:19 +0200 maximilian attems wrote:
hello,
Hi there! :)
On Wed, 13 Jun 2007, Francesco Poli wrote:
Package: linux-image-2.6.20-1-amd64
Version: 2.6.20-3
Severity: normal
Hi!
It seems I'm not able to read ACPI temperature or fan data on a box
with
I tried linux-image-2.6.23-rc4-amd64
(version: 2.6.23~rc4-1~experimental.1~snapshot.9444)
from trunk, but I still experience this bug:
$ ls -altrF /sys/bus/i2c/devices/
total 0
drwxr-xr-x 4 root root 0 2007-09-04 23:07 ../
drwxr-xr-x 2 root root 0 2007-09-04 23:07 ./
--
package: linux-2.6
Lenny Printing bug with Samsung ML-2010 with Kernel 2.6.21-2-486 #1 Wed
Jul 11 03:17:09 UTC 2007 i686
printing job stayed in Kjobviewer
Printing OK with/ older //kernel 2.6.18-4-486 #1 Mon Mar 26 16:39:10 UTC
2007 i686 /
Hi,
this Samsung ML-2010 [EMAIL PROTECTED]
Hey Maks: Thanks for the help.
On Tuesday 04 September 2007 16:54, maximilian attems wrote:
On Mon, 03 Sep 2007, Paul wrote:
You say you need more info. Like, what? --Paul
your 2.6.16 config please?
Ok..attached from the boot directory.
i bet your trouble is not reproducible with stock
On Monday 03 September 2007 19:04, Paul wrote:
urrgs why are you using such an old kernel?
So, are you saying that this behavior will go away when I upgrade? Somehow
I doubt that, but I will try. I was waiting to upgrade the kernel when I
moved from stable to unstable, and I was waiting to
40 matches
Mail list logo
