Bug#762984: Alert! /dev/vg0/usr does not exist

[Javier Barroso]

Hello Simon, (I'm dropping CCs, I'm not sure if all body is ok with
maintaining such CC list, sorry if somebody have would like to be in
CC)

On Thu, Nov 27, 2014 at 12:51 PM, Simon McVittie  wrote:
> On Wed, 01 Oct 2014 at 22:18:53 +0100, Ben Hutchings wrote:
>> I suspect this is essentially the same bug as #616689 and #678696,
>> except that now it may affect mounting /usr as well as /.
>
> I think this bug report is actually describing more than one bug in more
> than one package that have similar symptoms. There might be things
> that can be fixed in mdadm and lvm2 to fix the initramfs-tools/0.117
> regressions without needing to implement a full event-driven setup in
> initramfs-tools.
>
>  RAID (Elimar, Sven) 
>
> Elimar Riesebieter's "System 2" has a bunch of mdadm (RAID) partitions.
>
> Elimar, what is in your /etc/default/mdadm on "System 2" (and "System 1"
> for that matter)? I predict that the answer includes something like
> "INITRDSTART=/dev/md6".
>
> The problem here seems to be that mdadm tries to determine a minimal
> set of multi-disk partitions need to be assembled by the initramfs
> based on the assumption that the initramfs only needs the root device;
> but initramfs-tools >= 0.117 wants to mount /usr as well, so that
> assumption is no longer true.
>
> So it might be necessary to modify mdadm so that, if /usr is a separate
> filesystem on (a LVM VG on) a MD array, it will try to prepare that too.
>
>  LVM (Elimar's "System 1", Sven, Torsten, IOhannes, Javier) 
>
> In the LVM case, debian/initramfs-tools/lvm2/scripts/local-top
> does this:
>
> activate_vg "$ROOT"
> activate_vg "$resume"
>
> Note the lack of handling for /usr here.
>
> Further, activate_vg uses "lvm lvchange" to activate only the LV
> necessary for the root filesystem; if /usr is on a separate VG,
> it's not going to work.
>
> This on its own would be enough to make Sven Hartge's system fail:
> /usr needs a LVM partition activated that / does not. Similarly,
> I think Elimar's "System 1" is going to activate vg0/root but not
> vg0/usr.
>
> We don't have enough information in this bug report to know what
> layout Torsten, IOhannes, Javier used on their systems, but we can
> guess from the fact that "vgchange -a y" is a successful workaround...
> I predict that these are LVM over either a single RAID array, or
> real partitions.

My partition layout is:

javi@Doraemon:~$ lsblk
NAME  MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda 8:00 238,5G  0 disk
├─sda1  8:10   243M  0 part /boot
├─sda2  8:20 1K  0 part
└─sda5  8:50 238,2G  0 part
  ├─doraemon-root 254:00  13,4G  0 lvm  /
  ├─doraemon-swap 254:10   3,7G  0 lvm  [SWAP]
  ├─doraemon-var  254:20  11,3G  0 lvm  /var
  ├─doraemon-tmp  254:30   4,7G  0 lvm  /tmp
  ├─doraemon-opt  254:40   9,3G  0 lvm  /opt
  └─doraemon-home 254:50  65,2G  0 lvm  /home

$ sudo lshw -c disk
  *-disk
   description: ATA Disk
   product: C400-MTFDDAK256M
   physical id: 0.0.0
   bus info: scsi@0:0.0.0
   logical name: /dev/sda
   version: 0G09
   serial: 12440352D97A
   size: 238GiB (256GB)
   capabilities: partitioned partitioned:dos
   configuration: ansiversion=5 logicalsectorsize=512
sectorsize=512 signature=573692f2

Before this bug, i have too /usr ( doraemon-usr logical volume)
splited. I moved /usr into / after Ben suggested at a comment in this
bug.

The same happened in another computer which had the same partition layout

Thank you very much


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAL5yMZSocBOsio6g70S4h2k=RxmyF5Xs=jeipk-icfr5oc8...@mail.gmail.com

Bug#770394: initramfs-tools: Sorting rc versions

[Javier Barroso]

Control: tags -1 patch

On Thu, 20 Nov 2014 23:43:59 + Ben Hutchings  wrote:
> Control: severity -1 normal
>
> On Thu, 2014-11-20 at 23:47 +0100, Javier Barroso wrote:
> > Package: initramfs-tools
> > Version: 0.118
> > Severity: wishlist
> >
> > Dear Maintainer,
> >
> >
> >* What led up to the situation?
> > Running update-initramfs -u did not choose the latest installed kernel
> > version.
> >
> > dpkg --compare-versions doesn't play well with current kernel version
> > scheme
> >
> >* What exactly did you do (or not do) that was effective (or
> >  ineffective)?
> > Run update-initramfs -u
> >
> >* What was the outcome of this action?
> > update-initramfs chose 3.16-rc5-amd64
> >
> >* What outcome did you expect instead?
> > update-initramfs would chosen 3.16-3-amd64 version
> >
> > I'm attaching a possible patch. Maybe changing version scheme to -0-rc
> > would be more dpkg compatible behaviour, so this patch is not needed.
> >
> > I don't think that teaching dpkg --compare-version about this issue is a
> > better solution. (I think dpkg maintainers would complaint about)
> [...]
>
> It should really use the linux-version command from linux-base.  Thanks
> for pointing this out.
I didn't know about linux-version tool, the patch is even more simple
then. I'm attaching the new version.

Thank you very much
--- update-initramfs.orig	2014-11-21 19:30:46.984389934 +0100
+++ update-initramfs	2014-11-21 22:47:39.86974 +0100
@@ -228,27 +228,8 @@
 
 get_sorted_versions()
 {
-	version_list=""
 
-	for gsv_x in "${STATEDIR}"/*; do
-		gsv_x="$(basename "${gsv_x}")"
-		if [ "${gsv_x}" = '*' ]; then
-			return 0
-		fi
-		worklist=""
-		for gsv_i in $version_list; do
-			if dpkg --compare-versions "${gsv_x}" '>' "${gsv_i}" 2>/dev/null; then
-worklist="${worklist} ${gsv_x} ${gsv_i}"
-gsv_x=""
-			else
-worklist="${worklist} ${gsv_i}"
-			fi
-		done
-		if [ "${gsv_x}" != "" ]; then
-			worklist="${worklist} ${gsv_x}"
-		fi
-		version_list="${worklist}"
-	done
+	version_list="$(linux-version sort --reverse $(linux-version list))"
 
 	verbose "Available versions: ${version_list}"
 }

Bug#770394: initramfs-tools: Sorting rc versions

[Javier Barroso]

Package: initramfs-tools
Version: 0.118
Severity: wishlist

Dear Maintainer,


   * What led up to the situation?
Running update-initramfs -u did not choose the latest installed kernel
version.

dpkg --compare-versions doesn't play well with current kernel version
scheme

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Run update-initramfs -u

   * What was the outcome of this action?
update-initramfs chose 3.16-rc5-amd64

   * What outcome did you expect instead?
update-initramfs would chosen 3.16-3-amd64 version

I'm attaching a possible patch. Maybe changing version scheme to -0-rc
would be more dpkg compatible behaviour, so this patch is not needed.

I don't think that teaching dpkg --compare-version about this issue is a
better solution. (I think dpkg maintainers would complaint about)

Thank you

-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 16M Nov 20 23:23 /boot/initrd.img-3.16-2-amd64
-rw-r--r-- 1 root root 16M Nov 20 23:22 /boot/initrd.img-3.16-3-amd64
-rw-r--r-- 1 root root 15M Nov 20 23:23 /boot/initrd.img-3.16-rc5-amd64
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.16-3-amd64 root=/dev/mapper/fideo--vg-root ro
quiet i8042.notimeout i8042.nomux

-- resume
RESUME=/dev/mapper/fideo--vg-swap_1
-- /proc/filesystems
ext3
ext2
ext4
fuseblk
vfat

-- lsmod
Module  Size  Used by
ctr12927  2
ccm17577  2
bnep   17431  2
binfmt_misc16949  1
nfsd  263053  2
auth_rpcgss51240  1 nfsd
oid_registry   12419  1 auth_rpcgss
nfs_acl12511  1 nfsd
nfs   188053  0
lockd  83417  2 nfs,nfsd
fscache45542  1 nfs
sunrpc237445  6 nfs,nfsd,auth_rpcgss,lockd,nfs_acl
nls_utf8   12456  1
nls_cp437  16553  1
vfat   17135  1
fat61986  1 vfat

x86_pkg_temp_thermal12951  0
intel_powerclamp   17159  0
intel_rapl 17356  0
ecb12737  1
btusb  29721  0
uvcvideo   79005  0
coretemp   12820  0
kvm_intel 139077  0
videobuf2_vmalloc  12816  1 uvcvideo
bluetooth 374429  21 bnep,btusb
kvm   388597  1 kvm_intel
joydev 17063  0
arc4   12536  2
videobuf2_memops   12519  1 videobuf2_vmalloc
videobuf2_core 47787  1 uvcvideo
v4l2_common12995  1 videobuf2_core
videodev  126451  3 uvcvideo,v4l2_common,videobuf2_core
media  18305  2 uvcvideo,videodev
crc32_pclmul   12915  0
6lowpan_iphc   16588  1 bluetooth
iwldvm135156  0
mac80211  474202  1 iwldvm
iwlwifi92451  1 iwldvm
cfg80211  405538  3 iwlwifi,mac80211,iwldvm
rfkill 18867  4 cfg80211,bluetooth
ghash_clmulni_intel12978  0
iTCO_wdt   12831  0
iTCO_vendor_support12649  1 iTCO_wdt
psmouse98616  0
evdev  17445  16
tpm_tis17182  0
serio_raw  12849  0
i915  837133  3
snd_hda_codec_hdmi 45118  1
snd_hda_codec_realtek63031  1
tpm31511  1 tpm_tis
efi_pstore 12805  1
cryptd 14516  1 ghash_clmulni_intel
efivars17257  1 efi_pstore
pcspkr 12595  0
snd_hda_codec_generic63107  1 snd_hda_codec_realtek
fujitsu_laptop 17705  0
snd_hda_intel  26327  6
i2c_i801   16965  0
snd_hda_controller 26727  1 snd_hda_intel
snd_hda_codec 104463  5
snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller
mei_me 17941  0
snd_hwdep  13148  1 snd_hda_codec
snd_pcm88662  4
snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller
video  18030  1 i915
drm_kms_helper 49210  1 i915
drm   249955  5 i915,drm_kms_helper
i2c_algo_bit   12751  1 i915
snd_timer  26614  1 snd_pcm
button 12944  1 i915
snd65244  20
snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
soundcore  13026  2 snd,snd_hda_codec
i2c_core   46012  7
drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,v4l2_common,videodev
lpc_ich20768  0
battery13356  0
shpchp 31121  0
processor  28221  0
mei74977  1 mei_me
ac 12715  0
mfd_core   12601  1 lpc_ich
fuse   83350  3
autofs435529  2
ext4  469572  5
crc16  12343  2 ext4,bluetooth
mbcache17171  1 ext4
jbd2  

Bug#762984: initramfs-tools: Alert! /dev/vg0/usr does not exist

[Javier Barroso]

Hello,
On Tue, 07 Oct 2014 12:07:48 +0200
=?UTF-8?B?IklPaGFubmVzIG0gem3DtmxuaWcgKERlYmlhbi9HTlUpIg==?=
  wrote:
> On 10/07/2014 11:59 AM, IOhannes m zmoelnig wrote:
> > i am hit by the same problem.
> > as a temporary fix, i added the 'vgchange -ay' to
> >   /usr/share/initramfs-tools/scripts/local-top/lvm2
> > as adding it to
> >   /etc/initramfs-tools/scripts/local-top/vgscan
> > somehow did not work (most likely due wrong order of execution, but i did 
> > not
> > investigate further)
>
> i turned out that i had forgotten to set +x permissions for
> /etc/initramfs-tools/scripts/local-top/vgscan

Is there any reference about why this change is not made ?

All my debian systems with separated /usr are not booting until they
are fixed with "vgchange -ay". I don't like such manually changes.

Having a Debian Installation which not boot is a hurt for Debian (I'm
sure many people discard Debian when it doesn't boot, all Debian Sid
Users wait their boot problems solved upgrading its systems the next
week, having a updated Debian Sid two months without booting , is a
not go).

Should Debian Users discard /usr and merge into / ? Is this bug left
open with such idea at mind?

Where is the danger of such fix ? Do you know which would be the
perfect solution?

Thank you very much and sorry for my english


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cal5ymzszqq507hkokxu1zftwjpah5vb5_pcmokj23jzd9ea...@mail.gmail.com

Bug#717805: Adding an advice about lsinitramfs is not working when hit this bug ?

[Javier Barroso]

Hello,

While the patch at 22 comment in this bug [1] is not accepted (can you
clarify why it is not accepted or applied?), I suggest adding an
advice to script.

Next patch could be useful for some of Debian Users:
--- lsinitramfs.orig2014-03-25 21:55:07.704334678 +0100
+++ lsinitramfs2014-03-25 23:08:06.132850281 +0100
@@ -54,7 +54,9 @@
 bzip2 -c -d "$initramfs" | cpio ${cpio_args}
 elif lzop -t "$initramfs" >/dev/null 2>&1 ; then
 lzop -c -d "$initramfs" | cpio ${cpio_args}
+elif file "$initramfs" | grep -q "cpio archive" ; then
+echo "This tool is not ready for not compressed initramfs
files." >&2
+echo "See http://bugs.debian.org/717805 for more info"
 fi
-
 fi
 done

Thank you very much
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717805#22


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAL5yMZTGg68=hhumbpjhtjkosvnqvy_-qpcg5zhzqxctlb8...@mail.gmail.com

Bug#706991: Can be ibmvfc support added ?

[Javier Barroso]

package: linux-image-powerpc
version: 3.2+46

Hello,

I'm trying to install Debian 7 (Wheezy) in a Power 775 from IBM [1]

Debian Installer see correctly the CD and boot, but it doesn't detect
discs which are being presented via NVPI [2]

I suppose installer need to load ibmvfc module, but I think it is not
present / supported

If it is not possible, I would like to know if there are known
problems with that module. I suppose the not support is intentional,
but I cannot find any reference.

Thank you very much

[1] http://www-03.ibm.com/systems/power/hardware/775/
[2] http://en.wikipedia.org/wiki/NPIV


-- 
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/cal5ymzqyu+sv_7wl9z_e37px81byyde1ffe2oehce8ertnx...@mail.gmail.com

Bug#687478: It happens too with 3.2.0-2 version

[Javier Barroso]

This morning it happened to me in 3.2.0-2 (from
linux-image-3.2.0-2-amd64_3.2.20-1_amd64.deb , I think). Before I
always fix this issue rebooting with this kernel. Well, I will unplug
/ plug until it is fixed in sid

Thanks


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cal5ymzq7+2px6if9jpanopvl5taxuiwyrvu-3wvn1d3j8-q...@mail.gmail.com

Bug#687478: linux-image-3.2.0-3-amd64: Xorg (at least gdm) doesn't detect keyboard and mouse

[Javier Barroso]

Package: src:linux
Version: 3.2.23-1
Severity: normal

Dear Maintainer,

Booting with 3.2.0-2-amd64 version keyboard and mouse are detected by Xorg.

Booting with 3.2.0-3-amd64 version keyboard and mouse are NOT detected
by Xorg. I have to unplug and plug both devices to Xorg detect it.

Dmesg when I attach keyboard / mouse is:

[  577.46] usb 3-1: USB disconnect, device number 2
[  578.480032] usb 3-1: new low-speed USB device number 4 using uhci_hcd
[  578.654419] usb 3-1: New USB device found, idVendor=413c, idProduct=3012
[  578.654424] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  578.654428] usb 3-1: Product: Dell USB Optical Mouse
[  578.654431] usb 3-1: Manufacturer: Dell
[  578.670685] input: Dell Dell USB Optical Mouse as
/devices/pci:00/:00:1a.0/usb3/3-1/3-1:1.0/input/input10
[  578.670851] generic-usb 0003:413C:3012.0003: input,hidraw0: USB HID
v1.11 Mouse [Dell Dell USB Optical Mouse] on usb-:00:1a.0-1/input0
[  591.880049] usb 3-2: USB disconnect, device number 3
[  593.856027] usb 3-2: new low-speed USB device number 5 using uhci_hcd
[  594.030434] usb 3-2: New USB device found, idVendor=03f0, idProduct=0024
[  594.030439] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  594.030443] usb 3-2: Product: HP Basic USB Keyboard
[  594.030446] usb 3-2: Manufacturer: CHICONY
[  594.048794] input: CHICONY HP Basic USB Keyboard as
/devices/pci:00/:00:1a.0/usb3/3-2/3-2:1.0/input/input11
[  594.048998] generic-usb 0003:03F0:0024.0004: input,hidraw1: USB HID
v1.10 Keyboard [CHICONY HP Basic USB Keyboard] on
usb-:00:1a.0-2/input0

Thank you very much
-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: Hewlett-Packard
product_name: HP Compaq dc7700p Ultra-slim Desktop
product_version:
chassis_vendor: Hewlett-Packard
chassis_version:
bios_vendor: Hewlett-Packard
bios_version: 786E1 v02.09
board_vendor: Hewlett-Packard
board_name: 0A5Ch
board_version:

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 82Q963/Q965 Memory
Controller Hub [8086:2990] (rev 02)
Subsystem: Hewlett-Packard Company Device [103c:2803]
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: agpgart-intel

00:02.0 VGA compatible controller [0300]: Intel Corporation
82Q963/Q965 Integrated Graphics Controller [8086:2992] (rev 02)
(prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Device [103c:2803]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
SERR-  [disabled]
Capabilities: 
Kernel driver in use: i915

00:03.0 Communication controller [0780]: Intel Corporation 82Q963/Q965
HECI Controller [8086:2994] (rev 02)
Subsystem: Hewlett-Packard Company Device [103c:2803]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
SERR- 

00:03.2 IDE interface [0101]: Intel Corporation 82Q963/Q965 PT IDER
Controller [8086:2996] (rev 02) (prog-if 85 [Master SecO PriO])
Subsystem: Hewlett-Packard Company Device [103c:2803]
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: ata_generic

00:03.3 Serial controller [0700]: Intel Corporation 82Q963/Q965 KT
Controller [8086:2997] (rev 02) (prog-if 02 [16550])
Subsystem: Hewlett-Packard Company Device [103c:2803]
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: serial

00:19.0 Ethernet controller [0200]: Intel Corporation 82566DM Gigabit
Network Connection [8086:104a] (rev 02)
Subsystem: Hewlett-Packard Company Device [103c:2800]
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: e1000e

00:1a.0 USB controller [0c03]: Intel Corporation 82801H (ICH8 Family)
USB UHCI Controller #4 [8086:2834] (rev 02) (prog-if 00 [UHCI])
Subsystem: Hewlett-Packard Company Device [103c:2803]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
SERR- TAbort-
SERR- TAbort-
SERR- 
Kernel driver in use: ehci_hcd

00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8

Bug#655621: linux-image-3.1.0-1-amd64: ALT - ALT GR -2 and others are not recognized in toshiba Satellite Pro L300 keyboard

[Javier Barroso]

On Fri, Jan 13, 2012 at 5:57 AM, Ben Hutchings  wrote:

> On Thu, 2012-01-12 at 21:08 +0100, Javier Barroso wrote:
> > Package: linux-2.6
> >  Version: 3.1.8-2
> >  Severity: normal
> >
> >  Hi,
> >
> >  showkey nor xev show nothing when I type "ALT - ALT GR - 2" (and
> > nothing too
> >  with "ALT - ALT GR - 1"), I would like to
> >  use complete-hostname bash functionality with the default key combo.
> > "ALT - ALT
> >  GR - 3" is working
> >
> >  I'm attaching image from my keys because this behaviour could be
> > caused by
> >  extra function associated to that keys (it is like magnifiers keys).
> > I'm attaching too showkey output when I type "ALT-ALT GR - 3" and then
> > try "ALT-ALT GR -2"
> >
> >  Please reassign this bug to other package if this issue is not
> > directly
> >  related to kernel
> [...]
>
> It probably does need to be fixed in the kernel.  If these
> key-combinations are special then I would expect the toshiba_acpi driver
> should probably handle them.  However, the driver hasn't been loaded on
> your system, and since this model appears to be a few years old I
> suspect this is not just a case of adding a new device ID to the driver
> - there is probably some protocol difference.
>
> You could try running 'acpi_listen' (as root) and then pressing those
> keys to see whether it reports any events.  However, I don't know
> whether acpi_listen will receive any events that are not recognised by
> the kernel.
>
Hi

I'm not sure, if you are not ok with CC, please tell me

Thank you very much, acpi_listen didn't help, and module won't load in my
computer:

insmod
/lib/modules/3.1.0-1-amd64/kernel/drivers/platform/x86/toshiba_acpi.ko
insmod: error inserting
'/lib/modules/3.1.0-1-amd64/kernel/drivers/platform/x86/toshiba_acpi.ko':
-1 No such device

But I discover keymaps udev rules, though there is not one for my laptop:
/lib/udev/keymaps/toshiba-satellite_a110
/lib/udev/keymaps/toshiba-satellite_m30x
/lib/udev/keymaps/toshiba-satellite_a100

Maybe I need to load a different keymap ... but I have to investigate how
udev does that ...

Thank you again.

Regards,

Bug#655621:

[Javier Barroso]

retitle 655621 linux-image-3.1.0-1-amd64: ALT - ALT GR - 2 and others
are not recognized in toshiba Satellite Pro L300 keyboard

# Sorry sending empty subject to this bug :(



-- 
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/CAL5yMZScJJn_EKrprcCyHjY9+uBoZuCHP=u0yzr8dppmonq...@mail.gmail.com

Bug#594986: Re: Bug#594986: xen-linux-system-2.6.32-5-xen-686: Can't find hypervisor information in sysfs!

[Javier Barroso]

On -10/01/37 20:59, Bastian Blank wrote:

On Tue, Aug 31, 2010 at 10:45:22AM +0200, Javier Barroso wrote:
   

"
 

[0.00] Booting paravirtualized kernel on bare hardware
   

The kernel does not run on Xen. Closing as user error.
"
This is the same message which appear in my machine in syslog (I'm attaching 
dmesg output).
 

So you are not running on Xen.
   

Sorry my dmesg was produced by a working xen.
   

Maybe dropping a note in /usr/share/doc/xen*/README.Debian would be a good idea 
about how to solve this issue.
 

Which problem? That you can't read what Grub wants to tell you?
   

Grub should be configured to boot with the xen working configuration.

In my system:
### BEGIN /etc/grub.d/10_linux ### ##
# THIS ENTRY WILL NOT WORK ( "Booting paravirtualized kernel on bare 
hardware" message)
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-686' --class debian 
--class gnu-linux --class gnu --class os {

insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 
65ff51e3-bf08-4565-b0de-7f168c0e7602

echo'Loading Linux 2.6.32-5-xen-686 ...'
linux   /vmlinuz-2.6.32-5-xen-686 
root=/dev/mapper/isofuture-root ro

echo'Loading initial ramdisk ...'
initrd  /initrd.img-2.6.32-5-xen-686
}
...

### BEGIN /etc/grub.d/20_linux_xen ###
# THIS ENTRY WILL WORK
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-686 and XEN 
4.0-i386' --class debian --class gnu-linux --class gnu --class os 
--class xen {

insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 
65ff51e3-bf08-4565-b0de-7f168c0e7602

echo'Loading Linux 2.6.32-5-xen-686 ...'
multiboot   /xen-4.0-i386.gz placeholder
module  /vmlinuz-2.6.32-5-xen-686 placeholder 
root=/dev/mapper/isofuture-root ro

echo'Loading initial ramdisk ...'
module  /initrd.img-2.6.32-5-xen-686
}

So, is this a grub bug ?

   

First entry (default entry) will give me this message error. But if I boot with 
third entry (which talk about booting xen kernel and 4.0 xen flavour) then xm 
commands start working, but the same message (Booting paravirtualized kernel on 
bare hardware) is shown too in dmesg.
 

No, it looks more like this in the correct case.
| [0.00] Booting paravirtualized kernel on Xen
| [0.00] Xen version: 4.0.1-rc3 (preserve-AD) (dom0)
   

Sorry about reporting with not appropiate dmesg (I sent an older dmesg)





--
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/4c7cd0e2.6070...@isotrol.com

Bug#594986: xen-linux-system-2.6.32-5-xen-686: Can't find hypervisor information in sysfs!

[Javier Barroso]

Package: xen-linux-system-2.6.32-5-xen-686
Version: 2.6.32-20
Severity: important

Hi,

# xm new --help_config
WARNING!  Can't find hypervisor information in sysfs!

# uname -a 
Linux mysqueeze-2 2.6.32-5-xen-686 #1 SMP Thu Aug 12 18:09:47 UTC 2010 i686 
GNU/Linux

This is the same bug that:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580500

In that bug you comment:
"
> [0.00] Booting paravirtualized kernel on bare hardware

The kernel does not run on Xen. Closing as user error.
"

This is the same message which appear in my machine in syslog (I'm attaching 
dmesg output).

Maybe dropping a note in /usr/share/doc/xen*/README.Debian would be a good idea 
about how to solve this issue.

In my environment (cleaner squeeze install), installing 
xen-linux-system-2.6.32-5-xen-686 adds 4 boot entries to grub menu.

First entry (default entry) will give me this message error. But if I boot with 
third entry (which talk about booting xen kernel and 4.0 xen flavour) then xm 
commands start working, but the same message (Booting paravirtualized kernel on 
bare hardware) is shown too in dmesg.

So, which is the "user error" in this case ?

Thank you very much!

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

Kernel: Linux 2.6.32-5-xen-686 (SMP w/2 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xen-linux-system-2.6.32-5-xen-686 depends on:
ii  linux-image-2.6.32-5-xen-686 2.6.32-20   Linux 2.6.32 for modern PCs, Xen d
ii  xen-hypervisor-4.0-i386 [xen 4.0.1~rc6-1 The Xen Hypervisor on i386

xen-linux-system-2.6.32-5-xen-686 recommends no packages.

xen-linux-system-2.6.32-5-xen-686 suggests no packages.

-- no debconf information


dmesg-xen.gz
Description: GNU Zip compressed data

Bug#580028: linux-image-2.6.32-4-686: Can not mount cdroms, no dmesg output

[Javier Barroso]

Package: linux-2.6
Version: 2.6.32-11
Severity: normal
Tags: sid


Hi, I'm opening a new report as requested in #577534. My cdrom is working again 
(I can boot from a cd live)

But I can't mount the same cdrom which can boot.

No messages in dmesg.

# dmesg -c
# LANG=C mount /dev/cdrom1 /media/cdrom
mount: /dev/sr0: unknown device
# LANG=C mount -t iso9660 /dev/cdrom1 /media/cdrom
mount: no medium found on /dev/sr0
# isoinfo -f -i /dev/scd0 
Errno: 5 (Input/output error), test unit ready scsi sendcmd: no error
CDB:  00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 02 00 00 00 00 0E 00 00 00 00 3A 00 00 00
Sense Key: 0x2 Not Ready, Segment 0
Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0
Sense flags: Blk 0 (not valid) 
cmd finished after 0.000s timeout 20s
isoinfo: No such file or directory. Unable to open /dev/scd0
# ls -l /sys/block/ 
total 0
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-0 -> ../devices/virtual/block/dm-0
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-1 -> ../devices/virtual/block/dm-1
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-10 -> ../devices/virtual/block/dm-10
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-11 -> ../devices/virtual/block/dm-11
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-12 -> ../devices/virtual/block/dm-12
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-13 -> ../devices/virtual/block/dm-13
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-14 -> ../devices/virtual/block/dm-14
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-15 -> ../devices/virtual/block/dm-15
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-16 -> ../devices/virtual/block/dm-16
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-17 -> ../devices/virtual/block/dm-17
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-18 -> ../devices/virtual/block/dm-18
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-19 -> ../devices/virtual/block/dm-19
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-2 -> ../devices/virtual/block/dm-2
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-20 -> ../devices/virtual/block/dm-20
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-21 -> ../devices/virtual/block/dm-21
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-22 -> ../devices/virtual/block/dm-22
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-23 -> ../devices/virtual/block/dm-23
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-24 -> ../devices/virtual/block/dm-24
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-25 -> ../devices/virtual/block/dm-25
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-26 -> ../devices/virtual/block/dm-26
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-27 -> ../devices/virtual/block/dm-27
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-28 -> ../devices/virtual/block/dm-28
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-29 -> ../devices/virtual/block/dm-29
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-3 -> ../devices/virtual/block/dm-3
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-4 -> ../devices/virtual/block/dm-4
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-5 -> ../devices/virtual/block/dm-5
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-6 -> ../devices/virtual/block/dm-6
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-7 -> ../devices/virtual/block/dm-7
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-8 -> ../devices/virtual/block/dm-8
lrwxrwxrwx 1 root root 0 may  3 09:42 dm-9 -> ../devices/virtual/block/dm-9
lrwxrwxrwx 1 root root 0 may  3 09:42 loop0 -> ../devices/virtual/block/loop0
lrwxrwxrwx 1 root root 0 may  3 09:42 loop1 -> ../devices/virtual/block/loop1
lrwxrwxrwx 1 root root 0 may  3 09:42 loop2 -> ../devices/virtual/block/loop2
lrwxrwxrwx 1 root root 0 may  3 09:42 loop3 -> ../devices/virtual/block/loop3
lrwxrwxrwx 1 root root 0 may  3 09:42 loop4 -> ../devices/virtual/block/loop4
lrwxrwxrwx 1 root root 0 may  3 09:42 loop5 -> ../devices/virtual/block/loop5
lrwxrwxrwx 1 root root 0 may  3 09:42 loop6 -> ../devices/virtual/block/loop6
lrwxrwxrwx 1 root root 0 may  3 09:42 loop7 -> ../devices/virtual/block/loop7
lrwxrwxrwx 1 root root 0 may  3 09:42 sda -> 
../devices/pci:00/:00:1f.2/host2/target2:0:0/2:0:0:0/block/sda
lrwxrwxrwx 1 root root 0 may  3 09:42 sr0 -> 
../devices/pci:00/:00:1f.1/host0/target0:0:0/0:0:0:0/block/sr0
# lshw | grep -A12 cdrom
   *-cdrom
description: DVD writer
product: DVD+-RW GSA-H53L
vendor: HL-DT-ST
physical id: 0.0.0
bus info: s...@0:0.0.0
logical name: /dev/cdrom
logical name: /dev/cdrom1
logical name: /dev/cdrw
logical name: /dev/cdrw1
logical name: /dev/dvd
logical name: /dev/dvd1
logical name: /dev/dvdrw
logical name: /dev/dvdrw1
logical name: /dev/scd0
logical name: /dev/sr0
version: W712
serial: [HL-DT-STDVD+-RW GSA-H53LW71207/12/03 7U02
capabilities: removable audio cd-r cd-rw dvd dvd-r
configuration: ansiversion=5 status=nodisc
# dmesg
#

While I exec mount commands, I don't see any light in the 

Bug#577534: base: fails too with -11 kernel

[Javier Barroso]

 abr 23 08:27 dm-11 -> 
../devices/virtual/block/dm-11
lrwxrwxrwx 1 root root 0 abr 23 08:27 dm-12 -> 
../devices/virtual/block/dm-12
lrwxrwxrwx 1 root root 0 abr 23 08:27 dm-13 -> 
../devices/virtual/block/dm-13
lrwxrwxrwx 1 root root 0 abr 23 08:27 dm-14 -> 
../devices/virtual/block/dm-14
lrwxrwxrwx 1 root root 0 abr 23 08:27 dm-15 -> 
../devices/virtual/block/dm-15
lrwxrwxrwx 1 root root 0 abr 23 08:27 dm-16 -> 
../devices/virtual/block/dm-16
lrwxrwxrwx 1 root root 0 abr 23 08:27 dm-17 -> 
../devices/virtual/block/dm-17
lrwxrwxrwx 1 root root 0 abr 23 08:27 dm-18 -> 
../devices/virtual/block/dm-18
lrwxrwxrwx 1 root root 0 abr 23 08:27 dm-19 -> 
../devices/virtual/block/dm-19

lrwxrwxrwx 1 root root 0 abr 23 08:27 dm-2 -> ../devices/virtual/block/dm-2
lrwxrwxrwx 1 root root 0 abr 23 08:27 dm-20 -> 
../devices/virtual/block/dm-20
lrwxrwxrwx 1 root root 0 abr 23 08:27 dm-21 -> 
../devices/virtual/block/dm-21
lrwxrwxrwx 1 root root 0 abr 23 08:27 dm-22 -> 
../devices/virtual/block/dm-22
lrwxrwxrwx 1 root root 0 abr 23 08:27 dm-23 -> 
../devices/virtual/block/dm-23
lrwxrwxrwx 1 root root 0 abr 23 08:27 dm-24 -> 
../devices/virtual/block/dm-24
lrwxrwxrwx 1 root root 0 abr 23 08:27 dm-25 -> 
../devices/virtual/block/dm-25
lrwxrwxrwx 1 root root 0 abr 23 08:27 dm-26 -> 
../devices/virtual/block/dm-26
lrwxrwxrwx 1 root root 0 abr 23 08:27 dm-27 -> 
../devices/virtual/block/dm-27
lrwxrwxrwx 1 root root 0 abr 23 08:27 dm-28 -> 
../devices/virtual/block/dm-28
lrwxrwxrwx 1 root root 0 abr 23 08:27 dm-29 -> 
../devices/virtual/block/dm-29

lrwxrwxrwx 1 root root 0 abr 23 08:27 dm-3 -> ../devices/virtual/block/dm-3
lrwxrwxrwx 1 root root 0 abr 23 08:27 dm-4 -> ../devices/virtual/block/dm-4
lrwxrwxrwx 1 root root 0 abr 23 08:27 dm-5 -> ../devices/virtual/block/dm-5
lrwxrwxrwx 1 root root 0 abr 23 08:27 dm-6 -> ../devices/virtual/block/dm-6
lrwxrwxrwx 1 root root 0 abr 23 08:27 dm-7 -> ../devices/virtual/block/dm-7
lrwxrwxrwx 1 root root 0 abr 23 08:27 dm-8 -> ../devices/virtual/block/dm-8
lrwxrwxrwx 1 root root 0 abr 23 08:27 dm-9 -> ../devices/virtual/block/dm-9
lrwxrwxrwx 1 root root 0 abr 23 08:27 loop0 -> 
../devices/virtual/block/loop0
lrwxrwxrwx 1 root root 0 abr 23 08:27 loop1 -> 
../devices/virtual/block/loop1
lrwxrwxrwx 1 root root 0 abr 23 08:27 loop2 -> 
../devices/virtual/block/loop2
lrwxrwxrwx 1 root root 0 abr 23 08:27 loop3 -> 
../devices/virtual/block/loop3
lrwxrwxrwx 1 root root 0 abr 23 08:27 loop4 -> 
../devices/virtual/block/loop4
lrwxrwxrwx 1 root root 0 abr 23 08:27 loop5 -> 
../devices/virtual/block/loop5
lrwxrwxrwx 1 root root 0 abr 23 08:27 loop6 -> 
../devices/virtual/block/loop6
lrwxrwxrwx 1 root root 0 abr 23 08:27 loop7 -> 
../devices/virtual/block/loop7
lrwxrwxrwx 1 root root 0 abr 23 08:27 sda -> 
../devices/pci:00/:00:1f.2/host2/target2:0:0/2:0:0:0/block/sda
lrwxrwxrwx 1 root root 0 abr 23 08:27 sr0 -> 
../devices/pci:00/:00:1f.1/host0/target0:0:0/0:0:0:0/block/sr0


# wodim --devices
wodim: Overview of accessible drives (1 found) :
-
 0  dev='/dev/scd0'rwrw-- : 'HL-DT-ST' 'DVD+-RW GSA-H53L'
-

I'm not going to open another bug, because from this mount command, I 
can't boot any more with bootable cdrom, and I can't mount any cdrom


I'll try to change my writer, or update its firmware

Thank you very much, and sorry again for your wasted time


On 23/04/10 09:59, Will Set wrote:

  #wodim --devices might show the correct /dev that is on the #lshw list

--- On Thu, 4/22/10, Javier Barroso  wrote:

   

From: Javier Barroso
 


   

# lshw  # cdrom output
*-cdrom

description: DVD writer

product: DVD+-RW GSA-H53L

vendor: HL-DT-ST

physical id: 0.0.0

 bus
info: s...@0:0.0.0

logical name: /dev/cdrom

logical name: /dev/cdrom1

logical name: /dev/cdrw

logical name: /dev/cdrw1

logical name: /dev/dvd

logical name: /dev/dvd1
    
logical name: /dev/dvdrw

logical name: /dev/dvdrw1

logical name: /dev/scd0

logical name: /dev/sr0


 




   



--
Javier Barroso
Administrador de Sistemas
Dirección Servicios Corporativos: TI
jbarr...@isotrol.com
__

ISOTROL
Edificio BLUENET. Avda. Isaac Newton, s/n, Isla de la Cartuja
41092 Sevilla.
Tel.: 955 036 800 - Fax: 955 036 849
www.isotrol.com




--
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/4bd16efe.5050...@isotrol.com

Bug#577534: base: fails too with -11 kernel

[Javier Barroso]

Package: base
Severity: normal

Hello,

I'm in a sid environment
# LANG=C mount /dev/sr0 /media/cdrom
mount: /dev/sr0: unknown device
# LANG=C mount -t udf /dev/sr0 /media/cdrom
mount: no medium found on /dev/sr0

# ls -l /dev/cdrom /dev/sr0
lrwxrwxrwx  1 root root  3 abr 22 13:40 /dev/cdrom -> sr0
brw-rw+ 1 root cdrom 11, 0 abr 22 13:40 /dev/sr0

# dmesg | grep sr0
 dmesg | grep sr0
[1.480142]  sda: sda1 sda2 http://lists.debian.org/20100422124229.3080.77115.report...@pepinux.red.isotrol.com

Bug#571459: linux-2.6: with noserverino my user get read-only access

[Javier Barroso]

Package: linux-2.6
Severity: normal


Hi,

I'm replying here, but I'm not sure where this should go ... So sorry If I'm 
wasting your time

I'm having trouble:

$ # uname -r
2.6.32-3-686
$ sudo mount -o username=user,noserverino //alfresco/alfresco 
/home/user/alfresco/
$ touch alfresco/a
touch: cannot touch `alfresco/a': Permission denied
$ su 
# touch /home/user/alfresco/a # works fine

$ # uname -r
2.6.30-1-686
$ sudo mount -o username=user,noserverino //alfresco/alfresco 
/home/user/alfresco/
$ touch alfresco/a # works fine

So, this is a kernel bug, or is some issue with sudo ?? Please, tell me if I 
have to report this to bugzilla.kernel.org or to another package inside debian.

Thank you very much

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

Kernel: Linux 2.6.32-3-686 (SMP w/2 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20100323090616.3412.72467.report...@pepinux.red.isotrol.com

Bug#571459: linux-2.6: it works with noserverino option

[Javier Barroso]

Package: linux-2.6
Severity: normal

Jeff told me the solution, adding noserverino option.

I don't know if this is a bug now, if not at least indicate in Readme about 
this option could fix this problem

Thank you very much

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

Kernel: Linux 2.6.32-3-686 (SMP w/2 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20100304152457.17866.57012.report...@pepinux.red.isotrol.com

Bug#571459: linux-image-2.6.32-2-686: Mount as empty a smb alfresco share, but 2.6.30 do it fine

[Javier Barroso]

On 27/02/10 03:26, Ben Hutchings wrote:

On Thu, 2010-02-25 at 16:24 +0100, Javier Barroso wrote:
   

Package: linux-2.6
Version: 2.6.32-8
Severity: normal


Hi,

Today I tried to mount a share from alfresco via smbfs.

With older linux-image versions (I can test it with 2.6.30 for
example):

mount -t smbfs //alfresco/share ~/alfresco

works fine and ls ~/alfresco show me all my files

But with this kernel 2.6.32-8:

mount -t smbfs //alfresco/share ~/alfresco

seems to work fine but ls ~/alfresco doesn't show me any file and I
can't access to them

I would try with a newer kernel, but kernel-archive.buildserver.net is
down, at least this tell our wiki (w.d.o/DebianKernel)

I have too a PDC which samba, and its shares are working when I access
to them with the two kernels (2.6.32 and 2.6.30). I'm afraid it could
be an alfresco issue :(, but like it works with 2.6.30 kernel version,
I'm opening this bug.
 

Please report this bug upstream at<http://bugzilla.kernel.org>, under
product 'File System', component 'Samba/SMB' and let us know the bug
number.
   

Thanks for the tip, I forwarded the bug [1] , I'll wait any response

[1] http://bugzilla.kernel.org/show_bug.cgi?id=15427



--
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/4b8d41a0.1070...@isotrol.com

Bug#571459: linux-image-2.6.32-2-686: Mount as empty a smb alfresco share, but 2.6.30 do it fine

[Javier Barroso]

Package: linux-2.6
Version: 2.6.32-8
Severity: normal


Hi,

Today I tried to mount a share from alfresco via smbfs.

With older linux-image versions (I can test it with 2.6.30 for example):

mount -t smbfs //alfresco/share ~/alfresco

works fine and ls ~/alfresco show me all my files

But with this kernel 2.6.32-8:

mount -t smbfs //alfresco/share ~/alfresco

seems to work fine but ls ~/alfresco doesn't show me any file and I can't 
access to them

I would try with a newer kernel, but kernel-archive.buildserver.net is down, at 
least this tell our wiki (w.d.o/DebianKernel)

I have too a PDC which samba, and its shares are working when I access to them 
with the two kernels (2.6.32 and 2.6.30). I'm afraid it could be an alfresco 
issue :(, but like it works with 2.6.30 kernel version, I'm opening this bug.

Thank you very much

-- Package-specific info:
** Version:
Linux version 2.6.32-2-686 (Debian 2.6.32-8) (b...@decadent.org.uk) (gcc 
version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Thu Feb 11 04:08:42 UTC 2010

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.32-2-686 root=/dev/mapper/delorian-root ro quiet

** Tainted: P (1)
 * Proprietary module has been loaded.

** Kernel log:
[3.616063] usb 3-1: new full speed USB device using uhci_hcd and address 2
[3.643900] PM: Starting manual resume from disk
[3.643905] PM: Resume from partition 254:1
[3.643908] PM: Checking hibernation image.
[3.644072] PM: Error -22 checking image file
[3.644076] PM: Resume from disk failed.
[3.668785] kjournald starting.  Commit interval 5 seconds
[3.668799] EXT3-fs: mounted filesystem with ordered data mode.
[3.762307] usb 3-1: New USB device found, idVendor=047f, idProduct=c001
[3.762314] usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[3.762439] usb 3-1: configuration #1 chosen from 1 choice
[5.065247] udev: starting version 151
[5.375332] ACPI: SSDT 5ffe2b27 00453 (v01 COMPAQ  CPU_TM2 0001 MSFT 
010E)
[5.375765] processor LNXCPU:00: registered as cooling_device0
[5.376043] processor LNXCPU:01: registered as cooling_device1
[5.378574] input: PC Speaker as /devices/platform/pcspkr/input/input3
[5.412751] parport_pc 00:07: reported by Plug and Play ACPI
[5.413107] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
[5.493623] ACPI: WMI: Mapper loaded
[5.664936] intel_rng: Firmware space is locked read-only. If you can't or
[5.664939] intel_rng: don't want to disable this in firmware setup, and if
[5.664941] intel_rng: you are certain that your system has a functional
[5.664942] intel_rng: RNG, try using the 'no_fwh_detect' option.
[5.818603] usbcore: registered new interface driver hiddev
[5.822610] input: HID 047f:c001 as 
/devices/pci:00/:00:1d.1/usb3/3-1/3-1:1.3/input/input4
[5.822715] generic-usb 0003:047F:C001.0001: input,hidraw0: USB HID v1.00 
Device [HID 047f:c001] on usb-:00:1d.1-1/input3
[5.822744] usbcore: registered new interface driver usbhid
[5.822748] usbhid: v2.6:USB HID core driver
[6.149578] input: ImPS/2 Generic Wheel Mouse as 
/devices/platform/i8042/serio1/input/input5
[6.170870] nvidia: module license 'NVIDIA' taints kernel.
[6.170876] Disabling lock debugging due to kernel taint
[6.878130] HDA Intel :00:1b.0: PCI INT A -> GSI 21 (level, low) -> IRQ 
21
[6.878163] HDA Intel :00:1b.0: setting latency timer to 64
[6.948782] usbcore: registered new interface driver snd-usb-audio
[6.967330] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/input/input6
[7.035693] nvidia :01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[7.035703] nvidia :01:00.0: setting latency timer to 64
[7.035927] NVRM: loading NVIDIA UNIX x86 Kernel Module  190.53  Tue Dec  8 
18:51:41 PST 2009
[9.354537] EXT3 FS on dm-0, internal journal
[9.449650] loop: module loaded
[9.480534] smsc47b397: found SMSC SCH5307-NS (base address 0x0480, revision 
0)
[9.520621] vboxdrv: Trying to deactivate the NMI watchdog permanently...
[9.520625] vboxdrv: Successfully done.
[9.520628] vboxdrv: Found 2 processor cores.
[9.521197] vboxdrv: fAsync=0 offMin=0x915 offMax=0x3480
[9.521255] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 
'normal'.
[9.521258] vboxdrv: Successfully loaded version 3.1.4_OSE (interface 
0x0011).
[   10.745840] kjournald starting.  Commit interval 5 seconds
[   10.746013] EXT3 FS on sda1, internal journal
[   10.746021] EXT3-fs: mounted filesystem with ordered data mode.
[   10.797273] kjournald starting.  Commit interval 5 seconds
[   10.797513] EXT3 FS on dm-5, internal journal
[   10.797519] EXT3-fs: mounted filesystem with ordered data mode.
[   10.826649] kjournald starting.  Commit interval 5 seconds
[   10.826878] EXT3 FS on dm-2, internal journal
[   10.826885] EXT3-fs: mounted filesystem with ordered data mode.
[   10.844095] kjournald starting.  Commit interval 

Bug#535278: vlc: crash adding a second webcam

[Javier Barroso]

On 20/02/10 12:47, Moritz Muehlenhoff wrote:

tags 535278 moreinfo
thanks

On Thu, Jul 02, 2009 at 12:04:16PM +0200, Javier Barroso wrote:
   

Christophe Mutricy wrote:
 

For me it also looks like a kernel bug. the vlc log looks completly
normal and i can't see any vlc functions in the backtrace.

Does it works ok if the 2 webcams are plugged before you start vlc ?

   

Second webcams was affected by
http://bugzilla.kernel.org/show_bug.cgi?id=13074

Cheese is capable show me both webcam, but the second doesn't work fine.

Which command line should I try to use /dev/video{0,1} in my screen
without any type of stream or recording.

When I try select /dev/video1 from interface it doesn't work

neither
vlc --v4l-vdev /dev/video1
vlc v4l:/dev/video1
vlc --v4l2-dev /dev/video1
doesn't work,
 

Hi,
The next release of Debian (6.0, code name Squeeze) will be based
on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell
us whether the problem persists. If so, we should report it upstream
to the kernel.org developers.

The 2.6.32 kernel is available from packages.debian.org and can
be installed in both Debian stable, testing and unstable
installations.

Thanks,
 Moritz
   

Hi Moritz,

I don't be able to open two vlc with one video device in each. vlc is 
not crashing any more, and I can't see any oops from kernel


Currently :

$ vlc v4l2:///dev/video0 # video is showed and close vlc -> OK
$ vlc v4l2:///dev/video1 # video is showed and close vlc -> OK

$ vlc v4l2:///dev/video1 & vlc v4l2:///dev/video0
[1] 19834
VLC media player 1.0.5 Goldeneye
VLC media player 1.0.5 Goldeneye
[0x82e18a8] main libvlc: Ejecutar vlc con el interfaz por defecto. Usa 
'cvlc' para usar vlc sin interfaz.
[0x8bea8a8] main libvlc: Ejecutar vlc con el interfaz por defecto. Usa 
'cvlc' para usar vlc sin interfaz.

swScaler: Palette is not supported as output pixel format
[0x8e89e10] swscale scale error: could not init SwScaler and/or allocate 
memory

QPainter::begin: Paint device returned engine == 0, type: 1
QPainter::begin: Paint device returned engine == 0, type: 1
QPainter::begin: Paint device returned engine == 0, type: 1
QPainter::begin: Paint device returned engine == 0, type: 1
libv4l2: error turning on stream: Error de entrada/salida
[0x8554c20] v4l2 demux error: VIDIOC_STREAMON failed
libv4l2: warning v4l2 mmap buffers still mapped on close()
[0x8421880] v4l2 access error: VIDIOC_STREAMON failed
[0x8421880] v4l2 access error: device does not support mmap i/o
[0xb6c005c8] main input error: open of `v4l2:///dev/video0' failed: (null)

So I can't launch both instances from vlc, but if I open vlc I can chose 
both devices from "Open devices" dialog


Can vlc compose both cameras like a single film ?

Another try, playing with cheese:

$ cheese # -> /dev/video0  OK (don't close)
$ vlc v4l2:///dev/video1
VLC media player 1.0.5 Goldeneye
[0x91138a8] main libvlc: Ejecutar vlc con el interfaz por defecto. Usa 
'cvlc' para usar vlc sin interfaz.

libv4l2: error turning on stream: Error de entrada/salida
[0x91dbbe0] v4l2 demux error: VIDIOC_STREAMON failed
libv4l2: warning v4l2 mmap buffers still mapped on close()
[0x93775f0] v4l2 access error: VIDIOC_STREAMON failed
[0x93775f0] v4l2 access error: device does not support mmap i/o
[0xb6f0a910] main input error: open of `v4l2:///dev/video1' failed: (null)

And a window dialog with :
"
 Your input can't be opened:
VLC is unable to open the MRL 'v4l2:///dev/video1'. Check the log for 
details.


Where is the log ? This is a kernel fail then?

I can't probe two cheese instances, because it seems like it implements 
singleton (perhaps I should to try with two different users, but I think 
cheese is getting both cameras)


I think this should be reassigned to vlc, but I'm not sure

Thank you very much

PD: dmesg tell me about some errors:
[52175.655014] cheese[17950]: segfault at 0 ip (null) sp b298bfcc error 
4 in cheese[8048000+25000]

[52429.785816] gspca: usb_submit_urb alt 1 err -28
[52429.808712] gspca: no transfer endpoint found
[52429.812897] gspca: usb_submit_urb alt 1 err -28
[52429.836031] gspca: no transfer endpoint found
[55933.248033] gspca: usb_submit_urb alt 8 err -28
[55933.388600] gspca: usb_submit_urb alt 7 err -28
[55933.528603] gspca: usb_submit_urb alt 6 err -28
[55933.668605] gspca: usb_submit_urb alt 5 err -28
[55933.808607] gspca: usb_submit_urb alt 4 err -28
[55933.948614] gspca: usb_submit_urb alt 3 err -28
[55934.088609] gspca: usb_submit_urb alt 2 err -28
[55934.228613] gspca: usb_submit_urb alt 1 err -28
[55934.252017] gspca: no transfer endpoint found
[55934.372617] gspca: usb_submit_urb alt 8 err -28
[55934.512619] gspca: usb_submit_urb alt 7 err -28
[55934.652627] gspca: usb_submit_urb alt 6 err -28
[55934.792626] gspca: usb_submit_urb alt 5 err -28
[55934.932624] gspca: usb_submit_urb alt

Bug#530592: initramfs-tools: /dev/disk/by-uuid are not filled with logical volumes fs, so won't boot with uuid method in grub if root is a lv

[Javier Barroso]

Package: initramfs-tools
Version: 0.93.2
Severity: important

Hi,

Recently grub2 was installed in my pc and grubcfg contains:

menuentry "Debian GNU/Linux, linux 2.6.29-1-686" {
set root=(hd0,1)
search --fs-uuid --set b1124595-0bae-4e7a-8018-1a8a67ee2c85
linux   /vmlinuz-2.6.29-1-686 
root=UUID=2da467fc-77b6-4d4f-aec2-6ee323e3ef70 ro quiet 
initrd  /initrd.img-2.6.29-1-686
}

My root partition is a lvm volume, so I have to change the root parameter to 
/dev/vg/lvroot

In (initramfs) shell /dev/disk/by-uuid/ won't appears my lv filesystems.

Reassign this bug if I'm wrong thinking that is a initramfs-tools issue.

Thank you

-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-2.6.29-1-686 root=/dev/delorian/root ro quiet

-- /proc/filesystems
ext3
fuseblk
ext4
ext4dev

-- lsmod
Module  Size  Used by
binfmt_misc 7168  1 
nvidia   7215632  26 
i2c_core   20828  1 nvidia
ppdev   6224  0 
lp  7872  0 
battery 5832  0 
acpi_cpufreq6868  0 
cpufreq_stats   3588  0 
cpufreq_powersave   1276  0 
cpufreq_conservative 5456  0 
cpufreq_userspace   2748  0 
bridge 39864  0 
ipv6  232468  46 
8021q  17716  0 
garp7040  1 8021q
stp 2092  2 bridge,garp
ext4  193464  2 
jbd2   51580  1 ext4
crc16   1744  1 ext4
fuse   48352  1 
smsc47b397  4512  0 
loop   12988  0 
snd_hda_codec_realtek   173504  1 
snd_hda_intel  22092  0 
snd_hda_codec  58808  2 snd_hda_codec_realtek,snd_hda_intel
snd_usb_audio  71488  0 
snd_usb_lib13544  1 snd_usb_audio
snd_pcm_oss31708  0 
snd_mixer_oss  12000  1 snd_pcm_oss
snd_pcm62708  4 
snd_hda_intel,snd_hda_codec,snd_usb_audio,snd_pcm_oss
snd_seq_dummy   2368  0 
snd_seq_oss24756  0 
snd_seq_midi5448  0 
snd_seq_midi_event  6072  2 snd_seq_oss,snd_seq_midi
snd_seq42120  6 
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
psmouse36628  0 
snd_timer  17808  2 snd_pcm,snd_seq
snd_rawmidi18544  2 snd_usb_lib,snd_seq_midi
pcspkr  2092  0 
serio_raw   4544  0 
snd_seq_device  6108  5 
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq,snd_rawmidi
snd_hwdep   6000  2 snd_hda_codec,snd_usb_audio
rng_core3644  0 
evdev   8160  10 
snd48420  13 
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_usb_audio,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_seq,snd_timer,snd_rawmidi,snd_seq_device,snd_hwdep
soundcore   6204  1 snd
snd_page_alloc  8036  2 snd_hda_intel,snd_pcm
wmi 6332  0 
parport_pc 22020  1 
parport30868  3 ppdev,lp,parport_pc
button  5672  0 
ext3  107180  7 
jbd42500  1 ext3
mbcache 7180  2 ext4,ext3
dm_snapshot16716  0 
usbhid 29132  0 
hid34260  1 usbhid
sd_mod 28252  3 
crc_t10dif  1616  1 sd_mod
ide_cd_mod 25532  1 
cdrom  29804  1 ide_cd_mod
ata_generic 4316  0 
ide_pci_generic 3408  0 
ata_piix   20092  3 
uhci_hcd   19392  0 
libata148892  2 ata_generic,ata_piix
piix5584  1 
ide_core   91820  3 ide_cd_mod,ide_pci_generic,piix
ehci_hcd   29936  0 
tg391048  0 
scsi_mod  132076  2 sd_mod,libata
usbcore   124912  6 
snd_usb_audio,snd_usb_lib,usbhid,uhci_hcd,ehci_hcd
libphy 19424  1 tg3
intel_agp  22548  0 
agpgart30624  2 nvidia,intel_agp
thermal15092  0 
processor  39540  2 acpi_cpufreq,thermal
fan 4104  0 
thermal_sys10272  3 thermal,processor,fan
dm_mirror  12160  0 
dm_region_hash 10632  1 dm_mirror
dm_log  8588  2 dm_mirror,dm_region_hash
dm_mod 49048  43 dm_snapshot,dm_mirror,dm_log

-- /etc/kernel-img.conf
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
BOOT=local
DEVICE=eth0
NFSROOT=auto


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

Kernel: Linux 2.6.29-1-686 (SMP w/2 CPU cores)
Locale: LANG=es_ES

Bug#418342: linux-image-2.6.18-4-xen-686: Oops renaming a vlan interface over bonding interface

[Javier Barroso]

Package: linux-image-2.6.18-4-xen-686
Version: 2.6.18.dfsg.1-12
Severity: critical
Justification: breaks the whole system


Steps to reproduce:
ha0 and ha1 are eth0 and eth1 renamed with udev at 
/etc/udev/rules.d/z25_persistent-net.rules
ha is a bonding dev with ha0 and ha1 as slaves.
# ip link show dev ha
ha:  mtu 1500 qdisc noqueue
link/ether 00:18:fe:77:xx:xx brd ff:ff:ff:ff:ff:ff

# vconfig add ha 1004
# ip link set dev ha.1004 down
# ip link set dev ha.1004 name vlan-test

Apr  9 10:17:24 sscc2 kernel: bonding: Warning: Cannot create 
/proc/net/bonding/
Apr  9 10:17:24 sscc2 kernel: BUG: unable to handle kernel NULL pointer 
dereference at virtual address 0248
Apr  9 10:17:24 sscc2 kernel:  printing eip:
Apr  9 10:17:24 sscc2 kernel: c018eaa5
Apr  9 10:17:24 sscc2 kernel: 0071c000 -> *pde = :02745001
Apr  9 10:17:24 sscc2 kernel: 00745000 -> *pme = :
Apr  9 10:17:24 sscc2 kernel: Oops:  [#1]
Apr  9 10:17:24 sscc2 kernel: SMP
Apr  9 10:17:24 sscc2 kernel: Modules linked in: ipv6 button ac battery 8021q 
bonding loop serio_raw serial_core psmouse pcspkr evdev joydev shpchp 
pci_hotplug ext3 jbd mbcache dm_mirror dm_snapshot dm_mod ide_generic generic 
usbhid bnx2 piix cciss scsi_mod ide_core ehci_hcd uhci_hcd usbcore thermal 
processor fan
Apr  9 10:17:24 sscc2 kernel: CPU:1
Apr  9 10:17:24 sscc2 kernel: EIP:0061:[]Not tainted VLI
Apr  9 10:17:24 sscc2 kernel: EFLAGS: 00010202   (2.6.18-4-xen-686 #1)
Apr  9 10:17:24 sscc2 kernel: EIP is at sysfs_remove_group+0x17/0x5c
Apr  9 10:17:24 sscc2 kernel: eax:    ebx: ee1f51a0   ecx: 0007   
edx: ee1f51a0
Apr  9 10:17:24 sscc2 kernel: esi: 0218   edi: ee1f00bf   ebp: 000a   
esp: ecf57ec4
Apr  9 10:17:24 sscc2 kernel: ds: 007b   es: 007b   ss: 0069
Apr  9 10:17:24 sscc2 kernel: Process ip (pid: 4638, ti=ecf56000 task=c0e23000 
task.ti=ecf56000)
Apr  9 10:17:24 sscc2 kernel: Stack: c04d0ec0 ee1f4fa0 c04d0c00 ee1e6742 
ee1d12c4 c0126273 c04d0c00 
Apr  9 10:17:24 sscc2 kernel:c04d0c10 88c53113 c0232c1b  
c022940f ecf57f38 8923 ecf57f38
Apr  9 10:17:24 sscc2 kernel:c0233494 bf89f32c  ecf57f30 
c017b36a ed0fd768  0002
Apr  9 10:17:24 sscc2 kernel: Call Trace:
Apr  9 10:17:24 sscc2 kernel:  [] bond_netdev_event+0x33/0x74 
[bonding]
Apr  9 10:17:24 sscc2 kernel:  [] notifier_call_chain+0x19/0x32
Apr  9 10:17:24 sscc2 kernel:  [] dev_change_name+0x168/0x171
Apr  9 10:17:24 sscc2 kernel:  [] sock_ioctl+0x0/0x1b5
Apr  9 10:17:24 sscc2 kernel:  [] dev_ioctl+0x348/0x462
Apr  9 10:17:24 sscc2 kernel:  [] inotify_d_instantiate+0x36/0x59
Apr  9 10:17:24 sscc2 kernel:  [] do_page_fault+0x6af/0xb76
Apr  9 10:17:24 sscc2 kernel:  [] sock_ioctl+0x193/0x1b5
Apr  9 10:17:24 sscc2 kernel:  [] sock_ioctl+0x0/0x1b5
Apr  9 10:17:24 sscc2 kernel:  [] do_ioctl+0x1c/0x5d
Apr  9 10:17:24 sscc2 kernel:  [] vfs_ioctl+0x24a/0x25c
Apr  9 10:17:24 sscc2 kernel:  [] sys_socketcall+0x51/0x181
Apr  9 10:17:24 sscc2 kernel:  [] sys_ioctl+0x48/0x5f
Apr  9 10:17:24 sscc2 kernel:  [] syscall_call+0x7/0xb
Apr  9 10:17:24 sscc2 kernel: Code: 10 89 f0 83 c3 04 e8 85 e1 ff ff 8b 03 85 
c0 75 ee 5b 5e c3 57 56 89 c6 53 89 d3 8b 3a 85 ff 74 18 31 c0 83 c9 ff f2 ae 
f7 d1 49 <8b> 56 30 8b 03 e8 f0 6e fd ff 89 c7 eb 18 8b 78 30 85 ff 74 11
Apr  9 10:17:24 sscc2 kernel: EIP: [] sysfs_remove_group+0x17/0x5c 
SS:ESP 0069:ecf57ec4

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

Versions of packages linux-image-2.6.18-4-xen-686 depends on:
ii  initramfs-tools 0.85gtools for generating an initramfs
ii  linux-modules-2.6.18-4- 2.6.18.dfsg.1-12 Linux 2.6.18 modules on i686

Versions of packages linux-image-2.6.18-4-xen-686 recommends:
ii  libc6-xen   2.3.6.ds1-13 GNU C Library: Shared libraries [X

-- no debconf information


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