- main - earth.li

Help with hardware
by Peter Alcibiades 20 Jan '13

20 Jan '13

Any ideas what this might be? I was having a crash with instant power down. So I replaced the PSU with a Xilence, and for a while all seemed well. Then it happened again. Restarted. But to restart, I had to actually unplug the power cable. Only then did the power switch work. All carried along fine for a week or so - I never turn it off, and ir ran just fine. Then just now, it happens again! In the meantime afflicted by a sudden rush of nerves I have made a backup using clonezilla so its not going to be the end of the world if it goes south. What happens is, try to use the power switch and nothing whatever happens. Then I connected up to a different power cable and a different socket, and it goes on. The Gigabyte board asks me to pick the last good boot, so I do. Then it powers down and restarts, and goes into the usual Debian login, after which it runs the disk diagnostic and repairs itself, and now its running just fine again. What on earth could it be and what should I do? See what is weird is that I am tempted to think maybe its the extension block, but the screen runs off that, and that is just fine. It seems reasonable to change out the extension block because they are not expensive. But I can't quite see how that could do it. There is no doubt that last time it was the psu. It was totally dead, and replacing that first with the evo and then with the xilence, it did actually bring it all back to life. But this time its clearly not the psu, or could it be? Al

3 4

A conundrum to boot!
by Barry Samuels 19 Jan '13

19 Jan '13

We have a spare computer laying around the place, as you do, which serves as a quick substitute if either of our main computers goes wrong. It's just a case of taking the disc drive out of the faulty computer and putting it in the spare and off we go again. The mainboard in the spare went wrong a while ago and I managed to get a free replacement from my brother in the form of a discarded mainboard. This mainboard is an Intel DP965LT which has a respectable 2.7 GHz Core2 Duo CPU and 8 GBs of RAM. The PSU in my main (normal) computer exploded recently quite spectacularly with a flash, bang and a puff of smoke so I thought I would swap the drive into the spare computer while I sorted things out. It was then that I discovered that although the spare board had SATA connections it wouldn't boot a SATA drive. With just the SATA drive connected I got a "No bootable drives" message. It will, however, boot an IDE drive. I do have a small IDE drive and I was wondering if it were possible to write a Lilo boot sector on that drive in order to start the Linux system on the SATA drive. But with the two drives connected the IDE drive comes up as sda and the SATA drive as sdb and, of course, the system on the SATA drive is configured to use sda. I don't want to change the configuration on the SATA drive so is there a way round this apart from trying to cadge another mainboard from somewhere? -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain

6 13

zhead/ztail
by Mark Rogers 18 Jan '13

18 Jan '13

I want to display the first few line of each of a batch of log files, some of which are gzipped. Normally I'd use zcat in place of cat, zgrep in place of grep, etc, to work with a mixture of compressed and uncompressed files. But zhead and ztail don't exist. What's the best way to achieve this: zhead -n1 /var/log/syslog* (show the first line of each syslog* file)? All the thoughts I had got increasingly convoluted. Obviously stuff like: zcat /var/log/syslog* | head -n1 .. doesn't achieve what I want... -- Mark Rogers // More Solutions Ltd (Peterborough Office) // 0844 251 1450 Registered in England (0456 0902) 21 Drakes Mews, Milton Keynes, MK8 0ER

2 2

Re: [ALUG] Help with hardware
by Peter Alcibiades 16 Jan '13

16 Jan '13

