Bug#392986: linux-image-2.6.16-2-em64t-p4-smp: megaraid_sas issues warnings and RESETs

[Andrew Moise]

 Sumant Patro confirmed that that one-liner is a critical fix that
"must be applied."  Unfortunately, it doesn't fix my problem :-(.
I've gone back to the BLKDEV_MAX_RQ workaround for now; if I learn of
a better solution, I'll send it along.


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

where should arch/$arch/scripts go?

[dann frazier]

I'm looking at fixing #392592, and I'm wondering where
arch/$arch/scripts should go? ia64 has them (as does um).

Is linux-kbuild-2.6 the correct place?

If so, should I create a new orig.tar.gz rev?

On the other hand, I could just dump them in the generic linux-headers
package, I don't really understand the distinction.

-- 
dann frazier


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

Re: RFC: Possible (partial) solution for device persistence issue

[dann frazier]

On Tue, Oct 17, 2006 at 11:59:15PM +0200, Geert Stappers wrote:
> Please provide names of such tools.   (TIA)

udev - see /dev/by-id, etc.

-- 
dann frazier


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

Re: RFC: Possible (partial) solution for device persistence issue

[Geert Stappers]

Op 17-10-2006 om 17:10 schreef maximilian attems:
> On Tue, Oct 17, 2006 at 04:27:19PM +0200, Geert Stappers wrote:
> > Dear Kernel developers,
> > 
> > Your work is appriceated, but I have a request:
> > 
> >   Please allow reproducable hardware detection.
> > 
> > As systemadministrator I can't affort having a disk that is one moment
> > /dev/sda and the next reboot /dev/sdb.
> > 
> > Having a fast booting system is great, having disks swapped not.
> 
> the kernel _never_ guaranteed stable device nodes,
> that is an userspace policy.

I should smile.

In 1997 I had /dev/sda, which had SCSI target Id #3.
When I added another disk, being target #2, that became /dev/sda
And the original /dev/sda went into /dev/sdb
rendering the system _unbootable_
So after about 10 years, is the answer use UUID.

I should laugh ...

> use the tools that provide that.

Please provide names of such tools.   (TIA)


> > Please prefer consistence above speed.
> > 
> > Thank you for reading this humble plea.
> > Geert Stappers
> 
> edgy udev transforms the fstab to use plain uuids,
> to guarantee correct root recognition.
> i guess their installer also add uuid entries to the newly
> installed fstab - why is that not in d-i?
> 
> -- 
> maks

Cheers
Geert Stappers
-- 
During system recovery provide the boot option:

  root=UUID=4a6aed11-42dd-4c82-81ce-8f469e93f210


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

Processed: Re: Bug#393773: initramfs-tools: install fails, 'sed: no input files', missing escape in presinst file

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tags 393773 pending
Bug#393773: initramfs-tools: install fails, 'sed: no input files', missing 
escape in presinst file
There were no tags set.
Tags added: pending

> thanks for report
Unknown command or malformed arguments to command.

> On Tue, Oct 17, 2006 at 02:57:53PM -0400, Federico Grau wrote:
Unknown command or malformed arguments to command.

> > Package: initramfs-tools
Unknown command or malformed arguments to command.

> > Version: 0.83
Unknown command or malformed arguments to command.

> > Severity: grave
Unknown command or malformed arguments to command.

Too many unknown commands, stopping here.

Please contact me if you need assistance.

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


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

Bug#393773: initramfs-tools: install fails, 'sed: no input files', missing escape in presinst file

[maximilian attems]

tags 393773 pending
thanks for report

On Tue, Oct 17, 2006 at 02:57:53PM -0400, Federico Grau wrote:
> Package: initramfs-tools
> Version: 0.83
> Severity: grave
> Justification: renders package unusable
> 
> In the config file initramfs-tools.preinst , there is a missing escape 
> of the endofline/newline on line 32.
> 
> A patch is attached to correct this.
> 
> donfede

already fixed in my repo,
will upload tomorrow morning
 
