HELP! Orange San Francisco stuck on green man

[Guest Manbag]

Hello All

I am a bit of a noob that would appreciate some assistance.

I got the SanFran and flashed successfully. Got the new icon in the apps screen. Happy days.

I then put the r3 image on on to the SD card. Think this is where I messed up. I changed the file name of boot.blade.superboot.mcri.r3.img to the .gz one and put this on the memory card.

Now when I turn it on I get stuck on the Green Android man and the only way I can turn the power on or off is removing the battery. Phone is not recognised by laptop. I checked the card on a reader and the file came back as .flashed, so am presuming it's an issue with the ROM I am using.

Is there anyway I can reset to the stock ROM?

Any help would be most appreciated!

[Guest zillfish]

hi,

I've a similar problem to others on this thread i.e.,stuck at green android at power on. I've followed lonegunman's excellent instructions but at the first use of the cmd prompt it retuns "waiting for device", and nothing more happens.

my device manager doesn't show any probs, and if I click "safely remove hardware", it comes up with "android composite adb device", and "mass storage device-drive e".

This seems to mean that the pc is seeing the phone ok.(is that right?)

Any ideas on how to get into phone?

[Guest StevenHarperUK]

hi,

I've a similar problem to others on this thread i.e.,stuck at green android at power on. I've followed lonegunman's excellent instructions but at the first use of the cmd prompt it retuns "waiting for device", and nothing more happens.

my device manager doesn't show any probs, and if I click "safely remove hardware", it comes up with "android composite adb device", and "mass storage device-drive e".

This seems to mean that the pc is seeing the phone ok.(is that right?)

Any ideas on how to get into phone?

Many users have driver/connection problems in windows XP / Vista / Windows 7 - all of the users that have tried the same procedure on an Ubuntu Live CD have had no problems.

I recommend you use an Ubuntu live CD

To do this:

• Download a 32bit 10.10 CD from
  http://www.ubuntu.com/desktop/get-ubuntu/download
  - it will be in
  .iso
  format
  
  
• Download ImgBurn from
  http://www.imgburn.com/index.php?act=download
  
  
• Burn the .iso file to a new blank CD
  
  
• Boot from the new CD (This will not change your current OS, Ubuntu runs from the CD) - You may need to change your bios boot order to look for the CD before your harddisk. In your computers bios you get to choose which drive the PC will boot from first : Modern machines have F12 or F10 to choose which drive to boot from as the machine boots.
  
  

[Guest zillfish]

Many users have driver/connection problems in windows XP / Vista / Windows 7 - all of the users that have tried the same procedure on an Ubuntu Live CD have had no problems.

I recommend you use an Ubuntu live CD

To do this:

• Download a 32bit 10.10 CD from
  http://www.ubuntu.com/desktop/get-ubuntu/download
  - it will be in
  .iso
  format
  
  
• Download ImgBurn from
  http://www.imgburn.com/index.php?act=download
  
  
• Burn the .iso file to a new blank CD
  
  
• Boot from the new CD (This will not change your current OS, Ubuntu runs from the CD) - You may need to change your bios boot order to look for the CD before your harddisk. In your computers bios you get to choose which drive the PC will boot from first : Modern machines have F12 or F10 to choose which drive to boot from as the machine boots.
  
  

Thanks for that advice, I'll see if I can do it. It might be a bit complex for me. just to get it clear, once i'm working in ubuntu,(is that linux?), do I follow the same procedure as before, or do I need different fastboot,mrci,etc.

[Guest StevenHarperUK]

Thanks for that advice, I'll see if I can do it. It might be a bit complex for me. just to get it clear, once i'm working in ubuntu,(is that linux?), do I follow the same procedure as before, or do I need different fastboot,mrci,etc.

Follow my guide here.

http://android.modaco.com/content/zte-blad...and-other-roms/

[Guest zillfish]

Follow my guide here.

http://android.modaco.com/content/zte-blad...and-other-roms/

followed your guide for ubuntu, quite a learning curve for me,working with new operating system. The end result is identical to before, command window hangs at "waiting for device".

I was working on a netbook originally, but I've done the ubuntu stuff on my desktop, cos I'd downloaded so many files from modaco it was getting confusing. What I noticed is that the pc didn't prompt me to install drivers, (I hadn't usb'd the phone to it previously), is this strange, or does linux work differently?

I think I'm going to have to return phone, but have persisted with it cos i know there aren't any more with oled screens.

I'm dead sick about this but barring some last minute brilliance from one of the experts I have no choice.

I've enjoyed the challenge of ubuntu, and will try to use it more, so thanks for the help, great resource.

[Guest StevenHarperUK]

followed your guide for ubuntu, quite a learning curve for me,working with new operating system. The end result is identical to before, command window hangs at "waiting for device".

I was working on a netbook originally, but I've done the ubuntu stuff on my desktop, cos I'd downloaded so many files from modaco it was getting confusing. What I noticed is that the pc didn't prompt me to install drivers, (I hadn't usb'd the phone to it previously), is this strange, or does linux work differently?

I think I'm going to have to return phone, but have persisted with it cos i know there aren't any more with oled screens.

I'm dead sick about this but barring some last minute brilliance from one of the experts I have no choice.

I've enjoyed the challenge of ubuntu, and will try to use it more, so thanks for the help, great resource.

There are no drivers needed.

Can I just Check:

You made an Ubuntu 10.10 CD

You downloaded and extracted fastboot

You unplugged and shutdown the phone

You Turned the phone on and HELD the UP VOLUME button

The Android (green) stuck on the screen

You connected the USB cable

You opened a Terminal (Applications | Accessories Terminal

You ran the commands

cd Desktop/fastboot

sudo ./fastboot-linux flash recovery recovery-clockwork-2.5.0.9-modaco-r2-blade.img[/code]


Is that right?


Please try more than 1 USB slot on your PC

Also try this WITHOUT the SD Card in the phone


p.p.s If you can get to Clockwork then you should not a have a broken phone - Don't give up just yet - PM me if this doesn't work and we can switch to a Phone call - I'll call you - Its free - I work for Orange :) (this isn't my job - I write code)

Edited December 12, 2010 by StevenHarperUK

[Guest zillfish]

There are no drivers needed.

Can I just Check:

You made an Ubuntu 10.10 CD

You downloaded and extracted fastboot

You unplugged and shutdown the phone

You Turned the phone on and HELD the UP VOLUME button

The Android (green) stuck on the screen

You connected the USB cable

