Bug#515255: linux-image-2.6.18-6-xen-vserver-686: No grub entry's after install of kernel, and when I add it by hand the kernel can't start

2009-02-15 Thread Henrik Dige Semark
Package: linux-image-2.6.18-6-xen-vserver-686
Version: 2.6.18.dfsg.1-24
Severity: important


This is a very big problem for my anyway, I have to use both Xen and Vserver, 
and the kernel can provide my both, but when I install it, (both amd64 
and 686 kernel) it says “Changing /boot/grub/menu.lst” but there is 
nothing changed in menu.lst so I can't start the kernel, then I entered 
it by hand (see my menu.lst below) and rebooted and tried to start the 
new kernel, but then it boots and stops with “waiting for root filesystem... 
...” and then never continues

*** My menu.lst ***

## ## End Default Options ##

title   Debian GNU/Linux, kernel 2.6.18-6-686
root(hd2,0)
kernel  /boot/vmlinuz-2.6.18-6-686 root=/dev/md1 ro
initrd  /boot/initrd.img-2.6.18-6-686
savedefault

title   Debian GNU/Linux, kernel 2.6.18-6-xen-vserver-686
root(hd2,0)
kernel  /boot/vmlinuz-2.6.18-6-xen-vserver-686 root=/dev/md1 ro
initrd  /boot/initrd.img-2.6.18-6-xen-vserver-686
savedefault

title   Debian GNU/Linux, kernel 2.6.18-6-vserver-686
root(hd2,0)
kernel  /boot/vmlinuz-2.6.18-6-vserver-686 root=/dev/md1 ro
initrd  /boot/initrd.img-2.6.18-6-vserver-686
savedefault


*** ls -a of /boot ***
config-2.6.18-6-486
config-2.6.18-6-686
config-2.6.18-6-vserver-686
config-2.6.18-6-xen-vserver-686
grub
initrd.img-2.6.18-6-486
initrd.img-2.6.18-6-486.bak
initrd.img-2.6.18-6-686
initrd.img-2.6.18-6-vserver-686
initrd.img-2.6.18-6-xen-vserver-686
initrd.img-2.6.18-6-xen-vserver-686.bak
System.map-2.6.18-6-486
System.map-2.6.18-6-686
System.map-2.6.18-6-vserver-686
System.map-2.6.18-6-xen-vserver-686
vmlinuz-2.6.18-6-486
vmlinuz-2.6.18-6-686
vmlinuz-2.6.18-6-vserver-686
vmlinuz-2.6.18-6-xen-vserver-686



-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-686
Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6.18-6-xen-vserver-686 depends on:
ii  initramfs-tools 0.85itools for generating an initramfs
ii  linux-modules-2.6.18-6- 2.6.18.dfsg.1-24 Linux 2.6.18 modules on i686

Versions of packages linux-image-2.6.18-6-xen-vserver-686 recommends:
pn  libc6-xen  (no description available)

-- no debconf information



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#515261: linux-image-xen-686: missing dependancy to xen-linux-system-2.6.26-1-xen-686

2009-02-15 Thread Michael Rasmussen
Package: linux-image-xen-686
Severity: critical
Justification: breaks the whole system

When doing a full-upgrade from etch to lenny on a system running xen the xen 
hypervisor is not updated accordingly.
A dependancy to xen-linux-system-2.6.26-1-xen-686 is missing which means that 
grub is configured to use the xen
hypervisor from etch to run the 2.6.26-xen kernel. Result is an unbootable 
system.
Adding xen-linux-system-2.6.26-1-xen-686 will solve the issue since this 
correctly instructs grub to use the new
xen hyperviser from lenny.

-- System Information:
Debian Release: 5.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Re: Bug#515255: linux-image-2.6.18-6-xen-vserver-686: No grub entry's after install of kernel, and when I add it by hand the kernel can't start

2009-02-15 Thread Michael Rasmussen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi

If the system in question is a dom0 you are missing some references to
the xen hypervisor.

An example entry from my menu.lst
title   Xen 3.0.3-1-amd64 / Debian GNU/Linux, kernel
2.6.18-6-xen-amd64
root(hd0,0)
kernel  /boot/xen-3.0.3-1-amd64.gz
module  /boot/vmlinuz-2.6.18-6-xen-amd64 root=/dev/md0 ro
xencons=tty
module  /boot/initrd.img-2.6.18-6-xen-amd64


- -- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael  rasmussen  cc
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
mir  datanom  net
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
mir  miras  org
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
- --
Replace repetitive expressions by calls to a common function.
- The Elements of Programming Style (Kernighan & Plaugher)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkmYCFsACgkQQQOPluUB9RwK+ACeN54sExvKr22GrEtG1lCYD34C
9mcAn2aJGLh+WHn/a69yRKH3Ow77Co1i
=54yE
-END PGP SIGNATURE-


Bug#515277: r8169.c: incorrect RX dropped counter

2009-02-15 Thread kronberg . tatiana
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-8
Severity: normal

During a network session RX dropped counter shows great numbers.  All
the other things of the network are fine. The typical value of the
counter is  of the order of magnitude of 10^9, eg.,

