Processed: reassign 590480 to 0.27+dfsg-4 ...

2010-07-29 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> reassign 590480 0.27+dfsg-4
Bug #590480 [linux-2.6] linux-image-2.6.32-5-amd64: webcam does not work with 
gspca driver
Bug reassigned from package 'linux-2.6' to '0.27+dfsg-4'.
Warning: Unknown package '0.27+dfsg-4'
Warning: Unknown package '0.27+dfsg-4'
Bug No longer marked as found in versions 2.6.32-15.
Warning: Unknown package '0.27+dfsg-4'
Warning: Unknown package '0.27+dfsg-4'
Warning: Unknown package '0.27+dfsg-4'
> retitle 590480 camstream: Fails to capture from gspca_vc032x driver
Bug #590480 [0.27+dfsg-4] linux-image-2.6.32-5-amd64: webcam does not work with 
gspca driver
Warning: Unknown package '0.27+dfsg-4'
Changed Bug title to 'camstream: Fails to capture from gspca_vc032x driver' 
from 'linux-image-2.6.32-5-amd64: webcam does not work with gspca driver'
Warning: Unknown package '0.27+dfsg-4'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
590480: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590480
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.12804021211605.transcr...@bugs.debian.org

Processed: [bts-link] source package linux-2.6

2010-07-29 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package linux-2.6
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #580901 (http://bugs.debian.org/580901)
> #  * http://bugzilla.kernel.org/show_bug.cgi?id=15559
> #  * remote status changed: (?) -> NEEDINFO
> usertags 580901 + status-NEEDINFO
Bug#580901: core i3: suspend to disk break multithreading
There were no usertags set.
Usertags are now: status-NEEDINFO.
> # remote status report for #574560 (http://bugs.debian.org/574560)
> #  * https://bugs.freedesktop.org/show_bug.cgi?id=26664
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 574560 + fixed-upstream
Bug #574560 [linux-2.6] linux-image-2.6.32: Netbook Philco PHN 10108 doesn't 
supported by  kernel to change LCD brightness level
Added tag(s) fixed-upstream.
> usertags 574560 + status-RESOLVED resolution-FIXED
Bug#574560: linux-image-2.6.32: Netbook Philco PHN 10108 doesn't supported by  
kernel to change LCD brightness level
There were no usertags set.
Usertags are now: status-RESOLVED resolution-FIXED.
> # remote status report for #589690 (http://bugs.debian.org/589690)
> #  * https://bugs.freedesktop.org/show_bug.cgi?id=29153
> #  * remote status changed: RESOLVED -> REOPENED
> #  * remote resolution changed: FIXED -> (?)
> #  * reopen upstream
> tags 589690 - fixed-upstream
Bug #589690 [linux-2.6] [drm/i915] oops in i915_irq_emit on 965GM with UMS
Removed tag(s) fixed-upstream.
> usertags 589690 - status-RESOLVED resolution-FIXED
Bug#589690: [drm/i915] oops in i915_irq_emit on 965GM with UMS
Usertags were: status-RESOLVED resolution-FIXED.
Usertags are now: .
> usertags 589690 + status-REOPENED
Bug#589690: [drm/i915] oops in i915_irq_emit on 965GM with UMS
There were no usertags set.
Usertags are now: status-REOPENED.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
589690: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589690
574560: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574560
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.12804212472944.transcr...@bugs.debian.org

[bts-link] source package linux-2.6

2010-07-29 Thread bts-link-upstream 
#
# bts-link upstream status pull for source package linux-2.6
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#

user bts-link-upstr...@lists.alioth.debian.org

# remote status report for #580901 (http://bugs.debian.org/580901)
#  * http://bugzilla.kernel.org/show_bug.cgi?id=15559
#  * remote status changed: (?) -> NEEDINFO
usertags 580901 + status-NEEDINFO

# remote status report for #574560 (http://bugs.debian.org/574560)
#  * https://bugs.freedesktop.org/show_bug.cgi?id=26664
#  * remote status changed: (?) -> RESOLVED
#  * remote resolution changed: (?) -> FIXED
#  * closed upstream
tags 574560 + fixed-upstream
usertags 574560 + status-RESOLVED resolution-FIXED

