Re: Status of this bug

[David Goodenough]

On Monday, 23 July 2018 14:30:06 BST Lisandro Damián Nicanor Pérez Meyer wrote:

> This has happened so far:

>

> From the Debian side maxy added haveged as a sddm recommendation and as a

> workaround.

>

> From the Qt side Thiago from upstream is trying to determine what changed in

> the kernel side, as this clearly started to happen with 4.16 and got worse

> with 4.17.

>

> Ben, linux maintainers: if you could give us a hand to determine what

> changed from the kernel side it would be much much appreciated. If we find

> that there are valid changes then we might have an opportunity to make Qt

> upstreams reconsider the issue.

>

> Cheers, Lisandro.

Interesting to note that on a system with sysvinit (and 4.17 kernel) there is 
no noticeable delay in sddm startup.



David

Re: Status of this bug

[Lisandro Damián Nicanor Pérez Meyer]

On Mon, 23 Jul 2018 at 12:49, Ben Hutchings  wrote:
> CVE-2018-1108 was fixed in the kernel.

Thanks Ben


-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Re: Status of this bug

[Ben Hutchings]

On Mon, 2018-07-23 at 10:30 -0300, Lisandro Damián Nicanor Pérez Meyer wrote:
> This has happened so far:
> 
> From the Debian side maxy added haveged as a sddm recommendation and as a 
> workaround.
> 
> From the Qt side Thiago from upstream is trying to determine what changed in 
> the kernel side, as this clearly started to happen with 4.16 and got worse 
> with 4.17.
> 
> Ben, linux maintainers: if you could give us a hand to determine what changed 
> from the kernel side it would be much much appreciated. If we find that there 
> are valid changes then we might have an opportunity to make Qt upstreams 
> reconsider the issue.

CVE-2018-1108 was fixed in the kernel.

Ben.

-- 
Ben Hutchings
Anthony's Law of Force: Don't force it, get a larger hammer.


signature.asc
Description: This is a digitally signed message part

Status of this bug

[Lisandro Damián Nicanor Pérez Meyer]

This has happened so far:

From the Debian side maxy added haveged as a sddm recommendation and as a 
workaround.

From the Qt side Thiago from upstream is trying to determine what changed in 
the kernel side, as this clearly started to happen with 4.16 and got worse 
with 4.17.

Ben, linux maintainers: if you could give us a hand to determine what changed 
from the kernel side it would be much much appreciated. If we find that there 
are valid changes then we might have an opportunity to make Qt upstreams 
reconsider the issue.

Cheers, Lisandro.

-- 
Sobre Argentina: "sé que es uno de los países mas hospitalarios del mundo"
 Albert Einstein

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.

Bug#604613: Status of this bug?

[Ben Hutchings]

[Please always cc the bug address, i.e. reply to all.]

On Sun, 2012-05-13 at 14:48 -0700, Paul Zimmerman wrote:
> 
> On Monday, May 7, 2012 7:11 PM, Ben Hutchings  wrote:
> 
> >On Mon, 2012-05-07 at 14:51 -0700, Paul Zimmerman wrote:
> >> So what is happening with this bug? It seems to be the same thing that
> >> has broken what was perfectly working wifi on my laptop when I had
> >> Lenny installed. But upgrading to Squeeze so I could continue to get
> >> security updates has left me with no wireless connection unless I plug
> >> in an external device. It doesn't seem to have been marked as fixed,
> >> as it should not be if it is still present in the standard Squeeze
> >> kernel, but at the end of one of the responses it says a fix has been
> >> entered into the 2.6.36~rc5-1~experimental.1 kernel.
> >[...]
> 
> >The bug log is at  and there is no claim
> >that it has been fixed.
> 
> >Can you test Linux 3.2 from testing/unstable/squeeze-backports?  Then we
> >can see whether it was fixed after Linux 2.6.32. and either report the
> >bug upstream or try to find that fix.
> 
> Well, I don't claim to understand the system, but in a page linked on this 
> one (http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=11;bug=604613) it gives 
> a series of "reassigned" reports, ending with:
> 
> reassign 586995 linux-2.6 2.6.32-24
> found 586995 linux-2.6/2.6.32-24
> fixed 586995 2.6.36~rc5-1~experimental.1
> thanks
> 
> So it looks like the work on the bug was bounced around to various places, 
> perhaps because the same problem was causing more than one bug report. 
> The "fixed" line at the end would seem to mean that it was resolved, but 
> put into the experimental kernel rather than the stable one issued to users.

