Re: Bug#752878: lsinitramfs: fails to list contents with recent kernels

2014-06-29 Thread Ritesh Raj Sarraf
On 06/27/2014 05:54 PM, Reinhard Karcher wrote:
 I have no problems listing /boot/initrd.img-3.14-1-amd64 using 
 lsinitramfs 0.115. My system is nearly the same, with the exception of 
 udev (204-12 from testing) and kernel  (3.15-trunk-amd64 from 
 experimental)
 


Just came to know of this tool. And it does not work for me either.

11:38:04 rrs@zan:~$ lsinitramfs /boot/initrd.img-3.14-1-amd64
/boot/initrd.img-3.14-1-amd64
11:38:12 rrs@zan:~$


-- 
Given the large number of mailing lists I follow, I request you to CC me
in replies for quicker response



signature.asc
Description: OpenPGP digital signature


Bug#752878: lsinitramfs: fails to list contents with recent kernels

2014-06-29 Thread maximilian attems
On Fri, Jun 27, 2014 at 02:24:33PM +0200, Reinhard Karcher wrote:
 I have no problems listing /boot/initrd.img-3.14-1-amd64 using 
 lsinitramfs 0.115. My system is nearly the same, with the exception of 
 udev (204-12 from testing) and kernel  (3.15-trunk-amd64 from 
 experimental)

The bug has already been reported. It has to do, wether microcode-foo
is installed or not. Happy if anyone cares enough to fix it.

best,

-- 
maks


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140629092005.GA24992@gluino



Bug#748398: linux: Please disable CONFIG_DRM_RADEON_UMS on powerpc

2014-06-29 Thread John Paul Adrian Glaubitz
On 06/27/2014 05:35 PM, John Paul Adrian Glaubitz wrote:
 I will try rebuilding the kernel on the PowerPC with CONFIG_FB_RADEON=m
 and see if it fixes the issue by allowing to blacklist the radeonfb
 module. If yes, I'll send in a kernel patch to change the configuration
 for the powerpc kernel accordingly.

Verified. Setting CONFIG_FB_RADEON=m and rebuilding the kernel fixes the
radeon problem on my Mac Mini G4 PPC permanently. Since there are
several framebuffer drivers compiled into the kernel instead of building
them as modules on the PowerPC kernel, I suggest to build these as
modules as well to avoid the very same problem for other video adapters.

I will provide a proposed diff for the kernel configuration on powerpc
later.

Cheers,

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/53b00463.3060...@physik.fu-berlin.de



Howto build linux-kbuild-3.15?

2014-06-29 Thread Daniel Schröter
Hello,

I have read here that there will be no linux-kbuild for experimental. I
need on for 3.15, but it doesn't work:
[..]
config.status: executing libtool commands
make -j 8 -C userspace
make[5]: Entering directory
'/tmp/linux.3.15/linux-tools-3.15/debian/build/drivers/staging/usbip/userspace'
make -j 8  all-recursive
make[6]: Entering directory
'/tmp/linux.3.15/linux-tools-3.15/debian/build/drivers/staging/usbip/userspace'
make[6]: warning: -jN forced in submake: disabling jobserver mode.
Making all in libsrc
make[7]: Entering directory
'/tmp/linux.3.15/linux-tools-3.15/debian/build/drivers/staging/usbip/userspace/libsrc'
make[7]: warning: -jN forced in submake: disabling jobserver mode.
  CC   libusbip_la-names.lo
  CC   libusbip_la-usbip_host_driver.lo
  CC   libusbip_la-usbip_common.lo
  CC   libusbip_la-vhci_driver.lo
  CC   libusbip_la-sysfs_utils.lo
In file included from
/tmp/linux.3.15/linux-tools-3.15/drivers/staging/usbip/userspace/libsrc/vhci_driver.c:5:0:
/tmp/linux.3.15/linux-tools-3.15/drivers/staging/usbip/userspace/libsrc/usbip_common.h:18:30:
fatal error: ../../uapi/usbip.h: No such file or directory
 #include ../../uapi/usbip.h
  ^
compilation terminated.


Building 3.14 works fine. Can someone upload 3.15 to unstable so we can
get a kbuild package for 3.15? ;-)

I used:
https://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage#The_story_of_linux-tools
as How-To

Thanks!

Bye


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/53b056ab.7070...@gmx.de



Bug#753258: LIO crash

2014-06-29 Thread Matyas Koszik

Package: linux-image-3.2.0-4-amd64
Version: 3.2.57-3+deb7u2
Severity: important