You opened a Terminal (Applications | Accessories Terminal

You ran the commands

cd Desktop/fastboot

sudo ./fastboot-linux flash recovery recovery-clockwork-2.5.0.9-modaco-r2-blade.img

Is that right?

Please try more than 1 USB slot on your PC

Also try this WITHOUT the SD Card in the phone

p.p.s If you can get to Clockwork then you should not a have a broken phone - Don't give up just yet - PM me if this doesn't work and we can switch to a Phone call - I'll call you - Its free - I work for Orange :) (this isn't my job - I write code)

Thanks for persisting with me, it would be amazing if we could recover this phone.

in answer to your questions:

yes I did follow all your instructions,

I didn't try another usb slot, I will do that soon.

the sd card wasn't in the phone at the time.

What is "pm" in this context?

thanks again.

[Guest zillfish]

Thanks for persisting with me, it would be amazing if we could recover this phone.

in answer to your questions:

yes I did follow all your instructions,

I didn't try another usb slot, I will do that soon.

the sd card wasn't in the phone at the time.

What is "pm" in this context

I've found out about "pm", I should have searched before asking, sorry.

I don't think it matters, but I'm running ubuntu from usb stick not actual cd.

[Guest StevenHarperUK]

I've found out about "pm", I should have searched before asking, sorry.

I don't think it matters, but I'm running ubuntu from usb stick not actual cd.

Doesn't matter.

Try opening another terminal windows and run the command

tail -f /var/log/syslog

When you plug the phone in (in Fastboot mode) you should see some output - copy it and post it if it doesn't work.

[Guest zillfish]

Doesn't matter.

Try opening another terminal windows and run the command

tail -f /var/log/syslog

When you plug the phone in (in Fastboot mode) you should see some output - copy it and post it if it doesn't work.

sorry to be so stupid, but do I use this cmd when the first window is hanging at "waiting for device", or just usb the phone (v+ method), and do it straight away?

[Guest zillfish]

sorry to be so stupid, but do I use this cmd when the first window is hanging at "waiting for device", or just usb the phone (v+ method), and do it straight away?

hi again,

tried new cmd just plugging phone in, thid is what I got back:

ubuntu@ubuntu:~$ tail -f /var/log/syslog

Dec 13 11:34:22 ubuntu kernel: [ 193.982426] serial8250: too much work for irq17

Dec 13 11:34:22 ubuntu kernel: [ 193.987877] serial8250: too much work for irq17

Dec 13 11:34:22 ubuntu kernel: [ 193.990557] serial8250: too much work for irq17

Dec 13 11:34:22 ubuntu kernel: [ 194.004344] serial8250: too much work for irq17

Dec 13 11:34:24 ubuntu kernel: [ 195.859111] serial8250: too much work for irq17

Dec 13 11:41:37 ubuntu kernel: [ 629.048042] usb 1-6: new high speed USB device using ehci_hcd and address 4

Dec 13 11:41:37 ubuntu kernel: [ 629.209158] scsi3 : usb-storage 1-6:1.1

Dec 13 11:41:38 ubuntu kernel: [ 630.221104] scsi 3:0:0:0: Direct-Access ZTE Mass Storage ffff PQ: 0 ANSI: 2

Dec 13 11:41:38 ubuntu kernel: [ 630.230290] sd 3:0:0:0: Attached scsi generic sg6 type 0

Dec 13 11:41:38 ubuntu kernel: [ 630.239227] sd 3:0:0:0: [sdd] Attached SCSI removable disk

don't mean anything to me, how about you?

Why do lose all my downloaded files when I restart ubuntu? I've got to start again every time.

Edited December 13, 2010 by zillfish

[Guest zillfish]

hi again,

tried new cmd just plugging phone in, thid is what I got back:

T

my first copy of log might have got confused with other stuff when pasting, so I've done it again. Does it mean anything?

Why do lose all my downloaded files when I restart ubuntu? I've got to start again every time.

ubuntu@ubuntu:~$ tail -f /var/log/syslog

Dec 13 11:45:34 ubuntu kernel: [ 865.619825] sdd: sdd1

Dec 13 11:45:34 ubuntu kernel: [ 865.999373] sd 4:0:0:0: [sdd] Assuming drive cache: write through

Dec 13 11:45:34 ubuntu kernel: [ 865.999390] sd 4:0:0:0: [sdd] Attached SCSI removable disk

Dec 13 11:52:32 ubuntu kernel: [ 1284.121896] usb 1-6: USB disconnect, address 5

Dec 13 12:17:01 ubuntu CRON[4732]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)

Dec 13 13:08:48 ubuntu kernel: [ 5860.376045] usb 1-6: new high speed USB device using ehci_hcd and address 6

Dec 13 13:08:48 ubuntu kernel: [ 5860.536216] scsi5 : usb-storage 1-6:1.1

Dec 13 13:08:49 ubuntu kernel: [ 5861.549073] scsi 5:0:0:0: Direct-Access ZTE Mass Storage ffff PQ: 0 ANSI: 2

Dec 13 13:08:49 ubuntu kernel: [ 5861.558969] sd 5:0:0:0: Attached scsi generic sg6 type 0

Dec 13 13:08:49 ubuntu kernel: [ 5861.573311] sd 5:0:0:0: [sdd] Attached SCSI removable disk

Dec 13 13:17:01 ubuntu CRON[4796]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)

Edited December 13, 2010 by zillfish

[Guest zillfish]

This is what I get when I follow your guide:

ubuntu@ubuntu:~$ cd Desktop/fastboot

ubuntu@ubuntu:~/Desktop/fastboot$ md5sum recovery-clockwork-2.5.0.9-modaco-r2-blade.img

d7664757ec3d4862cc408b7304e4df8f recovery-clockwork-2.5.0.9-modaco-r2-blade.img

ubuntu@ubuntu:~/Desktop/fastboot$ sudo ./fastboot-linux flash recovery recovery-clockwork-2.5.0.9-modaco-r2-blade.img

< waiting for device >

Am I doing it right?

[Guest StevenHarperUK]

This is what I get when I follow your guide:

ubuntu@ubuntu:~$ cd Desktop/fastboot

ubuntu@ubuntu:~/Desktop/fastboot$ md5sum recovery-clockwork-2.5.0.9-modaco-r2-blade.img

d7664757ec3d4862cc408b7304e4df8f recovery-clockwork-2.5.0.9-modaco-r2-blade.img

ubuntu@ubuntu:~/Desktop/fastboot$ sudo ./fastboot-linux flash recovery recovery-clockwork-2.5.0.9-modaco-r2-blade.img

< waiting for device >

Am I doing it right?

The downloads dissapears because Ubuntu is running off a LIVE USB - this means its running in read only - its not installed onto your computer - the pen drive is never supposed to be altered.

You are doing the command right YES!

Let must do exactly the same thing with my Blade and compare it to my log : ill get back to you in a few minutes

[Guest StevenHarperUK]