Yes, I did check out the loading on the various calculators I found - in response to the suggestions - and there seems to be plenty of margin. More than the calculators suggest. Its 250W, and its only a main board, one hard drive and i3. No graphics card. The earlier psu that seems to have burned out was 300W. I'm feeling doubtful that an inadequate psu can be the cause. Didn't note exactly what the restart message was. Something about going back to the last good configuration. No, I don't think there are two bios files installed. But there were a bunch of choices which I don't exactly remember. What I did so far was to take the supply off the surge protected strip and connect it directly to the mains and everything is running fine now. One thing that makes me suspect the psu is that the crash happened when watching youtube - which presumably is more processor intensive than just web or word processing. Anyway, I ordered a new extension strip, this one brand named so maybe it will be better, and we will see. I truly hate intermittent faults! Don't we all? Al On Tuesday 15 January 2013 08:01:00 Wayne Stallwood wrote: > As an educated guess I'd say either there has been a power > spike/overload or PSU failure that puts it into protection mode or there > is something going on with your mainboard. > > When you say "The Gigabyte board asks me to pick the last good boot" > what exactly is the message ? Is it falling back to a redundant BIOS image ? > > Is the PSU adequately sized for the machine..I know we had this > conversation late last year on the list. But specifically if you use a > PSU calculator for your combination of hardware components does the > current draw on the 12v rails come in at way under whatever it says for > that rail on the PSU spec. > > If you go by wattage alone you don't know if the distribution of > capacity is sufficient across the rails for your hardware. You often > can't for example draw the total rated capacity from one rail. Sometimes > despite the overall rating appearing to be sufficient the 12V rail can > be undersized, this is particularly true on PSU's designed for older > hardware. > > > > > > >

1 0

Help, graphics broken!
by Mark Rogers 16 Jan '13

16 Jan '13

Kubuntu 12.10 on a new PC, has been working fine. Just had a power cut, and on restarting I see the BIOS on my screen then it goes grey and stays that way. I can tell it's booting up (combination of HDD lights etc, and the fact that if I wait long enough I can SSH in to it). But nothing on the screen. It's possible, but no means certain, that I had does some apt-get upgrade's (or dist-upgrade's) prior to the power cut that have now come into effect, How do I debug this to get my desktop back (by which I mean visible to me - I'm sure it's there!)? In case it helps: $ lspci | grep VGA 00:01.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI BeaverCreek [Radeon HD 6530D] It's just a default install, no graphics tweaking (I haven't even installed proprietary drivers). Monitor is Edge EF220A (1920 x 1080). Mark -- Mark Rogers // More Solutions Ltd (Peterborough Office) // 0844 251 1450 Registered in England (0456 0902) @ 13 Clarke Rd, Milton Keynes, MK1 1LG

1 1

Re: [ALUG] Leetkey
by Anthony Anson 14 Jan '13

14 Jan '13

On 14/01/13 17:39, Anthony Anson wrote: > On 13/01/13 18:07, steve-ALUG(a)hst.me.uk wrote: >> On 13/01/13 12:58, Anthony Anson wrote: >>> On 13/01/13 01:04, steve-ALUG(a)hst.me.uk wrote: >>>> On 12/01/13 12:07, Anthony Anson wrote: >>>> [SNIP] >>>>> I must say I dislike the current offering of Thunderbird. >>>>> >>>> Well I did too, until I found the various extensions and >>>> customisationshe >>>> that made it look, more or less, like it used to look like. What don't >>>> you like? >>> >>> How long have I got? I haven't (yet?) found a way to close mail on the >>> screen without clicking 'inbox'; > >> Not quite sure what you mean. > > Well, the old Thunderbird on the Eee, and Eee bah gum, it were old... > had a close box on the pane - the only 'close' box closes Thunderbird. > > Shall play with dragging functions about as you suggest - there's > already a backward and a forward arrow - ta. > >>> the only way to date that I've found to >>> go on to the next message is to remember to position the cursor in the >>> right area of the pane and use the 'down' key; > >> You can read through emails in the same style as a newsgroup reader >> program, by pressing space. Space shows you a pageful of an email at a >> time. When it gets to the end of the email, it then moves on to the >> next. >> Also, you can right click on the toolbar at the top of the screen (and >> possibly the one on top of the email), and add a Next and Previous >> button. This allows you to scroll through your emails by clicking on >> them. There's a bunch of shortcuts too - see: >> >> https://support.mozillamessaging.com/en-US/kb/keyboard-shortcuts#w_moving-a… >> >> >> >> Loads of useful stuff on that page - I've just learnt some stuff! :-) > > I shall look at it next time I can use wifi >> >>> I haven't yet found a way >>> to turn off red worms - er - spellcheck-as-you-trype, and lots more. >> >> Edit/Preferences >> Composition icon >> Spelling Tab >> Tick or untick as you see fit. >>> >>> Mind you, for reasons of my ISP's change of security and methods of >>> connecting, I haven't been able to use POP3 between getting this >>> new(ish) box before Christmas and last week, so I wasn't using the >>> program, and, I haven't tried *really* hard. >>> >>> I was considering overwriting Thunderguts on this box with the old >>> version I had been using on the Eee, but now the new one can get into >>> the mail server I'm loath to poke it with sharp sticks. >> >> as to why you're getting sent email in your inbox, well that's not a >> problem I'm getting. Is something somewhere BCCing your email back to >> you? Could it be a server/ISP issue? Does it happen when you send >> email by other means? > > I don't send email by any other means. > >> Don't get me wrong - I think Thunderbird is heading the wrong way. I've >> just installed it for the other half, and the menu bar was hidden and I >> was presented with all sorts of horrible menus and stuff, and by >> default, it looks horrible, but it is possible to wrangle it back to >> working OK with judicious use of extensions and customising. I've >> managed it! > > Thanks - working my way through all this. Worming powder applied. I had > already adjusted the menu bar, but became pi^h^h^somewhat incensed by > the unintuitive nature of the controls - it's rather like learning to > fly an airliner which is coming in to land without the help of George. > -- Tony

