Processing commands for [EMAIL PROTECTED]:
> found 423040 2.6.22-4
Bug#423040: Source package contains non-free IETF RFC/I-D
Bug marked as found in version 2.6.22-4.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administra
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 waitin
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 st
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] las
[ please don't drop bug report on cc, this not private thanks :) ]
On Tue, Sep 04, 2007 at 05:52:44PM -0400, Paul wrote:
> You mean the ".config" file from the /usr/src/linux dir, or do you mean
> the config from initramfs-tools?
yes the .config from your 2.6.16 kernel.
usually also on /boot/conf
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 ./
--
http://frx.nets
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 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 PROTECTE
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
> > deve
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
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
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
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
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
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 w
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
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 linux-image
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 cou
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 unst
maximilian attems <[EMAIL PROTECTED]> wrote:
> tags 362851 moreinfo
> stop
>
> could you please retest against etch kernel?
The issue is still present with both etch and sid kernels,
however maybe it's already fixed upstream in 2.6.23-rc1
by commit 49521f97ccd3c2bf6e71a91cea8fe65d170fa4fb :
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.
kerne
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
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
>
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.
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 i
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:
> > [ pl
Processing commands for [EMAIL PROTECTED]:
> tags 440694 -moreinfo
Bug#440694: initramfs-tools: hook-functions:dep_add_modules() breaks with
/dev/md/x device names
Tags were: moreinfo
Tags removed: moreinfo
> tags 440694 wontfix
Bug#440694: initramfs-tools: hook-functions:dep_add_modules() break
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
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 http://git.debian.org/?p=kernel/initramfs-tool
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 some
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?
>
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 re
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 y
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 kernel/
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 work
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 locall
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
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 nfs
38 matches
Mail list logo