-- 
maks


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

Bug#393329: After seemingly successful install on Turion X2 system, freeze on boot

[Cesare Leonardi]

Carl Fink wrote:

Removing the second SODIMM from the laptop had no effect, but
removing the first (and swapping the second into slot #1) seems to have
stopped the freezes, at least on ten minutes of work.  So maybe a
combination of kernel and hardware problems?


Since you suspect ram problems, i suggest you to try memtest86 or 
memtest86+ and run one of them as long as you can, to stress your RAM 
and to see if there are any errors. They are not infallible but can 
detect most ram problems.


You can install the debian packages or download the floppy or the iso 
bootable images from their sites:

memtest86:  http://www.memtest86.com
memtest86+: http://www.memtest.org

Good luck.

Cesare.


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

Bug#393773: initramfs-tools: install fails, 'sed: no input files', missing escape in presinst file

[Federico Grau]

Package: initramfs-tools
Version: 0.83
Severity: grave
Justification: renders package unusable

In the config file initramfs-tools.preinst , there is a missing escape 
of the endofline/newline on line 32.

A patch is attached to correct this.

donfede


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15.2-xwing-1
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
--- debian/initramfs-tools.preinst  2006-10-17 14:42:59.0 -0400
+++ debian/initramfs-tools.preinst.org  2006-10-17 14:42:49.0 -0400
@@ -29,7 +29,7 @@
  -e '/# This file should/,/one per line\./d' \
  -e 's/Comments begin with.*/Syntax:  module_name 
[args ...]/' \
  -e 's/^#  ext2$/# raid1/' \
- -e 's/^#  wd io=0x300$/# sd_mod/' \
+ -e 's/^#  wd io=0x300$/# sd_mod/'
  -e '/^ide-generic/d' \
  -e '/^ide-disk/d' \
  -e '/^ext2/d' \

Bug#391706: fixed

[Debian Archive Maintenance]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

kernel-headers-2.4-386 |  101sarge1 | i386
kernel-headers-2.4-586tsc |  101sarge1 | i386
kernel-headers-2.4-686 |  101sarge1 | i386
kernel-headers-2.4-686-smp |  101sarge1 | i386
kernel-headers-2.4-k6 |  101sarge1 | i386
kernel-headers-2.4-k7 |  101sarge1 | i386
kernel-headers-2.4-k7-smp |  101sarge1 | i386
kernel-image-2.4-386 |  101sarge1 | i386
kernel-image-2.4-586tsc |  101sarge1 | i386
kernel-image-2.4-686 |  101sarge1 | i386
kernel-image-2.4-686-smp |  101sarge1 | i386
kernel-image-2.4-k6 |  101sarge1 | i386
kernel-image-2.4-k7 |  101sarge1 | i386
kernel-image-2.4-k7-smp |  101sarge1 | i386
kernel-latest-2.4-i386 |  101sarge1 | source
kernel-pcmcia-modules-2.4-386 |  101sarge1 | i386
kernel-pcmcia-modules-2.4-586tsc |  101sarge1 | i386
kernel-pcmcia-modules-2.4-686 |  101sarge1 | i386
kernel-pcmcia-modules-2.4-686-smp |  101sarge1 | i386
kernel-pcmcia-modules-2.4-k6 |  101sarge1 | i386
kernel-pcmcia-modules-2.4-k7 |  101sarge1 | i386
kernel-pcmcia-modules-2.4-k7-smp |  101sarge1 | i386

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.

Packages are never removed from testing by hand.  Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED]

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[EMAIL PROTECTED]

Debian distribution maintenance software
pp.
Jeroen van Wolffelaar (the ftpmaster behind the curtain)


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

Bug#391712: fixed

[Debian Archive Maintenance]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

kernel-doc-2.4.27 |  2.4.27-12 | all
kernel-patch-debian-2.4.27 |  2.4.27-12 | all
kernel-source-2.4.27 |  2.4.27-12 | source, all
kernel-tree-2.4.27 |  2.4.27-12 | all

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.