$ /sbin/ifconfig eth0 | grep "RX packets"
RX packets:483 errors:0 dropped:3771247613 overruns:0 frame:0
$

The problem appears with the following network adapter:

$ lspci -nn -s 01:00.0
01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8101E/RTL8102E PCI Express Fast Ethernet controller [10ec:8136] (rev 02)
$

The same issue was mentioned with the kernel: `Linux 2.6.24-1-686' and
`RTL8111/8168B PCI Express Gigabit Ethernet controller' [1].

Francois Romieu suggested a patch [2] for `r8169.c' to solve the problem.

Please consider applying the patch to the Debian package.

[1] http://bugs.debian.org/497757
[2] https://kerneltrap.org/mailarchive/linux-netdev/2008/9/13/3288264/thread

Thanks,

Tatiana Kronberg



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#515261: linux-image-xen-686: missing dependancy to xen-linux-system-2.6.26-1-xen-686

2009-02-15 Thread Bastian Blank
severity 515261 important
thanks

On Sun, Feb 15, 2009 at 01:06:38PM +0100, Michael Rasmussen wrote:
> Justification: breaks the whole system

The kernel is the system, so not applicable.

> When doing a full-upgrade from etch to lenny on a system running xen the xen 
> hypervisor is not updated accordingly.
> A dependancy to xen-linux-system-2.6.26-1-xen-686 is missing which means that 
> grub is configured to use the xen
> hypervisor from etch to run the 2.6.26-xen kernel. Result is an unbootable 
> system.

This can happen with every kernel update. There was plans to add a meta
package for xen-linux-system, but it was never finished.

Bastian

-- 
... bacteriological warfare ... hard to believe we were once foolish
enough to play around with that.
-- McCoy, "The Omega Glory", stardate unknown



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Processed: Re: Bug#515261: linux-image-xen-686: missing dependancy to xen-linux-system-2.6.26-1-xen-686

2009-02-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 515261 important
Bug#515261: linux-image-xen-686: missing dependancy to 
xen-linux-system-2.6.26-1-xen-686
Severity set to `important' from `critical'

> thanks
Stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Processed: reassign 515073 to linux-2.6, found 515073 in 2.6.26-8

2009-02-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> # Automatically generated email from bts, devscripts version 2.10.35lenny3
> reassign 515073 linux-2.6
Bug#515073: linux-image-2.6.26-1-vserver-686: realtek r8139.ko shows erattic 
packets dropped (changes fast, always) from ifconfig
Bug reassigned from package `linux-image-2.6.26-1-vserver-686' to `linux-2.6'.

> found 515073 2.6.26-8
Bug#515073: linux-image-2.6.26-1-vserver-686: realtek r8139.ko shows erattic 
packets dropped (changes fast, always) from ifconfig
Bug marked as found in version 2.6.26-8.

>
End of message, stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Processed: reassign 515277 to linux-2.6, forcibly merging 515073 515277

2009-02-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> # Automatically generated email from bts, devscripts version 2.10.35lenny3
> reassign 515277 linux-2.6
Bug#515277: r8169.c: incorrect RX dropped counter
Bug reassigned from package `linux-image-2.6.26-1-amd64' to `linux-2.6'.

> forcemerge 515073 515277
Bug#515073: linux-image-2.6.26-1-vserver-686: realtek r8139.ko shows erattic 
packets dropped (changes fast, always) from ifconfig
Bug#515277: r8169.c: incorrect RX dropped counter
Forcibly Merged 515073 515277.

>
End of message, stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#514292: linux-image-2.6.28-1-amd64: Bad page state in process 'emacs'

2009-02-15 Thread Luca Capello
Hi there!

On Tue, 10 Feb 2009 17:26:41 +0100, maximilian attems wrote:
> how easily can you reproduce!?
> if easily please consider to tell bugzilla.kernel.org
> and let us know the bug number.

It is not easy at all: it was the first time I experienced such an error
and unfortunately I have not seen it again.  I reported it because the
machine was completely frozen.

