[RFC] Updating boot loaders in lenny and squeeze

[Ben Hutchings]

Stephen Powell recently reminded the kernel team that LILO is not
automatically updated on installation of a new kernel version in lenny.
In fact there is a general problem that there are several different ways
a boot loader may be updated automatically and currently no guarantee
that this does happen whenever it should.

There are two major cases where a boot loader should be updated
automatically:

1. Where the boot loader relies on block lists rather than reading the
filesystem, these block lists need to be updated whenever a kernel image
or an initramfs is updated or removed.

2. Where the boot loader allows selection between arbitrarily many
installed versions, the configuration should be updated whenever a
kernel package is newly installed or removed.

There are several ways such updates may be triggered:

A. Packages built with older versions of kernel-package, including the
official kernel packages in etch, run a platform-specific default boot
loader if it is installed and if it falls into case 1 above.

B. The maintainer scripts of kernel packages invoke hook scripts
installed in appropriate subdirectories under /etc/kernel/.

C. The maintainer scripts of kernel packages invoke hook commands
specified in /etc/kernel-img.conf.

D. "update-initramfs -u" will run certain boot loader update programs if
installed.

In lenny, route A was effectively disabled in official kernel packages.
However, no boot loader uses route B and debian-installer enables route
C only for GRUB (as far as I know).  Disabling route A in lenny was
clearly premature and I intend to restore it in a stable update.

However, given that route B is present in both lenny and squeeze (and
even in etch, I think) there is no good reason for packages not to rely
on it now.  (Well, except lack of documentation.)  All boot loader
packages that fall into case 1 or 2 should be installing hook scripts,
but currently only extlinux does.  I intend to remove the vestigial code
for route A, and file bugs on all boot loaders in case 1 or 2 that do
not use route B.

In case 1, the boot loader should also be called by update-initramfs
when it is called outside of kernel package installation and removal.
This is normally covered by route D, but this seems a little fragile.  I
would prefer to replace this with a hook system (as already exists for
building the initramfs itself), but I'm not that involved in
initramfs-tools development.

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#586386: linux-2.6: Please enable CONFIG_SND_PCM_XRUN_DEBUG

[Frédéric Brière]

Source: linux-2.6
Severity: wishlist

While CONFIG_SND_PCM_XRUN_DEBUG is mostly used for debugging purposes,
it can also affect the behavior of snd_pcm_update_hw_ptr0() since commit
c87d973.  (See XRUN_DEBUG_JIFFIESCHECK in sound/core/pcm_lib.c.)

This has been used before to work around bugs in intel8x0[1] and
cmipci[2], which have now been (mostly) fixed.  However, my own sound
card will still not play correctly without this hack[3].  It would be
nice not to have to recompile the kernel just to enable this option.

Note that CONFIG_SND_PCM_XRUN_DEBUG itself only creates a procfile; no
other effects will be felt until specific values are written to that
procfile.  It can thus be safely enabled, and will only bloat up the
kernel a little bit.  (Then, people like me who need this hack can
manually write XRUN_DEBUG_JIFFIESCHECK to the procfile.)


[1] 
[2] 
[3] 


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.34 (SMP w/1 CPU core)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
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/20100619020307.25818.66592.report...@toroia.fbriere.dyndns.org

Bug#586363: initramfs-tools: initramfs for the wrong kernel is updated

[maximilian attems]

On Fri, Jun 18, 2010 at 09:55:12PM +0200, Michal Suchanek wrote:
> Package: initramfs-tools
> Version: 0.94.4~bpo50+1
> Severity: normal
> 
> 
> Note that the initramfs is updated for a non-running kernel on package
> removal.
> 
> The following packages will be REMOVED:
>   plymouth plymouth-themes-solar{a} 
> 0 packages upgraded, 0 newly installed, 2 to remove and 4 not upgraded.
> Need to get 0B of archives. After unpacking 1307kB will be freed.
> Do you want to continue? [Y/n/?] 
> Writing extended state information... Done
> (Reading database ... 266342 files and directories currently installed.)
> Removing plymouth-themes-solar ...
> Removing plymouth ...
> Processing triggers for initramfs-tools ...
> update-initramfs: Generating /boot/initrd.img-2.6.34-rc4-amd64
> Processing triggers for man-db ...
> Reading package lists... Done 
> Building dependency tree   
> Reading state information... Done
> Reading extended state information... Done
> Initializing package states... Done   
> Writing extended state information... Done
> 

rc linux images are special, people having them are expected
to handle their initramfs.

i don't see the point of introducing special sorting code that
would discriminate those rcs.




-- 
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/2010061907.gq9...@baikonur.stro.at

Bug#586383: linux-image-2.6.32-bpo.5-amd64: Atheros AR242x wireless card relatively minor issues with Linux kernel 2.6.32 in Lenny (ath5k driver

[Deniz Akcal]

Package: linux-2.6
Version: 2.6.32-15~bpo50+1
Followup-For: Bug #586383

I just wanted to add that now "Connection 
Information" says that ath5k is running at 5MB/s. I don't think there is 
a problem here. The only issues are the minor blue/orange switching and 
the feature to disable the wireless using hardware. I forgot to mention 
that my laptop is an HP G50-113CA. (I think only the G50 part is 
important but I'm including the full name anyways)

-- Package-specific info:
** Version:
Linux version 2.6.32-bpo.5-amd64 (Debian 2.6.32-15~bpo50+1) 
(norb...@tretkowski.de) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #1 SMP Fri Jun 
11 08:42:31 UTC 2010

** Command line:
root=UUID=665667a7-c159-48fd-9938-963cf156cac1 ro quiet

** Not tainted

** Kernel log:
[   44.083008] wacom: v1.52:USB Wacom tablet driver
[   50.581775] Netfilter messages via NETLINK v0.30.
[   52.504156] ecryptfs_parse_options: eCryptfs: unrecognized option [rw]
[   52.504168] ecryptfs_parse_options: eCryptfs: unrecognized option 
[user=deniz]
[   52.699475] padlock: VIA PadLock not detected.
[   71.270092] CPUFREQ: Per core ondemand sysfs interface is deprecated - 
up_threshold
[   71.271156] CPUFREQ: Per core ondemand sysfs interface is deprecated - 
ignore_nice_load
[   72.518201] CPU0 attaching NULL sched-domain.
[   72.518214] CPU1 attaching NULL sched-domain.
[   72.552158] CPU0 attaching sched-domain:
[   72.552165]  domain 0: span 0-1 level MC
[   72.552171]   groups: 0 1
[   72.552183] CPU1 attaching sched-domain:
[   72.552187]  domain 0: span 0-1 level MC
[   72.552192]   groups: 1 0
[   73.205611] wlan0: direct probe to AP 00:13:46:a8:ad:b0 (try 1)
[   73.205636] wlan0: deauthenticating from 00:13:46:a8:ad:b0 by local choice 
(reason=3)
[   73.205701] wlan0: direct probe to AP 00:13:46:a8:ad:b0 (try 1)
[   73.207964] wlan0: direct probe responded
[   73.207967] wlan0: authenticate with AP 00:13:46:a8:ad:b0 (try 1)
[   73.217132] wlan0: authenticated
[   73.217157] wlan0: associate with AP 00:13:46:a8:ad:b0 (try 1)
[   73.235992] wlan0: RX AssocResp from 00:13:46:a8:ad:b0 (capab=0x431 status=0 
aid=1)
[   73.235995] wlan0: associated
[   73.237030] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   87.220528] wlan0: no IPv6 routers present
[  163.932068] No probe response from AP 00:13:46:a8:ad:b0 after 500ms, 
disconnecting.
[  172.160057] wlan0: direct probe to AP 00:13:46:a8:ad:b0 (try 1)
[  172.165244] wlan0: direct probe responded
[  172.165249] wlan0: authenticate with AP 00:13:46:a8:ad:b0 (try 1)
[  172.184013] wlan0: authenticated
[  172.184038] wlan0: associate with AP 00:13:46:a8:ad:b0 (try 1)
[  172.205891] wlan0: RX AssocResp from 00:13:46:a8:ad:b0 (capab=0x431 status=0 
aid=1)
[  172.205895] wlan0: associated
[ 1393.316054] No probe response from AP 00:13:46:a8:ad:b0 after 500ms, 
disconnecting.
[ 1398.320776] wlan0: direct probe to AP 00:13:46:a8:ad:b0 (try 1)
[ 1398.327912] wlan0: direct probe responded
[ 1398.327916] wlan0: authenticate with AP 00:13:46:a8:ad:b0 (try 1)
[ 1398.341881] wlan0: authenticated
[ 1398.341920] wlan0: associate with AP 00:13:46:a8:ad:b0 (try 1)
[ 1398.351844] wlan0: RX AssocResp from 00:13:46:a8:ad:b0 (capab=0x431 status=0 
aid=1)
[ 1398.351851] wlan0: associated
[ 1404.316075] No probe response from AP 00:13:46:a8:ad:b0 after 500ms, 
disconnecting.
[ 1405.508823] wlan0: direct probe to AP 00:13:46:a8:ad:b0 (try 1)
[ 1405.708063] wlan0: direct probe to AP 00:13:46:a8:ad:b0 (try 2)
[ 1405.908071] wlan0: direct probe to AP 00:13:46:a8:ad:b0 (try 3)
[ 1406.108037] wlan0: direct probe to AP 00:13:46:a8:ad:b0 timed out
[ 1747.239594] wlan0: direct probe to AP 00:13:46:a8:ad:b0 (try 1)
[ 1747.436050] wlan0: direct probe to AP 00:13:46:a8:ad:b0 (try 2)
[ 1747.636053] wlan0: direct probe to AP 00:13:46:a8:ad:b0 (try 3)
[ 1747.836046] wlan0: direct probe to AP 00:13:46:a8:ad:b0 timed out
[ 1753.951651] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1754.182628] wlan0: direct probe to AP 00:13:46:a8:ad:b0 (try 1)
[ 1754.189211] wlan0: direct probe responded
[ 1754.189216] wlan0: authenticate with AP 00:13:46:a8:ad:b0 (try 1)
[ 1754.207228] wlan0: authenticated
[ 1754.207262] wlan0: associate with AP 00:13:46:a8:ad:b0 (try 1)
[ 1754.211213] wlan0: RX AssocResp from 00:13:46:a8:ad:b0 (capab=0x431 status=0 
aid=1)
[ 1754.211219] wlan0: associated
[ 1754.212997] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 1754.764047] wlan0: deauthenticating from 00:13:46:a8:ad:b0 by local choice 
(reason=3)
[ 1755.780441] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1755.843546] r8169: eth0: link down
[ 1755.844197] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1767.692501] wlan0: direct probe to AP 00:13:46:a8:ad:b0 (try 1)
[ 1767.692556] wlan0: deauthenticating from 00:13:46:a8:ad:b0 by local choice 
(reason=3)
[ 1767.692589] wlan0: direct probe to AP 00:13:46:a8:ad:b0 (try 1)
[ 1767.694939] wlan0: direct probe responded
[ 1767.694942] wlan0: authenticate with AP 00:13:46:a8:ad:b0 (try 1)
[ 1767.72225

Bug#586383: linux-image-2.6.32-bpo.5-amd64: Atheros AR242x wireless card relatively minor issues with Linux kernel 2.6.32 in Lenny (ath5k driver)

[Deniz Akcal]

Package: linux-2.6
Version: 2.6.32-15~bpo50+1
Severity: normal


( lspci gives: 02:00.0 Ethernet controller: Atheros Communications Inc. 
AR242x 802.11abg Wireless PCI Express Adapter (rev 01) )
I am using the ath5k driver and when I upgraded from 2.6.30 to 2.6.32 in 
Lenny, I got a little excited because I saw that the light was blue like 
when I had first 
purchased it when I had Windows Vista pre-installed on this laptop. For 
a long time I had it at orange (although it worked). (Orange means it's 
disabled) Sometimes, it 
alternates between blue and orange either at long or extremely short 
intervals (the occurences seem very random). I don't have Windows 
installed to double check but it 
seems rather impossible to disable it (not that I want to but I just 
wanted to add more to the bug report since it technically is a feature). 
The more important part (for 
me) of this bug report is that the light switches colour occasionally 
which could at times being distracting but as I type this, the light 
hasn't flickered for a 
pretty long time but I'm pretty confident that it will again because the 
intervals vary. Although the performance is not affected, "Connection 
Information" on the Gnome 
panel lists  it as running as 1MB/s but I don't "feel" any slowdowns.

If more information is needed, just email me.

-- Package-specific info:
** Version:
Linux version 2.6.32-bpo.5-amd64 (Debian 2.6.32-15~bpo50+1) 
(norb...@tretkowski.de) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #1 SMP Fri Jun 
11 08:42:31 UTC 2010

** Command line:
root=UUID=665667a7-c159-48fd-9938-963cf156cac1 ro quiet

** Not tainted

** Kernel log:
[   44.083002] usbcore: registered new interface driver wacom
[   44.083008] wacom: v1.52:USB Wacom tablet driver
[   50.581775] Netfilter messages via NETLINK v0.30.
[   52.504156] ecryptfs_parse_options: eCryptfs: unrecognized option [rw]
[   52.504168] ecryptfs_parse_options: eCryptfs: unrecognized option 
[user=deniz]
[   52.699475] padlock: VIA PadLock not detected.
[   71.270092] CPUFREQ: Per core ondemand sysfs interface is deprecated - 
up_threshold
[   71.271156] CPUFREQ: Per core ondemand sysfs interface is deprecated - 
ignore_nice_load
[   72.518201] CPU0 attaching NULL sched-domain.
[   72.518214] CPU1 attaching NULL sched-domain.
[   72.552158] CPU0 attaching sched-domain:
[   72.552165]  domain 0: span 0-1 level MC
[   72.552171]   groups: 0 1
[   72.552183] CPU1 attaching sched-domain:
[   72.552187]  domain 0: span 0-1 level MC
[   72.552192]   groups: 1 0
[   73.205611] wlan0: direct probe to AP 00:13:46:a8:ad:b0 (try 1)
[   73.205636] wlan0: deauthenticating from 00:13:46:a8:ad:b0 by local choice 
(reason=3)
[   73.205701] wlan0: direct probe to AP 00:13:46:a8:ad:b0 (try 1)
[   73.207964] wlan0: direct probe responded
[   73.207967] wlan0: authenticate with AP 00:13:46:a8:ad:b0 (try 1)
[   73.217132] wlan0: authenticated
[   73.217157] wlan0: associate with AP 00:13:46:a8:ad:b0 (try 1)
[   73.235992] wlan0: RX AssocResp from 00:13:46:a8:ad:b0 (capab=0x431 status=0 
aid=1)
[   73.235995] wlan0: associated
[   73.237030] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   87.220528] wlan0: no IPv6 routers present
[  163.932068] No probe response from AP 00:13:46:a8:ad:b0 after 500ms, 
disconnecting.
[  172.160057] wlan0: direct probe to AP 00:13:46:a8:ad:b0 (try 1)
[  172.165244] wlan0: direct probe responded
[  172.165249] wlan0: authenticate with AP 00:13:46:a8:ad:b0 (try 1)
[  172.184013] wlan0: authenticated
[  172.184038] wlan0: associate with AP 00:13:46:a8:ad:b0 (try 1)
[  172.205891] wlan0: RX AssocResp from 00:13:46:a8:ad:b0 (capab=0x431 status=0 
aid=1)
[  172.205895] wlan0: associated
[ 1393.316054] No probe response from AP 00:13:46:a8:ad:b0 after 500ms, 
disconnecting.
[ 1398.320776] wlan0: direct probe to AP 00:13:46:a8:ad:b0 (try 1)
[ 1398.327912] wlan0: direct probe responded
[ 1398.327916] wlan0: authenticate with AP 00:13:46:a8:ad:b0 (try 1)
[ 1398.341881] wlan0: authenticated
[ 1398.341920] wlan0: associate with AP 00:13:46:a8:ad:b0 (try 1)
[ 1398.351844] wlan0: RX AssocResp from 00:13:46:a8:ad:b0 (capab=0x431 status=0 
aid=1)
[ 1398.351851] wlan0: associated
[ 1404.316075] No probe response from AP 00:13:46:a8:ad:b0 after 500ms, 
disconnecting.
[ 1405.508823] wlan0: direct probe to AP 00:13:46:a8:ad:b0 (try 1)
[ 1405.708063] wlan0: direct probe to AP 00:13:46:a8:ad:b0 (try 2)
[ 1405.908071] wlan0: direct probe to AP 00:13:46:a8:ad:b0 (try 3)
[ 1406.108037] wlan0: direct probe to AP 00:13:46:a8:ad:b0 timed out
[ 1747.239594] wlan0: direct probe to AP 00:13:46:a8:ad:b0 (try 1)
[ 1747.436050] wlan0: direct probe to AP 00:13:46:a8:ad:b0 (try 2)
[ 1747.636053] wlan0: direct probe to AP 00:13:46:a8:ad:b0 (try 3)
[ 1747.836046] wlan0: direct probe to AP 00:13:46:a8:ad:b0 timed out
[ 1753.951651] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1754.182628] wlan0: direct probe to AP 00:13:46:a8:ad:b0 (try 1)
[ 1754.189211] wlan0: direct probe responded
[ 1754.189216] wl

