registry team mailing list archive

[Willem Hobers <whobers@xxxxxxxxx>]

Hello Philippe,

I did as you asked. It seems to have resulted in a new kernel being
installed and running:

dpkg.log:
2010-05-18 08:37:49 startup archives install
2010-05-18 08:37:54 install linux-image-2.6.34-999-generic <geen>
2.6.34-999.201005172238
2010-05-18 08:37:54 status half-installed linux-image-2.6.34-999-generic
2.6.34-999.201005172238
2010-05-18 08:38:28 status unpacked linux-image-2.6.34-999-generic
2.6.34-999.201005172238
2010-05-18 08:38:28 status unpacked linux-image-2.6.34-999-generic
2.6.34-999.201005172238
2010-05-18 08:38:28 configure linux-image-2.6.34-999-generic
2.6.34-999.201005172238 2.6.34-999.201005172238
2010-05-18 08:38:28 status unpacked linux-image-2.6.34-999-generic
2.6.34-999.201005172238
2010-05-18 08:38:28 status half-configured linux-image-2.6.34-999-generic
2.6.34-999.201005172238
2010-05-18 08:38:55 status installed linux-image-2.6.34-999-generic
2.6.34-999.201005172238

uname in Console:

willem@PC10-135:~$ uname -r
2.6.34-999-generic

The laptop will now only work in safe mode.

The trick with pressing shift did not result in me seeing any grub-menu, so
I was not given the possibility to chose the newly installed kernel. Still
it seems that I am running it nonetheless.

The kernel log still shows the messages though they are not as numerous as
before:

May 18 08:53:49 PC10-135 kernel: [  798.431245]  CIFS VFS: ignoring corrupt
resume name
May 18 08:53:53 PC10-135 kernel: [  801.744130]  CIFS VFS: ignoring corrupt
resume name
May 18 08:55:24 PC10-135 kernel: [  892.502408]  CIFS VFS: ignoring corrupt
resume name

Does this help at all?

Willem

Ps. I will now deinstall the 2.6.34-999-kernel.

2010/5/18 Philippe Gauthier <philippe.gauthier@xxxxxxxxx>