Packages are never removed from testing by hand.  Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED]

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[EMAIL PROTECTED]

Debian distribution maintenance software
pp.
Jeroen van Wolffelaar (the ftpmaster behind the curtain)


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

Bug#391707: fixed

[Debian Archive Maintenance]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

kernel-build-2.4.27-2 |  2.4.27-12 | i386
kernel-headers-2.4.27-2 |  2.4.27-12 | i386
kernel-headers-2.4.27-2-386 |  2.4.27-12 | i386
kernel-headers-2.4.27-2-586tsc |  2.4.27-12 | i386
kernel-headers-2.4.27-2-686 |  2.4.27-12 | i386
kernel-headers-2.4.27-2-686-smp |  2.4.27-12 | i386
kernel-headers-2.4.27-2-k6 |  2.4.27-12 | i386
kernel-headers-2.4.27-2-k7 |  2.4.27-12 | i386
kernel-headers-2.4.27-2-k7-smp |  2.4.27-12 | i386
kernel-image-2.4.27-2-386 |  2.4.27-12 | i386
kernel-image-2.4.27-2-586tsc |  2.4.27-12 | i386
kernel-image-2.4.27-2-686 |  2.4.27-12 | i386
kernel-image-2.4.27-2-686-smp |  2.4.27-12 | i386
kernel-image-2.4.27-2-k6 |  2.4.27-12 | i386
kernel-image-2.4.27-2-k7 |  2.4.27-12 | i386
kernel-image-2.4.27-2-k7-smp |  2.4.27-12 | i386
kernel-image-2.4.27-i386 |  2.4.27-12 | source
kernel-pcmcia-modules-2.4.27-2-386 |  2.4.27-12 | i386
kernel-pcmcia-modules-2.4.27-2-586tsc |  2.4.27-12 | i386
kernel-pcmcia-modules-2.4.27-2-686 |  2.4.27-12 | i386
kernel-pcmcia-modules-2.4.27-2-686-smp |  2.4.27-12 | i386
kernel-pcmcia-modules-2.4.27-2-k6 |  2.4.27-12 | i386
kernel-pcmcia-modules-2.4.27-2-k7 |  2.4.27-12 | i386
kernel-pcmcia-modules-2.4.27-2-k7-smp |  2.4.27-12 | i386

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.

Packages are never removed from testing by hand.  Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED]

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[EMAIL PROTECTED]

Debian distribution maintenance software
pp.
Jeroen van Wolffelaar (the ftpmaster behind the curtain)


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

Re: RFC: Possible (partial) solution for device persistence issue

[maximilian attems]

On Tue, Oct 17, 2006 at 04:27:19PM +0200, Geert Stappers wrote:
> Op 16-10-2006 om 00:06 schreef Frans Pop:
> > On Sunday 15 October 2006 23:45, Geert Stappers wrote:
> > > The thing I would like to see is that the _difference_ in device naming
> > > between d-i kernel plus fellows and installed kernel plus fellows is
> > > solved.
> > 
> > See the discussions that we have had about this in the past.
> > The culprit is the kernel/udev: that can load drivers in a different order 
> > any time. It is not something we can solve in the installer.
> > 
> > The experts have said that using UUID is the best solution. I agree that 
> > it is extremely ugly.

it is see very practical, see for example this usage example
http://michael-prokop.at/blog/2006/08/11/stable-root-device-aka-uuid/
 
 
> Dear Kernel developers,
> 
> 
> Your work is appriceated, but I have a request:
> 
> 
>   Please allow reproducable hardware detection.
> 
> 
> As systemadministrator I can't affort having a disk that is one moment
> /dev/sda and the next reboot /dev/sdb.
> 
> Having a fast booting system is great, having disks swapped not.

the kernel _never_ guaranteed stable device nodes,
that is an userspace policy.
use the tools that provide that.

> Please prefer consistence above speed.
> 
> 
> 
> Thank you for reading this humble plea.
> Geert Stappers

