Upgraded to 2.6.18-4-686, trouble.

Whenever I boot into the 2.6.18-4-686 kernel everything works fine,
but when it starts loading hald I get:

Buffer I/O error on device sr0

It says this about 8 times. I tried reinstalling hal but that didn't
seem to change anything either.

I'm wondering if this is a serious issue (I still have 2.6.18-3-686
installed and it works perfectly, so I can switch back to using that)
or if I'll have to recompile the kernel from source to fix this or
something.

Thanks for your time.

--

No votes yet

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Upgraded to 2.6.18-4-686, trouble.

On Wed, Feb 28, 2007 at 10:05:30PM -0500, Michael Pobega wrote:
> Whenever I boot into the 2.6.18-4-686 kernel everything works fine,
> but when it starts loading hald I get:
>
> Buffer I/O error on device sr0

after this, I assume the boot continues normally?

>
> It says this about 8 times. I tried reinstalling hal but that didn't
> seem to change anything either.

Does your cd drive work after this has happened?? does this error show
up in dmesg?

A

Upgraded to 2.6.18-4-686, trouble.

On Wed, Feb 28, 2007 at 08:04:02PM -0800, Andrew Sackville-West wrote:
> On Wed, Feb 28, 2007 at 10:05:30PM -0500, Michael Pobega wrote:
> > Whenever I boot into the 2.6.18-4-686 kernel everything works fine,
> > but when it starts loading hald I get:
> >
> > Buffer I/O error on device sr0
>
> after this, I assume the boot continues normally?
>

Correct. It just jumps from the Buffer I/O errors to booting
correctly.

> >
> > It says this about 8 times. I tried reinstalling hal but that didn't
> > seem to change anything either.
>
> Does your cd drive work after this has happened?? does this error show
> up in dmesg?
>

The CDROM seems to be working fine, but it's much louder than normal.
I think I'm going to have GRUB default to *-3-686 for now, until (If)
I can get this solved. It's not the worst thing in the world, but it's
just loud enough to annoy me (I rip and use my CDROM pretty often, so
it's quite annoying).

--

Upgraded to 2.6.18-4-686, trouble.

On Wed, Feb 28, 2007 at 11:25:32PM -0500, Michael Pobega wrote:
> On Wed, Feb 28, 2007 at 08:04:02PM -0800, Andrew Sackville-West wrote:
> > On Wed, Feb 28, 2007 at 10:05:30PM -0500, Michael Pobega wrote:
> > > Whenever I boot into the 2.6.18-4-686 kernel everything works fine,
> > > but when it starts loading hald I get:
> > >
> > > Buffer I/O error on device sr0
> >
> > after this, I assume the boot continues normally?
> >
>
> Correct. It just jumps from the Buffer I/O errors to booting
> correctly.
>
>
> > >
> > > It says this about 8 times. I tried reinstalling hal but that didn't
> > > seem to change anything either.
> >
> > Does your cd drive work after this has happened?? does this error show
> > up in dmesg?
> >
>
> The CDROM seems to be working fine, but it's much louder than normal.
> I think I'm going to have GRUB default to *-3-686 for now, until (If)
> I can get this solved. It's not the worst thing in the world, but it's
> just loud enough to annoy me (I rip and use my CDROM pretty often, so
> it's quite annoying).

yeah, all the references I found to that error point to problems with
cd, so I think that's a good idea. you might hit of the kernel team
and see if they have any insight.

A

Upgraded to 2.6.18-4-686, trouble.

On Wed, Feb 28, 2007 at 09:03:30PM -0800, Andrew Sackville-West wrote:
> On Wed, Feb 28, 2007 at 11:25:32PM -0500, Michael Pobega wrote:
> > On Wed, Feb 28, 2007 at 08:04:02PM -0800, Andrew Sackville-West wrote:
> > > On Wed, Feb 28, 2007 at 10:05:30PM -0500, Michael Pobega wrote:
> > > > Whenever I boot into the 2.6.18-4-686 kernel everything works fine,
> > > > but when it starts loading hald I get:
> > > >
> > > > Buffer I/O error on device sr0
> > >
> > > after this, I assume the boot continues normally?
> > >
> >
> > Correct. It just jumps from the Buffer I/O errors to booting
> > correctly.
> >
> >
> > > >
> > > > It says this about 8 times. I tried reinstalling hal but that didn't
> > > > seem to change anything either.
> > >
> > > Does your cd drive work after this has happened?? does this error show
> > > up in dmesg?
> > >
> >
> > The CDROM seems to be working fine, but it's much louder than normal.
> > I think I'm going to have GRUB default to *-3-686 for now, until (If)
> > I can get this solved. It's not the worst thing in the world, but it's
> > just loud enough to annoy me (I rip and use my CDROM pretty often, so
> > it's quite annoying).
>
> yeah, all the references I found to that error point to problems with
> cd, so I think that's a good idea. you might hit of the kernel team
> and see if they have any insight.
>
> A

It actually ended up just turning out to be the CD, I forgot that it
was in the drive and I think it was scratched up (Or something
similar) because I got the same error when I booted into *-3-*.

Sorry for the false alarm, I guess I just have a really bad memory.

--

Upgraded to 2.6.18-4-686, trouble.

On Wed, 2007-02-28 at 22:05 -0500, Michael Pobega wrote:
> Whenever I boot into the 2.6.18-4-686 kernel everything works fine,
> but when it starts loading hald I get:
>
> Buffer I/O error on device sr0
>
> It says this about 8 times. I tried reinstalling hal but that didn't
> seem to change anything either.
>
> I'm wondering if this is a serious issue (I still have 2.6.18-3-686
> installed and it works perfectly, so I can switch back to using that)
> or if I'll have to recompile the kernel from source to fix this or
> something.
>
> Thanks for your time.
>
>

Hi all,
I also have problem with recent upgrades, once I installed (yesterday)
the new 2.6.18-4-686 kernel I ran into system freezes, but it seemed
to make no difference if I returned to the previous 2.6.18-3-686.

At first I thought about ipw3945* packages, which gave me problems also
in the past, but after I uninstalled them some problems still remain:
gnome-power-manager does not display icon even if it's running and I
had to kill gnome-screensaver which was not responding.

I think the problem is inside some component which was upgraded with
the kernel, maybe hal or acpi.

Anyone has an idea?

Thanks

Giacomo

Syndicate content