kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #91999
[Bug 1374759] Re: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
That is what is logged into /var/log/kern.log on Vivid i386 running
3.18.0.4 (canonical-kernel-team ppa), and using ext4 partitions for
lts/current/dev ubuntu os, /home is on ext3 (aka sda3) (there is no
other format around on that pc) :
Nov 25 17:54:35 u32 kernel: [29589.094552] EXT4-fs (sda3): unable to read superblock
Nov 25 17:54:35 u32 kernel: [29589.095944] EXT4-fs (sda3): unable to read superblock
Nov 25 17:54:35 u32 kernel: [29589.097316] EXT4-fs (sda3): unable to read superblock
Nov 25 17:54:35 u32 kernel: [29589.098783] FAT-fs (sda3): bogus number of reserved sectors
Nov 25 17:54:35 u32 kernel: [29589.098786] FAT-fs (sda3): Can't find a valid FAT filesystem
Nov 25 17:54:35 u32 kernel: [29589.103508] XFS (sda3): Invalid superblock magic number
Nov 25 17:54:35 u32 kernel: [29589.106556] FAT-fs (sda3): bogus number of reserved sectors
Nov 25 17:54:35 u32 kernel: [29589.106559] FAT-fs (sda3): Can't find a valid FAT filesystem
Nov 25 17:54:35 u32 kernel: [29589.111064] MINIX-fs: unable to read superblock
Nov 25 17:54:35 u32 kernel: [29589.112470] attempt to access beyond end of device
Nov 25 17:54:35 u32 kernel: [29589.112473] sda3: rw=16, want=3, limit=2
Nov 25 17:54:35 u32 kernel: [29589.112476] hfsplus: unable to find HFS+ superblock
Nov 25 17:54:35 u32 kernel: [29589.113914] qnx4: no qnx4 filesystem (no root dir).
Nov 25 17:54:35 u32 kernel: [29589.115265] ufs: You didn't specify the type of your ufs filesystem
Nov 25 17:54:35 u32 kernel: [29589.115265]
Nov 25 17:54:35 u32 kernel: [29589.115265] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
Nov 25 17:54:35 u32 kernel: [29589.115265]
Nov 25 17:54:35 u32 kernel: [29589.115265] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
Nov 25 17:54:35 u32 kernel: [29589.118051] hfs: can't find a HFS filesystem on dev sda3
Nov 25 17:54:55 u32 kernel: [29609.377181] EXT4-fs (sda3): unable to read superblock
Nov 25 17:54:55 u32 kernel: [29609.378565] EXT4-fs (sda3): unable to read superblock
Nov 25 17:54:55 u32 kernel: [29609.379947] EXT4-fs (sda3): unable to read superblock
Nov 25 17:54:55 u32 kernel: [29609.381458] FAT-fs (sda3): bogus number of reserved sectors
Nov 25 17:54:55 u32 kernel: [29609.381462] FAT-fs (sda3): Can't find a valid FAT filesystem
Nov 25 17:54:55 u32 kernel: [29609.386248] XFS (sda3): Invalid superblock magic number
Nov 25 17:54:55 u32 kernel: [29609.389318] FAT-fs (sda3): bogus number of reserved sectors
Nov 25 17:54:55 u32 kernel: [29609.389322] FAT-fs (sda3): Can't find a valid FAT filesystem
Nov 25 17:54:55 u32 kernel: [29609.395129] MINIX-fs: unable to read superblock
Nov 25 17:54:55 u32 kernel: [29609.396744] attempt to access beyond end of device
Nov 25 17:54:55 u32 kernel: [29609.396748] sda3: rw=16, want=3, limit=2
Nov 25 17:54:55 u32 kernel: [29609.396750] hfsplus: unable to find HFS+ superblock
Nov 25 17:54:55 u32 kernel: [29609.398259] qnx4: no qnx4 filesystem (no root dir).
Nov 25 17:54:55 u32 kernel: [29609.399623] ufs: You didn't specify the type of your ufs filesystem
Nov 25 17:54:55 u32 kernel: [29609.399623]
Nov 25 17:54:55 u32 kernel: [29609.399623] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
Nov 25 17:54:55 u32 kernel: [29609.399623]
Nov 25 17:54:55 u32 kernel: [29609.399623] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
Nov 25 17:54:55 u32 kernel: [29609.402391] hfs: can't find a HFS filesystem on dev sda3
************************ NOTE**********************
these logged lines are written when the system is shuted down by the user: running a gnome-shell session and hitting the 'shutdown' gui icon from the 'shutdown' icon on top right tray.
Why all that mess when a system is closed ? (system booted with systemd-boot)
Looks like a package (os-prober ? or else) is running some 'starting' boot routines it never should be calling at closed time.
****************************************************
What happen on next cold boot ?
A KERNEL PANIC
Nov 26 07:36:26 u32 kernel: [ 42.058213] nvidia 0000:06:00.0: irq 32 for MSI/MSI-X
Nov 26 07:36:27 u32 kernel: [ 42.806927] ------------[ cut here ]------------
Nov 26 07:36:27 u32 kernel: [ 42.806948] WARNING: CPU: 3 PID: 818 at /build/buildd/linux-3.18.0/drivers/gpu/drm/drm_ioctl.c:143 drm_setversion+0x185/0x190 [drm]()
Nov 26 07:36:27 u32 kernel: [ 42.807020] No drm_driver.set_busid() implementation provided by nv_drm_driver [nvidia]. Use drm_dev_set_unique() to set the unique name explicitly.
Nov 26 07:36:27 u32 kernel: [ 42.807021] Modules linked in: binfmt_misc ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack iptable_filter ip_tables x_tables nvidia(POE) drm serio_raw lpc_ich shpchp snd_hda_codec_hdmi 8250_fintek coretemp kvm_intel asus_atk0110 kvm snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm snd_seq_midi i82975x_edac edac_core snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore mac_hid parport_pc ppdev lp parport autofs4 hid_generic usbhid hid pata_acpi ahci pata_jmicron libahci sky2
Nov 26 07:36:27 u32 kernel: [ 42.807074] CPU: 3 PID: 818 Comm: Xorg Tainted: P OE 3.18.0-4-generic #5-Ubuntu
Nov 26 07:36:27 u32 kernel: [ 42.807076] Hardware name: ASUSTEK COMPUTER INC P5W DH Deluxe/P5W DH Deluxe, BIOS 3002 07/22/2010
Nov 26 07:36:27 u32 kernel: [ 42.807078] 00000003 00000000 f6859dd4 c16c3ad6 f6859e18 f6859e08 c105f9b2 f84af000
Nov 26 07:36:27 u32 kernel: [ 42.807083] f6859e34 00000332 f84aef64 0000008f f848a7e5 0000008f f848a7e5 f6859e8c
Nov 26 07:36:27 u32 kernel: [ 42.807088] f6612400 ffffffea f6859e20 c105fa03 00000009 f6859e18 f84af000 f6859e34
Nov 26 07:36:27 u32 kernel: [ 42.807094] Call Trace:
Nov 26 07:36:27 u32 kernel: [ 42.807101] [<c16c3ad6>] dump_stack+0x41/0x52
Nov 26 07:36:27 u32 kernel: [ 42.807105] [<c105f9b2>] warn_slowpath_common+0x82/0xa0
Nov 26 07:36:27 u32 kernel: [ 42.807117] [<f848a7e5>] ? drm_setversion+0x185/0x190 [drm]
Nov 26 07:36:27 u32 kernel: [ 42.807127] [<f848a7e5>] ? drm_setversion+0x185/0x190 [drm]
Nov 26 07:36:27 u32 kernel: [ 42.807130] [<c105fa03>] warn_slowpath_fmt+0x33/0x40
Nov 26 07:36:27 u32 kernel: [ 42.807140] [<f848a7e5>] drm_setversion+0x185/0x190 [drm]
Nov 26 07:36:27 u32 kernel: [ 42.807151] [<f848a660>] ? drm_noop+0x40/0x40 [drm]
Nov 26 07:36:27 u32 kernel: [ 42.807161] [<f848a24c>] drm_ioctl+0x2bc/0x560 [drm]
Nov 26 07:36:27 u32 kernel: [ 42.807171] [<f848a660>] ? drm_noop+0x40/0x40 [drm]
Nov 26 07:36:27 u32 kernel: [ 42.807176] [<c11b9219>] ? user_path_at_empty+0x49/0x80
Nov 26 07:36:27 u32 kernel: [ 42.807180] [<c133b786>] ? _copy_to_user+0x26/0x30
Nov 26 07:36:27 u32 kernel: [ 42.807183] [<c11b9301>] ? do_filp_open+0x31/0x90
Nov 26 07:36:27 u32 kernel: [ 42.807193] [<f8489f90>] ? drm_getmap+0xc0/0xc0 [drm]
Nov 26 07:36:27 u32 kernel: [ 42.807196] [<c11bb9d2>] do_vfs_ioctl+0x302/0x510
Nov 26 07:36:27 u32 kernel: [ 42.807199] [<c11b84ed>] ? final_putname+0x1d/0x40
Nov 26 07:36:27 u32 kernel: [ 42.807203] [<c11b84ed>] ? final_putname+0x1d/0x40
Nov 26 07:36:27 u32 kernel: [ 42.807205] [<c11b8734>] ? putname+0x24/0x40
Nov 26 07:36:27 u32 kernel: [ 42.807209] [<c11a89ad>] ? do_sys_open+0x19d/0x260
Nov 26 07:36:27 u32 kernel: [ 42.807212] [<c11bbc40>] SyS_ioctl+0x60/0x90
Nov 26 07:36:27 u32 kernel: [ 42.807216] [<c16ca41f>] sysenter_do_call+0x12/0x12
Nov 26 07:36:27 u32 kernel: [ 42.807218] ---[ end trace 02c9e0eed197c80a ]---
Nov 26 07:36:27 u32 kernel: [ 42.807221] ------------[ cut here ]------------
Nov 26 07:36:27 u32 kernel: [ 42.807231] WARNING: CPU: 3 PID: 818 at /build/buildd/linux-3.18.0/drivers/gpu/drm/drm_ioctl.c:143 drm_setversion+0x185/0x190 [drm]()
Nov 26 07:36:27 u32 kernel: [ 42.807283] No drm_driver.set_busid() implementation provided by nv_drm_driver [nvidia]. Use drm_dev_set_unique() to set the unique name explicitly.
Nov 26 07:36:27 u32 kernel: [ 42.807284] Modules linked in: binfmt_misc ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack iptable_filter ip_tables x_tables nvidia(POE) drm serio_raw lpc_ich shpchp snd_hda_codec_hdmi 8250_fintek coretemp kvm_intel asus_atk0110 kvm snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm snd_seq_midi i82975x_edac edac_core snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore mac_hid parport_pc ppdev lp parport autofs4 hid_generic usbhid hid pata_acpi ahci pata_jmicron libahci sky2
Nov 26 07:36:27 u32 kernel: [ 42.807328] CPU: 3 PID: 818 Comm: Xorg Tainted: P W OE 3.18.0-4-generic #5-Ubuntu
Nov 26 07:36:27 u32 kernel: [ 42.807330] Hardware name: ASUSTEK COMPUTER INC P5W DH Deluxe/P5W DH Deluxe, BIOS 3002 07/22/2010
Nov 26 07:36:27 u32 kernel: [ 42.807332] 00000003 00000000 f6859dd4 c16c3ad6 f6859e18 f6859e08 c105f9b2 f84af000
Nov 26 07:36:27 u32 kernel: [ 42.807337] f6859e34 00000332 f84aef64 0000008f f848a7e5 0000008f f848a7e5 f6859e8c
Nov 26 07:36:27 u32 kernel: [ 42.807342] f6612400 ffffffea f6859e20 c105fa03 00000009 f6859e18 f84af000 f6859e34
Nov 26 07:36:27 u32 kernel: [ 42.807347] Call Trace:
Nov 26 07:36:27 u32 kernel: [ 42.807350] [<c16c3ad6>] dump_stack+0x41/0x52
Nov 26 07:36:27 u32 kernel: [ 42.807354] [<c105f9b2>] warn_slowpath_common+0x82/0xa0
Nov 26 07:36:27 u32 kernel: [ 42.807364] [<f848a7e5>] ? drm_setversion+0x185/0x190 [drm]
Nov 26 07:36:27 u32 kernel: [ 42.807374] [<f848a7e5>] ? drm_setversion+0x185/0x190 [drm]
Nov 26 07:36:27 u32 kernel: [ 42.807377] [<c105fa03>] warn_slowpath_fmt+0x33/0x40
Nov 26 07:36:27 u32 kernel: [ 42.807388] [<f848a7e5>] drm_setversion+0x185/0x190 [drm]
Nov 26 07:36:27 u32 kernel: [ 42.807398] [<f848a660>] ? drm_noop+0x40/0x40 [drm]
Nov 26 07:36:27 u32 kernel: [ 42.807408] [<f848a24c>] drm_ioctl+0x2bc/0x560 [drm]
Nov 26 07:36:27 u32 kernel: [ 42.807418] [<f848a660>] ? drm_noop+0x40/0x40 [drm]
Nov 26 07:36:27 u32 kernel: [ 42.807422] [<c11b9219>] ? user_path_at_empty+0x49/0x80
Nov 26 07:36:27 u32 kernel: [ 42.807426] [<c133b786>] ? _copy_to_user+0x26/0x30
Nov 26 07:36:27 u32 kernel: [ 42.807428] [<c11b9301>] ? do_filp_open+0x31/0x90
Nov 26 07:36:27 u32 kernel: [ 42.807438] [<f8489f90>] ? drm_getmap+0xc0/0xc0 [drm]
Nov 26 07:36:27 u32 kernel: [ 42.807441] [<c11bb9d2>] do_vfs_ioctl+0x302/0x510
Nov 26 07:36:27 u32 kernel: [ 42.807444] [<c11b84ed>] ? final_putname+0x1d/0x40
Nov 26 07:36:27 u32 kernel: [ 42.807447] [<c11b84ed>] ? final_putname+0x1d/0x40
Nov 26 07:36:27 u32 kernel: [ 42.807450] [<c11b8734>] ? putname+0x24/0x40
Nov 26 07:36:27 u32 kernel: [ 42.807453] [<c11a89ad>] ? do_sys_open+0x19d/0x260
Nov 26 07:36:27 u32 kernel: [ 42.807456] [<c11bbc40>] SyS_ioctl+0x60/0x90
Nov 26 07:36:27 u32 kernel: [ 42.807459] [<c16ca41f>] sysenter_do_call+0x12/0x12
Nov 26 07:36:27 u32 kernel: [ 42.807461] ---[ end trace 02c9e0eed197c80b ]---
Nov 26 07:36:34 u32 kernel: [ 49.790074] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
so a new cold boot is needed, and boots fine that time.
****************** Comment for Andy (apw)************
that issue is more serious than you think: simply silencing os-prober is not what is needed.
as said previously, it seems that some 'booting' processes are called at shutdown time, and should never be ran.
That kernel panic at 'the next cold boot' is not new and has been met
since at least the latest LTS release.
--
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/1374759
Title:
>>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is
ufstype=old
Status in “linux” package in Ubuntu:
Triaged
Status in “os-prober” package in Ubuntu:
Confirmed
Bug description:
[ 556.734157] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
[ 556.746268] JFS: nTxBlock = 8192, nTxLock = 65536
[ 556.763789] ntfs: driver 2.1.30 [Flags: R/O MODULE].
[ 556.792231] QNX4 filesystem 0.2.3 registered.
[ 557.922469] EXT4-fs (sda4): unable to read superblock
[ 557.925868] EXT4-fs (sda4): unable to read superblock
[ 557.928967] EXT4-fs (sda4): unable to read superblock
[ 557.931784] FAT-fs (sda4): bogus number of reserved sectors
[ 557.931791] FAT-fs (sda4): Can't find a valid FAT filesystem
[ 557.946740] XFS (sda4): Invalid superblock magic number
[ 557.951904] FAT-fs (sda4): bogus number of reserved sectors
[ 557.951911] FAT-fs (sda4): Can't find a valid FAT filesystem
[ 557.959099] MINIX-fs: unable to read superblock
[ 557.965712] attempt to access beyond end of device
[ 557.965721] sda4: rw=16, want=3, limit=2
[ 557.965725] hfsplus: unable to find HFS+ superblock
[ 557.968487] qnx4: no qnx4 filesystem (no root dir).
[ 557.971203] You didn't specify the type of your ufs filesystem
mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep
|nextstep-cd|openstep ...
>>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[ 557.974459] hfs: can't find a HFS filesystem on dev sda4
[ 564.034208] EXT4-fs (sda4): unable to read superblock
[ 564.040322] EXT4-fs (sda4): unable to read superblock
[ 564.043485] EXT4-fs (sda4): unable to read superblock
[ 564.047076] FAT-fs (sda4): bogus number of reserved sectors
[ 564.047083] FAT-fs (sda4): Can't find a valid FAT filesystem
[ 564.059578] XFS (sda4): Invalid superblock magic number
[ 564.064473] FAT-fs (sda4): bogus number of reserved sectors
[ 564.064489] FAT-fs (sda4): Can't find a valid FAT filesystem
[ 564.072080] MINIX-fs: unable to read superblock
[ 564.074564] attempt to access beyond end of device
[ 564.074571] sda4: rw=16, want=3, limit=2
[ 564.074576] hfsplus: unable to find HFS+ superblock
[ 564.076688] qnx4: no qnx4 filesystem (no root dir).
[ 564.078847] You didn't specify the type of your ufs filesystem
mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep
|nextstep-cd|openstep ...
>>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[ 564.080902] hfs: can't find a HFS filesystem on dev sda4
[ 570.554296] EXT4-fs (sda4): unable to read superblock
[ 570.557647] EXT4-fs (sda4): unable to read superblock
[ 570.560516] EXT4-fs (sda4): unable to read superblock
[ 570.563451] FAT-fs (sda4): bogus number of reserved sectors
[ 570.563460] FAT-fs (sda4): Can't find a valid FAT filesystem
[ 570.574953] XFS (sda4): Invalid superblock magic number
[ 570.580796] FAT-fs (sda4): bogus number of reserved sectors
[ 570.580806] FAT-fs (sda4): Can't find a valid FAT filesystem
[ 570.588340] MINIX-fs: unable to read superblock
[ 570.590983] attempt to access beyond end of device
[ 570.590993] sda4: rw=16, want=3, limit=2
[ 570.590999] hfsplus: unable to find HFS+ superblock
[ 570.593321] qnx4: no qnx4 filesystem (no root dir).
[ 570.595556] You didn't specify the type of your ufs filesystem
mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep
|nextstep-cd|openstep ...
>>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[ 570.597775] hfs: can't find a HFS filesystem on dev sda4
[ 576.795014] EXT4-fs (sda4): unable to read superblock
[ 576.797554] EXT4-fs (sda4): unable to read superblock
[ 576.800063] EXT4-fs (sda4): unable to read superblock
[ 576.802647] FAT-fs (sda4): bogus number of reserved sectors
[ 576.802655] FAT-fs (sda4): Can't find a valid FAT filesystem
[ 576.813305] XFS (sda4): Invalid superblock magic number
[ 576.820257] FAT-fs (sda4): bogus number of reserved sectors
[ 576.820276] FAT-fs (sda4): Can't find a valid FAT filesystem
[ 576.830945] MINIX-fs: unable to read superblock
[ 576.834108] attempt to access beyond end of device
[ 576.834119] sda4: rw=16, want=3, limit=2
[ 576.834125] hfsplus: unable to find HFS+ superblock
[ 576.837264] qnx4: no qnx4 filesystem (no root dir).
[ 576.840408] You didn't specify the type of your ufs filesystem
mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep
|nextstep-cd|openstep ...
>>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[ 576.843535] hfs: can't find a HFS filesystem on dev sda4
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-18-generic 3.16.0-18.25
ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
Uname: Linux 3.16.0-18-generic x86_64
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: caravena 2117 F.... pulseaudio
CurrentDesktop: GNOME
Date: Sat Sep 27 10:39:43 2014
HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
InstallationDate: Installed on 2014-09-25 (2 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-18-generic root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.16.0-18-generic N/A
linux-backports-modules-3.16.0-18-generic N/A
linux-firmware 1.134
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1374759/+subscriptions
References