edgy udev transforms the fstab to use plain uuids,
to guarantee correct root recognition.
i guess their installer also add uuid entries to the newly
installed fstab - why is that not in d-i?

-- 
maks


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

Bug#393688: initramfs-tools: Needs to create /lib/modules/${version} in initramfs in case no modules are required

[maximilian attems]

tags 393688 pending
stop

On Tue, Oct 17, 2006 at 01:20:53PM +0100, Ian Campbell wrote:
> 
> If your kernel configuration is such that no modules are required in
> the initramfs then /lib/modules/${version}/ is never created and on boot
> you get some noisy message:
>   FATAL: Could not load /lib/modules/${version}/modules.dep: No such file or 
> directory
> (several times)
> 
> This can happen if you are using initramfs only to get early udev etc.
> 
> I've pasted a simple patch below, with the following changelog entry:
> 
>   * mkinitramfs: Ensure that /lib/modules/${version} exists. Otherwise
> if no modules are required a warning is issued at boot.
> 
> Thanks,
> Ian.

thanks, applied.

-- 
maks
 


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

Processed: Re: Bug#393688: initramfs-tools: Needs to create /lib/modules/${version} in initramfs in case no modules are required

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tags 393688 pending
Bug#393688: initramfs-tools: Needs to create /lib/modules/${version} in 
initramfs in case no modules are required
Tags were: patch
Tags added: pending

> stop
Stopping processing here.

Please contact me if you need assistance.

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


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

Bug#386226: same problem with linux-image-2.6.18-1-686-bigmem

[Vincent Lefevre]

I have the same problem with linux-image-2.6.18-1-686-bigmem.
The bug should probably be reassigned to the linux-2.6 source.

-- 
Vincent Lefèvre <[EMAIL PROTECTED]> - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

Re: RFC: Possible (partial) solution for device persistence issue

[Geert Stappers]

Op 16-10-2006 om 00:06 schreef Frans Pop:
> On Sunday 15 October 2006 23:45, Geert Stappers wrote:
> > The thing I would like to see is that the _difference_ in device naming
> > between d-i kernel plus fellows and installed kernel plus fellows is
> > solved.
> 
> See the discussions that we have had about this in the past.
> The culprit is the kernel/udev: that can load drivers in a different order 
> any time. It is not something we can solve in the installer.
> 
> The experts have said that using UUID is the best solution. I agree that 
> it is extremely ugly.


Dear Kernel developers,


Your work is appriceated, but I have a request:


  Please allow reproducable hardware detection.


As systemadministrator I can't affort having a disk that is one moment
/dev/sda and the next reboot /dev/sdb.

Having a fast booting system is great, having disks swapped not.

Please prefer consistence above speed.



Thank you for reading this humble plea.
Geert Stappers


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

Bug#393688: initramfs-tools: Needs to create /lib/modules/${version} in initramfs in case no modules are required

[Ian Campbell]

Package: initramfs-tools
Version: 0.82
Severity: minor
Tags: patch

If your kernel configuration is such that no modules are required in
the initramfs then /lib/modules/${version}/ is never created and on boot
you get some noisy message:
  FATAL: Could not load /lib/modules/${version}/modules.dep: No such file or 
directory
(several times)

This can happen if you are using initramfs only to get early udev etc.

I've pasted a simple patch below, with the following changelog entry:

  * mkinitramfs: Ensure that /lib/modules/${version} exists. Otherwise
if no modules are required a warning is issued at boot.

Thanks,
Ian.

--- initramfs-tools-0.83/mkinitramfs2006-09-27 14:31:49.0 +0100
+++ initramfs-tools-0.84/mkinitramfs2006-10-17 12:45:45.0 +0100
@@ -166,7 +166,7 @@
 # Private, used by 'catenate_cpiogz'.
 export __TMPCPIOGZ
 