The downloads dissapears because Ubuntu is running off a LIVE USB - this means its running in read only - its not installed onto your computer - the pen drive is never supposed to be altered.

You are doing the command right YES!

Let must do exactly the same thing with my Blade and compare it to my log : ill get back to you in a few minutes

What is on your Phones screen when you plug it in???

It should be the Green android

in my log I see

Dec 13 16:06:21 shnitsel kernel: [282723.831110] usb 1-4.3: new high speed USB device using ehci_hcd and address 11

Your response has a lot more

Dec 13 13:08:48 ubuntu kernel: [ 5860.376045] usb 1-6: new high speed USB device using ehci_hcd and address 6

Dec 13 13:08:49 ubuntu kernel: [ 5861.549073] scsi 5:0:0:0: Direct-Access ZTE Mass Storage ffff PQ: 0 ANSI: 2

Dec 13 13:08:49 ubuntu kernel: [ 5861.558969] sd 5:0:0:0: Attached scsi generic sg6 type 0

Dec 13 13:08:49 ubuntu kernel: [ 5861.573311] sd 5:0:0:0: [sdd] Attached SCSI removable disk[/code]



This means that you phone is listening trying to be a USB Disk.... this is wrong


Your phone is not in the mode ready to talk to fastboot.

Edited December 13, 2010 by StevenHarperUK

[Guest zillfish]

What is on your Phones screen when you plug it in???

It should be the Green android

in my log I see

Dec 13 16:06:21 shnitsel kernel: [282723.831110] usb 1-4.3: new high speed USB device using ehci_hcd and address 11

Your response has a lot more

Dec 13 13:08:48 ubuntu kernel: [ 5860.376045] usb 1-6: new high speed USB device using ehci_hcd and address 6

Dec 13 13:08:49 ubuntu kernel: [ 5861.549073] scsi 5:0:0:0: Direct-Access ZTE Mass Storage ffff PQ: 0 ANSI: 2

Dec 13 13:08:49 ubuntu kernel: [ 5861.558969] sd 5:0:0:0: Attached scsi generic sg6 type 0

Dec 13 13:08:49 ubuntu kernel: [ 5861.573311] sd 5:0:0:0: [sdd] Attached SCSI removable disk

This means that you phone is listening trying to be a USB Disk.... this is wrong

Your phone is not in the mode ready to talk to fastboot.

right, when I power on the phone with v+, it sticks at green android,

likewise with power button only.

power and v- gives android initially for a few seconds, then a flash of orange square logo, then FTM, where it sticks, and as with other start-up methods you have to remove battery, (I have found a reset button also), to power down.

thanks for ubuntu advice.

you still think there's a chance?

[Guest hecatae]

right, when I power on the phone with v+, it sticks at green android,

likewise with power button only.

power and v- gives android initially for a few seconds, then a flash of orange square logo, then FTM, where it sticks, and as with other start-up methods you have to remove battery, (I have found a reset button also), to power down.

thanks for ubuntu advice.

you still think there's a chance?

have you taken the micro sd out? that will stop the sd card trying to register itself as a mass storage device

miht be worth running the command as

sudo su

Edited December 13, 2010 by hecatae

[Guest zillfish]

have you taken the micro sd out? that will stop the sd card trying to register itself as a mass storage device

miht be worth running the command as

sudo su

sd is already out.

is this what you meant?

ubuntu@ubuntu:~$ sudo su

root@ubuntu:/home/ubuntu#

[Guest hecatae]

yes,

sudo su

then

ls

to check what folder you are in

then

cd /home/ubuntu/Downloads/

ls

to confirm fastboot-linux and recovery-clockwork-2.5.0.9-modaco-r2-blade.img are in that folder

then

./fastboot-linux flash recovery recovery-clockwork-2.5.0.9-modaco-r2-blade.img

Edited December 13, 2010 by hecatae

[Guest zillfish]

yes,

sudo su

then

ls

to check what folder you are in

then

cd /home/ubuntu/Downloads/

ls

to confirm fastboot-linux and recovery-clockwork-2.5.0.9-modaco-r2-blade.img are in that folder

then

./fastboot-linux flash recovery recovery-clockwork-2.5.0.9-modaco-r2-blade.img

this didn't work, as you may see below. my downloads are now in the home folder called ubuntu, i should probably alter the code to allow for this, but I'd only be guessing and wouldn't know if failure is down to my lack of competence

ubuntu@ubuntu:~$ sudo su

root@ubuntu:/home/ubuntu# ls

Desktop fastboot Pictures Templates

Documents fastboot.zip Public Videos

Downloads Music r4-update-modacocustomrom-blade-signed.zip

root@ubuntu:/home/ubuntu# cd /home/ubuntu/Downloads/

root@ubuntu:/home/ubuntu/Downloads# ls

root@ubuntu:/home/ubuntu/Downloads# ./fastboot-linux flash recovery recovery-clockwork-2.5.0.9-modaco-r2-blade.img

bash: ./fastboot-linux: No such file or directory

root@ubuntu:/home/ubuntu/Downloads#

cheers for your continued support.

[Guest hecatae]

cd /home/ubuntu/

instead of cd /home/ubuntu/Downloads/ then

run

./fastboot flash recovery recovery-clockwork-2.5.0.9-modaco-r2-blade.img

without the phone attached. it should go to waiting for device, power on phone in fast boot mode then attach to usb cable

and you would need to unzip the fastboot.zip folder, grab fastboot-linux.sh and place it in /home/ubuntu/

Edited December 13, 2010 by hecatae

[Guest zillfish]

cd /home/ubuntu/

instead of

cd /home/ubuntu/Downloads/

then

run

./fastboot flash recovery recovery-clockwork-2.5.0.9-modaco-r2-blade.img

without the phone attached. it should go to waiting for device, power on phone in fast boot mode then attach to usb cable

and you would need to unzip the fastboot.zip folder, grab fastboot-linux.sh and place it in /home/ubuntu/

as you can see below, I've tried different cmds to no effect. Ireally don't know what I am doing.

ubuntu@ubuntu:~$ cd /home

ubuntu@ubuntu:/home$ /ubuntu/Downloads/

bash: /ubuntu/Downloads/: No such file or directory

ubuntu@ubuntu:/home$ cd /home/ubunu

bash: cd: /home/ubunu: No such file or directory

ubuntu@ubuntu:/home$ cd /home/ubuntu

ubuntu@ubuntu:~$ cd /home/ubuntu/Downloads

ubuntu@ubuntu:~/Downloads$ ./fastboot flash recovery recovery-clockwork-2.5.0.9-modaco-r2-blade.img

bash: ./fastboot: No such file or directory