I reassigned a large number of bugs with a single control message, one
of which happened to be this one.  I also marked another bug fixed.

> As for the backported kernel, I did try that when I first upgraded and found 
> the
> wifi was broken. It would not finish loading, but froze with a black screen 
> when
> it tried to start the desktop. It seems to be a little _too_ unstable for me 
> at this 
> 
> time. :) So I simply uninstalled it. But if it has been updated since early 
> March,
> I can try it again and let you know if it works now.

It's updated almost every week in unstable.  I can't promise the
graphics bug has been fixed though.

Ben.

-- 
Ben Hutchings
Experience is directly proportional to the value of equipment destroyed.
 - Carolyn Scheppner


signature.asc
Description: This is a digitally signed message part

Bug#673496: Bug#604613: Status of this bug?

[Jonathan Nieder]

Hi again,

Paul Zimmerman wrote:

> It's fairly simple to go back and look at dmesg, kern.log, syslog and such. 
> The Xorg.log 
> would be gone by now, after several restarts. Or would it? I'm not sure how 
> many 
> iterations are kept as .z archives. But I'm not sure if I could figure out 
> how to use 
> netconsole or serial console. It has to be connected to another machine 
> running Linux,
> doesn't it?

Thanks.  Netconsole requires another machine connected to the network,
but it doesn't have to run Linux.  Anything that can run netcat will
do (e.g., Windows or Mac OS).

Serial console requires a serial cable ("null modem cable") and a
machine capable of reading from that serial cable on the other end.
For example, a computer running minicom (on a Mac), LapLink (on DOS),
or HyperTerminal (on Windows) should work.  See [*] for an overview.

> Is there some other bug page for this that I should send any reports to?

Let's use bug#673496 to track the wifi regression and a new bug once
the failures starting X are clearer.

Hope that helps,
Jonathan

[*] http://tldp.org/HOWTO/Text-Terminal-HOWTO-10.html#ss10.6



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120519021428.GB22429@burratino

Processed: Re: Bug#604613: Status of this bug?

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> clone 604613 -1
Bug #604613 [linux-2.6] ath5k driver refuses to get an IP address from dhclient 
in squeeze
Bug 604613 cloned as bug 673496
> retitle -1 [lenny -> squeeze regression] wifi broken (?)
Bug #673496 [linux-2.6] ath5k driver refuses to get an IP address from dhclient 
in squeeze
Changed Bug title to '[lenny -> squeeze regression] wifi broken (?)' from 
'ath5k driver refuses to get an IP address from dhclient in squeeze'
> submitter -1 Paul Zimmerman 
Bug #673496 [linux-2.6] [lenny -> squeeze regression] wifi broken (?)
Changed Bug submitter to 'Paul Zimmerman ' from 
''
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
604613: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604613
673496: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.13373925303231.transcr...@bugs.debian.org

Bug#604613: Status of this bug?

[Paul Zimmerman]

Jonathan Nieder  wrote:

>Paul Zimmerman wrote:

>> No go. I don't know how to tell if it has been updated since early
>> March, but the 3.2 kernel does exactly the same thing now that it
>> did then. It looks like it is booting ok, but when it gets to
>> loading the desktop it freezes with a black screen. Apparently it
>> runs into some sort of problem starting X on this system. 

>Is the machine completely frozen?  Does caps lock work?  Does the
>magic sysrq key work?  Can you access the machine using SSH via a
>wired or wireless connection?  Can you get logs from this event, for
>example by using netconsole or serial console[1] or examining
>/var/log/dmesg, /var/log/Xorg.0.log, and /var/log/syslog after a
.reboot?

