Re: Netconsole scripts for Debian
Hello! It's very important for debugging kernel oops when syslog over network running, because syslog can't send any information on dead kernel. When you haven't persistent kvm/idrac/ilo it's only one way for getting debug information about kernel hang. But why I need to integrate it with initrd? On Wed, Jun 18, 2014 at 10:19 AM, Ritesh Raj Sarraf r...@debian.org wrote: On 06/17/2014 03:00 PM, Pavel Odintsov wrote: Hello, folks! I'm prepared and thoroughly tested scripts for managing netconsole kernel facility in Debian 6/7. Netconsole facility is very useful for debugging kernel bugs. These scripts are inspired by CentOS 6 netconsole scripts in some cases and work in same way. Scripts are written in clean bash. All scripts and configuration you can find here: https://github.com/FastVPSEestiOu/debian_netconsole Yes, it's possible to configure netconsole statically (i.e. as /etc/modprobe.d/netconsole.conf) but it's a bad way because it relies on network configuration (i.e. gateway address, server address) which may be changed and netconsole will not work. I tested both startup option: 1) As /etc/init.d/netconsole 2) As /etc/network/if-up.d/netconsole script IMHO, the first variant is more reliable and convenient for this task. But both variants have some troubles because some network cards (like e1000) call /etc/network/if-up.d and /etc/init.d scripts on network level BEFORE real network initialization. I fixed this issue only by adding fixed timeout in my /etc/init.d/netconsole script. In the same way this issue was fixed in RH. Maybe you can provide more convenient solution? Thank you for any feedback! You should add support for it in initrd. netconsole is more useful at that stage. In real boot, why would one want netconsole if syslog is running. -- Given the large number of mailing lists I follow, I request you to CC me in replies for quicker response -- Sincerely yours, Pavel Odintsov -- 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/calgsdbdzydhbmmbilj5g-frn-ejv3rot+nlwmwuleaaans4...@mail.gmail.com
Re: Netconsole scripts for Debian
Hello! At now I configure netconsole dynamically and got network configuration from ip route command. For getting netconsole server MAC address I use arping to it. But I can generate modprobe configuration file with current configuration and integrate it to initrd. You can check my approach here: 1) On first netconsole script start I can get netconsole collector IP and MAC address (of destination server or gateway for current server) 2) I create /etc/modprobe.d/netconsole.conf configuration with fixed MAC, PORT and IP of netconsole server 3) I add netconsole to initramfs configuration file (/etc/initramfs-tools/modules) with fixed IP/MAC configuration 4) I rebuild initramfs for current kernel: update-initramfs -v -u -k `uname -r` -t 5) On every system run I will check if MAC/IP of destination server was changes I will reconfigure netconsole modprobe.conf file and rebuilt initrd. It's ok? On Wed, Jun 18, 2014 at 1:59 PM, Bjørn Mork bj...@mork.no wrote: Ritesh Raj Sarraf r...@debian.org writes: On 06/17/2014 03:00 PM, Pavel Odintsov wrote: Hello, folks! I'm prepared and thoroughly tested scripts for managing netconsole kernel facility in Debian 6/7. Netconsole facility is very useful for debugging kernel bugs. These scripts are inspired by CentOS 6 netconsole scripts in some cases and work in same way. Scripts are written in clean bash. All scripts and configuration you can find here: https://github.com/FastVPSEestiOu/debian_netconsole Yes, it's possible to configure netconsole statically (i.e. as /etc/modprobe.d/netconsole.conf) but it's a bad way because it relies on network configuration (i.e. gateway address, server address) which may be changed and netconsole will not work. I tested both startup option: 1) As /etc/init.d/netconsole 2) As /etc/network/if-up.d/netconsole script IMHO, the first variant is more reliable and convenient for this task. But both variants have some troubles because some network cards (like e1000) call /etc/network/if-up.d and /etc/init.d scripts on network level BEFORE real network initialization. I fixed this issue only by adding fixed timeout in my /etc/init.d/netconsole script. In the same way this issue was fixed in RH. Maybe you can provide more convenient solution? Thank you for any feedback! You should add support for it in initrd. netconsole is more useful at that stage. In real boot, why would one want netconsole if syslog is running. To debug a driver/kernel crash. netconsole is generally a very useful feature for oops debugging on laptops and other devices with no serial ports. Having some scripts making it simpler to configure sounds like a great idea. Will these depend on configfs being mounted? Or are they only using module parameters? Bjørn -- 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/87ppi6sfma@nemi.mork.no -- Sincerely yours, Pavel Odintsov -- 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/CALgsdbfxY5GDO8rKvMf0k40UqD+34NHFe8=kuo7cmtl-jjk...@mail.gmail.com
Re: Netconsole scripts for Debian
Pavel Odintsov pavel.odint...@gmail.com writes: Hello! At now I configure netconsole dynamically and got network configuration from ip route command. For getting netconsole server MAC address I use arping to it. But I can generate modprobe configuration file with current configuration and integrate it to initrd. You can check my approach here: 1) On first netconsole script start I can get netconsole collector IP and MAC address (of destination server or gateway for current server) The MAC address is optional and should be so in your package too. 2) I create /etc/modprobe.d/netconsole.conf configuration with fixed MAC, PORT and IP of netconsole server Why? You have to load the module from a script anyway, so you could just set the options there. 3) I add netconsole to initramfs configuration file (/etc/initramfs-tools/modules) with fixed IP/MAC configuration 4) I rebuild initramfs for current kernel: update-initramfs -v -u -k `uname -r` -t 5) On every system run I will check if MAC/IP of destination server was changes I will reconfigure netconsole modprobe.conf file and rebuilt initrd. There is already netconsole= cmdline support in initramfs-tools. Whatever you add should integrate nicely with this IMHO. Bjørn -- 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/87ionxq9vt@nemi.mork.no
Processed: block 695563 with 751417
Processing commands for cont...@bugs.debian.org: block 695563 with 751417 Bug #695563 [src:liblinux-prctl-perl] liblinux-prctl-perl: FTBFS on mips and mipsel 695563 was not blocked by any bugs. 695563 was not blocking any bugs. Added blocking bug(s) of 695563: 751417 thanks Stopping processing here. Please contact me if you need assistance. -- 695563: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695563 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.14031901812375.transcr...@bugs.debian.org
Re: Netconsole scripts for Debian
On 06/19/2014 06:39 PM, Pavel Odintsov wrote: It's very important for debugging kernel oops when syslog over network running, because syslog can't send any information on dead kernel. When you haven't persistent kvm/idrac/ilo it's only one way for getting debug information about kernel hang. I don't know what you mean by a dead kernel here. If, say, the e1000e device driver is crashy, irrespective of what you use (netconsole or syslog), there's not much help. In this case, you'll then have to resort to serial console. But why I need to integrate it with initrd? Because it fills the gap in between kernel load to real init start. Imagine a scenario where as soon as the disk driver is loaded, the kernel panics. How would you debug that ? PS: It is just a suggestion. Your patch is still valid, just not very relevant to the use cases. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: OpenPGP digital signature
Bug#747247: linux-image-3.14-1-686-pae: Same issue with linux-image-3.14-1-686-pae
Package: src:linux Version: 3.14.7-1 Followup-For: Bug #747247 Dear Maintainer, I see exactly the same problem as the orignal reporter. I use pm-suspend to suspend. Resume from suspend worked for several years on that system, e.g. 3.13.7-1 works flawless. Thaw from hibernate still works flawless with 3.14 on that system. I followed the procedure described in the Debian wiki, https://wiki.debian.org/Suspend in particular I set the tests in /sys/power/pm_test and all (!) of them successfully resume. While writting the bug report, I am running linux-image 3.13.7-1. I am happy to provide more information if anybody requests something. Thanks, Rainer -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information not available ** Network interface configuration: auto lo iface lo inet loopback allow-hotplug wlan1 eth0 iface eth0 inet dhcp mtu 1492 iface wlan1 inet dhcp wpa-ssid LS6 wpa-key-mgmt *** wpa-psk wpa-driver wext iface ppp0 inet ppp provider klarmobil iface ppp1 inet ppp provider fonic allow-hotplug n900 iface n900 inet static address 192.168.2.14 netmask 255.255.255.0 broadcast 192.168.2.255 up iptables -I INPUT 1 -s 192.168.2.15 -j ACCEPT iface n900wiki inet static address 192.168.2.14 netmask 255.255.255.0 up iptables -A POSTROUTING -t nat -s 192.168.2.15/32 -j MASQUERADE up echo 1 /proc/sys/net/ipv4/ip_forward down iptables -D POSTROUTING -t nat -s 192.168.2.15/32 -j MASQUERADE down echo 0 /proc/sys/net/ipv4/ip_forward ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 82G35 Express DRAM Controller [8086:2980] (rev 03) Subsystem: ASUSTeK Computer Inc. Device [1043:8295] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: access denied Kernel driver in use: agpgart-intel 00:02.0 VGA compatible controller [0300]: Intel Corporation 82G35 Express Integrated Graphics Controller [8086:2982] (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8276] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 44 Region 0: Memory at fe80 (32-bit, non-prefetchable) [size=1M] Region 2: Memory at d000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at cc00 [size=8] Expansion ROM at unassigned [disabled] Capabilities: access denied Kernel driver in use: i915 00:02.1 Display controller [0380]: Intel Corporation 82G35 Express Integrated Graphics Controller [8086:2983] (rev 03) Subsystem: ASUSTeK Computer Inc. Device [1043:8276] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Region 0: Memory at fe90 (32-bit, non-prefetchable) [size=1M] Capabilities: access denied 00:1a.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02) (prog-if 00 [UHCI]) Subsystem: ASUSTeK Computer Inc. Device [1043:8277] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 16 Region 4: I/O ports at c480 [size=32] Capabilities: access denied Kernel driver in use: uhci_hcd 00:1a.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 02) (prog-if 00 [UHCI]) Subsystem: ASUSTeK Computer Inc. Device [1043:8277] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin B routed to IRQ 21 Region 4: I/O ports at c800 [size=32] Capabilities: access denied Kernel driver in use: uhci_hcd 00:1a.2 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 02) (prog-if 00 [UHCI]) Subsystem: ASUSTeK Computer Inc. Device [1043:8277] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz-
Bug#747247: Kernel Module loaded
Here are the kernel modules I have loaded. One commonality is that we have both virtualbox kernel modules, I try to unload them before suspend after the weekend. rd@blackbox:~$ lsmod Module Size Used by zram 17160 2 nfnetlink_queue17364 0 nfnetlink_log 17033 0 nfnetlink 12853 2 nfnetlink_log,nfnetlink_queue autofs426711 2 bnep 17184 2 rfcomm 32155 3 bluetooth 209064 10 bnep,rfcomm rfkill 18387 2 bluetooth pci_stub 12397 1 vboxpci22738 0 vboxnetadp 25431 0 vboxnetflt 27112 0 vboxdrv 236422 3 vboxnetadp,vboxnetflt,vboxpci binfmt_misc12733 1 nfsd 224910 13 auth_rpcgss45764 1 nfsd oid_registry 12387 1 auth_rpcgss nfs_acl12463 1 nfsd nfs 163553 0 lockd 69375 2 nfs,nfsd fscache40686 1 nfs sunrpc198661 23 nfs,nfsd,auth_rpcgss,lockd,nfs_acl fuse 73027 3 hwmon_vid 12364 0 loop 21960 0 firewire_sbp2 17533 0 ppdev 12590 0 lp 12766 0 dm_crypt 22171 0 dm_mod 74768 1 dm_crypt iTCO_wdt 12727 0 iTCO_vendor_support12585 1 iTCO_wdt snd_hda_codec_hdmi 40179 1 snd_hda_codec_realtek45228 1 psmouse76509 0 serio_raw 12737 0 coretemp 12734 0 kvm_intel 129078 0 kvm 317865 1 kvm_intel pcspkr 12531 0 uvcvideo 69768 0 videobuf2_vmalloc 12720 1 uvcvideo videobuf2_memops 12471 1 videobuf2_vmalloc videobuf2_core 34683 1 uvcvideo videodev 90856 2 uvcvideo,videobuf2_core media 17840 2 uvcvideo,videodev snd_usb_audio 100940 3 snd_usbmidi_lib22916 1 snd_usb_audio lpc_ich16616 0 i2c_i801 16845 0 mfd_core 12537 1 lpc_ich parport_serial 12577 0 parport_pc 26004 2 parport_serial parport35213 3 lp,ppdev,parport_pc evdev 17136 21 snd_hda_intel 34991 3 snd_hda_codec 126872 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel snd_hwdep 12906 2 snd_usb_audio,snd_hda_codec snd_pcm_oss40069 0 snd_mixer_oss 21822 1 snd_pcm_oss snd_pcm69595 5 snd_pcm_oss,snd_usb_audio,snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel snd_page_alloc 12882 2 snd_pcm,snd_hda_intel snd_seq_midi 12744 0 snd_seq_midi_event 13124 1 snd_seq_midi snd_rawmidi22283 2 snd_usbmidi_lib,snd_seq_midi snd_seq43336 2 snd_seq_midi_event,snd_seq_midi snd_seq_device 12980 3 snd_seq,snd_rawmidi,snd_seq_midi snd_timer 22010 2 snd_pcm,snd_seq snd46718 26 snd_hda_codec_realtek,snd_pcm_oss,snd_usb_audio,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_usbmidi_lib,snd_hda_codec,snd_hda_intel,snd_seq_device,snd_mixer_oss soundcore 12890 1 snd asus_atk0110 17048 0 i915 647235 3 video 17511 1 i915 drm_kms_helper 35231 1 i915 acpi_cpufreq 12983 0 drm 194499 4 i915,drm_kms_helper i2c_algo_bit 12647 1 i915 i2c_core 23342 6 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,videodev button 12824 1 i915 processor 27635 1 acpi_cpufreq thermal_sys22925 2 video,processor ext4 434217 3 crc16 12327 2 ext4,bluetooth mbcache12938 1 ext4 jbd2 73002 1 ext4 sr_mod 21563 0 cdrom 34540 1 sr_mod sg 25573 0 ata_generic12450 0 hid_generic12369 0 usbhid 39650 0 hid76882 2 hid_generic,usbhid sd_mod 43674 6 crct10dif_generic 12517 1 crc_t10dif 12399 1 sd_mod crct10dif_common 12340 2 crct10dif_generic,crc_t10dif usb_storage43324 1 firewire_ohci 34856 0 ahci 25000 3 libahci22610 1 ahci firewire_core 51113 2 firewire_ohci,firewire_sbp2 crc_itu_t 12331 1 firewire_core floppy 51903 0 pata_jmicron 12443 0 atl1 34792 0 mii12595 1 atl1 ehci_pci 12432 0 uhci_hcd 26364 0 ehci_hcd 47854 1 ehci_pci libata149321 4 ahci,libahci,ata_generic,pata_jmicron scsi_mod
Re: uploading 3.15-exp1
On Wed, Jun 11, 2014 at 11:38:36PM +0200, maximilian attems wrote: On Wed, Jun 11, 2014 at 11:13:10AM +0200, maximilian attems wrote: I will upload today around 22h00 UT to experimental. withdrawing for now, seems to not play well on some test system (X1 Thinkpad gen2). fixed in latest, so will upload tomorrow evening to experimental. -- 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/20140619233233.ga2...@stro.at