# remote status report for #589690 (http://bugs.debian.org/589690)
#  * https://bugs.freedesktop.org/show_bug.cgi?id=29153
#  * remote status changed: RESOLVED -> REOPENED
#  * remote resolution changed: FIXED -> (?)
#  * reopen upstream
tags 589690 - fixed-upstream
usertags 589690 - status-RESOLVED resolution-FIXED
usertags 589690 + status-REOPENED

thanks


--
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/20100729163405.11699.84091.btsl...@merkel.debian.org

Processed: unmerging 579862, found 579862 in 2.6.32-15, tagging 579862

2010-07-29 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> unmerge 579862
Bug#579862: linux-image-2.6.32-trunk-686: Fatal DMA error in b43 broadcom 
kernel module
Bug#589122: "b43-phy0: Controller RESET (DMA error)" with BCM4312 and b43 driver
Disconnected #579862 from all other report(s).

> found 579862 2.6.32-15
Bug #579862 [linux-2.6] linux-image-2.6.32-trunk-686: Fatal DMA error in b43 
broadcom kernel module
There is no source info for the package 'linux-2.6' at version '2.6.32-15' with 
architecture ''
Unable to make a source version for version '2.6.32-15'
Bug Marked as found in versions 2.6.32-15.
> tags 579862 - moreinfo
Bug #579862 [linux-2.6] linux-image-2.6.32-trunk-686: Fatal DMA error in b43 
broadcom kernel module
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
579862: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579862
589122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589122
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.128042278417904.transcr...@bugs.debian.org

Bug#590327: linux-image-2.6.32-5-amd64: Unbalanced enable for IRQ 19

2010-07-29 Thread Ben Hutchings 
On Mon, 2010-07-26 at 00:30 +0200, Jan Echternach wrote:
> Package: linux-2.6
> Version: 2.6.32-18
> Severity: minor
> 
> I'm getting this warning for quite a while now, but not on every boot.
> Stack traces below ide_pci_init_two differ slightly.  I've also tried
> the current experimental kernel, but the warning is still there (although
> the stack trace is somewhat different).
[...]

Please report this bug upstream at  under
product 'IO/Storage' component 'IDE', including the stack trace from the
experimental kernel.  Let us know the bug number or URL so that we can
track it.

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

Processed: tagging 590327

2010-07-29 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 590327 + upstream moreinfo
Bug #590327 [linux-2.6] linux-image-2.6.32-5-amd64: Unbalanced enable for IRQ 19
Added tag(s) upstream and moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
590327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590327
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.128042297619525.transcr...@bugs.debian.org

Bug#590192: linux-source-2.6.32: RTL8187SE working unstable

2010-07-29 Thread Moritz Muehlenhoff 
tags 590192 moreinfo
thanks

On Sat, Jul 24, 2010 at 12:45:49PM -0300, Joao Eriberto Mota Filho wrote:
> Package: linux-source-2.6.32
> Version: all
> Severity: normal
> Tags: upstream
> 
> The RTL8187SE is working bad on 2.6.32. I can get IP in some times.
> 
> I don't know how to make tests to send more informations now.
> Do you want to suggest any tests to generate more informations?
> 
> Thanks in advance.

The driver is from the staging section of the Linux drivers, i.e. for
drivers which do not yet match the quality standards of the rest of 
the kernel. See http://www.kroah.com/log/linux/linux-staging-update.html
for a description.

There have been quite a few bugfixes since 2.6.32, though. Please test
the 2.6.35-rc6 kernel package from experimental and tell us whether
the problem persists.

Cheers,
Moritz




-- 
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/20100729172404.ga2...@galadriel.inutil.org

Processed: Re: linux-source-2.6.32: RTL8187SE working unstable

2010-07-29 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 590192 moreinfo
Bug #590192 [linux-source-2.6.32] linux-source-2.6.32: RTL8187SE working 
unstable
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
590192: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590192
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.128042426230900.transcr...@bugs.debian.org

