Bug#446724: SAME SITUATION - initramfs-tools: creates broken initramfs image as reported on Bug #445688

2007-10-14 Thread Miguel Martins Feitosa Filho
Package: initramfs-tools
Version: 0.90a
Severity: critical
Justification: breaks the whole system


Hi,

I have the same situation described by Beojan in one of my boxes but
not the other two - all three are debian testing.
His solution - yaird - also worked for me.
Reading the bug report I came about an interesting point in 
that the phrases below do not apply to me as my systems always were/are
debian:

"
i'm sorry but your initramfs-tools is not from debian,
we _never_ shipped with an modprobe -Q argument in those boot scripts.
"

"
>You may wish to know that I switched to Debian from Feisty using
> dist-upgrade, and udev
> didn't get upgraded.
"

A call to 
egrep -r modprobe /usr/share/initramfs-tools/scripts/init-premount/
shows some modprobe commands, all are without options such as:

tatarana:/etc/default# egrep -r modprobe
/usr/share/initramfs-tools/scripts/init-premount/ | head -2
/usr/share/initramfs-tools/scripts/init-premount/ps3:modprobe
ps3_storage
/usr/share/initramfs-tools/scripts/init-premount/ps3:modprobe gelic_net


I run apt-get dist-upgrade regularly on these systems.
Yesterday - oct 14 2007 - I brought all three up to date.
Only one maintained the problem. The other two booted ok with new
2.6.22-2 kernel.
My systems differ only in installed packages and initial install date.
I do not get any deb files outside of apt.
At the end of this message is my sources.list for reference.

My current initramfs is also 0.90a.
tatarana:~# ls /var/cache/apt/archives/ | grep initram
initramfs-tools_0.89_all.deb
initramfs-tools_0.90a_all.deb
initramfs-tools_0.90_all.deb

Since apt installed kernel  2.6.21-2 on my system I get the
"Waiting for root filesystem" at boot time error.

What is amazing is that my other two boxes have also up to date kernels
and
never had this problem.

I initially reported this error as a kernel error but was unable to do a
good follow-up on it. I imagined that as the kernel evolved the problem
would dissapear. Since it did not I resumed trying to figure out the
situation. Beojan's report reproduced my error.

His modprobe -Q explanation though does not seem to apply to my
computer.

I hope a comparision of my three systems will help in finding the cause
of this problem.

Thanks for your help, I am available to supply any necessary
information. 



Miguel

sources.list information
tatarana:~# grep ^deb /etc/apt/sources.list
deb http://http.us.debian.org/debian testing main contrib non-free
deb http://security.debian.org testing/updates main contrib non-free
deb http://http.us.debian.org/debian unstable main contrib non-free
deb http://download.skype.com/linux/repos/debian/ stable non-free
deb http://www.debian-multimedia.org testing main
deb-src http://http.us.debian.org/debian testing main contrib non-free




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

-- /proc/filesystems
cramfs
ext3
fuseblk
vfat

-- lsmod
Module  Size  Used by
tcp_diag1760  0 
inet_diag  11432  1 tcp_diag
nls_iso8859_1   4128  1 
nls_cp437   5792  1 
vfat   12032  1 
fat48540  1 vfat
sd_mod 27136  2 
usb_storage76608  1 
ppdev   8676  0 
lp 10980  0 
thermal13416  0 
fan 4836  0 
button  7920  0 
ac  5188  0 
battery 9988  0 
xt_TCPMSS   4672  1 
xt_tcpmss   2176  1 
xt_tcpudp   3072  8 
xt_state2432  12 
processor  31016  1 thermal
speedstep_lib   5156  0 
cpufreq_ondemand8300  0 
cpufreq_powersave   1792  0 
cpufreq_userspace   4128  0 
cpufreq_stats   5120  0 
freq_table  4512  2 cpufreq_ondemand,cpufreq_stats
cpufreq_conservative 6888  0 
ipt_LOG 5952  0 
iptable_mangle  2784  1 
iptable_filter  2944  1 
iptable_nat 7204  1 
ip_tables  12260  3 iptable_mangle,iptable_filter,iptable_nat
nf_nat 17964  1 iptable_nat
nf_conntrack_ipv4  17772  14 iptable_nat
nf_conntrack   60424  4 xt_state,iptable_nat,nf_nat,nf_conntrack_ipv4
nfnetlink   5752  3 nf_nat,nf_conntrack_ipv4,nf_conntrack
x_tables   14372  7 
xt_TCPMSS,xt_tcpmss,xt_tcpudp,xt_state,ipt_LOG,iptable_nat,ip_tables
pppoe  13184  2 
pppox   3848  1 pppoe
ppp_generic26164  6 pppoe,pppox
slhc5888  1 ppp_generic
ipv6  236964  41 
fuse   41908  1 
dm_snapshot16516  0 
dm_mirror  20928  0 
dm_mod 52160  2 dm_snapshot,dm_mirror
visor  18316  0 
usbserial  31560  1 visor
loop   16932  0 
tsdev   7968  0 
parport_pc 33796  1 
analog

