module compile error for aarch64

Bug #1348277 reported by Chuck Tuffli
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

When compiling an external module for aarch64 on Ubuntu 14.04, the compiler generates the following error:

In file included from /home/ctuffli/dev/ubuntu-trusty/include/linux/netlink.h:6:0,
                 from /home/ctuffli/dev/ubuntu-trusty/include/uapi/scsi/scsi_netlink.h:25,
                 from /home/ctuffli/dev/ubuntu-trusty/include/scsi/scsi_transport_fc.h:32,
<edited>
/home/ctuffli/dev/ubuntu-trusty/include/linux/skbuff.h: In function ‘skb_can_coalesce’:
/home/ctuffli/dev/ubuntu-trusty/include/linux/skbuff.h:2255:14: error: comparison between signed and unsigned integer expressions [-Werror=sign-compare]
          off == frag->page_offset + skb_frag_size(frag);
              ^
cc1: all warnings being treated as errors
cc1: all warnings being treated as errors

Although something like the below quiets the warning, it isn't clear to me this is the correct change

diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
index e9b1a3c..e3623cc 100644
--- a/include/linux/skbuff.h
+++ b/include/linux/skbuff.h
@@ -2252,7 +2252,7 @@ static inline bool skb_can_coalesce(struct sk_buff *skb, int i,
   const struct skb_frag_struct *frag = &skb_shinfo(skb)->frags[i - 1];

   return page == skb_frag_page(frag) &&
- off == frag->page_offset + skb_frag_size(frag);
+ off == (int)(frag->page_offset + skb_frag_size(frag));
  }
  return false;
 }
---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory
CRDA: Error: [Errno 2] No such file or directory
CurrentDmesg: [ 17.335985] init: plymouth-upstart-bridge main process ended, respawning
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=88388f89-d798-4675-9542-27cacae45a9d
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
Package: linux (not installed)
PciMultimedia:

ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: console=ttyS0,115200n8 ro
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-32-generic N/A
 linux-backports-modules-3.13.0-32-generic N/A
 linux-firmware 1.127.4
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty
Uname: Linux 3.13.0-32-generic aarch64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory
CRDA: Error: [Errno 2] No such file or directory
CurrentDmesg: [ 17.335985] init: plymouth-upstart-bridge main process ended, respawning
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=88388f89-d798-4675-9542-27cacae45a9d
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
Package: linux (not installed)
PciMultimedia:

ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: console=ttyS0,115200n8 ro
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-32-generic N/A
 linux-backports-modules-3.13.0-32-generic N/A
 linux-firmware 1.127.4
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty
Uname: Linux 3.13.0-32-generic aarch64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1348277

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Chuck Tuffli (ctuffli) wrote : AudioDevicesInUse.txt

apport information

tags: added: apport-collected trusty
description: updated
Revision history for this message
Chuck Tuffli (ctuffli) wrote : BootDmesg.txt

apport information

Revision history for this message
Chuck Tuffli (ctuffli) wrote : Lspci.txt

apport information

Revision history for this message
Chuck Tuffli (ctuffli) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Chuck Tuffli (ctuffli) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Chuck Tuffli (ctuffli) wrote : ProcModules.txt

apport information

Revision history for this message
Chuck Tuffli (ctuffli) wrote : UdevDb.txt

apport information

Revision history for this message
Chuck Tuffli (ctuffli) wrote : UdevLog.txt

apport information

Revision history for this message
Chuck Tuffli (ctuffli) wrote : WifiSyslog.txt

apport information

description: updated
Revision history for this message
Chuck Tuffli (ctuffli) wrote : AudioDevicesInUse.txt

apport information

Revision history for this message
Chuck Tuffli (ctuffli) wrote : BootDmesg.txt

apport information

Revision history for this message
Chuck Tuffli (ctuffli) wrote : Lspci.txt

apport information

Revision history for this message
Chuck Tuffli (ctuffli) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Chuck Tuffli (ctuffli) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Chuck Tuffli (ctuffli) wrote : ProcModules.txt

apport information

Revision history for this message
Chuck Tuffli (ctuffli) wrote : UdevDb.txt

apport information

Revision history for this message
Chuck Tuffli (ctuffli) wrote : UdevLog.txt

apport information

Revision history for this message
Chuck Tuffli (ctuffli) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-rc7-utopic/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Chuck Tuffli (ctuffli)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream
Revision history for this message
Brian Fromme (brianfromme) wrote :

Hi Joseph,

Can you comment whether you know about an upstream fix for this problem. Emulex has a customer that is trying to work around this issue. If we know that the problem is fixed in a daily Ubuntu build, perhaps they could test that.

 thanks,
 Brian

tags: added: kernel-da-key
tags: added: kernel-key
removed: kernel-da-key
tags: added: kernel-da-key
removed: kernel-key
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.