>[1] http://kernel-handbook.alioth.debian.org/ch-bugs.html#s9.1.1

I admit I did not try these other options. If it wasn't going to boot to the 
desktop, 
it was hung and I just did a hard power-off and selected the old kernel from 
the GRUB menu when restarting. After removing the backported kernel I used 
"shutdown -Fr now" to make sure no major problems were left in the file system.

It's fairly simple to go back and look at dmesg, kern.log, syslog and such. The 
Xorg.log 
would be gone by now, after several restarts. Or would it? I'm not sure how 
many 
iterations are kept as .z archives. But I'm not sure if I could figure out how 
to use 
netconsole or serial console. It has to be connected to another machine running 
Linux,
doesn't it?

Is there some other bug page for this that I should send any reports to?




--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1337391018.28403.yahoomail...@web162605.mail.bf1.yahoo.com

Bug#604613: Status of this bug?

[Jonathan Nieder]

Hi Paul,

Paul Zimmerman wrote:

> No go. I don't know how to tell if it has been updated since early
> March, but the 3.2 kernel does exactly the same thing now that it
> did then. It looks like it is booting ok, but when it gets to
> loading the desktop it freezes with a black screen. Apparently it
> runs into some sort of problem starting X on this system. 

Is the machine completely frozen?  Does caps lock work?  Does the
magic sysrq key work?  Can you access the machine using SSH via a
wired or wireless connection?  Can you get logs from this event, for
example by using netconsole or serial console[1] or examining
/var/log/dmesg, /var/log/Xorg.0.log, and /var/log/syslog after a
reboot?

[1] http://kernel-handbook.alioth.debian.org/ch-bugs.html#s9.1.1



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120518215108.GA13925@burratino

Bug#604613: Status of this bug?

[Paul Zimmerman]

No go. I don't know how to tell if it has been updated since early March, but 
the 3.2 kernel does exactly 
the same thing now that it did then. It looks like it is booting ok, but when 
it gets to loading the desktop 
it freezes with a black screen. Apparently it runs into some sort of problem 
starting X on this system. 

Admittedly, this is a marginal system. It's a laptop with the VIA P4M800 Pro 
integrated chipset. The 
video system uses the OpenChrome drivers, which actually work more reliably 
than the Windows drivers. 
But it is still buggy. Since I have no idea how to make it work, I have 
uninstalled the backported kernel, 
and tried to uninstall the supporting packages but they seem to have 
disappeared. Both initramfs and 
linux-base had to be upgraded to backports for the 3.2 kernel, but now I cannot 
find the upgraded 
versions to uninstall them. Why would they turn invisible? At least the 
standard kernel is able to boot 
and the system is usable.

For now I have installed a different wifi card I found on eBay with a Realtek 
chipset. This does work, so 
the system is otherwise functional. It's just the ath5k driver that is broken. 
The performance of this other 
card is noticeably less, though, so I am definitely watching and waiting for 
this driver to be fixed in the 
stable kernel for Squeeze.



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1337375379.43431.yahoomail...@web162602.mail.bf1.yahoo.com

Bug#604613: Status of this bug?

[Jonathan Nieder]

Paul Zimmerman wrote:

(where "that" = initramfs-tools)
>   Would updating that for 
> the 
> newer kernel make the current stable kernel not able to load?

No.  initramfs-tools from wheezy and squeeze-backports are known to
work well with the kernel from squeeze.

Hope that helps,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120517052452.GB12275@burratino

Bug#604613: Status of this bug?

[Paul Zimmerman]

Ben Hutchings  wrote:

>On Mon, 2012-05-07 at 14:51 -0700, Paul Zimmerman wrote:
>> So what is happening with this bug? It seems to be the same thing that
>> has broken what was perfectly working wifi on my laptop when I had
>> Lenny installed. But upgrading to Squeeze so I could continue to get
>> security updates has left me with no wireless connection unless I plug
>> in an external device. It doesn't seem to have been marked as fixed,
>> as it should not be if it is still present in the standard Squeeze
>> kernel, but at the end of one of the responses it says a fix has been
>> entered into the 2.6.36~rc5-1~experimental.1 kernel.
[...]