Bug#586381: initramfs-tools: lsinitramfs fails with non-gzipped initramfs images

[Christoph Anton Mitterer]

Package: initramfs-tools
Version: 0.97
Severity: normal


Hi.

lsinitramgs fails with non-gzipped (well at least with lzma-ed)
initramfs images:
gzip: /boot/initrd.img-2.6.33: not in gzip format
cpio: premature end of archive

Cheers,
Chris.



-- 
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/20100619002605.10142.24747.report...@heisenberg.scientia.net

Call for Testing: initramfs-tools 0.97

[Michael Prokop]

Hi,

we - the initramfs-tools maintainers in Debian - want to provide a
solid initramfs-tools version for squeeze. The new release 0.97 is
expected to fix many longstanding problems. It would be great if we
could receive feedback from testers.

The new release is available from Debian/unstable and is expected to
install without problems in at least lenny, squeeze and sid:

  
http://cdn.debian.net/debian/pool/main/i/initramfs-tools/initramfs-tools_0.97_all.deb
  SHA256:56eb56d472d0dd24c8f2fd030222586e258ec882b716f02d114865cef9c19639

No matter how your partition layout looks like (rootfs on lvm,
crypto, sw-raid,...), if you're booting on physical hardware or a
virtualized system (Xen, openvz, kvm,...) - please give it a shot
and report any possible problems.

thanks && regards,
-mika-


signature.asc
Description: Digital signature

Bug#505609: loader varialbe in kernel maintainer scripts

[Stephen Powell]

On Fri, 18 Jun 2010 11:51:11 -0400 (EDT), maximilian attems wrote:
> On Fri, Jun 18, 2010 at 10:55:35AM -0400, Stephen Powell wrote:
>> As for "update-initramfs -u", it *will* invoke lilo if lilo is installed
>> and "do_bootloader = yes" is specified in /etc/kernel-img.conf, which I
>> highly recommend. 
> 
> this fall back will be gone as soon as squeeze is out.
> so you'd really need to gear up.

That is interesting.  Suppose that the user issues an

   aptitude update
   aptitude full-upgrade

sequence.  And suppose something other than the kernel gets updated that
requires that the initial RAM file system be updated.  Somehow, aptitude
knows to run "update-initramfs -u".  But if "update-initramfs -u" does
not invoke lilo, and the kernel is not updated, what will cause lilo to
get run?  The kernel hook scripts won't be run because the kernel itself
was not updated.  The same principle applies to zipl on the s390 platform,
which is the *only* supported boot loader on this platform, by the way.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-



-- 
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/1199263906.109692.1276893897406.javamail.r...@md01.wow.synacor.com

Bug#586363: initramfs-tools: initramfs for the wrong kernel is updated

[Michal Suchanek]

Package: initramfs-tools
Version: 0.94.4~bpo50+1
Severity: normal


Note that the initramfs is updated for a non-running kernel on package
removal.

The following packages will be REMOVED:
  plymouth plymouth-themes-solar{a} 
0 packages upgraded, 0 newly installed, 2 to remove and 4 not upgraded.
Need to get 0B of archives. After unpacking 1307kB will be freed.
Do you want to continue? [Y/n/?] 
Writing extended state information... Done
(Reading database ... 266342 files and directories currently installed.)
Removing plymouth-themes-solar ...
Removing plymouth ...
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.34-rc4-amd64
Processing triggers for man-db ...
Reading package lists... Done 
Building dependency tree   
Reading state information... Done
Reading extended state information... Done
Initializing package states... Done   
Writing extended state information... Done


-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-2.6.34-1-amd64 
root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro quiet

-- /proc/filesystems
ext3
fuseblk
reiserfs

-- lsmod
Module  Size  Used by
tun12166  10 
binfmt_misc 6558  1 
openafs   602666  2 
vboxnetadp  4241  0 
oss_usb   118853  0 
oss_hdaudio   146129  0 
osscore   550925  2 oss_usb,oss_hdaudio
ib_iser23647  0 
rdma_cm21170  1 ib_iser
ib_cm  26008  1 rdma_cm
iw_cm   6465  1 rdma_cm
ib_sa  16082  2 rdma_cm,ib_cm
ib_mad 29813  2 ib_cm,ib_sa
ib_core41391  6 ib_iser,rdma_cm,ib_cm,iw_cm,ib_sa,ib_mad
ib_addr 4038  1 rdma_cm
iscsi_tcp   8153  0 
libiscsi_tcp   11127  1 iscsi_tcp
libiscsi   31537  3 ib_iser,iscsi_tcp,libiscsi_tcp
scsi_transport_iscsi25151  4 ib_iser,iscsi_tcp,libiscsi
bridge 53994  0 
stp 1464  1 bridge
reiserfs  195202  1 
fuse   50697  1 
coretemp4235  0 
hwmon_vid   1804  0 
radeonfb   50840  0 
fb_ddc  1429  1 radeonfb
vboxnetflt 12118  0 
vboxdrv  1721774  2 vboxnetadp,vboxnetflt
loop   12330  0 
firewire_sbp2  11407  0 
asus_atk01109268  0 
processor  29010  0 
led_class   2203  0 
wacom  19865  0 
tpm_tis 7349  0 
joydev  8920  0 
evdev   7426  9 
i2c_i8017822  0 
tpm 9843  1 tpm_tis
tpm_bios4629  1 tpm
parport_pc 18869  0 
rng_core3166  0 
psmouse45509  0 
parport25598  1 parport_pc
serio_raw   3726  0 
ext3  106594  4 
jbd37179  1 ext3
mbcache 5152  1 ext3
usbhid 33354  0 
hid63831  1 usbhid
radeon603657  2 
ttm39481  1 radeon
drm_kms_helper 20107  1 radeon
drm   144377  4 radeon,ttm,drm_kms_helper
i2c_algo_bit4297  2 radeonfb,radeon
i2c_core   16076  7 
radeonfb,fb_ddc,i2c_i801,radeon,drm_kms_helper,drm,i2c_algo_bit
sg 19141  3 
sr_mod 12711  0 
cdrom  29769  1 sr_mod
sd_mod 30469  7 
crc_t10dif  1284  1 sd_mod
ata_generic 2895  0 
ata_piix   20652  8 
ehci_hcd   30813  0 
firewire_ohci  18688  0 
thermal12046  0 
uhci_hcd   18410  0 
libata133830  2 ata_generic,ata_piix
button  4706  0 
thermal_sys12036  2 processor,thermal
firewire_core  38607  2 firewire_sbp2,firewire_ohci
crc_itu_t   1315  1 firewire_core
usbcore   125665  6 oss_usb,wacom,usbhid,ehci_hcd,uhci_hcd
scsi_mod  125191  9 
ib_iser,iscsi_tcp,libiscsi,scsi_transport_iscsi,firewire_sbp2,sg,sr_mod,sd_mod,libata
atl1   25914  0 
mii 3250  1 atl1
nls_base6369  1 usbcore

-- /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = no
postinst_hook = update-grub
postrm_hook   = update-grub

-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
KEYMAP=n
COMPRESS=gzip
BOOT=local
DEVICE=eth0
NFSROOT=auto