-for d in bin conf/conf.d etc lib modules sbin scripts; do
+for d in bin conf/conf.d etc lib modules sbin scripts ${MODULESDIR}; do
mkdir -p "${DESTDIR}/${d}"
 done
 

-- Package-specific info:
-- /proc/cmdline
root=/dev/mapper/Vol00-root ro console=tty0 

-- /proc/filesystems
cramfs
ext3
ext2
msdos
vfat

-- lsmod
Module  Size  Used by
nls_iso8859_1   9856  0 
vfat   18048  0 
nls_cp437  11520  0 
msdos  14336  0 
fat56496  2 vfat,msdos
ext2   70288  0 
loop   20112  0 
binfmt_misc17292  1 
nfs   236216  6 
nfsd  256200  17 
exportfs   10368  1 nfsd
lockd  67600  3 nfs,nfsd
nfs_acl 8320  2 nfs,nfsd
sunrpc166984  13 nfs,nfsd,lockd,nfs_acl
autofs427912  4 
ipv6  285664  30 
ide_disk   20608  0 
tsdev  13056  0 
snd_ens137132192  3 
gameport   21264  1 snd_ens1371
snd_ac97_codec106456  1 snd_ens1371
snd_ac97_bus7296  1 snd_ac97_codec
snd_pcm_oss48672  0 
snd_mixer_oss  21888  1 snd_pcm_oss
snd_pcm89096  4 snd_ens1371,snd_ac97_codec,snd_pcm_oss
snd_seq_dummy   8580  0 
snd_seq_oss37248  0 
snd_seq_midi   13632  0 
snd_rawmidi31392  2 snd_ens1371,snd_seq_midi
snd_seq_midi_event 12544  2 snd_seq_oss,snd_seq_midi
snd_seq59520  6
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer  29192  3 snd_pcm,snd_seq
snd_seq_device 13204  5
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
snd65256  14
snd_ens1371,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
parport_pc 41640  0 
soundcore  15392  1 snd
psmouse44432  0 
i2c_i801   13076  0 
parport44684  1 parport_pc
serio_raw  12036  0 
sky2   45700  0 
intel_agp  29248  1 
snd_page_alloc 14864  1 snd_pcm
i2c_core   27776  1 i2c_i801
evdev  15360  1 
pcspkr  7808  0 
floppy 67112  0 
ext3  138384  9 
jbd65008  1 ext3
mbcache14216  2 ext2,ext3
dm_mirror  25216  0 
dm_snapshot20536  0 
dm_mod 62800  19 dm_mirror,dm_snapshot
ide_generic 5760  0 [permanent]
sd_mod 25856  4 
ide_cd 45088  0 
cdrom  40488  1 ide_cd
ata_piix   19976  3 
ehci_hcd   36104  0 
libata106784  1 ata_piix
scsi_mod  152880  2 sd_mod,libata
uhci_hcd   28432  0 
piix   15492  0 [permanent]
generic10756  0 [permanent]
ide_core  147584  5 ide_disk,ide_generic,ide_cd,piix,generic
thermal20240  0 
processor  38248  1 thermal
fan 9864  0 

-- kernel-img.conf
do_symlinks = yes
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = yes
postinst_hook = /sbin/update-grub
postrm_hook   = /sbin/update-grub


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-1-amd64
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages initramfs-tools depends on:
ii  busybox   1:1.1.3-3  Tiny utilities for small
and embed
ii  cpio  2.6-17 GNU cpio -- a program to
manage ar
ii  klibc-utils   1.4.27-1   small statically-linked
utilities 
ii  module-init-tools 3.2.2-3tools for managing Linux
kernel mo
ii  udev  0.100-2 

Bug#383447: marked as done (ACPI problem, hdb timed out)

[Debian Bug Tracking System]

Your message dated Tue, 17 Oct 2006 13:33:56 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#383447: Fixed
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

--- Begin Message ---

Package: linux-image-2.6.17-2-k7
Version: 2.6.17-6