I'm running a redundant storage server pair with DRBD and LIO. On the
secondary node I had some RAID card resets, which triggered DRBD to
disconnect the node - but before that, requests were held for several
seconds in the DRBD layer, which seems to be a problem for LIO (or maybe
the subsequent initiator reconnects - I'm not sure).


warning kernel: [1022062.839595] block drbd0: Remote failed to finish a request 
within ko-count * timeout
info kernel: [1022062.839604] block drbd0: peer( Secondary - Unknown ) conn( 
Connected - Timeout ) pdsk( UpToDate - DUnknown )
info kernel: [1022062.839697] block drbd0: new current UUID 
9E9A652A9DC0D857:7115C7324E030315:8355E6AB18AD03EE:8354E6AB18AD03EF
info kernel: [1022062.839957] block drbd0: asender terminated
info kernel: [1022062.839962] block drbd0: Terminating drbd0_asender
info kernel: [1022062.840629] block drbd0: Connection closed
info kernel: [1022062.840636] block drbd0: conn( Timeout - Unconnected )
info kernel: [1022062.840641] block drbd0: receiver terminated
info kernel: [1022062.840644] block drbd0: Restarting drbd0_receiver
info kernel: [1022062.840647] block drbd0: receiver (re)started
info kernel: [1022062.840651] block drbd0: conn( Unconnected - WFConnection )
emerg kernel: [1022062.840840] general protection fault:  [#1] SMP
warning kernel: [1022062.840986] CPU 5
warning kernel: [1022062.841028] Modules linked in: tcm_loop tcm_fc 
iscsi_target_mod target_core_pscsi target_core_file target_core_iblock 
target_core_mod netconsole parport_pc ppdev bnep rfcomm bluetooth rfkill lp 
parport drbd lru_cache libfc scsi_transport_fc scsi_tgt configfs uinput nfsd 
nfs nfs_acl auth_rpcgss fscache lockd sunrpc nf_conntrack_ipv6 nf_defrag_ipv6 
ip6table_filter ip6_tables nf_conntrack_ipv4 nf_defrag_ipv4 xt_state 
nf_conntrack xt_tcpudp iptable_filter ip_tables x_tables loop snd_pcm 
snd_page_alloc snd_timer ioatdma acpi_cpufreq psmouse i7core_edac iTCO_wdt 
serio_raw mperf edac_core iTCO_vendor_support coretemp joydev evdev snd 
soundcore pcspkr processor i2c_i801 thermal_sys crc32c_intel button ext4 crc16 
jbd2 mbcache dm_mod raid1 md_mod sg sd_mod ses enclosure crc_t10dif usbhid hid 
usb_storage uhci_hcd megaraid_sas ahci libahci libata scsi_mod ehci_hcd usbcore 
usb_common ixgbe mdio igb i2c_algo_bit i2c_core dca [last unloaded: 
target_core_mod]
warning kernel: [1022062.845110]
warning kernel: [1022062.845169] Pid: 5165, comm: iscsi_trx Not tainted 
3.2.0-4-amd64 #1 Debian 3.2.57-3+deb7u2 Supermicro X8DT3/X8DT3
warning kernel: [1022062.845373] RIP: 0010:[a0442696]  
[a0442696] core_tmr_release_req+0x2c/0x66 [target_core_mod]
warning kernel: [1022062.845514] RSP: 0018:880314badd80  EFLAGS: 00010046
warning kernel: [1022062.845581] RAX: 0286 RBX: 8802ce58d7c0 
RCX: dead00100100
warning kernel: [1022062.845668] RDX: dead00200200 RSI: 0286 
RDI: 880329dc45d4
warning kernel: [1022062.845754] RBP: 880329dc45d4 R08: 880314badd60 
R09: 8803155fc040
warning kernel: [1022062.845840] R10: 8803155fc040 R11: 8803155fc040 
R12: 88032f365ae8
warning kernel: [1022062.845927] R13: 8803121d0ac0 R14: 88032f365a08 
R15: 8803121d0ac0
warning kernel: [1022062.846014] FS:  () 
GS:88033fca() knlGS:
warning kernel: [1022062.846103] CS:  0010 DS:  ES:  CR0: 
8005003b
warning kernel: [1022062.846170] CR2: 7f73283f89de CR3: 01605000 
CR4: 06e0
warning kernel: [1022062.846257] DR0:  DR1:  
DR2: 
warning kernel: [1022062.846344] DR3:  DR6: 0ff0 
DR7: 0400
warning kernel: [1022062.846430] Process iscsi_trx (pid: 5165, threadinfo 
880314bac000, task 88032e951780)
emerg kernel: [1022062.846519] Stack:
warning kernel: [1022062.846577]  0282 8803156517c0 
8803151ea800 a0445b6e
warning kernel: [1022062.846813]  88032f365800 a053af12 
0030 0001
warning kernel: [1022062.847046]  88032f365b68 8803151ea800 
0246 88032f365800
emerg kernel: [1022062.847280] Call Trace:
warning kernel: [1022062.847349]  [a0445b6e] ? 
transport_release_cmd+0x21/0x71 [target_core_mod]
warning kernel: [1022062.847442]  [a053af12] ? 
iscsit_close_connection+0x120/0x4bb [iscsi_target_mod]
warning kernel: [1022062.847536]  [a053a948] ? 
iscsi_target_rx_thread+0x18e4/0x1930 [iscsi_target_mod]
warning kernel: [1022062.847630]  [a0539064] ? 
iscsit_thread_get_cpumask+0x88/0x88 [iscsi_target_mod]
warning kernel: [1022062.847723]  [8105f6d9] ? kthread+0x76/0x7e
warning kernel: [1022062.847792]  [81356d74] ? 
kernel_thread_helper+0x4/0x10
warning kernel: [1022062.847862]  [8105f663] ? 
kthread_worker_fn+0x139/0x139
warning