However, I am experiencing various issues with the latest 2.6.28
kernels, including a thermal error thought to have been solved [1]:
either my X60 is dying or 2.6.28 has some problems.  Shoulw I report
every trace I get?  FYI, I have s2disk/kmmc traces now :-(

[1] http://thread.gmane.org/gmane.linux.acpi.devel/37230

> also please upgrade to latest snapshot it features all stable
> releases up to 2.6.28.4

I usually upgrade my sid every morning, but I do not reboot every day,
since I use a lot s2disk.  I will try to keep an eye on my syslog and
reboot as soon as I spot an error.

Thx, bye,
Gismo / Luca


pgpLecYxCmdaj.pgp
Description: PGP signature


Re: [PATCH] Do not pass exit code through on pipe failure

2009-02-15 Thread maximilian attems
On Sun, 15 Feb 2009, Kees Cook wrote:

> Since "exit 2" has a special meaning, we must "exit 1" when the
> find/cpio/gzip pipe fails, otherwise "update-initramfs" will potentially
> ignore failures (it ignores return code "2" from mkinitramfs).
> 
> Signed-off-by: Kees Cook 

thanks, applied.

> ---
>  mkinitramfs |4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/mkinitramfs b/mkinitramfs
> index 2f5112c..d1d46b0 100755
> --- a/mkinitramfs
> +++ b/mkinitramfs
> @@ -268,7 +268,7 @@ fi
>  [ "${verbose}" = y ] && echo "Building cpio ${outfile} initramfs"
>  (
>  # work around lack of "set -o pipefail" for the following pipe:
> -# cd "${DESTDIR}" && find . | cpio --quiet --dereference -o -H newc | gzip 
> >"${outfile}"
> +# cd "${DESTDIR}" && find . | cpio --quiet --dereference -o -H newc | gzip 
> >"${outfile}" || exit 1
>  exec 3>&1
>  eval `
>  # http://cfaj.freeshell.org/shell/cus-faq-2.html
> @@ -284,7 +284,7 @@ eval `
>  if [ "$ec1" -ne 0 ]; then exit "$ec1"; fi
>  if [ "$ec2" -ne 0 ]; then exit "$ec2"; fi
>  if [ "$ec3" -ne 0 ]; then exit "$ec3"; fi
> -) || exit $?
> +) || exit 1
>  
>  if [ -s "${__TMPCPIOGZ}" ]; then
>   cat "${__TMPCPIOGZ}" >>"${outfile}" || exit 1
> -- 
> 1.6.0.4
> 
> -- 
> Kees Cook@debian.org
-- 
maks


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#514292: linux-image-2.6.28-1-amd64: Bad page state in process 'emacs'

2009-02-15 Thread Jonas Smedegaard
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sun, Feb 15, 2009 at 07:12:22PM +0100, Luca Capello wrote:
>Hi there!
>
>On Tue, 10 Feb 2009 17:26:41 +0100, maximilian attems wrote:
>> how easily can you reproduce!?
>> if easily please consider to tell bugzilla.kernel.org
>> and let us know the bug number.
>
>It is not easy at all: it was the first time I experienced such an error
>and unfortunately I have not seen it again.  I reported it because the
>machine was completely frozen.
>
>However, I am experiencing various issues with the latest 2.6.28
>kernels, including a thermal error thought to have been solved [1]:
>either my X60 is dying or 2.6.28 has some problems.  Shoulw I report
>every trace I get?  FYI, I have s2disk/kmmc traces now :-(
>
>[1] http://thread.gmane.org/gmane.linux.acpi.devel/37230
>
>> also please upgrade to latest snapshot it features all stable
>> releases up to 2.6.28.4
>
>I usually upgrade my sid every morning, but I do not reboot every day,
>since I use a lot s2disk.  I will try to keep an eye on my syslog and
>reboot as soon as I spot an error.

Beware that if you upgrade the running kernel, then things like 
hibernation (which unloads and reloads drivers) won't work until next 
reboot.



  - Jonas

- -- 
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

  [x] quote me freely  [ ] ask before reusing  [ ] keep private
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkmYZTsACgkQn7DbMsAkQLj3VgCfTq+/RMR+AjcXeptf+qoBr2Hj
cDQAn3dVKgkwlOCBk9VJz/wHDOT3/rPn
=DmQ0
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#514292: linux-image-2.6.28-1-amd64: Bad page state in process 'emacs'

2009-02-15 Thread Luca Capello
Hi Jonas!

On Sun, 15 Feb 2009 19:55:55 +0100, Jonas Smedegaard wrote:
> On Sun, Feb 15, 2009 at 07:12:22PM +0100, Luca Capello wrote:
>> I usually upgrade my sid every morning, but I do not reboot every
>> day, since I use a lot s2disk.  I will try to keep an eye on my
>> syslog and reboot as soon as I spot an error.
>
> Beware that if you upgrade the running kernel, then things like
> hibernation (which unloads and reloads drivers) won't work until next
> reboot.

Without going into details (since I do not have the time to check again
how it works), AFAIK uswsusp (which ships s2disk) does not unload/reload
any module by default.  This shoul mean that if you do not require any
new module, the fact that the kernel has been upgraded should not cause
any problem.

Thx, bye,
Gismo / Luca


pgpCbSijNLTM2.pgp
Description: PGP signature


Re: Problem with CIFS on Lenny?

2009-02-15 Thread Harald Krammer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Harald Krammer schrieb:
> Ben Hutchings schrieb:
>> On Fri, 2009-02-13 at 14:12 +0100, Harald Krammer wrote:
>> [...]
>>> Hello Ben,
>>> I did my network configuration with the Debian installer,  selected DHCP
>>> and nothing more.
>>>
>>> h...@hkpc:~$ ps axu | grep -i network
>>> root  3073  0.0  0.0  12972  2084 ?Ssl  07:45   0:00
>>> /usr/sbin/NetworkManager --pid-file
>>> /var/run/NetworkManager/NetworkManager.pid
>>> root  3081  0.0  0.0   3504  1324 ?Ss   07:45   0:00
>>> /usr/sbin/NetworkManagerDispatcher --pid-file
>>> /var/run/NetworkManager/NetworkManagerDispatcher.pid
>>>
>>> Here is my /etc/network/interfaces :
>>> # The loopback network interface
>>> auto lo
>>> iface lo inet loopback
>>>
>>> # The primary network interface
>>> allow-hotplug eth0
>>> iface eth0 inet dhcp
>> That means that eth0 is managed by NetworkManager and not ifupdown.  You
>> should change "allow-hotplug eth0" to "auto eth0".
>> See /usr/share/doc/network-manager/README.Debian for more details.
> 
>> Ben.
> 
> 
> Hello Ben,
> sure it will work on my workstation, but other users will use the
> NetworkManager (rather default configuration) together with CIFS/NFS
> shares and the problem appears again.
> 
> The shut down process runs following steps:
> [...]
> *) K14network-manger(stops nm, get eth0 down?)
> *) K14network-manger-dispatcher (stops nm-dis)
> [...]
> *) S31umountnfs.sh  Possible race when eth0 is already down?
> Time-out messages from Kernel
> *) S35networking'ifdown -a  only when no network fs is mounted
> *) S36ifupdown  Cleaning up ifupdown
> *) SS40umountfs unmount fs
> *) SS60umountroot   unmount root fs
> *) SS90halt bye bye
> 
> 
> I think it's not a kernel related issue. I will look into step
> K14network-manger to verify my suspicion.
> 

