I guess the question is should this bug be reported.  The final cause of
this glitch is this:  "No space left on device"  I ran out of ramdisk
while trying to report some previous bug.

There are some things in the logs that I would like to ask about.  Early
on I get this entry,

"weird, boot CPU (#0) not listedby the BIOS.  Mar 12 17:36:01 ubuntu
kernel: [    1.328854] SMP motherboard not detected."  Should I be
concerned about that?

I seem to be having problems with my CD drive.  I have tested it using a 
Windows-based tool, and the drive checks out OK.  I am booting from the CD, so 
this could be a real problem:  "sr 1:0:1:0: [sr0] Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE,SUGGEST_OK
Mar 14 07:20:20 ubuntu kernel: [118135.522057] sr 1:0:1:0: [sr0] Sense Key : 
Medium Error [current] 
Mar 14 07:20:20 ubuntu kernel: [118135.522079] sr 1:0:1:0: [sr0] Add. Sense: No 
seek complete
Mar 14 07:20:20 ubuntu kernel: [118135.522101] end_request: I/O error, dev sr0, 
sector 1381812
Mar 14 07:20:20 ubuntu kernel: [118135.522135] Buffer I/O error on device sr0, 
logical block 345453
Mar 14 07:20:20 ubuntu kernel: [118135.522160] Buffer I/O error on device sr0, 
logical block 345454
Mar 14 07:20:20 ubuntu kernel: [118135.522462] SQUASHFS error: sb_bread failed 
reading block 0xa81e9
Mar 14 07:20:20 ubuntu kernel: [118135.522489] SQUASHFS error: Unable to read 
fragment cache block [2a073743]

I thank you for any info you can provide.
Paul

** Changed in: gcc-4.3 (Ubuntu)
       Status: New => Invalid

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/gcc-4.3/+question/71363

-- 
package gcc-4.3 4.3.2-1ubuntu11 failed to install/upgrade: failed in 
buffer_write(fd) (10, ret=-1): backend dpkg-deb during 
`./usr/lib/gcc/i486-linux-gnu/4.3/libgcc.a'
https://bugs.launchpad.net/bugs/342844
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

Reply via email to