Bug#723761: Info received (irq 16: nobody cared errors for the mptsas driver)
[0.446949] Fusion MPT SAS Host driver 3.04.20
[0.461810] mptbase: ioc0: Initiating bringup
[1.164034] ioc0: LSISAS1064E B1: Capabilities={Initiator}
[1.164071] mptsas :05:00.0: setting latency timer to 64
[1.280036] Refined TSC clocksource calibration: 2133.408 MHz.
[1.280041] Switching to clocksource tsc
[6.944375] scsi0 : ioc0: LSISAS1064E B1, FwRev=0110h, Ports=1,
MaxQ=511, IRQ=16
[6.968667] mptsas: ioc0: attaching sata device: fw_channel 0, fw_id 5,
phy 0, sas_addr 0x3da8a999f1ba7995
[6.971490] scsi 0:0:0:0: Direct-Access ATA WD2502ABYS-23B7A
3B02 PQ: 0 ANSI: 5
[6.974862] mptsas: ioc0: attaching sata device: fw_channel 0, fw_id 1,
phy 1, sas_addr 0x3dbaa996ebba7994
[6.977688] scsi 0:0:1:0: Direct-Access ATA WD2502ABYS-23B7A
3B04 PQ: 0 ANSI: 5
[6.981055] mptsas: ioc0: attaching raid volume, channel 1, id 0
[6.981890] scsi 0:1:0:0: Direct-Access LSILOGIC Logical Volume
3000 PQ: 0 ANSI: 2
[6.994397] sd 0:1:0:0: [sda] 486326272 512-byte logical blocks: (248
GB/231 GiB)
[6.994635] sd 0:1:0:0: [sda] Write Protect is off
[6.994638] sd 0:1:0:0: [sda] Mode Sense: 03 00 00 08
[6.994843] sd 0:1:0:0: [sda] Got wrong page
[6.994900] sd 0:1:0:0: [sda] Assuming drive cache: write through
[6.995920] sd 0:1:0:0: [sda] Got wrong page
[6.995975] sd 0:1:0:0: [sda] Assuming drive cache: write through
[7.016636] sda: sda1 sda2
[7.017787] sd 0:1:0:0: [sda] Got wrong page
[7.017845] sd 0:1:0:0: [sda] Assuming drive cache: write through
[7.017903] sd 0:1:0:0: [sda] Attached SCSI disk
*
[ 10.386339] irq 16: nobody cared (try booting with the irqpoll option)
[ 10.386454] Pid: 665, comm: pidof Not tainted 3.2.0-4-amd64 #1 Debian
3.2.51-1
[ 10.386457] Call Trace:
[ 10.386460] IRQ [810928bd] ? __report_bad_irq+0x2c/0xb5
[ 10.386473] [81092c7a] ? note_interrupt+0x170/0x1f2
[ 10.386478] [8109102c] ? handle_irq_event_percpu+0x15f/0x17d
[ 10.386483] [8104c37d] ? __do_softirq+0x13e/0x177
[ 10.386487] [8109107e] ? handle_irq_event+0x34/0x52
[ 10.386492] [810933f1] ? handle_fasteoi_irq+0x7c/0xaf
[ 10.386498] [8100f88d] ? handle_irq+0x1d/0x21
[ 10.386502] [8100f5bd] ? do_IRQ+0x42/0x98
[ 10.386507] [8134f4ee] ? common_interrupt+0x6e/0x6e
[ 10.386510] EOI [81140a5d] ? task_dumpable+0x23/0x34
[ 10.386519] [8110a5bb] ? dput+0x1b/0xee
[ 10.386523] [8110252c] ? path_to_nameidata+0x19/0x3a
[ 10.386528] [81103353] ? walk_component+0x3bf/0x406
[ 10.386533] [811039e1] ? link_path_walk+0x174/0x421
[ 10.386537] [81105a3d] ? path_openat+0xac/0x33a
[ 10.386542] [81105d33] ? user_path_at_empty+0x53/0x7b
[ 10.386546] [81105d8d] ? do_filp_open+0x2a/0x6e
[ 10.386551] [8110eb13] ? alloc_fd+0x64/0x109
[ 10.386556] [810f9d59] ? do_sys_open+0x5e/0xe5
[ 10.386561] [81354212] ? system_call_fastpath+0x16/0x1b
[ 10.386564] handlers:
[ 10.386615] [a0001d67] mpt_interrupt
[ 10.386697] [a01e10cd] usb_hcd_irq
[ 10.386780] Disabling IRQ #16
2014-01-21 Debian Bug Tracking System ow...@bugs.debian.org:
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.
Your message has been sent to the package maintainer(s):
Debian Kernel Team debian-kernel@lists.debian.org
If you wish to submit further information on this problem, please
send it to 723...@bugs.debian.org.
Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.
--
723761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723761
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Building a debian kernel - symlink from build to source?
Hi, I built many times debian kernels for myself, but now I have a problem that I don't understand. I'm following advices here: http://forum.excito.net/viewtopic.php?f=9t=4744sid=d7c5dadbaac8d9955ad07db7dcea31a9 but I get not any help sofar out there. On the abowe mentioned forum there is an advice for someone else, I quote it here: quote Re: B2 Wireless AP setup: RTL8188CUS Postby Gordon » 14 Dec 2013, 11:34 Are you compiling on the B2 itself? I had a similar issue with one of my first projects. The modules directory should contain a symlink to the kernel source ( build - ../../../usr/src/linux ). Obviously this means you need to have the source and it needs to be prepared. There is a second issue here as well and that is that the source as distributed by Excito is meant to create a Debian package and adds additional symbols during that build. The result is that if you use that source to create external modules, the version stamping is off and the module won't work. You need to change the Makefile so that the module version you're creating matches `uname -r`: i.e. change the value for EXTRAVERSION from .4 to .4-13, or whatever that last number says on your B2 (my B3 has 11). /quote I don't understand this abowe, because English isn't my first language. So I did'nt make any symlink and didn't change the Makefile as adviced abowe. I built the kernel version linux_2.6.39.4-13 from the downloaded source linux_2.6.39.4-13.dsc on the Debian Squeeze 64 bit guest op. system on my Virtual Box emulator, where the host op. system is Debian SID. I did the followings steps: echo deb http://www.emdebian.org/debian/ squeeze main \ /etc/apt/sources.list.d/emdebian.list apt-get update apt-get install gcc-4.4-powerpc-linux-gnu apt-get install build-essential devscripts apt-get install device-tree-compiler uboot-mkimage apt-get install libncurses5-dev export ARCH=powerpc export CROSS_COMPILE=powerpc-linux-gnu- dget -xu \ http://b3.update.excito.org/pool/main/l/linux/linux_2.6.39.4-13.dsc cd linux-2.6.39.4 make menuconfig Load the default excito configuration: From the menu, select Load an Alternate Configuration File and enter the following path: arch/powerpc/configs/bubbatwo_defconfig Note: whenever you customize the kernel, the resulting configuration must be placed in arch/arm/configs/bubba3_defconfig (arch/powerpc/configs/bubbatwo_defconfig for the B2); only this file will be used during the compilation phase to configure the kernel. So I saved the resulting configuration into arch/powerpc/configs/bubbatwo_defconfig . dpkg-buildpackage -us -uc -b -apowerpc sudo dpkg -i bubba3-kernel-headers-powerpc_2.6.39.4-13_powerpc.deb \ bubba3-kernel_2.6.39.4-13_powerpc.deb The problem is when I installed this new kernel on my Bubba headless power pc box, I can't find any modules in the /lib/modules/2.6.39.4-13/ directory. So, I think that that I must to create the abowe mentioned symlink build - ../../../usr/src/linux but I don't know in which directory to do this? Can one help me in this? Any advices will be appreciated! -- Regards from Pal -- 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/20140206102457.GB5892@localhost
Bug#689942: Also here
I am seeing the same bug here. I have yet to check fstab which is likely to be odd ( a heritage machine). Was the patch incorporated? -- 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/20140206104511.GA5662@exact.conquest
Bug#737023: marked as done (BCM5708 with bnx2 driver shows lots of errors on packets.)
Your message dated Thu, 6 Feb 2014 12:51:10 +0100 with message-id 20140206115110.ga3...@www.manty.net and subject line Re: Bug#737023: BCM5708 with bnx2 driver shows lots of errors on packets. has caused the Debian Bug report #737023, regarding BCM5708 with bnx2 driver shows lots of errors on packets. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 737023: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737023 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-latest Severity: important Tags: upstream Hi! I have wheezy installed on several servers wich have a BCM5708 based NIC, which uses the bnx2 driver and I'm seeing a lot of errors on the network RX packets, this happens wether the machine runs current 3.2 stable kernel or 3.12 unstable one, and with firmware-bnx2 coming from stable and unstable. Searching on google didn't show any solution on this, but I found a couple of discussions showing the same kind of errors: http://slashzeroconf.wordpress.com/2008/04/17/broadcom-netxtreme-ii-bcm5708-bnx2-ip-checksum-error/ http://h30499.www3.hp.com/t5/Networking/bnx2-ip-checksum-error/td-p/4119430 These are posts from 2008, however I'm still seeing this right now with current kernels and firmware. I've tried to run these commands: ethtool -K eth0 rx off ethtool -K eth0 tx off ethtool -K eth0 tso off but that didn't make any change on the behaviour. For my tests I'm running a ping which is loosing packets ranging from 12% to 60% (I suppose that this depends on how busy the NIC is). On the setups I did right now I'm using VLAN tagging, I don't know if that makes any difference, I'll try to run more tests with and without this. The systems run Debian 7.3 and the kernels I tried were: linux-image-3.11-2-amd64 3.11.8-1 linux-image-3.12-1-amd64 3.12.8-1 linux-image-3.2.0-4-amd64 3.2.51-1 Don't know what else to add, if you feel I'm missing something just let me know. I removed the system information at the end as I'm not writing from the servers having the problem. Regards. ---End Message--- ---BeginMessage--- Hi! Sorry Ben for making you loose time with this, I thought the hardware was broken from the beginning, but having several servers with the same problem and the bugs that I had found on google drove me to think it could be the driver and that's why I sent the bug. In the end it seems all the problems were caused by the Pass-Thru (I had asked a local hp technician about it and he told me that this part could not be causing the problems). I managed to get my hands on a new Pass-Thru and changed the old one with the new one and I'm seeing http transfers of 108 MB/s and above without a single error. Thanks for your help and interest and sorry again for the disturbance. -- Manty/BestiaTester - http://manty.net---End Message---
Bug#737701: marked as done (ext4 silently ignores acl mount option)
Your message dated Thu, 06 Feb 2014 10:23:48 -0500 with message-id 52f3a904.4060...@ubuntu.com and subject line Re: Processed: Re: Bug#737701: mount: When I execute 'mount -o remount,acl /' . This command dont work. has caused the Debian Bug report #737701, regarding ext4 silently ignores acl mount option to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 737701: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737701 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mount Version: 2.20.1-5.3 Severity: normal -- System Information: Debian Release: 7.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mount depends on: ii libblkid12.20.1-5.3 ii libc62.13-38 ii libmount12.20.1-5.3 ii libselinux1 2.1.9-5 ii libsepol12.1.4-3 mount recommends no packages. Versions of packages mount suggests: ii nfs-common 1:1.2.6-4 -- no debconf information ---End Message--- ---BeginMessage--- -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 After asking about it on the upstream ext4 mailing list, it turns out this is not a bug. The acl option is enabled by default on ext4, so it only indicates if you disable it with the noacl option. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJS86kEAAoJEI5FoCIzSKrw6FkH/0sJC8+bJb0j/+jLC+3CsZX8 VnBssZhp2OeMb0WD5hew73NtCIHUZESFRb2681AeGdlLpM1zsdEA4WgnhtGHotEC 8tq04Yg9JiFsPMPLs+bgF5aUeGIV0jQULgBMRSnSOo6L9MY3LTVQ4KtLEPSafsZM 4bg1Vk7Zg45QNrpjaHKMH1PimfFm6WhcslC5FCF03gJcwoo55XND9n79i97ivoCq PJPBpED3fW4R7E7LrX00Fv0Uw5TWeHqfigS/zboMDgPp8B5Yw1bAxiIRwZKWmZsn 2y1wZCrG2cuOP269QDtl9p38Vq8JUENwRTf6Vzkr+h4FmHs4Zs6FzqJ/+kxxjTc= =W5yo -END PGP SIGNATUREEnd Message---
Bug#737938: BUG: unable to handle kernel paging request at 000008000000001c
Package: linux Version: 3.11.10-1 [38587.355263] BUG: unable to handle kernel paging request at 081c [38587.355328] IP: [8110b149] find_get_page+0x29/0x90 [38587.355382] PGD 0 [38587.355401] Oops: [#1] SMP [38587.355430] Modules linked in: tun bnep rfcomm bluetooth rfkill parport_pc ppdev lp parport nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc fuse loop usb_storage ata_generic snd_hda_codec_realtek kvm crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 ablk_helper cryptd lrw gf128mul glue_helper evdev edac_mce_amd psmouse edac_core pcspkr radeon serio_raw fam15h_power k10temp sp5100_tco ttm drm_kms_helper drm i2c_algo_bit wmi button snd_hda_intel sg snd_hda_codec acpi_cpufreq snd_hwdep mperf snd_pcm processor snd_page_alloc snd_seq snd_seq_device snd_timer sr_mod ohci_pci cdrom ohci_hcd snd pata_atiixp i2c_piix4 ehci_pci ehci_hcd i2c_core usbcore alx thermal_sys shpchp usb_common soundcore mdio ext4 crc16 mbcache jbd2 sd_mod crc_t10dif ahci libahci libata scsi_mod microcode [38587.356087] CPU: 2 PID: 4050 Comm: hercules Not tainted 3.11-2-amd64 #1 Debian 3.11.10-1 [38587.356151] Hardware name: Gigabyte Technology Co., Ltd. GA-78LMT-S2P/GA-78LMT-S2P, BIOS F3 10/18/2012 [38587.356223] task: 8801f42b1140 ti: 8801f436c000 task.ti: 8801f436c000 [38587.356281] RIP: 0010:[8110b149] [8110b149] find_get_page+0x29/0x90 [38587.356348] RSP: 0018:8801f436dd80 EFLAGS: 00010246 [38587.356390] RAX: 880101caf718 RBX: 8801e06379f8 RCX: fffa [38587.356445] RDX: 0800 RSI: 000444c4 RDI: [38587.356499] RBP: 000444c4 R08: 0800 R09: 880101caf718 [38587.356554] R10: 0006 R11: 0293 R12: 000e [38587.356608] R13: eac3b920 R14: R15: 8801f4233580 [38587.356664] FS: 7f2c70237700() GS:88020fc8() knlGS: [38587.356726] CS: 0010 DS: ES: CR0: 80050033 [38587.356770] CR2: 081c CR3: 0001f434c000 CR4: 000407e0 [38587.356825] Stack: [38587.356842] 8801e06379f0 000444c4 8110c720 8801e06378a0 [38587.356904] 8801f42335f8 000444d2 810abac2 [38587.356965] 000444c3 000444c4 8801f436de68 [38587.357027] Call Trace: [38587.357053] [8110c720] ? generic_file_aio_read+0x250/0x6f0 [38587.357108] [81169527] ? do_sync_read+0x67/0x90 [38587.357154] [81169ab4] ? vfs_read+0x94/0x160 [38587.357199] [8116a5a3] ? SyS_read+0x43/0xa0 [38587.357244] [81481469] ? system_call_fastpath+0x16/0x1b [38587.357291] Code: 00 00 55 48 89 f5 53 48 8d 5f 08 48 89 ee 48 89 df e8 ac e5 14 00 48 85 c0 49 89 c1 74 34 48 8b 10 48 85 d2 74 26 f6 c2 03 75 45 8b 4a 1c 85 c9 74 d9 8d 71 01 48 8d 7a 1c 89 c8 f0 0f b1 72 1c [38587.357502] RIP [8110b149] find_get_page+0x29/0x90 [38587.357551] RSP 8801f436dd80 [38587.360506] CR2: 081c [38587.363626] ---[ end trace a69c5e0ca2716703 ]--- -- .''`. Stephen Powell : :' : `. `'` `- -- 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/2027073877.834564.1391741777992.javamail.r...@md01.wow.synacor.com