>The bug log is at  and there is no claim
>that it has been fixed.
>
>Can you test Linux 3.2 from testing/unstable/squeeze-backports?  Then 
>we can see whether it was fixed after Linux 2.6.32. and either report the
>bug upstream or try to find that fix.

When I first discovered on upgrading that the wifi was broken I tried the 3.2 
backport 
kernel. It couldn't finish loading, but froze with a black screen. If it has 
been updated 
since early March I could try it again. But when I tried to install it again 
there was a 
dependency problem that I don't recall from my first attempt. It says that the 
newer 
kernel needs an backported initramfs as well. Was initramfs possibly involved 
in the 
problem that caused it to not be able to load before? Would updating that for 
the 
newer kernel make the current stable kernel not able to load? Not knowing for 
certain
that the backport would work, I would hate to get into a situation where I 
could not 
revert without some major rescue effort.



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1337220806.51639.yahoomail...@web162604.mail.bf1.yahoo.com

Bug#604613: Status of this bug?

[Robert Wallner]

I can confirm that it works for me on linux 3.2.0 from squeeze-backports,
while failing on 2.6.32 from squeeze.

--
Robert Wallner

Bug#604613: Status of this bug?

[Ben Hutchings]

On Mon, 2012-05-07 at 14:51 -0700, Paul Zimmerman wrote:
> So what is happening with this bug? It seems to be the same thing that
> has broken what was perfectly working wifi on my laptop when I had
> Lenny installed. But upgrading to Squeeze so I could continue to get
> security updates has left me with no wireless connection unless I plug
> in an external device. It doesn't seem to have been marked as fixed,
> as it should not be if it is still present in the standard Squeeze
> kernel, but at the end of one of the responses it says a fix has been
> entered into the 2.6.36~rc5-1~experimental.1 kernel.
[...]

The bug log is at  and there is no claim
that it has been fixed.

Can you test Linux 3.2 from testing/unstable/squeeze-backports?  Then we
can see whether it was fixed after Linux 2.6.32. and either report the
bug upstream or try to find that fix.

Ben.

-- 
Ben Hutchings
Life is what happens to you while you're busy making other plans.
   - John Lennon


signature.asc
Description: This is a digitally signed message part

Bug#604613: Status of this bug?

[Paul Zimmerman]

So what is happening with this bug? It seems to be the same thing that has 
broken what was perfectly working wifi on my laptop when I had Lenny installed. 
But upgrading to Squeeze so I could continue to get security updates has left 
me with no wireless connection unless I plug in an external device. It doesn't 
seem to have been marked as fixed, as it should not be if it is still present 
in the standard Squeeze kernel, but at the end of one of the responses it says 
a fix has been entered into the 2.6.36~rc5-1~experimental.1 kernel. When will 
this propagate to the regular kernel issued to users? If it worked perfectly in 
Lenny, could it be that hard to implement the fix? Can I get a patch somewhere 
to apply myself while waiting for this to appear in the standard kernel?

Bug#659519: Status of this Bug?

[David Baron]

On Saturday 21 April 2012 18:20:44 Ben Hutchings wrote:
> On Fri, 2012-04-20 at 11:14 +0300, David Baron wrote:
> > I am seeing more and more posts on linux-audio and debian-user which seem
> > to relate to this problem. Some relating to new versions of alsa
> > libraries installed over 2.6.33 kernels, not just 3.2.4!
> 
> What makes you think they relate to the same bug?  If they do then of
> course this is not a kernel bug and we need to reassign it.

Maybe should be looked into. I see to many complaints about those built-in 
intel-hda having stopped working. I never started using pulse, not installed, 
so that is not my problem.

> 
> By the way, Linux for x86_64/amd64 does not support ISA expansion cards.
> I would expect your ISA cards to still be supported in 32-bit kernel
> configurations, though it's very likely you will need to do some manual
> configuration of the driver.

Interesting.