-- System Information:
Debian Release: 5.0.4
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'testing'), (300, 'unstable'), (295, 
'experimental'), (290, 'stable-i386'), (280, 'testing-i386'), (270, 
'unstable-i386'), (150, 'exper

Bug#505609: loader varialbe in kernel maintainer scripts

[maximilian attems]

On Fri, Jun 18, 2010 at 10:55:35AM -0400, Stephen Powell wrote:
> 
> So far, Ben has only agreed to reinstate the historic function of
> 
>do_bootloader = yes
> 
> in /etc/kernel-img.conf for Lenny kernel maintainer scripts.
> It hasn't actually happened yet, but
> he has agreed to restore its former function in Lenny as it was in Etch
> and previous releases.  I am trying to persuade him to restore its
> function in Squeeze too.  Whether or not I am successful remains to be
> seen. 

it is gone, get over it.

> In the mean time, for lilo users of Squeeze/Sid who use *only* official
> stock Debian kernels, I recommend that they use the hook script described
> in an earlier post to this bug log in conjunction with other appropriate
> settings in /etc/kernel-img.conf.

it is about time that lilo gets an hook script.
even extlinux has one although that one seems to trigger funny bug
reports, but we are used to forward such bugs.
 
> For lilo users of Squeeze/Sid who use
> custom kernels created by make-kpkg,

k-p is deprecated, use upstream way: make deb-pkg
needs no strange debian scripting and is maintained in linux-2.6 itself.

> As for "update-initramfs -u", it *will* invoke lilo if lilo is installed
> and "do_bootloader = yes" is specified in /etc/kernel-img.conf, which I
> highly recommend. 

this fall back will be gone as soon as squeeze is out.
so you'd really need to gear up.

>There are types of upgrades which do not affect the
> kernel itself but which do require that the initial RAM file system
> be re-built.  And for lilo users, it is essential that lilo be run after
> any changes are made to the initial RAM file system.  "update-initramfs -c"
> and "update-initramfs -d", however, will *not* invoke lilo, even if
> "do_bootloader = yes" is specified in /etc/kernel-img.conf.

yes in those case either you have valid hooks or an intelligent
postinst.

thanks

-- 
maks



-- 
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/20100618155110.gp9...@baikonur.stro.at

Bug#505609: loader varialbe in kernel maintainer scripts

[Stephen Powell]

On Fri, 18 Jun 2010 04:25:38 -0400 (EDT), Joachim Wiedorn wrote:
> Ben Hutchings  wrote on 2010-06-18 02:02:
>> On Thu, 2010-06-17 at 20:37 -0400, Stephen Powell wrote:
>>> And how would one go about setting this "loader" variable?
>>> The "loader" variable is not documented in the man page for
>>> /etc/kernel-img.conf in Lenny, which appears to be the closest thing
>>> there is to documentation for the variables supported by official
>>> Debian stock kernel images.  Nevertheless, at your suggestion, I tried
>>> putting
>>> 
>>>loader = lilo
>>> 
>>> in /etc/kernel-img.conf.  ("do_bootloader = yes" was also set.)  Then I
>>> issued
>>> 
>>>dpkg-reconfigure linux-image-2.6.26-2-686
>>> 
>>> There was no evidence from the output that lilo was run.
>>> [...]
>> 
>> I'm sorry, you're right.  Most of the other variables at the top of the
>> postinst script can be overridden by /etc/kernel-img.conf, but not this
>> one.  Given that, I think you are right that the 'historical' bootloader
>> setting should be restored in an update to lenny.
> 
> Now I am a little confused. How is the recommended procedure for using the
> LILO bootloader within squeeze/sid? 
> How I understand the normal installation of lilo package have the result,
> that lilo doesn't be started after an kernel update (and also after update
> of initramfs-tools?). 
> What must I config on my squeeze machine that lilo bootloader will be
> automatically updated after kernel update?

So far, Ben has only agreed to reinstate the historic function of

   do_bootloader = yes

in /etc/kernel-img.conf for Lenny kernel maintainer scripts.
It hasn't actually happened yet, but
he has agreed to restore its former function in Lenny as it was in Etch
and previous releases.  I am trying to persuade him to restore its
function in Squeeze too.  Whether or not I am successful remains to be
seen.  In the mean time, for lilo users of Squeeze/Sid who use *only* official
stock Debian kernels, I recommend that they use the hook script described
in an earlier post to this bug log in conjunction with other appropriate
settings in /etc/kernel-img.conf.

For lilo users of Squeeze/Sid who use
custom kernels created by make-kpkg, I recommend that they use the hook
scripts provided on my unofficial kernel building web page,
http://www.wowway.com/~zlinuxman/Kernel.htm, under "Step 10: Customize
the Kernel Installation Environment".  I must add that this recommendation
is my own and not official Debian advice.  I have never used the
upstream-provided "make deb-pkg" way of building a custom kernel; so
I don't have any hook scripts pre-made for that purpose.  There doesn't
seem to be a "one size fits all" solution at this point.  If Ben agrees
to reinstate the historic function of "do_bootloader = yes" for Squeeze,
then there will be a "one size fits all" solution for lilo users, at least
as it pertains to stock kernels.  Users of custom kernels are on their own.
They need to figure out what hook scripts they need and how to customize
and configure them.  And if they don't do it right, you may be sure that
they will blame lilo!  (That's one of the reasons why I think it would
be a good idea for lilo to implement a "check sum" method of figuring
out if something changed in the kernel image or initial RAM file system
image without lilo being re-run.  But I digress.)

As for "update-initramfs -u", it *will* invoke lilo if lilo is installed
and "do_bootloader = yes" is specified in /etc/kernel-img.conf, which I
highly recommend.  There are types of upgrades which do not affect the
kernel itself but which do require that the initial RAM file system
be re-built.  And for lilo users, it is essential that lilo be run after
any changes are made to the initial RAM file system.  "update-initramfs -c"
and "update-initramfs -d", however, will *not* invoke lilo, even if
"do_bootloader = yes" is specified in /etc/kernel-img.conf.

HTH

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-



-- 
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/531218163.101000.1276872935122.javamail.r...@md01.wow.synacor.com

Bug#574555: BUG: scheduling while atomic: irq/11-b43/2018/0x00000101

[Arne Nordmark]

My problem seems related to those in Ubuntu report #55 
. If I 
unload the 3c59x module, I can no longer reproduce this problem, and 
wireless is stable. With the 3c59x module loaded, b43 wireless is 
essentially unusable, since the machine will reliably lock up.


Arne



--
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/4c1b8554.8090...@mech.kth.se

Processed: reopening 337176

[Debian Bug Tracking System]

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

> reopen 337176
Bug #337176 {Done: Guido Günther } [initramfs-tools] 
troubles due to 32-bit chroot on amd64
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
>
End of message, stopping processing here.

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

Processed: unmerging 337176

[Debian Bug Tracking System]

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

> unmerge 337176
Bug#337176: troubles due to 32-bit chroot on amd64
Bug#581377: initramfs-tools: Multipath does not load correctly at boot time
Disconnected #337176 from all other report(s).

>
End of message, stopping processing here.

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

initramfs-tools 0.97 release

[Michael Prokop]

Hi,

we just uploaded and released initramfs-tools 0.97 to Debian/unstable.

Most notably are bugfixes for mdstat parsing, hooks can abort build
of initramfs, bash-completion for update-initramfs, some code
cleanups and further bugfixes. Continous work for easier bug
reporting together with a lsinitramfs script.

We've a new document titled "Maintainer documentation for
initramfs-tools" in our docs, which documents our workflow, how to
contribute patches, test, - it's available online at:

  
http://git.debian.org/?p=kernel/initramfs-tools.git;a=blob_plain;f=docs/maintainer-notes.html;hb=HEAD

Thanks to Colin Watson for merging in Ubuntu previous 0.96.1 and
providing patches.

regards,
-mika-

shortlog has the details:

Colin Watson (1):
  initramfs-tools: work around 'find -printf %Y' bug

Ferenc Wagner (1):
  scripts/nfs: cleanup retry logic

Martin Michlmayr (2):
  Produce an error when root cannot be determined with MODULES=dep
  hook-functions/init/scripts/local: add support for ubifs.

Michael Prokop (25):
  Fix bug number in changelog (#584520 -> #549680) for upload of 0.96.1.
  hook-functions/mkinitramfs/update-initramfs: consequently output error 
messages to stderr
  init: display warning message if devtmpfs could not be mounted.
  code cleanup: drop trailing whitespaces.
  code cleanup: consequently replace spaces in indentions with tabs to 
unify coding stile
  code cleanup: consequently use "W:" for warnings.
  add bash-completion for update-initramfs
  hook-functions: replace awk calls with sed in dep_add_modules()
  debian/script: append /proc/mdstat (iff present) to bugreports
  scripts/functions: allow hooks to abort build
  hook-functions: do not install ubi module by default via 
auto_add_modules()
  initial version of maintainer-notes.html
  maintainer-notes.html: fix git-dch commandline.
  move maintainer-notes.html to docs/ and install as 
/usr/share/doc/initramfs-tools/maintainer-notes.html
  maintainer-notes.html: extend contribution section, rewrap + fix 
git-dch/git-buildpackage commandline
  lsinitramfs: be more defensive against cmdline options
  scripts/functions: fix usage of test for script execution
  scripts/functions: fix another sh -n usage and fix typo
  hook-functions: install virtio_pci module if /sys/bus/virtio is present 
and using modules=dep
  docs/maintainer-notes: valid XHTML 1.0 Strict document, add section 
"Build snapshot version", add license note, minor formating cleanups + 
improvements
  slightly improve manpage lsinitramfs.8
  Releasing version 0.97.

maximilian attems (16):
  script: Add update-initramfs.conf to bug report
  update-initramfs: Fix another unbound variable
  get_fstype: reference blkid in comment
  pre_mountroot(): reduce timeout to 30 seconds
  scripts/functions: On panic change to tty1 if chvt around
  mkinitramfs: No point in hardcoding busybox path
  Add lsinitramfs to initramfs-tools
  lsinitramfs: set errexit and nounset
  lsinitramfs: allow to pass several filenames
  mkinitramfs: check syntax of boot and hook scripts
  scripts/functions: beautify a bit reduce_satisfied()
  maintainer doc: use git commands without the dash
  nfsmount: more small cleanups
  lsinitramfs: use getopt for -l option
  mkinitramfs, lsinitramfs: Better error message for non-GNU getopt


signature.asc
Description: Digital signature

Bug#575924: linux-image-2.6.32-4-amd64: fuse module oops on boot

[Denis Laxalde]

Hi,

Le lundi 12 avril 2010 à 01:18 +0100, Ben Hutchings a écrit :
> On Sun, 2010-04-11 at 18:23 -0400, Denis Laxalde wrote:
> > forwarded 575924 https://bugzilla.kernel.org/show_bug.cgi?id=14347
> > thanks
> > 
> > On Sun, 11 Apr 2010 16:05:57 +0100, Ben Hutchings wrote:
> > > On Sat, 2010-04-10 at 23:05 -0400, Denis Laxalde wrote:
> > > > Hi,
> > > > 
> > > > On Sun, 11 Apr 2010 00:28:24 +0100, Ben Hutchings wrote:
> > > > > The more serious error messages suggest memory  corruption.  Have
> > > > > you tested the RAM with memtest86+ yet?
> > > > 
> > > > Yes, I've just run a pretty long test with memtest86+ and there was
> > > > no error reported.
> > > 
> > > OK, so we can be fairly sure this is a kernel bug.  Please report this
> > > at .  It is hard to know where the bug
> > > may be, but try submitting it under product 'Memory Management',
> > > component 'Slab Allocator'.  Let us know the bug number so we can
> > > track it.
> > 
> > The above bug report looks similar, so I just added comments and dmesgs
> > there.
> > Maybe the bug should be retitled ?
> 
> I'm not convinced that these are the same bug.  Let's see what the
> response is.

There was no response so far and, since boot failures still happen from
time to time (once a week or so), I may open a new bug upstream...
In fact, there are even worse than before since I cannot recover using
SysRq keys combination anymore (I just power-off the computer now).
Hence, I cannot save a relevant dmesg anymore.
Is there any way to recover messages in such situations?

Cheers,

Denis



-- 
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/20100618134435.ga2...@schloss

Processed: tagging 586330, reassign 586330 to src:grub2

[Debian Bug Tracking System]

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

> tags 586330 - squeeze
Bug #586330 [linux-2.6] linux-image-2.6.32-5-amd64 fails to configure when 
installed by me or by aptitude safe-upgrade
Ignoring request to alter tags of bug #586330 to the same tags previously set
> reassign 586330 src:grub2
Bug #586330 [linux-2.6] linux-image-2.6.32-5-amd64 fails to configure when 
installed by me or by aptitude safe-upgrade
Bug reassigned from package 'linux-2.6' to 'src:grub2'.
Bug No longer marked as found in versions 2.6.32-15.
> thanks
Stopping processing here.

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

Processed: tagging 586330

[Debian Bug Tracking System]

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

> tags 586330 - squeeze
Bug #586330 [linux-2.6] linux-image-2.6.32-5-amd64 fails to configure when 
installed by me or by aptitude safe-upgrade
Removed tag(s) squeeze.
> thanks
Stopping processing here.

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

Bug#586330: linux-image-2.6.32-5-amd64 fails to configure when installed by me or by aptitude safe-upgrade

[Abel Coto]

Package: linux-2.6
Version: 2.6.32-15
Severity: important
Tags: squeeze

r...@quantico:~# aptitude safe-upgrade

Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information... Done
Initializing package states... Done
Reading task descriptions... Done
The following partially installed packages will be configured:
  linux-image-2.6.32-5-amd64
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
Setting up linux-image-2.6.32-5-amd64 (2.6.32-15) ...
Running depmod.
Running update-initramfs.
update-initramfs: Generating /boot/initrd.img-2.6.32-5-amd64
initrd.img(/boot/initrd.img-2.6.32-5-amd64
) points to /boot/initrd.img-2.6.32-5-amd64
 (/boot/initrd.img-2.6.32-5-amd64) -- doing nothing at /var/lib/dpkg/info
/linux-image-2.6.32-5-amd64.postinst line 400.
vmlinuz(/boot/vmlinuz-2.6.32-5-amd64
) points to /boot/vmlinuz-2.6.32-5-amd64
 (/boot/vmlinuz-2.6.32-5-amd64) -- doing nothing at /var/lib/dpkg/info/linux-
image-2.6.32-5-amd64.postinst line 400.
Running update-grub.
/usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?).
User postinst hook script [update-grub] exited with value 1
dpkg: error processing linux-image-2.6.32-5-amd64 (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 linux-image-2.6.32-5-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up linux-image-2.6.32-5-amd64 (2.6.32-15) ...
Running depmod.
Running update-initramfs.
update-initramfs: Generating /boot/initrd.img-2.6.32-5-amd64
initrd.img(/boot/initrd.img-2.6.32-5-amd64
) points to /boot/initrd.img-2.6.32-5-amd64
 (/boot/initrd.img-2.6.32-5-amd64) -- doing nothing at /var/lib/dpkg/info
/linux-image-2.6.32-5-amd64.postinst line 400.
vmlinuz(/boot/vmlinuz-2.6.32-5-amd64
) points to /boot/vmlinuz-2.6.32-5-amd64
 (/boot/vmlinuz-2.6.32-5-amd64) -- doing nothing at /var/lib/dpkg/info/linux-
image-2.6.32-5-amd64.postinst line 400.
Running update-grub.
/usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?).
User postinst hook script [update-grub] exited with value 1
dpkg: error processing linux-image-2.6.32-5-amd64 (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 linux-image-2.6.32-5-amd64
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information... Done
Initializing package states... Done
Reading task descriptions... Done


r...@quantico:~# dpkg --configure -a

Setting up linux-image-2.6.32-5-amd64 (2.6.32-15) ...
Running depmod.
Running update-initramfs.
update-initramfs: Generating /boot/initrd.img-2.6.32-5-amd64
initrd.img(/boot/initrd.img-2.6.32-5-amd64
) points to /boot/initrd.img-2.6.32-5-amd64
 (/boot/initrd.img-2.6.32-5-amd64) -- doing nothing at /var/lib/dpkg/info
/linux-image-2.6.32-5-amd64.postinst line 400.
vmlinuz(/boot/vmlinuz-2.6.32-5-amd64
) points to /boot/vmlinuz-2.6.32-5-amd64
 (/boot/vmlinuz-2.6.32-5-amd64) -- doing nothing at /var/lib/dpkg/info/linux-
image-2.6.32-5-amd64.postinst line 400.
Running update-grub.
/usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?).
User postinst hook script [update-grub] exited with value 1
dpkg: error processing linux-image-2.6.32-5-amd64 (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 linux-image-2.6.32-5-amd64



-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: System manufacturer
product_name: System Product Name
product_version: System Version
chassis_vendor: Chassis Manufacture
chassis_version: Chassis Version
bios_vendor: American Megatrends Inc.
bios_version: 0505   
board_vendor: ASUSTeK Computer INC.
board_name: P5E3 PRO
board_version: Rev X.0x

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 82X38/X48 Express DRAM Controller 
[8086:29e0] (rev 01)
Subsystem: ASUSTeK Computer Inc. Device [1043:8295]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: x38_edac

00:06.0 PCI bridge [0604]: Intel Corporation 82X38/X48 Express Host-Secondary 
PCI Express Bridge [8086:29e9] (rev 01) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
  

Bug#585992: marked as done (initramfs-tools: in KVM machine modules=dep does not add virtio_pci)

[Debian Bug Tracking System]

Your message dated Fri, 18 Jun 2010 13:18:23 +
with message-id 
and subject line Bug#585992: fixed in initramfs-tools 0.97
has caused the Debian Bug report #585992,
regarding initramfs-tools: in KVM machine modules=dep does not add virtio_pci
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.)


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

  Hi,

  In a KVM machine using virtio block disk (),