Bug#432971: Similar issue, but solved

2007-07-22 Thread Miguel Martins Feitosa Filho
Guido,
Have not tested 2.6.22 yet, received an updated 2.6.21 with the same
bug.
Is it correct that I must get an experimental kernel package called
Linux 2.6.22-rc5 or compile from source?
Can you give me some pointers here?
Thanks,
Miguel
On Wed, 2007-07-18 at 12:18 +0200, Guido Trotter wrote:
> I had a similar problem for 2.6.20 and 2.6.21, but it was solved for me in
> 2.6.22... Does this work for you too? Can this be closed?
> 
> Guido
> 
> 
> 



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



Bug#432971: linux-image-2.6.21-2-686: Hangs at boot before "Begin: Waiting for root filesystem" message

2007-07-13 Thread Miguel Martins Feitosa Filho
Package: linux-image-2.6.21-2-686
Version: 2.6.21-5
Severity: critical
Justification: breaks the whole system

On boot if kernel 2.6.21-2 is selected either for 486 or 686
architecture than system hangs on 
"Begin: Waiting for root filesystem"
I believe this is right after kernel has inited. Is this correct?

Kernel - 2.6.18 boots normally.

Please suggest some tests so I can bring more specific info to this bug
report.

On boot BIOS says system is an intel
Celeron 1700.
RAM is  753664 bytes + 32768 shared

2 ide hard drives, 1 creative cdr drive
1 AGP video, 1 PCI video

Thank you.
Miguel

Some system related info:

Linux version 2.6.18-4-686 (Debian 2.6.18.dfsg.1-12) ([EMAIL PROTECTED])
(gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Mon
Mar 26 17:17:36 UTC 2007


[EMAIL PROTECTED]:/proc$ cat /etc/fstab 
# /etc/fstab: static file system information.
#
#
proc/proc   procdefaults0   0
/dev/hda1   /   ext3defaults,errors=remount-ro 0
1
/dev/hdd1   /home   ext3defaults0   2
/dev/hda2   noneswapsw  0   0
/dev/hdc/media/cdrom0   udf,iso9660 user,noauto 0   0
/dev/fd0/media/floppy0  autorw,user,noauto  0   0


[EMAIL PROTECTED]:/proc$ cat meminfo 
MemTotal:   744104 kB
MemFree:475840 kB
Buffers: 12908 kB
Cached: 138108 kB
SwapCached:  0 kB
Active: 175276 kB
Inactive:73692 kB
HighTotal:   0 kB
HighFree:0 kB
LowTotal:   744104 kB
LowFree:475840 kB
SwapTotal: 1477972 kB
SwapFree:  1477972 kB
Dirty:  96 kB
Writeback:   0 kB
AnonPages:   97956 kB
Mapped:  42280 kB
Slab:11780 kB
PageTables:   1692 kB
NFS_Unstable:0 kB
Bounce:  0 kB
CommitLimit:   1850024 kB
Committed_AS:   306048 kB
VmallocTotal:   278520 kB
VmallocUsed:  3472 kB
VmallocChunk:   275016 kB



[EMAIL PROTECTED]:~$ cat /proc/ide/drivers 
ide-disk version 1.18
ide-cdrom version 4.61

[EMAIL PROTECTED]:/proc$ cat cpuinfo 
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 15
model   : 1
model name  : Intel(R) Celeron(R) CPU 1.70GHz
stepping: 3
cpu MHz : 1715.319
cache size  : 128 KB
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 2
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm up
bogomips: 3433.92



[EMAIL PROTECTED]:~$ lspci 
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 650/M650 Host (rev
01)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI
bridge (AGP)
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS961 [MuTIOL
Media IO] (rev 10)
00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus
Controller
00:02.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.0
Controller (rev 07)
00:02.3 USB Controller: Silicon Integrated Systems [SiS] USB 1.0
Controller (rev 07)
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev
d0)
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS]
AC'97 Sound Controller (rev a0)
00:03.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI
Fast Ethernet (rev 90)
00:0e.0 Ethernet controller: Davicom Semiconductor, Inc. 21x4x DEC-Tulip
compatible 10/100 Ethernet (rev 31)
00:0f.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 MX
420] (rev a3)
00:10.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS]
65x/M650/740 PCI/AGP VGA Display Adapter