It's true. K14network-manger kills my network interface and so
S31umountnfs.sh runs in a time out...

Nice greetings,
Harald


- --

Harald Krammer
Brucknerstrasse 33
A - 4020  Linz
AUSTRIA

Mobil +43.(0) 664. 130 59 58
Mail: Harald.Krammer (at) hkr.at
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREIAAYFAkmYeHkACgkQ9QlAsubHO9sCqQCfSJxWIOXltW4ygmDU90FVhZpL
JZgAmQE5n0zKCGBJNbsrYm8HbkQ8AwIH
=IfGg
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#357538: marked as done (initramfs-tools: can't boot into new 2.6.15 evms system)

2009-02-15 Thread Debian Bug Tracking System

Your message dated Sun, 15 Feb 2009 21:53:59 +0100
with message-id <20090215205359.gb24...@stro.at>
and subject line Re: initramfs-tools: can't boot into new 2.6.15 evms system
has caused the Debian Bug report #357538,
regarding initramfs-tools: can't boot into new 2.6.15 evms system
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
357538: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357538
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.55b
Severity: normal


I am running a mostly testing system under a 2.4.27 kernel.  I built a
2.6.15 kernel with the latest sources (2.6.15-8).  kernel-package
10.036.  lilo 22.6.1-7 and installed it with the latest unstable
initramfs-tools (0.55b).

When I boot the system I end up in busybox with no disk partitions
mounted.  When I try to mount my root partition on a mount point, I
get "cramfs wrong magic."

I'm using evms, and I suspect it's involved in these problems.  I use
lvm through it, but have no lvm packages installed.

Here is a rough transcription of the console toward the end:

Begin: Mounting root file system.
Begin: Running /scripts/local-top
device-mapper: 4.4.0-ioctl (2005-01-12) initialised
/scripts/local-top/lvm: 36 vgchange: not found
# bug 354708 involv3s an error with that file
# and notes it's not there because a current lvm is not
# installed.  I have neither an old nor a new one.
Done.
/init: 1: cannot open /dev/root: No such device or address
Begin: Running /scripts/local-premount
Done:
Usage: modprobe # several lines of instructions
# suggests something is invoking modprobe improperly
,pimt"
Cannot read /etc/fstab: No such file or dir
Done
Running /scripts/log-bottom
Running /scripts/init-bottom
mount: /root/dev on /dev/.static/dev failed
mount: Mounting /sys on /root/sys failed: no such...
mount: Mounting /proc on /root/proc failed...
Target filesysem doesn't have /sbin/init
BusyBox 1:1.01-4
-

Though I am running evms now, the transition to 2.6 is particularly
delicate because under 2.6 evms must control all partitions on a
disk.  Under 2.4 my root is a vanilla partition.  I've edited fstab
and lilo.conf in ways I think are appropriate, but the environment in
which initramfs runs is significantly different from that in which the
ramdisk will execute.  The change from devfs to udev is another
example of this.

I don't know what's going on, or even the extent to which this is an
initramfs-tools issue.  I'm happy to provide more info or conduct
other experiments.

Here are some configuration snippets
- fstab -
# I use the next line for my current 2.4 system
/dev/sda8   /   ext2defaults 1 1
# I use the line below for 2.6
#/dev/evms/newroot  /   ext2defaults 1 1

# I was using devfs for 2.4, but have disabled it
# during the 2.6 transition.  2.6.15 doesn't do devfs
#devfs  /devdevfs defaults 0 0