using "modules=dep" does not add the required virtio_pci module in the
generated initramfs.
  A workaround is to add "virtio_pci" to /etc/initramfs-tools/modules

  Here is the trace of "bash -x mkinitramfs -o 
/boot/initrd.img-2.6.34-1-amd64.new 2.6.34-1-amd64" with modules=dep but 
without virtio_pci in 
/etc/initramfs-tools/modules 

  Regards,
Vincent
+ umask 0022
+ export PATH=/usr/bin:/sbin:/bin
+ PATH=/usr/bin:/sbin:/bin
+ keep=n
+ CONFDIR=/etc/initramfs-tools
+ verbose=n
+ export BUSYBOXDIR=/bin
+ BUSYBOXDIR=/bin
++ getopt -o c:d:ko:r:v -n mkinitramfs -- -o 
/boot/initrd.img-2.6.34-1-amd64.new 2.6.34-1-amd64
+ OPTIONS=' -o '\''/boot/initrd.img-2.6.34-1-amd64.new'\'' -- 
'\''2.6.34-1-amd64'\'''
+ '[' 0 '!=' 0 ']'
+ eval set -- ' -o '\''/boot/initrd.img-2.6.34-1-amd64.new'\'' -- 
'\''2.6.34-1-amd64'\'''
++ set -- -o /boot/initrd.img-2.6.34-1-amd64.new -- 2.6.34-1-amd64
+ true
+ case "$1" in
+ outfile=/boot/initrd.img-2.6.34-1-amd64.new
+ shift 2
+ true
+ case "$1" in
+ shift
+ break
+ . /usr/share/initramfs-tools/scripts/functions
+ . /usr/share/initramfs-tools/hook-functions
+ . /etc/initramfs-tools/initramfs.conf
++ MODULES=dep
++ BUSYBOX=y
++ KEYMAP=n
++ COMPRESS=gzip
++ BOOT=local
++ DEVICE=
++ NFSROOT=auto
+ EXTRA_CONF=
+ for i in '/usr/share/initramfs-tools/conf.d/*' '${CONFDIR}/conf.d/*'
+ '[' -e '/usr/share/initramfs-tools/conf.d/*' ']'
+ for i in '/usr/share/initramfs-tools/conf.d/*' '${CONFDIR}/conf.d/*'
+ '[' -e /etc/initramfs-tools/conf.d/resume ']'
++ grep -v '\.dpkg-.*$'
++ grep '^[[:alnum:]][[:alnum:]\._-]*$'
++ basename /etc/initramfs-tools/conf.d/resume
+ EXTRA_CONF=' resume'
+ for i in '${EXTRA_CONF}'
+ '[' -e /etc/initramfs-tools/conf.d/resume ']'
+ . /etc/initramfs-tools/conf.d/resume
++ RESUME=/dev/vda2
+ for i in '/usr/share/initramfs-tools/conf-hooks.d/*'
+ '[' -e '/usr/share/initramfs-tools/conf-hooks.d/*' ']'
+ '[' -n '' ']'
+ '[' -z /boot/initrd.img-2.6.34-1-amd64.new ']'
+ touch /boot/initrd.img-2.6.34-1-amd64.new
++ readlink -f /boot/initrd.img-2.6.34-1-amd64.new
+ outfile=/boot/initrd.img-2.6.34-1-amd64.new
+ '[' 1 -ne 1 ']'
+ version=2.6.34-1-amd64
+ check_minkver 2.6.34-1-amd64
+ local curversion initdir DPKG_ARCH minversion cm_x tmp
+ curversion=2.6.34-1-amd64
+ initdir=
+ '[' -z '' ']'
+ case ${DPKG_ARCH:-} in
+ minversion=2.6.12
+ dpkg --compare-versions 2.6.34-1-amd64 lt 2.6.12
+ return 0
+ check_minkver 2.6.34-1-amd64 /usr/share/initramfs-tools/hooks
+ local curversion initdir DPKG_ARCH minversion cm_x tmp
+ curversion=2.6.34-1-amd64
+ initdir=/usr/share/initramfs-tools/hooks
+ '[' -z /usr/share/initramfs-tools/hooks ']'
+ set_initlist
+ unset initlist
+ for si_x in '${initdir}/*'
+ '[' /usr/share/initramfs-tools/hooks/busybox = 
'/usr/share/initramfs-tools/hooks/*' ']'
+ case ${si_x#${initdir}/} in
+ '[' '!' -x /usr/share/initramfs-tools/hooks/busybox ']'
+ '[' -d /usr/share/initramfs-tools/hooks/busybox ']'
+ initlist=' busybox'
+ for si_x in '${initdir}/*'
+ '[' /usr/share/initramfs-tools/hooks/dmsetup = 
'/usr/share/initramfs-tools/hooks/*' ']'
+ case ${si_x#${initdir}/} in
+ '[' '!' -x /usr/share/initramfs-tools/hooks/dmsetup ']'
+ '[' -d /usr/share/initramfs-tools/hooks/dmsetup ']'
+ initlist=' busybox dmsetup'
+ for si_x in '${initdir}/*'
+ '[' /usr/share/initramfs-tools/hooks/keymap = 
'/usr/share/initramfs-tools/hooks/*' ']'
+ case ${si_x#${initdir}/} in
+ '[' '!' -x /usr/share/initramfs-tools/hooks/keymap ']'
+ '[' -d /usr/share/initramfs-tools/hooks/keymap ']'
+ initlist=' busybox dmsetup keymap'
+ for si_x in '${initdir}/*'
+ '[' /usr/share/initramfs-tools/hooks/klibc = 
'/usr/share/initramfs-tools/hooks/*' ']'
+ case ${si_x#${initdir}/} in
+ '[' '!' -x /usr/share/initramfs-tools/hooks/klibc ']'
+ '[' -d /usr/share/initramfs-tools/hooks/klibc ']'
+ initlist=' busybox dmsetup keymap klibc'
+ for si_x in '${initdir}/*'
+ '[' /usr/share/initramfs-tools/hooks/lvm2 = 
'/usr/share/initramfs-tools/hooks/*' ']'
+ case ${si_x#${initdir}/} in
+ '[' '!' -x /usr/share/initramfs-tools/hooks/lvm2 ']'
+ '[' -d /usr/share/initramfs-to

Bug#585991: marked as done (initramfs-tools: package installation fails (postinst scripts?))

[Debian Bug Tracking System]

Your message dated Fri, 18 Jun 2010 13:18:23 +
with message-id 
and subject line Bug#585991: fixed in initramfs-tools 0.97
has caused the Debian Bug report #585991,
regarding initramfs-tools: package installation fails (postinst scripts?)
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.)


-- 
585991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.94.4
Severity: serious
Justification: Policy 6.4

Cannot upgrade to initramfs-tools 0.96.1, I have to downgrade back to 0.94.4
for aptitude to work properly.

# aptitude upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information... Done
Initializing package states... Done
Reading task descriptions... Done
The following packages will be upgraded:
  initramfs-tools
1 packages upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Need to get 0B/78.8kB of archives. After unpacking 0B will be used.
Do you want to continue? [Y/n/?] y
Writing extended state information... Done
Reading changelogs... Done
(Reading database ... 164486 files and directories currently installed.)
Preparing to replace initramfs-tools 0.94.4 (using .../initramfs-
tools_0.96.1_all.deb) ...
Unpacking replacement initramfs-tools ...
Processing triggers for man-db ...
Setting up initramfs-tools (0.96.1) ...
Installing new version of config file /etc/initramfs-tools/initramfs.conf ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.32-trunk-686-bigmem
[: 2: /sys/block/md2: unexpected operator
readlink: extra operand `:'
Try `readlink --help' for more information.
dirname: missing operand
Try `dirname --help' for more information.
dirname: missing operand
Try `dirname --help' for more information.
dirname: missing operand
Try `dirname --help' for more information.
dirname: missing operand
[and so on until aptitude is killed]



-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=//vmlinuz-2.6.32-trunk-686-bigmem 
root=UUID=3078287d-711f-4a0e-9d85-4033c3f9ac77 ro

-- /proc/filesystems
reiserfs
ext2
fuseblk

-- lsmod
Module  Size  Used by
nls_utf8 908  1 
cifs  219978  2 
tun 8728  2 
ppdev   4058  0 
lp  5570  0 
parport22554  2 ppdev,lp
sco 5837  2 
bnep7376  2 
l2cap  21677  3 bnep
crc16   1027  1 l2cap
bluetooth  36259  5 sco,bnep,l2cap
rfkill 10196  2 bluetooth
acpi_cpufreq4907  0 
cpufreq_powersave602  0 
cpufreq_stats   1940  0 
cpufreq_userspace   1444  0 
cpufreq_conservative 4018  0 
kvm_intel  32458  3 
binfmt_misc 4875  1 
kvm   179565  1 kvm_intel
fuse   43554  1 
bridge 32851  0 
stp  996  1 bridge
ext2   46141  1 
mbcache 3762  1 ext2
loop9721  0 
usbhid 26836  0 
hid50545  1 usbhid
snd_hda_codec_analog45498  1 
snd_hda_intel  15347  3 
snd_hda_codec  46002  2 snd_hda_codec_analog,snd_hda_intel
snd_hwdep   4054  1 snd_hda_codec
snd_pcm_oss28479  0 
snd_mixer_oss  10461  1 snd_pcm_oss
snd_pcm47518  4 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq_midi3480  0 
snd_rawmidi12313  1 snd_seq_midi
snd_seq_midi_event  3684  1 snd_seq_midi
snd_seq35303  2 snd_seq_midi,snd_seq_midi_event
snd_timer  12258  2 snd_pcm,snd_seq
snd_seq_device  3673  3 snd_seq_midi,snd_rawmidi,snd_seq
snd33551  16 
snd_hda_codec_analog,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
uhci_hcd   16033  0 
ide_pci_generic 1924  0 
ehci_hcd   27626  0 
i915  217471  3 
ide_core   63922  1 ide_pci_generic
drm_kms_helper 17183  1 i915
sg 15932  0 
drm   108143  4 i915,drm_kms_helper
ata_generic 2015  0 
sr_mod 10770  0 
soundcore   3450  1 snd
usbcore98278  4 usbhid,uhci_hcd,ehci_hcd
snd_page_alloc  5045

Bug#583700: marked as done (initramfs-tools: package upgrade fails)

[Debian Bug Tracking System]

Your message dated Fri, 18 Jun 2010 13:18:23 +
with message-id 
and subject line Bug#583695: fixed in initramfs-tools 0.97
has caused the Debian Bug report #583695,
regarding initramfs-tools: package upgrade fails
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.)


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

Hi,

I get this when I try to install the latest version:

Unpacking replacement initramfs-tools ...
Setting up initramfs-tools (0.95) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for man-db ...
Processing triggers for initramfs-tools ...
/usr/sbin/update-initramfs: line 317: 1: unbound variable
dpkg: error processing initramfs-tools (--install):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 initramfs-tools

Gabor

-- Package-specific info:
-- initramfs sizes
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-2.6.33.5 root=/dev/md4 ro console=tty0 selinux=0 
audit=0 hpet=force sata_nv.adma=0 radeon.modeset=1 quiet

-- resume
RESUME=UUID=b0d60940-d4a8-4417-90fd-d412c2ee7153
-- /proc/filesystems
ext3
ext4
iso9660
udf
fuseblk

-- lsmod
Module  Size  Used by
bridge 43562  0 
stp 1971  1 bridge
llc 5208  2 bridge,stp
fuse   55997  1 
pppoe   8337  2 
pppox   2566  1 pppoe
ipt_MASQUERADE  1647  1 
xt_recent   7304  2 
ipt_ULOG7527  1 
dm_crypt   10952  0 
snd_usb_audio  82066  0 
snd_hwdep   5656  1 snd_usb_audio
snd_usb_lib16597  1 snd_usb_audio
snd_seq_midi5010  0 
snd_seq_midi_event  6465  1 snd_seq_midi
snd_rawmidi18298  2 snd_usb_lib,snd_seq_midi
saa7134_alsa   10563  0 
tuner  17798  1 
saa7134   152625  1 saa7134_alsa
videobuf_dma_sg11056  2 saa7134_alsa,saa7134
firewire_ohci  20029  0 
videobuf_core  16599  2 saa7134,videobuf_dma_sg
parport_pc 30757  0 
tveeprom   12970  1 saa7134
firewire_core  44333  1 firewire_ohci
sky2   40834  0 
forcedeth  46335  0 
parport33115  1 parport_pc
floppy 53605  0 

-- /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = no
do_bootloader = yes
do_initrd = yes
link_in_boot = yes
postinst_hook = /usr/sbin/update-grub
postrm_hook   = /usr/sbin/update-grub

-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
KEYMAP=n
COMPRESS=gzip
BOOT=local
DEVICE=
NFSROOT=auto

-- /etc/crypttab
# 


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.33.5 (SMP w/1 CPU core; PREEMPT)
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 initramfs-tools depends on:
ii  cpio 2.11-4  GNU cpio -- a program to manage ar
ii  findutils4.4.2-1 utilities for finding files--find,
ii  klibc-utils  1.5.18-1small utilities built with klibc f
ii  module-init-tools3.12~pre2-3 tools for managing Linux kernel mo
ii  udev 154-1   /dev/ and hotplug management daemo

Versions of packages initramfs-tools recommends:
ii  busybox   1:1.15.3-1 Tiny utilities for small and embed

initramfs-tools suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: initramfs-tools
Source-Version: 0.97

We believe that the bug you reported is fixed in the latest version of
initramfs-tools, which is due to be installed in the Debian FTP archive:

initramfs-tools_0.97.dsc
  to main/i/initramfs-tools/initramfs-tools_0.97.dsc
initramfs-tools_0.97.tar.gz
  to main/i/initramfs-tools/initramfs-tools_0.97.tar.gz
initramfs-tools_0.97_all.deb
  to main/i/initramfs-tools/initramfs-tools_0.97_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 583...@bugs.debian.org,
and the ma

Bug#583666: marked as done ([initramfs-tools] upgrade from 0.94.4 to 0.95 fails)

[Debian Bug Tracking System]

Your message dated Fri, 18 Jun 2010 13:18:23 +
with message-id 
and subject line Bug#583695: fixed in initramfs-tools 0.97
has caused the Debian Bug report #583695,
regarding [initramfs-tools] upgrade from 0.94.4 to 0.95 fails
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.)


-- 
583695: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583695
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: initramfs-tools
Version: 0.95
Severity: important

--- Please enter the report below this line. ---

Got this while updating sid:

Elaborazione dei trigger per initramfs-tools...
/usr/sbin/update-initramfs: 517: 1: parameter not set
dpkg: errore nell'elaborare initramfs-tools (--configure):
 il sottoprocesso vecchio script di post-installation ha restituito lo 
stato di errore 2


line 517 of the script is the last line "esac":

[...]
u)
update
;;
esac

I don't have any kernel that requires an initramfs installed.


thanks,
riccardo

--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.34

Debian Release: squeeze/sid
  500 unstablemi.mirror.garr.it
  500 unstableftp.de.debian.org
  500 stable  www.emdebian.org
1 experimentalftp.de.debian.org

--- Package information. ---
Depends  (Version) | Installed
==-+-=
klibc-utils   (>= 1.5.9-1) | 1.5.18-1
cpio   | 2.11-4
module-init-tools  | 3.12~pre2-3
udev  (>= 0.086-1) | 154-1
findutils  (>= 4.2.24) | 4.4.2-1


Recommends (Version) | Installed
-+-===
busybox   (>= 1:1.01-3)  | 1:1.15.3-1
 OR busybox-initramfs|


Package's Suggests field is empty.


--- Output from package bug script ---
-- initramfs sizes
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-2.6.34 root=/dev/sda1 ro quiet

-- resume
RESUME=/dev/sda3
-- /proc/filesystems
ext3
ext2
ext4
fuseblk

-- lsmod
Module  Size  Used by
aes_generic27407  3
acpi_cpufreq6119  1
cpufreq_stats   3147  0
ipv6  259095  18
fbcon  34231  71
tileblit2159  1 fbcon
font7933  1 fbcon
bitblit 4677  1 fbcon
softcursor  1349  1 bitblit
uinput  7006  1
fuse   56272  1
joydev  9242  0
loop   13478  0
snd_hda_codec_intelhdmi 9375  1
snd_hda_codec_realtek   278704  1
usbhid 33840  0
hid72005  1 usbhid
snd_hda_intel  20990  0
snd_hda_codec  83683  3 
snd_hda_codec_intelhdmi,snd_hda_codec_realtek,snd_hda_intel

snd_hwdep   5938  1 snd_hda_codec
snd_pcm_oss33609  0
uvcvideo   52676  0
videodev   37498  1 uvcvideo
v4l1_compat12985  2 uvcvideo,videodev
v4l2_compat_ioctl32 9035  1 videodev
snd_mixer_oss  14926  1 snd_pcm_oss
option 18271  0
snd_pcm74709  3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
sdhci_pci   6759  0
i915  280406  2
sdhci  14731  1 sdhci_pci
snd_seq_dummy   1582  0
arc41385  2
snd_seq_oss25118  0
ecb 1975  2
snd_seq_midi4972  0
snd_rawmidi19699  1 snd_seq_midi
snd_seq_midi_event  6427  2 snd_seq_oss,snd_seq_midi
drm_kms_helper 25767  1 i915
drm   181359  3 i915,drm_kms_helper
snd_seq46781  6 
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
fb 45591  6 
fbcon,tileblit,bitblit,softcursor,i915,drm_kms_helper

iwlagn 87009  0
snd_timer  19361  2 snd_pcm,snd_seq
i2c_algo_bit4984  1 i915
iwlcore   119413  1 iwlagn
snd_seq_device  6058  5 
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq

mmc_core   57815  1 sdhci
fan 3591  0
usbserial  34206  1 option
cfbcopyarea 3161  1 i915
mac80211  137682  2 iwlagn,iwlcore
snd60816  12 
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device

psmouse36294  0
video  20710  1 i915
thermal  

Bug#582858: marked as done (initramfs-tools: MODULES=dep fails when / is ubifs)

[Debian Bug Tracking System]

Your message dated Fri, 18 Jun 2010 13:18:23 +
with message-id 
and subject line Bug#582858: fixed in initramfs-tools 0.97
has caused the Debian Bug report #582858,
regarding initramfs-tools: MODULES=dep fails when / is ubifs
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.)


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

When / is on ubifs, if i set MODULES=dep in 
/etc/initramfs-tools/initramfs.conf, i get the following error:

0 r...@moo:~# update-initramfs -k all -u
update-initramfs: Generating /boot/initrd.img-2.6.32-5-kirkwood
readlink: missing operand
Try `readlink --help' for more information.
stdin: Illegal seek
mkinitramfs: for root  missing  /sys/block/ entry
mkinitramfs: workaround is MODULES=most
mkinitramfs: Error please report the bug
update-initramfs: failed for /boot/initrd.img-2.6.32-5-kirkwood
0 r...@moo:~# 

here's more information about this machine (it's a guruplug, running 
directly from nand flash:

0 r...@moo:~# cat /proc/cmdline 
console=ttyS0,115200n8 root=ubi0:root ubi.mtd=2 rootfstype=ubifs
0 r...@moo:~# cat /proc/mounts 
rootfs / rootfs rw 0 0
none /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
none /proc proc rw,nosuid,nodev,noexec,relatime 0 0
none /dev devtmpfs rw,relatime,size=254824k,nr_inodes=63706,mode=755 0 0
none /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
ubi0:root / ubifs rw,relatime 0 0
tmpfs /lib/init/rw tmpfs rw,nosuid,relatime,mode=755 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0
tmpfs /var/cache/apt/archives tmpfs rw,nosuid,nodev,noexec,relatime,mode=755 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
/dev/md0 /home ext3 rw,relatime,errors=continue,data=ordered 0 0
0 r...@moo:~# 

I can provide more info if you want it; please let me know.

Thanks for keeping initramfs-tools up-to-date!

--dkg


-- Package-specific info:
-- /proc/cmdline
console=ttyS0,115200n8 root=ubi0:root ubi.mtd=2 rootfstype=ubifs

-- /proc/filesystems
ext3

-- lsmod
Module  Size  Used by
ext3  110692  1 
jbd37274  1 ext3
mbcache 4860  1 ext3
sd_mod 31168  2 
crc_t10dif  1106  1 sd_mod
ipv6  252757  10 
btmrvl_sdio 8140  0 
btmrvl 10622  1 btmrvl_sdio
libertas_sdio   6387  0 
bluetooth  47558  1 btmrvl
libertas   79561  1 libertas_sdio
mv_cesa 4620  0 
rfkill 14240  1 bluetooth
lib802113680  1 libertas
usb_storage34775  2 
aes_generic32820  1 mv_cesa
raid0   5835  1 
md_mod 80194  2 raid0
mmc_block   7634  0 
sata_mv24181  0 
ehci_hcd   35267  0 
libata137558  1 sata_mv
mvsdio  5294  0 
mv643xx_eth22510  0 
usbcore   122040  3 usb_storage,ehci_hcd
scsi_mod  119084  3 sd_mod,usb_storage,libata
mmc_core   49668  4 btmrvl_sdio,libertas_sdio,mmc_block,mvsdio
nls_base5367  1 usbcore
libphy 14808  1 mv643xx_eth

-- /etc/initramfs-tools/initramfs.conf
MODULES=dep
BUSYBOX=y
KEYMAP=n
COMPRESS=gzip
BOOT=local
DEVICE=eth0
NFSROOT=auto

-- /sys/block
md0
mtdblock0
mtdblock1
mtdblock2
sda
sdb
sdc
sdd


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: armel (armv5tel)

Kernel: Linux 2.6.32-5-kirkwood
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages initramfs-tools depends on:
ii  cpio 2.11-4  GNU cpio -- a program to manage ar
ii  findutils4.4.2-1 utilities for finding files--find,
ii  klibc-utils  1.5.18-1small utilities built with klibc f
ii  module-init-tools3.12~pre2-3 tools for managing Linux kernel mo
ii  udev 154-1   /dev/ and hotplug management daemo

Versions of packages initramfs-tools recommends:
ii  busybox   1:1.14.2-2 Tiny utilities for small and embed

initramfs-tools suggests no packages.

-- Configuration Files:
/etc/initramfs-tools/initramfs.conf changed:
MODULES=dep
BUSYBOX=y
KEYMAP=n
COMPRESS=gzip
BOOT=local
DEVICE=eth0
NFSROOT=auto


-- no debconf information


--- End Message ---
--- Begin Message ---
Source: 

Bug#583695: marked as done (/usr/sbin/update-initramfs: line 317: 1: unbound variable)

[Debian Bug Tracking System]

Your message dated Fri, 18 Jun 2010 13:18:23 +
with message-id 
and subject line Bug#583695: fixed in initramfs-tools 0.97
has caused the Debian Bug report #583695,
regarding /usr/sbin/update-initramfs: line 317: 1: unbound variable
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Setting up initramfs-tools (0.95) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools ...
/usr/sbin/update-initramfs: line 317: 1: unbound variable
dpkg: error processing initramfs-tools (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)


- -- Package-specific info:
- -- initramfs sizes
- -- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic 
root=UUID=cd9a1998-9fb2-4208-aba6-bc2ba8f5e36a ro rootfstype=ext4 quiet splash

- -- /proc/filesystems
ext3
ext2
ext4
fuseblk
vfat

- -- lsmod
Module  Size  Used by
nls_iso8859_1   3249  0 
nls_cp437   4919  0 
vfat8901  0 
fat47767  1 vfat
usb_storage39425  0 
aes_i5867268  1 
aes_generic26863  1 aes_i586
hidp   11083  0 
hid67032  1 hidp
rfcomm 33421  4 
sco 7885  2 
bridge 45582  0 
stp 1655  1 bridge
bnep9436  2 
l2cap  30624  17 hidp,rfcomm,bnep
ppdev   5259  0 
lp  7028  0 
parport32635  2 ppdev,lp
dm_crypt   11331  0 
joydev  8708  0 
snd_hda_codec_idt  51914  1 
snd_hda_intel  21877  2 
snd_hda_codec  74201  2 snd_hda_codec_idt,snd_hda_intel
snd_hwdep   5412  1 snd_hda_codec
arc41153  2 
snd_pcm70662  2 snd_hda_intel,snd_hda_codec
snd_seq_midi4557  0 
snd_rawmidi19056  1 snd_seq_midi
snd_seq_midi_event  6003  1 snd_seq_midi
snd_seq47263  2 snd_seq_midi,snd_seq_midi_event
pcmcia 33024  0 
snd_timer  19098  2 snd_pcm,snd_seq
snd_seq_device  5700  3 snd_seq_midi,snd_rawmidi,snd_seq
iwlagn105566  0 
dell_wmi1793  0 
yenta_socket   20408  1 
iwlcore   105922  1 iwlagn
snd54148  13 
snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
sdhci_pci   5470  0 
dell_laptop 6856  0 
rsrc_nonstatic 10015  1 yenta_socket
mac80211  204922  2 iwlagn,iwlcore
sdhci  15462  1 sdhci_pci
psmouse63245  0 
dcdbas  5422  1 dell_laptop
btusb  10925  2 
bluetooth  49892  10 hidp,rfcomm,sco,bnep,l2cap,btusb
pcmcia_core32964  3 pcmcia,yenta_socket,rsrc_nonstatic
led_class   2864  2 iwlcore,sdhci
soundcore   6620  1 snd
serio_raw   3978  0 
cfg80211  126485  3 iwlagn,iwlcore,mac80211
snd_page_alloc  7076  2 snd_hda_intel,snd_pcm
fbcon  35102  73 
tileblit2031  1 fbcon
font7557  1 fbcon
bitblit 4707  1 fbcon
softcursor  1189  1 bitblit
vga16fb11385  0 
vgastate8961  1 vga16fb
i915  282354  2 
ohci1394   26950  0 
drm_kms_helper 29297  1 i915
intel_agp  24177  2 i915
ieee1394   81181  1 ohci1394
drm   162471  3 i915,drm_kms_helper
tg3   109292  0 
agpgart31724  2 intel_agp,drm
i2c_algo_bit5028  1 i915
video  17375  1 i915
output  1871  1 video

- -- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
KEYMAP=n
COMPRESS=gzip
BOOT=local
DEVICE=
NFSROOT=auto


- -- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-22-generic (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI

Bug#537139: marked as done (initramfs-tools: please include update-initramfs bash completion)

[Debian Bug Tracking System]

Your message dated Fri, 18 Jun 2010 13:18:23 +
with message-id 
and subject line Bug#537139: fixed in initramfs-tools 0.97
has caused the Debian Bug report #537139,
regarding initramfs-tools: please include update-initramfs bash completion
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.)


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

Hi,

Please install the following as /etc/bash_completion.d/initramfs-tools
to enable bash completion for update-initramfs :

--
# update-initramfs(8) completion
# provided by Stéphane (kwisatz) Jourdois 

_update_initramfs()
{
local cur prev valid_options

cur=`_get_cword`
prev=${COMP_WORDS[COMP_CWORD-1]}

# The only option that takes an argument is -k
if [[ "$prev" == '-k' ]]; then
# Complete with kernel versions
_kernel_versions
return;
fi

# Complete with available options (obtained from -h)
valid_options=$( update-initramfs -h 2>&1 | \
sed -e '/^ -/!d;s/^ \(-\w\+\).*/\1/' )
COMPREPLY=( $( compgen -W "$valid_options" -- $cur ) )
}
complete -F _update_initramfs update-initramfs
--

Thanks in advance,

Stéphane.


--- End Message ---
--- Begin Message ---
Source: initramfs-tools
Source-Version: 0.97

We believe that the bug you reported is fixed in the latest version of
initramfs-tools, which is due to be installed in the Debian FTP archive:

initramfs-tools_0.97.dsc
  to main/i/initramfs-tools/initramfs-tools_0.97.dsc
initramfs-tools_0.97.tar.gz
  to main/i/initramfs-tools/initramfs-tools_0.97.tar.gz
initramfs-tools_0.97_all.deb
  to main/i/initramfs-tools/initramfs-tools_0.97_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 537...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Prokop  (supplier of updated initramfs-tools package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 18 Jun 2010 12:28:04 +0200
Source: initramfs-tools
Binary: initramfs-tools
Architecture: source all
Version: 0.97
Distribution: unstable
Urgency: low
Maintainer: Debian kernel team 
Changed-By: Michael Prokop 
Description: 
 initramfs-tools - tools for generating an initramfs
Closes: 396388 537139 582858 583695 585991 585992
Changes: 
 initramfs-tools (0.97) unstable; urgency=low
 .
   [ Martin Michlmayr ]
   * [e65ee48] Produce an error when root cannot be determined with
 MODULES=dep
   * [bb66fc2] hook-functions/init/scripts/local: add support for ubifs.
 (Closes: #582858) - thanks to Martin Michlmayr 
 .
   [ Ferenc Wagner ]
   * [1d66ae1] scripts/nfs: cleanup retry logic
 .
   [ Colin Watson ]
   * [3054e3e] initramfs-tools: work around 'find -printf %Y' bug
 .
   [ maximilian attems ]
   * [a8a5ce4] script: Add update-initramfs.conf to bug report
   * [cc6077a] update-initramfs: Fix another unbound variable (Closes:
 #583695)
   * [b1f74e6] get_fstype: reference blkid in comment - thanks to
 Christoph Anton Mitterer 
   * [eb93a7e] pre_mountroot(): reduce timeout to 30 seconds
   * [38563fe] scripts/functions: On panic change to tty1 if chvt around
 - thanks to Colin Watson 
   * [2031379] mkinitramfs: No point in hardcoding busybox path
   * [68c87cd] mkinitramfs: check syntax of boot and hook scripts
   * [ae02e4b] scripts/functions: beautify a bit reduce_satisfied()
   * [22d996c] maintainer doc: use git commands without the dash
   * [6147641] nfsmount: more small cleanups
   * [e967b03] mkinitramfs, lsinitramfs: Better error message for
 non-GNU getopt
   * Add lsinitramfs (to list content of an initramfs image) ([a39db63]
 [969f8fd] [fafede5] [2f3eb88])
 .
   [ Michael Prokop ]
   * [2a8c990] hook-functions/mkinitramfs/update-initramfs: consequently
 output error messages to stderr
   * [04b8619] init: display warning message if devtmpfs could not be
 mounted. - thanks to Ferenc Wagner 
   * [60afd2a] code cleanup: drop trailin

Bug#396388: marked as done (should allow hooks to abort build)

[Debian Bug Tracking System]

Your message dated Fri, 18 Jun 2010 13:18:23 +
with message-id 
and subject line Bug#396388: fixed in initramfs-tools 0.97
has caused the Debian Bug report #396388,
regarding should allow hooks to abort build
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.)


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

mkinitramfs is not a set -x script, and so when call_scripts runs a hook
script, any error is ignored.

In some cases, a hook script needs to abort the initramfs build. For
example, then nslu2-tools hook script can detect issues, like a missing
ixp ethernet driver, that will make the box unusable, and needs to be
able to abort the initramfs build in these situations.

Currently the only way for a hook script to abort the build is a nasty
hack. Since call_scripts sources /conf/param.conf, a hook script could
create that file, and make it exit 1. Of course, that's beyond gross,
and I won't do it. :-)

Please provide a mechanism for hook scripts to abort a build. Note that
in the past, if a hook script exited nonzero, the build did abort, so my
guess is that there are few hook scripts that exit nonzero in cases
where the build would continue. However, if you don't feel that's safe
now, an alternative would be to check for a flag file in the initramfs
tree, which a hook script could create to indicate that the build needs
to be aborted.

-- 
see shy jo


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: initramfs-tools
Source-Version: 0.97

We believe that the bug you reported is fixed in the latest version of
initramfs-tools, which is due to be installed in the Debian FTP archive:

initramfs-tools_0.97.dsc
  to main/i/initramfs-tools/initramfs-tools_0.97.dsc
initramfs-tools_0.97.tar.gz
  to main/i/initramfs-tools/initramfs-tools_0.97.tar.gz
initramfs-tools_0.97_all.deb
  to main/i/initramfs-tools/initramfs-tools_0.97_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 396...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Prokop  (supplier of updated initramfs-tools package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 18 Jun 2010 12:28:04 +0200
Source: initramfs-tools
Binary: initramfs-tools
Architecture: source all
Version: 0.97
Distribution: unstable
Urgency: low
Maintainer: Debian kernel team 
Changed-By: Michael Prokop 
Description: 
 initramfs-tools - tools for generating an initramfs
Closes: 396388 537139 582858 583695 585991 585992
Changes: 
 initramfs-tools (0.97) unstable; urgency=low
 .
   [ Martin Michlmayr ]
   * [e65ee48] Produce an error when root cannot be determined with
 MODULES=dep
   * [bb66fc2] hook-functions/init/scripts/local: add support for ubifs.
 (Closes: #582858) - thanks to Martin Michlmayr 
 .
   [ Ferenc Wagner ]
   * [1d66ae1] scripts/nfs: cleanup retry logic
 .
   [ Colin Watson ]
   * [3054e3e] initramfs-tools: work around 'find -printf %Y' bug
 .
   [ maximilian attems ]
   * [a8a5ce4] script: Add update-initramfs.conf to bug report
   * [cc6077a] update-initramfs: Fix another unbound variable (Closes:
 #583695)
   * [b1f74e6] get_fstype: reference blkid in comment - thanks to
 Christoph Anton Mitterer 
   * [eb93a7e] pre_mountroot(): reduce timeout to 30 seconds
   * [38563fe] scripts/functions: On panic change to tty1 if chvt around
 - thanks to Colin Watson 
   * [2031379] mkinitramfs: No point in hardcoding busybox path
   * [68c87cd] mkinitramfs: check syntax of boot and hook scripts
   * [ae02e4b] scripts/functions: beautify a bit reduce_satisfied()
   * [22d996c] maintainer doc: use git commands without the dash
   * [6147641] nfsmount: more small cleanups
   * [e967b03] mkinitramfs, lsinitramfs: Better error message for
 non-GNU getopt
   * Add lsinitramfs (to list content of an initramfs image) ([a39db63]
 [969f8fd] [fafede5] [2f3eb88])
 .
   [ Michael Prokop ]
   * [2a8c990] hook-functions/mkinitramfs/update-initramfs: consequently
 output error messages to stderr
   * [04b8619] init: display warning message 

initramfs-tools_0.97_amd64.changes ACCEPTED

[Archive Administrator]

Accepted:
initramfs-tools_0.97.dsc
  to main/i/initramfs-tools/initramfs-tools_0.97.dsc
initramfs-tools_0.97.tar.gz
  to main/i/initramfs-tools/initramfs-tools_0.97.tar.gz
initramfs-tools_0.97_all.deb
  to main/i/initramfs-tools/initramfs-tools_0.97_all.deb


Override entries for your package:
initramfs-tools_0.97.dsc - source utils
initramfs-tools_0.97_all.deb - optional utils

Announcing to debian-devel-chan...@lists.debian.org
Closing bugs: 396388 537139 582858 583695 585991 585992 


Thank you for your contribution to Debian.


-- 
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/e1opbsh-00076j...@ries.debian.org

Processing of initramfs-tools_0.97_amd64.changes

[Archive Administrator]

initramfs-tools_0.97_amd64.changes uploaded successfully to localhost
along with the files:
  initramfs-tools_0.97.dsc
  initramfs-tools_0.97.tar.gz
  initramfs-tools_0.97_all.deb

Greetings,

Your Debian queue daemon (running on host ries.debian.org)


-- 
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/e1opb2k-00059w...@ries.debian.org

Bug#582275: ext3 filesystem corruption on md RAID1 device

[Theodore Tso]

On Jun 18, 2010, at 7:09 AM, Theodore Tso wrote:
> 
> It could be an e2fsck bug, or it could be a hardware issue.  In my 
> experience, every time
> I've tried digging into problems with e2fsck -fy not fixing all problems in a 
> single
> pass, it's been a hardware problem.  That being said, multiply claimed blocks 
> is
> something that isn't exercised that much, so it's *possible* that it is an 
> e2fsck bug.
> 
> I really would need a reproducible test case before I could do anything 
> though.

And reviewing the thread, the fact that you are reliably getting directory 
corruption
every single time you're booting, and the reliability of the hardware has been 
called into question (forgive me for being a little suspicious of people trying
to do reliable storage using IDE devices).

-- Ted




--
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/bb158359-ccdb-49e6-975d-b2a9f3062...@mit.edu

Bug#582275: ext3 filesystem corruption on md RAID1 device

[Theodore Tso]

On Jun 18, 2010, at 3:12 AM, Buehl, Reiner wrote:

> Hi Jan,
> 
> I tried for a while with alternate hardware and the original controller but 
> the error did never happen again. I think your idea of a bug in e2fsck's 
> handling of multiply claimed blocks is the only explanation: Maybe during a 
> corruption long ago a number of multiply claimed blocks existed and where 
> reduced with each reboot. Is this possible? How can this be fixed?
> 

It could be an e2fsck bug, or it could be a hardware issue.  In my experience, 
every time
I've tried digging into problems with e2fsck -fy not fixing all problems in a 
single
pass, it's been a hardware problem.  That being said, multiply claimed blocks is
something that isn't exercised that much, so it's *possible* that it is an 
e2fsck bug.

I really would need a reproducible test case before I could do anything though.

 -- Ted





--
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/ee6e2e73-39b6-4d90-b2e2-3ba2c1dd4...@mit.edu

Re: [initramfs-tools PATCH] scripts/nfs: cleanup retry logic

[maximilian attems]

On Thu, 17 Jun 2010, Ferenc Wagner wrote:

> The condition of log_end_msg was always true.
> Calling do_nfsmount before the loop lets us drop two other checks.
> 
> Signed-off-by: Ferenc Wagner 

thanks nice, merged and pushed out, will be in next upstream release.


-- 
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/20100618094443.gb25...@stro.at

Processed: Re: Bug#586292: xserver-xorg-core: deadlocks for no apparent reason

[Debian Bug Tracking System]

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

> reassign 586292 linux-2.6 2.6.32-15
Bug #586292 [xserver-xorg-core] xserver-xorg-core: deadlocks for no apparent 
reason
Bug reassigned from package 'xserver-xorg-core' to 'linux-2.6'.
Bug No longer marked as found in versions xorg-server/2:1.7.7-2.
Bug #586292 [linux-2.6] xserver-xorg-core: deadlocks for no apparent reason
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.
> kthxbye
Stopping processing here.

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

Re: Bug#586292: xserver-xorg-core: deadlocks for no apparent reason

[Julien Cristau]

reassign 586292 linux-2.6 2.6.32-15
kthxbye

On Fri, Jun 18, 2010 at 09:57:31 +0200, Ulrich Klauer wrote:

> I'm running a regularly updated squeeze/testing system (at most a few days
> lag behind the current version). Earlier this week, I experienced for the
> first time a complete freeze of my X system, for no apparent reason - just
> browsing the web (using Iceweasel), nothing dangerous.
> 
> Today, this has happened again, again while browsing, but this may be a
> coincidence. The desktop stops responding to any key presses or mouse
> movements; automatically updated displays like the clock stop too. No
> reaction to Ctrl-Alt-BS or Ctrl-Alt-Del. However, Magic SysRq is still
> working.
> 
> I am including the relevant part of syslog, which shows a deadlock warning
> first from "events" and then from "Xorg". Please note that the file
> Xorg.0.log automatically included below is not of before the crash, but of
> the reboot. However, the differences are minimal - see attached diff.
> 
Sounds like a kernel bug to me, so reassigning.

> 
> Jun 18 08:30:23 chalkos kernel: [   99.655588] CE: hpet increasing 
> min_delta_ns to 15000 nsec
> Jun 18 08:33:52 chalkos anacron[1263]: Job `cron.daily' started
> Jun 18 08:33:52 chalkos anacron[2247]: Updated timestamp for job `cron.daily' 
> to 2010-06-18
> Jun 18 08:53:44 chalkos kernel: [ 1500.100506] CE: hpet increasing 
> min_delta_ns to 22500 nsec
> Jun 18 08:53:44 chalkos kernel: [ 1500.100506] CE: hpet increasing 
> min_delta_ns to 33750 nsec
> Jun 18 08:56:44 chalkos kernel: [ 1680.532322] INFO: task events/0:9 blocked 
> for more than 120 seconds.
> Jun 18 08:56:44 chalkos kernel: [ 1680.532331] "echo 0 > 
> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> Jun 18 08:56:44 chalkos kernel: [ 1680.532337] events/0  D 
> 880001815640 0 9  2 0x
> Jun 18 08:56:44 chalkos kernel: [ 1680.532348]  880079101530 
> 0046 88003ab65fff 0001
> Jun 18 08:56:44 chalkos kernel: [ 1680.532357]   
> 81033d99 f8a0 88007bb9bfd8
> Jun 18 08:56:44 chalkos kernel: [ 1680.532366]  00015640 
> 00015640 88007bb53f90 88007bb54288
> Jun 18 08:56:44 chalkos kernel: [ 1680.532374] Call Trace:
> Jun 18 08:56:44 chalkos kernel: [ 1680.532391]  [] ? 
> change_page_attr_set_clr+0x2f2/0x394
> Jun 18 08:56:44 chalkos kernel: [ 1680.532404]  [] ? 
> __switch_to+0x27b/0x297
> Jun 18 08:56:44 chalkos kernel: [ 1680.532429]  [] ? 
> ttm_bo_wait_unreserved+0x102/0x11c [ttm]
> Jun 18 08:56:44 chalkos kernel: [ 1680.532438]  [] ? 
> autoremove_wake_function+0x0/0x2e
> Jun 18 08:56:44 chalkos kernel: [ 1680.532448]  [] ? 
> pick_next_task_fair+0xcd/0xd8
> Jun 18 08:56:44 chalkos kernel: [ 1680.532461]  [] ? 
> ttm_bo_reserve_locked+0x73/0xc4 [ttm]
> Jun 18 08:56:44 chalkos kernel: [ 1680.532472]  [] ? 
> ttm_bo_cleanup_refs+0xe4/0x248 [ttm]
> Jun 18 08:56:44 chalkos kernel: [ 1680.532484]  [] ? 
> ttm_bo_delayed_delete+0x88/0xf7 [ttm]
> Jun 18 08:56:44 chalkos kernel: [ 1680.532495]  [] ? 
> ttm_bo_delayed_workqueue+0x12/0x26 [ttm]
> Jun 18 08:56:44 chalkos kernel: [ 1680.532505]  [] ? 
> worker_thread+0x188/0x21d
> Jun 18 08:56:44 chalkos kernel: [ 1680.532516]  [] ? 
> ttm_bo_delayed_workqueue+0x0/0x26 [ttm]
> Jun 18 08:56:44 chalkos kernel: [ 1680.532523]  [] ? 
> autoremove_wake_function+0x0/0x2e
> Jun 18 08:56:44 chalkos kernel: [ 1680.532531]  [] ? 
> worker_thread+0x0/0x21d
> Jun 18 08:56:44 chalkos kernel: [ 1680.532537]  [] ? 
> kthread+0x79/0x81
> Jun 18 08:56:44 chalkos kernel: [ 1680.532545]  [] ? 
> child_rip+0xa/0x20
> Jun 18 08:56:44 chalkos kernel: [ 1680.532551]  [] ? 
> kthread+0x0/0x81
> Jun 18 08:56:44 chalkos kernel: [ 1680.532558]  [] ? 
> child_rip+0x0/0x20
> Jun 18 08:56:44 chalkos kernel: [ 1680.532583] INFO: task Xorg:1689 blocked 
> for more than 120 seconds.
> Jun 18 08:56:44 chalkos kernel: [ 1680.532587] "echo 0 > 
> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> Jun 18 08:56:44 chalkos kernel: [ 1680.532592] Xorg  D 
>  0  1689   1676 0x0044
> Jun 18 08:56:44 chalkos kernel: [ 1680.532600]  8145b1f0 
> 0082  00ffa02fc679
> Jun 18 08:56:44 chalkos kernel: [ 1680.532609]  8800376c29b8 
> 00ff8800376c2fb0 f8a0 88007ab51fd8
> Jun 18 08:56:44 chalkos kernel: [ 1680.532617]  00015640 
> 00015640 88007905bf90 88007905c288
> Jun 18 08:56:44 chalkos kernel: [ 1680.532625] Call Trace:
> Jun 18 08:56:44 chalkos kernel: [ 1680.532637]  [] ? 
> ttm_bo_wait+0x13c/0x160 [ttm]
> Jun 18 08:56:44 chalkos kernel: [ 1680.532646]  [] ? 
> schedule_timeout+0x2e/0xdd
> Jun 18 08:56:44 chalkos kernel: [ 1680.532658]  [] ? 
> ttm_bo_free_old_node+0x23/0x37 [ttm]
> Jun 18 08:56:44 chalkos kernel: [ 1680.532670]  [] ? 
> ttm_bo_move_accel_cleanup+0xbc/0x2c6 [ttm]
> Jun 18 08:56:44 chalkos kernel: [ 1680.532681]  [] ? 
> virt_

Processed: severity of 586289 is important, tagging 586289

[Debian Bug Tracking System]

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

> severity 586289 important
Bug #586289 [linux-2.6] linux-image-2.6.32-5-486: Driver pegasus freeze 
networking very often so one must reboot to get it to work again
Severity set to 'important' from 'grave'

> tags 586289 - squeeze
Bug #586289 [linux-2.6] linux-image-2.6.32-5-486: Driver pegasus freeze 
networking very often so one must reboot to get it to work again
Removed tag(s) squeeze.
> thanks
Stopping processing here.

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

Bug#505609: loader varialbe in kernel maintainer scripts

[Joachim Wiedorn]

Ben Hutchings  wrote on 2010-06-18 02:02:

> On Thu, 2010-06-17 at 20:37 -0400, Stephen Powell wrote:
> > On Thu, 17 Jun 2010 18:11:04 -0400 (EDT), Ben Hutchings wrote:
:
:
> > And how would one go about setting this "loader" variable?
> > The "loader" variable is not documented in the man page for
> > /etc/kernel-img.conf in Lenny, which appears to be the closest thing
> > there is to documentation for the variables supported by official
> > Debian stock kernel images.  Nevertheless, at your suggestion, I tried
> > putting
> > 
> >loader = lilo
> > 
> > in /etc/kernel-img.conf.  ("do_bootloader = yes" was also set.)  Then I
> > issued
> > 
> >dpkg-reconfigure linux-image-2.6.26-2-686
> > 
> > There was no evidence from the output that lilo was run.
> [...]
> 
> I'm sorry, you're right.  Most of the other variables at the top of the
> postinst script can be overridden by /etc/kernel-img.conf, but not this
> one.  Given that, I think you are right that the 'historical' bootloader
> setting should be restored in an update to lenny.

Now I am a little confused. How is the recommended procedure for using the
LILO bootloader within squeeze/sid ? 
How I understand the normal installation of lilo package have the result,
that lilo doesn't be started after an kernel update (and also after update
of initramfs-tools ?). 
What must I config on my squeeze machine that lilo bootloader will be
automatically updated after kernel update?


Fondest regards,
 Joachim Wiedorn



signature.asc
Description: PGP signature

Bug#582275: ext3 filesystem corruption on md RAID1 device

[Buehl, Reiner]

Hi Jan,

I tried for a while with alternate hardware and the original controller but the 
error did never happen again. I think your idea of a bug in e2fsck's handling 
of multiply claimed blocks is the only explanation: Maybe during a corruption 
long ago a number of multiply claimed blocks existed and where reduced with 
each reboot. Is this possible? How can this be fixed?

Best regards,
Reiner.

> -Original Message-
> From: Jan Kara [mailto:j...@suse.cz]
> Sent: Tuesday, June 01, 2010 12:23 PM
> To: Buehl, Reiner
> Subject: Re: ext3 filesystem corruption on md RAID1 device
>
>   Hi,
>
> On Tue 01-06-10 07:25:28, Buehl, Reiner wrote:
> > I have organized a second Promise SATA controller now. Should I move
> one
> > or both of the disks from my RAID1 from the Intel to the Promise
> controller
> > for testing?
>   I have no strong opinion. I'd just try moving the primary disk to the
> new
> controller and see what happens...
>
> > Regarding the repeated fscks: It seems that the fsck does not
> completely fix
> > everything even though it states so. The two attached fsck outputs
> that you
> > had a look at earlier are from two fscks that I did directly after
> each other
> > without any reboot. They are just a minute or two apart and both find
> problems
> > in the same group as far as I can see.
>   Yes, I've noticed that last time but I'd blamed it to a bug in e2fsck
> in
> handling of multiply claimed blocks. So if you run fsck for a third
> time,
> does it still complain (note that during second run, there were no more
> multiply claimed blocks)?
>
>   Honza
>
> > > -Original Message-
> > > From: linux-ide-ow...@vger.kernel.org [mailto:linux-ide-
> > > ow...@vger.kernel.org] On Behalf Of Jan Kara
> > > Sent: Monday, May 31, 2010 10:56 PM
> > > To: Buehl, Reiner
> > > Cc: Jan Kara; ty...@mit.edu; linux-...@vger.kernel.org; linux-
> > > fsde...@vger.kernel.org; 582...@bugs.debian.org
> > > Subject: Re: ext3 filesystem corruption on md RAID1 device
> > >
> > >   Hi,
> > >
> > > On Sat 29-05-10 13:48:56, Buehl, Reiner wrote:
> > > > I have an unused PATA controller on the mainboard - unfortunately
> I
> > > do
> > > > not have two SATA-to-PATA converters. Do you think that
> connecting
> > > the
> > > > two disks to the PATA controller is a good option? If so, I would
> > > have to
> > > > buy to adapters.
> > >   I have heard that the boards with both PATA and SATA slots have
> just
> > > one
> > > disk controller which has only different kinds of slots. So I'm not
> > > sure
> > > that would change anything. More interesting would be if you could
> > > borrow a
> > > SATA controller that you could plug into a PCI slot or so...
> > > Alternatively
> > > you could also try shuffling disks in the slots you already have.
> > >
> > > > Is there a way to fix the current file system problem with the
> > > original
> > > > setup first since repeated FSCKs always seem to return errors for
> the
> > > > same area again and again?
> > >   Do you mean that fsck does not fix all the problems? So if you
> run
> > > fsck
> > > -f -y several times in a row is keeps reporting problems? What kind
> of
> > > problems is it?
> > >
> > >   Honza
> > >
> > > > > -Original Message-
> > > > > From: Jan Kara [mailto:j...@suse.cz]
> > > > > Sent: Thursday, May 27, 2010 10:13 PM
> > > > > To: Buehl, Reiner
> > > > > Cc: ty...@mit.edu; linux-...@vger.kernel.org; linux-
> > > > > fsde...@vger.kernel.org
> > > > > Subject: Re: ext3 filesystem corruption on md RAID1 device
> > > > >
> > > > >   Hi,
> > > > >
> > > > > On Sun 23-05-10 05:46:29, Buehl, Reiner wrote:
> > > > > > Hi Ted,
> > > > > >
> > > > > > please find attached the output of two fsck.ext3 -fy /dev/md1
> > > runs
> > > > > > conducted directly after each other. The ext3 fs error
> message in
> > > > > dmesg
> > > > > > was:
> > > > >   I took a look at the fsck logs. So there are inodes 17269110-
> > > 17269115
> > > > > (from group 2108 if my counting is correct) that have problems.
> > > > > 17269110 is
> > > > > the corrupted directory, 17269111 is an unconnected directory
> (was
> > > > > subdir of
> > > > > 17269110), 17269112-17269115 share blocks with some other
> inodes.
> > > > >   Interestingly enough, these other inodes are all in group
> 2120
> > > and
> > > > > also
> > > > > the blocks that are shared are in group 2120.
> > > > >   Multiply claimed blocks in this amount are usually caused by
> a
> > > > > corrupted
> > > > > block bitmap. In your case, it seems as if bitmap for group
> 2120
> > > was
> > > > > not
> > > > > written (or was zeroed?) and thus later some inodes reused the
> > > space.
> > > > > This
> > > > > kind of corruption is usually caused by HW - flaky memory or
> disk
> > > > > controller (I wouldn't suspect disks in your case since the
> problem
> > > > > seems to
> > > > > consistently happen 

Bug#586289: linux-image-2.6.32-5-486: Driver pegasus freeze networking very often so one must reboot to get it to work again

[Paul Chany]

Package: linux-2.6
Version: 2.6.32-15
Severity: grave
Tags: squeeze
Justification: renders package unusable

Hi,

the driver pegasus freeze networking very often so one must to reboot 
to get networking work again. At reboot the system hang and one can 
see a message like:
[5952.880465] pegasus 1-1:1.0: update_eth_regs_async, status -22

At this point one must press the Reset button of the PC Box because 
the system hangs forever.

-- Package-specific info:
** Version:
Linux version 2.6.32-5-486 (Debian 2.6.32-15) (b...@decadent.org.uk) (gcc 
version 4.3.5 (Debian 4.3.5-1) ) #1 Tue Jun 1 04:27:25 UTC 2010

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-486 
root=UUID=127a8e72-b9d4-4a28-8aa9-e6cdcb3985c9 ro all_generic_ide quiet

** Not tainted

** Kernel log:
[7.386866] ohci_hcd :00:0b.0: power state changed by ACPI to D0
[7.391599] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
[7.391636] ohci_hcd :00:0b.0: PCI INT A -> Link[LNKD] -> GSI 11 (level, 
low) -> IRQ 11
[7.391792] ohci_hcd :00:0b.0: OHCI Host Controller
[7.391994] ohci_hcd :00:0b.0: new USB bus registered, assigned bus 
number 1
[7.392242] ohci_hcd :00:0b.0: irq 11, io mem 0xf7fff000
[7.957294] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
[7.957323] usb usb1: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[7.957344] usb usb1: Product: OHCI Host Controller
[7.957362] usb usb1: Manufacturer: Linux 2.6.32-5-486 ohci_hcd
[7.957380] usb usb1: SerialNumber: :00:0b.0
[7.958819] usb usb1: configuration #1 chosen from 1 choice
[7.959658] hub 1-0:1.0: USB hub found
[7.959803] hub 1-0:1.0: 2 ports detected
[9.469598] PM: Starting manual resume from disk
[9.469635] PM: Resume from partition 8:8
[9.469648] PM: Checking hibernation image.
[9.495441] PM: Error -22 checking image file
[9.495458] PM: Resume from disk failed.
[9.683653] EXT3-fs: INFO: recovery required on readonly filesystem.
[9.683682] EXT3-fs: write access will be enabled during recovery.
[   10.019741] kjournald starting.  Commit interval 5 seconds
[   10.019839] EXT3-fs: recovery complete.
[   10.038103] EXT3-fs: mounted filesystem with ordered data mode.
[   14.275485] udev: starting version 157
[   16.300368] Marking TSC unstable due to TSC halts in idle
[   16.301500] processor LNXCPU:00: registered as cooling_device1
[   16.344132] Switching to clocksource acpi_pm
[   16.682421] input: Lid Switch as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1
[   16.682917] ACPI: Lid Switch [LID]
[   16.683650] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[   16.683697] ACPI: Power Button [PWRF]
[   16.735214] input: PC Speaker as /devices/platform/pcspkr/input/input3
[   16.854916] psmouse serio1: ID: 12 02 3c
[   16.916017] ACPI: Battery Slot [MBAT] (battery absent)
[   17.086489] ACPI: AC Adapter [ADP1] (on-line)
[   17.582986] input: PS/2 Generic Mouse as 
/devices/platform/i8042/serio1/input/input4
[   17.912789] NET: Registered protocol family 23
[   17.941369] yenta_cardbus :00:13.0: CardBus bridge found [1179:0001]
[   17.950140] toshiba_acpi: Toshiba Laptop ACPI Extras version 0.19
[   17.950167] toshiba_acpi: HCI method: \_SB_.VALD.GHCI
[   18.071396] yenta_cardbus :00:13.0: ISA IRQ mask 0x06b8, PCI irq 11
[   18.071425] yenta_cardbus :00:13.0: Socket status: 3007
[   18.083845] parport_pc 00:0b: reported by Plug and Play ACPI
[   18.083954] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
[   18.085976] yenta_cardbus :00:13.1: CardBus bridge found [1179:0001]
[   18.213173] yenta_cardbus :00:13.1: ISA IRQ mask 0x0638, PCI irq 11
[   18.213203] yenta_cardbus :00:13.1: Socket status: 3007
[   18.569373] donauboe :00:11.0: power state changed by ACPI to D0
[   18.570090] donauboe :00:11.0: power state changed by ACPI to D0
[   18.586984] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
[   18.587026] donauboe :00:11.0: PCI INT A -> Link[LNKC] -> GSI 11 (level, 
low) -> IRQ 11
[   18.608224] IrDA: Registered device irda0
[   18.608250] toshoboe: Using multiple tasks
[   18.757339] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x100-0x3af: 
excluding 0x220-0x22f 0x330-0x337 0x388-0x38f
[   18.758735] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x3e0-0x4ff: 
clean.
[   18.759560] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x820-0x8ff: 
clean.
[   18.760770] pcmcia_socket pcmcia_socket1: cs: IO port probe 0xc00-0xcf7: 
clean.
[   18.762765] pcmcia_socket pcmcia_socket1: cs: IO port probe 0xa00-0xaff: 
clean.
[   19.156878] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: 
excluding 0x220-0x22f 0x330-0x337 0x388-0x38f
[   19.158656] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: 
clean.
[   19.159693] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: 
clean.
[   19.160848] pcmcia_socket pcmcia_socket0: cs: IO port pr