Latest kernels
Fedora 29 XFCE4 wm, fresh install Latest 4.19.9 and 4.19.10 kernels, after update booted into blank screen, I thought, that it is, because of darkest time here, 5h20min daylight :) :). But found somewhere from net solution. I have laptop HP 15-bw021na, with AMD 4 core processor, AMDGPU. Had to add into linux cmdline AMDGPU.DC=0, after that booted OK. Now, something with these "new" kernels is going wrong? because with 4.19.5 kernel does not need amdgpu.dc=0 command. So, if someone counter same problem, this might help. Happy Holidays Jarmo ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: fedora 18 and lsi latest kernels don't boot
On Sat Mar 30 16:41:10 UTC 2013 Reindl Harald wrote: make a bugreport and consider use software-RAID which works damned well and makes you independent of the hardware Unfortunately I have not great control on the hw... Opened bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=947255 After updating the system, if I boot with original stock f18 kernel is ok, while newer ones drive to emergency shell... From lshw I see ... *-scsi description: SCSI storage controller product: SAS1064ET PCI-Express Fusion-MPT SAS vendor: LSI Logic / Symbios Logic physical id: 0 bus info: pci@:04:00.0 logical name: scsi1 version: 08 width: 64 bits clock: 33MHz capabilities: scsi pm pciexpress msi msix bus_master cap_list rom scsi-host configuration: driver=mptsas latency=0 resources: irq:30 ioport:1000(size=256) memory:b191-b1913fff memory:b190-b190 memory:b1c0-b1df *-disk description: SCSI Disk product: Multi-Flex vendor: Intel physical id: 0.0.0 bus info: scsi@1:0.0.0 logical name: /dev/sda version: 0308 serial: 4C20202078164A5806D0806B size: 20GiB (21GB) capacity: 20GiB (21GB) capabilities: 15000rpm partitioned partitioned:dos configuration: ansiversion=5 sectorsize=512 signature=00020619 ... Gianluca -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
fedora 18 and lsi latest kernels don't boot
Hello, default 3.6.10-4.fc18.x86_64 f18 install kernel is ok. Instead both kernel-3.8.4-202.fc18 and 3.7.9-205.fc18 stop at boot with error and systemd emergency shell and journalctl shows like in this picture: https://docs.google.com/file/d/0BwoPbcrMv8mvd0Z0bExhTDYxQjQ/edit?usp=sharing any hint? I suspect raid controller: The same thing happens on two intel blades after I install f18 and run a yum update. [root@management02 ~]# cat /proc/cmdline BOOT_IMAGE=/vmlinuz-3.6.10-4.fc18.x86_64 root=/dev/mapper/fedora_management02-root ro nomodeset rd.md=0 rd.lvm.lv=fedora_management02/root rd.dm=0 rd.lvm.lv=fedora_management02/swap rd.luks=0 vconsole.keymap=us rhgb quiet [root@management02 ~]# lspci|grep SCSI 04:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1064ET PCI-Express Fusion-MPT SAS (rev 08) [root@management02 ~]# cat /proc/mpt/version mptlinux-3.04.20 Fusion MPT base driver Fusion MPT SAS host driver [root@management02 ~]# cat /proc/mpt/summary ioc0: LSISAS1064E B3, FwRev=011eh, Ports=1, MaxQ=277, IRQ=30 processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU X5570 @ 2.93GHz stepping: 5 microcode : 0x11 cpu MHz : 1596.000 cache size : 8192 KB physical id : 0 siblings: 8 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ida dtherm tpr_shadow vnmi flexpriority ept vpid bogomips: 5852.54 clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ... Thanks in advance, Gianluca -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: fedora 18 and lsi latest kernels don't boot
Am 30.03.2013 17:35, schrieb Gianluca Cecchi: default 3.6.10-4.fc18.x86_64 f18 install kernel is ok. Instead both kernel-3.8.4-202.fc18 and 3.7.9-205.fc18 stop at boot with error and systemd emergency shell and journalctl shows like in this picture: https://docs.google.com/file/d/0BwoPbcrMv8mvd0Z0bExhTDYxQjQ/edit?usp=sharing any hint? I suspect raid controller: The same thing happens on two intel blades after I install f18 and run a yum update. [root@management02 ~]# lspci|grep SCSI 04:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1064ET PCI-Express Fusion-MPT SAS (rev 08) [root@management02 ~]# cat /proc/mpt/version mptlinux-3.04.20 Fusion MPT base driver Fusion MPT SAS host driver make a bugreport and consider use software-RAID which works damned well and makes you independent of the hardware up to move the whole RAID disks in another machine like the one below has a older bitwise-clone on the other side of the city with different hardware [root@srv-rhsoft:~]$ uname -r 3.8.5-201.fc18.x86_64 #1 SMP Thu Mar 28 21:01:19 UTC 2013 - /dev/md0: Version : 1.0 Creation Time : Wed Jun 8 13:10:48 2011 Raid Level : raid1 Array Size : 511988 (500.07 MiB 524.28 MB) Used Dev Size : 511988 (500.07 MiB 524.28 MB) Raid Devices : 4 Total Devices : 4 Persistence : Superblock is persistent Update Time : Fri Mar 29 16:38:00 2013 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Name : localhost.localdomain:0 UUID : 1d691642:baed26df:1d197496:4fb00ff8 Events : 476 Number Major Minor RaidDevice State 0 8 490 active sync /dev/sdd1 5 8 331 active sync /dev/sdc1 4 812 active sync /dev/sda1 3 8 173 active sync /dev/sdb1 - /dev/md1: Version : 1.1 Creation Time : Wed Jun 8 13:10:52 2011 Raid Level : raid10 Array Size : 30716928 (29.29 GiB 31.45 GB) Used Dev Size : 15358464 (14.65 GiB 15.73 GB) Raid Devices : 4 Total Devices : 4 Persistence : Superblock is persistent Intent Bitmap : Internal Update Time : Sat Mar 30 17:39:12 2013 State : active Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Layout : near=2 Chunk Size : 512K Name : localhost.localdomain:1 UUID : b7475879:c95d9a47:c5043c02:0c5ae720 Events : 11654 Number Major Minor RaidDevice State 0 8 500 active sync /dev/sdd2 5 8 341 active sync /dev/sdc2 4 822 active sync /dev/sda2 3 8 183 active sync /dev/sdb2 - /dev/md2: Version : 1.1 Creation Time : Wed Jun 8 13:10:56 2011 Raid Level : raid10 Array Size : 3875222528 (3695.70 GiB 3968.23 GB) Used Dev Size : 1937611264 (1847.85 GiB 1984.11 GB) Raid Devices : 4 Total Devices : 4 Persistence : Superblock is persistent Intent Bitmap : Internal Update Time : Sat Mar 30 17:39:05 2013 State : active Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Layout : near=2 Chunk Size : 512K Name : localhost.localdomain:2 UUID : ea253255:cb915401:f32794ad:ce0fe396 Events : 268057 Number Major Minor RaidDevice State 0 8 510 active sync /dev/sdd3 5 8 351 active sync /dev/sdc3 4 832 active sync /dev/sda3 3 8 193 active sync /dev/sdb3 - Personalities : [raid10] [raid1] md1 : active raid10 sdb2[3] sda2[4] sdd2[0] sdc2[5] 30716928 blocks super 1.1 512K chunks 2 near-copies [4/4] [] bitmap: 1/1 pages [4KB], 65536KB chunk md0 : active raid1 sda1[4] sdb1[3] sdd1[0] sdc1[5] 511988 blocks super 1.0 [4/4] [] md2 : active raid10 sda3[4] sdb3[3] sdd3[0] sdc3[5] 3875222528 blocks super 1.1 512K chunks 2 near-copies [4/4] [] bitmap: 3/29 pages [12KB], 65536KB chunk unused devices: none - signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a
Re: Strange panic with latest kernels and/or updates
On Tue, Nov 6, 2012 at 6:13 PM, Bruno Wolff III br...@wolff.to wrote: Yum can get a 3.6.6 update from: http://koji.fedoraproject.org/**koji/buildinfo?buildID=364595http://koji.fedoraproject.org/koji/buildinfo?buildID=364595 I meant that I had no packages in yum update queue, so my system was full updated and all packages with released fixes applied. BTW: in old days you could put /forcefsck file and next reboot force a file system check. This was parsed by rc.sysinit that I see there is not anymore in F17. Found nothing related to this neither in /etc/rc.d nor in /etc/systemd. Ho can one force a full fsck if in my case has 4-5 lock down in short times (I saw in the past for example when faulting dimms, that strange things could happen until a full fsck...) Gianluca -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Strange panic with latest kernels and/or updates
Hello, it happens even after booting the system in a few minutes if these conditions are met - manually mount a windows share Its entry in fstab is something like this \\ /myshare cifs noauto,_netdev,credentials=/etc/smbcred,uid=1000,workgroup=YYY 0 0 - go inside the share under /myshare - try to run scp of a file over another server sometimes completes, but quite soon I get panic As soon as I type scp file and for example also if I only use tab+tab to expand filename bash completion I get a panic as in https://www.dropbox.com/s/xgoeemnbln98xqi/20121106_102138.jpg The screenshot has been taken going to console and shows bash as a process, but tipically I see awk in my previous 3 tests (don't know where awk comes into place I didn't have one...) It happened 4 times reproducing this kind of operation, while now the system is up since 1hour without mounting the share and is ok. Anyone observing something similar? I don't know against what to bugzilla... Thanks, Gianluca -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Strange panic with latest kernels and/or updates
System is Fedora 17 x86_64. Reproduced with both 3.6.3-1.fc17.x86_64 and kernel-3.6.2-4.fc17.x86_64 yum update shows no package to be updated bash-4.2.37-2.fc17.x86_64 gawk-4.0.1-1.fc17.x86_64 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Strange panic with latest kernels and/or updates
On Tue, Nov 06, 2012 at 11:21:58 +0100, Gianluca Cecchi gianluca.cec...@gmail.com wrote: System is Fedora 17 x86_64. Reproduced with both 3.6.3-1.fc17.x86_64 and kernel-3.6.2-4.fc17.x86_64 yum update shows no package to be updated Yum can get a 3.6.6 update from: http://koji.fedoraproject.org/koji/buildinfo?buildID=364595 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Linux software RAID does not work with latest kernels
With the latest kernel to Fedora 16 x86_64 starting with kernel-3.2.9-2.fc16.x86_64, Linux software RAID no longer works. kernel-3.2.10-3.fc16.x86_64 has the same issue. kernel-3.2.7-1.fc16.x86_64 works just fine. I just didn't notice it until a recent reboot into 3.2.9 and 3.2.10. With the 3.2.9 and 3.2.10 kernel for Fedora 16, the system can't boot so it prompts for root's password to login for repairs. The errors on the screen upon login and exiting to 'default' mode is: device-mapper: table: 253.4: multipath: error getting device /boot isn't mounted. This is my fstab file: /dev/mapper/vg_home-lv_root / ext4 defaults1 1 UUID=a3141701-455a-4835-8701-0f25ed4ac761 /boot ext4defaults1 2 /dev/mapper/vg_home-lv_home /home ext4 defaults1 2 /dev/mapper/vg_home-lv_swap swapswap defaults0 0 tmpfs /dev/shmtmpfs defaults0 0 devpts /dev/ptsdevpts gid=5,mode=620 0 0 sysfs /syssysfs defaults0 0 proc/proc procdefaults0 0 LABEL=data1 /data1 xfs defaults,noatime 0 0 It appears all devices managed by LVM and Linux software RAID are having issues mounted. Again, kernel 3.2.7 for FC16 works just fine, but antyhing after that doesn't work. dmidecode to get a better idea what this hardware is: # dmidecode 2.11 SMBIOS 2.4 present. 40 structures occupying 1217 bytes. Table at 0x000F0100. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: Award Software International, Inc. Version: F12 Release Date: 06/18/2009 Address: 0xE Runtime Size: 128 kB ROM Size: 1024 kB Characteristics: PCI is supported PNP is supported APM is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported 5.25/360 kB floppy services are supported (int 13h) 5.25/1.2 MB floppy services are supported (int 13h) 3.5/720 kB floppy services are supported (int 13h) 3.5/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) CGA/mono video services are supported (int 10h) ACPI is supported USB legacy is supported LS-120 boot is supported ATAPI Zip drive boot is supported BIOS boot specification is supported Targeted content distribution is supported Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Gigabyte Technology Co., Ltd. Product Name: P35C-DS3R Version: Serial Number: UUID: ----001A4D46CBAA Wake-up Type: Power Switch SKU Number: Family: Handle 0x0002, DMI type 2, 8 bytes Base Board Information Manufacturer: Gigabyte Technology Co., Ltd. Product Name: P35C-DS3R Version: Serial Number: Handle 0x0003, DMI type 3, 17 bytes Chassis Information Manufacturer: Gigabyte Technology Co., Ltd. Type: Desktop Lock: Not Present Version: Serial Number: Asset Tag: Boot-up State: Unknown Power Supply State: Unknown Thermal State: Unknown Security Status: Unknown OEM Information: 0x Handle 0x0004, DMI type 4, 35 bytes Processor Information Socket Designation: Socket 775 Type: Central Processor Family: Other Manufacturer: Intel ID: F7 06 00 00 FF FB EB BF Signature: Type 0, Family 6, Model 15, Stepping 7 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension)
Re: Linux software RAID does not work with latest kernels
On Wed, Mar 21, 2012 at 9:50 AM, Fong Vang sudoy...@gmail.com wrote: With the latest kernel to Fedora 16 x86_64 starting with kernel-3.2.9-2.fc16.x86_64, Linux software RAID no longer works. kernel-3.2.10-3.fc16.x86_64 has the same issue. kernel-3.2.7-1.fc16.x86_64 works just fine. I just didn't notice it until a recent reboot into 3.2.9 and 3.2.10. With the 3.2.9 and 3.2.10 kernel for Fedora 16, the system can't boot so it prompts for root's password to login for repairs. The errors on the screen upon login and exiting to 'default' mode is: I've got 6 different machine w/ software RAID running w/ 3.2.10 with hardware ranging from top-of-the-Line Intel Xeon w/ Intel SATA chipset to low-end AMD machines w/ nVidia chipset. Your issue is most likely hardware and/or configuration specific. 1. Do you see non software RAID partitions on all the drives? 2. What's your disk configuration (sda, 4 paritions, two RAID, etc). 3. What's the $ fdisk -l output of each device? 4. Can you start the RAID by hand using mdadm? - Gilboa -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