proc/proc   procdefaults0 0
none/proc/bus/usb   usbfs   defaults0 0
# other partitions omitted
--- lilo.conf --
prompt
default=debian
boot=/dev/sda
lba32
install=menu
map=/boot/map

# what I'm trying to use for the 2.6 kernel
image=/vmlinuz
initrd=/initrd.img
label=debian
root=/dev/evms/newroot

# working for the 2.4 kernel
image=/vmlinuz.old
label=debian-old
root=/dev/discs/disc0/part8
append="hda=ide-scsi hdb=ide-scsi"


I've got 2.6 with evms running at home (built with the tools of a
couple months ago).

This system is dual-processor Athlon; one SCSI disk and some optical
drives.

My latest lilo run was triggered when I upgraded to the unstable
initramfs-tools.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (50, 'unstable'), (40, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27adnvcd
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages initramfs-tools depends on:
ii  busybox   1:1.01-4   Tiny utilities for small and embed
ii  cpio  2.6-10 GNU cpio -- a program to manage ar
ii  klibc-utils   1.2.2-3small statically-linked utilities 
ii  udev  0.085-1/dev/ and hotplug manage

Bug#411284: marked as done (evms_activate complains about missing lib in initramfs)

2009-02-15 Thread Debian Bug Tracking System

Your message dated Sun, 15 Feb 2009 21:54:55 +0100
with message-id <20090215205455.gc24...@stro.at>
and subject line re: evms_activate complains about missing lib in initramfs
has caused the Debian Bug report #411284,
regarding evms_activate complains about missing lib in initramfs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
411284: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=411284
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.85e
Severity: normal

The created initramfs for some reason seems to fail to activate evms.

I have a setup where I have evms+lvm2, and an evms-volume
"root-crypted" is a luks volume of the root file system.

This is what happens (typed, not captured from serial console or
something, so any typos are mine):


Begin: Mounting root file system ...
Begin: Running /scripts/local-top ...
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-de...@redhat.com
   Volume group "root" not found
Done.
Begin: Waiting for root file system...


I don't know what causes the message about vg "root" to not be found.
I have no such vg, although it might be that I have have once had
such.

Once I get dropped to busybox shell, inspecting /dev reveals there is
no /dev/evms directory. Running evms_activate from the shell correctly
creates the directory and the nodes/mappings there, but after that
fails with


libgcc_s.so.1 must be installed for pthread_cancel to work
Aborted


However the nodes and mappings apparently have been correctly created
before that.

After that, I run "cryptsetup luksOpen /dev/evms/root-crypted
root-decrypted" and enter my root filesystem password.
/dev/mapper/root-decrypted is created. Then typing "exit" allows the
boot process to continue and finish successfully.

All the required block devices are correctly detected in the boot
process (I have hda, hdd, sda. Of these all are detected, but only sda
should be needed for booting after grub; the initramfs and kernel are
on a partition on hda).

Here's how my evms/lvm2 is setup (the volume1-root in the output below
is my old root, not the current one; the current one is
root-decrypted):


# dmsetup --tree ls
hda4 (254:3)
 `- (3:0)
volume1-root (254:19)
 `-hdd3 (254:7)
`- (22:64)
hda3 (254:2)
 `- (3:0)
my_container-test--region (254:22)
 `-sda6 (254:10)
`- (8:0)
hda2 (254:1)
 `- (3:0)
my_container-my_region (254:20)
 `-sda5 (254:9)
`- (8:0)
hdd4 (254:6)
 `- (22:64)
lvm2|volume1|root (254:8)
 `-hdd3 (254:7)
`- (22:64)
hda1 (254:0)
 `- (3:0)
hdd2 (254:5)
 `- (22:64)
swap-crypted (254:15)
 `-lvm2|my_container|swap1 (254:14)
`-sda6 (254:10)
   `- (8:0)
hdd1 (254:4)
 `- (22:64)
test-volume (254:17)
 `-lvm2|my_container|test-region (254:16)
`-sda6 (254:10)
   `- (8:0)
sda1 (254:13)
 `- (8:0)
my_container-swap1 (254:21)
 `-sda6 (254:10)
`- (8:0)
root-decrypted (254:18)
 `-root-crypted (254:12)
`-lvm2|my_container|my_region (254:11)
   `-sda5 (254:9)
  `- (8:0)


Additionally there's something wrong with the busybox shell: ctrl-c
and ctrl-z do not work in it, so if I issue e.g. the commad "cat" in
the shell, I'm stuck forever.

The kernel I'm running is the Debian-provided
linux-image-2.6.18-4-amd64 2.6.18.dfsg.1-10.

You can get the generated initramfs from
http://users.tkk.fi/~sliedes/my-initramfs
.

Sami


-- Package-specific info:
-- /proc/cmdline
root=/dev/mapper/root-decrypted ro 

-- /proc/filesystems
cramfs
ext3
ext2

