[Kernel-packages] [Bug 1343109] Re: Ubuntu14.10: CONFIG_SCSI_IPr_TRACE and CONFIG_SCSI_IPR_DUMP are not set in config file
** Package changed: ubuntu = linux-meta (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1343109 Title: Ubuntu14.10: CONFIG_SCSI_IPr_TRACE and CONFIG_SCSI_IPR_DUMP are not set in config file Status in “linux-meta” package in Ubuntu: New Bug description: Problem Description --- CONFIG_SCSI_IPR_TRACE and CONFIG_SCSI_IPR_DUMP are not set in config file in Ubuntu14.10 ---uname output--- ubuntu 14.10 Machine Type = P8 Steps to Reproduce In config file, # CONFIG_SCSI_IPR_TRACE is not set # CONFIG_SCSI_IPR_DUMP is not set They are not set. Ipr device driver couldn't generate dump and trace files for debugging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1343109/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1343032] Re: Ubuntu14.04: /sys/bus/pci/slots show weird numbers as slot_name on PPC64LE
** Package changed: ubuntu = linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1343032 Title: Ubuntu14.04: /sys/bus/pci/slots show weird numbers as slot_name on PPC64LE Status in “linux” package in Ubuntu: New Bug description: ---Problem Description--- root@powerio-le21:/sys/bus/pci/slots# ls -l total 0 drwxr-xr-x 2 root root 0 Jul 15 21:03 1 drwxr-xr-x 2 root root 0 Jul 15 21:03 16 drwxr-xr-x 2 root root 0 Jul 15 21:03 17 drwxr-xr-x 2 root root 0 Jul 15 21:03 8 drwxr-xr-x 2 root root 0 Jul 15 21:03 8-1 drwxr-xr-x 2 root root 0 Jul 15 21:03 9 drwxr-xr-x 2 root root 0 Jul 15 21:03 9-1 In /sys/bus/pci/slots directory, there are bunch of numbers. What these numbers mean? Do we expect slot_name for each pci device here? Some applications read these number as slot_name for pci device. For example, there is a Solstice SAS adapter on this system, when we dump detail information for this adapter, we got Platform Location = 8. IOA Hardware Resource Information Details Manufacturer . . . . . . . . . . . . . . : IBM Machine Type and Model . . . . . . . . . : 57D7001SISIOA Firmware Version . . . . . . . . . . . . : Serial Number. . . . . . . . . . . . . . : 00398091 Part Number. . . . . . . . . . . . . . . : 000E3229 Plant of Manufacturer. . . . . . . . . . : 00UE DRAM Size. . . . . . . . . . . . . . . . : 512 MB Resource Name. . . . . . . . . . . . . . : /dev/sg19 Physical location PCI Address. . . . . . . . . . . . . . . : 0001:04:00.0 Resource Path. . . . . . . . . . . . . . : FE SCSI Host Number . . . . . . . . . . . . : 0 Platform Location. . . . . . . . . . . . : 8 ---uname output--- 3.13.0 Machine Type = P8 ---Steps to Reproduce--- iprconfig-1 In other distros, we see the real location code in this directory. For example: [root@jupiter1-lp1 slots]# pwd /sys/bus/pci/slots drwxr-xr-x. 2 root root 0 Jul 9 12:15 UTMP3.C02.01AC022-P1-C10 drwxr-xr-x. 2 root root 0 Jul 9 12:15 UTMP3.C02.01AC022-P1-C2 drwxr-xr-x. 2 root root 0 Jul 9 12:15 UTMP3.C02.01AC022-P1-C3 drwxr-xr-x. 2 root root 0 Jul 9 12:15 UTMP3.C02.01AC022-P1-C9 or in PowerKVM, It is empty in /sys/bus/pci/slots. In Ubuntu, these random numbers break some code in iprconfig. What is generating these in Ubuntu? Thanks, Wendy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1343032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1340789] Re: Kernel BUG @of/base.c:251 during attach-device operation on Ubuntu 14.10 LE guest
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1340789
Title:
Kernel BUG @of/base.c:251 during attach-device operation on Ubuntu
14.10 LE guest
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
-- Problem Description --
Trying to dynamically add a network device of type virtio to a Ubuntu 14.10
guest running on PowerKVM generates a kernel BUG message. Virsh reports the
operation as successful.
Steps to recreate the problem :
1) Install 14.10 as a Power KVM guest.
2) Install ppc64-diag package
librtas1 1.3.10-1 ppc64el userspace
RTAS library
librtasevent11.3.10-1 ppc64el RTAS events
library
ppc64-diag 2.6.6-0ubuntu1 ppc64el Platform error
log analysis tool and rtas_errd daemon
libservicelog-1.1-1:ppc64el1.1.14-0ubuntu1 ppc64el
Library to create and maintain a database for storing events
servicelog 1.1.12-0ubuntu1 ppc64el Platform
Service/Error Message Database
3) Using a network device definition as mentioned below try a virsh
attach-device operation
On the PowerKVM host :
# cat net
interface type='bridge'
mac address='52:54:00:A0:9D:9a'/
source bridge='virbr0'/
model type='virtio'/
/interface
# virsh attach-device ss_1410_1 net
Device attached successfully
#
Following kernel BUG is observed on the guest
[ 6380.112079] RTAS: event: 1, Type: Unknown, Severity: 1
[ 6380.209844] [ cut here ]
[ 6380.209848] kernel BUG at /build/buildd/linux-3.15.0/drivers/of/base.c:251!
[ 6380.209922] Oops: Exception in kernel mode, sig: 5 [#1]
[ 6380.209963] SMP NR_CPUS=2048 NUMA pSeries
[ 6380.210006] Modules linked in: pseries_rng rtc_generic e1000
[ 6380.210084] CPU: 0 PID: 3642 Comm: drmgr Not tainted 3.15.0-6-generic
#11-Ubuntu
[ 6380.210146] task: c000770968a0 ti: c00079858000 task.ti:
c00079858000
[ 6380.210207] NIP: c0871c24 LR: c0872704 CTR:
c0080ed0
[ 6380.210268] REGS: c0007985b7f0 TRAP: 0700 Not tainted
(3.15.0-6-generic)
[ 6380.210328] MSR: 80029033 SF,EE,ME,IR,DR,RI,LE CR: 24002488
XER: 2000
[ 6380.210473] CFAR: c0872700 SOFTE: 1
[ 6380.210473] GPR00: c0872704 c0007985ba70 c1791188
c4192100
[ 6380.210473] GPR04: 0001 c0007e039fc0 c419ee80
c1aa1188
[ 6380.210473] GPR08: 0002 0001
c453025b
[ 6380.210473] GPR12: 24002482 cfe4
000c
[ 6380.210473] GPR16: 01001e42eeda 0020
10016a00
[ 6380.210473] GPR20: 10016950 100167b0 0001
c0007e039800
[ 6380.210473] GPR24: c0cc0310 c4530009 c00077594f80
c0007fff6d38
[ 6380.210473] GPR28: 0015 c4192100 c1aa01b0
c4192100
[ 6380.211355] NIP [c0871c24] .of_node_add+0x34/0x110
[ 6380.211397] LR [c0872704] .of_attach_node+0xd4/0xf0
[ 6380.211440] Call Trace:
[ 6380.211462] [c0007985ba70] [10016950] 0x10016950 (unreliable)
[ 6380.211525] [c0007985baf0] [c0872704] .of_attach_node+0xd4/0xf0
[ 6380.211633] [c0007985bb70] [c0076420] .ofdt_write+0x590/0x780
[ 6380.211753] [c0007985bc50] [c030727c]
.proc_reg_write+0xac/0x110
[ 6380.211815] [c0007985bcf0] [c0279370] .vfs_write+0xe0/0x260
[ 6380.211876] [c0007985bd90] [c027a034] .SyS_write+0x64/0x110
[ 6380.211939] [c0007985be30] [c0009ffc] syscall_exit+0x0/0x7c
[ 6380.212001] Instruction dump:
[ 6380.212033] fbc1fff0 fbe1fff8 f8010010 f821ff81 7c7f1b78 6000 6000
2fbf
[ 6380.212142] 419e006c 813f0094 69290001 792907e0 0b09 3fc2ffeb
3bdefe60 7fc3f378
[ 6380.212250] ---[ end trace 410b60b95ac50ef5 ]---
[ 6380.214151]
sachin@1410:/var/log$
sachin@1410:/var/log$ cat /etc/issue
Ubuntu Utopic Unicorn (development branch) \n \l
sachin@1410:/var/log$ uname -a
Linux 1410 3.15.0-6-generic #11-Ubuntu SMP Thu Jun 12 00:40:49 UTC 2014
ppc64le ppc64le ppc64le GNU/Linux
sachin@1410:/var/log$
The BUG_ON() it is hitting is likely this one:
int of_node_add(struct device_node *np)
{
int rc = 0;
BUG_ON(!of_node_is_initialized(np));
This appears to be related to commit
75b57ecf9d1d1e17d099ab13b8f48e6e038676be.
This was part of the updates that Grant did to move the device tree
from /proc/to sysfs. As part of this he removed the kref_init call we
made prior to adding the device node.
Attached patch
[Kernel-packages] [Bug 1340789] Re: Kernel BUG @of/base.c:251 during attach-device operation on Ubuntu 14.10 LE guest
** Package changed: ubuntu = linux (Ubuntu)
** Tags added: inin1410
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1340789
Title:
Kernel BUG @of/base.c:251 during attach-device operation on Ubuntu
14.10 LE guest
Status in “linux” package in Ubuntu:
New
Bug description:
-- Problem Description --
Trying to dynamically add a network device of type virtio to a Ubuntu 14.10
guest running on PowerKVM generates a kernel BUG message. Virsh reports the
operation as successful.
Steps to recreate the problem :
1) Install 14.10 as a Power KVM guest.
2) Install ppc64-diag package
librtas1 1.3.10-1 ppc64el userspace
RTAS library
librtasevent11.3.10-1 ppc64el RTAS events
library
ppc64-diag 2.6.6-0ubuntu1 ppc64el Platform error
log analysis tool and rtas_errd daemon
libservicelog-1.1-1:ppc64el1.1.14-0ubuntu1 ppc64el
Library to create and maintain a database for storing events
servicelog 1.1.12-0ubuntu1 ppc64el Platform
Service/Error Message Database
3) Using a network device definition as mentioned below try a virsh
attach-device operation
On the PowerKVM host :
# cat net
interface type='bridge'
mac address='52:54:00:A0:9D:9a'/
source bridge='virbr0'/
model type='virtio'/
/interface
# virsh attach-device ss_1410_1 net
Device attached successfully
#
Following kernel BUG is observed on the guest
[ 6380.112079] RTAS: event: 1, Type: Unknown, Severity: 1
[ 6380.209844] [ cut here ]
[ 6380.209848] kernel BUG at /build/buildd/linux-3.15.0/drivers/of/base.c:251!
[ 6380.209922] Oops: Exception in kernel mode, sig: 5 [#1]
[ 6380.209963] SMP NR_CPUS=2048 NUMA pSeries
[ 6380.210006] Modules linked in: pseries_rng rtc_generic e1000
[ 6380.210084] CPU: 0 PID: 3642 Comm: drmgr Not tainted 3.15.0-6-generic
#11-Ubuntu
[ 6380.210146] task: c000770968a0 ti: c00079858000 task.ti:
c00079858000
[ 6380.210207] NIP: c0871c24 LR: c0872704 CTR:
c0080ed0
[ 6380.210268] REGS: c0007985b7f0 TRAP: 0700 Not tainted
(3.15.0-6-generic)
[ 6380.210328] MSR: 80029033 SF,EE,ME,IR,DR,RI,LE CR: 24002488
XER: 2000
[ 6380.210473] CFAR: c0872700 SOFTE: 1
[ 6380.210473] GPR00: c0872704 c0007985ba70 c1791188
c4192100
[ 6380.210473] GPR04: 0001 c0007e039fc0 c419ee80
c1aa1188
[ 6380.210473] GPR08: 0002 0001
c453025b
[ 6380.210473] GPR12: 24002482 cfe4
000c
[ 6380.210473] GPR16: 01001e42eeda 0020
10016a00
[ 6380.210473] GPR20: 10016950 100167b0 0001
c0007e039800
[ 6380.210473] GPR24: c0cc0310 c4530009 c00077594f80
c0007fff6d38
[ 6380.210473] GPR28: 0015 c4192100 c1aa01b0
c4192100
[ 6380.211355] NIP [c0871c24] .of_node_add+0x34/0x110
[ 6380.211397] LR [c0872704] .of_attach_node+0xd4/0xf0
[ 6380.211440] Call Trace:
[ 6380.211462] [c0007985ba70] [10016950] 0x10016950 (unreliable)
[ 6380.211525] [c0007985baf0] [c0872704] .of_attach_node+0xd4/0xf0
[ 6380.211633] [c0007985bb70] [c0076420] .ofdt_write+0x590/0x780
[ 6380.211753] [c0007985bc50] [c030727c]
.proc_reg_write+0xac/0x110
[ 6380.211815] [c0007985bcf0] [c0279370] .vfs_write+0xe0/0x260
[ 6380.211876] [c0007985bd90] [c027a034] .SyS_write+0x64/0x110
[ 6380.211939] [c0007985be30] [c0009ffc] syscall_exit+0x0/0x7c
[ 6380.212001] Instruction dump:
[ 6380.212033] fbc1fff0 fbe1fff8 f8010010 f821ff81 7c7f1b78 6000 6000
2fbf
[ 6380.212142] 419e006c 813f0094 69290001 792907e0 0b09 3fc2ffeb
3bdefe60 7fc3f378
[ 6380.212250] ---[ end trace 410b60b95ac50ef5 ]---
[ 6380.214151]
sachin@1410:/var/log$
sachin@1410:/var/log$ cat /etc/issue
Ubuntu Utopic Unicorn (development branch) \n \l
sachin@1410:/var/log$ uname -a
Linux 1410 3.15.0-6-generic #11-Ubuntu SMP Thu Jun 12 00:40:49 UTC 2014
ppc64le ppc64le ppc64le GNU/Linux
sachin@1410:/var/log$
The BUG_ON() it is hitting is likely this one:
int of_node_add(struct device_node *np)
{
int rc = 0;
BUG_ON(!of_node_is_initialized(np));
This appears to be related to commit
75b57ecf9d1d1e17d099ab13b8f48e6e038676be.
This was part of the updates that Grant did to move the device tree
from /proc/to sysfs. As part of this he removed the kref_init call we
made prior to adding the device node.
Attached patch
[Kernel-packages] [Bug 1340200] Re: Backport EEH patches to 14.04
** Package changed: ubuntu = linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1340200 Title: Backport EEH patches to 14.04 Status in “linux” package in Ubuntu: New Bug description: Canonical, We would like to have the following patch as part of 14.04. Is it possible to have it before 14.04.02? powerpc/powernv: Fix endianness problems in EEH https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ddf0322a3ffe2d98facc72f255ac5c140b547c72 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1340200/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