ubuntu@ubuntu:~/Downloads$ fastboot flash recovery recovery-clockwork-2.5.0.9-modaco-r2-blade.img

fastboot: command not found

ubuntu@ubuntu:~/Downloads$

[Guest hecatae]

type

dmesg

and post please

[Guest zillfish]

type

dmesg

and post please

there's a lot of it! probably mostly c**p

rio0/input/input2

[ 4.207444] isapnp: No Plug & Play device found

[ 4.207523] ata1.00: ATA-6: WDC WD400BB-75FJA1, 14.03G14, max UDMA/100

[ 4.207578] ata1.00: 78125000 sectors, multi 8: LBA

[ 4.207850] ata1.01: ATA-5: MAXTOR 6L040J2, A93.0500, max UDMA/133

[ 4.207909] ata1.01: 78177792 sectors, multi 8: LBA

[ 4.207991] ata1.00: limited to UDMA/33 due to 40-wire cable

[ 4.208080] ata1.01: limited to UDMA/33 due to 40-wire cable

[ 4.216639] ata1.00: configured for UDMA/33

[ 4.232513] ata1.01: configured for UDMA/33

[ 4.232864] scsi 0:0:0:0: Direct-Access ATA WDC WD400BB-75FJ 14.0 PQ: 0 ANSI: 5

[ 4.233303] sd 0:0:0:0: Attached scsi generic sg0 type 0

[ 4.233755] sd 0:0:0:0: [sda] 78125000 512-byte logical blocks: (40.0 GB/37.2 GiB)

[ 4.234073] sd 0:0:0:0: [sda] Write Protect is off

[ 4.234129] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00

[ 4.234244] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

[ 4.234948] sda:

[ 4.240802] ata2.00: ATAPI: HL-DT-ST RW/DVD GCC-4481B, E106, max UDMA/33

[ 4.240952] ata2.01: ATAPI: SONY DVD RW DW-G120A, MYR4, max UDMA/66

[ 4.241038] ata2.01: limited to UDMA/33 due to 40-wire cable

[ 4.245345] sda1 sda2 sda3

[ 4.246073] scsi 0:0:1:0: Direct-Access ATA MAXTOR 6L040J2 A93. PQ: 0 ANSI: 5

[ 4.246477] sd 0:0:1:0: Attached scsi generic sg1 type 0

[ 4.246834] sd 0:0:1:0: [sdb] 78177792 512-byte logical blocks: (40.0 GB/37.2 GiB)

[ 4.247506] sd 0:0:1:0: [sdb] Write Protect is off

[ 4.247564] sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00

[ 4.247678] sd 0:0:0:0: [sda] Attached SCSI disk

[ 4.247817] sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

[ 4.248758] sdb: sdb1

[ 4.256278] ata2.00: configured for UDMA/33

[ 4.256597] sd 0:0:1:0: [sdb] Attached SCSI disk

[ 4.288308] ata2.01: configured for UDMA/33

[ 4.291262] scsi 1:0:0:0: CD-ROM HL-DT-ST RW/DVD GCC-4481B E106 PQ: 0 ANSI: 5

[ 4.293911] sr0: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray

[ 4.293978] Uniform CD-ROM driver Revision: 3.20

[ 4.294273] sr 1:0:0:0: Attached scsi CD-ROM sr0

[ 4.294451] sr 1:0:0:0: Attached scsi generic sg2 type 5

[ 4.295703] scsi 1:0:1:0: CD-ROM SONY DVD RW DW-G120A MYR4 PQ: 0 ANSI: 5

[ 4.300662] sr1: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray

[ 4.300993] sr 1:0:1:0: Attached scsi CD-ROM sr1

[ 4.301178] sr 1:0:1:0: Attached scsi generic sg3 type 5

[ 4.316098] usb 1-3: new high speed USB device using ehci_hcd and address 2

[ 4.817886] Freeing initrd memory: 11144k freed

[ 4.841233] Freeing unused kernel memory: 684k freed

[ 4.842720] Write protecting the kernel text: 4932k

[ 4.842820] Write protecting the kernel read-only data: 1976k

[ 4.908196] udev[73]: starting version 163

[ 5.104302] usb 3-2: new low speed USB device using uhci_hcd and address 2

[ 5.477038] FDC 0 is a post-1991 82077

[ 5.496357] Linux agpgart interface v0.103

[ 5.590217] agpgart-intel 0000:00:00.0: Intel 830M Chipset

[ 5.590552] agpgart-intel 0000:00:00.0: detected 892K stolen memory

[ 5.612934] Initializing USB Mass Storage driver...

[ 5.620625] agpgart-intel 0000:00:00.0: AGP aperture is 128M @ 0xe8000000

[ 5.635172] b44 0000:01:09.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17

[ 5.644805] scsi2 : usb-storage 1-3:1.0

[ 5.661771] usbcore: registered new interface driver usb-storage

[ 5.661831] USB Mass Storage support registered.

[ 5.672202] ssb: Core 0 found: Fast Ethernet (cc 0x806, rev 0x04, vendor 0x4243)

[ 5.672214] ssb: Core 1 found: V90 (cc 0x807, rev 0x01, vendor 0x4243)

[ 5.672222] ssb: Core 2 found: PCI (cc 0x804, rev 0x02, vendor 0x4243)

[ 5.689337] usbcore: registered new interface driver hiddev

[ 5.713337] input: Cypress Sem PS2/USB Browser Combo Mouse as /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/input/input3

[ 5.713751] generic-usb 0003:05FE:0011.0001: input,hidraw0: USB HID v1.00 Mouse [Cypress Sem PS2/USB Browser Combo Mouse] on usb-0000:00:1d.1-2/input0

[ 5.713871] usbcore: registered new interface driver usbhid

[ 5.713943] usbhid: USB HID core driver

[ 5.716219] ssb: Sonics Silicon Backplane found on PCI device 0000:01:09.0

[ 5.716323] b44: b44.c:v2.0

[ 5.760996] b44 ssb0:0: eth0: Broadcom 44xx/47xx 10/100BaseT Ethernet 00:0f:1f:5d:0f:c8

[ 5.775480] [drm] Initialized drm 1.1.0 20060810

[ 5.829208] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16

[ 5.829276] i915 0000:00:02.0: setting latency timer to 64

[ 5.848844] [drm] set up 7M of stolen space

[ 5.875816] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem

[ 5.876342] [drm] initialized overlay support

[ 6.129598] Console: switching to colour frame buffer device 240x67

[ 6.141466] fb0: inteldrmfb frame buffer device

[ 6.141521] drm: registered panic notifier

[ 6.141585] Slow work thread pool: Starting up

[ 6.141840] Slow work thread pool: Ready

[ 6.141936] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0