-- lsmod
Module  Size  Used by
radeon116384  2 
drm87080  3 radeon
binfmt_misc17292  1 
freq_table  9728  0 
ppdev  14088  0 
lp 17736  0 
button 12192  0 
ac 10376  0 
battery15496  0 
ipv6  285664  18 
ext2   70416  1 
it87   28708  0 
hwmon_vid   7424  1 it87
i2c_isa10752  1 it87
eeprom 12560  0 
usbmouse   10496  0 
ide_cd 45088  0 
cdrom  40488  1 ide_cd
tsdev  13056  0 
snd_mpu401  

[bts-link] source package linux-2.6

2009-02-15 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 #490694
#  * http://bugzilla.kernel.org/show_bug.cgi?id=12436
#  * remote status changed: (?) -> NEW
usertags 490694 + status-NEW

# remote status report for #515277
#  * http://bugzilla.kernel.org/show_bug.cgi?id=10180
#  * remote status changed: (?) -> RESOLVED
#  * remote resolution changed: (?) -> PATCH-ALREADY-AVAILABLE
usertags 515277 + status-RESOLVED resolution-PATCH-ALREADY-AVAILABLE

# remote status report for #515277
#  * http://bugzilla.kernel.org/show_bug.cgi?id=10180
#  * remote status changed: (?) -> RESOLVED
#  * remote resolution changed: (?) -> PATCH-ALREADY-AVAILABLE
usertags 515277 + status-RESOLVED resolution-PATCH-ALREADY-AVAILABLE

thanks


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#515514: linux-image-2.6.26-1-amd64: combination of kernel amd64 and 6G memory by using a lvm in a software raid creates a kernel panic

2009-02-15 Thread Jochen Becker
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-13
Severity: critical
Justification: breaks the whole system

by copying data from one software raid device into annother a kernel panic 
comes up

newstorage
2 harddiscs wdc 750 ayps combined with software raid 1
into software raid lvm pv and into this ext3 filesystems

old storage
2 harddisks samsung 400 software raid1 into it ext3 file system nolvm

copying data from old stroage to new storage failed

i removed 2G memory so that there will be only 4 in the system and mounted the 
old filesystem as ext2 
and everything works fine.


it is a productive system so i will not test it any more with more than 4 G 
memory




-- Package-specific info:
** Version:
Linux version 2.6.26-1-amd64 (Debian 2.6.26-13) (wa...@debian.org) (gcc version 
4.1.3 20080704 (prerelease) (Debian 4.1.2-24)) #1 SMP Sat Jan 10 17:57:00 UTC 
2009

** Command line:
root=/dev/mapper/vgcamelot-lvmRoot ro quiet

** Tainted: P (1)

** Kernel log:
[   10.062847] raid1: raid set md0 active with 2 out of 2 mirrors
[   10.062847] md: md2 stopped.
[   10.127932] md: bind
[   10.127932] md: bind
[   10.136134] raid1: raid set md2 active with 2 out of 2 mirrors
[   10.136134] md: md1 stopped.
[   10.211307] md: bind
[   10.211502] md: bind
[   10.218256] raid1: raid set md1 active with 2 out of 2 mirrors
[   10.290730] device-mapper: uevent: version 1.0.3
[   10.290730] device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised: 
dm-de...@redhat.com
[   10.303601] hda: No disk in drive
[   10.315661] hdb: No disk in drive
[   10.447604] PM: Starting manual resume from disk
[   10.475138] kjournald starting.  Commit interval 5 seconds
[   10.475138] EXT3-fs: mounted filesystem with ordered data mode.
[   11.683110] udevd version 125 started
[   12.233076] input: Power Button (FF) as /class/input/input4
[   12.291446] ACPI: Power Button (FF) [PWRF]
[   12.291515] input: Power Button (CM) as /class/input/input5
[   12.360070] ACPI: Power Button (CM) [PWRB]
[   12.488651] Bluetooth: Core ver 2.11
[   12.504653] NET: Registered protocol family 31
[   12.504653] Bluetooth: HCI device and connection manager initialized
[   12.504653] Bluetooth: HCI socket layer initialized
[   12.520836] Bluetooth: HCI USB driver ver 2.9
[   12.520836] usbcore: registered new interface driver hci_usb
[   12.520836] i801_smbus :00:1f.3: enabling device (0001 -> 0003)
[   12.520836] ACPI: PCI Interrupt :00:1f.3[C] -> GSI 18 (level, low) -> 
IRQ 18
[   12.576835] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.03 (30-Apr-2008)
[   12.576835] iTCO_wdt: Found a ICH8 or ICH8R TCO device (Version=2, 
TCOBASE=0x0860)
[   12.576835] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   12.586320] input: PC Speaker as /class/input/input6
[   12.656887] ISDN subsystem Rev: 
1.1.2.3/1.1.2.3/1.1.2.2/1.1.2.3/1.1.2.2/1.1.2.2 loaded
[   12.725594] pnp: the driver 'parport_pc' has been registered
[   12.725594] parport_pc 00:0b: reported by Plug and Play ACPI
[   12.725594] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE,EPP]
[   12.740129] HiSax: Linux Driver for passive ISDN cards
[   12.740129] HiSax: Version 3.5 (module)
[   12.740129] HiSax: Layer1 Revision 2.46.2.5
[   12.740129] HiSax: Layer2 Revision 2.30.2.4
[   12.740129] HiSax: TeiMgr Revision 2.20.2.3
[   12.740129] HiSax: Layer3 Revision 2.22.2.3
[   12.740129] HiSax: LinkLayer Revision 2.59.2.4
[   12.772128] hisax_isac: ISAC-S/ISAC-SX ISDN driver v0.1.0
[   12.822139] parport_pc 00:0b: driver attached
[   12.835092] hisax_fcpcipnp: Fritz!Card PCI/PCIv2/PnP ISDN driver v0.0.1
[   12.835092] HiSax: Card 1 Protocol EDSS1 Id=fcpcipnp0 (0)
[   12.835092] HiSax: DSS1 Rev. 2.32.2.3
[   12.835092] HiSax: 2 channels added
[   12.835092] HiSax: MAX_WAITING_CALLS added
[   12.835092] ACPI: PCI Interrupt :05:02.0[A] -> GSI 23 (level, low) -> 
IRQ 23
[   12.835092] hisax_fcpcipnp: found adapter Fritz!Card PCI v2 at :05:02.0
[   12.867092] pnp: the driver 'fcpnp' has been registered
[   13.059988] ACPI: PCI Interrupt :00:1b.0[A] -> GSI 22 (level, low) -> 
IRQ 22
[   13.060006] PCI: Setting latency timer of device :00:1b.0 to 64
[   14.376790] Adding 9767416k swap on /dev/md2.  Priority:-1 extents:1 
across:9767416k
[   14.896661] EXT3 FS on dm-0, internal journal
[   15.429352] loop: module loaded
[   15.985703] hda: No disk in drive
[   16.158397] hdb: No disk in drive
[   17.842752] kjournald starting.  Commit interval 5 seconds
[   17.886202] EXT3 FS on dm-1, internal journal
[   17.886202] EXT3-fs: mounted filesystem with ordered data mode.
[   18.030048] kjournald starting.  Commit interval 5 seconds
[   18.048275] EXT3 FS on dm-3, internal journal
[   18.048278] EXT3-fs: mounted filesystem with ordered data mode.
[   18.154804] kjournald starting.  Commit interval 5 seconds
[   18.170057] EXT3 FS on dm-2, internal journal
[   18.170057] EXT3-fs: mounted filesystem with ordered data mode.
[   18.582518] atl1 :03:00.0: eth0 link is up 100 