The only thing on ISA is running through snd_mpu401, this with a port number. 
No IRQ, no DMA. Might even still work on 64 bit. I may have the last (very 
special, I suppose) MB with ISA running a modern CPU.

I want to switch to 64 bit but this may be one reason to keep putting it off.



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201204212238.02122.d_ba...@012.net.il

Bug#659519: Status of this Bug?

[Ben Hutchings]

On Fri, 2012-04-20 at 11:14 +0300, David Baron wrote:
> I am seeing more and more posts on linux-audio and debian-user which seem to 
> relate to this problem. Some relating to new versions of alsa libraries 
> installed over 2.6.33 kernels, not just 3.2.4!

What makes you think they relate to the same bug?  If they do then of
course this is not a kernel bug and we need to reassign it.

By the way, Linux for x86_64/amd64 does not support ISA expansion cards.
I would expect your ISA cards to still be supported in 32-bit kernel
configurations, though it's very likely you will need to do some manual
configuration of the driver.

Ben.

-- 
Ben Hutchings
For every action, there is an equal and opposite criticism. - Harrison


signature.asc
Description: This is a digitally signed message part

Bug#659519: Status of this Bug?

[David Baron]

I am seeing more and more posts on linux-audio and debian-user which seem to 
relate to this problem. Some relating to new versions of alsa libraries 
installed over 2.6.33 kernels, not just 3.2.4!



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201204201114.5.d_ba...@012.net.il

Bug#588200: Re: Bug#588200: bootchart2 in Debian now; status of this bug?

[Riccardo Magliocchetti]

Hello,

Il -10/01/-28163 20:59, Josh Triplett ha scritto:

On Sun, Mar 13, 2011 at 12:16:15AM +, Ben Hutchings wrote:

On Sat, 2010-11-06 at 22:17 +, maximilian attems wrote:

On Sat, Nov 06, 2010 at 01:59:11PM -0700, Josh Triplett wrote:

bootchart2 has entered unstable now; pinging this bug again to find out
if the next experimental kernel could include CONFIG_PROC_EVENTS=y, if
not the next unstable kernel.



well PROC_EVENTS depends on connector built-in, needs investigation cost.
no modular improvement in linux-next. might need prodding.


Adds about 8K to the kernel on i386/686-bigmem.


That sounds quite minimal.


Any update on this please?

thanks,
riccardo



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e3c5786.3060...@gmail.com

Bug#588200: bootchart2 in Debian now; status of this bug?

[Josh Triplett]

On Sun, Mar 13, 2011 at 12:16:15AM +, Ben Hutchings wrote:
> On Sat, 2010-11-06 at 22:17 +, maximilian attems wrote:
> > On Sat, Nov 06, 2010 at 01:59:11PM -0700, Josh Triplett wrote:
> > > bootchart2 has entered unstable now; pinging this bug again to find out
> > > if the next experimental kernel could include CONFIG_PROC_EVENTS=y, if
> > > not the next unstable kernel.
> > > 
> > 
> > well PROC_EVENTS depends on connector built-in, needs investigation cost.
> > no modular improvement in linux-next. might need prodding.
> 
> Adds about 8K to the kernel on i386/686-bigmem.

That sounds quite minimal.

- Josh Triplett



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110313003924.GB20845@feather

Bug#588200: bootchart2 in Debian now; status of this bug?

[Ben Hutchings]

On Sat, 2010-11-06 at 22:17 +, maximilian attems wrote:
> On Sat, Nov 06, 2010 at 01:59:11PM -0700, Josh Triplett wrote:
> > bootchart2 has entered unstable now; pinging this bug again to find out
> > if the next experimental kernel could include CONFIG_PROC_EVENTS=y, if
> > not the next unstable kernel.
> > 
> 
> well PROC_EVENTS depends on connector built-in, needs investigation cost.
> no modular improvement in linux-next. might need prodding.

Adds about 8K to the kernel on i386/686-bigmem.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part

Bug#588200: bootchart2 in Debian now; status of this bug?

[maximilian attems]

