[Bug 491044] Re: Inconsistent attributes reported over time by smartctl
Unfortunately as this bug is almost four years old, it is not feasible to test for reproducibility at this point: * The motherboard failed. Changed, but as you can probably guess the CPU, RAM, RAM controller, and SATA controllers were all changed & upgraded with it. * Operating system upgraded from 9.10 to 10.04 to 10.10 to 11.04, then wiped the OS only and reinstalled to 12.04 . * SATA drives all decommissioned and sold. * Power supply failed, replaced & upgraded. Unfortunately due to the extreme delay between bug report and triage, the system today bears almost no resemblance to the system that generated the report. (Really the only thing that remains are the data on the system!) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/491044 Title: Inconsistent attributes reported over time by smartctl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/491044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 198849] Re: [g35] [hardy alpha 5] xserver autoconfigure fails ONLY over HDMI (Intel G35)
Amazingly, I still have this equipment after all this time. I've since upgraded to 10.10, and I no longer experience this issue so yeah, I'd call it fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/198849 Title: [g35] [hardy alpha 5] xserver autoconfigure fails ONLY over HDMI (Intel G35) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 370495] Re: Wireless WPA password corrupted on reboot
Bug no longer present in ubuntu 10. ** Changed in: ubuntu Status: New => Invalid -- Wireless WPA password corrupted on reboot https://bugs.launchpad.net/bugs/370495 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 563773] Re: package ttf-indic-fonts-core 1:0.5.4ubuntu2 failed to install/upgrade: ErrorMessage: package ttf-indic-fonts-core is already installed and configured
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/44257645/Dependencies.txt ** Attachment added: "VarLogDistupgradeAptlog.gz" http://launchpadlibrarian.net/44257646/VarLogDistupgradeAptlog.gz ** Attachment added: "VarLogDistupgradeApttermlog.gz" http://launchpadlibrarian.net/44257647/VarLogDistupgradeApttermlog.gz ** Attachment added: "VarLogDistupgradeHistorylog.gz" http://launchpadlibrarian.net/44257648/VarLogDistupgradeHistorylog.gz -- package ttf-indic-fonts-core 1:0.5.4ubuntu2 failed to install/upgrade: ErrorMessage: package ttf-indic-fonts-core is already installed and configured https://bugs.launchpad.net/bugs/563773 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 563773] [NEW] package ttf-indic-fonts-core 1:0.5.4ubuntu2 failed to install/upgrade: ErrorMessage: package ttf-indic-fonts-core is already installed and configured
Public bug reported: Binary package hint: dpkg Just ran an upgrade, and got an error that some ttf fonts were already installed. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: ttf-indic-fonts-core 1:0.5.4ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-20.30-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-20-generic x86_64 Architecture: amd64 Date: Thu Apr 15 07:15:23 2010 ErrorMessage: ErrorMessage: package ttf-indic-fonts-core is already installed and configured InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) PackageArchitecture: all SourcePackage: dpkg Title: package ttf-indic-fonts-core 1:0.5.4ubuntu2 failed to install/upgrade: ErrorMessage: package ttf-indic-fonts-core is already installed and configured ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lucid -- package ttf-indic-fonts-core 1:0.5.4ubuntu2 failed to install/upgrade: ErrorMessage: package ttf-indic-fonts-core is already installed and configured https://bugs.launchpad.net/bugs/563773 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 356526] Re: BUG: soft lockup - CPU#0 stuck for 61s! [md0_raid1:740]
Well it looked like the issue was no longer being worked on so I stopped logging data to the ticket. It hasn't happened in 26 days (my current uptime), but that doesn't really mean much. I'm not sure if I should flip this back to new or not. I just stopped paying attention because it looked like nobody was doing anything. -- BUG: soft lockup - CPU#0 stuck for 61s! [md0_raid1:740] https://bugs.launchpad.net/bugs/356526 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 491044] [NEW] Inconsistent attributes reported over time by smartctl
Public bug reported: Binary package hint: smartmontools I have five identical hitachi HDS722020ALA330 running firmware JKAOA20N. If I run smartctl --attributes against each drive, at random a drive (or sometimes two!) will report its raw_read_error_rate as 65535 . Which would be alarming, except that if I simply wait a few minutes (ten?) then run smartctl against that SAME DRIVE again, it'll report it's raw read error rate as zero! Example: ~$ sudo smartctl --attributes /dev/sde smartctl version 5.38 [x86_64-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 016Pre-fail Always - 65536 2 Throughput_Performance 0x0005 132 132 054Pre-fail Offline - 103 3 Spin_Up_Time0x0007 136 136 024Pre-fail Always - 594 (Average 466) (snipten minutes or so go by.) ~$ sudo smartctl --attributes /dev/sde smartctl version 5.38 [x86_64-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 016Pre-fail Always - 0 2 Throughput_Performance 0x0005 132 132 054Pre-fail Offline - 103 3 Spin_Up_Time0x0007 136 136 024Pre-fail Always - 594 (Average 466) (...snip rest...) There aren't any other problems with any of the drives, and they're ALL doing it. No remapped sectors or other signs of any impending drive failures are happening, just these spurious raw read error rates being reported. Note: when the problem occurs, palimpsest shows identical data. Hopefully it's not just asking smartctl. :) Here is one of my drives in full; the other four are identical with different serial numbers obviously: ~$ sudo smartctl --all /dev/sda smartctl version 5.38 [x86_64-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: Hitachi HDS722020ALA330 Serial Number:JK1121[rest of serial number redacted] Firmware Version: JKAOA20N User Capacity:2,000,398,934,016 bytes Device is:Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is:Tue Dec 1 15:21:30 2009 CST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (21742) seconds. Offline data collection capabilities:(0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:(0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:(0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time:( 1) minutes. Extended self-test routine recommended polling time:( 255) minutes. SCT capabilities: (0x003d) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision nu
[Bug 356526] Re: BUG: soft lockup - CPU#0 stuck for 61s! [md0_raid1:740]
BTW, this is continuing to happen on an elongated basis. Noticed this in my logs from a few days ago: [743406.504221] md: data-check of RAID array md0 [743406.504226] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. [743406.504229] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for data-check. [743406.504236] md: using 128k window, over a total of 14651136 blocks. [743580.172502] BUG: soft lockup - CPU#1 stuck for 61s! [md0_raid1:847] [743580.172503] Modules linked in: snd_usb_audio snd_usb_lib yealink snd_hwdep binfmt_misc ppdev bridge stp bnep video output input_polldev jfs lp parport mxl5005s tuner_simple tuner_types cs5345 tda18271 tda9887 tda8290 snd_hda_intel tuner snd_pcm_oss cx25840 snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event mt2131 snd_seq snd_timer s5h1409 snd_seq_device cx18 snd i2c_algo_bit cx23885 psmouse lirc_mceusb2 compat_ioctl32 videodev v4l1_compat videobuf_dma_sg videobuf_dvb dvb_core cx2341x videobuf_core v4l2_common btcx_risc iTCO_wdt pcspkr serio_raw nvidia(P) soundcore tveeprom intel_agp iTCO_vendor_support usbhid snd_page_alloc lirc_dev atl1e raid10 raid456 async_xor async_memcpy async_tx xor raid1 raid0 multipath linear fbcon tileblit font bitblit softcursor [743580.172503] CPU 1: [743580.172503] Modules linked in: snd_usb_audio snd_usb_lib yealink snd_hwdep binfmt_misc ppdev bridge stp bnep video output input_polldev jfs lp parport mxl5005s tuner_simple tuner_types cs5345 tda18271 tda9887 tda8290 snd_hda_intel tuner snd_pcm_oss cx25840 snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event mt2131 snd_seq snd_timer s5h1409 snd_seq_device cx18 snd i2c_algo_bit cx23885 psmouse lirc_mceusb2 compat_ioctl32 videodev v4l1_compat videobuf_dma_sg videobuf_dvb dvb_core cx2341x videobuf_core v4l2_common btcx_risc iTCO_wdt pcspkr serio_raw nvidia(P) soundcore tveeprom intel_agp iTCO_vendor_support usbhid snd_page_alloc lirc_dev atl1e raid10 raid456 async_xor async_memcpy async_tx xor raid1 raid0 multipath linear fbcon tileblit font bitblit softcursor [743580.172503] Pid: 847, comm: md0_raid1 Tainted: P 2.6.28-11-generic #42-Ubuntu [743580.172503] RIP: 0010:[] [] sync_request_write+0x58f/0x7e0 [raid1] [743580.172503] RSP: 0018:88012bc4bd30 EFLAGS: 00010286 [743580.172503] RAX: 6db6db6db6db6db7 RBX: 88012bc4be00 RCX: 01d4 [743580.172503] RDX: 0060 RSI: 8800999fee2c RDI: 880049da8e2c [743580.172503] RBP: 88012bc4be00 R08: 0080 R09: 88012c463b40 [743580.172503] R10: 1000 R11: 0010 R12: 88012bc4bce0 [743580.172503] R13: 88012c463bc0 R14: 0286 R15: 88012bc4bca0 [743580.172503] FS: () GS:88012f802b80() knlGS: [743580.172503] CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b [743580.172503] CR2: 7f45470d1000 CR3: 00012d009000 CR4: 06a0 [743580.172503] DR0: DR1: DR2: [743580.172503] DR3: DR6: 0ff0 DR7: 0400 [743580.172503] Call Trace: [743580.172503] [] ? _spin_lock_irq+0x11/0x20 [743580.172503] [] raid1d+0xd6/0x410 [raid1] [743580.172503] [] ? default_spin_lock_flags+0x9/0x10 [743580.172503] [] md_thread+0x5c/0x140 [743580.172503] [] ? autoremove_wake_function+0x0/0x40 [743580.172503] [] ? md_thread+0x0/0x140 [743580.172503] [] kthread+0x49/0x90 [743580.172503] [] child_rip+0xa/0x11 [743580.172503] [] ? kthread+0x0/0x90 [743580.172503] [] ? child_rip+0x0/0x11 [743589.881116] md: md0: data-check done. -- BUG: soft lockup - CPU#0 stuck for 61s! [md0_raid1:740] https://bugs.launchpad.net/bugs/356526 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 356526] Re: BUG: soft lockup - CPU#0 stuck for 61s! [md0_raid1:740]
I too just ran into this bug this morning! My system did not require a reboot, though I did restart my myth TV backend as a precaution. (System still up and running now, for what it's worth.) uname -a: Linux Mythtery 2.6.28-11-generic #38-Ubuntu SMP Fri Mar 27 10:01:17 UTC 2009 x86_64 GNU/Linux I will attach the dmesg log and lspci logs as requested. ~$ sudo mdadm --query --detail /dev/md0 /dev/md0: Version : 00.90 Creation Time : Thu Mar 26 12:16:36 2009 Raid Level : raid1 Array Size : 14651136 (13.97 GiB 15.00 GB) Used Dev Size : 14651136 (13.97 GiB 15.00 GB) Raid Devices : 4 Total Devices : 4 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Mon Apr 6 10:42:47 2009 State : active Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 UUID : 30e55caa:7b37846c:2f942441:c20bfe15 Events : 0.121 Number Major Minor RaidDevice State 0 8 33 0 active sync /dev/sdc1 1 8 17 1 active sync /dev/sdb1 2 8 1 2 active sync /dev/sda1 3 8 49 3 active sync /dev/sdd1 ~$ sudo mdadm --query --detail /dev/md1 /dev/md1: Version : 00.90 Creation Time : Thu Mar 26 12:19:24 2009 Raid Level : raid5 Array Size : 2883386112 (2749.81 GiB 2952.59 GB) Used Dev Size : 961128704 (916.60 GiB 984.20 GB) Raid Devices : 4 Total Devices : 4 Preferred Minor : 1 Persistence : Superblock is persistent Update Time : Mon Apr 6 09:02:59 2009 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Layout : left-symmetric Chunk Size : 64K UUID : 40b52493:7870492f:792c47d7:3ad308e9 Events : 0.48 Number Major Minor RaidDevice State 0 8 3 0 active sync /dev/sda3 1 8 19 1 active sync /dev/sdb3 2 8 35 2 active sync /dev/sdc3 3 8 51 3 active sync /dev/sdd3 ~$ sudo blkid /dev/sda1: UUID="aa5ce530-6c84-377b-4124-942f15fe0bc2" TYPE="mdraid" /dev/sda2: TYPE="swap" UUID="1bb03a5b-012d-43cf-a23b-1bcc191f1210" /dev/sda3: UUID="9324b540-2f49-7078-d747-2c79e908d33a" TYPE="mdraid" /dev/sdb1: UUID="aa5ce530-6c84-377b-4124-942f15fe0bc2" TYPE="mdraid" /dev/sdb2: TYPE="swap" UUID="54be76a6-fdfa-4534-a57b-a011320797d2" /dev/sdb3: UUID="9324b540-2f49-7078-d747-2c79e908d33a" TYPE="mdraid" /dev/sdc1: UUID="aa5ce530-6c84-377b-4124-942f15fe0bc2" TYPE="mdraid" /dev/sdc2: TYPE="swap" UUID="8e18c25c-8b70-4621-9886-faf06e947c07" /dev/sdc3: UUID="9324b540-2f49-7078-d747-2c79e908d33a" TYPE="mdraid" /dev/sdd1: UUID="aa5ce530-6c84-377b-4124-942f15fe0bc2" TYPE="mdraid" /dev/sdd2: TYPE="swap" UUID="af25dc05-12af-429d-91bd-5f1058ddf92f" /dev/sdd3: UUID="9324b540-2f49-7078-d747-2c79e908d33a" TYPE="mdraid" /dev/md0: UUID="5c27feed-09cc-4233-9d27-282f5d6b787c" TYPE="ext3" /dev/md1: UUID="07a45363-1129-49df-a054-b34a44f50695" TYPE="jfs" There was hard drive activity when this happened, but not a TON going on. (Just watching TV.) I've pounded these disks a LOT harder when transcoding, for example. If there is anything else you guys need/want, feel free to let me know! (Especially since the system has NOT been rebooted!) -- BUG: soft lockup - CPU#0 stuck for 61s! [md0_raid1:740] https://bugs.launchpad.net/bugs/356526 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 356526] Re: BUG: soft lockup - CPU#0 stuck for 61s! [md0_raid1:740]
** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/24884668/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/24884669/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/24884670/Dependencies.txt ** Attachment added: "HalComputerInfo.txt" http://launchpadlibrarian.net/24884671/HalComputerInfo.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/24884672/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/24884673/Lsusb.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/24884674/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/24884677/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/24884678/ProcModules.txt -- BUG: soft lockup - CPU#0 stuck for 61s! [md0_raid1:740] https://bugs.launchpad.net/bugs/356526 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 356526] [NEW] BUG: soft lockup - CPU#0 stuck for 61s! [md0_raid1:740]
Public bug reported: Brian Morris asked me to file this. Originally filed under bug # 348218 , but Brian says this one is different. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 MachineType: ECS G43T-M NonfreeKernelModules: nvidia Package: linux-image-2.6.28-11-generic 2.6.28-11.38 ProcCmdLine: root=/dev/md0 ro quiet splash ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.28-11.38-generic SourcePackage: linux ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- BUG: soft lockup - CPU#0 stuck for 61s! [md0_raid1:740] https://bugs.launchpad.net/bugs/356526 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 348218] Re: BUG: soft lockup - CPU#1 stuck for 61s! [xfs_fsr:948]
Thoughts: This locked up TWICE while checking /dev/md0 , which is a 15GB raid 1 array. It didn't lock up at all checking the 2.7TB array, /dev/md1 , which exists on the rest of the space of *the same drives*. My spidey sense says there's might be something hinky going on with raid 1 here. -- BUG: soft lockup - CPU#1 stuck for 61s! [xfs_fsr:948] https://bugs.launchpad.net/bugs/348218 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 348218] Re: BUG: soft lockup - CPU#1 stuck for 61s! [xfs_fsr:948]
** Attachment added: "lspci output" http://launchpadlibrarian.net/24876478/lspci-vvnn.log -- BUG: soft lockup - CPU#1 stuck for 61s! [xfs_fsr:948] https://bugs.launchpad.net/bugs/348218 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 348218] Re: BUG: soft lockup - CPU#1 stuck for 61s! [xfs_fsr:948]
I too just ran into this bug this morning! My system did not require a reboot, though I did restart my myth TV backend as a precaution. (System still up and running now, for what it's worth.) uname -a: Linux Mythtery 2.6.28-11-generic #38-Ubuntu SMP Fri Mar 27 10:01:17 UTC 2009 x86_64 GNU/Linux I will attach the dmesg log and lspci logs as requested. ~$ sudo mdadm --query --detail /dev/md0 /dev/md0: Version : 00.90 Creation Time : Thu Mar 26 12:16:36 2009 Raid Level : raid1 Array Size : 14651136 (13.97 GiB 15.00 GB) Used Dev Size : 14651136 (13.97 GiB 15.00 GB) Raid Devices : 4 Total Devices : 4 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Mon Apr 6 10:42:47 2009 State : active Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 UUID : 30e55caa:7b37846c:2f942441:c20bfe15 Events : 0.121 Number Major Minor RaidDevice State 0 8 330 active sync /dev/sdc1 1 8 171 active sync /dev/sdb1 2 812 active sync /dev/sda1 3 8 493 active sync /dev/sdd1 ~$ sudo mdadm --query --detail /dev/md1 /dev/md1: Version : 00.90 Creation Time : Thu Mar 26 12:19:24 2009 Raid Level : raid5 Array Size : 2883386112 (2749.81 GiB 2952.59 GB) Used Dev Size : 961128704 (916.60 GiB 984.20 GB) Raid Devices : 4 Total Devices : 4 Preferred Minor : 1 Persistence : Superblock is persistent Update Time : Mon Apr 6 09:02:59 2009 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Layout : left-symmetric Chunk Size : 64K UUID : 40b52493:7870492f:792c47d7:3ad308e9 Events : 0.48 Number Major Minor RaidDevice State 0 830 active sync /dev/sda3 1 8 191 active sync /dev/sdb3 2 8 352 active sync /dev/sdc3 3 8 513 active sync /dev/sdd3 ~$ sudo blkid /dev/sda1: UUID="aa5ce530-6c84-377b-4124-942f15fe0bc2" TYPE="mdraid" /dev/sda2: TYPE="swap" UUID="1bb03a5b-012d-43cf-a23b-1bcc191f1210" /dev/sda3: UUID="9324b540-2f49-7078-d747-2c79e908d33a" TYPE="mdraid" /dev/sdb1: UUID="aa5ce530-6c84-377b-4124-942f15fe0bc2" TYPE="mdraid" /dev/sdb2: TYPE="swap" UUID="54be76a6-fdfa-4534-a57b-a011320797d2" /dev/sdb3: UUID="9324b540-2f49-7078-d747-2c79e908d33a" TYPE="mdraid" /dev/sdc1: UUID="aa5ce530-6c84-377b-4124-942f15fe0bc2" TYPE="mdraid" /dev/sdc2: TYPE="swap" UUID="8e18c25c-8b70-4621-9886-faf06e947c07" /dev/sdc3: UUID="9324b540-2f49-7078-d747-2c79e908d33a" TYPE="mdraid" /dev/sdd1: UUID="aa5ce530-6c84-377b-4124-942f15fe0bc2" TYPE="mdraid" /dev/sdd2: TYPE="swap" UUID="af25dc05-12af-429d-91bd-5f1058ddf92f" /dev/sdd3: UUID="9324b540-2f49-7078-d747-2c79e908d33a" TYPE="mdraid" /dev/md0: UUID="5c27feed-09cc-4233-9d27-282f5d6b787c" TYPE="ext3" /dev/md1: UUID="07a45363-1129-49df-a054-b34a44f50695" TYPE="jfs" There was hard drive activity when this happened, but not a TON going on. (Just watching TV.) I've pounded these disks a LOT harder when transcoding, for example. If there is anything else you guys need/want, feel free to let me know! (Especially since the system has NOT been rebooted!) ** Attachment added: "Dmesg output" http://launchpadlibrarian.net/24876455/dmesg.log -- BUG: soft lockup - CPU#1 stuck for 61s! [xfs_fsr:948] https://bugs.launchpad.net/bugs/348218 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 353132] Re: mythtv will not accept non-blank mysql password
A... I'm confusing the mythtv-database and mythtv-common packages. Yeah, now it makes sense why you wouldn't *have* to have mythtv-database be a required package of mythtv-backend. -- mythtv will not accept non-blank mysql password https://bugs.launchpad.net/bugs/353132 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 353132] Re: mythtv will not accept non-blank mysql password
You can have a backend that DOESN'T KNOW HOW to talk to a database? That's news to me! -- mythtv will not accept non-blank mysql password https://bugs.launchpad.net/bugs/353132 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 353132] Re: mythtv will not accept non-blank mysql password
Just rebuilt the system, and this bug DOES NOT appear if I change the line sudo apt-get install mythtv-backend mythtv-frontend to sudo apt-get install mythtv-backend mythtv-frontend mythtv-database ...which again begs the question WHY isn't mythtv-database a required package for mythtv-backend!?? -- mythtv will not accept non-blank mysql password https://bugs.launchpad.net/bugs/353132 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 353132] [NEW] mythtv will not accept non-blank mysql password
Public bug reported: Binary package hint: mythtv-backend OS: ubuntu jaunty amd64 beta (beta 1? :) ) version: alternate install CLEAN INSTALL steps to reproduce: * format and install ubuntu jaunty amd64 beta then... sudo apt-get install mysql-server (put in a mysql root user password, say for example WHOOPS) sudo apt-get install apache2 (since we'll need it later) sudo /etc/init.d/mysql restart (so mysql is running and the password has been 'flushed through') mysql -u root -p mysql will prompt for your root user's password. put it in, should result in mysql prompt So we know that mysql is running and the root user's password is good. type exit or quit to get out of mysql. sudo apt-get install mythtv-backend mythtv-frontend gets the backend and frontend packages sudo apt-get install mythtv-database (??? shouldn't this be a dependency of mythtv-backend, since you can't run a backend without a database connection??) sudo dpkg-reconfigure mythtv-database FAIL!!!mythtv-database's reconfiguration will not accept ANY password for the mysql root user, *even though we tested it above!* (Should accept the mysql user "root"'s password to set up the myth tv database stuff.) ~$ apt-cache policy mythtv-frontend mythtv-backend mythtv-database mysql-server apache2 mythtv-frontend: Installed: 0.21.0+fixes19961-0ubuntu8 Candidate: 0.21.0+fixes19961-0ubuntu8 Version table: *** 0.21.0+fixes19961-0ubuntu8 0 500 http://us.archive.ubuntu.com jaunty/multiverse Packages 100 /var/lib/dpkg/status mythtv-backend: Installed: 0.21.0+fixes19961-0ubuntu8 Candidate: 0.21.0+fixes19961-0ubuntu8 Version table: *** 0.21.0+fixes19961-0ubuntu8 0 500 http://us.archive.ubuntu.com jaunty/multiverse Packages 100 /var/lib/dpkg/status mythtv-database: Installed: 0.21.0+fixes19961-0ubuntu8 Candidate: 0.21.0+fixes19961-0ubuntu8 Version table: *** 0.21.0+fixes19961-0ubuntu8 0 500 http://us.archive.ubuntu.com jaunty/multiverse Packages 100 /var/lib/dpkg/status mysql-server: Installed: 5.1.30really5.0.75-0ubuntu10 Candidate: 5.1.30really5.0.75-0ubuntu10 Version table: *** 5.1.30really5.0.75-0ubuntu10 0 500 http://us.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status apache2: Installed: 2.2.11-2ubuntu1 Candidate: 2.2.11-2ubuntu1 Version table: *** 2.2.11-2ubuntu1 0 500 http://us.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status ** Affects: mythtv (Ubuntu) Importance: Undecided Status: New -- mythtv will not accept non-blank mysql password https://bugs.launchpad.net/bugs/353132 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 217947] Re: compiz.real crashed with SIGSEGV in _IceTransClose()
Sorry, but I've rebuilt the system since then. (After about two months I said to hell with it!) You might as well go ahead and close this, since there's no way I can UNformat the machine. -- compiz.real crashed with SIGSEGV in _IceTransClose() https://bugs.launchpad.net/bugs/217947 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 199657] Re: frequency scaling for overclocked core 2 duo uses original frequencies
Same results here using hardy beta... 2.2 GHz overclock falls back to 1.8 GHz (stock) when speedstep is enabled. -- frequency scaling for overclocked core 2 duo uses original frequencies https://bugs.launchpad.net/bugs/199657 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 198849] Re: [hardy alpha 5] xserver autoconfigure fails ONLY over HDMI (Intel G35)
Correction... I just tried the gutsy live CD, and I guess this combo did NOT work via HDMI then, only VGA. My mistake! -- [hardy alpha 5] xserver autoconfigure fails ONLY over HDMI (Intel G35) https://bugs.launchpad.net/bugs/198849 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 198849] Re: [hardy alpha 5] xserver autoconfigure fails ONLY over HDMI (Intel G35)
** Attachment added: "lspci.txt" http://launchpadlibrarian.net/12443924/lspci.txt -- [hardy alpha 5] xserver autoconfigure fails ONLY over HDMI (Intel G35) https://bugs.launchpad.net/bugs/198849 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 198849] Re: [hardy alpha 5] xserver autoconfigure fails ONLY over HDMI (Intel G35)
Here is the xorg.0.log when the monitor is connected via the VGA cable. ** Attachment added: "Xorg.0.log.vga" http://launchpadlibrarian.net/12443355/Xorg.0.log.vga -- [hardy alpha 5] xserver autoconfigure fails ONLY over HDMI (Intel G35) https://bugs.launchpad.net/bugs/198849 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 198849] Re: [hardy alpha 5] xserver autoconfigure fails ONLY over HDMI (Intel G35)
** Attachment added: "xorg.conf" http://launchpadlibrarian.net/12443051/xorg.conf -- [hardy alpha 5] xserver autoconfigure fails ONLY over HDMI (Intel G35) https://bugs.launchpad.net/bugs/198849 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 198849] Re: [hardy alpha 5] xserver autoconfigure fails ONLY over HDMI (Intel G35)
** Attachment added: "xorg.0.log" http://launchpadlibrarian.net/12442959/Xorg.0.log -- [hardy alpha 5] xserver autoconfigure fails ONLY over HDMI (Intel G35) https://bugs.launchpad.net/bugs/198849 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 198849] [NEW] [hardy alpha 5] xserver autoconfigure fails ONLY over HDMI (Intel G35)
Public bug reported: Binary package hint: gdm monitor: hanns-g hc194d graphics chipset: intel G35 motherboard: asus p5e-vm hdmi OS version: hardy alpha 5, patched on 3/5/2008 DISTRIB_ID=Ubuntu DISTRIB_RELEASE=8.04 DISTRIB_CODENAME=hardy DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)" gdm: Installed: 2.20.3-0ubuntu6 Candidate: 2.20.3-0ubuntu6 Version table: *** 2.20.3-0ubuntu6 0 500 http://us.archive.ubuntu.com hardy/main Packages 100 /var/lib/dpkg/status When monitor is connected via VGA D-sub cable, everything works great! When monitor is connected via DVI cable (w/ DVI-HDMI adapter), monitor shows "unsupported display mode". FWIW, this exact combo works GREAT under gutsy (even under HDMI). more info: I'm rebooting in between swapping cables, and at no point in time are both cables connected to the machine. Sequence is to power down, swap VGA for DVI cable (or vice-versa), power up, see BIOS and then ubuntu splash screens, then when the login screen should come up (I hear the bongo sound, and can log in blind or administer via SSH) that's when I get unsupported display mode. So I'm not crashing at all, it's just not exactly working quite right. ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- [hardy alpha 5] xserver autoconfigure fails ONLY over HDMI (Intel G35) https://bugs.launchpad.net/bugs/198849 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