Processed: Found it again

2010-07-29 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> found 515754 1:1.2.2-2
Bug #515754 [nfs-common] nfs-common: Mounting with sec=krb5p fails with "access 
denied by server while mounting"
Bug Marked as found in versions nfs-utils/1:1.2.2-2.
> --
Stopping processing here.

Please contact me if you need assistance.
-- 
515754: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515754
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.128042430231260.transcr...@bugs.debian.org

Bug#588770: initramfs-tools: modules=dep in initramfs.conf breaks suspend-to-disk

2010-07-29 Thread maximilian attems 
On Mon, 12 Jul 2010, Matthias Berndt wrote:

> Package: initramfs-tools
> Version: 0.97.2
> Severity: normal
> Tags: sid
> 
> Hi,
> 
> i just noticed using modules=dep instead of modules=most breaks 
> suspend-to-disk
> for me. My swap partition lies on a PATA disk  while my root file system lies
> on a SATA disk, so  the needed PATA drivers aren't loaded and thus the device
> file for the swap partition doesn't exist. Perhaps there should be a resume
> hook script that checks for this condition?
> 

this isn't as trivial as said. the sys walking code is nicely abstracted
in a function the ugly^Wdiverse root parsing code not.
so it should do that and then one can add aboves.

this is clearly wishlist as MODULES=dep is not default.
not a priority for squeeze, thanks for the report.




-- 
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/20100728180705.gc16...@stro.at

Processed: severity of 588770 is wishlist

2010-07-29 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> severity 588770 wishlist
Bug #588770 [initramfs-tools] initramfs-tools: modules=dep in initramfs.conf 
breaks suspend-to-disk
Severity set to 'wishlist' from 'normal'

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
588770: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588770
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.12804315232668.transcr...@bugs.debian.org

Processed: bug 590661 is forwarded to http://bugzilla.openvz.org/show_bug.cgi?id=1554

2010-07-29 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> forwarded 590661 http://bugzilla.openvz.org/show_bug.cgi?id=1554
Bug #590661 [linux-2.6] linux-image-2.6.32-5-openvz-amd64: openswan ipsec 
packets do not reach openvz instances
Set Bug forwarded-to-address to 
'http://bugzilla.openvz.org/show_bug.cgi?id=1554'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
590661: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590661
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.12804315272713.transcr...@bugs.debian.org

Processed: block 590889 with 561203

2010-07-29 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> block 590889 with 561203
Bug #590889 [libqtcore4] libqtcore4: has a hardcoded sleep in thread creation 
on hppa, should be removed before release
Was not blocked by any bugs.
Added blocking bug(s) of 590889: 561203
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
590889: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590889
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.12804430928966.transcr...@bugs.debian.org

Bug#590327: linux-image-2.6.32-5-amd64: Unbalanced enable for IRQ 19

2010-07-29 Thread Jan Echternach 
On Thu, Jul 29, 2010 at 06:02:41PM +0100, Ben Hutchings wrote:
> Let us know the bug number or URL so that we can track it.

https://bugzilla.kernel.org/show_bug.cgi?id=16481

-- 
Jan



-- 
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/2010073715.ga6...@goneko.de

Processed: bug 590327 is forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=16481

2010-07-29 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> forwarded 590327 https://bugzilla.kernel.org/show_bug.cgi?id=16481
Bug #590327 [linux-2.6] linux-image-2.6.32-5-amd64: Unbalanced enable for IRQ 19
Set Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi?id=16481'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
590327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590327
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.128045143828715.transcr...@bugs.debian.org

Bug#590744: Fails to boot if /sbin/init is a symlink

2010-07-29 Thread Michael Biebl 
On 29.07.2010 03:01, Michael Prokop wrote:
> * Michael Biebl  [Thu Jul 29, 2010 at 02:16:32AM +0200]:
>> On 29.07.2010 01:37, Michael Prokop wrote:
>>> * Michael Biebl  [Thu Jul 29, 2010 at 01:13:01AM +0200]:
> 
 for testing purposes, I installed the upstart binary as /sbin/upstart and
 created a symlink /sbin/init → /sbin/upstart
 This causes a boot failure, due to this check in /usr/share/initramfs-
 tools/init