Bug#504549: marked as done (initramfs-tools: please add mtd/jffs2/ubifs modules to initrd when 'most' is selected)

2009-02-15 Thread Debian Bug Tracking System

Your message dated Sun, 15 Feb 2009 17:30:26 -0500
with message-id <20090215173026.44d4f...@ephemeral>
and subject line Re: initramfs-tools: please add mtd/jffs2/ubifs modules to 
initrd when
has caused the Debian Bug report #504549,
regarding initramfs-tools: please add mtd/jffs2/ubifs modules to initrd when 
'most' is selected
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
504549: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.92l
Severity: wishlist

OLPC laptops use jffs2 or ubifs for their root filesystem, along with
cafe_nand and mtd for the lower level devices.  The following patch is
necessary for building a modular kernel on the XO.  Please consider
including it!

>From 8854095ef36c80a4178bc2ea93fe80415019bc34 Mon Sep 17 00:00:00 2001
From: Andres Salomon 
Date: Tue, 14 Oct 2008 14:19:12 -0400
Subject: [PATCH] include mtd, jffs2, and ubifs modules

This adds support for mtd/jffs/ubifs when 'most' is selected.  Note
that this doesn't fix 'dep'.

Signed-off-by: Andres Salomon 
---
 debian/changelog |7 +++
 hook-functions   |7 +++
 2 files changed, 14 insertions(+), 0 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 1d73a4a..de7f8f5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+initramfs-tools (0.92l.1) unstable; urgency=high
+
+  * NMU
+  * include mtd/jffs2/ubifs modules when 'most' is selected.
+
+ -- Andres Salomon   Tue, 14 Oct 2008 14:16:50 -0400
+
 initramfs-tools (0.92l) unstable; urgency=high
 
   * Revert "initramfs-tools: Add support for linux-2.6 make deb-pkg
diff --git a/hook-functions b/hook-functions
index 53867da..1c9f303 100644
--- a/hook-functions
+++ b/hook-functions
@@ -347,6 +347,12 @@ auto_add_modules()
 	mmc)
 		copy_modules_dir kernel/drivers/mmc
 	;;
+	mtd)
+		copy_modules_dir kernel/drivers/mtd
+		for x in jffs2 ubifs; do
+			manual_add_modules "${x}"
+		done
+	;;
 	scsi)
 		copy_modules_dir kernel/drivers/scsi
 		for x in mptfc mptsas mptscsih mptspi zfcp; do
@@ -392,6 +398,7 @@ auto_add_modules()
 		auto_add_modules ieee1394
 		auto_add_modules firewire
 		auto_add_modules mmc
+		auto_add_modules mtd
 	;;
 	esac
 }