1 0

A cry for help
by nev young 14 Jan '13

14 Jan '13

well for hardware. Does any one have a graphics card, with a PCIE connector and SVGA D-connector on the output, going spare that Vickie could have? If so could they bring it to the ALUG meet tomorrow. I've taken one out of my (spit)windows PC to get hers going and would like to avoid having to part with cash for a new one. Thankx Nev

2 3

Leetkey
by Anthony Anson 13 Jan '13

13 Jan '13

ISTR a workround for adding Leetkey to Thunderbird 17 was sent to the list. Am I dreaming? If my memory is correct I can rootle through everything I have saved from ALUG on the old Eee. If I am wrong, what is the last version in which Leetkey works? If I go onto the Mozilla website and install it, will it replace Mozilla 17, or install another one beside it? -- Tony

4 8

Backup Disk Freeze - Any cause clue from syslog?
by steve-alug＠hst.me.uk 13 Jan '13

13 Jan '13

Hi! My backup system has recently started causing me some grief. I'm running backuppc backing up to an IDE drive in a Netgear SC101 SAN storage box. There are two drives in this device, and the second one is being talked to by Simple Backup, and is working fine. The main/bigger drive is /dev/nbd1 and backuppc has started hanging whilst using it. It doesn't happen straight away - it's several hours after the backup has been started. If I power everything down, wait and switch it back on again, all the drives spin up and seem to work ok again. The SC101 is attached via the SC101-nbd project driver. http://code.google.com/p/sc101-nbd/ It has all been working fine until recently. Nothing's changed, apart from installing routine security updates (inc kernel updates) I'm running ubuntu 10.04. I'm currently doing a deep check on the disk using a tool from Ultimate boot Cd appropriate for the drive manufacturer, but a quick check said the disk's OK. Any ideas why it's hanging like this? Once hung, I can't even ls the disk - it's completely blocked. I tried reformatting it yesterday, and erasing and reinstalling backuppc, but it crashed again. Some of Syslog output below - there's many more after this one, but this is the first. Possible candidates: Disk SAN controller Main PC faulty Disk sleeping and failing to wake again. Any ideas guys? Cheers Steve Jan 11 07:00:28 myserver ntpd[1950]: kernel time sync status change 6001 Jan 11 07:02:01 myserver CRON[11758]: (logcheck) CMD ( if [ -x /usr/sbin/logcheck ]; then nice -n10 /usr/sbin/logcheck; fi) Jan 11 07:04:11 myserver kernel: [45960.212092] INFO: task jbd2/nbd1-8:12704 blocked for more than 120 seconds. Jan 11 07:04:11 myserver kernel: [45960.212100] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 11 07:04:11 myserver kernel: [45960.212104] jbd2/nbd1-8 D 00005645 0 12704 2 0x00000000 Jan 11 07:04:11 myserver kernel: [45960.212113] c6ce9de4 00000046 f7490000 00005645 00000000 c08964e0 c47b9c24 c08964e0 Jan 11 07:04:11 myserver kernel: [45960.212123] 3c1ac4f3 0000299c c08964e0 c08964e0 c47b9c24 c08964e0 c08964e0 d7e7d800 Jan 11 07:04:11 myserver kernel: [45960.212131] 00000000 0000299c c47b9980 c47b9980 c30094e0 c6ce9e2c c6ce9df4 c05b71a1 Jan 11 07:04:11 myserver kernel: [45960.212140] Call Trace: Jan 11 07:04:11 myserver kernel: [45960.212157] [<c05b71a1>] io_schedule+0x61/0xa0 Jan 11 07:04:11 myserver kernel: [45960.212165] [<c01d4b9d>] sync_page+0x3d/0x50 Jan 11 07:04:11 myserver kernel: [45960.212171] [<c05b795d>] __wait_on_bit+0x4d/0x70 Jan 11 07:04:11 myserver kernel: [45960.212176] [<c01d4b60>] ? sync_page+0x0/0x50 Jan 11 07:04:11 myserver kernel: [45960.212181] [<c01d4dc1>] wait_on_page_bit+0x91/0xa0 Jan 11 07:04:11 myserver kernel: [45960.212187] [<c0170e90>] ? wake_bit_function+0x0/0x50 Jan 11 07:04:11 myserver kernel: [45960.212193] [<c01d5051>] wait_on_page_writeback_range+0xa1/0x110 Jan 11 07:04:11 myserver kernel: [45960.212201] [<c023ca2e>] ? bio_alloc_bioset+0x2e/0xf0 Jan 11 07:04:11 myserver kernel: [45960.212209] [<c02da977>] ? jbd2_journal_write_metadata_buffer+0x277/0x370 Jan 11 07:04:11 myserver kernel: [45960.212215] [<c01d511a>] filemap_fdatawait+0x5a/0x70 Jan 11 07:04:11 myserver kernel: [45960.212221] [<c02d2bae>] jbd2_journal_commit_transaction+0x51e/0x1030 Jan 11 07:04:11 myserver kernel: [45960.212230] [<c01311b8>] ? default_spin_lock_flags+0x8/0x10 Jan 11 07:04:11 myserver kernel: [45960.212236] [<c0164c78>] ? try_to_del_timer_sync+0x68/0xb0 Jan 11 07:04:11 myserver kernel: [45960.212241] [<c02d93d5>] kjournald2+0x95/0x1c0 Jan 11 07:04:11 myserver kernel: [45960.212247] [<c0170e40>] ? autoremove_wake_function+0x0/0x50 Jan 11 07:04:11 myserver kernel: [45960.212252] [<c02d9340>] ? kjournald2+0x0/0x1c0 Jan 11 07:04:11 myserver kernel: [45960.212256] [<c0170bb4>] kthread+0x74/0x80 Jan 11 07:04:11 myserver kernel: [45960.212261] [<c0170b40>] ? kthread+0x0/0x80 Jan 11 07:04:11 myserver kernel: [45960.212267] [<c010a467>] kernel_thread_helper+0x7/0x10 Jan 11 07:04:11 myserver kernel: [45960.212278] INFO: task flush-43:16:11670 blocked for more than 120 seconds. Jan 11 07:04:11 myserver kernel: [45960.212281] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 11 07:04:11 myserver kernel: [45960.212285] flush-43:16 D 00000484 0 11670 2 0x00000000 Jan 11 07:04:11 myserver kernel: [45960.212291] c46d3b34 00000046 c07eaa20 00000484 00000000 c08964e0 ef5735a4 c08964e0 Jan 11 07:04:11 myserver kernel: [45960.212300] f5f3884b 0000299a c08964e0 c08964e0 ef5735a4 c08964e0 c08964e0 e8566a00 Jan 11 07:04:11 myserver kernel: [45960.212308] f5f2b230 0000299a ef573300 c2e0afe0 eb6accc0 c46d3b74 c46d3b94 c02d1ec5 Jan 11 07:04:11 myserver kernel: [45960.212316] Call Trace: Jan 11 07:04:11 myserver kernel: [45960.212324] [<c02d1ec5>] do_get_write_access+0x245/0x440 Jan 11 07:04:11 myserver kernel: [45960.212330] [<c0170e90>] ? wake_bit_function+0x0/0x50 Jan 11 07:04:11 myserver kernel: [45960.212336] [<c02d2238>] jbd2_journal_get_write_access+0x28/0x40 Jan 11 07:04:11 myserver kernel: [45960.212343] [<c02bb3fe>] __ext4_journal_get_write_access+0x2e/0x60 Jan 11 07:04:11 myserver kernel: [45960.212349] [<c02bd611>] ext4_mb_mark_diskspace_used+0x61/0x2f0 Jan 11 07:04:11 myserver kernel: [45960.212354] [<c02c38a6>] ext4_mb_new_blocks+0x306/0x590 Jan 11 07:04:11 myserver kernel: [45960.212360] [<c02b8613>] ? ext4_ext_find_extent+0x253/0x280 Jan 11 07:04:11 myserver kernel: [45960.212365] [<c02baf12>] ext4_ext_get_blocks+0x472/0x700 Jan 11 07:04:11 myserver kernel: [45960.212373] [<c0298f98>] ext4_get_blocks+0xf8/0x2c0 Jan 11 07:04:11 myserver kernel: [45960.212379] [<c02997c9>] mpage_da_map_blocks+0x99/0x410 Jan 11 07:04:11 myserver kernel: [45960.212385] [<c02b0d90>] ? ext4_journal_start_sb+0xc0/0xf0 Jan 11 07:04:11 myserver kernel: [45960.212390] [<c0296917>] ? ext4_meta_trans_blocks+0xb7/0xd0 Jan 11 07:04:11 myserver kernel: [45960.212396] [<c0299dc9>] ext4_da_writepages+0x289/0x580 Jan 11 07:04:11 myserver kernel: [45960.212403] [<c01489d9>] ? update_curr+0x169/0x2a0 Jan 11 07:04:11 myserver kernel: [45960.212410] [<c01dc66c>] do_writepages+0x1c/0x40 Jan 11 07:04:11 myserver kernel: [45960.212417] [<c0232a15>] writeback_single_inode+0xd5/0x380 Jan 11 07:04:11 myserver kernel: [45960.212422] [<c02331f9>] writeback_sb_inodes+0x149/0x230 Jan 11 07:04:11 myserver kernel: [45960.212427] [<c023364a>] writeback_inodes_wb+0x8a/0x160 Jan 11 07:04:11 myserver kernel: [45960.212432] [<c0233903>] wb_writeback+0x1e3/0x230 Jan 11 07:04:11 myserver kernel: [45960.212438] [<c0233a81>] wb_do_writeback+0x131/0x140 Jan 11 07:04:11 myserver kernel: [45960.212443] [<c0233acb>] bdi_writeback_task+0x3b/0xb0 Jan 11 07:04:11 myserver kernel: [45960.212448] [<c01eb9e0>] ? bdi_start_fn+0x0/0xc0 Jan 11 07:04:11 myserver kernel: [45960.212453] [<c01eba3d>] bdi_start_fn+0x5d/0xc0 Jan 11 07:04:11 myserver kernel: [45960.212457] [<c01eb9e0>] ? bdi_start_fn+0x0/0xc0 Jan 11 07:04:11 myserver kernel: [45960.212461] [<c0170bb4>] kthread+0x74/0x80 Jan 11 07:04:11 myserver kernel: [45960.212466] [<c0170b40>] ? kthread+0x0/0x80 Jan 11 07:04:11 myserver kernel: [45960.212471] [<c010a467>] kernel_thread_helper+0x7/0x10 Jan 11 07:05:01 myserver CRON[11897]: (root) CMD (if [ -x /usr/bin/vnstat ] && [ `ls /var/lib/vnstat/ | wc -l` -ge 1 ]; then /usr/bin/vnstat -u; fi) Jan 11 07:06:11 myserver kernel: [46080.212093] INFO: task jbd2/nbd1-8:12704 blocked for more than 120 seconds. Jan 11 07:06:11 myserver kernel: [46080.212101] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 11 07:06:11 myserver kernel: [46080.212106] jbd2/nbd1-8 D 00005645 0 12704 2 0x00000000 Jan 11 07:06:11 myserver kernel: [46080.212114] c6ce9de4 00000046 f7490000 00005645 00000000 c08964e0 c47b9c24 c08964e0 Jan 11 07:06:11 myserver kernel: [46080.212124] 3c1ac4f3 0000299c c08964e0 c08964e0 c47b9c24 c08964e0 c08964e0 d7e7d800 Jan 11 07:06:11 myserver kernel: [46080.212132] 00000000 0000299c c47b9980 c47b9980 c30094e0 c6ce9e2c c6ce9df4 c05b71a1 Jan 11 07:06:11 myserver kernel: [46080.212140] Call Trace: Jan 11 07:06:11 myserver kernel: [46080.212156] [<c05b71a1>] io_schedule+0x61/0xa0 Jan 11 07:06:11 myserver kernel: [46080.212165] [<c01d4b9d>] sync_page+0x3d/0x50 Jan 11 07:06:11 myserver kernel: [46080.212171] [<c05b795d>] __wait_on_bit+0x4d/0x70 Jan 11 07:06:11 myserver kernel: [46080.212175] [<c01d4b60>] ? sync_page+0x0/0x50 Jan 11 07:06:11 myserver kernel: [46080.212180] [<c01d4dc1>] wait_on_page_bit+0x91/0xa0 Jan 11 07:06:11 myserver kernel: [46080.212187] [<c0170e90>] ? wake_bit_function+0x0/0x50 Jan 11 07:06:11 myserver kernel: [46080.212192] [<c01d5051>] wait_on_page_writeback_range+0xa1/0x110 Jan 11 07:06:11 myserver kernel: [46080.212200] [<c023ca2e>] ? bio_alloc_bioset+0x2e/0xf0 Jan 11 07:06:11 myserver kernel: [46080.212207] [<c02da977>] ? jbd2_journal_write_metadata_buffer+0x277/0x370 Jan 11 07:06:11 myserver kernel: [46080.212213] [<c01d511a>] filemap_fdatawait+0x5a/0x70 Jan 11 07:06:11 myserver kernel: [46080.212219] [<c02d2bae>] jbd2_journal_commit_transaction+0x51e/0x1030 Jan 11 07:06:11 myserver kernel: [46080.212228] [<c01311b8>] ? default_spin_lock_flags+0x8/0x10 Jan 11 07:06:11 myserver kernel: [46080.212234] [<c0164c78>] ? try_to_del_timer_sync+0x68/0xb0 Jan 11 07:06:11 myserver kernel: [46080.212239] [<c02d93d5>] kjournald2+0x95/0x1c0 Jan 11 07:06:11 myserver kernel: [46080.212245] [<c0170e40>] ? autoremove_wake_function+0x0/0x50 Jan 11 07:06:11 myserver kernel: [46080.212250] [<c02d9340>] ? kjournald2+0x0/0x1c0 Jan 11 07:06:11 myserver kernel: [46080.212254] [<c0170bb4>] kthread+0x74/0x80 Jan 11 07:06:11 myserver kernel: [46080.212259] [<c0170b40>] ? kthread+0x0/0x80 Jan 11 07:06:11 myserver kernel: [46080.212265] [<c010a467>] kernel_thread_helper+0x7/0x10 Jan 11 07:06:11 myserver kernel: [46080.212277] INFO: task flush-43:16:11670 blocked for more than 120 seconds. Jan 11 07:06:11 myserver kernel: [46080.212282] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 11 07:06:11 myserver kernel: [46080.212285] flush-43:16 D 00000484 0 11670 2 0x00000000 Jan 11 07:06:11 myserver kernel: [46080.212292] c46d3b34 00000046 c07eaa20 00000484 00000000 c08964e0 ef5735a4 c08964e0 Jan 11 07:06:11 myserver kernel: [46080.212300] f5f3884b 0000299a c08964e0 c08964e0 ef5735a4 c08964e0 c08964e0 e8566a00 Jan 11 07:06:11 myserver kernel: [46080.212309] f5f2b230 0000299a ef573300 c2e0afe0 eb6accc0 c46d3b74 c46d3b94 c02d1ec5 Jan 11 07:06:11 myserver kernel: [46080.212317] Call Trace: Jan 11 07:06:11 myserver kernel: [46080.212325] [<c02d1ec5>] do_get_write_access+0x245/0x440 Jan 11 07:06:11 myserver kernel: [46080.212331] [<c0170e90>] ? wake_bit_function+0x0/0x50 Jan 11 07:06:11 myserver kernel: [46080.212337] [<c02d2238>] jbd2_journal_get_write_access+0x28/0x40 Jan 11 07:06:11 myserver kernel: [46080.212344] [<c02bb3fe>] __ext4_journal_get_write_access+0x2e/0x60 Jan 11 07:06:11 myserver kernel: [46080.212349] [<c02bd611>] ext4_mb_mark_diskspace_used+0x61/0x2f0 Jan 11 07:06:11 myserver kernel: [46080.212354] [<c02c38a6>] ext4_mb_new_blocks+0x306/0x590 Jan 11 07:06:11 myserver kernel: [46080.212359] [<c02b8613>] ? ext4_ext_find_extent+0x253/0x280 Jan 11 07:06:11 myserver kernel: [46080.212364] [<c02baf12>] ext4_ext_get_blocks+0x472/0x700 Jan 11 07:06:11 myserver kernel: [46080.212372] [<c0298f98>] ext4_get_blocks+0xf8/0x2c0 Jan 11 07:06:11 myserver kernel: [46080.212377] [<c02997c9>] mpage_da_map_blocks+0x99/0x410 Jan 11 07:06:11 myserver kernel: [46080.212383] [<c02b0d90>] ? ext4_journal_start_sb+0xc0/0xf0 Jan 11 07:06:11 myserver kernel: [46080.212388] [<c0296917>] ? ext4_meta_trans_blocks+0xb7/0xd0 Jan 11 07:06:11 myserver kernel: [46080.212393] [<c0299dc9>] ext4_da_writepages+0x289/0x580 Jan 11 07:06:11 myserver kernel: [46080.212400] [<c01489d9>] ? update_curr+0x169/0x2a0 Jan 11 07:06:11 myserver kernel: [46080.212407] [<c01dc66c>] do_writepages+0x1c/0x40 Jan 11 07:06:11 myserver kernel: [46080.212413] [<c0232a15>] writeback_single_inode+0xd5/0x380 Jan 11 07:06:11 myserver kernel: [46080.212418] [<c02331f9>] writeback_sb_inodes+0x149/0x230 Jan 11 07:06:11 myserver kernel: [46080.212422] [<c023364a>] writeback_inodes_wb+0x8a/0x160 Jan 11 07:06:11 myserver kernel: [46080.212427] [<c0233903>] wb_writeback+0x1e3/0x230 Jan 11 07:06:11 myserver kernel: [46080.212433] [<c0233a81>] wb_do_writeback+0x131/0x140 Jan 11 07:06:11 myserver kernel: [46080.212438] [<c0233acb>] bdi_writeback_task+0x3b/0xb0 Jan 11 07:06:11 myserver kernel: [46080.212443] [<c01eb9e0>] ? bdi_start_fn+0x0/0xc0 Jan 11 07:06:11 myserver kernel: [46080.212447] [<c01eba3d>] bdi_start_fn+0x5d/0xc0 Jan 11 07:06:11 myserver kernel: [46080.212451] [<c01eb9e0>] ? bdi_start_fn+0x0/0xc0 Jan 11 07:06:11 myserver kernel: [46080.212455] [<c0170bb4>] kthread+0x74/0x80 Jan 11 07:06:11 myserver kernel: [46080.212459] [<c0170b40>] ? kthread+0x0/0x80 Jan 11 07:06:11 myserver kernel: [46080.212464] [<c010a467>] kernel_thread_helper+0x7/0x10 Jan 11 07:08:11 myserver kernel: [46200.212124] INFO: task jbd2/nbd1-8:12704 blocked for more than 120 seconds.

3 3

Have I bought the wrong kit?
by Chris Walker 11 Jan '13

11 Jan '13

I am fed up with the cheap Huawei router that Talktalk supply so decided I would go for something that will run ddwrt. Having looked at the ddwrt site, I then started looking at Amazon. I decided I would buy a Buffalo Air Station and went for a WZR-HP-AG300H. But it tells me I should connect it to my modem. <Thinks> Hmm. Thought that was built-in. Look again at spec. B*gger. So should I buy a cheap ADSL modem or ask Amazon if they'll take it back and buy another Air Station but this time, one with the correct specs?

2 1