Came here through Google. Very likely the cause of these error messages
is a faulty SMB implementation in the proprietary OS of the Freecom
Network drive. This is not a bug in Ubuntu.
In the original post, Willem mentions: "The network harddisk is a
Freecom 500Gb, which is NTFS-formatted." These d
Willem Hobers, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/580952/comments/26
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow
Hi Christopher
Thanks for you email.
I am not using 10.04 any more, so I can't test as described below.
Thank you for the good work.
Happy to be using Ubuntu.
op 23-12-13 14:56, Christopher M. Penalver schreef:
> WIllem Hobers, this bug was reported a while ago and there hasn't been
> any acti
WIllem Hobers, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/cu
Perhaps this may help your analysis.
I've got another PC ( CPU1: Intel(R) Atom(TM) CPU 230 @ 1.60GHz
stepping 02) which is running Ubuntu 9.04, with kernel:
2.6.28-18-generic
In the syslog there's also quite a number of the same messages:
CIFS VFS: ignoring corrupt resume name.
Any more in
** Tags removed: needs-upstream-testing
--
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
Well, bless my baby's bottom: after uninstalling the 2.6.34.999-kernel
and rebooting my wifi is working again!
Am now running:
wil...@pc10-135:~$ uname -r
2.6.32-22-generic
as before.
--
Log messages: "CIFS VFS: ignoring corrupt resume name"
https://bugs.launchpad.net/bugs/580952
You received
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
2.6.34-999.201005172238
2010-05-18 08:37:54 status half-installed linux-ima
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 c
7 21:02:06 PC10-135 kernel: [ 9075.457181] CIFS VFS: ignoring corrupt
resume name
etc etc etc
-- Forwarded message --
From: Willem Hobers
Date: 2010/5/17
Subject: Fwd: [Bug 580952] Re: Log messages: "CIFS VFS: ignoring corrupt
resume name"
To: Bug 580952 <580...@bugs
st the wireless connection at the moment, I am afraid: wireless
stopped working for I don't know what reason.
And I can't find a solution to that yet.
Sorry about that.
-- Forwarded message --
From: Willem Hobers
Date: 2010/5/17
Subject: Re: [Bug 580952] Re: Log mess
Hello Philippe,
Thanks for your feedback.
I did as you asked... it seems to have gone all right. Cool.
One question in the process after "apport-collect" sort of confused me:
the process remarked (something along the lines of): a bug is considered
a regression if it did NOT exist in a previous r
apport information
** Tags added: apport-collected
** Description changed:
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
Willem: Thank you for your bug report. Don't worry too much about the
Invalid status for now, it's just marked as such because it was
initially assigned to a project called NULL which had nothing to do with
the problem. Also, adding comments to this bug report is perfectly OK.
Because your problem
Hello Curtis,
I'm a launchpad newby, and as such I am not able to "parse" your
message. Sorry.
Am I to understand that the status of this bug is now "invalid"? And if
so, what does that mean? Do I perhaps have to report this bug elsewhere?
Have I not supplied the right information?
Please bear w
** Project changed: launchpad-registry => null
** Changed in: null
Status: New => Invalid
** Also affects: ubuntu
Importance: Undecided
Status: New
--
Log messages: "CIFS VFS: ignoring corrupt resume name"
https://bugs.launchpad.net/bugs/580952
You received this bug notificatio
16 matches
Mail list logo