-- Package-specific info:

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (700, 'testing'), (650, 'unstable')
Architecture: i386 (i686)

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

Versions of packages linux-image-2.6.21-2-686 depends on:
ii  initramfs-tools [linux-initr 0.88tools for generating an initramfs
ii  module-init-tools3.3-pre11-1 tools for managing Linux kernel mo

Versions of packages linux-image-2.6.21-2-686 recommends:
ii  libc6-i6862.5-9+b1   GNU C Library: Shared libraries [i

-- debconf-show failed


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



Bug#432716: exim4-config: Exim4 4.67-5 does not honor dc_hide_mailname='true' setting

2007-07-12 Thread Miguel Martins Feitosa Filho
I think it is ok to commit.
I will dist-update my system and send feedback if all is not ok.
MIguel
On Thu, 2007-07-12 at 19:41 +0200, Marc Haber wrote:
> On Thu, Jul 12, 2007 at 12:52:11PM -0400, Miguel Martins Feitosa Filho wrote:
> > Works now...thank you.
> 
> You're welcome. So I can commit to svn without doing more
> comprehensive testin?
> 
> > The macro language used to generate the config file has a pretty tough
> > syntax
> 
> Yes, the prefix stuff is pretty bad.
> 
> > The log shows the origianl mailname but the email domains are being
> > rewritten and the emails relayed:
> > 
> > 2007-07-12 12:48:21 1I91q1-0006i2-D6 <= [EMAIL PROTECTED] U=mirian P=local
> > S=338
> > 2007-07-12 12:48:22 1I91q1-0006i2-D6 => [EMAIL PROTECTED] R=smarthost
> > T=remote_smtp_smarthost H=vip-test03.terra.com.br [200.154.55.12] 
> > 2007-07-12 12:48:22 1I91q1-0006i2-D6 Completed
> 
> exim does not log rewrites by default.
> 
> Greetings
> Marc
> 



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



Bug#432716: exim4-config: Exim4 4.67-5 does not honor dc_hide_mailname='true' setting

2007-07-12 Thread Miguel Martins Feitosa Filho
Hi Marc,

Works now...thank you.
The macro language used to generate the config file has a pretty tough
syntax
Thanks again for your prompt response...
The log shows the origianl mailname but the email domains are being
rewritten and the emails relayed:

2007-07-12 12:48:21 1I91q1-0006i2-D6 <= [EMAIL PROTECTED] U=mirian P=local
S=338
2007-07-12 12:48:22 1I91q1-0006i2-D6 => [EMAIL PROTECTED] R=smarthost
T=remote_smtp_smarthost H=vip-test03.terra.com.br [200.154.55.12] 
2007-07-12 12:48:22 1I91q1-0006i2-D6 Completed

Miguel

On Thu, 2007-07-12 at 17:26 +0200, Marc Haber wrote:
> On Thu, Jul 12, 2007 at 10:32:03AM -0400, Miguel Martins Feitosa Filho wrote:
> > added the lines sent after 
> > # This transport is used for smarthost and satellite configurations.
> > comment in template file
> > 
> > exim accepts config changes...
> > 
> > I get 
> > 2007-07-12 10:27:52 1I8ze4-0005SR-Qm <= [EMAIL PROTECTED] U=mirian P=local
> > S=335
> > 2007-07-12 10:27:52 1I8ze4-0005SR-Qm == [EMAIL PROTECTED] R=smarthost
> > T=remote_smtp_smarthost defer (-1): Failed to expand return path "${if
> > [EMAIL PROTECTED] match_domain{$sender_address_domain}{'"$mailname"'[EMAIL 
> > PROTECTED]": unknown variable name "mailname"
> > 
> > in the log...
> > 
> > 
> > Could it be that I inserted lines in incorrect position in the file?
> 
> No, it is just more stupidity on my part.
> 
> .ifdef HIDE_MAILNAME
> [EMAIL PROTECTED] [EMAIL PROTECTED] frs : [EMAIL PROTECTED] [EMAIL PROTECTED] 
> frs
> REMOTE_SMTP_RETURN_PATH=${if [EMAIL PROTECTED] [EMAIL PROTECTED]
> .endif
> 
> I still didn't try this, but will actually do so tonight. If you're
> faster than me, your help is appreciated.
> 
> Greetings
> Marc
> 



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



Bug#432716: exim4-config: Exim4 4.67-5 does not honor dc_hide_mailname='true' setting

2007-07-12 Thread Miguel Martins Feitosa Filho
Hi,

added the lines sent after 
# This transport is used for smarthost and satellite configurations.
comment in template file

exim accepts config changes...

I get 
2007-07-12 10:27:52 1I8ze4-0005SR-Qm <= [EMAIL PROTECTED] U=mirian P=local
S=335
2007-07-12 10:27:52 1I8ze4-0005SR-Qm == [EMAIL PROTECTED] R=smarthost
T=remote_smtp_smarthost defer (-1): Failed to expand return path "${if
[EMAIL PROTECTED] match_domain{$sender_address_domain}{'"$mailname"'[EMAIL 
PROTECTED]": unknown variable name "mailname"

in the log...


Could it be that I inserted lines in incorrect position in the file?

Thanks,
Miguel Feitosa

On Thu, 2007-07-12 at 07:53 +0200, Marc Haber wrote:
> On Wed, Jul 11, 2007 at 10:21:34PM +0200, Marc Haber wrote:
> > Try adding this:
> > .ifdef HIDE_MAILNAME
> > REMOTE_SMTP_HEADERS_REWRITE=headers_rewrite = [EMAIL PROTECTED] [EMAIL 
> > PROTECTED] frs : *@'"$mailname"' [EMAIL PROTECTED] frs
> > REMOTE_SMTP_RETURN_PATH=return_path = ${if [EMAIL PROTECTED] 
> > match_domain{$sender_address_domain}{'"$mailname"'[EMAIL PROTECTED]
> > .endif
> > 
> > right before your remote_smtp_smarthost router in
> > /etc/exim4/exim4.conf.template and restart exim. Please report back if
> > this fixes things for you.
> 
> Idiot me. The correct lines are of course
> 
> .ifdef HIDE_MAILNAME
> [EMAIL PROTECTED] [EMAIL PROTECTED] frs : *@'"$mailname"' [EMAIL PROTECTED] 
> frs
> REMOTE_SMTP_RETURN_PATH=${if [EMAIL PROTECTED] 
> match_domain{$sender_address_domain}{'"$mailname"'[EMAIL PROTECTED]
> .endif
> 
> Try again please and report back.
> 
> Please always reply to the BTS as well so that the bug trail is
> completely visible.
> 
> Greetings
> Marc
> 



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



Bug#432716: exim4-config: Exim4 4.67-5 does not honor dc_hide_mailname='true' setting

2007-07-12 Thread Miguel Martins Feitosa Filho
Hi,

added the lines sent after 
# This transport is used for smarthost and satellite configurations.
comment in template file

exim accepts config changes...

I get 
2007-07-12 10:27:52 1I8ze4-0005SR-Qm <= [EMAIL PROTECTED] U=mirian P=local
S=335
2007-07-12 10:27:52 1I8ze4-0005SR-Qm == [EMAIL PROTECTED] R=smarthost
T=remote_smtp_smarthost defer (-1): Failed to expand return path "${if
[EMAIL PROTECTED] match_domain{$sender_address_domain}{'"$mailname"'[EMAIL 
PROTECTED]": unknown variable name "mailname"

in the log...


Could it be that I inserted lines in incorrect position in the file?

Thanks,
Miguel Feitosa

On Thu, 2007-07-12 at 07:53 +0200, Marc Haber wrote:
> On Wed, Jul 11, 2007 at 10:21:34PM +0200, Marc Haber wrote:
> > Try adding this:
> > .ifdef HIDE_MAILNAME
> > REMOTE_SMTP_HEADERS_REWRITE=headers_rewrite = [EMAIL PROTECTED] [EMAIL 
> > PROTECTED] frs : *@'"$mailname"' [EMAIL PROTECTED] frs
> > REMOTE_SMTP_RETURN_PATH=return_path = ${if [EMAIL PROTECTED] 
> > match_domain{$sender_address_domain}{'"$mailname"'[EMAIL PROTECTED]
> > .endif
> > 
> > right before your remote_smtp_smarthost router in
> > /etc/exim4/exim4.conf.template and restart exim. Please report back if
> > this fixes things for you.
> 
> Idiot me. The correct lines are of course
> 
> .ifdef HIDE_MAILNAME
> [EMAIL PROTECTED] [EMAIL PROTECTED] frs : *@'"$mailname"' [EMAIL PROTECTED] 
> frs
> REMOTE_SMTP_RETURN_PATH=${if [EMAIL PROTECTED] 
> match_domain{$sender_address_domain}{'"$mailname"'[EMAIL PROTECTED]
> .endif
> 
> Try again please and report back.
> 
> Please always reply to the BTS as well so that the bug trail is
> completely visible.
> 
> Greetings
> Marc
> 



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