[ 6.661618] scsi 2:0:0:0: Direct-Access SanDisk Cruzer 8.02 PQ: 0 ANSI: 0 CCS

[ 6.662377] scsi 2:0:0:1: CD-ROM SanDisk Cruzer 8.02 PQ: 0 ANSI: 0

[ 6.667289] sd 2:0:0:0: Attached scsi generic sg4 type 0

[ 6.678263] sd 2:0:0:0: [sdc] 15704063 512-byte logical blocks: (8.04 GB/7.48 GiB)

[ 6.678890] sr2: scsi3-mmc drive: 48x/48x tray

[ 6.681155] sr 2:0:0:1: Attached scsi CD-ROM sr2

[ 6.681918] sr 2:0:0:1: Attached scsi generic sg5 type 5

[ 6.682551] sd 2:0:0:0: [sdc] Write Protect is off

[ 6.682639] sd 2:0:0:0: [sdc] Mode Sense: 45 00 00 08

[ 6.682644] sd 2:0:0:0: [sdc] Assuming drive cache: write through

[ 6.685508] sd 2:0:0:0: [sdc] Assuming drive cache: write through

[ 6.685622] sdc: sdc1

[ 6.690728] sd 2:0:0:0: [sdc] Assuming drive cache: write through

[ 6.690828] sd 2:0:0:0: [sdc] Attached SCSI removable disk

[ 7.416773] Btrfs loaded

[ 7.435989] xor: automatically using best checksumming function: pIII_sse

[ 7.456016] pIII_sse : 3312.000 MB/sec

[ 7.456021] xor: using function: pIII_sse (3312.000 MB/sec)

[ 7.463320] device-mapper: dm-raid45: initialized v0.2594b

[ 9.822427] aufs 2-standalone.tree-35-rcN-20100705

[ 9.898237] squashfs: version 4.0 (2009/01/31) Phillip Lougher

[ 11.664318] sr 2:0:0:1: [sr2] Unhandled sense code

[ 11.664328] sr 2:0:0:1: [sr2] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE

[ 11.664334] sr 2:0:0:1: [sr2] Sense Key : Hardware Error [current]

[ 11.664340] sr 2:0:0:1: [sr2] Add. Sense: No additional sense information

[ 11.664346] sr 2:0:0:1: [sr2] CDB: Read(10): 28 00 00 00 bf c0 00 00 02 00

[ 11.664358] end_request: I/O error, dev sr2, sector 196352

[ 11.664365] Buffer I/O error on device sr2, logical block 49088

[ 11.664371] Buffer I/O error on device sr2, logical block 49089

[ 11.667943] sr 2:0:0:1: [sr2] Unhandled sense code

[ 11.667953] sr 2:0:0:1: [sr2] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE

[ 11.667959] sr 2:0:0:1: [sr2] Sense Key : Hardware Error [current]

[ 11.667964] sr 2:0:0:1: [sr2] Add. Sense: No additional sense information

[ 11.667970] sr 2:0:0:1: [sr2] CDB: Read(10): 28 00 00 00 bf c0 00 00 02 00

[ 11.667981] end_request: I/O error, dev sr2, sector 196352

[ 11.667986] Buffer I/O error on device sr2, logical block 49088

[ 11.667994] Buffer I/O error on device sr2, logical block 49089

[ 11.672951] sr 2:0:0:1: [sr2] Unhandled sense code

[ 11.672962] sr 2:0:0:1: [sr2] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE

[ 11.672969] sr 2:0:0:1: [sr2] Sense Key : Hardware Error [current]

[ 11.672974] sr 2:0:0:1: [sr2] Add. Sense: No additional sense information

[ 11.672980] sr 2:0:0:1: [sr2] CDB: Read(10): 28 00 00 00 bf fa 00 00 02 00

[ 11.672992] end_request: I/O error, dev sr2, sector 196584

[ 11.672998] Buffer I/O error on device sr2, logical block 49146

[ 11.673006] Buffer I/O error on device sr2, logical block 49147

[ 11.676703] sr 2:0:0:1: [sr2] Unhandled sense code

[ 11.676711] sr 2:0:0:1: [sr2] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE

[ 11.676717] sr 2:0:0:1: [sr2] Sense Key : Hardware Error [current]

[ 11.676723] sr 2:0:0:1: [sr2] Add. Sense: No additional sense information

[ 11.676729] sr 2:0:0:1: [sr2] CDB: Read(10): 28 00 00 00 bf fa 00 00 02 00

[ 11.676740] end_request: I/O error, dev sr2, sector 196584

[ 11.676747] Buffer I/O error on device sr2, logical block 49146

[ 11.676753] Buffer I/O error on device sr2, logical block 49147

[ 11.682072] sr 2:0:0:1: [sr2] Unhandled sense code

[ 11.682084] sr 2:0:0:1: [sr2] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE

[ 11.682090] sr 2:0:0:1: [sr2] Sense Key : Hardware Error [current]

[ 11.682096] sr 2:0:0:1: [sr2] Add. Sense: No additional sense information

[ 11.682102] sr 2:0:0:1: [sr2] CDB: Read(10): 28 00 00 00 bf fe 00 00 01 00

[ 11.682114] end_request: I/O error, dev sr2, sector 196600

[ 11.682120] Buffer I/O error on device sr2, logical block 49150

[ 11.685816] sr 2:0:0:1: [sr2] Unhandled sense code

[ 11.685826] sr 2:0:0:1: [sr2] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE

[ 11.685833] sr 2:0:0:1: [sr2] Sense Key : Hardware Error [current]

[ 11.685838] sr 2:0:0:1: [sr2] Add. Sense: No additional sense information

[ 11.685844] sr 2:0:0:1: [sr2] CDB: Read(10): 28 00 00 00 bf fe 00 00 01 00

[ 11.685855] end_request: I/O error, dev sr2, sector 196600

[ 11.685860] Buffer I/O error on device sr2, logical block 49150

[ 11.690697] sr 2:0:0:1: [sr2] Unhandled sense code

[ 11.690708] sr 2:0:0:1: [sr2] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE

[ 11.690714] sr 2:0:0:1: [sr2] Sense Key : Hardware Error [current]

[ 11.690720] sr 2:0:0:1: [sr2] Add. Sense: No additional sense information

[ 11.690726] sr 2:0:0:1: [sr2] CDB: Read(10): 28 00 00 00 bf fe 00 00 01 00

[ 11.690737] end_request: I/O error, dev sr2, sector 196600

[ 11.694440] sr 2:0:0:1: [sr2] Unhandled sense code

[ 11.694451] sr 2:0:0:1: [sr2] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE

[ 11.694458] sr 2:0:0:1: [sr2] Sense Key : Hardware Error [current]