On Sat, Nov 06, 2010 at 01:59:11PM -0700, Josh Triplett wrote:
> bootchart2 has entered unstable now; pinging this bug again to find out
> if the next experimental kernel could include CONFIG_PROC_EVENTS=y, if
> not the next unstable kernel.
> 

well PROC_EVENTS depends on connector built-in, needs investigation cost.
no modular improvement in linux-next. might need prodding.



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20101106221711.gf19...@vostochny.stro.at

Bug#588200: bootchart2 in Debian now; status of this bug?

[Josh Triplett]

bootchart2 has entered unstable now; pinging this bug again to find out
if the next experimental kernel could include CONFIG_PROC_EVENTS=y, if
not the next unstable kernel.

- Josh Triplett



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20101106205907.ga5...@feather

Bug#409271: Status of this bug ?

[Michael Prokop]

* maximilian attems  [Wed Jun 09, 2010 at 04:25:09AM +0200]:
> On Tue, Jun 08, 2010 at 03:47:59PM +0200, Michael Prokop wrote:
> > * Steinar H. Gunderson  [Son Aug 10, 2008 at 
> > 05:03:28 +0200]:
> > > On Sun, Aug 10, 2008 at 04:35:23PM +0200, Fabrice Lorrain wrote:
> > > > I've just read through bts #409271 :"initramfs-tools: NFSv4 not  
> > > > supported for root fs"
> > > > and I'm interrested in knowing the status of this bug for lenny.

> > > AFAIK my understanding is: klibc's mount doesn't support NFSv4, initramfs
> > > insists on using klibc's mount, stalemate.

> > maks, we should discuss this issue in further details,
> > we be great if we could resolve this in time for squeeze.

> in a week i'm a back, but this is over ambitious.

Fair enoug,. though if we have a conclusion regarding
klibc<->libc<->busybox... solving this problem might not be that
much work. But yeah, let's discuss that when you're back.

thanks && regards,
-mika-


signature.asc
Description: Digital signature

Bug#409271: Status of this bug ?

[maximilian attems]

On Tue, Jun 08, 2010 at 03:47:59PM +0200, Michael Prokop wrote:
> * Steinar H. Gunderson  [Son Aug 10, 2008 at 05:03:28 
> +0200]:
> > On Sun, Aug 10, 2008 at 04:35:23PM +0200, Fabrice Lorrain wrote:
> > > I've just read through bts #409271 :"initramfs-tools: NFSv4 not  
> > > supported for root fs"
> > > and I'm interrested in knowing the status of this bug for lenny.
> 
> > AFAIK my understanding is: klibc's mount doesn't support NFSv4, initramfs
> > insists on using klibc's mount, stalemate.
> 
> maks, we should discuss this issue in further details,
> we be great if we could resolve this in time for squeeze.

in a week i'm a back, but this is over ambitious.



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100609022509.gd18...@baikonur.stro.at

Bug#409271: Status of this bug ?

[Michael Prokop]

* Steinar H. Gunderson  [Son Aug 10, 2008 at 05:03:28 
+0200]:
> On Sun, Aug 10, 2008 at 04:35:23PM +0200, Fabrice Lorrain wrote:
> > I've just read through bts #409271 :"initramfs-tools: NFSv4 not  
> > supported for root fs"
> > and I'm interrested in knowing the status of this bug for lenny.

> AFAIK my understanding is: klibc's mount doesn't support NFSv4, initramfs
> insists on using klibc's mount, stalemate.

maks, we should discuss this issue in further details,
we be great if we could resolve this in time for squeeze.

regards,
-mika-


signature.asc
Description: Digital signature

Bug#493479: linux-image-2.6.26-1-amd64: Update on status of this bug

[Dave Witbrodt]

Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-*
Followup-For: Bug #493479


After originally filing this bug report here on the Debian BTS, I
performed a kernel bisection and took my findings to the LKML.  About
3 weeks later, the problem had finally been correctly diagnosed:
changes between 2.6.25 and 2.6.26 had reordered the sequence of
function calls responsible for detecting PCI devices, and in my case
an overlap of the memory resource region for the HPET device was
causing kernel hangs on my hardware.  This had not occured with
2.6.25, but the changes leading up to 2.6.26 (which apparently fixed a
bug on other hardware) created the problem on my hardware.