> 
 # Check init bootarg
 if [ -n "${init}" ] && [ ! -x "${rootmnt}${init}" ]; then
echo "Target filesystem doesn't have ${init}."
init=
 fi
> 
 To quote Mithrandir (from irc):
  -x follows symlinks
  but that means it'll look for symlinks in the initramfs, so 
 the
 check is buggy.
> 
>>> You shouldn't use an absolut symlink here, use a relative one instead.
>>> See Debian policy 10.5 for details.
> 
>> Well, changing it to /sbin/init -> upstart did indeed work for this 
>> particular
>> case. But I still get the problem when the link is absolute, as is specified 
>> by
>> the policy for symlinks not in the same directory.
> 
>> To be a bit more specific what I was doing:
>> I tested the new systemd init system, which installs the binary in 
>> /bin/systemd
>> (note the "/bin").
> 
> This isn't an existing + available Debian package yet, right?

It's in experimental currently.

> Why is it installing itself to /bin/systemd? Is it supposed to be
> executed by non-root users as well?

Indeed. The idea is, that systemd is also started by regular users and helps
track their user session (replacement/extension for e.g. gnome-session)

>> So I moved /sbin/init from upstart to /sbin/upstart and made
>> /sbin/init a symlink so I could easily test both systems. Using a relative
>> symlink for /sbin/upstart does work, but an absolute symlink /sbin/init ->
>> /bin/systemd does not.
>> So I'm reopening the bug report and retitling appropriately.
> 
> If systemd really uses /bin for a reason we could use something like
> the following in initramfs-tools' init:
> 
>   # Check init bootarg
>   if [ -n "${init}" ] ; then
> 
> # Work around absolute symlinks
> initsymlinktarget="${init}"
> if [ -d "${rootmnt}" ] && [ -h "${rootmnt}${init}" ] ; then
> case $(readlink "${rootmnt}${init}") in /*)
> initsymlinktarget=$(chroot "${rootmnt}" readlink "${init}")
> ;;
> esac
> fi
> 
> if [ ! -x "${rootmnt}${init}" ] || [ ! -x 
> "${rootmnt}${initsymlinktarget}" ] ; then
>   echo "Target filesystem doesn't have ${init}."
>   init=
> fi
>   fi

Does not work. For one, I guess this check
if [ ! -x "${rootmnt}${init}" ] || [ ! -x "${rootmnt}${initsymlinktarget}" ] ;

should be using &&.

Even after fixing that, we run into the same problem, later again, at:

# No init on rootmount
if [ ! -x "${rootmnt}${init}" ]; then
panic "No init found. Try passing init= bootarg."
fi

Cheers,
Michael



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#590744: Fails to boot if /sbin/init is a symlink

2010-07-29 Thread Michael Prokop 
* Michael Biebl  [Fri Jul 30, 2010 at 03:53:03AM +0200]:
> On 29.07.2010 03:01, Michael Prokop wrote:
> > * Michael Biebl  [Thu Jul 29, 2010 at 02:16:32AM +0200]:

> > Why is it installing itself to /bin/systemd? Is it supposed to be
> > executed by non-root users as well?

> Indeed. The idea is, that systemd is also started by regular users and helps
> track their user session (replacement/extension for e.g. gnome-session)

Ok.

> >> So I moved /sbin/init from upstart to /sbin/upstart and made
> >> /sbin/init a symlink so I could easily test both systems. Using a relative
> >> symlink for /sbin/upstart does work, but an absolute symlink /sbin/init ->
> >> /bin/systemd does not.
> >> So I'm reopening the bug report and retitling appropriately.

> > If systemd really uses /bin for a reason we could use something like
> > the following in initramfs-tools' init:

> >   # Check init bootarg
> >   if [ -n "${init}" ] ; then

> > # Work around absolute symlinks
> > initsymlinktarget="${init}"
> > if [ -d "${rootmnt}" ] && [ -h "${rootmnt}${init}" ] ; then
> > case $(readlink "${rootmnt}${init}") in /*)
> > initsymlinktarget=$(chroot "${rootmnt}" readlink "${init}")
> > ;;
> > esac
> > fi

> > if [ ! -x "${rootmnt}${init}" ] || [ ! -x 
> > "${rootmnt}${initsymlinktarget}" ] ; then
> >   echo "Target filesystem doesn't have ${init}."
> >   init=
> > fi
> >   fi

> Does not work. For one, I guess this check
> if [ ! -x "${rootmnt}${init}" ] || [ ! -x "${rootmnt}${initsymlinktarget}" ] ;

> should be using &&.

> Even after fixing that, we run into the same problem, later again, at:

> # No init on rootmount
> if [ ! -x "${rootmnt}${init}" ]; then
> panic "No init found. Try passing init= bootarg."
> fi

You have to drop the old "No init on rootmount" stuff of course, so
just replace the "No init on rootmount" part with above code.

regards,
-mika-


signature.asc
Description: Digital signature

Bug#590744: Fails to boot if /sbin/init is a symlink

2010-07-29 Thread Michael Biebl 
On 30.07.2010 03:57, Michael Prokop wrote:
> * Michael Biebl  [Fri Jul 30, 2010 at 03:53:03AM +0200]:
>> On 29.07.2010 03:01, Michael Prokop wrote:
>>> * Michael Biebl  [Thu Jul 29, 2010 at 02:16:32AM +0200]:
> 
>>> Why is it installing itself to /bin/systemd? Is it supposed to be
>>> executed by non-root users as well?
> 
>> Indeed. The idea is, that systemd is also started by regular users and helps
>> track their user session (replacement/extension for e.g. gnome-session)
> 
> Ok.
> 
 So I moved /sbin/init from upstart to /sbin/upstart and made
 /sbin/init a symlink so I could easily test both systems. Using a relative
 symlink for /sbin/upstart does work, but an absolute symlink /sbin/init ->
 /bin/systemd does not.
 So I'm reopening the bug report and retitling appropriately.
> 
>>> If systemd really uses /bin for a reason we could use something like
>>> the following in initramfs-tools' init:
> 
>>>   # Check init bootarg
>>>   if [ -n "${init}" ] ; then
> 
>>> # Work around absolute symlinks
>>> initsymlinktarget="${init}"
>>> if [ -d "${rootmnt}" ] && [ -h "${rootmnt}${init}" ] ; then
>>> case $(readlink "${rootmnt}${init}") in /*)
>>> initsymlinktarget=$(chroot "${rootmnt}" readlink "${init}")
>>> ;;
>>> esac
>>> fi
> 
>>> if [ ! -x "${rootmnt}${init}" ] || [ ! -x 
>>> "${rootmnt}${initsymlinktarget}" ] ; then
>>>   echo "Target filesystem doesn't have ${init}."
>>>   init=
>>> fi
>>>   fi
> 
>> Does not work. For one, I guess this check
>> if [ ! -x "${rootmnt}${init}" ] || [ ! -x "${rootmnt}${initsymlinktarget}" ] 
>> ;
> 
>> should be using &&.
> 
>> Even after fixing that, we run into the same problem, later again, at:
> 
>> # No init on rootmount
>> if [ ! -x "${rootmnt}${init}" ]; then
>> panic "No init found. Try passing init= bootarg."
>> fi
> 
> You have to drop the old "No init on rootmount" stuff of course, so
> just replace the "No init on rootmount" part with above code.

I think this check is required if "# Search for valid init" does not find a
valid init?

Besides, I noticed that if no valid init is found, I get a kernel panic, but I
assume I should get a rescue shell.

I also noticed, that initsymlinktarget is set (ie. we run and expensive chroot
call), even if I pass init=/bin/systemd on the kernel command line.

Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#590744: Fails to boot if /sbin/init is a symlink

2010-07-29 Thread Michael Biebl 
On 30.07.2010 04:15, Michael Biebl wrote:

> 
> Besides, I noticed that if no valid init is found, I get a kernel panic, but I
> assume I should get a rescue shell.

I guess this might be due to the following:
# Search for valid init
if [ -z "${init}" ] ; then
for init in /sbin/init /etc/init /bin/init /bin/sh; do
if [ ! -x "${rootmnt}${init}" ]; then
continue
fi
break
done
fi

Upstart stores its configuration files in /etc/init/. This means, the loop above
exits at /etc/init, and the init variable is set to the /etc/init directory.
Is there a good resp. historical reason to search for init in /etc (or /bin 
ftm)?




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#590744: Fails to boot if /sbin/init is a symlink

2010-07-29 Thread Michael Prokop 
* Michael Biebl  [Fri Jul 30, 2010 at 04:26:16AM +0200]:
> On 30.07.2010 04:15, Michael Biebl wrote:

> > Besides, I noticed that if no valid init is found, I get a kernel panic, 
> > but I
> > assume I should get a rescue shell.

> I guess this might be due to the following:
> # Search for valid init
> if [ -z "${init}" ] ; then
> for init in /sbin/init /etc/init /bin/init /bin/sh; do
> if [ ! -x "${rootmnt}${init}" ]; then
> continue
> fi
> break
> done
> fi

> Upstart stores its configuration files in /etc/init/.

D'oh.

> This means, the loop above exits at /etc/init, and the init
> variable is set to the /etc/init directory. Is there a good resp.
> historical reason to search for init in /etc (or /bin ftm)?

The kernel uses /sbin/init, /etc/init, /bin/init and /bin/sh
for its run_init_process().

regards,
-mika-


signature.asc
Description: Digital signature

Bug#590744: Fails to boot if /sbin/init is a symlink

2010-07-29 Thread Michael Prokop 
* Michael Biebl  [Fri Jul 30, 2010 at 04:15:44AM +0200]:
> On 30.07.2010 03:57, Michael Prokop wrote:

> >> Does not work. For one, I guess this check
> >> if [ ! -x "${rootmnt}${init}" ] || [ ! -x "${rootmnt}${initsymlinktarget}" 
> >> ] ;

> >> should be using &&.

> >> Even after fixing that, we run into the same problem, later again, at:

> >> # No init on rootmount
> >> if [ ! -x "${rootmnt}${init}" ]; then
> >> panic "No init found. Try passing init= bootarg."
> >> fi

> > You have to drop the old "No init on rootmount" stuff of course, so
> > just replace the "No init on rootmount" part with above code.

[...]
> I also noticed, that initsymlinktarget is set (ie. we run and expensive chroot
> call), even if I pass init=/bin/systemd on the kernel command line.

No, initsymlinktarget is set to $init, but evaluated only if
${rootmnt}${init} is a symlink.

Can you please give the following snapshot version a try:

  
http://people.debian.org/~mika/initramfs-tools/initramfs-tools_0.97.3~1.gbp8d572e_all.deb

(sha1sum and gpg-signed sha1sum in the same directory) and report
back whether this works for all the situations you expect to work?

regards,
-mika-


signature.asc
Description: Digital signature

Bug#585625: Switch to i915/KMS lefts console unusable

2010-07-29 Thread Andrew Lee 
Hi Ben and others,

On 2010年07月27日 18:25, Ben Hutchings wrote:
> Since we applied all the DRM changes from Linux 2.6.33 in 2.6.32-10, you
> could start bisecting with this command:
> 
> git bisect v2.6.33 v2.6.32 drivers/gpu/drm/i915

I never did bisect before. I have been trying my first time. It has been
compiling and compiling and compiling and compiling kernel on my
laptop.

I relized I have limited time to get together with our people in DebCamp
and DebConfr. I am not sure if this is a bester way to do it and
saves time?

>> And should I also test 2.6.35-rc5 vanilla kernel to see if I can
>> reproduce this problem still?
> 
> I suggest you test a 2.6.35-rc6 kernel package from experimental.

Let me report this test first. It doesn't work and had problem the
screen is blank.

Hope this helpful,

-Andrew



--
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/4c526756.6060...@debian.org