[ 11.694464] sr 2:0:0:1: [sr2] Add. Sense: No additional sense information

[ 11.694470] sr 2:0:0:1: [sr2] CDB: Read(10): 28 00 00 00 bf fe 00 00 01 00

[ 11.694482] end_request: I/O error, dev sr2, sector 196600

[ 11.698190] sr 2:0:0:1: [sr2] Unhandled sense code

[ 11.698200] sr 2:0:0:1: [sr2] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE

[ 11.698207] sr 2:0:0:1: [sr2] Sense Key : Hardware Error [current]

[ 11.698213] sr 2:0:0:1: [sr2] Add. Sense: No additional sense information

[ 11.698219] sr 2:0:0:1: [sr2] CDB: Read(10): 28 00 00 00 bf fe 00 00 01 00

[ 11.698229] end_request: I/O error, dev sr2, sector 196600

[ 11.701937] sr 2:0:0:1: [sr2] Unhandled sense code

[ 11.701948] sr 2:0:0:1: [sr2] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE

[ 11.701955] sr 2:0:0:1: [sr2] Sense Key : Hardware Error [current]

[ 11.701961] sr 2:0:0:1: [sr2] Add. Sense: No additional sense information

[ 11.701967] sr 2:0:0:1: [sr2] CDB: Read(10): 28 00 00 00 bf fe 00 00 01 00

[ 11.701978] end_request: I/O error, dev sr2, sector 196600

[ 11.705688] sr 2:0:0:1: [sr2] Unhandled sense code

[ 11.705698] sr 2:0:0:1: [sr2] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE

[ 11.705705] sr 2:0:0:1: [sr2] Sense Key : Hardware Error [current]

[ 11.705711] sr 2:0:0:1: [sr2] Add. Sense: No additional sense information

[ 11.705717] sr 2:0:0:1: [sr2] CDB: Read(10): 28 00 00 00 bf fe 00 00 01 00

[ 11.705728] end_request: I/O error, dev sr2, sector 196600

[ 11.710570] sr 2:0:0:1: [sr2] Unhandled sense code

[ 11.710580] sr 2:0:0:1: [sr2] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE

[ 11.710587] sr 2:0:0:1: [sr2] Sense Key : Hardware Error [current]

[ 11.710593] sr 2:0:0:1: [sr2] Add. Sense: No additional sense information

[ 11.710598] sr 2:0:0:1: [sr2] CDB: Read(10): 28 00 00 00 bf ee 00 00 02 00

[ 11.710610] end_request: I/O error, dev sr2, sector 196536

[ 11.714303] sr 2:0:0:1: [sr2] Unhandled sense code

[ 11.714311] sr 2:0:0:1: [sr2] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE

[ 11.714318] sr 2:0:0:1: [sr2] Sense Key : Hardware Error [current]

[ 11.714323] sr 2:0:0:1: [sr2] Add. Sense: No additional sense information

[ 11.714329] sr 2:0:0:1: [sr2] CDB: Read(10): 28 00 00 00 bf fc 00 00 02 00

[ 11.714340] end_request: I/O error, dev sr2, sector 196592

[ 11.718190] sr 2:0:0:1: [sr2] Unhandled sense code

[ 11.718200] sr 2:0:0:1: [sr2] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE

[ 11.718207] sr 2:0:0:1: [sr2] Sense Key : Hardware Error [current]

[ 11.718213] sr 2:0:0:1: [sr2] Add. Sense: No additional sense information

[ 11.718219] sr 2:0:0:1: [sr2] CDB: Read(10): 28 00 00 00 bf fe 00 00 01 00

[ 11.718230] end_request: I/O error, dev sr2, sector 196600

[ 11.721935] sr 2:0:0:1: [sr2] Unhandled sense code

[ 11.721946] sr 2:0:0:1: [sr2] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE

[ 11.721953] sr 2:0:0:1: [sr2] Sense Key : Hardware Error [current]

[ 11.721959] sr 2:0:0:1: [sr2] Add. Sense: No additional sense information

[ 11.721965] sr 2:0:0:1: [sr2] CDB: Read(10): 28 00 00 00 bf fe 00 00 01 00

[ 11.721976] end_request: I/O error, dev sr2, sector 196600

[ 11.725686] sr 2:0:0:1: [sr2] Unhandled sense code

[ 11.725695] sr 2:0:0:1: [sr2] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE

[ 11.725701] sr 2:0:0:1: [sr2] Sense Key : Hardware Error [current]

[ 11.725707] sr 2:0:0:1: [sr2] Add. Sense: No additional sense information

[ 11.725713] sr 2:0:0:1: [sr2] CDB: Read(10): 28 00 00 00 bf fc 00 00 02 00

[ 11.725725] end_request: I/O error, dev sr2, sector 196592

[ 47.911760] udev[2654]: starting version 163

[ 49.021237] intel_rng: FWH not detected

[ 49.065685] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4

[ 50.796735] Linux video capture interface: v2.00

[ 50.802539] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2)

[ 50.865871] parport_pc 00:09: reported by Plug and Play ACPI

[ 50.865937] parport0: PC-style at 0x378 (0x778), irq 7, using FIFO [PCSPP,TRISTATE,COMPAT,ECP]

[ 51.002574] IR NEC protocol handler initialized

[ 51.232616] IR RC5(x) protocol handler initialized

[ 51.360184] cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.8 loaded

[ 51.420602] cx88[0]: subsystem: 17de:08a6, board: KWorld/VStream XPert DVB-T [card=14,autodetected], frontend(s): 1

[ 51.420612] cx88[0]: TV tuner type 4, Radio tuner type -1

[ 51.440361] IR RC6 protocol handler initialized

[ 51.604859] cx88/0: cx2388x v4l2 driver version 0.0.8 loaded

[ 51.712253] IR JVC protocol handler initialized

[ 52.028262] ADDRCONF(NETDEV_UP): eth0: link is not ready

[ 52.052769] IR Sony protocol handler initialized

[ 52.365426] lirc_dev: IR Remote Control driver registered, major 250

[ 52.464754] IR LIRC bridge handler initialized

[ 52.760175] Registered IR keymap rc-dntv-live-dvb-t