My motherboard has an AMD SB600 southbridge, and some of the Linux
kernel team mistakenly believed that the problem is limited to that
chipset.  I was able to discover (in a Google search) at least one
other person with completely different hardware -- Intel CPU +
motherboard combination -- who began experiencing hangs in the 2.6.26
kernel series at exactly the same SHA1 hash that I discovered when
carrying out my original bisection, so the changes between 2.6.25 and
2.6.26 affect more hardware combinations than my own.

After a lengthy and frustrating period of time trying to discover the
root cause of the hangs, patches were created that allowed me to build
a kernel that would not hang.  These patches were primarily made by
Yinghai Lu and Ingo Molnar, and were against Ingo Molnar's tip/master
git tree.  Unfortunately, the patches were created too late in the
development of 2.6.27:  when Linus Torvalds saw the PCI code being
touched, and the potential problems that could create, he decided to
reject those changes for the 2.6.27 kernels and postpone them until
the 2.6.28 series.

I had hoped to provide a patch for the 2.6.26 kernels which Debian
will be using for its Lenny release, but my attention moved away from
these kernel issues until release candidates for 2.6.28 became
available.  Only today did I return to this issue again to determine
the status of the situation.  Here is what I found:


1) A patch had been provided on Sep. 12 by Jordan Crouse (a kernel
developer employed by AMD, IIRC) which should have allowed any
2.6.26 or 2.6.27 kernel to boot on my hardware:

http://www.uwsg.indiana.edu/hypermail/linux/kernel/0809.1/1902.html

This patch is supposed to prevent the memory resource region of
the HPET device on SB600 southbridge motherboards from overlapping
with the resource regions of other PCI devices.  I found that this
patch fails to make any difference on my hardware (with said
southbridge) for any 2.6.26 or 2.6.27 kernel.


2) Since the release candidates for 2.6.28 are now up to "rc3", I
decided to begin with "rc1".  I found that kernel 2.6.28-rc1 (from
Torvalds' git tree) would hang during boot when initializing the
HPET device, which I took as a bad sign!  Booting the kernel with
the "nohpet" parameter allowed to kernel to boot all the way to a
login prompt, only to hang at that point.  (Unlike the hangs
experienced with 2.6.2[67] kernels, I was able to use the Magic
SysRq keys to sync, unmount, and reboot my filesystem in a nice
way, however.)


3) Fully expecting fallout from the mad rush of changes that go
into that first 2-week window of changes, I checked out the
2.6.28-rc3 kernel from the Torvalds tree.  Happily, this kernel
boots fine... and without the need for any special parameters.
The HPET device is working, and no hang occurs at the login
prompt.  (I am submitting this BTS update using the very same
kernel, as can be seen below under "System Information"!)

I can now state that the 2.6.28 kernel series has resolved the
problems with hangs on my hardware.

It may now be possible to provide patches for 2.6.26 which will allow
it to boot without hanging on machines experiencing such problems.
Does the Debian Kernel Team have any interest in seeing such patches?
If so, I could start working on backporting the minimum set of changes
from 2.6.28 to 2.6.26 which cure the problem on my hardware.