Hello,
After the last update yesterday of the kernel ( from 2.6.17-1 up to 
2.6.17-2 ) I've get some problems.
After many boots, I'm getting at the point, where the kernel 
initialiazes the HID driver, that my hdb timed out and lost his 
interrupt, then he tried to readdress him an interrupt, but that's not 
working.


--- End Message ---
--- Begin Message ---
On Tuesday 17 October 2006 09:37, Patrick Matthäi wrote:
> Seems as this bug is since the 2.6.18 kernel fixed.
> Bye and thanks.

Let's close it then. Thank you for following up.

Cheers,
FJP


pgp9up88Uu3Fd.pgp
Description: PGP signature
--- End Message ---

Bug#383447: Fixed

[Patrick Matthäi]

Hello,

Seems as this bug is since the 2.6.18 kernel fixed.
Bye and thanks.


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

Re: Kernel width "HIGMEM64G=y" kills my adaptec hw-raid

[Frederik Schueler]

Hello,

On Tue, Oct 17, 2006 at 09:58:16AM +0200, [EMAIL PROTECTED] wrote:
> I think I found a bug in kernel-source-2.6.8-16sarge4. I'm trying to
> compile it width HIGHMEM64G support as I have 12Gbyte RAM. 

2.6.8 is _old_. Can you please give a try to 2.6.17-2-686-bigmem from
backports.org, or 2.6.18-1-686-bigmem from unstable, and see if that 
works for you? 

The -bigmem flavour has PAE activated and supports up to 64G ram.

Best regards
Frederik Schueler

-- 
ENOSIG


signature.asc
Description: Digital signature

Kernel width "HIGMEM64G=y" kills my adaptec hw-raid

[masu]

Hi!

I think I found a bug in kernel-source-2.6.8-16sarge4. I'm trying to
compile it width HIGHMEM64G support as I have 12Gbyte RAM. To compile it I
run:

# make-kpkg clean
# time fakeroot make-kpkg --initrd --append-to-version=kk2 kernel_image
kernel_headers modules_image kernel_source

I install it width dpkg and everything looks fine.
I restart and finds my new kernel in Grub-bootloader

When it get's to the line below it stops:
EXT3-fs: mounted filesystem with ordered data mode.

I wait a minute two and then both my 36Gb scsi-disks starts to indicate
DISK FAILURE. I also get som SCSI-bus reset error. I have a adaptec
raid-controller with a raid-1 setup for the two disks. To get the server
going again I have to unconfigure both disks in the
"adaptec-bios-raid-configuration-tool" and then reconfigure everything and
build a new raid.

The only thing I add to the kernel is the HIGHMEM64G support using "make
menuconfig" If I compile the kernel adding nothing everthing works fine
except for the last 8Gbyte RAM that I'm unable to use.

Here's a diff between the to kernel configs.
m0002:/usr/src/kernel-source-2.6.8# diff .config_working .config
119,120c119,120
< CONFIG_HIGHMEM4G=y
< # CONFIG_HIGHMEM64G is not set
---
> # CONFIG_HIGHMEM4G is not set
> CONFIG_HIGHMEM64G=y
121a122
> CONFIG_X86_PAE=y
1973d1973
< CONFIG_VIDEO_MEYE=m

Am I doing something wrong or have I found a bug?

\\Marcus





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

Processed: Re: Bug#393543: initramfs-tools: wrong mknod call

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tags 393543 pending
Bug#393543: initramfs-tools: wrong mknod call
Tags were: patch
Tags added: pending

> stop
Stopping processing here.

Please contact me if you need assistance.

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


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

Bug#393543: initramfs-tools: wrong mknod call

[maximilian attems]

tags 393543 pending
stop

On Mon, 16 Oct 2006, Kiro Zimmer wrote:

> 
> Hello,
> 
> the file /usr/share/initramfs-tools/scripts/init-top/framebuffer
> contains a wrong call of the (busybox) mknod binary. The trivial
> patch is appended. ;)
> 
> thanks, Kiro

applied, thanks
 
-- 
maks


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