-- 
1.5.6.5

--- End Message ---
--- Begin Message ---
Hi,

Actually, this is better handled through an olpc-specific hook.  Since flash
without an FTL is rare, there's probably not much point in applying the patch.
Thanks!

--- End Message ---


Bug#504553: marked as done (initramfs-tools: include framebuffer modules when 'most' is selected)

2009-02-15 Thread Debian Bug Tracking System

Your message dated Sun, 15 Feb 2009 17:31:56 -0500
with message-id <20090215173156.7382a...@ephemeral>
and subject line Re: initramfs-tools: include framebuffer modules when 'most' is
has caused the Debian Bug report #504553,
regarding initramfs-tools: include framebuffer modules when 'most' is selected
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
504553: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504553
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.92l
Severity: wishlist

Hi,

There is currently support for modular framebuffers in initramfs-tools
(modules are loaded when the kernel is passed "video=$mod"), but those
framebuffer modules aren't normally included.  Please consider the
following patch which includes framebuffer modules.
>From c52b4d1346055c0c33c2474162585be7dde7c9dd Mon Sep 17 00:00:00 2001
From: Andres Salomon 
Date: Tue, 14 Oct 2008 15:31:24 -0400
Subject: [PATCH] include video (framebuffer, fbcon) modules

This adds support for video/fbcon when 'most' is selected.
Note that this doesn't fix 'dep'.

Signed-off-by: Andres Salomon 
---
 debian/changelog |1 +
 hook-functions   |4 
 2 files changed, 5 insertions(+), 0 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index babb190..833dcfa 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -3,6 +3,7 @@ initramfs-tools (0.92l.1) unstable; urgency=high
   * NMU
   * include mtd/jffs2/ubifs modules when 'most' is selected.
   * add support for linux-2.6's deb-pkg (via /etc/kernel).
+  * include video (framebuffer, fbcon) modules when 'most' is selected.
 
  -- Andres Salomon   Tue, 14 Oct 2008 14:16:50 -0400
 
diff --git a/hook-functions b/hook-functions
index 1c9f303..7d0ad15 100644
--- a/hook-functions
+++ b/hook-functions
@@ -353,6 +353,9 @@ auto_add_modules()
 			manual_add_modules "${x}"
 		done
 	;;
+	video)
+		copy_modules_dir kernel/drivers/video
+	;;
 	scsi)
 		copy_modules_dir kernel/drivers/scsi
 		for x in mptfc mptsas mptscsih mptspi zfcp; do
@@ -399,6 +402,7 @@ auto_add_modules()
 		auto_add_modules firewire
 		auto_add_modules mmc
 		auto_add_modules mtd
+		auto_add_modules video
 	;;
 	esac
 }
-- 
1.5.6.5

--- End Message ---
--- Begin Message ---
Hi,

At least for OLPC machines, we can include the requisite framebuffer modules
via hook.  Thus, there's not much need for this patch.  Thanks!

--- End Message ---


Bug#515533: linux-2.6.26: tulip module handles dmfe cards (again)

2009-02-15 Thread Daniel Hornung
Package: linux-image-2.6-486
Version: 2.6.26+17
Severity: important


After upgrading to linux-2.6.26 from 2.6.18, one of my two network cards 
stopped working.  Closer examination showed lots of 
"tulip_stop_rxtx() failed (CSR5 0xfc74 CSR6 0x2042202)"
messages.  It seems that bug #405203 resurfaced again, but I was unable to add 
a reply there since it's archived already.  The workaround described there 
(rmmod tulip; rmmod dmfe; modprobe dmfe) works for me.  A quick diff of the two 
kernel versions' modules.pcimap files shows that both dmfe and tulip claim 
responsibility for the same devices (again):

$ diff -y 2.6.18-6-486/modules.pcimap 2.6.26-1-486/modules.pcimap | grep 
1282
dmfe 0x1282 0x9132 0x 0xf   dmfe
 0x1282 0x9132 0x 0xf
dmfe 0x1282 0x9102 0x 0xf   dmfe
 0x1282 0x9102 0x 0xf
dmfe 0x1282 0x9100 0x 0xf   dmfe
 0x1282 0x9100 0x 0xf
dmfe 0x1282 0x9009 0x 0xf   dmfe
 0x1282 0x9009 0x 0xf
  > tulip   
 0x1282 0x9100 0x 0xf
  > tulip   
 0x1282 0x9102 0x 0xf



-- System Information:
Debian Release: 5.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-486
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6-486 depends on:
ii  linux-image-2.6.26-1-486  2.6.26-13  Linux 2.6.26 image on x86

linux-image-2.6-486 recommends no packages.

linux-image-2.6-486 suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#515533: linux-2.6.26: tulip module handles dmfe cards (again)

2009-02-15 Thread Daniel Hornung
A patch that would probably have fixed this issue on x86 systems seems to have 
been deferred because the current behaviour seemed to be necessary for 
sparc64.  At least if I interpret these mails correctly:

http://lkml.org/lkml/2008/4/4/86
http://lkml.org/lkml/2008/4/4/292


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