[ 52.760415] input: cx88 IR (KWorld/VStream XPert D as /devices/pci0000:00/0000:00:1e.0/0000:01:06.2/rc/rc0/input4

[ 52.760657] rc0: cx88 IR (KWorld/VStream XPert D as /devices/pci0000:00/0000:00:1e.0/0000:01:06.2/rc/rc0

[ 52.760670] cx88[0]/2: cx2388x 8802 Driver Manager

[ 52.760703] cx88-mpeg driver manager 0000:01:06.2: PCI INT A -> GSI 18 (level, low) -> IRQ 18

[ 52.760716] cx88[0]/2: found at 0000:01:06.2, rev: 5, irq: 18, latency: 64, mmio: 0xfd000000

[ 52.761549] cx8800 0000:01:06.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18

[ 52.761565] cx88[0]/0: found at 0000:01:06.0, rev: 5, irq: 18, latency: 64, mmio: 0xfc000000

[ 52.761842] cx88[0]/0: registered device video0 [v4l2]

[ 52.762013] cx88[0]/0: registered device vbi0

[ 53.193566] ppdev: user-space parallel port driver

[ 53.603813] cx88/2: cx2388x dvb driver version 0.0.8 loaded

[ 53.603820] cx88/2: registering cx8802 driver, type: dvb access: shared

[ 53.603826] cx88[0]/2: subsystem: 17de:08a6, board: KWorld/VStream XPert DVB-T [card=14]

[ 53.603831] cx88[0]/2: cx2388x based DVB/ATSC card

[ 53.603834] cx8802_alloc_frontends() allocating 1 frontend(s)

[ 53.841845] DVB: registering new adapter (cx88[0])

[ 53.841856] DVB: registering adapter 0 frontend 0 (Zarlink MT352 DVB-T)...

[ 54.032130] Intel ICH 0000:00:1f.5: PCI INT B -> GSI 17 (level, low) -> IRQ 17

[ 54.032246] Intel ICH 0000:00:1f.5: setting latency timer to 64

[ 54.468163] intel8x0_measure_ac97_clock: measured 55857 usecs (2691 samples)

[ 54.468170] intel8x0: clocking to 48000

[ 54.816257] b44 ssb0:0: eth0: Link is up at 100 Mbps, full duplex

[ 54.816264] b44 ssb0:0: eth0: Flow control is off for TX and off for RX

[ 54.816602] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

[ 54.826689] serial8250: too much work for irq17

[ 55.198685] serial8250: too much work for irq17

[ 55.582604] serial8250: too much work for irq17

[ 55.596026] serial8250: too much work for irq17

[ 55.604032] serial8250: too much work for irq17

[ 55.632028] serial8250: too much work for irq17

[ 55.640058] serial8250: too much work for irq17

[ 55.763442] lp0: using parport0 (interrupt-driven).

[ 56.034731] serial8250: too much work for irq17

[ 56.280036] serial8250: too much work for irq17

[ 56.328025] serial8250: too much work for irq17

[ 56.530795] serial8250: too much work for irq17

[ 56.582630] serial8250: too much work for irq17

[ 56.590589] serial8250: too much work for irq17

[ 56.592021] serial8250: too much work for irq17

[ 56.780026] serial8250: too much work for irq17

[ 56.838818] serial8250: too much work for irq17

[ 56.840019] serial8250: too much work for irq17

[ 56.888019] serial8250: too much work for irq17

[ 56.980024] serial8250: too much work for irq17

[ 56.986901] serial8250: too much work for irq17

[ 57.088024] serial8250: too much work for irq17

[ 57.092738] serial8250: too much work for irq17

[ 57.340027] serial8250: too much work for irq17

[ 57.343431] serial8250: too much work for irq17

[ 57.528026] serial8250: too much work for irq17

[ 57.540031] serial8250: too much work for irq17

[ 57.570877] serial8250: too much work for irq17

[ 58.088028] serial8250: too much work for irq17

[ 58.180022] serial8250: too much work for irq17

[ 58.195695] serial8250: too much work for irq17

[ 58.354725] serial8250: too much work for irq17

[ 58.740021] serial8250: too much work for irq17

[ 58.744520] serial8250: too much work for irq17

[ 59.058600] serial8250: too much work for irq17

[ 59.060023] serial8250: too much work for irq17

[ 59.063728] serial8250: too much work for irq17

[ 59.095915] serial8250: too much work for irq17

[ 59.099628] serial8250: too much work for irq17

[ 59.132026] serial8250: too much work for irq17

[ 59.635614] serial8250: too much work for irq17

[ 59.667554] serial8250: too much work for irq17

[ 59.668021] serial8250: too much work for irq17

[ 59.672942] serial8250: too much work for irq17

[ 59.720019] serial8250: too much work for irq17

[ 59.728021] serial8250: too much work for irq17

[ 59.752029] serial8250: too much work for irq17

[ 59.871191] serial8250: too much work for irq17

[ 59.904022] serial8250: too much work for irq17

[ 59.907456] serial8250: too much work for irq17

[ 59.940021] serial8250: too much work for irq17

[ 59.943210] serial8250: too much work for irq17

[ 59.976021] serial8250: too much work for irq17

[ 59.978842] serial8250: too much work for irq17

[ 60.012020] serial8250: too much work for irq17

[ 60.032021] serial8250: too much work for irq17

[ 60.064020] serial8250: too much work for irq17

[ 60.084020] serial8250: too much work for irq17

[ 60.087709] serial8250: too much work for irq17

[ 60.120031] serial8250: too much work for irq17

[ 60.152023] serial8250: too much work for irq17

[ 60.156448] serial8250: too much work for irq17

[ 60.188020] serial8250: too much work for irq17

[ 60.192820] serial8250: too much work for irq17

[ 60.196049] serial8250: too much work for irq17

[ 60.230851] serial8250: too much work for irq17

[ 60.232021] serial8250: too much work for irq17

[ 60.236776] serial8250: too much work for irq17

[ 60.272021] serial8250: too much work for irq17

[ 60.275938] serial8250: too much work for irq17

[ 60.277331] serial8250: too much work for irq17

[ 60.281343] serial8250: too much work for irq17

[ 60.312018] serial8250: too much work for irq17

[ 60.594595] serial8250: too much work for irq17

[ 62.478558] serial8250: too much work for irq17

[ 62.571583] serial8250: too much work for irq17

[ 62.583819] serial8250: too much work for irq17

[ 63.128031] serial8250: too much work for irq17

[ 63.136040] serial8250: too much work for irq17

[ 63.963575] serial8250: too much work for irq17

[ 63.964033] serial8250: too much work for irq17

[ 63.969236] serial8250: too much work for irq17

[ 63.972995] serial8250: too much work for irq17

[ 63.984027] serial8250: too much work for irq17

[ 64.602650] serial8250: too much work for irq17

[ 65.600058] eth0: no IPv6 routers present

[ 88.442889] serial8250: too much work for irq17

[ 88.628032] serial8250: too much work for irq17

[ 88.812042] serial8250: too much work for irq17

[ 88.999876] serial8250: too much work for irq17

[ 89.184043] serial8250: too much work for irq17

[ 89.371351] serial8250: too much work for irq17

[ 89.556034] serial8250: too much work for irq17

[ 89.742862] serial8250: too much work for irq17

[ 89.928024] serial8250: too much work for irq17

[ 90.112046] serial8250: too much work for irq17

[ 90.300052] serial8250: too much work for irq17

[ 90.484032] serial8250: too much work for irq17

[ 90.671654] serial8250: too much work for irq17

[ 90.856030] serial8250: too much work for irq17

[ 91.043175] serial8250: too much work for irq17

[ 91.228053] serial8250: too much work for irq17

[ 91.414650] serial8250: too much work for irq17

[ 91.600032] serial8250: too much work for irq17

[ 91.784030] serial8250: too much work for irq17

[ 91.971935] serial8250: too much work for irq17

[ 92.156030] serial8250: too much work for irq17

[ 92.343532] serial8250: too much work for irq17

[ 92.528031] serial8250: too much work for irq17

[ 92.714988] serial8250: too much work for irq17

[ 92.900029] serial8250: too much work for irq17

[ 93.084032] serial8250: too much work for irq17

[ 93.272050] serial8250: too much work for irq17

[ 93.456027] serial8250: too much work for irq17

[ 93.643714] serial8250: too much work for irq17

[ 93.828033] serial8250: too much work for irq17

[ 94.015426] serial8250: too much work for irq17

[ 94.035742] serial8250: too much work for irq17

[ 94.036029] serial8250: too much work for irq17

[ 94.042350] serial8250: too much work for irq17

[ 94.045678] serial8250: too much work for irq17

[ 94.059030] serial8250: too much work for irq17

[ 94.200041] serial8250: too much work for irq17

[ 94.386958] serial8250: too much work for irq17

[ 94.572029] serial8250: too much work for irq17

[ 94.756025] serial8250: too much work for irq17

[ 94.944028] serial8250: too much work for irq17

[ 95.128029] serial8250: too much work for irq17

[ 95.315719] serial8250: too much work for irq17

[ 95.500030] serial8250: too much work for irq17

[ 95.687215] serial8250: too much work for irq17

[ 95.872030] serial8250: too much work for irq17

[ 96.058706] serial8250: too much work for irq17

[ 96.244032] serial8250: too much work for irq17

[ 96.428029] serial8250: too much work for irq17

[ 96.616032] serial8250: too much work for irq17

[ 96.800032] serial8250: too much work for irq17

[ 96.987517] serial8250: too much work for irq17

[ 97.172028] serial8250: too much work for irq17

[ 97.359001] serial8250: too much work for irq17

[ 97.544029] serial8250: too much work for irq17

[ 97.734049] serial8250: too much work for irq17

[ 97.916033] serial8250: too much work for irq17

[ 98.100032] serial8250: too much work for irq17

[ 98.288029] serial8250: too much work for irq17

[ 98.472032] serial8250: too much work for irq17

[ 98.659395] serial8250: too much work for irq17

[ 98.844038] serial8250: too much work for irq17

[ 99.030830] serial8250: too much work for irq17

[ 99.216026] serial8250: too much work for irq17

[ 99.323252] ISO 9660 Extensions: Microsoft Joliet Level 3

[ 99.400033] serial8250: too much work for irq17

[ 99.407997] ISOFS: changing to secondary root

[ 99.588029] serial8250: too much work for irq17

[ 99.772034] serial8250: too much work for irq17

[ 99.959570] serial8250: too much work for irq17

[ 100.144039] serial8250: too much work for irq17

[ 100.331098] serial8250: too much work for irq17

[ 100.516030] serial8250: too much work for irq17

[ 100.702618] serial8250: too much work for irq17

[ 100.888030] serial8250: too much work for irq17

[ 101.072028] serial8250: too much work for irq17

[ 101.259861] serial8250: too much work for irq17

[ 101.444030] serial8250: too much work for irq17

[ 101.631356] serial8250: too much work for irq17

[ 101.816029] serial8250: too much work for irq17

[ 102.002891] serial8250: too much work for irq17

[ 102.188034] serial8250: too much work for irq17

[ 103.205305] serial8250: too much work for irq17

[ 110.402573] serial8250: too much work for irq17

[ 124.107235] serial8250: too much work for irq17

[ 124.109791] serial8250: too much work for irq17

[ 124.113509] serial8250: too much work for irq17

[ 124.116238] serial8250: too much work for irq17

[ 124.130903] serial8250: too much work for irq17

[ 142.879414] serial8250: too much work for irq17

[ 142.912031] serial8250: too much work for irq17

[ 142.915223] serial8250: too much work for irq17

[ 142.916287] serial8250: too much work for irq17

[ 142.926869] serial8250: too much work for irq17

[ 142.958710] serial8250: too much work for irq17

[ 142.960020] serial8250: too much work for irq17

[ 142.992036] serial8250: too much work for irq17

[ 142.996772] serial8250: too much work for irq17

[ 142.999758] serial8250: too much work for irq17

[ 143.044032] serial8250: too much work for irq17

[ 143.047747] serial8250: too much work for irq17

[ 143.080032] serial8250: too much work for irq17

[ 143.085083] serial8250: too much work for irq17

[ 143.088057] serial8250: too much work for irq17

[ 143.118716] serial8250: too much work for irq17

[ 148.296022] serial8250: too much work for irq17

[ 148.380025] serial8250: too much work for irq17

[ 148.384305] serial8250: too much work for irq17

[ 149.380022] serial8250: too much work for irq17

[ 149.384311] serial8250: too much work for irq17

[ 151.382690] serial8250: too much work for irq17

[ 151.384015] serial8250: too much work for irq17

[ 154.185847] serial8250: too much work for irq17

[ 154.187365] serial8250: too much work for irq17

[ 154.192555] serial8250: too much work for irq17

[ 154.195128] serial8250: too much work for irq17

[ 154.207493] serial8250: too much work for irq17

[ 155.383673] serial8250: too much work for irq17

[ 155.384938] serial8250: too much work for irq17

[ 172.264055] usb 1-5: new high speed USB device using ehci_hcd and address 4

[ 172.424196] scsi3 : usb-storage 1-5:1.1

[ 173.433231] scsi 3:0:0:0: Direct-Access ZTE Mass Storage ffff PQ: 0 ANSI: 2

[ 173.442235] sd 3:0:0:0: Attached scsi generic sg6 type 0

[ 173.451353] sd 3:0:0:0: [sdd] Attached SCSI removable disk

[ 184.256028] serial8250: too much work for irq17

[ 184.261090] serial8250: too much work for irq17

[ 184.265112] serial8250: too much work for irq17

[ 184.267891] serial8250: too much work for irq17

[ 184.280027] serial8250: too much work for irq17

ubuntu@ubuntu:~$

Does this lot mean anything?