> Thanks Willem! The question about the regression is only there to add a
> tag to the bug report. See [1] for more information about the regression
> tags. For now, we will assume it always been broken ;)
>
> Since it looks like we have hit a genuine kernel bug and we have the
> basic information about the current configuration, I am marking this bug
> as Confirmed, and also adding the "needs-upstream-testing" tag. This
> means that it would be nice to verify if the bug is still present when
> using a stock kernel (that is, not customized by Ubuntu.) The complete
> details are explained here [2]
>
> To install the mainline kernel, you need to download the linux-image
> package from http://kernel.ubuntu.com/~kernel-<http://kernel.ubuntu.com/%7Ekernel->
> ppa/mainline/daily/current/  corresponding to the architecture of your
> system (i386). To install it, run the following command in the directory
> where the package has been downloaded:
>
> sudo dpkg -i *.deb
>
> There should be a new option line in the boot loader after you restart
> (hold the Shift key to get to the menu.) If the bug is still there, we
> will send the bug to the upstream kernel developers. Otherwise we will
> try to track back what change in the Ubuntu kernel causes this problem.
> Thanks in advance!
>
> [1] https://wiki.ubuntu.com/QATeam/RegressionTracking
> [2] https://wiki.ubuntu.com/KernelTeam/MainlineBuilds
>
>
> ** Tags added: needs-upstream-testing
>
> ** Changed in: linux (Ubuntu)
>       Status: Incomplete => Confirmed
>
> --
> Log messages: "CIFS VFS: ignoring corrupt resume name"
> https://bugs.launchpad.net/bugs/580952
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in NULL Project: Invalid
> Status in “linux” package in Ubuntu: Confirmed
>
> Bug description:
> Kernel-log contains numerous messages:
>
> May 14 21:55:23 PC10-135 kernel: [ 3061.200126]  CIFS VFS: ignoring corrupt
> resume name
> May 14 21:55:24 PC10-135 kernel: [ 3062.690731]  CIFS VFS: ignoring corrupt
> resume name
> May 14 21:55:27 PC10-135 kernel: [ 3065.119520]  CIFS VFS: ignoring corrupt
> resume name
> May 14 21:55:27 PC10-135 kernel: [ 3065.375574]  CIFS VFS: ignoring corrupt
> resume name
> May 14 21:55:28 PC10-135 kernel: [ 3066.125056]  CIFS VFS: ignoring corrupt
> resume name
> May 14 21:55:30 PC10-135 kernel: [ 3068.819686]  CIFS VFS: ignoring corrupt
> resume name
> May 14 21:55:31 PC10-135 kernel: [ 3069.075233]  CIFS VFS: ignoring corrupt
> resume name
> May 14 21:55:37 PC10-135 kernel: [ 3075.533021]  CIFS VFS: ignoring corrupt
> resume name
> May 14 21:55:39 PC10-135 kernel: [ 3077.600779]  CIFS VFS: ignoring corrupt
> resume name
> May 14 21:55:44 PC10-135 kernel: [ 3082.421668]  CIFS VFS: ignoring corrupt
> resume name
> May 14 21:55:47 PC10-135 kernel: [ 3085.569055]  CIFS VFS: No response for
> cmd 50 mid 17781
> May 14 21:55:47 PC10-135 kernel: [ 3085.577106]  CIFS VFS: No response for
> cmd 50 mid 23875
>
> I *think* these may be the cause of problems I experience when copying
> files from a local harddisk to a network harddisk: copying files with
> nautilus failes quite often. Sometimes gnome commander also failes (and
> sometimes it does not, even though nautilus does). Using CLI cp is at times
> the only way to get files copied.
>
> Runing Ubuntu 10.04, 32 bits, updated on a 64 bit AMD Turion laptop (HP
> Pavilion dv9000).
>
> The network harddisk is a Freecom 500Gb, which is NTFS-formatted.
>
> fstab:
> //its.ip.num.ber/Thuis  /media/Thuis  cifs
>  user_name=,user_group=,iocharset=iso8859-15,nounix,noserverinfo,file_mode=0777,dir_mode=0777
>  0 0
>
> Please advice.
>
> If you need any more information, please tell me what you need me to
> provide.
> ---
> AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
> Architecture: i386
> ArecordDevices:
>  **** List of CAPTURE Hardware Devices ****
>  card 0: NVidia [HDA NVidia], device 0: CONEXANT Analog [CONEXANT Analog]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> AudioDevicesInUse:
>  USER        PID ACCESS COMMAND
>  /dev/snd/controlC0:  willem     1496 F.... pulseaudio
> CRDA: Error: [Errno 2] Bestand of map bestaat niet
> Card0.Amixer.info:
>  Card hw:0 'NVidia'/'HDA NVidia at 0xf2480000 irq 21'
>   Mixer name   : 'Conexant CX20561 (Hermosa)'
>   Components   : 'HDA:14f15051,103c30cf,00100000'
>   Controls      : 11
>   Simple ctrls  : 6
> DistroRelease: Ubuntu 10.04
> HibernationDevice: RESUME=UUID=fd67cd7d-03c3-4d21-ae1b-1fb83d52bb7c
> InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
> Lsusb:
>  Bus 002 Device 002: ID 03f0:171d Hewlett-Packard Wireless (Bluetooth +
> WLAN) Interface [Integrated Module]
>  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>  Bus 001 Device 003: ID 04f2:b023 Chicony Electronics Co., Ltd Gateway USB
> 2.0 Webcam
>  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> MachineType: Hewlett-Packard HP Pavilion dv9700 Notebook PC
> NonfreeKernelModules: nvidia wl
> Package: linux (not installed)
> ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic
> root=UUID=5ae68070-cf0f-407e-948f-894c1cd677c2 ro splash vga=795 quiet
> splash
> ProcEnviron:
>  LANG=nl_NL.utf8
>  SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
> Regression: No
> RelatedPackageVersions: linux-firmware 1.34
> Reproducible: Yes
> RfKill:
>  0: hci0: Bluetooth
>        Soft blocked: no
>        Hard blocked: no
> Tags: lucid filesystem needs-upstream-testing
> Uname: Linux 2.6.32-22-generic i686
> UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare
> dmi.bios.date: 01/11/2008
> dmi.bios.vendor: Hewlett-Packard
> dmi.bios.version: F.27
> dmi.board.name: 30DA
> dmi.board.vendor: Quanta
> dmi.board.version: 85.24
> dmi.chassis.type: 10
> dmi.chassis.vendor: Quanta
> dmi.chassis.version: N/A
> dmi.modalias:
> dmi:bvnHewlett-Packard:bvrF.27:bd01/11/2008:svnHewlett-Packard:pnHPPaviliondv9700NotebookPC:pvrRev1:rvnQuanta:rn30DA:rvr85.24:cvnQuanta:ct10:cvrN/A:
> dmi.product.name: HP Pavilion dv9700 Notebook PC
> dmi.product.version: Rev 1
> dmi.sys.vendor: Hewlett-Packard
>
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/null/+bug/580952/+subscribe
>

-- 
Log messages: "CIFS VFS: ignoring corrupt resume name"
https://bugs.launchpad.net/bugs/580952
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for NULL Project.