-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.28-rc3.081104.fileserver.uvesafb (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.26-1-amd64 depends on:
ii  debconf [debconf-2.0] 1.5.22 Debian configuration management sy
ii  initramfs-tools [linux-initra 0.92j  tools for generating an initramfs
ii  module-init-tools 3.4-1  tools for managing Linux kernel mo

linux-image-2.6.26-1-amd64 recommends no packages.

Versions of packages linux-image-2.6.26-1-amd64 suggests:
ii  grub  0.97-47GRand Unified Bootloader (Legacy v
pn  linux-doc-2.6.26   (no desc

Bug#409271: Status of this bug ?

[Fabrice Lorrain]

Hello,

I've just read through bts #409271 :"initramfs-tools: NFSv4 not 
supported for root fs"

and I'm interrested in knowing the status of this bug for lenny.

Thanks,

@+,
Fab

PS : ccing nfs-aware people.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#409271: Status of this bug ?

[Steinar H. Gunderson]

On Sun, Aug 10, 2008 at 04:35:23PM +0200, Fabrice Lorrain wrote:
> I've just read through bts #409271 :"initramfs-tools: NFSv4 not  
> supported for root fs"
> and I'm interrested in knowing the status of this bug for lenny.

AFAIK my understanding is: klibc's mount doesn't support NFSv4, initramfs
insists on using klibc's mount, stalemate.

/* Steinar */
-- 
Homepage: http://www.sesse.net/



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#473180: what's the status of this bug?

[maximilian attems]

On Mon, Jun 23, 2008 at 03:53:56PM +0200, Evgeni Golov wrote:
> On Mon, Jun 23, 2008 at 03:26:59PM +0200, maximilian attems wrote:
> > > I just wanted to hear if there is any progress on building Debian's 
> > > kernels
> > > with CONFIG_FB_UVESA=m?
> > > 
> > 
> > not sure if we want that close to the release, might give some
> > bad fb regressions..
> 
> Thats should not give any regressions. It coexists fine with vesafb and
> radeonfb on my boxes.
> 1. It's a module, so users will have to load it themself.
> 2. It just prints an error until v86d[1] is installed.
> 

right due to not beeing autoloaded enabled in trunk for 2.6.26
Lenny release on x86.

thanks for report

-- 
maks



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#473180: what's the status of this bug?

[Evgeni Golov]

On Mon, Jun 23, 2008 at 03:26:59PM +0200, maximilian attems wrote:
> > I just wanted to hear if there is any progress on building Debian's kernels
> > with CONFIG_FB_UVESA=m?
> > 
> 
> not sure if we want that close to the release, might give some
> bad fb regressions..

Thats should not give any regressions. It coexists fine with vesafb and
radeonfb on my boxes.
1. It's a module, so users will have to load it themself.
2. It just prints an error until v86d[1] is installed.

Regards
Evgeni

[1] http://dev.gentoo.org/~spock/projects/uvesafb/



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#473180: what's the status of this bug?

[maximilian attems]

On Mon, Jun 23, 2008 at 03:08:47PM +0200, Evgeni Golov wrote:
> found 473180 2.6.25-5
> found 473180 2.6.24-7
> block 473176 by 473180
> thanks
> 
> Hi,
> 
> I just wanted to hear if there is any progress on building Debian's kernels
> with CONFIG_FB_UVESA=m?
> 

not sure if we want that close to the release, might give some
bad fb regressions..

-- 
maks



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#473180: what's the status of this bug?

[Evgeni Golov]

found 473180 2.6.25-5
found 473180 2.6.24-7
block 473176 by 473180
thanks

Hi,

I just wanted to hear if there is any progress on building Debian's kernels
with CONFIG_FB_UVESA=m?

Regards
Evgeni



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: what's the status of this bug?

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> found 473180 2.6.25-5
Bug#473180: linux-2.6: please build with CONFIG_FB_UVESA=m
Bug marked as found in version 2.6.25-5.

> found 473180 2.6.24-7
Bug#473180: linux-2.6: please build with CONFIG_FB_UVESA=m
Bug marked as found in version 2.6.24-7.

> block 473176 by 473180
Bug#473180: linux-2.6: please build with CONFIG_FB_UVESA=m
Bug#473176: ITP: v86d -- execute x86 BIOS code in a controlled environment
Was not blocked by any bugs.
Blocking bugs of 473176 added: 473180

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#444271: Status of this bug

[Martin Michlmayr]

Some background information explaining why this issue hasn't been
resolved yet:

http://lists.debian.org/debian-arm/2008/06/msg00029.html

-- 
Martin Michlmayr
http://www.cyrius.com/



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#317258: Status of this bug?

[jeff]

I have a NetRAID-1M and have been trying to use it in a 2.6.11 or
greater kernel. Google has not helped, and neither has the linux-scsi
ml. Is this patch ready or is more modification still needed?

Thanks for any pointers!



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]